Cannot receive mail on Exchange 2013 CAS: 451 4.7.0 Temporary server error. Please try again later. PRX4

Hi all,
I have just deployed Exchange 2013 on two CAS boxes and two MBX boxes as follows:
10.10.20.11
CAS01
10.10.20.12
CAS02
10.10.10.11
MBX01
10.10.10.12
MBX02
If I telnet to the internet facing IP on CAS01 and attempt to send an email internally (to a mailbox on MBX01) I get the following:
220 smtp.myrealdomain.com Microsoft ESMTP MAIL Service ready at Wed, 26 Mar 2014 01:14:24 +1000
EHLO test.com
250-smtp.myrealdomain.com Hello [10.10.20.11]
250-SIZE 36700160
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-AUTH
250-8BITMIME
250-BINARYMIME
250 CHUNKING
MAIL FROM:[email protected]
250 2.1.0 Sender OK
RCPT TO:[email protected]
250 2.1.5 Recipient OK
DATA
354 Start mail input; end with <CRLF>.<CRLF>
Subject:Test email 452
This is test email 452
451 4.7.0 Temporary server error. Please try again later. PRX4
Connectivity Log on CAS01:
2014-03-25T15:27:15.353Z,08D11605A575FAE1,SMTP,internalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=<no priority counts>
2014-03-25T15:27:15.353Z,08D11605A575FAE1,SMTP,internalproxy,>,"MBX02.myaddomain.com[10.10.10.12], MBX01.myaddomain.com[10.10.10.11]"
2014-03-25T15:27:15.353Z,08D11605A575FAE1,SMTP,internalproxy,>,Established connection to 10.10.10.12
2014-03-25T15:27:15.369Z,08D11605A575FAE1,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (Attempting next target)
2014-03-25T15:27:15.369Z,08D11605A575FAE2,SMTP,internalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=<no priority counts>
2014-03-25T15:27:15.369Z,08D11605A575FAE2,SMTP,internalproxy,>,Established connection to 10.10.10.11
2014-03-25T15:27:15.369Z,08D11605A575FAE2,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (Retry : EHLO Options do not match for proxy)
2014-03-25T15:28:10.328Z,08D11605A575FAFA,SMTP,internalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=<no priority counts>
2014-03-25T15:28:21.669Z,08D11605A575FAFA,SMTP,internalproxy,>,"MBX01.myaddomain.com[10.10.10.11], MBX02.myaddomain.com[10.10.10.12]"
2014-03-25T15:28:21.669Z,08D11605A575FAFA,SMTP,internalproxy,>,Established connection to 10.10.10.11
2014-03-25T15:28:21.669Z,08D11605A575FAFA,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (Attempting next target)
2014-03-25T15:28:21.669Z,08D11605A575FAFF,SMTP,internalproxy,+,Undefined 00000000-0000-0000-0000-000000000000;QueueLength=<no priority counts>
2014-03-25T15:28:21.669Z,08D11605A575FAFF,SMTP,internalproxy,>,Established connection to 10.10.10.12
2014-03-25T15:28:21.669Z,08D11605A575FAFF,SMTP,internalproxy,-,Messages: 0 Bytes: 0 (Retry : EHLO Options do not match for proxy)
SmtpSend Log on CAS01:
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,1,10.10.20.11:25495,10.10.10.12:25,+,,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,2,10.10.20.11:25495,10.10.10.12:25,<,220 ********************************************************************************************************************,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,3,10.10.20.11:25495,10.10.10.12:25,*,,Proxying inbound session with session id 08D11605A575FB5D
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,4,10.10.20.11:25495,10.10.10.12:25,>,EHLO CAS01.myaddomain.com,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,5,10.10.20.11:25495,10.10.10.12:25,<,250-MBX02.myaddomain.com Hello [10.10.20.11],
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,6,10.10.20.11:25495,10.10.10.12:25,<,250-SIZE,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,7,10.10.20.11:25495,10.10.10.12:25,<,250-PIPELINING,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,8,10.10.20.11:25495,10.10.10.12:25,<,250-DSN,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,9,10.10.20.11:25495,10.10.10.12:25,<,250-ENHANCEDSTATUSCODES,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,10,10.10.20.11:25495,10.10.10.12:25,<,250-XXXXXXXA,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,11,10.10.20.11:25495,10.10.10.12:25,<,250-XXXXXXXXXXXXXB,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,12,10.10.20.11:25495,10.10.10.12:25,<,250-AUTH NTLM,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,13,10.10.20.11:25495,10.10.10.12:25,<,250-XXXXXXXXXXXXXXXXXC,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,14,10.10.20.11:25495,10.10.10.12:25,<,250-8BITMIME,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,15,10.10.20.11:25495,10.10.10.12:25,<,250-BINARYMIME,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,16,10.10.20.11:25495,10.10.10.12:25,<,250-XXXXXXXD,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,17,10.10.20.11:25495,10.10.10.12:25,<,250-XXXXXXE,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,18,10.10.20.11:25495,10.10.10.12:25,<,250-XXXXF,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,19,10.10.20.11:25495,10.10.10.12:25,<,250 XXXXXXXXXXXXXG,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,20,10.10.20.11:25495,10.10.10.12:25,*,,"EHLO options between current server and proxy target do not match : Chunking, Xrdst. Critical non
matching options : Chunking, Xrdst. Failing over."
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,0,,10.10.10.11:25,*,,attempting to connect
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,21,10.10.20.11:25495,10.10.10.12:25,>,QUIT,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,1,10.10.20.11:25496,10.10.10.11:25,+,,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,22,10.10.20.11:25495,10.10.10.12:25,<,221 2.0.0 Service closing transmission channel,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB5E,23,10.10.20.11:25495,10.10.10.12:25,-,,Local
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,2,10.10.20.11:25496,10.10.10.11:25,<,220 ********************************************************************************************************************,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,3,10.10.20.11:25496,10.10.10.11:25,*,,Proxying inbound session with session id 08D11605A575FB5D
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,4,10.10.20.11:25496,10.10.10.11:25,>,EHLO CAS01.myaddomain.com,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,5,10.10.20.11:25496,10.10.10.11:25,<,250-MBX01.myaddomain.com Hello [10.10.20.11],
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,6,10.10.20.11:25496,10.10.10.11:25,<,250-SIZE,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,7,10.10.20.11:25496,10.10.10.11:25,<,250-PIPELINING,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,8,10.10.20.11:25496,10.10.10.11:25,<,250-DSN,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,9,10.10.20.11:25496,10.10.10.11:25,<,250-ENHANCEDSTATUSCODES,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,10,10.10.20.11:25496,10.10.10.11:25,<,250-XXXXXXXA,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,11,10.10.20.11:25496,10.10.10.11:25,<,250-XXXXXXXXXXXXXB,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,12,10.10.20.11:25496,10.10.10.11:25,<,250-AUTH NTLM,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,13,10.10.20.11:25496,10.10.10.11:25,<,250-XXXXXXXXXXXXXXXXXC,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,14,10.10.20.11:25496,10.10.10.11:25,<,250-8BITMIME,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,15,10.10.20.11:25496,10.10.10.11:25,<,250-BINARYMIME,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,16,10.10.20.11:25496,10.10.10.11:25,<,250-XXXXXXXD,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,17,10.10.20.11:25496,10.10.10.11:25,<,250-XXXXXXE,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,18,10.10.20.11:25496,10.10.10.11:25,<,250-XXXXF,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,19,10.10.20.11:25496,10.10.10.11:25,<,250 XXXXXXXXXXXXXG,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,20,10.10.20.11:25496,10.10.10.11:25,*,,"EHLO options between current server and proxy target do not match : Chunking, Xrdst. Critical non
matching options : Chunking, Xrdst. Failing over."
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,21,10.10.20.11:25496,10.10.10.11:25,>,QUIT,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,22,10.10.20.11:25496,10.10.10.11:25,<,221 2.0.0 Service closing transmission channel,
2014-03-25T15:32:34.158Z,Inbound Proxy Internal Send Connector,08D11605A575FB67,23,10.10.20.11:25496,10.10.10.11:25,-,,Local
Can anyone help? I'm at the end of my Googling!

The answer has been found. In our case, we had to disable the Mailguard feature of the Cisco ASA between the CAS subnet and the MBX subnet. Essentially it was stripping AUTH commands from the SMTP handshake which meant the servers could not authenticate
to each other and establish a secured connection.
I guess for future reference, if you're getting a PRX4 error code you should look at any device that could be inspecting SMTP between your CAS and MBX servers.
This Microsoft KB article has more information: http://support.microsoft.com/kb/320027

Similar Messages

451 4.7.0 temporary server error. please try again later. prx4

Hello,
in my environment i can send/receive mail.
When doing some checks i will end up with this error :
451 4.7.0 temporary server error. please try again later. prx4
I have tried the following without results :
Exchange 2013 SMTP error "451 4.7.0 Temporary server error. Please try again later. PRX3"
This error message seems to be caused by DNS issues in the Exchange 2013 set up. Exchange then rejects all emails like this. It is not quite clear what Microsoft means with this error code and the various PRX-numbers at the end - we've also seen PRX1, PRX3,
PRX7. There is no list and no documentation on them available.
From customer feedback we found these ways to solve the problem:
Disable all unused network cards.
Check all DNS server entries in the configuration of your network cards (check
all network adapters) and make sure not to reference server 127.0.0.1 as DNS server but to use the real IP address instead.
If you have more than one fixed IP address in the server add an entry for each IP address in the hosts file (C:\Windows\System32\drivers\etc\hosts) formatted like "192.168.1.1 SERVERNAME".
Important: Do load the latest Exchange 2013 updates, especially CU1 if you haven't done that already.
Please delete the receive connectors in Exchange and create one new receive connector. Use the "front end" instead of "hub transport" setting and vice versa.
What do do, to fix this issue?
Thx

Hello,
Please use dcdiag command to check if all DC run normally.
Please use repadmin /showrepl command to verify DC replication status.
Please check if there is any related error in application log.
Cara Chen
TechNet Community Support

HT1338 Guys I need some help with deleting junk mail/bulk mail...I keep getting this air message that says THE IMAP COMMAND "UID COPY" (TO DELETED MESSAGES) FAILED FOR THE MAILBOX "BULK MAIL" WITH SERVER ERROR: UID COPY SERVER ERROR- PLEASE TRY AGAIN LATE

I need help in deleting my junk mail/bulk mail...when I dump junk mail and bulk mail into the trash it not allowing me to delete all mail only some. HELP!!

What program are you using? And what version?

How come, when I add myYahoo! email account to MAIL, after verifying, I always get the "server unavailable. please try again later"

How come, when I add myYahoo! email account to MAIL, after verifying, I always get the "server unavailable. please try again later"

THANKS! this worked !!!
I hit "DELETE THIS ACCOUNT" on my iphone (this is the Yahoo I tried to set up by "picking" it from the list that the iphone5 gives you) and then confirmed to delete everything.
THEN: while in Mail (still in the Settings Section) I tapped on "ADD ACCOUNT..." but this time tapped on "OTHER" and manually put in my yahoo ID and password and I did not even have to go to the SMTP or IMAP incomming/outgoing stuff at all. But I checked it out under the "ADVANCE" tab and it was already correct for yahoo. (ALMOST SEEMED TOO EASY)
Went to my home screen and tapped on MAIL and my yahoo email loaded up just right!
Now, I have no idea if I have any other issues like if I delete mail on the iphone; does it delete properly on my ipad...etc..etc. but one problem at a time is getting fixed. THANKS!

TS3899 When trying to set up E-mail, keep getting a message "Yahoo! Server Unavailable" Please try again later. What can I do?

When trying to set up E-mail, keep getting message "Yahoo! Server Unavailable" Please try again later. What can I do?

http://ca.answers.yahoo.com/question/index?qid=20080509161003AAyvqpx
this worked for me with my .ca yahoo account

The Mrs. and I are receiving "The iTunes Store is unable to process purchases at this time. Please try again later." message whenever we try to update apps or purchase new apps. This is on two separate iPhone4's running 4.3.3

I haven't updated the iOS this week because I'm still working on resolving a separate issue, syncing playlists back to iTunes from the iPhone after a Snow Leopard restore.
FWIW-- The Mac Store on my MacBook also returns a similar error message when I try to update pixelmator and evernote. I get "The iTunes Store is unable to process purchases at this time. Credit card processing is temporarily unavailable. You may continue to browse the store. Please try to make your purchase later."
After that error in the Mac Store, I immediately get the following error message: "We Could Not Complete Your Request. There was an error in the App Store. Please try again later. (100)"

Try contacting iTunes via email to check if there is an issue with the account. go to apple.com/support/itunes
Click on iTunes Store account and billing and select inquiries. On the right side click on "email us".
Before doing that trying viewing your account information first. Open the iTunes on you mac, look at the menu and select store and select view my account. Try removing the card (this is only applicable if you don't have a pending charges with iTunes) and hit done. Sign out, quit iTunes and sign back in and try updating the apps again.

Exchange 2013 "451 4.7.0 Temporary server error. Please try again later. PRX5" Error

I know this error message is discussed on other topics on several different forums including TechNet but I ended up opening this as the suggestions that solved the problems with the previous threads dos not work on mine.
We have a ticketing software that runs on client computers which sends mails to local Exchange server for notifications using port 25.
Approximately 1 out of 5 mails end up getting the "451 4.7.0 Temporary server error. Please try again later. PRX5" error. I have confirmed this by running Wireshark on the clients, saw the exact error message. This has been replicated with
several client machines running Win7 & 8.
I have tried several solutions to this, one of them being this:
http://www.techieshelp.com/exchange-2013-451-4-7-0-temporary-server-error-please-try-again-later-prx5/
I still get the same error from time to time after doing this, so it is not the issue. All the records in local hosts file, receive connector is listening to port 25 on all IPv4 addresses.
The server has a single NIC and the DNS lookups are done through that single NIC, not through "All available adapters" as set by default on ECP.
Almost everyone seems to be convinced that this is related to DNS but looking at how fast I get the error message, it doesn't look like it's waiting for a timeout (maybe unrelated, just an observation). Do you think it is possible that the DNS servers themselves
are causing this issue?
Also, I see Event 5504 on the primary dns server almost all of them coming from the mail server, saying that the DNS query was invalid. It may be related.
Additional Notes:
- CU6 is applied but did not fix the issue.
- None of these have solved it for me: http://www.servolutions.com/support/articles/Temporaryservererror2013.htm
- Receive Connectors do listen to separate ports 25 & 2525 -> There is a single instance of both Transport Service and Edge Transport service respectively. Anonymous users are accepted in both Receive connectors.

Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
Niko Cheng
TechNet Community Support
Thank you Niko. I'm looking forward to your answer as I've gone through every post regarding this and none of them worked. I will let everyone know if I can find a solution to this.

Exchange 2013 in Mac Environment - iPhones recieves email, Mac Outlook does not, OWA Error: Your request cannot be completed right now. Please try again later.

We are having some problems in Exchange when customers send us emails with large attachments. It doesn't happen all the time which is weird.
The emails show up fine on iPhones although it is very slow to show the whole email and attachment.
In OWA it gives an error - Error: Your request cannot be completed right now. Please try again later.
The emails never make it to our computer email program, Mac Outlook 2011

Hi,
What’s your Exchange 2013 version?
According to your description, I understand that the message which is sent from external customers with large attachments can’t be opened in OWA and Outlook for Mac for Exchange users. Is it rights?
If that is the case, please confirm if the issue only happens with the large attachment messages. Please confirm if the message with no attachment sent from the same customer can be received and shown correctly in OWA.
Please recycle the application pools in IIS Manager to have a try. If it doesn’t work, please change the OWA to use Conversation view then check whether the issue persists.
Regards,
Winnie Liang
TechNet Community Support

Exchange Receive Connector Temporary Server Error. Please Try again later. PRX4

Hi ,
I installated Exchange server 2013 on Windows 2012 R2 Servers..
Topology ;
1 Active Directory Server : Windows 2012 r2 all updates installed.
1 Exchange 2013 Server : Windows 2012 r2 all updates installed.
I configured send Connector settings and I checked Receive connectors Default Frontend Exchange settings. Anonymous users is ok and don't have any problem.
When I send mail Exchange -> Internet mail goes. this is ok.
But when I send mail Internet -> Exchange I am getting this error ;
Message or connection acked with status Retry and response 451 4.4.0 Primary target IP address responded with: ""501 5.5.4 Required arguments not present."" Attempted failover to alternate host, but that did not succeed. Either there
are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was xxx.xxx.xxx.xxx:2525
telnet results are below ;
220 exchange.bulut.email Microsoft ESMTP MAIL Service ready at Tue, 30 Dec 2014
14:12:19 +0200
EHLO bulut.email 250-exchange.bulut.email Hello [xxxxxxxxxxxxxxxxx]
250-SIZE 37748736
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-X-ANONYMOUSTLS
250-AUTH NTLM
250-X-EXPS GSSAPI NTLM
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 XRDST
MAIL FROM:[email protected] 250 2.1.0 Sender OK
RCPT TO:[email protected] NOTIFY=success,failure 250 2.1.5 Recipient OK
DATA354 Start mail input; end with <CRLF>.<CRLF>
Subject: Test from Contosoa
This is a test message
451 4.7.0 Temporary server error. Please try again later. PRX4
QUIT 221 2.0.0 Service closing transmission channel
Thanks. Regards.

Hi,
If the CAS and MBX servers are collocated on the same server the SMTP Receive connection for the Transport service will listen on 2525 instead of 25. This is because two services (FET and Transport Service) can’t listen on the same port.
Refer from this article:
http://blogs.technet.com/b/rischwen/archive/2013/03/13/exchange-2013-mail-flow-demystified-hopefully.aspx
Please try to create an endpoint for 2525 on default receive connector to test mail flow by the following steps:
EAC -> mail flow -> receive connectors -> Default EXCHANGE
Click Edit then click scoping tab.
Under Network adapter bindings, click
add button to create port 2525 for all available Ipv4/Ipv6 addresses.
Best Regards.

Error in Edge server mail queue LED=451 4.7.0 Temporary server error. Please try again later. PRX6

We have two Edge servers deployed at our Central location where it accepts mails from all other site and send it to Internet and vice versa. There is no problem for outgoing mails but while receiving the mails from the internet there is always an average
queue of 600 to 700 mails (some time goes up to 2000). After analysing the issue we found the below errors..
LED=451 4.7.0 Temporary server error. Please try again later. PRX6
451 4.4.0 SMTPSEND.SuspiciousRemoteServerError; remote server disconnected abruptly; retry will be delayed
421 4.4.2 Connection dropped due to TimedOut
We have then picked random 10/12 recipients from the error queue and found all of ‘em were
from a specific site.
we have tried the below solution... after searching for resolution on the Internet
Tried enabling protocol logging but nothing found
Since it was more likely to be a DNS issue, tried manually adding DNS server IPs in the ‘Default front end receive connector’ properties.
Tried adding DNS server IPs manually into both Transport servers in ‘DNS Lookup’ setting in the server properties.
Tried adding local server's IP to the hosts file.
Checked if SMTP fixup is enabled on Firewall.
Verified the receive connector security settings.
Verified the CPU and Memory utilization is normal.
Disabled the Performance Counter on both Transport Server to ensure memory usage.
but nothing seems helping
now the problem is because of this there is a mail delay of at least 20 minutes for incoming mails.
Need help resolving the same.
Neilesh

I think its working now ..
after researching a lot on events on Transport servers we got to know that 'Default Frontend Receive Connector' was rejecting some messages...
we have then increased the value for the parameter "MaxInboundConnectionPerSource" from 20 to unlimited and
MaxInboundConnectionPercentagePerSource
from 2 to 10.. we have the waited for 2 to three hours .. the queue then came down from 1500 to 5 and petty stable thereafter.
we will be monitoring the same for few days from now.
Neilesh

Unable to open delivery reports in Exchange 2013 SP1. Gives warning "The status for the recipient can't be determined because of a temporary error. Please try again later."

This seems to be occurring with all users (have tested a few, all display the same exact error message).
When I click on "Message Delivery Report" in Outlook 2010 or 2013, it points me to the ECP and displays this message "Warning The status for the recipient can't be determined because of a temporary error. Please try again later." I'm
not sure which log files to look at. The last time I remember it worked was before I applied SP1, I think CU3.
Our environment is two servers running Exchange Server 2013 Std. SP1 (847.32) in a DAG.
Thanks.

Hi,
From the error description, I would like to clarify the following thing:
Delivery Reports is a message tracking tool that you can use to search for delivery status on email messages sent to or from users in your organization's address book, with a certain subject. In Exchange 2013, you can track messages for up to 14 days after
they were sent or received. Please make sure the message you are tracking isn't older than 14 days.
Here is an article for your reference:
Track messages with delivery reports
http://technet.microsoft.com/en-us/library/jj150554(v=exchg.150).aspx
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

I am getting "Error in accessing iTunes store. Please try again later." Error 0x80092013. I have just downloaded and installed current version of iTunes, and have the 2013 Norton IS. My proxy server is letting me got to iTunes, but cannot login.

I have a proxy server and the server is allowing me to go to iTunes. But I get a message "Error in accessing iTunes store. Please try again later." Error code ox80092013. I cannot find that code in the troubleshooting section. I have just installed a new PC HP5750, with Norton IS 2013. I installed the current version of iTunes directly from the iTunes site. My proxy server is American Family Online web browsing filter. I contacted them and they said there should not be a problem with their server. I have had an account previously, but has been inactive for several months. I even tried to create a new account, but still got the same error code.
Someone please help with this. I have accompaniment tracks on iTunes that I need for music ministry.

Hi Lcoffin8,
Thanks for visiting Apple Support Communities.
See this article for additional information and steps that can help:
Can't connect to the iTunes Store
http://support.apple.com/kb/ts1368
Regards,
Jeremy

Cannot open Photoshop Elements. Receive error message 400 (Photoshop services are currently unavailable. Please try again later (I have) or check your network connections (they are OK). Error 400.

Cannot open Photoshop Elements. Receive error message 400 (Photoshop services are currently unavailable. Please try again later (I have) or check your network connections (they are OK). Error 400.

Photoshop.com is no longer available. The service transferred to Revel.
Ignore the sign-in altogether.
You may need to turn off Sync in Organizer prefs if you have it activated.

451 4.7.0 Temporary server error. Please try again later. PRX2 on sending emails to Office 365 Business Essentials email.

I've signed up for Office 365 Business Essentials service, and I have trouble sending and receiving emails. All the messages I send to my email associated with this account get a reply with error message
451 4.7.0 Temporary server error. Please try again later. PRX2
Additionally, all the mails I send from Outlook OWA in a browser and with iPhone app are stuck in Drafts folder and are not sent anywhere.
This is what I tried:
Checked the mail flow in Exchange admin center. There are no mail rules, no inbound or outbound connectors
Checked for DNS issues with my domain by clicking "Manage domains" in Admin center. Message was "barsukov.net domain is set up correctly. No action is
required."
Checked the MX records of my domain, barsukov.net, which point to a correct domain suggested by Microsoft.
Most of the search results related to this error suggest to add entries to hosts file on server with Exchange. This is not applicable to my case, obviously, since I use a cloud version of Exchange.
How to fix this issue?

It takes some time for newly added domains to be recognized by the service. If the issue persists, open a case with MS support:
http://virtualchat.support.microsoft.com/client/default.aspx?siteid=32ECF580-B446-44E5-8B4D-25F0AFE07779&query=Support%20phone%20number

451 4.7.0 Temporary server error. Please try again later. PRX2

I'm getting the dreaded "
451 4.7.0 Temporary server error. Please try again later. PRX2
" error when receiving SMTP mail.
does anyone know exactly what causes this error? there are many references to it on the web, but nobody seems to know exactly what causes it. maybe it's something to do with DNS?
can someone please ask someone on the exchange team to help document this?

Option A works for me...
Important: DNS Lookup issues
may prevent or delay message delivery or cause items to sit in OWA Drafts folder (7/22)
I’ve been following a thread on this since CU1\April but just now getting around to post it here, sorry for the delay if you’ve hit this issue
Tony Redmond’s also covered this on his blog here:http://thoughtsofanidlemind.wordpress.com/2013/03/25/exchange-2013-dns-stuck-messages/
In some environment message delivery will fail with the following error or be delayed by many seconds or minutes.
451 4.7.0 Temporary server error. Please try again later. PRX5
Threads on MS TechNet Forums: http://bit.ly/14A1JQY &http://bit.ly/13UG1ks
Quick Fix:
Option A: Set the NIC to use for “External DNS lookups” in EAC under Servers
Option B: Set ExternalDNSAdapterEnabled and InternalDNSAdapterEnabled to $false and set DNS servers on ExternalDNSServers and InternalDNSServers with the Set-FrontendTransportService command
Others have used a host file with the Exchange 2013 servers in it, but the above method is easier to manage

Cannot receive mail on Exchange 2013 CAS: 451 4.7.0 Temporary server error. Please try again later. PRX4

Similar Messages

Maybe you are looking for