Share via


451 Temporary local problem - please try later: retry timeout exceeded

Question

Thursday, October 3, 2013 6:59 PM

Hi all!

Some of our users get this error Message: ** 451 Temporary local problem - please try later: retry timeout exceeded**

Have anyone seen this and does anyone have a solution for this?  The problem is that I can not find anything in the Queue Viewer.

The whole error Message is:

SMTP error from remote mail server after RCPT TO:<[email protected]m>:
    host post.domain.com [XX.XX.XX.XX]: 451 Temporary local problem -
please try later: retry timeout exceeded

The user is a member of our domain. Sometimes it is our Exchange server who reports it and sometimes it is external mail servers.

Pittbull

All replies (16)

Thursday, October 3, 2013 8:33 PM | 1 vote

It seems to be a DNS, IP blacklisting problem.

Hence first check your MTA IPs for blacklisting and whether your MTAs can properly resolve the DNS, if you are using any smarthost to send email to external provider then check connectivity between their system vice-versa.

Regards, Sourabh Kumar Jha | Please mark it as an answer if it solves your problem or vote as helpful if you like it. |


Friday, October 4, 2013 5:54 AM

Thank you for your input.  I will check that and come back to you.

Pittbull


Friday, October 4, 2013 6:29 AM

I have now checked for blacklisting for both my domain and the public ip of our mx-record. Everything is ok.

As far as I can see mail is being delivered and recieved. I also have used Microsoft Remote Connectivity Analyzer and ran all of the tests. No errors. I have also used the Best Practices Analyzer and executed all the tests there and it could not find anything.

Still my users are getting the error.

Pittbull


Friday, October 4, 2013 2:47 PM

Please track the email and see if there is any more information could be found ?

Enable Debug logging and SMTP protocol logging then see for the logs ?

Regards, Sourabh Kumar Jha | Please mark it as an answer if it solves your problem or vote as helpful if you like it. |


Friday, October 4, 2013 5:14 PM

sounds like server you are sending to is temporally down.

do a telnet session from your exchange server

find mx record for domain www.mxtoolbox.com can do this quickly

telnet <mx record> 25

if this "times out" either they are blocking you or they are down, if you can try from and another ip address see if the same things happens.


Monday, October 7, 2013 7:00 AM

Hi

The SMTP protocol logging folders "SmtpRecieve" and "SmtpSend" are both empty even though the "Enable connectivity log" is enabled.

The "Message tracking log" is enabled and the "MessageTracking" folder is populated with log files. I have read the latest log file and everything seems to be ok.

We are using a Sophos Spamwasher as a smarthost. Can it be this one that arcausing this? I am not so familiar with this one since I have always used Barracudas.

Pittbull


Monday, October 7, 2013 7:03 AM

I will try this a litle bit later and give you the output.

Pittbull


Tuesday, October 8, 2013 6:08 AM

I have now used telnet on several domains and no one is blocking us.

This whole thing is bugging me.

I have also read logs today and I can not find anything wrong.  I am starting to believe that the error lays on our smarthost/spam washer.

Pittbull


Tuesday, October 8, 2013 12:07 PM

Dear Pitbull,

Anyhow this is related to Network / DNS where time-out is happening. If below two URL doesn't help then i think it is time to call MS support Team.

http://social.technet.microsoft.com/Forums/exchange/en-US/fc26dac5-d4e2-49da-903d-361ea8b85388/451-470-temporary-server-error-please-try-again-later-prx5?forum=exchangesvrgeneral

http://social.technet.microsoft.com/Forums/exchange/en-US/fc23776c-bae4-4ca9-ad6d-4f8df880f47c/451-470-temporary-server-error-please-try-again-later-prx2?forum=exchangesvrsecuremessaging

Regards, Sourabh Kumar Jha | Please mark it as an answer if it solves your problem or vote as helpful if you like it. |


Tuesday, October 8, 2013 12:47 PM

Hi Sourabh

We have one CAS/HUB server and two Mailbox servers. Should I do this on all of them or on just the CAS/HUB?

Pittbull


Tuesday, October 8, 2013 12:54 PM

I should have also mentioned that the two Mailbox servers are in a DAG. Does that have something to say with this problem?

Pittbull


Tuesday, October 8, 2013 1:03 PM

Please do it on only HUB Server, Also DAG will not affect the routing. Good Luck !!!

Regards, Sourabh Kumar Jha | Please mark it as an answer if it solves your problem or vote as helpful if you like it. |


Tuesday, October 8, 2013 1:08 PM

Hi!

I have now done it. I will wait until tomorrow and check if it worked.

Thanx for the hint.

Pittbull


Thursday, October 24, 2013 4:45 AM

Any update on this thread ?

Regards, Sourabh Kumar Jha | Please mark it as an answer if it solves your problem or vote as helpful if you like it. |


Monday, February 8, 2016 4:32 PM

Where can I find that MTA IPs for blacklisting?

Thanks


Wednesday, December 7, 2016 10:08 AM

Server error: '451 Temporary local problem - please try later' (2010 and similar Outlook versions)

This error can be easily resolved in most cases by simply following Step 5 below. Detailed step follows,

1. Go to Account settings

2. Select the email account that you face problem

3. Click on 'Repair' tab and verify all details (account settings) to be correct

4. Now, before clicking on Test Account Settings, Click on More settings on the bottom right

5. Click on Outgoing Server Tab, and check/ Tick My outgoing server (SMTP) requires authentication

  1. Click the radio button below (Use same settings as my incoming mail server) and Click OK

7. Now, Test your account settings, you must be successful, click next and finish.

8. Restart Outlook and press F9 (Send or receive).

Your problem will be resolved.

(If successful, please do message me)