Solved

Internal email servers weird routing

Posted on 2016-09-27
4
39 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 41

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

Salesforce Made Easy to Use

On-screen guidance at the moment of need enables you & your employees to focus on the core, you can now boost your adoption rates swiftly and simply with one easy tool.

Question has a verified solution.

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

MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

705 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