The mailing list for listmasters using Sympa

[Israel Cardenas <address@concealed>]

Hi again.

I think the error is one of this (or both):

no decoder for us-ascii at
/usr/lib/perl5/site_perl/5.8.8/MIME/Entity.pm line 1881
no decoder for us-ascii at
/usr/lib/perl5/site_perl/5.8.8/MIME/Parser.pm line 821

We have found the messages which are choking Sympa (today have
happened again), have a Subject like this:

Subject:
        
=?iso-8859-1http-equivContent-Type?Q?una_escapada_con_ni=F1os_en_La_Const?=
        =?iso-8859-1http-equivContent-Type?Q?ituci=F3n____?=

The problem is this: iso-8859-1http-equivContent-Type .

If I remove the "http-equivContent-Type", then Subject is:

Subject:
        =?iso-8859-1?Q?una_escapada_con_ni=F1os_en_La_Const?=
        =?iso-8859-1?Q?ituci=F3n____?=

It works ok, no problem with sympa.pl.

We are trying to protect our system from those mails with a system
filter, and trying to found how to update Perl to fix this bug.

Help will be welcome :)




El día 25 de noviembre de 2010 21:58, José María Palacio Carabias
<address@concealed> escribió:
> Hi all,
>
> Having a look at the error message "Unrecognised BOM 5000", it seems to be
> thrown by Encode::Unicode, one of the dependencies of MIME::Charset module.
> A new version of Encode module was released last September.
>
> Maybe, upgrading this module instead of Sympa could solve the crashes.
>
> Regards
>
> El 25/11/2010, a las 19:04, Omen Wild escribió:
>
>> Quoting Israel Cardenas <address@concealed> on Thu, Nov 25 13:06:
>>>
>>> We can't see anything unusual with this message. I'm thinking if you
>>> have found anything unusual with the messages when the same fail
>>> occurs to you.
>>
>> We have found 2 types of messages that choke 6.0.1: very large
>> messages, and messages with broken/invalid MIME in headers.  We see a
>> line like the following in spool/tmp/*.stdout:
>> UTF-16:Unrecognised BOM 5000 at
>> /ucd/pkg/perl-5.10.1/lib/site_perl/5.10.1/MIME/Charset.pm line 697.
>>
>> From the changelog it looks like the MIME issue is fixed in later
>> releases.
>>
>> There was a comment by David Verdin earlier in this thread that "any
>> version prior to 6.1.3 can have such a weird problem when a too big
>> message is refused". I can't find anything in the changelog for 6.1.3
>> that matches up with that statement though.
>>
>> We're hoping that upgrading will solve all of our crashes.  It's on my
>> todo list.
>>
>> --
>> Omen Wild
>> Security Administrator
>> (530) 752-1700
>
>
>