[SA-exim] SA-exim suddenly started ignoring "X-Spam-Status: Yes"

[Rick Moen]

Quoting Sander Smeenk (ssmeenk at freshdot.net):

> The permissions on /var/spool/sa-exim are wrong, if you ask me. They
> indeed should have been Debian-exim:Debian-exim. But this should not be
> the show-stopper for spam detection, afaik.

Concur.  For the record, those would have been created by the sa-exim
.deb that I downloaded from Marc's site, when I converted from Exim3,
last year.

Having done the necessary recursive chown operations on the
/var/spool/sa-exim/ tree, suddenly /var/log/exim4/paniclog became glad
tidings, i.e., null contents.


[On the main matter, denoted by the subject header:]

> > Any clues as to how I figure out what has suddenly broken?
> 
> Logfiles.

It never hurts to give this advice.  ;->  A surprising number of people
are oddly unaware that that's the first place you look.

That's about the second thing I learned about Unix systems, back in the
day.  The first was "98% of all Unix problems turn out, upon
examination, to involve ownership or permissions."

I'm posting in order to reveal the explanation, which turned out to be
that I'd at some point chgrp'd /home/rick/inboxes/junkmail to mail:rick 
instead of rick:rick, and _procmail_, my local delivery agent (not
Exim4, not spamassassin) was unhappy.

Almost certainly, I managed to carelessly do this somehow when I cp'd
/home/rick/inboxes/junkmail to /tmp in order to su to my sa-exim user
and run sa-learn on it.  At that time, I'm in the habit of truncating
the /home/rick/inboxes/junkmail file to zero length, and must have
screwed that step up.

So, it fundamentally wasn't an Exim4 problem, and not an sa-exim one.

-- 
Cheers,        "A raccoon tangled with a 23,000 volt line, today.  The results
Rick Moen       blacked out 1400 homes and, of course, one raccoon."
rick at linuxmafia.com                                  -- Steel City News