On 2022/12/28 12:45:48 Matus UHLAR - fantomas wrote:
have you reloaded amavisd?
On 28.12.22 08:50, John Stimson via users wrote:
I restarted the amavisd-new.service and spamassassin.service after
editing /etc/spamassassin/local.cf
spamassassin service is not needed when you use amavis, you can stop and
disable it.
do you have anything set in amavis' home directory?
usually ~amavis/.spamassassin
~amavis/.spamassassin contains a file user.prefs that has only comment
lines. Could /etc/spamassassin/local.cf be ignored when spamassassin
is invoked by amavis?
no, it's being used, but amavis won't notice the change until you reload
amavis (not spamassassin/spamd)
On the incoming mail , the
X-Spam-RelaysUntrusted: header is not being added for messages that
are not flagged as spam.
There is another strange thing: I received two messages today that
triggered the RCVD_IN_DNSWL_HI test, but there was no
X-Originating-IP: header -- re-running the message through
spamassassin from the command line, the IP number from the first
untrusted Received line was specifically listed as being in
lists.dnswl.org, even though a manual test at the dnswl.org web site
showed that the same IP was not in their list.
how do you use amavisd, do you use amavisd-milter?
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Despite the cost of living, have you noticed how popular it remains?
