Link to home
Start Free TrialLog in
Avatar of Information Technology
Information Technology

asked on

mail.protection.outlook.com rejecting our email

We host our own Exchange Server.  We only have trouble sending email to Outlook.com addresses.  Here is the error -

mail.protection.outlook.com[x.x.x.x] said: 451 4.7.500 Server busy. Please try again later from [x.x.x.x]. (AS77712200).

We are not on any block list and have submitted our ip address to Outlook.com Deliverability Support.  Also joined SNDS and JMRP per their recommendations.  

Any suggestions?
Avatar of CES
CES

Does your sending server have correct PTR and SRV records in place?
This message 451 4.7.500 Server busy suggests the server you're connecting to really is busy.

If there was a problem with your outgoing DNS + SPF + DKIM, I'd expect a very different message.

Open a support ticket with Outlook + ask them how to resolve this. Likely this will provide you with the fastest resolution.
HI,

Which Exchange version do you have?

It seems that there is some delay in sending. Do you use any proxy?

Is your environment hybrid?

Cheers
Avatar of Information Technology

ASKER

We have Exchange 2013.  

Microsoft has NOT been much help.  Here is their response last week...

Hello,
 
We have completed our investigation of your sending IP (x.x.x.x) and determined that there are no active blocks against it.  
 
However, we found that some messages were being filtered based on the recommendations of the SmartScreen® Filter which is resulting in them being delivered to user's junk mail folder rather than their inbox.
 
We have confirmed that your IP is eligible for temporary mitigation based on our mail policies.
 
Please note: The mitigation process may take 24 - 48 hours to replicate completely throughout our system.
ASKER CERTIFIED SOLUTION
Avatar of Information Technology
Information Technology

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Author reached resolution on their own.