It's possible, the local DNS server becomes non-responsive -hate Microsoft- restarting DNS service is not solution, I have to restart machine. *** I DIDN'T VERIFY IT'S THE ROOT CAUSE OR NOT ***
I also have spamd crash problem, it crashes very often: Application: spamd.exe, version 3.3.1.2, timestamp 0x4b75db31, modul IPHLPAPI.DLL_unloaded, version 0.0.0.0, timestamp 0x49e037a4, code 0xc0000005, error loc 0x74f83386, eventid 0xe98, app startup 0x01cb23e00ec14618. So, I wrote a batch file which one checks and recovers the service, if necessary, in every 5 minutes. I use free cryping.exe utility. --- Recover-Spamassassin.bat --- c: cd \NET\Services cryping -port 783 127.0.0.1 | Find "100%%" > nul @If ErrorLevel 1 Goto OK :RESTART @echo Restarting Spamassassin & MTA services... @call restart-spamassassin&mta.bat @echo Done! @echo %Date%, %Time%, RESTARTED >> recover.log @GoTo EXIT :OK @echo Everything seems OK! @echo %Date%, %Time%, OK >> recover.log @GoTo EXIT :EXIT @rem pause > nul On Thu, Jul 15, 2010 at 2:58 AM, Matt Kettler <mkettler...@verizon.net>wrote: > On 7/14/2010 11:27 AM, Emin Akbulut wrote: > > I noticed randomly while I was testing SA. All I did is below: > > WinSpamC < realspam.txt > result1.txt > NET STOP Spamassassin > NET START Spamassassin > WinSpamC < realspam.txt > result2.txt > WinSpamC < realspam.txt > result3.txt > > result1: under 6.3 > result2: very high > result3: under 6.3 > > That is quite strange.. sounds like you've got DNS timeout problems. > > Might want to check the DNS settings on your machine and make sure all of > the listed DNS servers are working and are capable of properly resolving > internet hosts. > > SpamAssassin will *NOT* query every DNS server in your setup. It will pick > one, and query it. If it gets no response, SA goes with that and does NOT > ask the other DNS servers. So if there's a dead DNS server in your config, > that's not so good for SA. >
