Status code 550 5.7.350: another server called it spam

Paste a status code 550 5.7.350 bounce to read the reply Microsoft 365 passed on and see what to check before you resend.

Try:

Runs in your browser. Nothing is sent or stored.

550 5.7.350: Remote server rejected it as spamMicrosoft 365 is passing on another server's refusal: the recipient's server (or its filter) judged the message to be spam. The reply after '->' is that server's own code and reason.Microsoft 365 ยท Hard bounce ยท No automatic retry
Browse all 213 codes

1 of 213 codes

  • 550 5.7.350Remote server rejected it as spamMicrosoft 365
    What it means
    Microsoft 365 is passing on another server's refusal: the recipient's server (or its filter) judged the message to be spam. The reply after '->' is that server's own code and reason.
    Why it happens
    Depends on the remote server's reason, often the sending domain's reputation or authentication, or the links in the message.
    The fix
    Decode the code after '->': that is the real reason. Check SPF, DKIM and DMARC for your domain and the links in the message.
    Bounce
    Hard bounce. No automatic retry

    Source: learn.microsoft.com (opens in a new tab), learn.microsoft.com (opens in a new tab). Checked Nov 9, 2026.

Photo of Utku Zihnioglu

By

ยท CEO & co-founder

Updated Nov 11, 2026

Shorter page: the tool first, the answer in a few lines.

Status code 550 5.7.350 means another mail server judged your message to be spam and refused it, and Microsoft 365 passed that refusal back to you. The reason is in the reply after the arrow, so fix what that reply names before you send again.

How to read the result

The line reads close to "550 5.7.350 Remote server returned message detected as spam", then an arrow, then a second code. Everything before the arrow is Microsoft's wrapper. After it comes the remote server's own reply, and the decoder reads both.

In one Microsoft Q&A thread, the reply after the arrow was a Gmail 5.7.1 about a very low domain reputation. Microsoft's half said only "spam", and Gmail's half said why.

No Microsoft Learn article documents 5.7.350. Its meaning rests on a Microsoft Q&A thread where a Microsoft Community Moderator answers that the recipient's server detected the message as spam. Treat it as a careful reading, not an official definition, and do not confuse it with 5.0.350, Microsoft's catch-all for nonspecific errors from the recipient's organization.

How to fix it

Work from the far side of the arrow back to your own setup:

  • The reply after the arrow. Decode it on its own; it names the real reason.

  • SPF, DKIM, and DMARC. Check them for the service you send from, aligned with your From domain.

  • The links. Check every link in the message and the domain it points to.

  • Your sending reputation. When the reply names it, send less, to people who expect your mail, and give it time.

No record you publish today changes how a receiver judged yesterday's mail. In Oneprofile, a sequence can send as plain text with no links or formatting, and each mailbox has a daily send limit you raise a little at a time. For the wider picture, read a cold email deliverability playbook, list to mailbox.

Status code 550 5.7.350: common questions

Is 550 5.7.350 a problem with my Microsoft 365 account?

Usually not. Microsoft 365 only delivers the news: the refusal came from the server after it. Your own setup still matters, because that server's reasons are often your domain's authentication or reputation.

Will changing a forwarding rule fix 550 5.7.350?

Nothing Microsoft has published says so. The code reports another server's spam verdict, so start from that server's reply after the arrow, then check SPF, DKIM, and DMARC, and the links in the message.

Does verifying email addresses prevent a 550 5.7.350 bounce?

Not directly. A spam verdict is about the message and the sender, not about whether the address exists. Verification still helps over time: verified addresses bounce less, which protects the sending reputation spam filters weigh.

About this article

Photo of Utku Zihnioglu

Utku Zihnioglu

CEO & co-founder

Serial entrepreneur who built infrastructure companies handling billions of requests. Now leads engineering at Oneprofile, which finds the people worth talking to, researches each one, and follows up until they reply.

Drafted with AI from our product docs and code. Utku Zihnioglu answers for what it says.

Verify the list before the next send

Oneprofile can verify each address before a sequence sends, and you can start free.

Free plan: 200 credits a month, 3 integrations, no card

Verify the list before the next send

Oneprofile can verify each address before a sequence sends, and you can start free.

Free plan: 200 credits a month, 3 integrations, no card