Hi: We have been running SpamAssassin 2.31 for some time now without problem. We have been using spamc/spamd in the following way:
/usr/bin/spamd -d -a -s local2 And in procmail: :0fw | /usr/bin/spamc Suddenly today spamd seems to have gone bad. When a message is piped to spamc nothing is returned. A spamd process is forked and it seems to go in some kind of a never ending loop and never send anything back. Of course this makes the procmail process hang, which makes the sendmail process hang until there are so many processes on the machine... you get the picture. Changing the procmail recipie to just do /usr/bin/spamassassin -P -a works fine. Has anyone experienced this before, or know what is wrong? As far as I can tell nothing has changed configuration wise that should affect spamassasin in the least. Doing an strace on the spamd process, it seems to be quite interested in reading the file /etc/protocols again and again. I don't know if that helps. I will be digging into it furthur unless someone knows right off what is going on. Thanks -- -------------------------------------------------------------------------- Steven Saner <[EMAIL PROTECTED]> Voice: 316-858-3000 Director of Network Operations Fax: 316-858-3001 Hubris Communications http://www.hubris.net ------------------------------------------------------- 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
