"David F. Skoll" <d...@roaringpenguin.com> wrote:
The battle raged for a while, but eventually we were delisted. (We block mail from <> to postmas...@roaringpenguin.com because we never, ever send mail from postmas...@roaringpenguin.com)
We do the same for postmas...@columbia.edu for the same reason, and I don't think we got listed. Back to go: $ host 140.211.11.3 3.11.211.140.in-addr.arpa domain name pointer hermes.apache.org. $ host hermes.apache.org hermes.apache.org has address 140.211.11.3 Nothing wrong there. The host says helo mail.apache.org and... $ host mail.apache.org mail.apache.org has address 140.211.11.3 If you're going to verify HELO, you need to look up the name given in the HELO. Whether the cost of a lookup is worth the benefit is a bit questionable. We score for impossible HELO names, like name with no dot. Those are usually home Windows boxes, but look out, they can also be hosts at small organizations with overworked or newbie system admins. I would not block outright for that. As David said, lots of fps await. Joseph Brennan Lead Email Systems Engineer Columbia University Information Technology
