[Mailman-Users] rare problem

Jesús Oliván Jesus.Olivan at uab.es
Mon Jul 9 16:34:25 CEST 2007

We've got this mailman version in a production environment and users 
that are not suscribed to a list cannot publish any message and the 
worst fact is that sender cannot know if his message has been sended, 
cause "From" address doesn't exist. Is there any modification we can do 
(some code inside a function) to patch this little bug?

Thanks for your great help =)

Mark Sapiro escribió:
> Hash: SHA1
> Jesús Oliván wrote:
>> I've applied changes in my regexp like u said, thanks!
>> and this is the From line you requested:
>> From: =?ISO-8859-1?Q?123456789-123456789-12345678=E99-123456789-123456789?=
>>  =?ISO-8859-1?Q?-123456789-123456789-?= <ccmjs at cc.mynet.com>
>> This one comes from a mail that has not beed accepted by mailman, 
>> although address in from is allowed by regexp in Allowed senders.
> The problem is a bug in some versions of the Python email library. This
> problem will occur whether the 'address' in *_these_nonmembers is a
> regexp or a string. It also does not depend on the 'real name' being RFC
> 2047 encoded. All that is required is that the 'real name' be long
> enough that the From: header folds into two lines. In this case, the
> email.Utils function getaddresses() returns a spurious extra 'address'
> based on the first line of the folded header and this is the 'address'
> we check against *_these_nonmembers instead of checking the real address.
> This bug exists in Mailman through 2.1.9. I will work around it for
> Mailman 2.1.10.
> - --
> Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> Version: GnuPG v1.4.7 (MingW32)
> iD8DBQFGhSXFVVuXXpU7hpMRAkRpAKDYF1Lk1dsNRfVAgX8QomeswrkadwCfbmVN
> Yk6i/KOIfDCFHUrUGUhurq4=
> =dH8a

More information about the Mailman-Users mailing list