Hybrid Mail Flow

Luizg_mg 81 Reputation points
2020-08-04T00:17:59.22+00:00

Hello everyone,

I have an Hybrid environment with E2K13 servers.
My mail flow is, for outgoing messages:
From On Prem Mailbox to Internet:
Mailbox -> Edge Server -> EXO -> Antispam-> Internet
From EXO to Internet:
EXO -> Antispam-> Internet

SMTP domain: @test .com
I have hosted an application at AWS that contains a subdomain email address @aws .test.com.
The MX for that subdomain is on AWS.
When I send an email to x@aws .test.com from OnPrem mailbox I receive an message "Remote Server returned '554 5.4.6 Hop count exceeded - possible mail loop'. It´s not working when sends email from EXO.
I added @aws .test.com as Accepted Domain in On Prem and EXO but not working:
New-AcceptedDomain -DomainName aws.test.com -DomainType InternalRelay -Name aws.test.com.
Any clue?

Any help will welcome.
Thank you all.

Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
1,975 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Joyce Shen - MSFT 16,646 Reputation points
    2020-08-05T01:53:06.893+00:00

    What antispam are you using? Please note that if you are using 3rd party anti-spam filter, it can only filter the messages sent from Internet to your organization, detailed information about this: Manage mail flow using a third-party cloud service with Exchange Online, you could try temporarily disabling the antispam to verify whether the issue is caused by this.

    In addition, here is an article discussed about Fix email delivery issues for error code 5.4.6 or 5.4.14 in Exchange Online

    0 comments
  2. Andy David - MVP 144.2K Reputation points MVP
    2020-08-05T12:42:15.15+00:00

    Your anti-spam solution is configured to route all messages sent to your domain to your Exchange org and creating a mail loop. You will need to set an exception for aws.test.com and route it to AWS.

    0 comments