If some senders get a rejection or bounce-back, this is often not a mailbox setting on the Hotmail/Outlook.com side.
Check these items first in Outlook.com:
- Check Junk Email settings and the Junk Email folder. If valid messages were marked as junk, move them back by right-clicking the message and selecting Mark as not junk.
- Check whether email forwarding is enabled.
- Check whether any rules are moving or hiding messages.
- Check the Other tab and make sure filters are not hiding messages.
- Check mailbox and Microsoft cloud storage usage. If cloud storage is full, Outlook.com cannot send or receive email, and messages sent while storage was full are bounced back and unrecoverable.
- If the account password was changed recently, update it. Accounts can also be temporarily blocked because of unusual sign-in activity.
If senders are receiving a non-delivery report, the exact error in that report matters:
- If the rejection mentions SPF fail or that the sender domain does not meet authentication requirements, the sender must fix their domain email authentication. That is not something that can be corrected in the mailbox.
- If the rejection says the sender IP is blocked or shows 5.7.511 Access denied, the sender needs to use the Microsoft delist process for their sending IP.
- If the rejection says Microsoft temporarily restricted mail from the sender IP, such as 451 4.7.550 Access denied, please try again later, the restriction is temporary while the traffic is evaluated.
If only certain senders are affected and others can still deliver mail, that strongly points to a sender-side issue such as SPF/authentication failure or poor sending IP reputation, not a problem with the mailbox itself.
A practical next step is to ask one affected sender to send the full bounce-back error text. That will show whether the issue is:
- sender authentication failure,
- sender IP blocklisting or throttling, or
- a mailbox-side filtering or forwarding issue.