Still evaluating and learning about SpamBayes before attempting to put it into production use. I ran into a problem where a message (actual message from my March mail spool) causes a UnicodeEncodeError to be raised due to a bogus Content-Type header.
As the welcome message suggested, I've written a bug. 1175439 https://sourceforge.net/tracker/index.php?func=detail&aid=1175439&group_id=61702&atid=498103 I see that SpamBayes will sometimes catch exceptions and write an exception header, but it doesn't in this case. The exception originates in the email package, and the problem affects at least two high level scripts, so I'm not even sure where to start looking to hack together a patch. Advice or workarounds? Thanks, Jim _______________________________________________ [email protected] http://mail.python.org/mailman/listinfo/spambayes Check the FAQ before asking: http://spambayes.sf.net/faq.html
