How to set external Domain Name in outgoing Headers
Hi everyone, some external domains (comcast.net) refuse to accept mail from our Exchange 2003 server because the domain in some of the outgoing headers does not match the DNS lookup or MX record for our IP address. We were sending out our internal Active Directory domain name instead of our public domain name.
I changed the Fully Qualified Domain name under SMTP Vurtual Server properties, Delivery, Advanced to "mail.estarmail.com" from our internal Active Directory domain name. That seems to have corrected the domain name shown in the EHLO response shown in the Received from header.
It is still showing our internal Fully Qualified Domain name in the Message ID header however. Is there any way to override that as well?
Thank you.
Martin
All Replies
Hello Martin,
I think there isn't any way to change it. As per RFC 2822, after creation of Message-ID for a mail it should NOT be changed and it is a single unique message identifier so messages can be tracked. SMTP virtual server can not change the Message-ID but if it is not present then it creates new one.
Check Myth 3b in SMTP Virtual Server Myths Exposed
“- Message-Id is almost always generated by the store (Outlook or OWA) or client (Outlook Express), long before SMTP gets a chance to generate one. The only scenario where SMTP generates one is if a message somehow comes into Exchange without it. SMTP will not under any circumstance modify a message-id if the message already has one -- even an SMTP event sink cannot do this.”
Thanks Amit, I guess there is no way.
The problem we are haviung is that comcast.net refuses to accept email from our domain. They say they are doing forward and reverse DNS and MX lookups to validate the sender's domain. They claim that the domain in our outgoing headers does not match what they are looking up and that's why they will not accept our email.
Our domain name is www.estarmail.com registered at register.com and our IP is 70.91.104.193.
Is there anything that I am doing wrong in my Exchange settings that would cause this problem or is it just Comcast?
Here is a sample outgoing header that was accepted by Yahoo.
------------------------------------------------------------------------------------------------------------------------------------------------------------------
From Martin Kultermann Tue Jul 1 11:22:52 2008
Return-Path: <martinator@estarmail.com>
Authentication-Results: mta186.mail.re3.yahoo.com from=estarmail.com; domainkeys=neutral (no sig)
Received: from 70.91.104.193 (EHLO mail.estarmail.com) (70.91.104.193)
by mta186.mail.re3.yahoo.com with SMTP; Tue, 01 Jul 2008 11:22:36 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C8DBA7.7AFB6018"
Subject: test final
Content-class: urn:content-classes:message
Date: Tue, 1 Jul 2008 13:22:52 -0500
Message-ID: <F5ACB00A38B5064F90AF0F389224939652B3@aguirre.amazonia.com>
Thread-Topic: test final
Thread-Index: Acjbp3l/Q6p+ZgVFTR+mX/KkCXT1eQ==
From: "Martin Kultermann" <Martinator@estarmail.com>
To: <Martinator2000@yahoo.com>
Content-Length: 2683- Did you ever get a fix for this? We're having the same problem.
