Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

454 5.7.1 Error - Outbound emails getting bounced

Posted on 2014-03-31
5
Medium Priority
?
1,167 Views
Last Modified: 2014-04-11
Error message:
454 5.7.1 DXNS3 1.2.3.4: Message refused. Your host name dosen't match with your IP address: EX1SERVER.domain.local If you need, please contact stamp@daumcorp.com.

We have been getting mail bounced back from a lot of outside mail servers. To fix it, I have removed the SPF record but don't think that is the issue.

We asked our ISP to change the PTR record for 1.2.3.4 to reflect as mail.domain.com.


Question:
Why do outside servers see us as EX1SERVER.domain.local if we have changed the PTR to show as the mail.domain.com address?


I looked here but didn't have direct info regarding my issue:
http://www.experts-exchange.com/Networking/Misc/Q_25518074.html
0
Comment
Question by:Paul Wagner
5 Comments
 
LVL 25

Expert Comment

by:Tony Giangreco
ID: 39968331
This normally means you have to check the "My outgoing server requires authentication" box on the Outgoing Server tab of the "More settings" dialog of your account.

Since this is from the Exchange server, you probably need to adjust the authentication level and may need to use a secure port.
0
 

Expert Comment

by:leHazard
ID: 39968340
Another possibility to try is to look at the client configuration. If the client is authenticating to EX1SERVER.domain.local (as the server name) then this will be attached to each message. If the message says it was sent through  EX1SERVER.domain.local but the DNS says it came from mail.domain.com, the client configuration should be causing the problem. Assuming you allow outside authentication, I would change the client to authenticate to the external name, which might solve the issue as well.

If these are server errors, this should solve the issue. If the errors are in the email client than the other suggestion should work well.
0
 
LVL 5

Author Comment

by:Paul Wagner
ID: 39968352
Are you sure that's all it is? We currently have authentication required for our server.

I was looking at this field in the Send and Receive connectors:
Specify the FQDN this connector will provide in response to HELO or EHLO

Should I have that listed as mail.domain.com? It's currently listed as EX1SERVER.domain.local
0
 
LVL 76

Accepted Solution

by:
Alan Hardisty earned 2000 total points
ID: 39968569
Your SEND connector FQDN should be mail.domain.com as that is what is used to verify you are who you say you are.

When a server receives email, they check your FQDN, confirm that it resolves to the IP Address you are sending from and then reverse check by making sure that the IP address you send from resolves in DNS to the FQDN and if it matches, it continues to listen to your server sending the email, otherwise it can reject your communication for being improperly configured which looks like what is happening here.

Are you sending out from the same IP Address that you receive emails on?

Alan
0
 
LVL 5

Author Closing Comment

by:Paul Wagner
ID: 39994564
Changing send connector to reflect mail.domain.com cleared the issue right up!

Sorry it took so long to get back to you guys. I wanted to test long enough to make sure the problem truly went away.

Yes, the outbound is the same as inbound.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Exchange administrators are always vigilant about Exchange crashes and disasters that are possible any time. It is quite essential to identify the symptoms of a possible Exchange issue and be prepared with a proper recovery plan. There are multiple…
Among the most obnoxious of Exchange errors is error 1216 – Attached Database Mismatch error of the Jet Database Engine. When faced with this error, users may have to suffer from mailbox inaccessibility and in worst situations, permanent data loss.
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
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 anti-spam), the admin…
Suggested Courses

581 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