550 5.7.350 Remote server returned message detected as spam

Anonymous
2024-05-22T09:14:51+00:00

I have emails that don't want to reach the recipient, but I can't determine whether the problem is with them or with me?

550 5.7.350 Remote server returned message detected as spam -> 554 5.7.1 Message refused by SURBL check. m**i.s****.ch This email from IP 5*.*.*.0 has been rejected. The email message was detected as spam.

En-têtes du message d’origine

(The message header has been moved to private message)
Outlook | Windows | Classic Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2024-05-22T12:49:53+00:00

Hello Thomas Kisszalay ADM**,**

Good day!! Thank you for reaching out to Microsoft community.

Based on the provided description, it seems that the email you are trying to send has been detected as spam by the recipient's email server, leading to the 550 5.7.350 error. This could be due to various reasons such as the content of the email, the sender's email address, or the email server's reputation.

Since we do not have additional information regarding your issue, we cannot say for certain which is causing this issue for the moment. As you know in Mail flow there could be a number of possibilities for marked as SPAM. But here are some steps you can take for future incidents for a healthy Mail flow.

Follow this article for more information: Fix NDR error 550 5.7.1 in Exchange Online - Exchange | Microsoft Learn.

  • The sender is external, and their source IP address is on Microsoft's blocklist.
  • Your domain's MX record might have problem.
  • Your domain's MX record might have problem.
  • If your domain isn't fully enrolled in Microsoft 365 or Office 365, try the following steps:

To resolve this issue, you can try the following initial steps:

  • You can ask the recipient to whitelist your IP address.
  • My suggestion is to add the sender’s domain in the safe sender list and allow list in the spam filter.
  • Check the content of your email and ensure that it does not contain any spammy or suspicious content.
  • Contact the recipient and ask them to check their spam or junk folder to see if your email has been mistakenly marked as spam.
  • Depending on the recipient side and if you have access to the Exchange admin center, we can add a connector to force outgoing traffic to recipient mail hosts to use IPv4 apparently fixed the issue (Mostly on google service provider).

Additionally, I have checked your domain reputation also the header you have sent, it's strange to admit that there should be a reason for marking your email as SPAM. your domain reputation seems fine also the message header SCL value seems fine along with other data.

So, we looked into the service incident, and this is what we found below:

  • Title: Users are unable to receive email messages from external domains within Exchange Online
  • User impact: Users are unable to receive email messages from external domains within Exchange Online.
  • Current status: We’re continuing to review details provided in the support case and are attempting to retrieve diagnostic data from our telemetry to identify the source of the issue and formulate a mitigation plan.
  • Scope of impact: Your organization is affected by this event, and any user attempting to receive email messages from external domains is impacted.

Image

I hope this helps. Let me know if you have any further questions or concerns.

To better understand the issue and after the Serice Incident is lifted, if you still experience the same issue, I need your help on sending all the answers along with the data only via Private Messages - Microsoft Community. So that we can get on the same page and resolve the issue together:

Please understand that our initial response may not always resolve the issue immediately. However, with your help and more detailed information, we can work together to find a solution.

Thanks for choosing the MS community.

Looking forward to your response and have a great day ahead!!

Sincerely

S M Nazmun Nur | Microsoft Community Moderator

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

0 additional answers

Sort by: Most helpful