This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
When the emails is sent to gmail its being blocked stating
Delivery has failed to these recipients or groups:
___@___.___ (***********@gmail.com)
Your message wasn't delivered because the recipient's email provider rejected it.
all my records are up to date..
gmail.com suspects your message is spam and rejected it.
| natasha.daniel | Office 365 | gmail.com | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Sender | Action Required | |||||||||||
| <br> | --- | --- | --- | --- | --- | |||||||
| Messages suspected as spam |
| How to Fix It |
|---|
| Try to modify your message, or change how you're sending the message, using the guidance in this article: Bulk E-mailing Best Practices for Senders Using Forefront Online Protection for Exchange. Then resend your message. |
| If you continue to experience the problem, contact the recipient by some other means (by phone, for example) and ask them to ask their email admin to add your email address, or your domain name, to their allowed senders list. |
Was this helpful?Send feedback to Microsoft.
More Info for Email AdminsStatus code: 550 5.7.350
When Office 365 tried to send the message to the recipient (outside Office 365), the recipient's email server (or email filtering service) suspected the sender's message is spam.
If the sender can't fix the problem by modifying their message, contact the recipient's email admin and ask them to add your domain name, or the sender's email address, to their list of allowed senders.
Although the sender may be able to alter the message contents to fix this issue, it's likely that only the recipient's email admin can fix this problem. Unfortunately, Office 365 Support is unlikely to be able to help fix these kinds of externally reported errors.
Original Message Details
| Created Date: | 3/2/2023 11:29:38 PM |
|---|---|
| Sender Address: | *********@*****.com |
| Recipient Address: | *********@gmail.com |
| Subject: | Email check |
Error Details
| Reported error: | 550 5.7.350 Remote server returned message detected as spam -> 550 5.7.1 [2a01:111:f403:700f::715 19] Our system has detected that this;message is likely suspicious due to the very low reputation of the;sending domain. To best protect our users from spam, the message has;been blocked. Please visit; https://support.google.com/mail/answer/188131 for more information. c23-20020aa7c997000000b004ace5dc6b61si945041edt.369 - gsmtp |
|---|---|
| DSN generated by: | PN3P287MB0113.INDP287.PROD.OUTLOOK.COM |
Using Classic Outlook on Windows for personal email, calendar, and contact management
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.
I'm having the same issue in 365 connected to go daddy. did you ever get a resolution to this? thanks!
After troubleshooting this issue I wanted to add my experience as it might be helpful to those still having issues. We were also seeing NDRs as described by @ProfessionalGeek who opened this thread. Long story short....
Root cause: Thanks to DMARC reporting (and a good baseline) we found the domain had recently been used in a mass spam mail out due to a misconfigured SPF record. We saw spammers sending out mail from the domain (passing SPF & DMARC) which spiked for 3 days and then stopped but then google started rejecting the domain due to low reputation of the domain. Kinda makes sense right?
Takeaway #1 - Setup DMARC reporting!
Takeaway #2 - Check DMARC and SPF records DMARC should not be p=none!! and SPF record should -all
Takeaway #3 - Are you 100% sure your domain is really not sending spam? Spammers can be like trying to find a water leak *sad face*
The IPv4 Work Around
As suggested we adjusted to hit the IPv4 addresses rather than IPv6. The result was 1 email out of 3 would deliver. For me that is totally strange but the inconsistencies don't stop there. After a week all mail via IPv4 connectors worked but any attempts via IPv6 continue to fail to this day.
My Take Away
Is Microsoft at fault? No I don't think so.
Is Google at fault? No I don't think so. We confirmed for other domains IPv6 worked without issues between Microsoft and Google.
Are you are fault? Maybe... I'll let you answer that :)
But I would add that we saw clear inconstancies with google mail servers. I have a the feeling the IPv6 server farm is either not seeing enough traffic to train it's spam engine or is more harden for blocking these types of events. But it's the sort of thing that only a Google engineer can answer. *insert another sad face here*
Hi.
Have you aligned the SPF, DKIM, and DMARC?
I use this tool which is a life saver for keeping emails out of junk
I'm using Officer 2019 and what I did was reload the software. Everything is now working.
Hi,
We've been experiencing this issue for the past few months. We are not a business sending bulk mail by any means either.
I've setup a connector as described in Michael B Morell's post which allows for mail to flow through except the mail still goes to the recipients junk folder.
I've tried raising a ticket with Gmail support but we are still waiting to hear anything for 2 months. Does any one know if theres anything else that can be done to prevent these messages going to junk folder?
Thanks