Migration to PGLister - Mailing list pgsql-www

Greetings!

This list has now been migrated to new mailing list software known as
'PGLister'.  This migration will impact all users of this mailing list
in one way or another.

If you would like to unsubscribe from this mailing list, please click on
'Show Original' or 'Show Headers' in your client and find the
'List-Unsubscribe' header which will include a link that you can click
on (or copy/paste into your browser) and use to unsubscribe yourself
from this list.

The changes which we expect to be most significant to users can be found
on the wiki here: https://wiki.postgresql.org/wiki/PGLister_Announce the
current version of which is also included below.

Note that the pgsql-hackers email list is used in examples below, but
this change applies to all project mailing lists.

Managing subscriptions and unsubscribing
--------------------------------------------------------------------
* PGLister includes a web interface which is greatly improved from the old majordomo2 system.  Users can log into the
PGListersystem using their regular community account [2]. 

* The URL for users to manage their subscriptions in PGLister [3] is: https://lists.postgresql.org/manage

* At this page, users can subscribe, unsubscribe, and adjust parameters associated with their mailing list
subscriptions.

* There is also an option at the above URL to have a test email sent from the mailing list system as if it were being
sentfrom the list, to assist users with testing their filter settings. 

* List members who do not have a community account [2] may create an account and then, through the PGLister web
interface,associate their email address(es) with their account. 

No adjustment of Subject: lines any longer
--------------------------------------------------------------------
* The "Subject:" header will no longer be changed to include the name of the list (for example, "[HACKERS]").  This
changeis to avoid breaking DKIM [1] (a standard for preventing nefarious changes in email between the sender and the
receiverby calculating a hash of certain headers and the body).  Not breaking DKIM signed messages will make it less
likelythat emails sent through our mailing lists will be classified as spam. 

* If you filter your email based on those "Subject:" header insertions, you will need to adjust your filtering rules.
Werecommend looking at the industry standard "List-ID:" header instead. 

New email addresses for the lists
--------------------------------------------------------------------
* Existing email addresses will continue to work for a while

* For example, this means that pgsql-hackers(at)postgresql(dot)org will change to be
pgsql-hackers@'''lists'''.postgresql.org.

* Having a flat namespace that both lists and user accounts, as well as other addresses, live in has been a maintenance
issuefor the PostgreSQL Infrastructure team. It also prevents us from implementing DKIM [1] on messages from
postgresql.org. Moving the lists to "lists.postgresql.org" reduces this burden, allows us to implement DKIM [1], and
allowsadditional flexibility for handling other lists in the future. 

* The existing list email addresses will work for some time, but eventually must be retired for us to realize the
maintenanceburden reduction. 

Other email header changes
--------------------------------------------------------------------
* The old majordomo2 system used both non-standard and industry standard headers to provide information about which
lista given message came from. 
* PGLister will use standard, industry-recognized headers to identify mailing list messages.  The non-standard header
"X-Mailing-List"will no longer be included.  Any users whose filters are based on this non-standard header will need to
adjusttheir filters. 

* The value of the headers will also be changing, to match the change of list names.  The header "List-ID" will be
changedfrom, eg, "List-ID: <pgsql-hackers.postgresql.org>" to "List-ID: <pgsql-hackers.lists.postgresql.org>".  Users
whohave filters defined to use this header will need to adjust their filters to account for this change. 

* Certain email providers should be able to take advantage of these headers automatically to provide things such as an
"Unsubscribe"button, but we cannot guarantee this as it depends on their systems. 

Email footer removal
--------------------------------------------------------------------
* The footer text inserted by the old majordomo2 system will no longer be included in each email (the footer is the
textwhich starts with: "Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)"). Removing the
footeris necessary to avoid breaking DKIM [1] signed messages as they pass through our system. 

Cross-posts not de-duped
--------------------------------------------------------------------
* Emails cross-posted to multiple lists will no longer be de-duped, so if posted to two lists the message will be
deliveredtwice. Both copies will have the same message-id (and can be locally de-duplicated on that), but different
envelopesender and recipient addresses. 

Digest capability offered by majordomo2 no longer supported
--------------------------------------------------------------------
* This was discussed with a few of the users who use digest and determined to be acceptable.

* Using digest emails also caused problems when a user replies to the digest email.

* There are no plans to implement digest capabilities in PGLister in the future.

Thank you!

Stephen (on behalf of the pginfra team)

[1]: DKIM - https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail
[2]: Community Account - https://www.postgresql.org/account
[3]: Manage subscriptions - https://lists.postgresql.org/manage