<That's not a problem. No decent mailserver or anti-spam program will complain if the EHLO/HELO does not match the PTR.>
But some are starting to do just that (supanet.com).
That's their choice. You should set up your MTA and DNS on the supposition that more MXs will demand the same. If you can't, you will have more problems delivering your mail, and you will waste a lot time trying to get such MXs to except your MTA from their credentials, thereby wasting their time, and the time of your mail users and their correspondents.
what if this practice become more widely used ?
It would be an excellent idea that I strongly endorse.
Shouldn't IPSWITCH add an option to let us define what ehlo should be used with VD?
The MTA is a real machine and should only worry about its real, canonical, (non-virtual) credentials AS A MACHINE.
As I showed last week, the most impeccable credentials for an MTA are:
In DNS, the MTA with an IP of A.B.C.D as these records:
C.D.B.A.in-addr.arpa. PTR label.domain.com.
label.domain.com. A A.B.C.D
In SMTP:
220 label.domain.com ESMTP is my SMTP greeting
EHLO label.domain.com
... is how I say hello. As you can see, these credentials would get past supanet's MX.
If your MTA software, or lack of control of your DNS records, or your own MTA/DNS design decisions prevents you from meeting those credentials, you should work to correct the deficiencies and aim (and hit) higher in meeting the best practices.
The question about Imail is that, in supporting different domains on the canonical IP and domains on their own IP aliases, can Imail (or registry hacking) meet the above credentials?
Len
_____________________________________________________________________ http://MenAndMice.com/DNS-training: Wash DC; Dallas; Atlanta IMGate.MEIway.com: anti-spam gateway, effective on 1000's of sites, free
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/
