So may be something like this hit us too... On Fri, Sep 12, 2003 at 02:57:14PM -0400, Scott Lambert wrote: > If spamc can't connect to spamd, (all slots full on the spamd server), > it just passes the message through. If spamd dies while running under > something like DJB's daemontools, one to several messages could get > through while the spamd daemon is being restarted. > > You probably need more spamd hardware/time slots.
I had exactly that idea and hacked the script which calls my 'spamc -c -d somehost' to loop through a few more hosts, if the result of my 'spamc -c' is '0/0' (which seems to indicate 'no connect to the spamd'). The result was surprising! If the spamc could not reach the first host. ALL hosts could not be reached for a short time! So in my case this looks like a VERY strange reaction to system Parameters like 'load', 'latencies', DNS-Troubles, 'memory-hogs' or other problems vanishing a short time later. The only common denominator was 'suddenly no spamd reachable'. Seconds later and for hours no trouble. THen teh same thing again. May be I'm brking up the wrong tree and my scripting is faulty but the results look the same. Users (and me) wondering how obvious (and if rechecked definitely acknowleged) spam come through. I Don't have the time now but may be somebody could look into sources of spamc and make it (sys)log it's troubles? Stucki ------------------------------------------------------- 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
