[spambayes-dev] If msg.as_string() fails...

[Tony Meyer]

> Isn't the code in the except clause more-or-less what 
> msg.as_string() itself does?

Basically.  It could probably also just set the type to multipart and that
would work as well, but I'm not really sure of the right way to do that, so
used this.

> I'll give it some thought.  Do we have a message we know 
> makes this process barf?

There are a few around.  I'll attach one to this message - it fails for me
with current CVS SpamBayes, but works ok with code like I posted.

> The few I encountered the other
> day didn't fail on my development machine which runs Python
> from CVS and version 2.5.5 of the email package.
> The machine on which it failed runs Python 2.2.3 and email 
> 2.5.3.  Maybe shipping 2.5.5 with Spambayes and installing it is a 
> reasonable alternative.

That's interesting.  If the attached one works also, then this is probably a
better solution (the binary users won't notice any difference, and it's not
that big a deal for source users to download that, too).

> Didn't we used to ship some version of the email package?  I 
> don't see it in my CVS sandbox now.

It was there once, but is gone (as much as anything is gone from CVS) now.
It was either before my time or right at the time that I started using
SpamBayes (can't recall), so I don't know why it was there or why it isn't
anymore.

=Tony Meyer