Steven Dickenson wrote:
On Oct 31, 2006, at 6:09 AM, John Rudd wrote:
I've considered the exact opposite (adding static to the check for
keywords). My rules are really looking more for "is this a _client_
host", not "is this a dynamic host". That one check looks for
"dynamic", but I'm not interested in exempting anyone because they're
"static". They've still got a hostname that looks like an end-client,
and an end-client shouldn't be connecting to other people's mail
servers. Any end-client that connects to someone else's email server
should be treated like it's a spam/virus zombie
I can't agree with this. Many small businesses in the US get just these
kind of static connections from broadband ISPs. Comcast, for example,
has all of their static customers using rDNS that would fail your tests,
and they refuse to set up a custom PTR record or delegate the record to
someone else. Most of these static customers are legitimate business
networks running their own mail server, and have neither the need nor
desire to relay their mail through Comcast's SMTP servers. I think your
general idea is very good, but you're reaching a little too far with
this one.
I think based on all of the feedback I'm getting on this, I'm going to
have a config option for something like
"relaychecker_skip_statichostname=1" with 1 being the default. It will
cause both the "IP in hostname" and "dynamic hostname" checks to be
skipped if "\bstatic\b" is in the hostname. I may also have a
"relaychecker_skip_iphostname" and "relaychecker_skip_dynamichostname",
which default to 0 ... to allow places like Italian sites to skip those
entirely if they just want the basic DNS checks.
It may be a couple days before I can make the changes I've put
forward... we're having a problem at work (not related to this; it's at
the network level), and I wont be able to put much coding/testing time
into this until that problem gets handled.
John
