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.
I disagree on your disagreement. This is my opinion: If you don't have
control over your rDNS, do NOT run any mail server, unless you relay all
outbound mail through a server at your ISP.
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.
'No need nor desire', that's not really any good excuse. Use a relay or
find your mail rejected, I'd say.
--
Andreas
