Solved

Exchange 2013 - message not being delivered to the inbox internally

Posted on 2015-02-24
9
17 Views
Last Modified: 2015-05-24
hi,

this is my first installation of Exchange 2013 and I'm missing something...  Internal mail isn't being delivered to the users inboxes, however the mail is showing as being sent in the Sent Mail folder and I can't figure out what's wrong.

at the moment this server is at release candidate 1, so not service packs have been installed; that's my next step but I thought it worth asking the question before proceeding the SP3 installation.

any advise, would be very much appreciated.

thanks
0
Comment
Question by:TopCat-007
[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
  • 6
  • 2
9 Comments
 
LVL 14

Expert Comment

by:Andy M
ID: 40628081
I would start by looking through the tracking logs on the server - this will show the process that the email has gone through and should also indicate the area the problem occurs.

Here's how to do it: https://technet.microsoft.com/en-GB/library/bb124926%28v=exchg.150%29.aspx

I would also recommend putting the updates on (believe it's up to CU7 at the moment) as these fix a lot of bugs in Exchange 2013.
0
 

Author Comment

by:TopCat-007
ID: 40628096
Thanks Andy, i'm installing CU7 as I type
0
 
LVL 10

Expert Comment

by:Muhammad Mulla
ID: 40628102
I would also check to see how the Hub transport connectors are setup.
0
Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

 

Author Comment

by:TopCat-007
ID: 40628306
The installation of CU7 has resolved my issue however all the emails I've sent previously as tests have not been delivered yet, which I find a bit mystifying; Newly send emails are being delivered correctly.  phew!

thanks for your help!
0
 

Author Comment

by:TopCat-007
ID: 40630807
bizarrely this problem has not been resolved, after a reboot today the problem has returned.  

Does anyone have any information on how to check the Hub Transport setup? it a brand new installation which hasn't been tinkered with but I don't have any other 2013 to compare it with.

Thank you
0
 

Author Comment

by:TopCat-007
ID: 40631404
My internal & external domain name are the same, that wouldn't have a bearing on this would it?  I'm close to rebuilding this troublesome box.  

I.e. Xyz.com is the public email domain and the internal windows 2012 domain is also Xyz.com - I was under the impression using Xyz.local internally was bad practice nowerdays.

Thanks again
0
 
LVL 14

Expert Comment

by:Andy M
ID: 40635375
You are correct with the domain - using .local and .lan are not considered good practice as you can't purchase ssl certificates for them these days.

One thing to check is dns - if you have an internal dns server ensure you have relevant records for the external addresses but pointing to the internal IP's. For example if your external server address is mail.xyz.com pointing to 81.12.13.14 create an internal record for mail.xyz.com pointing to 10.0.0.1 (or whatever your server internal address is). This is usually known as split-brain dns and you may need to add other external records to it for some features to be accessible (i..e websites - create a record for www to point to the web hosting address).

Regarding the email issues I would also consider running a best practice analyzer if not already done so and there is a powershell command to test mail flow: (http://exchangeserverpro.com/exchange-2013-test-mail-flow/) - these can indicate if there's any issues with the setup.
0
 

Accepted Solution

by:
TopCat-007 earned 0 total points
ID: 40785034
this problem wasn't resolved, the server was rebuilt and the problems vanished
0
 

Author Closing Comment

by:TopCat-007
ID: 40793676
I believe a corrupt Exchange installation was the root cause of the problems - a re-install resolved all the issues
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

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

The following article is comprised of the pearls we have garnered deploying virtualization solutions since Virtual Server 2005 and subsequent 2008 RTM+ Hyper-V in standalone and clustered environments.
Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

752 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