asked on

Exchange 2013 - message not being delivered to the inbox internally

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

Andy M

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.

TopCat-007

ASKER

Thanks Andy, i'm installing CU7 as I type

Muhammad Mulla

I would also check to see how the Hub transport connectors are setup.

TopCat-007

ASKER

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!

TopCat-007

ASKER

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

TopCat-007

ASKER

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

Andy M

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.

ASKER CERTIFIED SOLUTION

TopCat-007

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

TopCat-007

ASKER

I believe a corrupt Exchange installation was the root cause of the problems - a re-install resolved all the issues