On Apr 20, 2012, at 11:33 AM, Terri Oda wrote: >A question, though: what if the list gets migrated to a new server and the >list id changes (e.g. because the domain or hostname changes)? I'm guessing >we can handle it, but we should make sure there's a path for that.
I have to read RFC 2919 more carefully, but it does have this to say: 4. Persistence of List Identifiers Although the list identifier MAY be changed by the mailing list administrator this is not desirable. (Note that there is no disadvantage to changing the description portion of the List-Id header.) A MUA may not recognize the change to the list identifier because the MUA SHOULD treat a different list identifier as a different list. As such the mailing list administrator SHOULD avoid changing the list identifier even when the host serving the list changes. On the other hand, transitioning from an informal unmanaged-list-id-namespace to a domain namespace is an acceptable reason to change the list identifier. Also if the focus of the list changes sufficiently the administrator may wish to retire the previous list and its associated identifier to start a new list reflecting the new focus. So a migration would typically not change the List-ID. If it does, then it's considered a different mailing list after the migration. Of course, this wouldn't change any headers in messages already sent through the pre-migrated list, nor the archiving of any such messages. It would however change for any subsequent messages sent through the migrated list. Cheers, -Barry _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
