Sergio Durigan Junior wrote: > On Monday, November 11 2013, I wrote: > >> Hi there, > > Hi, again! > > I am sorry to ressurect this thread, but after some time, investigation > and fixes, I would like to share what I did and ask for more opinions. > > First, I have fixed the previous warnings that I was seeing on the > messages. URI_BLOCKED was easily fixed by setting up my own named > (which, I confess, I should have done right after installing my server, > but I was unfortunately postponing it...). UNPARSABLE_RELAY was > happening because I modify the headers of every message sent through my > server in order to anonymize the sender's IP address;
I'm not quite sure I understand what you're trying to obscure, and chances are it's causing a lot of your trouble. Disable this for a while and see what happens. If you must do this, ensure it only happens on *outbound* email. Based on your two examples, you're applying this Received: munging to incoming mail as well, because otherwise you'd have a Received header added by your server showing the remote IP your server received the message from. As it stands, it looks to me as if pretty much all inbound mail will appear to be coming from 127.0.0.1, and so ALL_TRUSTED will fire for -1.8 points, and you won't get any hits on any IP address DNSBLs. Nor will a fairly extensive set of other rules give you any benefit; they have nothing to work with. Your second example likely would have been caught, or at least gotten a lot closer to 5 points, without the mangled Received: header(s). -kgd
