On 2022/12/26 23:47:41 Benny Pedersen wrote:
X-Originating-Ip should not be used for whitelists, only for blacklist
rbl, even on only blacklist its unsafe to use, rules maintainers can
remove it, now that spamassassin 4.0.0 is out :)
read "perldoc Mail::SpamAssassin::Conf" to see how this header is
included, and remove it
man Mail::SpamAssassin::Conf
works too on Debian and should work on Debian-based distributions, Ubuntu
including
On 27.12.22 13:04, John Stimson via users wrote:
Thanks -- I found a mechanism that empties the list of headers used to
determine the originating IP. I added this line to my local.cf:
clear_originating_ip_headers
I recommend checking:
trusted_networks
clear_trusted_networks
internal_networks
clear_internal_networks
these to be set up properly instead of just clear_originating_ip_headers
- you should still check them, as they give you opportunity to check proper
headers in DNS, not just in DNSWL.
spamassassin -D metadata,netset,received-header < mail
should produce nice output of header processing
Upon restarting the amavisd-new service, the messages that got through
before no longer trigger the DNSWL_HI test. I hope that's what you
had in mind!
I am looking forward to having time to update to Kubuntu 2022.04 LTS
and getting spamassassin 4.0.
--
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.
"The box said 'Requires Windows 95 or better', so I bought a Macintosh".
