Brad Knowles writes: > At 4:25 PM +0900 4/12/07, Stephen J. Turnbull wrote:
> > And on which host? Ie, is it that [EMAIL PROTECTED] composes a message > > "To: [EMAIL PROTECTED]", and the MTA at example.com is rewriting that > > to "To: [EMAIL PROTECTED]"? If so, it's purely a DNS issue and > > neither Mailman nor Mailman's MTA can do anything about it. Or is the > > MTA at hosting-service.dom rewriting it before redistributing? Or > > what? > > Well, the way that the standards were previously interpreted was that > this sort of transformation should always be done, and on all hosts > that would be touching the message. So, even if you didn't do it, > the machine downstream should. Right, my point is that readers of the Mailman FAQ are are there because they're thinking "Mailman 'should' be able to do something about this", but as I understand it (I haven't actually had to deal with, so I haven't seen it "in the wild") you've saying the rewriting could be happening *anywhere*, so there's not much that Mailman can do. So site admins need to make sure via the DNS, not Mailman, that what goes out is what is going to come back. Right? ------------------------------------------------------ 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/ 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
