We had similar problems. Running spamd with debugging on a different port showed that it could get a list of machiens in the razor.vipul.net zone, but could not connect to the closest machine. It sat there and continued to try again and again. This was during the startup of spamd using version 2.20. I suspect that the already running daemon was doing something simmilar. Sorry I do not have the output in my buffer anymore.
It was up and running a few hours later. I am just about to run spamd again. This certainly caused a denial of service on our mail system! Cheers, Stuart. At 01:24 PM 11/10/2002, Steven Saner wrote: >Suddenly today spamd seems to have gone bad. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
