You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@spamassassin.apache.org by Marc Perkel <ma...@perkel.com> on 2008/08/26 16:51:49 UTC

spamd: bad protocol: header error

Getting a lot of these:

spamd: bad protocol: header error: (closed before headers) at 
/usr/bin/spamd line 2001.

Not sure what this means. Thanks in advance for your help.

Re: spamd: bad protocol: header error

Posted by Edward Francis Klimowicz <ed...@voicenet.com>.

Marc Perkel wrote:
> Getting a lot of these:
> 
> spamd: bad protocol: header error: (closed before headers) at
> /usr/bin/spamd line 2001.
> 
> Not sure what this means. Thanks in advance for your help.

That implies that something opened up a network socket to spamd, then closed
the socket before either sending any data, or sending any data that spamd
expected.

I see that at my installations when our monitoring software connects to make
sure that spamd is still running/responding; you might also see that if
someone were to open up a telnet connection to the spamd socket.