Micke Andersson wrote:
excuse me for my ignorance, but is this really the correct approach
right now, since it is quite a lot of badly configured DNS servers out
there. Should this not be handled by the SMTP server as is instead!
And return an error code of 421 or something like this. Like AOL has
implemented at their servers, you will be informed as sender about the
problem, with an URL link to
http://postmaster.info.aol.com/errors/421dnsnr.html
Whatever opinions you may have about AOL, when they began rejecting mail
without reverse-DNS entries a few years' back, AOL's sheer size forced
mail admins to make sure that their servers have both forward and reverse
lookups enable. Heck, even random cable/DSL hosts usually have reverse
lookups configured, usually something like 123-123-123-123.someisp.com.
Most of the mail I see coming from servers without reverse-resolution is
spam, usually from hosts in places like China.
Moreover, I'd much rather give such messages a relatively high SA score
than reject them at the SMTP level. False positives in the SMTP exchange
cause ill-will with clients and their correspondents.
Or if one should have this above Rule, me my self would not for the time
being, have that high of a score,
I give these messages a score of 3.3 with an SA criterion of 4.0; I get
very few false positives.
Peter
