There is no way for the Mailman developers to fix this, since if they didn't have the Sender address be the list bounce address then all of Mailman's bounce handling would no longer work, and the author of the message would get flooded with bounces that they don't care about and cant do anything about.
The "Sender:" header field is not used in bounces. The envelope sender information is used in bounces. It so happens that Mailman is recording the envelope sender information in the "Sender:" field, but it could always do that in a different field. Mailman would simply need to be programmed to detect that information in a different field.
Nevertheless, this is common usage for the "Sender:" field, according to the RFCs and the typical usage on the entire rest of the Internet.
Fixing Mailman will not fix the entire rest of the Internet. Try fixing the broken client instead.
-- Brad Knowles, <[EMAIL PROTECTED]>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)
------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
