Following up... Bill - thanks for your input. Yes, the internal_networks and trusted_network settings are correct. I have 3 mail servers with those settings properly implemented and the other 2 work fine. This particular server is on an old Ubuntu version (14.04) and I will be upgrading it soon so please save the chastisements. I'm stuck with it for now. ALL - running the emails through Spamassassin via the command line does NOT fire the ALL_TRUSTED flag so I am left to believe the issue is with Amavis. I am not using milter. Ubuntu says Amavis is already at the latest version so I guess I would have to manually upgrade. I'm hesitant to do this as it could break the whole server.
I read where the bug on milter that this could potentially cause it in amvisd-new. There was a patch available? I have no idea of how to find that and then no idea of how to install it. For the time being, I just set the ALL_TRUSTED to 0. This is not desirable I know but until I find a fix this all I know to do. If you men have any more ideas I'll try them. Thanks for now! -----Original Message----- From: Matus UHLAR - fantomas <uh...@fantomas.sk> To: users@spamassassin.apache.org Sent: Mon, Jun 26, 2023 5:21 am Subject: Re: ALL_TRUSTED is Always in Headers >>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
