Link to home
Start Free TrialLog in
Avatar of tiptechs
tiptechs

asked on

external exchange domain through edge transport server

I have the following setup.

Exchange 2003 on domain2.com (external)

Exchange 2013 on domain1.com

In the exchange 2013 setup there is an Edge transport server and the plan is to have all mail go through that for both domains.  I have send / receive connectors setup on 2013 exchange servers to allow domain2 to email through domain1 and out the edge transport service.  

Currently I have no problems emailing back and forth between domain1 and domain2.  I can also send email outside both domains from domain2 and domain1 through the edge transport server.

My issue is with inbound email from the outside to domain2.  I can send to domain1 from the outside with no issues.    On the edge transport server I see the emails for domain2 in the message tracking logs making it into the server, but can't tell where they are getting hung up.    I did get a few non deliverables a few hours later from the edge transport server.

Not sure if the issue is with the edge transport server or if there is a way to see where it is hanging up.

Thanks
Avatar of Veerappan Sundaram
Veerappan Sundaram
Flag of India image

To find out complete detail on a message, find out the events of a particular message using
Get-messagetrackinglog -recipients user_id@domain2.com -start "02/13/2015 09:00 AM" -end "02/13/2015 11:00 AM"
Above cmdlet gives the events related every message.

The sample event IDs are Receive, deliver, transfer, Fail, etc.

If there is a event ID for Fail, then run the above cmdlet and add "-eventid fail | fl"
this should give you the details.

------
Is it non-deliverable notification or Delay Notification?

In either case, the notification should have the required information.
please post the notification.

Thanks,
Veera.
How do you have the two domains connected to the edge server .e send and receive connectors?
check the bouncback messages as that will tell you what occurred. let us know the error.
I suspect you've got a routing issue as the servers are confused about where to send the mail for the separate domain, but its only a guess until we get more info.
Also, find the messages in message tracking and look for the error In there. this will let you know how far through the process it got before giving up (ie don't just look at the 'recieve' action.)
ASKER CERTIFIED SOLUTION
Avatar of tiptechs
tiptechs

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of tiptechs
tiptechs

ASKER

Found the fix for the issue on another site.