On [050212 15:38] Falk Hueffner <[EMAIL PROTECTED]> wrote: > Package: getmail4 > Version: 4.2.5-1 > Severity: normal > File: /usr/bin/getmail > > I very often get spam that produces the following error in getmail: > > -snip- > A badly-corrupt message was retrieved and could not be parsed > for the following reason: > > No terminating boundary and no trailing empty line > > Below the following line is the original message contents.
[...]
>
> While this message is probably violating some RFCs, I don't see why it
> "could not be parsed". The end of the message is not marked properly,
> but unambiguous. The "container" confuses spam filters and I get
> annoying mails from my cron job.
>
> getmail should just add a trailing newline and be done with it.
Asked upstream and this is the answer (rewritten somewhat)
No. It's designed to do this.
Later versions of Python's email modue don't fail to parse these messages. So
using python 2.4 och later will make this go away..
With Python 2.3.{4,5} badly-corrupt messages can't be parsed, so getmail
constructs a container to hold the original message and delivers that.
There's not much else it can do; the alternative was to lose messages, and
getmail won't ever do that :).
--
.''`. Fredrik Steen, [EMAIL PROTECTED]
: :' : 2CD6 C838 BE77 795F 5EF1 3E5B DA91 EE7B A58E 164
`. `' http://www.stone.nu/
`-- http://www.debian.org/
signature.asc
Description: Digital signature
