Exchange 2013 Message Loop
Hello EE Community
here is scenario that i am dealing with exchange 2013
the company already has an exchange email service through a 3rd party..we'll call it domaina.com
a few cloud servers were setup separately elsewhere with active directory using the domaina.com, one of those servers was setup with exchange. this is for another domain that they have we'll call it domainb.com.
to setup an email for domainb.com it obviously gets a domaina.com ad account.
sending and receiving using the domainB.com alias works great to anyone in the world EXCEPT when trying to send to domainA.com
that's where the loop occurs and it that cant leave the server because it thinks a domaina.com email address is within its realm.
my question is has anyone dealt with a situation like this or would active directory have to be reconfigured with the domainb domain name?
Thanks again fellas and ladies
here is scenario that i am dealing with exchange 2013
the company already has an exchange email service through a 3rd party..we'll call it domaina.com
a few cloud servers were setup separately elsewhere with active directory using the domaina.com, one of those servers was setup with exchange. this is for another domain that they have we'll call it domainb.com.
to setup an email for domainb.com it obviously gets a domaina.com ad account.
sending and receiving using the domainB.com alias works great to anyone in the world EXCEPT when trying to send to domainA.com
that's where the loop occurs and it that cant leave the server because it thinks a domaina.com email address is within its realm.
my question is has anyone dealt with a situation like this or would active directory have to be reconfigured with the domainb domain name?
Thanks again fellas and ladies
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Adam Brown
Okay. The smart host on the send connector should point to the MX record of DomainA.com. Other than that, those settings should work to resolve your issue.
ASKER
i was able to get the 3rd party's mx record..the question is should i have any @domaina.com recipient or contact accounts set up on the exchange 2013 box?
ASKER
update:
i have a few domainA emails set up as mail contacts within exchange..
i created the internal and send connector..i was able to receive replies from domainA.com
i replied back and fourth with a few message perfectly fine. but now i am not able to
i checked the delivery report for the few test emails and it reads:
Delivery Report for donald beno (dbeno@domainA.com)
Submitted
11/4/2016 8:50 AM exch2k13
The message was submitted to exch2k13.domainA.com.
Pending
11/4/2016 8:50 AM exch2k13.domainA.com
Message was received by exch2k13.domainA.com from exch2k13.domainA.com.
11/4/2016 8:50 AM exch2k13.domainA.com
The message has been queued on server 'exch2k13.domainA.com' since 11/4/2016 8:50:36 AM (UTC-08:00) Pacific Time (US & Canada). The last attempt to send the message was at 11/4/2016 9:06:44 AM (UTC-08:00) Pacific Time (US & Canada) and generated the error '[{LRT=};{LED=};{FQDN=};{I
i have a few domainA emails set up as mail contacts within exchange..
i created the internal and send connector..i was able to receive replies from domainA.com
i replied back and fourth with a few message perfectly fine. but now i am not able to
i checked the delivery report for the few test emails and it reads:
Delivery Report for donald beno (dbeno@domainA.com)
Submitted
11/4/2016 8:50 AM exch2k13
The message was submitted to exch2k13.domainA.com.
Pending
11/4/2016 8:50 AM exch2k13.domainA.com
Message was received by exch2k13.domainA.com from exch2k13.domainA.com.
11/4/2016 8:50 AM exch2k13.domainA.com
The message has been queued on server 'exch2k13.domainA.com' since 11/4/2016 8:50:36 AM (UTC-08:00) Pacific Time (US & Canada). The last attempt to send the message was at 11/4/2016 9:06:44 AM (UTC-08:00) Pacific Time (US & Canada) and generated the error '[{LRT=};{LED=};{FQDN=};{I
ASKER
internal relay config worked..so far so good. thanks adam
ASKER
internal relay config advice worked