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.
Can you post the full failure message?
Just to make sure, you are entering in a valid gmail address correct?
And do you have a valid SPF record?
If you send me your domain name, I can check your record.
Thanks for the detailed instructions!
I can't get any of the Gmail mail exchangers to validate any gmail address so far. ie, alt3.gmail-smtp-in.1.google.com
Updated 22 April 2024
Issue: Your O365 hosted email bounces back as SPAM from any g-mail/google hosted domain.
SOLUTION: Create a DMARC record for your domain
The "TRUE" solution is to add a DMARC record to your domains DNS records. I won't go into details of what dmarc is, but you can read it here: https://dmarc.org/ . The simplified version is that "YOU" are sent reports by ISPs regarding how your domain name is being used.
**If you do not know how to add a record into your DNS server, contact the person who manages it for you".
The record is very easy to build. It requires sending to an valid email address. I strongly recommend creating "THIS/AN" special email address (a group based distribution list that can receive email from outside your org). I use dmarc@ for all my domains email.
The format in DNS is as follows
HOST: _dmarc
VALUE: v=DMARC1; p=none; rua=mailto:YourEmailAddress; ruf=mailto:YourEmailAddress fo=1:d:s
TTL: I prefer 1Hour but you can choose anything.
Once it is set up correctly, you can test this by going to https://mx****/dmarc.aspx
That is all there is too it. No need for special mail flow rules.
Michael B. Morell, CISSP #431307 CCSK
Information Security Professional
DirectionWeb Inc.
** I am leaving the below for research purposes on how to properly create a mail flow rule **
Solution: Create a "Mail Flow Connector" within the Exchange Admin Center. The mail flow connecter will be used for the domains you are having issues sending to.
Assumptions: 1. You have at a minimum, a properly formatted SPF record published in DNS. 2. You have access to the exchange admin console.
==========================================
--- How to create a Connector to GMAIL/Google MX servers ---
==========================================
** where DOMAINNAME is the domain you are having issues with.
DOMAINNAME.com MX preference = 10, mail exchanger = aspmx2.googlemail.com
DOMAINNAME.com MX preference = 10, mail exchanger = aspmx3.googlemail.com
DOMAINNAME.com MX preference = 1, mail exchanger = aspmx.l.google.com
DOMAINNAME.com MX preference = 5, mail exchanger = alt1.aspmx.l.google.com
DOMAINNAME.com MX preference = 5, mail exchanger = alt2.aspmx.l.google.com4
gmail.com MX preference = 40, mail exchanger = alt4.gmail-smtp-in.l.google.com
gmail.com MX preference = 10, mail exchanger = alt1.gmail-smtp-in.l.google.com
gmail.com MX preference = 20, mail exchanger = alt2.gmail-smtp-in.l.google.com
gmail.com MX preference = 30, mail exchanger = alt3.gmail-smtp-in.l.google.com
gmail.com MX preference = 5, mail exchanger = gmail-smtp-in.l.google.com
Press Next
Description: This will route all email to google hosted domains we are having issue with. Any new domains discovered to be having issues can be added to this rule. This rule supports multiple destination domains.
Check the two boxes
Press Next
"Only when email messages are sent to these domains"
Type gmail.com and press the Plus sign on the far right.
Enter in the remaining domains. **There is no limit**
Press Next
It is the same procedures as step 9. Add one in at a time.
**Important, you MUST enter in mail exchangers
Press Next
11**.** In the security restrictions, leave the defaults as they are.
Press Next
Once you add in the email address(s), press Validate. The validation process takes a minute or two, so be patient.
If the "Send Test Message" does not succeed, you will need to recheck the MX records.
**Tip- If it fails, Make sure you are not trying to add a domain that exists in another transport rule. It will fail.
Press Next
You can now send emails to those domains that did not work before.
Michael B. Morell, CISSP #431307 CCSK
Information Security Professional
DirectionWeb Inc.
Same thing here, as per my finding this is something with MS SPF record, when the email uses their IPV6 address to deliver emails is when it is failing when it uses ipv4 it goes through..
OK, so thanks to this I was able to find a temporary workaround, at least for gmail accounts.
I looked for the MX records for gmail.com, using mxtoolbox, and took note of a few IPv4 addresses. They apparently rotate these addresses, but whatever.
Then in Exchange Admin, I created a conector from Office365 to Partner organization -> for emails sent to *.gmail.com -> route mail through smart hosts, and added all the IPv4 addresses.
Finished creating the connector, saved it and that's it. All emails to gmail are going through now.
Of course we still can't send emails to our customers that are hosted by google, but it's better than nothing. I guess I can create individual connectors for them. Not ideal.
Anyway. I hope this workaround holds and that this helps someone.
I've tried this, and it verifies fine with my personal gmail addresses, but when testing through the dynamic distribution lists all gmail recipients are delayed... The way we run this (a small community band) is DDLs that people can email at for distribution to the whole band. This is killing the utility and we're starting to investigate alternatives (which are not as powerful in my opinion). Any other suggestions would be great!
yes, godaddy. is there any help?