diacritics in from header with from_is_list set to munge
hello,
i just noticed several times now that a bunch of users (most of them subscribed with their yahoo email address) get bounced off my list when the senders address contains diacritical marks in their additional text field describing the name e.g
From: "valérie" <valerie@somesomain.com>
the problem here occurs when setting /munge from/ in from_is_list. the text between the quotes is merged with the string "via " and then the name of the list e.g.
From: "valérie via mylist <this@is.my.list>"
but in mailman 2.1.20 this merging breaks presumably because of the character encoding.
what happens is that the From string in the mailman list header is no longer a valid email address but two totally mixed up. the then have the list name split accross both addresses and the domain is not correct either.
this obviously violates yahoo's dmarc policy and therefore users start to bounce.
what can i do?
thanks in advance, gabriel
On 01/20/2016 11:38 AM, gabriel wrote:
i just noticed several times now that a bunch of users (most of them subscribed with their yahoo email address) get bounced off my list when the senders address contains diacritical marks in their additional text field describing the name e.g
From: "valérie" <valerie@somesomain.com>
the problem here occurs when setting /munge from/ in from_is_list. the text between the quotes is merged with the string "via " and then the name of the list e.g.
From: "valérie via mylist <this@is.my.list>"
I am unable to duplicate this in my development version which I think is no different from 2.1.20 in this regard.
I have tried posting a message with the exact From: header
From: "valérie" <valerie@somesomain.com>
with the é encoded as utf-8 and in another post encoded as iso-8859-1 and in both cases the message delivered from Mailman has
From: valérie via List1 <list1@msapiro.net> Reply-To: valérie <valerie@somesomain.com>
with no quotes and the é encoded as the same encoding as the posted message.
This could be a difference in the underlying Python email package. Mine is Python 2.7.9 with email 4.0.3. What is yours? (do the following)
$ python Python 2.7.9 (default, Apr 2 2015, 15:33:21) [GCC 4.9.2] on linux2 Type "help", "copyright", "credits" or "license" for more information.
import email email.__version__ '4.0.3'
Also, it might help if you post the exact From: and Reply-To: headers in the garbled message.
but in mailman 2.1.20 this merging breaks presumably because of the character encoding.
what happens is that the From string in the mailman list header is no longer a valid email address but two totally mixed up. the then have the list name split accross both addresses and the domain is not correct either.
I'm confused as to what you are saying here and how it relates to the
From: "valérie via mylist <this@is.my.list>"
line in your post. Is that what the From: in the delivered message looks like or just some representation of what you think it should look like?
In any case, the From: I see is
From: valérie via List1 <list1@msapiro.net>
which is technically not valid because it contains a non-ascii character, but even so, the message with that exact From: header is accepted by Yahoo and delivered to my Yahoo address.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
gabriel -
Mark Sapiro