> Are the 196.28.80.29, 196.28.80.61, and 196.28.66.13 in your
> trusted X.X.X.X/29 ? If they are, then hitting ALL_TRUSTED is expected.
No, the X.X.X.X/29 is a different server -- one of my own, not in a 186. block,
and definitely not in ZA.
> > Jun 18 22:38:19.967 [19747] dbg: check:
> > tests=BAYES_50,DCC_CHECK,HTML_MESSAGE,UNPARSEABLE_RELAY
>
> See the UNPARSEABLE_RELAY here? It prevents ALL_TRUSTED from firing.
Yes, saw that. Did not realize that it was interfering with any tests or
scoring.
But ALL_TRUSTED _is_ firing,
tests=[ALL_TRUSTED=-1, <==
and triggering the shortcircuit. Or have I misinterpreted the report?
> > Received: from mail-backend.DDDD.com (LHLO mail-backend.DDDD.com)
> > (10.2.2.20) by mail-backend.DDDD.com with LMTP; Thu, 18 Jun 2015
> > 16:50:56 -0700 (PDT)
>
> It is this Received header field above that is supposedly unparsable,
I confirmed
Hm. What is unparseable about that?
> and it was added _after_ a message went though a content filter.
I've a 2 postfix setup --frontend and a backend. IIUC, That header's reporting
delivery by the backend to the IMAP store on the backend.
I see that header on ALL emails received -- most of which neither trigger
ALL_TRUSTED, nor report UNPARSEABLE_RELAY.
I'm not clear why it would be intermittent. There's something else 'off' here
...
