Sending, receiving, and organizing email in Outlook.com
The error indicates that the sending address has been flagged as a bad or spammy sender and is now blocked by the receiving systems. In Microsoft 365/Exchange Online this appears as an NDR like:
"Your message couldn't be delivered because you weren't recognized as a valid sender… Remote Server returned 550 5.1.8 Access denied, bad outbound sender."
This typically happens after malware or a hacker uses the account to send spam, or the account exceeds sending limits.
To fix this, two things must happen:
- Secure the compromised account
Because an attachment was opened and the account was hacked, the account and devices must be treated as compromised:- Follow the guidance in “Secure a compromised email account in Exchange Online” to:
- Reset the account password.
- Check and remove malicious inbox rules, forwarding, and delegates.
- Review sign-in activity and revoke suspicious sessions.
- Follow the steps in “Responding to a compromised email account” (linked from the NDR guidance) to ensure no malicious rules or connectors remain.
- Run a full malware scan on all devices used to access the mailbox.
- Follow the guidance in “Secure a compromised email account in Exchange Online” to:
- Remove the sending block placed by Microsoft
Once the account is secure, the sending block must be lifted:- If this is an organizational Microsoft 365/Exchange Online account, the email administrator must:
- Go to the Microsoft 365 Defender portal → Restricted entities page (
https://security.microsoft.com/restrictedusers). - Locate the blocked user and unblock the account.
- After unblocking, outbound restrictions are usually removed within about an hour so mail can be sent again.
- Go to the Microsoft 365 Defender portal → Restricted entities page (
- If this is a consumer Outlook.com/Hotmail account and messages are being rejected by Outlook.com recipients, review and follow the Outlook.com sender support guidance to improve spam reputation and, if needed, contact support using the troubleshooting form under “Troubleshooting tips for IT admins”.
- If this is an organizational Microsoft 365/Exchange Online account, the email administrator must:
If the problem is that other organizations (not Microsoft 365) are rejecting the mail because the sending IP or domain is on a block list, their NDRs may reference a blocked IP and direct to a delist portal such as https://sender.office.com/. In that case, follow the NDR instructions and use the Office 365 Anti-Spam IP Delist Portal to request removal from the blocked senders list after confirming the environment is clean.
Until the account is fully secured and the sending block removed, any mail sent from that address is likely to continue to be rejected as suspected spam.
References: