[snip] Ok, I've tracked this down. The reason for this occurring is complex (an explanation is in a message I just posted, if anyone is interested), but basically this problem will occur if:
(1) You are using Python 2.4 (1.0.3 is built with Python 2.4) (2) A connection to the mail server cannot be established and (3) The DNS lookup succeeds It will only take one fail (unfortunately) to enter into a continual loop with the (very unhelpful) asyncore "warning: unhandled exception" message being printed out. The fix I checked in for the original report of large logs (which did not have #3, which results in the "getaddrinfo failed" error, which is only printed once per attempt), would not fix this, as the error never gets from asyncore to SpamBayes. I've checked in a fix that works for me simulating these conditions, so I'm pretty confident it will work for others as well. So the solution is to: (1) Use Python 2.3 (1.0.1 or run from source) (2) Use 1.1 when it is released (or CVS head) optionally with Python 2.4 Or (3) Convince me to do a 1.0.4 release with either this fix or built with Python 2.3, and use that. =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
