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:
On 6/25/2023 9:23 AM, Matus UHLAR - fantomas wrote:
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
On 25.06.23 19:21, Jared Hall wrote:
No, that affects amavis internal handlers. SpamAssassin is getting
called and it is being presented with the proper headers.
nevertheless, this problem caused SpamAssassin rules hitting ALL_TRUSTED
when amavis was called via AM.PDP socket (via milter), see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958462
OP provided headers have amavis syntax, so if OP uses amavisd-milter, there
is his problem.
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.
yes, checking setting of trusted_networks is not a bad idea.
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.
SA 3.4.2 is still in debian 10, and upgrading SA will hardly solve this
problem, if it lies outside of SA.
--
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.
Spam = (S)tupid (P)eople's (A)dvertising (M)ethod
