Mark Sapiro writes: > [EMAIL PROTECTED] wrote: > > > >But does Mailman have to treat this as an implicit address?
Mark was generous. Yes, it does. Mailman is doing the right thing. Your user's system is broken. Just because people rarely die from misconfigured mail programs doesn't mean they are free from the ethical obligation to fix them. A tool under their control is causing problems for others (specifically you!) They should fix their tools, or pay to have them fixed. Just like a car with bad brake lights. Sure, AFAIK nobody has died from a misconfigured MUA yet, but it's basically the same attitude: "Watch out world, here I come!" > If this is a significant problem, I think the email library is the > place to address it. If it's that much of a problem, I would suggest configuring the MTA to reject it, myself. But I think a better approach is to explain to the user that her mail is being lost and delayed because it doesn't conform to the standards that most systems do. It's not just Rob's list-serving system where this will happen. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
