Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Unexpected SMTP server response. Expected: 220, actual: 500

Posted on 2013-07-01
5
Medium Priority
?
2,789 Views
Last Modified: 2013-07-22
Exchange 2012 version 15.0 on server 2012

Getting the following error message when i run the Remote connectivity Analyzer.  I have made adjustments to the auth mechanisms but have not been able to resolve the issue.

Also, every once in a while, I get the 451 local error.  I immediately rerun the test and everything works.  I mention this because there are times that email gets rejected with "#5.4.4 smtp;554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain".  It is unpattered and happens a few times during the day.



Testing inbound SMTP mail flow for domain ME@Mycomp.com
 Inbound SMTP mail flow was verified successfully.
 
Test Steps
 
Attempting to retrieve DNS MX records for domain Mycomp.com.
 One or more MX records were successfully retrieved from DNS.
 
Additional Details
 MX Records Host server.mycomp.com, Preference 10



Testing Mail Exchanger server.mycomp.com.
 This Mail Exchanger was tested successfully.
 
Test Steps
 
Attempting to resolve the host name server.mycomp.com in DNS.
 The host name resolved successfully.
 
Additional Details
 IP addresses returned: XX.XX.XX.XX


Testing TCP port 25 on host server.mycomp.com to ensure it's listening and open.
 The port was opened successfully.
 
Additional Details
 Banner received: 220 server.mycomp.com Microsoft ESMTP MAIL Service ready at Mon, 1 Jul 2013 12:50:25 -0500


Analyzing SMTP Capabilities for server server.mycomp.com:25
 The test passed with some warnings encountered. Please expand the additional details.
 
Additional Details
 Unabled to determine SMTP capabilities. Reason: Unexpected SMTP server response. Expected: 220, actual: 500, whole response: 500 5.3.3 Unrecognized command




Attempting to send a test email message to me@mycomp.com using MX server.mycomp.com.
 The test email message was delivered successfully.

Testing the MX server.mycomp.com for open relay by trying to relay to user Admin@TestExchangeConnectivity.com.
 The Open Relay test passed. This MX isn't an open relay.
 
Additional Details
 The open relay test message delivery failed, which is a good thing.
The exception detail:
Exception details:
Message: Mailbox unavailable. The server response was: 5.7.1 Unable to relay
Type: System.Net.Mail.SmtpFailedRecipientException
Stack trace:
at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender, MailAddressCollection recipients, String deliveryNotify, Boolean allowUnicode, SmtpFailedRecipientException& exception)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at Microsoft.Exchange.Tools.ExRca.Tests.SmtpOpenRelayTest.PerformTestReally()

Thanks a bunch in advance
0
Comment
Question by:theDRM
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
5 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39290941
What is between Exchange and the internet? A firewall of some description?

Simon.
0
 

Author Comment

by:theDRM
ID: 39290953
There is a Sonicwall Firewall.  Port 25 has been opened and a NAT policy created to forward all traffice to the server.
0
 

Accepted Solution

by:
theDRM earned 0 total points
ID: 39333559
The receive connectors are configured correctly.  This is exchange 2013, so that article doesn't help whatsoever.

However, I have learned that Exchange 2013 doesn't like any connectors configured other than the default.  It also requires that you leave ALL default connectors in place.  

This error went away when I removed receive connectors that were not default.  I had intentionally created a connector that I know works on exchange 2010 and it caused email to stop sporadically and the above error message to happen sporadically.  Upon removal, all is well.

I have not been given a reason for the glitch or a workaround by Microsoft to create alternative connectors in exchange 2013 other than the default.
0
 

Author Closing Comment

by:theDRM
ID: 39345442
Worked with Microsoft and this is the only way we have been able to solve the issue thus far.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

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

Are you an Exchange administrator employed with an organization? And, have you encountered a corrupt Exchange database due to which you are not able to open its EDB file. This article will explain all the steps to repair corrupt Exchange database.
With so many activities to perform, Exchange administrators are always busy in organizations. If everything, including Exchange Servers, Outlook clients, and Office 365 accounts work without any issues, they can sit and relax. But unfortunately, it…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
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…

618 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