You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by Apache Wiki <wi...@apache.org> on 2008/11/21 12:30:15 UTC
[Spamassassin Wiki] Update of "TrustPath" by MattKettler
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.
The following page has been changed by MattKettler:
http://wiki.apache.org/spamassassin/TrustPath
The comment on the change is:
Description of the two cases got lost in editing. Added back.
------------------------------------------------------------------------------
- SpamAssassin, by default, will automatically attempt to figure out which Received: headers were inserted by mailservers in your network, and which were not. This auto detection works pretty well for most networks, but when Network Address Translation (NAT) is involved there are two possible configurations that SpamAssassin cannot automatically detect the difference between. Also, if you have a large or complex network topology, it's strongly recommended you set this (most ISPs, for instance).
+ SpamAssassin, by default, will automatically attempt to figure out which Received: headers were inserted by mailservers in your network, and which were not. This auto detection works pretty well for most networks, but when Network Address Translation (NAT) is involved there are two possible configurations that SpamAssassin cannot automatically detect the difference between. One case is where your MX has a publicly routed IP, and the other where it does not. Looking at Received: headers alone, SA cannot distinguish between the two, so it assumes your MX has a public IP. Also, if you have a large or complex network topology, it's strongly recommended you set this (most ISPs, for instance).
The common symptoms of a broken Trust path include:
* ["ALL_TRUSTED"] matching spam email from the outside or other untrusted mail.