Stephen J. Turnbull wrote:
Detect is one thing, fix is another.
Um, unless I'm mistaken, Mailman will not accept a message in to a mailing list if the header exists and has the list in question listed in said header.
In other words, that's Mailman's loop detection to make sure that a subscribed email address does not get re-routed in to the mailing list, forming a nasty loop.
So, I think this does "fix" this problem.
Certainly it makes sense to cut out all but one of the "received" headers for the list host, though, since you'll have MTA logs to trace that.
Well, unless the mail logs include all the contents of the Received: headers, not everything would be logged.
Sure, the system that the message was (directly) received from would be logged, but none of the earlier Received: headers.
I've never had a need to do so, but I have considered (and thought about how to do so) a pre-Mailman archive on the server that includes the full headers as they would go in to Mailman (or formail that would remove headers).
Grant. . . . ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org