Sircorp
asked on
Exchange problem -- What did i miss? Smtp Subject: Undeliverable
The following is an email that was received by someone on our server.
From: System Administrator
Sent: Monday, May 01, 2006 10:54 AM
To: someone@comcast.net
Subject: Undeliverable: FW: Starting Salary
Your message did not reach some or all of the intended recipients.
Subject: FW: what up
Sent: 5/1/2006 10:54 AM
The following recipient(s) could not be reached:
someone@comcast.net on 5/1/2006 10:54 AM
There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.
<BCASERVER.bca.int #5.5.0 smtp;521-EHLO/HELO from sender (our ip addy) does not map to bcaserver.bca.int in DNS>
Now to give you the background on my situation.
The server is small business 2003.
When the server was installed it was set up in the domain of bca.int with a name of bcaserver .
Our domain for our email is with a different domain now. But the server's name and internal domain is still the same.
What do i need to do to correct the problem. We are getting a lot of bounced and delayed messages that we send out.
This is a major problem as the emails that are sent are VERY Time sensitive. Please Help. Thanks
From: System Administrator
Sent: Monday, May 01, 2006 10:54 AM
To: someone@comcast.net
Subject: Undeliverable: FW: Starting Salary
Your message did not reach some or all of the intended recipients.
Subject: FW: what up
Sent: 5/1/2006 10:54 AM
The following recipient(s) could not be reached:
someone@comcast.net on 5/1/2006 10:54 AM
There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.
<BCASERVER.bca.int #5.5.0 smtp;521-EHLO/HELO from sender (our ip addy) does not map to bcaserver.bca.int in DNS>
Now to give you the background on my situation.
The server is small business 2003.
When the server was installed it was set up in the domain of bca.int with a name of bcaserver .
Our domain for our email is with a different domain now. But the server's name and internal domain is still the same.
What do i need to do to correct the problem. We are getting a lot of bounced and delayed messages that we send out.
This is a major problem as the emails that are sent are VERY Time sensitive. Please Help. Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
the mx and the a records are pointing to the correct ip address.
The dns report has a yellow flag for "Mail server host name in greeting" with this message
WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.
mail.brownchambless.com claims to be non-existent host BCASERVER.bca.int:
220 BCASERVER.bca.int Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Tue, 2 May 2006 07:53:51 -0500
So how do i correct it?
The dns report has a yellow flag for "Mail server host name in greeting" with this message
WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.
mail.brownchambless.com claims to be non-existent host BCASERVER.bca.int:
220 BCASERVER.bca.int Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Tue, 2 May 2006 07:53:51 -0500
So how do i correct it?
Look at the properties of your Default SMTP Virtual Server in ESM, and click the Delivery tab, then the Advanced button. If the Fully-qualified Domain Name field is empty, then it may help to put the name from your MX record in there, so that the rest of the world knows that it's the same server.
ASKER
Thanks for all your help it is corrected now
http://support.microsoft.com/default.aspx?scid=kb;en-us;300171