Forum Discussion

Anthony Obi's avatar
Anthony Obi
Copper Contributor
Sep 23, 2016

Remote Server returned '550 5.7.501 Access denied, spam abuse detected.

 

Anyone else receiving "Remote Server returned '550 5.7.501 Access denied, spam abuse detected." when attempting to send from @<O365subdomain>.onmicrosoft.com?

 

Found various discussions that mention MS Engineers 'delisting' domain to resolve the issue?

http://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook/remote-server-returned-550-57501-access-denied/23b2794d-ddc2-4e4d-a4b7-ee1f136a300a?page=2
http://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook-mso_win10/cant-respond-to-emails-anymore-receiving-this/cf29cbfd-3e7b-48d3-a186-8436b5ee35f9

http://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook/remote-server-returned-550-57501-access-denied/7d6df30b-a185-4c69-95b7-2c94537127ee

6 Replies

  • Anthony Obi 

    I am getting same error whenever I send any mail to any one (Inside the group or outside the group).

    Please help me.

     

    Delivery has failed to these recipients or groups:

    mailto:o365su12@microsoft.com
    Your message wasn't delivered because the recipient's email provider rejected it.

    Diagnostic information for administrators:

    Generating server: BM1PR01MB2561.INDPRD01.PROD.OUTLOOK.COM

    o365su12@microsoft.com
    Remote Server returned '550 5.7.501 Service unavailable. Spam abuse detected from IP range. For more information please go to http://go.microsoft.com/fwlink/?LinkId=526653. S(2017052602) [BM1PR01MB2532.INDPRD01.PROD.OUTLOOK.COM]'

  • Yes, this is something usual when sending from onmicrosoft.com and when the originating IP is from specific network classes.

     

    You can send from a vanity domain, or send from another network that is not blacklisted, or you can open a service request to Microsoft Support and give them a complete NDR.

    • Anthony Obi's avatar
      Anthony Obi
      Copper Contributor

      Thanks Victor.

       

      Attempting to send from https://outlook.office.com so assuming no way of affecting/changing the originating IP network classes etc?

       

      Will try applying custom domain (vanity domain) to O365 tenancy and try resending.

      (Failing that, service request to Microsoft Support as suggested)

       

      Thanks

      • Victor_Ungureanu's avatar
        Victor_Ungureanu
        Icon for Microsoft rankMicrosoft

        Changing the primary SMTP to a vanity domain will solve this issue for sure :)

Resources