On Thu, 9 Jun 2016 02:54:34 -0700 (MST) jimimaseye wrote: > FEEDBACK for all who have contributed: > > I have a result. > > It seems that the 'internal_networks' is only adhered to *in the > absence* of a 'trusted_networks' entry. If I remove the > 'trusted_networks', and simply leave: > > internal_networks 195.26.90.
It shouldn't matter whether whether you specified trusted_networks as long as it contains all of the relevant addresses seen in the headers. It's now working, but this doesn't explain why it wasn't working before. > then it is correctly applied: > > X-Spam-Report: > * -0.0 SHORTCIRCUIT Not all rules were run, due to a > shortcircuited rule > * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP > * > > I then confirmed this discovery be re-re-re-reading the LOCAL.CF wiki > manual The wiki isn't the manual: https://spamassassin.apache.org/full/3.4.x/doc/Mail_SpamAssassin_Conf.html see also http://spamassassin.apache.org/full/3.4.x/doc/ > which does suggest 'trusted' networks takes precedence and is > a 'one or the other' affair. So, if a TRUSTED entry exists, and you > want to add another network ('internal' or otherwise) then it should > be just added to the TRUSTED entry as ultimately it does exactly the > same thing (both get deemed as "trusted" and bypassed with the > "shortcircuit ALL_TRUSTED" option set, as shown above). Only without > a 'trusted' entry will an 'internal' entry get applied. No that's wrong. Everything that's in internal has to be in trusted. But if you define only trusted or only internal, they are assumed to be the same.
