Comment RDNS Not Unreasonable (Score 1) 301
I run a small ISP and my email server is set to block illegitimate connections. Why should I allow an IP address with a PTR record of something like "generic_dumbass_user_IP123.233.domain.com" to freely connect to my email server and start spewing data? That's just stupid. Granted, a "fake" record can easily be created, but it is not unreasonable to setup or have your ISP setup a simple PTR record for your email server. It doesn't even have to match your domain's MX record. It just has to NOT be an obvious generic entry, or worse, no record at all. I understand the headaches when dealing with other email "admins" out there who may or may not know how to configure things, or may or may not care when you give them "friendly" advice on how things should be configured. Network admins are usually governed 90% by their ego, and nobody who is "king of his own little hill" appreciates being told by some stranger that his network is messed up. But there are "industry best practices" and RFCs to guide you. So IMHO, RDNS will not stop all SPAM, but it is simple enough to implement and does not create a lot of "false positives" when integrated with a comprehensive security profile.