Mail server host name in greeting
good day to everyone, I have setup our Exchange Server 2003 in a Windows Server 2003, but using www.dnsreport.com, DNS diagnostic site, it is reporting a warning error of,
Mail server host name in greeting
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.domain.com claims to be invalid hostname '***********************************************************0****0****0':
220 ***********************************************************0****0****0 **********************200**20********0*00any idea on how to resolve this one. I have both A and MX records for this domain, it's functions as web and at the same time as a mail exchange server. Thanks
All Replies
In your SMTP server properties, go to the delivery tab and click on the Advanced button. Change the FQDN (middle box) to the external name that you're doing the lookup against. It also looks like your firewall is masking the header. I tend to turn this off since it seemed to create problems for me sending to AOL and Cox.
bugoy wrote: good day to everyone, I have setup our Exchange Server 2003 in a Windows Server 2003, but using www.dnsreport.com, DNS diagnostic site, it is reporting a warning error of,
Mail server host name in greeting
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.domain.com claims to be invalid hostname '***********************************************************0****0****0':
220 ***********************************************************0****0****0 **********************200**20********0*00any idea on how to resolve this one. I have both A and MX records for this domain, it's functions as web and at the same time as a mail exchange server. Thanks
bugoy wrote: warning error of
Mail server host name in greeting
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.domain.com claims to be invalid hostname '***********************************************************0****0****0':
220 ***********************************************************0****0****0 **********************200**20********0*00any idea on how to resolve this one. I have both A and MX records for this domain, it's functions as web and at the same time as a mail exchange server. Thanks
Well several things.
1. This is a warning, not an error. Warnings are not necissarily problems.
2. The host name your server advertises in the banner has nothing to do with Exchange. That is a PIX with the SMTP fixup protocol running. That protocol pretty much sucks, so if it were m server I'd disable it. Not to solve the warning from dnsreports, but just because it sucks generally. But YMMV.
3. No one is going to reject mail they are sending to you as spam based on what your host name reports, so this 'test' is misleading at best and assumes what you advertise on receive is what you advertise on send (or that receive and send is even done by the same server... it's a poorly designed and implemented test).
4. Since you've excluded the domain from your post, I'll assume your A and Mx records are correct and correctly configured. Someone else pointed out how you can change the name given in helo conversations, but that won't effect what your PIX advertises.Hi bugoy,
This post was very helpfull. I had the same problem for a while and was pulling out what little hair I had trying to figure out the solution. My problem turned out to be the PIX SMTP fixup command like you mentioned above. Removing the fixup command solved the problem for me. So thank you VERY MUCH for the post....
Calvin
- OOPS!... Sorry Chris... Meant to give you the credit for the post.... Anyways... Thanks again.
Hi everyone, H
How can I change the mailserver greeting name in Exchange Server 2007?
When i try to change appear the following message:
--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
The following error(s) occurred while saving changes:set-receiveconnector
Failed
Error:
When the AuthMechanism parameter on a Receive connector is set to the value ExchangeServer, you must set the FQDN parameter on the Receive connector to one of the following values: the FQDN of the transport server "servername.domainname", the NetBIOS name of the transport server "SERVERNAME", or $null.Thanks in advance,
Cleber
Hi everyone,
I have this problem too.
My office had mail front-end (DMZ-Exchange 2003) and backend (Exchange 2003). When I sent the mail from front-end to someone in company group (outside Thailand), the mail will pass by VPN Link but I sent the mail to another ex. Hotmail, Yahoo etc. mail will pass by normal network link. So mail in company group will responds as 220 SV-DMZ-Sever.domainname.com and the other mail will responds as mail.domainname.co.th (check reverse DNS). Could you help me to solve this warning?
- Dear Cleber,
Start Exchange Management Console
Organization Configuration > Hub Transport
Send Connectors tab
Choose 'To internet' from the list
General tab
At the bottom you can specify the FQDN.
Yours,
Balázs HORVÁTH
WiseGroup Informatics Ltd.
http://wgi.hu
