On 6/25/2023 9:23 AM, Matus UHLAR - fantomas wrote:
On 24.06.23 02:12, Denny Jones via users wrote:
Spamassassin Version: 3.4.2Amavisd-new Vrsion: 2.7.1
ALL_TRUSTED is always in every header:Here's an example header:
do you use amavisd-milter?
There's bug in older versions of amavis describes here:
https://gitlab.com/amavis/amavis/-/issues/61
with patch here:
https://gitlab.com/amavis/amavis/-/merge_requests/81/diffs
No, that affects amavis internal handlers. SpamAssassin is getting
called and it is being presented with the proper headers.
You probably noticed I bumped up the ALL_TRUSTED score but even if
use the default value (-1) it still fires on every message.
Any clues as to where to start sleuthing this?
1) As per Bill Cole, I'd double-check your internal_networks and
trusted_networks setting. Usually, this is just the IP address of the
server. Check if any values exist in any other config files; something
like "grep -r trusted_networks" and "grep -r trusted_networks" from the
/etc/spamassassin folder.
2) SA 3.4.2 is about 5 years old. There have been issues with
LASTEXTERNAL, EnvelopeFrom, and AskDNS that have been fixed since then.
I would upgrade SA to 3.4.6.
-- Jared Hall
