Re: Could not extract score from <>

[Dan Nelson]

In the last episode (Aug 02), Giles Coochey said:
> Recently, since about Friday, the incidence of the following has markedly
> increased:

Line wrapping fixed.  When you paste logfiles, it's much easier to read them
if you leave them as one line per log entry:
 
> Aug  1 11:04:48 gate sm-mta[5348]: i71A4cli005348: from=<address@hidden>, 
> size=6077, class=0, nrcpts=1, msgid=<address@hidden>, proto=SMTP, daemon=MTA, 
> relay=[218.190.26.60]
> Aug  1 11:04:48 gate spamd[1934]: connection from localhost [127.0.0.1] at 
> port 58514
> Aug  1 11:04:48 gate spamd[5352]: processing message <address@hidden> for 
> root:1005.
> Aug  1 11:04:50 gate spamass-milter[5349]: Could not extract score from <>
> Aug  1 11:04:50 gate sm-mta[5348]: i71A4cli005348: Milter add: header: 
> X-Virus-Scanned: clamd / ClamAV version 0.70, clamav-milter version 0.70j
> Aug  1 11:04:50 gate sm-mta[5359]: i71A4cli005348: to=<address@hidden>, 
> delay=00:00:10, xdelay=00:00:00, mailer=esmtp, pri=36077, 
> relay=sanitized.mirada-solutions.com. [ip.ip.ip.ip] , dsn=2.0.0, stat=Sent ( 
> <address@hidden> Queued mail for delivery)
> 
> I am wondering whether spammers are now attempting to exploit a problem
> with the software that causes this error to occur and allow their spam
> through. I notice that this error _only_ appears to happen when the
> message is spam - is it possible that some some malformed message causes
> this error?

Possible.  If you add "-d spamc", you can see the message sent and the
result returned from spamassassin itself.  That message is printed when
spamass-milter can't find the X-Spam-Status: header.  It could be caused by
a parsing bug.
 
-- 
        Dan Nelson
        address@hidden