This flies ok in reverse dns lookups, etc?
Reverse DNS basically looks up the PTR record for an IP address. Without dedicated IP's there may be confusion.
Only with broken software. :)
Virtual IPs for mailservers have been used for years (with no technical issues), and normally there is only 1 PTR record for a given IP. As a result, software shouldn't block E-mail on a multi-homed server.
For example, you'll define a mail host in each domain, then an MX record to point to that host. For example -- after all is said and done the MX records for both 'domain1.com' and 'domain2.com' may both resolve to 192.168.1.1. Yet a reverse lookup for that IP address returns the original PTR record, which may be 'imail.305spin.com'
That's not going to cause any problems.
For example, Declude JunkMail for years has had a test to check for the reverse DNS entry -- but it doesn't try to match [1] The reverse DNS entry with [2] the HELO/EHLO data with the [3] EDN (Envelope Domain Name -- the domain name of the sender) with any other hostnames/domain names.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection.
Find out what you have been missing: Ask for a free 30-day evaluation.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
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/
