At 4:57 PM +0900 4/13/07, Stephen J. Turnbull wrote: > 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.
Correct. There's nothing that Mailman can do to help with this situation. > So site admins need to make sure via the DNS, not Mailman, that what > goes out is what is going to come back. Right? Also correct. But we need something in our FAQ to identify what the real problem is and what the appropriate admins will have to do, because Mailman administrators will certainly be affected by this kind of thing, even if there's nothing they can do to prevent it. -- Brad Knowles <[EMAIL PROTECTED]>, Consultant & Author LinkedIn Profile: <http://tinyurl.com/y8kpxu> Slides from Invited Talks: <http://tinyurl.com/tj6q4> ------------------------------------------------------ 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
