At 1/5/2006 01:36 PM, you wrote:
the MX domain name's A record doesn't have a matching PTR domain name.
Right... My virtually hosted websites don't, either; it's the
nature of virtually hosting. Are you saying you have an IP address
bound for every domain you host email for?
no
So how can you have a PTR record that matches every A record that
points to it? In our environment, we have customer1.com MX
mail.customer1.com & mail.customer1.com A 64.30.43.3. Then,
customer2.com MX mail.customer2.com & mail.customer2.com A
64.30.43.3. Thus, our mailserver's IP address is resolved to by any
of our hosted domains. It sounds like what you're proposing is that
I have that PTR record point back to (match) each customers' domain.
They must have seen infected machines sending all kinds of random
crap in the helo hostname. I often see them sending <my mx ip> as
their HELO name, a very common tactic which never legal and a very
effective filter.
I guess my issue with this or any other *definitive* mark of spam is
that there are always exceptions to the rule. You just can't account
for all the possibilities, and when mail admins completely trust any
given test, innocent people get hurt. It's way better to assign a
weight to a test and make a decision based on the aggregate score of
a given email.
or other domain, that's not really helpful or necessary.
I agree - it sounds like a perfect item for a 'customize config' option.
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
