none
550 5.4.1 [email]: Recipient address rejected

    Question

  • Good day!

    We are encountering this error:

         550 5.4.1 [email]: Recipient address rejected:

         Access denied [<>.eop-APC01.prod.protection.outlook.com]

    We set two MX record so Office 365 will propagate before our switching.

         Office 365 MX Record with 20 Priority Level

         Current Email System's (3rd Party) MX Record with 10 Priority Level

    Hope someone can give me answers :) .

    Thank you!


    Mary Yvette Bulaong

    Wednesday, May 15, 2019 3:32 AM

Answers

  • If you post your domain, I can look at your MX records.

    Note that if you have an MX record, spammers will often use the record with the highest cost number to try to send spam under the assumption, which is often valid, that the secondary MX will have less protection.

    Do you have a hybrid configuration and/or Azure AD Connect?  Are the target addresses in question defined in your Office 365 directory?


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!


    Thursday, May 16, 2019 2:12 AM
    Moderator

All replies

  • In your Office 365 Admin Portal, click Setup > Domains.  Use the FQDN value shown for MX as the destination for your SMTP services.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Wednesday, May 15, 2019 6:07 PM
    Moderator
  • Hi Ed,

    MX Records for Office 365 are correct.

    We are not yet planning to do the switching. We just want the two records to coexist but the email priority will still go to their existing Email System. But we are receiving Email Delivery Issue.

    Thank you!


    Mary Yvette Bulaong


    Thursday, May 16, 2019 1:14 AM
  • If you post your domain, I can look at your MX records.

    Note that if you have an MX record, spammers will often use the record with the highest cost number to try to send spam under the assumption, which is often valid, that the secondary MX will have less protection.

    Do you have a hybrid configuration and/or Azure AD Connect?  Are the target addresses in question defined in your Office 365 directory?


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!


    Thursday, May 16, 2019 2:12 AM
    Moderator
  • Hi Mary,

    I'm just writing to check how's everything going? If you have any questions or needed further help on this issue, please feel free to post back. If the issue has been resolved, please mark the helpful replies as answers, this will make answer searching in the forum easier and be beneficial to other community members as well.

    Thanks for your understanding.


    Best Regards,
    Niko Cheng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.


    Friday, May 24, 2019 9:41 AM
    Moderator
  • Thanks for all the help. The issue is now resolved. The Office 365 and their 3rd party email system is no coexisting the DNS record. With the 3rd party with high privilege. The issue was with the the steps done in adding the Office 365 MX Record in the DNS Management.


    Mary Yvette Bulaong

    Saturday, May 25, 2019 1:03 AM
  • Hi Mary,

    Glad you solved the issue and thanks for your sharing, it would help other community members as well.



    Best Regards,
    Niko Cheng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, May 27, 2019 1:13 AM
    Moderator