It sems to me that it we had a way to do a different dsn test like,
ReverseDNS 10 Contains client.comcast.net
You can use:
REVDNS 10 CONTAINS client.comcast.net
However:
As these client machines should not be connecting to our server anyways.
Be very, very careful in making such assumptions. One person last year decided that any connections with reverse DNS entries that appeared as though they might be from dynamic IPs should not be allowed. While that sounds reasonable, many static IPs have reverse DNS entries that look like dynamic IPs (we found that the guy who tried that would have blocked at least 10% to 15% of legitimate mail).
So if all reverse DNS entries with client.comcast.net are dynamic/residential IPs, you're safe doing that (but could use one of the DYNA/DUL tests instead, which should catch them). But if there are static IPs with reverse DNS that contains client.comcast.net, you could block legitimate E-mail.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000.
Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection.
Find out what you've been missing: Ask for a free 30-day evaluation.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
--- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
