Fredrik Steen <[EMAIL PROTECTED]> writes:
> On [050212 15:38] Falk Hueffner <[EMAIL PROTECTED]> wrote:
>> 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 :).
Okay, I see three options:
* Work around this Python 2.3 bug in getmail
* Depend on Python 2.4
* Reassign to Python 2.3 and have them backport the fix
What's your plan?
--
Falk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
