I run many virtuals and have never experienced this issue you are describing. Does your FQDN.org have a proper reverse entry in DNS (you didn’t provide the real name, so I couldn’t check it myself)? And do you have a proper SPF entry for both your domains that include the FQDN.org?

 

 

From: Admin [mailtoHIDDEN@iodp-mi-sapporo.org] 
Sent: Wednesday, January 19, 2011 12:59 AM
To: surgemailHIDDEN@etwinsite.com
Subject: [SurgeMail List] telnet header domain, surgeweb domain and surgemail.ini configuration

 

Hello,

I have mirrored mail servers hosting 2 domains. I am having trouble with mail rejections from many recipients based on the telnet header not matching the FQDN for the mail servers. When I change the surgemail.ini file so that the vdomain name matches the FQDN for the server, the FQDN becomes the domain listed for Surgeweb login and users cannot login to Surgeweb.

My surgemail.ini has the following lines:
vdomain address="1xx.xxx.xxx.xx1" name="MXdomain.org"  ---This works for Surgeweb but the Telnet banner is the MXdomain.org and the mail servers reject our mail.

My surgemail.ini has the following lines:
vdomain address="1xx.xxx.xxx.xx1" name="FQDN.org"  ---This makes the Telnet banner match the FQDN, but users cannot log into Surgeweb because their login becomes