Re: [Evolution] Header parsing problem

[Not Zed <notzed ximian com>]

please open a bug report and attach the COMPLETE message, not just a too-small-to-work-anything-out snippet of it.

On Sat, 2004-12-11 at 15:49 +0100, Miravlix wrote:
> --original header--
> Content-Type: multipart/mixed;  boundary="===6d69ec71.a411"
> Content-Transfer-Encoding: 7bit
> This is a multi-part message in MIME format.
> X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at lix-world.net
> X-Amavis-Alert: INFECTED, message contains virus: Worm.Sober.I
> X-Amavis-Alert: BANNED FILENAME, message contains part named:
>         auto__mail.manchester.7693.com
> --end header--
>
> --Evolution view--
> Content-Type: multipart/mixed;  boundary="===6d69ec71.a411"
> Content-Transfer-Encoding: 7bit
> X-Evolution-Source: mbox:/var/mail/dragon
>
> This is a multi-part message in MIME format.
> X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at lix-world.net
> X-Amavis-Alert: INFECTED, message contains virus: Worm.Sober.I
> X-Amavis-Alert: BANNED FILENAME, message contains part named:
>         auto__mail.manchester.7693.com
> --End view--
>
> I was originally thinking Amavis was doing something wrong here, but
> looking at the email before Evolution 'fixes' it says otherwise.
>
> Looks to me like Evolution is deciding that "This is a multi-part
> message in MIME format." is a end of header indicator, breaking software
> that follow normal rfc rules for header detection.

--

Michael Zucchi <notzed ximian com> "Ride, Work, Sleep. Beer." Novell's Evolution and Free Software Developer