Hiya Has anyone come across error like these before - spamassassin was working perfect - but a couple of days ago - we got flooded with spam. Checking the logs ... errors like the one below come up 25,000 times :-) ... The only solution i've found to work is to keep restarting spamd on a crond ... a temporary fix ..
Sun Mar 11 15:46:15 2007 [26282] info: spamd: connection from mxr1duk.xxxxx.com [127.0.0.1] at port 36877 Sun Mar 11 15:46:15 2007 [26282] warn: spamd: bad protocol: header error: (closed before headers) at /usr/bin/spamd line 1671. Sun Mar 11 15:46:15 2007 [26280] info: prefork: child states: II Sun Mar 11 15:46:20 2007 [26282] info: spamd: connection from mxr1duk.xxxxx.com [127.0.0.1] at port 36878 Sun Mar 11 15:46:20 2007 [26282] warn: spamd: bad protocol: header error: (closed before headers) at /usr/bin/spamd line 1671. Sun Mar 11 15:46:20 2007 [26280] info: prefork: child states: II Sun Mar 11 15:46:25 2007 [26282] info: spamd: connection from mxr1duk.xxxxx.com [127.0.0.1] at port 36879 Sun Mar 11 15:46:25 2007 [26282] warn: spamd: bad protocol: header error: (closed before headers) at /usr/bin/spamd line 1671. Sun Mar 11 15:46:25 2007 [26280] info: prefork: child states: II Sun Mar 11 15:46:31 2007 [26282] info: spamd: connection from mxr1duk.xxxxx.com [127.0.0.1] at port 36880 Sun Mar 11 15:46:31 2007 [26282] warn: spamd: bad protocol: header error: (closed before headers) at /usr/bin/spamd line 1671. Sun Mar 11 15:46:31 2007 [26280] info: prefork: child states: II any assistance would be much appreciated Cheers ... -- View this message in context: http://www.nabble.com/protocol-error-in-spamassassin-tf3386186.html#a9425679 Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
