Outlook.com/Hotmail rejects messages when the sending server or domain does not meet Microsoft’s current authentication and anti‑spam requirements.
Two common causes from the provided information:
- Relay / unauthorized‑sender style failures (550/553)
If the Yahoo message is being forwarded through another SMTP server (for example, an intermediate service or a misconfigured client), Outlook.com may see that server as not authorized to send for the Yahoo address and reject it with a 550/553 or “relaying denied” type error. In these cases, the Outlook.com SMTP server does not recognize the sender as an authorized user and refuses to relay or accept the message.
- Authentication requirements for high‑volume senders (550 5.7.515)
If the Yahoo message is coming from a domain or service that sends large volumes of mail into Outlook.com and that domain does not meet Microsoft’s required authentication level (SPF/DKIM/DMARC alignment, etc.), Outlook.com can return an NDR like: “550 5.7.515 Access denied, sending domain <domain> does not meet the required authentication level. The sender's domain in the 5322.From address doesn't meet the authentication requirements defined for the sender.” In this case, Outlook.com is enforcing stricter authentication rules to reduce spam and phishing.
What to do next depends on who controls the sending system:
- If using automatic forwarding from Yahoo or another service into Outlook.com, review that service’s forwarding configuration so that messages are sent in a way that preserves proper authentication (SPF/DKIM/DMARC) for the original From domain.
- If the error text includes
550 5.7.515, the owner of the sending domain (for example, an email service or IT admin) must update the domain’s email authentication to meet Microsoft’s requirements for high‑volume senders, as described in the non‑delivery report.
References: