I have known the reason why SA take the ip as a trusted ip.
When a mail whose authentication method is esmtp included the
received-header,
SA will take the ip as a trusted ip.
See the SpamAssassin/Message/Metadata/Received.pm:
# if we find authentication tokens in the received header we can
Hi all:
I'm using SA-3.2.3 to test a spam, the following is the dbg message:
*Nov 29 09:51:19.982 [23076] dbg: received-header: authentication method
esmtpa*
*Nov 29 09:51:19.982 [23076] dbg: received-header: relay 124.73.143.235
trusted? yes internal? yes msa? no*
*Nov 29 09:51:19.982 [2307
