[Mailman-Users] diacritics in from header with from_is_list set to munge
gabriel at unseen.is
Thu Jan 21 12:27:42 EST 2016
On Fri, Jan 22, 2016 at 01:06:29AM +0900, Stephen J. Turnbull wrote:
> > From: =?utf-8?q?Val=C3=A9rie/Something_via_mylist_=3Cmyli?=,
> > =?utf-8?b?ZW5AbGlzdHMubXRtZWRpYS5vcmc+?=
> > Sender: "mylist" <mylist-bounces at lists.mydomain.org>
> So this has already been through Mailman. We really really need to
> see the mail as it was *before* Mailman handled it (possibly in the
> mbox file in the archive, if you have it).
That may not be so easy. in fact there is no archive of that list, but haven't
archived messages not been processed by mailman?
luckily exactly this message has been posted on one other list i have access to:
Return-Path: <otherlist-bounces at someotherserver.org>
X-Original-To: otherlist at someotherserver.org
Delivered-To: otherlist at someotherserver.org
Received: from onedomain.de (mail.onedomain.de
by someotherserver.org (Postfix) with ESMTP id DA99150142
for <otherlist at someotherserver.org>; Wed, 20 Jan 2016 16:24:07 +0100 (CET)
Received: from eggmann.mydomain.org (eggmann.mydomain.org [126.96.36.199])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by onedomain.de (Postfix) with ESMTPS id E51E740036
for <otherlist at onedomain.de>; Wed, 20 Jan 2016 16:24:07 +0100 (CET)
Received: from roundcube.mydomain.org ([::1])
by eggmann.mydomain.org with ESMTP; Wed, 20 Jan 2016 16:24:05 +0100
Date: Wed, 20 Jan 2016 16:24:05 +0100
From: valerie at mydomain.org
To: otherlist <otherlist at onedomain.de>
Message-ID: <7e498749e02d18656fd14393b90cdc38 at mydomain.org>
X-Sender: valerie at mydomain.org
Subject: [otherlist] some subject
X-BeenThere: otherlist at someotherserver.org
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Errors-To: otherlist-bounces at someotherserver.org
Sender: "otherlist" <otherlist-bounces at someotherserver.org>
what is grabbing my attention here is that there is no text in the From: field,
only the blank email address. digging little further reveals that the text that
gets merged originates from the members name field with which that address is
associated in mailman.
> And then you've redacted stuff, and that may matter. If you don't
> want to send unredacted headers to a list with public archives, we
> understand, but in that case you can and should send them to Mark (and
> possibly me, but Mark is the real expert if you really want to send it
> to the fewest people) privately.
thank you very much. i appreciate it. i will send the originals to you when
this email doesn't help.
> I don't think this is a Mailman bug. Mailman would not choose to send
> using two different transfer encodings (Q in the first line, B in the
> second). So I suspect Mailman is just forwarding the garbage it
> receives, or something downstream of Mailman is doing it.
More information about the Mailman-Users