> 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. [...] > Advice or workarounds?
I've fixed this in CVS, thanks. The fix is pretty straightforward (just catch the exception in tokenizer.py), so you could apply it to your local copy if you like. =Tony.Meyer -- Please always include the list ([email protected]) in your replies (reply-all), and please don't send me personal mail about SpamBayes. http://www.massey.ac.nz/~tameyer/writing/reply_all.html explains this. _______________________________________________ [email protected] http://mail.python.org/mailman/listinfo/spambayes Check the FAQ before asking: http://spambayes.sf.net/faq.html
