Remember that spamc will only scan messages that are 250KB or smaller. Could it be that some larger messages are the ones that you saw without any SA headers?
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Scott > Doty > Sent: Wednesday, March 20, 2002 11:43 PM > To: [EMAIL PROTECTED] > Subject: [SAtalk] Anyone seeing a spamc/spamd timeout? > > > I'm using spamc from my .procmailrc to talk to a dedicated spamd box. > I'm seeing an intermittent failure of the system, and I thought I'd > ask if others have seen the same thing. > > Essentially, there are spams making it through to my mailbox which > don't even have an "X-Spam-Status" header. Yet, I'm certain that > the spam was passed to spamc by procmail. > > Once I caught it in the act -- an strace of spamc showed it sitting on > a "read(3,...)", which is the server file descriptor. Since I invoke > spamc thusly: > > :0fw > | /opt/protect/bin/spamc-new -f -d spamcan -p 783 > > ...I'm assuming that spamc is timing out, and the procmail failsafe flag > is taking over. > > Has anyone else seen this problem? > > Also, our spamd is patched to avoid the cpu-churning regex problem. > > Thanks, > > -Scott > > _______________________________________________ > Spamassassin-talk mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/spamassassin-talk > _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
