Mark Sapiro writes: > For Mailman 2.2, I am considering changing the Sender: header from the > LIST-bounces address to the LIST posting address.
IMO the list-post address is semantically inappropriate. The sender header is the mailbox of the agent that injected the message and presumably would want to know about problems. That's not the list membership. I think a better idea is to use a less geeky name like LIST-admin for the bounce recipient. That's already taken, you might say, but in fact I think it works. This has several advantages IMO: 1. If the recipient's MTA uses a standard bounce format, it will work as it does today, with automatic delivery disabling, etc. 2. Other bounces will go to a responsible party who can deal with them. This could be combined with the usual moderator flow, with an additional button "reply with list-help" along with the current defer/accept/reject/discard. (Yes, I know that for some lists this could be a burden.) 3. On broken MUAs it reads correctly: "From list-ad...@example.com on behalf of aut...@net.invalid". 4. Recipients whose MUAs CC the sender can be automatically disabled, too! (Maybe that's not a great idea for corporate MLs where people are using Blackberrys and other such common offenders, but I often wish I could!) ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9