Re: latest spam-milter

[Dan Nelson]

In the last episode (Nov 19), Cowles, Steve said:
> Thought I would add to this thread. Last night my milter also died
> after running for months withut a single problem. FWIW: I run a low
> volume mail server. 1000+ a day
> 
> I too, see nothing in the logfiles that point to why this happened.
> Well except for the 2 bytes expecting part (see below). I have never
> seen this in any of my logfiles.
> 
> The following logfile entries show when sa-mailter died. Every e-mail
> after this, errored out with the "to error state". Also note the
> size=0 part of the from header portion. Fricken spammers!
> 
> Nov 18 23:59:39 excelsior sm-mta[10358]: gAJ5xcd5010358: 
> from=<address@hidden>, size=0, class=0, nrcpts=1, msgid=<address@hidden>, 
> proto=SMTP, daemon=MTA, relay=[216.52.222.152]
> Nov 18 23:59:39 excelsior spamd[11229]: connection from 
> localhost.mydomain.com [127.0.0.1] at port 2038
> Nov 18 23:59:39 excelsior spamd[10361]: processing message (unknown) for 
> root:99, expecting 2 bytes.
> Nov 18 23:59:39 excelsior spamd[10361]: identified spam (11.1/5.0) for 
> root:99 in 0.0 seconds, 2 bytes.
> Nov 18 23:59:39 excelsior sm-mta[10358]: gAJ5xcd5010358: Milter add: header: 
> X-Spam-Flag: YES
> Nov 18 23:59:40 excelsior sm-mta[10358]: gAJ5xcd5010358: Milter add: header: 
> X-Spam-Report : 11.10 hits, 5 required;\n * -0.0 -- Missing From: header\n  * 
>  9.0 -- Missing Date: header \n  *  0.3 -- Subject: is empty or missing\n  *  
> 0.8 -- BODY: Spam phrases score is 00 to 01 (low)\n  *  1.0 -- Missing To: 
> header
> Nov 18 23:59:40 excelsior sm-mta[10358]: gAJ5xcd5010358: Milter add: header: 
> X-Spam-Level: ***********
> Nov 18 23:59:40 excelsior sm-mta[10358]: gAJ5xcd5010358: Milter add: header: 
> X-Spam-Checker-Version: SpamAssassin 2.42 (1.115.2.14-2002-10-04-exp)
> Nov 19 00:03:39 excelsior sm-mta[10358]: gAJ5xcd5010358: Milter 
> (spamassassin): timeout before data read
> Nov 19 00:03:39 excelsior sm-mta[10358]: gAJ5xcd5010358: Milter 
> (spamassassin): to error state
> 
> etc...
> 
> Every e-mail after this just went through without being processed through
> SA. When I bounced sa-milter/spamd, everything is back to normal.
> 
> Is there any debug info I can supply to help localize this problem? Could
> the zero bytes possibly be casuing this abort?

The milter's header-processing code is pretty simplistic.  I just did a
couple tests sending 0-byte messages, and it couldn't even parse the
X-Spam-Report header out of the message, probably because it was the
very first header and the code checks for "\nHeader: ".

My guess is it crashed trying to process the body text, but I'm not
sure.  I'll have to fix the header-processing bug first :)  

-- 
        Dan Nelson
        address@hidden