[Aside: I sent my previous message from the wrong address, and it was rejected. I am *not* resending it, since Mark quoted everything at some point. Nobody except me lost mail, and I deserved to! :-]
Mark Sapiro writes: > On 01/20/2016 04:23 PM, Stephen J. Turnbull wrote: > > Really? It's not that you're looking at this in your MUA and it's > > being silently MIME-encoded and -decoded at the MTA/MUA boundary? > > Really. OK, just checking. > > One thing I've seen is this: > > > > in MUA UI: From: [email protected] (non-ASCII display name) > > > > on the wire: From: [email protected] (non-ASCII display name) > > Yes, I see where that would be an issue, but as far as Mailman is > concerned, this would only be an issue if the incoming post had that > From: header. > Mailman would never create a header like that. Absent a bug in the email package. But yes, I'm suggesting exactly that there's a broken MUA out there sending something that doesn't parse correctly, and the email package is failing to respect the "In the face of ambiguity, refuse to guess" Zen. We really need to see both the input and the output headers that Mailman sends and receives. Steve ------------------------------------------------------ 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
