[Spambayes] Re: Outlook plugin plus Exchange

[Tim Peters]

[Mark Hammond]
> I believe the email package should give some consideration to the
> real world here.

It tries to, starting in 2.2.2:

    http://www.python.org/doc/current/lib/node383.html

The Parser class defaults to non-strict now, but as the docs say

    this doesn't mean MessageParseErrors are never raised; some ill-
    formatted messages just can't be parsed

I'm sure Barry would be willing to entertain this specific case as a bug
report.  In theory, he reads this list, so should be shamed enough to do
that himself <wink>.

> While creating well-formed messages is clearly mandatory,
> it is very frustrating when something exists in the real world, is
> clearly invalid, but everything else in the world has no trouble
> with it.

In this specific case, it looks like Outlook created damaged headers itself,
and Outlook doesn't care because *it* never *looks* at the headers again.
It already sucked out the HTML and stored it in a property, and that's the
only part it looks at again; the Subject and From etc are also tucked away
in other properties.  So as far as Outlook is concerned,
PR_TRANSPORT_MESSAGE_HEADERS is passive trash.

At least that's my guess <wink>.

> ...
> happy with the message.  Eg, how much smarts do we move back into the
> plugin?  Do we try and recover any headers at all? etc.

In this case I will; the form of the damage is clear and easily wormed
around, provided you know what you're looking for in advance.