On Nov 06, 2013, at 09:05 AM, Stephen J. Turnbull wrote: >For lists hosted by the same Mailman, Mailman 3 might be able to >handle this by adding *both* List-Ids to the header, and only adding >the (other) RFC 2369 headers for the list(s) the user is subscribed >to. Of course this requires personalization, but that seems to be >less and less a problem these days.
MM2.1 adds X-BeenThere headers for every list the message flows through; these are to prevent loops. However MM3 got rid of this header in favor of the RFC 2919 List-ID headers. I took a quick look at that RFC just now and I didn't see anything about how many List-Id headers a message could have, but from the discussion it seems to assume there'd only be one header per message. >If that solution is interesting to anybody, please let me know, and >I'll check the relevant RFCs to see if multiple values are permissible >for List-* headers (and for which ones). Code of course will depend >on Barry's permission, but I suppose he wouldn't object to providing >it as an option. Best to file a bug so we can explore the issue and solutions. You can then attach a branch to the bug. Cheers, -Barry
signature.asc
Description: PGP signature
------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
