Revenge of SMFIC_BODYEOB reply packet header
My old friend SMFIC_BODYEOB put in another appearance today. Or, more probably, the last six months and I haven't noticed.
GAH! I thought I'd fixed this.
Off to the /etc/default/spamass-milter I ran. No obvious problem...
Next, head scratching.
Then, comparing to my test server, I added in "-d spamc" to the OPTIONS line - which shows input/output to spamc in the mail.log
Sure enough - although spamd was returning a result in about ten seconds (not especially speedy, but it is a Pi) spamc was taking five minutes to return those results to spamass-milter. By then Postfix had given up and delivered the mail.
Jan 12 16:41:20 myserver postfix/cleanup[4860]: warning: milter unix:/spamass/spamass.sock: can't read SMFIC_BODYEOB reply packet header: Connection timed out
GAH! I thought I'd fixed this.
Off to the /etc/default/spamass-milter I ran. No obvious problem...
Next, head scratching.
Then, comparing to my test server, I added in "-d spamc" to the OPTIONS line - which shows input/output to spamc in the mail.log
Sure enough - although spamd was returning a result in about ten seconds (not especially speedy, but it is a Pi) spamc was taking five minutes to return those results to spamass-milter. By then Postfix had given up and delivered the mail.
Jan 12 22:46:03 myserver postfix/smtpd[3108]: connect from localhost[127.0.0.1]
Jan 12 22:46:03 myserver spamass-milter[2979]: output "X-Envelope-From: <ldhsnvf@ca-se-visite.fr>#015#012"
...
Jan 12 22:46:13 myserver spamd[2476]: spamd: identified spam (8.7/5.0) for myuser:1001 in 9.8 seconds, 2139 bytes.
Jan 12 22:47:03 myserver postfix/cleanup[3111]: warning: milter unix:/spamass/spamass.sock: can't read SMFIC_BODYEOB reply packet header: Connection timed out
...
Jan 12 22:51:04 myserver spamass-milter[2979]: input "Received: from localhost by myserver#015#012#011with SpamAssassin (version 3.3.2) ...
Well, at least spamc was talking back to the milter.
Next step - a bit of testing directly with spamc.
spamc -u pi < /usr/share/doc/spamassassin/examples/sample-spam.txtspamc -u myuser < /usr/share/doc/spamassassin/examples/sample-spam.txt
Pi was fine, myuser not so much.
So, what was the difference between them? The ~/.spamassasin bayes data.
After moving bayes* to bayes.bad/ spamc returned to its speedy old behaviour.
I'm not sure if it's corrupt bayes data, or just that after months of sorting spam the bayes files are just a little too big for the Pi to manage in a timely way. Seeing as I've now disabled autolearn it probably doesn't matter much...
I'll put it down as a partial win.
Comments
Post a Comment