On 3/19/2005 16:16, "Zoran Dzelajlija" <[EMAIL PROTECTED]> wrote:
> Mark Sapiro <[EMAIL PROTECTED]> wrote: >> It looks to me like a Postfix configuration problem, i.e. Mailman is >> sending the mail as it should and Postfix is not accepting it because >> it doesn't like the sender <[EMAIL PROTECTED]>. > > Shouldn't that be <[EMAIL PROTECTED]> (as per rfc2821, 4.1.3)? > Indeed. Thanks to 3Com and friends, 64.40.10.147, which was once syntactically invalid, is now simply a syntactically correct FQDN which doesn't have a host to be the name of (there is no 147 top level domain). To be a IP literal, the IP indeed needs to be inside a bracket pair (as it long has...well before 3Com caused domain names to be much harder to recognize than they should be). Postfix is configured "correctly" by some definition of correct. The sending entity needs to get it right. If mailman is generating the <[EMAIL PROTECTED]>, Mailman is incorrect. --John ------------------------------------------------------ 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
