Mike Sassaman wrote: > > > Ok, so according to the logs it seems that just about every spam message is > hitting the ALL_TRUSTED rule. Maybe this is my problem. I understand that > indicates a broken trust path, as told here: > http://wiki.apache.org/spamassassin/TrustPath > > But why is my trust broken? My local.cf contains the lines: > > clear_internal_networks > clear_trusted_networks > internal_networks x.x.x.x > trusted_networks x.x.x.x >
I know the docs claim you can do just an IP as a trusted_networks declaration, but I've had problems with SA misbehaving when you use that format. Try adding a /32 netmask on the end and see if that clears it up. It's a long shot, but worth a quick try. > Where x.x.x.x is the address of my mail server running SA. All other mail > (basically all mail period) should be external, untrusted. So how can spam > be hitting the ALL_TRUSTED rule? Based on past posts I read you are using SA 3.0.4. Versions older than 3.0.5 can also have this problem if there's an unparaseable Received: header. Since the header is unparsable, it doesn't count as either trusted or untrusted, which is a problem. This is fixed in SA 3.0.5 by backporting the 3.1.0 trust path code that adds an unparsable counter to the equation.
