You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2019/01/25 22:47:55 UTC

[Bug 7686] RCVD_IN_PBL false positive from X-Originating-IP despite existence of ESMTPSA header

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7686

Bill Cole <bi...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |billcole@apache.org

--- Comment #1 from Bill Cole <bi...@apache.org> ---
FIRST: You've reported the bug against (and your example shows) SpamAssassin
v3.4.0, which is obsolete, buggy and insecure. You should upgrade, and your
problem MAY have been fixed during the 4+ years between the releases of 3.4.0
and 3.4.2. 

Which IP SA checks against PBL (if any) is determined in large part by the
internal_networks, trusted_networks, and msa_networks settings. The IP that is
checked is the last external address (i.e. NOT in internal_networks) which is
recorded by a trusted relay as the source of the message. If the last trusted
relay is in msa_networks, the IP it records as the source is NOT checked. In
this case, I suspect that the problem is that you have 192.95.53.248 in
trusted_networks and internal_networks, but not msa_networks. Any machine which
accepts initial submissions (i.e. from PBL-eligible machines) should be in all
3 network lists in most cases. See the documentation of
Mail::SpamAssassin::Conf for more information. 

If this doesn't help you solve your problem, in order to look more closely at
this we would need a full example to reproduce the problem: a complete and
valid unredacted message which demonstrates the bug AND the relevant
configuration parameters, most importantly the *_networks settings.

-- 
You are receiving this mail because:
You are the assignee for the bug.