On Wed, Jun 11, 2003 at 12:22:23AM +1200, Simon Byrnand wrote: > When most people on the list here are concerned about scans taking as long > as 5 seconds to complete, your suggestion that people could be waiting > hours for the messages to arrive due to spam filtering is laughable.
It's happened to me, but I didn't laugh! I ran into the problem with the 133MHz laptop I pick my mail up from my ISP every morning: The first sign that there was a problem was that my inbox was filling up with duplicate messages and that fetchmail was reporting an ever increasing number of messages to be downloaded. The problem was caused by using spamassassin, rather than spamd (which I now use) on my lightweight machine, and getting fetchmail to poll the server every 900 seconds. What was happening was fetchmail+perl+spamassassin+procmail was unable to process all the messages during the 900 second time slot, so another fetchmail etc. started - again and again. Also, because all the messages weren't download from the server, they _all_ remained including the ones already downloaded. What I do now is run spamd - much faster and run fetchmail to download the messages accumulated during the night - then put fetchmail in the background polling the server every 900 secs. Regards: Jim Ford ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
