Solved

Internal email servers weird routing

Posted on 2016-09-27
4
37 Views
Last Modified: 2016-09-29
below i have a message header from an email sent from one user to another in our organization. Both users reside on the same server but in different mailboxes.

Looking at the log it looks like it was passed around servers a few times before coming to rest at the correct mailstore. what could cause this sort of routing issue? Everything else seems to be working without issue.

Received: from INTERNAL-EXCHSRV.internaldomain.local (192.168.1.12) by
 INTERNAL-MAILSRV.internaldomain.local (192.168.1.33) with Microsoft SMTP
 Server (TLS) id 15.1.466.34 via Mailbox Transport; Mon, 26 Sep 2016 11:29:52
 +0100
Received: from INTERNAL-MAILSRV.internaldomain.local (192.168.1.33) by
 INTERNAL-EXCHSRV.internaldomain.local (192.168.1.12) with Microsoft SMTP
 Server (TLS) id 15.0.1210.3; Mon, 26 Sep 2016 11:29:52 +0100
Received: from INTERNAL-MAILSRV.internaldomain.local ([::1]) by
 INTERNAL-MAILSRV.internaldomain.local ([::1]) with mapi id 15.01.0466.034; Mon,
 26 Sep 2016 11:29:52 +0100
0
Comment
Question by:CaptainGiblets
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 40

Expert Comment

by:Adam Brown
ID: 41818170
Do all your exchange servers have all the roles installed? What version are you running?
0
 
LVL 6

Author Comment

by:CaptainGiblets
ID: 41818198
oen is 2013 latest CU and the other is 2016 latest CU

Basically i am in middle of migrating users between 2013 to 2016 when i noticed this weird issue. but both users are on the 2016 server.

Both have all roles installed.
0
 
LVL 49

Accepted Solution

by:
Akhater earned 500 total points
ID: 41818592
There is nothing weird here, an email is routed to another transport server for it to be in covered by the shadow redundancy in case the sending server failed (part of the Exchange safety net)

in short 2016 got the message from the mailbox server
2016 routed the email directly to 2013 to put it in the shadow redundancy
2013 routed it back to 2016 since the mailbox is on 2016
2016 delivered the message
0
 
LVL 6

Author Closing Comment

by:CaptainGiblets
ID: 41821478
Thanks.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Find out what you should include to make the best professional email signature for your organization.
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

737 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question