cgizzi
asked on
5.7.1 Error on SMTP messages
I'm getting some messages bounced back from a few recipients. Here is what the receipt says:
There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.
<mail.company-name.com #5.5.0 smtp;553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)>
I recently added a PTR record to my mail server because email to AOL and Optimum Online were being delayed and bounced.
When I go to DNS reports, everything passes but i get a warning that I think might be related to this issue. It reads:
WARNING: One or more of your mail servers 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). This probably won't cause any harm, but is 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.
mail.company-name.com claims to be invalid hostname '************************* ********** ********** ********** ********** **
220 ************************** ********** ********** ********** *******
Here is the background information:
I'm running MS Exchange Server 2003 which is also the domain controller running AD.
The external domain is: company-name.com but the internal domain name is: company-name-location.com
The internal name of the server is: apollo.company-name-locati on.com
The MX record points to an external IP address as mail.company-name.com
My SMTP virtual server has the masquerade domain and the FQDN as mail.company-name.com
Any help or assistance is greatly appreciated in advance.
There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.
<mail.company-name.com #5.5.0 smtp;553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)>
I recently added a PTR record to my mail server because email to AOL and Optimum Online were being delayed and bounced.
When I go to DNS reports, everything passes but i get a warning that I think might be related to this issue. It reads:
WARNING: One or more of your mail servers 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). This probably won't cause any harm, but is 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.
mail.company-name.com claims to be invalid hostname '*************************
220 **************************
Here is the background information:
I'm running MS Exchange Server 2003 which is also the domain controller running AD.
The external domain is: company-name.com but the internal domain name is: company-name-location.com
The internal name of the server is: apollo.company-name-locati
The MX record points to an external IP address as mail.company-name.com
My SMTP virtual server has the masquerade domain and the FQDN as mail.company-name.com
Any help or assistance is greatly appreciated in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The
************************** ********** ********** ********** ********** *
220 ************************** ********** ********** ********** *******
Is classic PIX with fixup SMTP.
If you have a PIX with version 7.0 of the software it might be called something else. I haven't seen a 7.0 PIX yet so cannot be sure what they changed.
Simon.
**************************
220 **************************
Is classic PIX with fixup SMTP.
If you have a PIX with version 7.0 of the software it might be called something else. I haven't seen a 7.0 PIX yet so cannot be sure what they changed.
Simon.
ASKER
but I did turn off esmtp inspection just in case they are the same thing.
And on the second suggestion, the DNS lookup works... and I know that its set to the right value of mail.company-name.com
Hopefully, your first suggestion works.