Improve company productivity with a Business Account.Sign Up

x
?
Solved

#5.5.0 smtp;521-EHLO/HELO error when sending emails to Comcast.net or aol.com

Posted on 2006-06-29
6
Medium Priority
?
1,338 Views
Last Modified: 2010-03-06


Background info:  we have one server which has Windows Server 2003 SB...we are using Exchange internally only (for shared calendar, contacts). Our ISP is still hosting our email and I have set each user up in Outlook with their Exchange account as well as their POP3 email account.

So, in brief, the emails are coming and going thru the pop account, but are being stored in an exchange account (for backup reasons, and because some users roam to different computers).

Does anyone know why emails sent aol.com or comcast.net keep on kicking back the following email?:
There was a SMTP communication problem with the recipient's email server. Please contact your system administrator. <???.????.local #5.5.0 smtp;521-ECHO/HELO from sender ???????? does not map to ????.????.local in DNS>

I have read other posts, but I'm not sure they apply to me since we are not functionally using Exchange to send or receive emails.

Thanks,  Dave
0
Comment
Question by:bswensen
  • 2
4 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 17014079
Your server's SMTP banner says that it is servername.domain.local
You need to correct that.

ESM, Servers, <your server>, Protocols, SMTP. Right click on the default SMTP VS and choose Properties. Click on the tab Delivery and then Advanced. Change the entry in the FQDN to what the server is known as on the internet.
If the server doesn't have a DNS entry on the internet, then configure an SMTP Connector to route email through your ISP. http://www.amset.info/exchange/smtp-connector.asp

Your emails may be coming in through the POP3 connection, but I would be surprised if they were going out through it.
Once you introduce an Exchange configuration to Outlook, it will try and use it for all email. If you are sending email to a mix of internal and external users then Outlook will send all email through Exchange.

Exchange is an email server - if you are on any kind of permanent internet connection then you will get a much better user experience using Exchange for what it is designed for.
Even if you aren't using Exchange for email, you should still configure it as if it is, as email will very often slip out through Exchange.

Simon.
0
 
LVL 9

Expert Comment

by:Exchgen
ID: 17014416
Aol sees the sender IP and rejects it if does not get a reverse pointer back.

Ensure that Email does not leave through exchange, do the needful as simon has suggested, rename the FQDN to match the sender IP and not the MX record.

Raghu
0
 

Author Comment

by:bswensen
ID: 17015281
Simon...my FQDN is servername.domain.local...as you said it would be.

You say change this to what the server is known as on the internet. Is this the FQDN of our email hostname...which is mail.domain.com?

Thanks, Dave
0
 
LVL 104

Accepted Solution

by:
Sembee earned 1000 total points
ID: 17016763
You will have an external IP address - every machine that is on the internet does. This could be a dedicated or a shared IP address.
Either way, it needs to have a host name attached to it. That could be mail.domain.com - it may not. If you are getting your email from an ISP then it may not be mail.domain.com
If you don't have a host name, then ask whoever looks after your domain name (this may be your ISP, or it could be a domain name registrar) to create one for you, pointing at your external IP address. You could use office.domain.com, owa.domain.com etc.
Once you have that host created, enter that information in to the FQDN box.

Simon.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Are you in the migration process of your Exchange to Exchange Online? Be aware of customized solutions developed on the transport role on your old Exchange server. They might not be convertible to Exchange Online!
This article explains how to move an Exchange 2013/2016 mailbox database and logs to a different drive.
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

606 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question