杨枭 skrev den 2013-11-29 08:40:
Thank you all the way.
nope that ip is not hardcoded in a perl module, see your *.cf files
Henrik K skrev den 2013-11-29 08:28:
http://spamassassin.apache.org/full/3.3.x/doc/Mail_SpamAssassin_Conf.html
internal_networks ip.add.re.ss[/mask] ... (default: none)
except that 127.0.0.0/8 is hardcoded
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
On Fri, Nov 29, 2013 at 10:48:42AM +0800, wrote:
>
> but I did not set any ip in the trusted_networks, why SA take the
> 124.73.143.235 as a trusted ip?
In what case not "trusting" internal ip would make sense? What is it that
you are really trying to achieve?
http://spamassassin.apache.org
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
