On Thu, Jan 21, 2016 at 10:50:55AM -0800, Mark Sapiro wrote: > On 01/21/2016 10:40 AM, gabriel wrote: > > On Thu, Jan 21, 2016 at 10:15:33AM -0800, Mark Sapiro wrote: > >> > >> So there are no archives from which to retrieve what I asked for. I'm > >> still interested in seeing the unmunged, raw headers from the message > >> delivered by Mailman, but I'm sure I know what's happening. > > > > i'm sorry there's really no easy way for me to get the raw headers before > > they > > are processed by mailman. but i guess you've already identified the problem > > correctly anyway. > > > I said "I'm still interested in seeing the unmunged, raw headers from > the message delivered by Mailman" I.e., the message FROM Mailman, not > the message TO Mailman.
I don't quite understand. Mailman is configured to munge the From header. When a message passes Mailman, headers will be munged. how could i get a unmunged, raw header message delivered by Mailman? If i set the list to from_is_list = off all my users will get bounced by yahoo. do you want me to enable archives and wait for another incident? > > The problem is really an MTA bug just triggered by a Mailman bug. I'd > like to see that message so I can see what MTA(s) it passed through > after Mailman and possibly file a bug report with the MTA. yes sure that makes sense, too. ------------------------------------------------------ Mailman-Users mailing list [email protected] https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
