On 2025-09-19 at 14:23:48 UTC-0400 (Fri, 19 Sep 2025 14:23:48 -0400)
Mark London <[email protected]>
is rumored to have said:
I have the following rule:
header BAD_FROM From =~ /\"psfc.mit.edu\"/i
In which file did you add that rule?
If it was somewhere other than a file matching
/etc/mail/spamassassin/*.cf then that is almost certainly the root of
the problem.
It doesn't get triggered when the email is received. But if I run
spamassassin from the command line, it gets triggered.
This indicates with 100% certainty that your mail system is NOT using
the same SA configuration and rules as when you run from the command
line. The most likely cause of that is that the user doing the check in
the mail system is different from the logged in user you have enabled
per-user rules.
There are many different ways to create that problem, differing by how
you have hooked SA into your mail system (milter? delivery agent content
filter? SMTP proxy?) and which particular software you're using
(Postfix? Sendmail? Amavis? MIMEDefang? spamass-milter?) in that system.
If you run the spamassassin script from the command line with the option
"-D config,rules" you will see which files are actually being loaded. It
may be possible to identify the problem from that alone, if you see a
file being loaded that your mail system would not.
--
Bill Cole
[email protected] or [email protected]
(AKA @[email protected] and many *@billmail.scconsult.com
addresses)
Not Currently Available For Hire
