What version of Surgemail are you running?  And on what platform? That might be useful info.

For all domains hosted here, outgoing email for them is sent from mail3.lcrcomputer.net(and I have well over 100 domains here).    I am running mirrored servers here with this set:

g_received_name "mail3.lcrcomputer.net"

The host names are mail3a.lcrcomputer.net and mail3b.lcrcomputer.net and are behind a nat box.  However the all banners are tagged mail3.lcrcomputer.net because of the above setting.  The forward on the public IP address for this is mail3.lcrcomputer.net on ip address 209.172.152.5 and the reverse points back to mail3.lcrcomputer.net.

What you are calling the telnet header is properly called the banner.  The FQDN announced does not have to relate directly to the domain in the From address field.  However the ip address reverse lookup needs to match the FQDN and the FQDN needs to have an A record that matches the IP address connecting to the other mail server and the FQDN needs to match the name announced in the banner.

Again, the banner or FQDN does not have to relate directly to the domain in the From field in the email.  However SPF records for the domain should list the IP address or FQDN of the sending mail server which should match the name announced in the banner.

Lyle Giese
LCR Computer Services, Inc.

Admin wrote:

Hi Stephen,

Yes, both domains have proper PTR records, reverse DNS and SPF entries. Many universities, particularly in Europe, are checking that the telnet header matches the FQDN and rejecting if it does not.

I seem to remember that in earlier versions of Surgemail that there was a config setting that would allow admins to pre-set the webmail log-in domain. Is that still a possibility? Any other ideas?

Thanks,

Jamus

On 2011/01/19, at 22:29, Stephen D. Goff wrote:

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