Mark Sapiro wrote: >> But here's the thing: the only occurrence of >> "[EMAIL PROTECTED]" on the fresh system is a .forward file in >> /root, /var/spool/postfix, and /home/ftg. The test message is sent from >> the 'ftg' ID whose home directory is /home/ftg. >> >> Do you guys follow or look at .forward files ? If not, I can't imagine >> how mailman is getting hold of this address. >> > > > No. MDAs look at .forward files. Mailman doesn't know anything about > them. >
End of mystery. My test machines all use a third-party relay server which requires "From:" to be one of a fixed set of pre-registered values. I handle this by using Postfix's "generic" file to rewrite the sender on outbound messages to the 'frank.griffin' address above. Apparently, it also rewrites the "Reply-To:" address. Mailman was correctly setting "Reply-To:" to "listname<listaddress>". Postfix was rewriting "listaddress" to the fixed address from the "generic" file, thus causing the error I saw. This won't affect the machines on which I actually run Mailman for production, so it appears that the porting procedure (augmented by fix_url) is successful. However, this can easily bite anyone who runs a server-type system at home and needs to conform to the sending policies of a commercial relay server. Maybe worth an entry in the FAQ ? Mark, thanks for your time and help in resolving this. ------------------------------------------------------ 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
