On Thu, 3 Nov 2011 06:59:14 -0700 (PDT) Schorny wrote: > > > Kelson Vibber-2 wrote: > > > > A matter of perspective: You don't need to tell SA to ignore the > > last header, you need to tell it NOT to ignore the second one. > > Generally speaking, SA checks blacklists against the first hop > > outside your internal network. It sounds like your local SA has > > decided that mailserver.provider.com is trusted, so instead of > > starting there, it's starting at the next one out. (And yes, that > > last Received: header should be there.) > > > > I agree with Matus UHLAR's advice: check the trust path settings. > > > > Hi. > > Thank you. This sounds very good, but there are no trusted_networks > configured. We only trust 127.0.0.1 and that is implicit. Therefore > there is no trusted_networks line in our local.cf or any other .cf > File. There are also no internal_networks lines.
I doubt it's anything to do with with *_networks > @Darxus: > The following rules are hitting: > RCVD_IN_CBL, RCVD_IN_SBL_XBL, RCVD_IN_SORBS > Which are IIRC all Spamlists we are checking. By the look of it these are all custom rules, which you have messed-up. e.g. SBL & XBL shouldn't be combined because you are mixing a deep and non-deep list, and you are probably doing the same thing with SORBS. I would suggest you remove these custom rules and use those provided.
