Solved

Exchange 2013 - message not being delivered to the inbox internally

Posted on 2015-02-24
9
18 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
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 

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

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

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

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

623 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