Sorry, my bad. Output from list_members LISTNAME shows email addresses 
containing &#8203 like m...@example.com&#8203, but without semicolon (;) used 
in HTML.

All the affected members seems to have been added by mass subscribtion from an 
admin so maybe the Mailman web interface form have been altered somewhere. I 
wonder why it's random though.

Thank you for the command. I will look further in to the problem.

Yours faithfully
 
Henrik Rasmussen
Systemadministrator, Core Services






> -----Oprindelig meddelelse-----
> Fra: Mailman-Users [mailto:mailman-users-
> bounces+her=adm.ku...@python.org] På vegne af Mark Sapiro
> Sendt: 21. oktober 2015 05:59
> Til: mailman-users@python.org
> Emne: Re: [Mailman-Users] Some subscriber's e-mail adresses contains
> linebreak unicode character 
> 
> On 10/20/2015 01:52 AM, Henrik Rasmussen wrote:
> > In some occasions, a few subscribers of different lists contains the
> character ​ in the mail-address, like
> m...@example.com&#8203;<mailto:m...@example.com&#8203;> preventing
> them from receiving any mails from Mailman. The Unicode is always the
> same on affected subscribers.
> 
> 
> I am confused. Are you saying the addresses end with an actual Unicode zero
> width space character or that they end with the ascii string '&#8203;'. If the
> latter, I don't see how this can happen. In no version of Mailman 2.1 back to
> pre 2.1.1 has a ';' been allowed in an email address. If the former, an 
> address
> with '\u200B' (the python escape for that character) in the domain would not
> have been allowed since Mailman 2.1.15, but may have been allowed before
> that.
> 
> 
> > As what I've read it is a zero space line break unicode character. So far 
> > the
> only think I found was about HTML pages containing the character and a
> single post explains something about the character being added to a page
> through the Office 365 Public Website editor. But since subscribing to a
> Mailman list does not involve an editor, I assume that the character could
> have been added by a webbased mail client.
> 
> 
> That is probably correct, but gmail's web mail in particular (which I once
> thought was good about stuff like this) and probably others when composing
> in 'rich text' and creating a multipart/alternative message, sometimes creates
> a text/plain alternative littered with these characters.
> 
> Thus, if one composes an email in Gmail's web client to the list-request
> address with a body line
> 
> subscribe m...@example.com
> 
> It is possible the text/plain alternative will have a zero width space 
> appended
> to the address.
> 
> 
> > I don't know whether the subscribers have subscribed through mail or
> through the Mailman web interface, but since the problem is random, I
> assume that the Mailman web interface is not associated. I guess that it must
> be some kind of common web based MUA they have used, like Gmail or
> Hotmail or similar.
> 
> 
> Have you looked at Mailman's subscribe log?
> 
> 
> > What could course this and how can I prevent it?
> 
> 
> Conjecture on cause above. Prevention - upgrade Mailman to >= 2.1.15
> 
> --
> Mark Sapiro <m...@msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users@python.org
> 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/her%40adm.ku.dk
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
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

Reply via email to