not authorized to relay messages through the Office 365 email servers

Paul Wells 21 Reputation points
2022-10-12T18:50:38.13+00:00

We have a 3rd party app that needs to send an email using smtp but we get the error "not authorized to relay messages through the Office 365 email servers" with Status code: 550 5.7.64

This sort of points us to look at connectors, there is already one in the but we are un able to edit and there is no option to create new connectors !!.

if we try and edit the current one it says "you do not have permission to edit this information" . I have a full admin account with access to everything, also our 365 license providers who are also admins get the same problem.

Exchange Online
Exchange Online
A Microsoft email and calendaring hosted service.
6,194 questions
Exchange | Exchange Server | Management
0 comments No comments
{count} votes

Accepted answer
  1. Aholic Liang-MSFT 13,886 Reputation points Microsoft External Staff
    2022-10-27T09:57:50.913+00:00

    Hi @Paul Wells ,

    To fix this issue i had to do the following

    Great to know that you've already thought of a solution and really appreciate it for your sharing!
    By the way, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others.". and according to the scenario introduced here: Answering your own questions on Microsoft Q&A, I would make a brief summary of this thread:
    [not authorized to relay messages through the Office 365 email servers]
    Issue Symptom:
    We have a 3rd party app that needs to send an email using smtp but we get the error "not authorized to relay messages through the Office 365 email servers" with Status code: 550 5.7.64
    This sort of points us to look at connectors, there is already one in the but we are un able to edit and there is no option to create new connectors !!.
    if we try and edit the current one it says "you do not have permission to edit this information" . I have a full admin account with access to everything, also our 365 license providers who are also admins get the same problem.

    The Cause:
    The administrator account loss "Remote and Accepted Domains" role to has no permissions
    The loss of "Remote and Accepted Domains" role for the administrator account leaves the administrator account without permissions to create connectors.
    Then run this

    New-ManagementRoleAssignment -Role "Remote and Accepted Domains" -SecurityGroup "Organization Management"  
    

    You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks!

    0 comments No comments

9 additional answers

Sort by: Most helpful
  1. Aholic Liang-MSFT 13,886 Reputation points Microsoft External Staff
    2022-10-13T06:47:00.437+00:00

    Hi @Paul Wells ,
    I checked the connector in my environment, and it doesn't seem to have modified the UI layout.
    249870-2022-10-13.png
    Did you try creating the connector using PowerShell?
    Please refer to the following command to create the connector to see if it works:

    New-InboundConnector -Name "SMTP Relay POSH" -ConnectorType 'OnPremises' -SenderDomains * -SenderIPAddresses 10.11.12.13 -RestrictDomainsToIPAddresses $true  
    

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Paul Wells 21 Reputation points
    2022-10-13T06:57:47.083+00:00

    Hi, yes we have also tried various things in powershell and that hasn't worked either.

    249982-capture.png


  3. Paul Wells 21 Reputation points
    2022-10-13T07:41:26.33+00:00

    yes we created a new test account with full admin roles and that was still the same.

    0 comments No comments

  4. Aholic Liang-MSFT 13,886 Reputation points Microsoft External Staff
    2022-10-13T09:02:46.727+00:00

    Hi @Paul Wells ,

    We have tried all basic troubleshooting that we can do. In my opinion, this issue may be caused by the tenant backend. I would suggest that you need open a ticket to resolve it.
    Thank you for your patient reply and understanding!
    The following is how to contact M365 support in the admin portal:
    250061-2022-10-13-2.png


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.