Exchange 2013 SMTP inbound is taking up to several hours to receive emails. Is there a way to optimize the speed of incoming mail?


Ive put an Exchange 2013 intallation in 3 weeks ago. The setup is all on one server which shares AD and DNS. There is a split domain scenario with .local and .com in the internal DNS. Messages tend to send out instantly but outside mail takes awhile. We had to move the zone file to go daddy a week ago ant the problems have increased. The MX record is set to * and associated to the WAN ip of the server. Is there anyway to test for incorrectness or optimize the server for quicker reception of mail? I tried adding an SPR record. Also we are getting tons of spam now. Is the internal filter in Exchange sufficient. Any help would be a life saver.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Zephyr ICTCloud ArchitectCommented:
For starters I'd run the checks using and check DNS setup of your domain with Post any issues detected (sanitize the domain name if needed).

This will give us some ideas on where to help out.
JRome225Author Commented:
I ran the exchange analyzer and it was all checks. Mxtoobox generated a delay error. I rebooted the server and now am getting Attempting to send a test email message to using MX
  Delivery of the test email message failed.
 Additional Details
The server returned status code 451 - Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX2
Exception details:
Message: Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later. PRX2
Type: System.Net.Mail.SmtpException
Stack trace:
 at System.Net.Mail.DataStopCommand.CheckResponse(SmtpStatusCode statusCode, String serverResponse)
 at System.Net.Mail.DataStopCommand.Send(SmtpConnection conn)
 at System.Net.Mail.SmtpClient.Send(MailMessage message)
 at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally()

Elapsed Time: 605 ms.
Zephyr ICTCloud ArchitectCommented:
So is your domain name right? DNS wise it's looking ok, spf missing and reverse DNS mismatch, nothing major.

Can you run this command on your mail server:

get-ReceiveConnector | select name,tarpitinterval
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Simon Butler (Sembee)ConsultantCommented:
Unless you have changed the tarpit interval the default is usually fine.
What else is on the server, as my instinct is this is outside of Exchange. If you have antivirus on the server, does it have the correct exclusions for Exchange configured within?

JRome225Author Commented:
No AV, just AD and DNS. I removed an offline backup from the server prior to this error but can't identify it as the prime reason for the fail as the mail has been ultra slow and I got a similar error to this from sending on an outside email domain.
Zephyr ICTCloud ArchitectCommented:
How is the network configured on this host? Gateway correct? Internal DNS server(s)? ... Routing ok?
We'll need more info to pinpoint the possible issue.
Zephyr ICTCloud ArchitectCommented:
I've run another test on your domain using , nothing reported as being wrong or not working... So if tarpitting isn't set too high, it might be something else... But as I said. we'll need more info.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JRome225Author Commented:
Well I set the tarpitting to 0 and the time went down significantly on the analyzer. Still Im going to monitor it this evening as Im not 100% confident that it fixed the issue.
Simon Butler (Sembee)ConsultantCommented:
Do you have something between Exchange and the internet?
I have never had to change tarpit time, so if you have seen a change by doing so that would suggest something is interfering. Tarpit shouldn't affect the day to day operation of email delivery.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

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.