Re: None

[Dan Nelson]

In the last episode (Jun 12), Valentin Chopov said:
> today I tried the latest spamass-milter from the CVS and I got a lot
> of spamd "bad protocol: header error:..." (see below) in the maillog
> file. What does this mean?
> 
> Jun 12 15:38:30 milter spamd[68946]: bad protocol: header error: (closed 
> before headers)
> Jun 12 15:38:30 milter spamd[14625]: connection from localhost [127.0.0.1] at 
> port 1625
> Jun 12 15:38:30 milter spamd[68950]: processing message <address@hidden> for 
> spamass:1003.
> Jun 12 15:38:30 milter spamd[14625]: connection from localhost [127.0.0.1] at 
> port 1626
> Jun 12 15:38:30 milter spamd[68951]: bad protocol: header error: (closed 
> before headers)
> Jun 12 15:38:30 milter spamd[68950]: identified spam (6.0/5.0) for 
> spamass:1003 in 0.3 seconds, 10774 bytes.
> Jun 12 15:38:31 milter spamd[14625]: connection from localhost [127.0.0.1] at 
> port 1627
> Jun 12 15:38:31 milter spamd[68957]: bad protocol: header error: (closed 
> before headers)
> Jun 12 15:38:31 milter spamd[14625]: connection from localhost [127.0.0.1]

That could be due to a modification I did to the milter; it launches
spamc at MAIL FROM instead of at the first message header.  This means
that if a client connects and you have an access.db entry or DNSBL
check that blocks the message, spamc will get started then killed
before the message gets sent.  I did this so that the milter could send
the envelope data to spamc (greatly increasing its accuracy).  It looks
like I'll have to simply store this info temporarily, move the launch
of spamc back to where it was, and send those lines then.

It shouldn't affect processing of regular email.  I'm not sure why I'm
not seeing similar entries myself, though.

-- 
        Dan Nelson
        address@hidden