Internal emails are not delivered but they are shown in the Sent Mail

hi,

I'm not enjoying Exch2013, the lack of a "proper" admin console is a pain and I'm having trouble getting the required diagnostic/tracking information out of PShell to fix my problem.

I've installed Exch2013 RC1 on a new 2012r2 Domain, the install went OK and there were no obvious issues however internal email's wouldn't deliver, they appear in Sent Items but aren't received in the internal rcpt's inbox.

while trying to fix the problem, I installed ExchCU7 and bingo everything sprang to life and mail was working, inbound/outbound & internally - so I assumed the service pack/update had fixed it but the next day I rebooted the server and to my horror, I'm back where I started - no mail flow.

One single test message which I sent outbound using the Web mail, rather than Outlook did arrive but hours after I sent it?  confused.com

this is running on a HV-2012r2 as a VM, with a dedicated Nic and plenty of Fixed VD storage.

Any help/advice would be greatly appreciated.

I'm very close to removing Exch2013 and re-installing but I worry this would cause more issues.

Thanks Iain

February 25th, 2015 4:24pm

Hi icb,

Thank you for your question.

Did you send email to intranet with latency by OWA?

Are there any error when we open OWA?

We could refer to the following steps to troubleshooting:

1. Telnet Exchange

we could use telnet <FQDN of Exchange> 25 on clientto check if we could test port 25 on Exchange.

2. Using the following command the check if the email is in the queue. Get-Queue -Server Mailbox01 -Exclude Empty

If email which we send was in the queue, we could collect message trace log  by the following command and send to ibsexc@microsoft.com for our troubleshooting

Get-MessageTrackingLog -ResultSize Unlimited -Start "2/26/2015 8:00AM" -End "2/26/2015 9:00AM" -EventId "Fail" -Sender "User@contoso.com"     

3. We could restart the service of Microsoft Exchange Transport.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Free Windows Admin Tool Kit Click here and download it now
February 26th, 2015 1:22am

Hi ,

In addition jim suggestions , please have a look in to the below mentioned points.

1.What is the last error message shown on the queue viewer ?

2.Did you have enough space on the disk where the queue database resides ?

3.Moreover analyzing the headers of the delayed message will tell us on which hop the message is been delayed and also message tracking will tell us what has happened to that message ?

4.test-servicehealth is the command which needs to be executed on the exchange servers to check all the exchange services are up and running.

5.Then tell me how many exchange 2013 servers and AD sites did you have in your environment ?

February 26th, 2015 1:40am

this server is the first and only Exchange server in a single site/AD enviroment. 

Doamin and Exch are both brand new, with one DC and Exch runing on a member server.

This server isn't recieving inbound mail yet, however the SMTP port is availible.

Am I correct in thinking that internal mail from one mailbox to another doesn't require SMTP, instead the msgs are transmitted within the HUB.  I'd like to stress that the isntallation of ExchCU7 instantly fixed all the mail flow problems, then a day later and after a reboot it reverted to back to its current state.

test-servicehealth shows:


Role                    : Mailbox Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeDelivery, MSExchangeIS,
                          MSExchangeMailboxAssistants, MSExchangeRepl, MSExchangeRPC, MSExchangeServiceHost,
                          MSExchangeSubmission, MSExchangeThrottling, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning      : {}

Role                    : Client Access Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeMailboxReplication, MSExchangeRPC,
                          MSExchangeServiceHost, W3Svc, WinRM}
ServicesNotRunning      : {}

Role                    : Unified Messaging Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeServiceHost, MSExchangeUM, W3Svc, WinRM}
ServicesNotRunning      : {}

Role                    : Hub Transport Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeEdgeSync, MSExchangeServiceHost,
                          MSExchangeTransport, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning      : {}

I'm looking at the q's now but wanted to post this asap... i will update this thread again shortly

thanks for your help.

Free Windows Admin Tool Kit Click here and download it now
February 26th, 2015 4:39am

FYI - this Exchange server isn't actaully online properly just yet, we're replacing a 2003 and Exch 2007 by installing a fresh new domain.

At the moment mail.compnay.com is still routing to the previous server, I have not updated the FQDN options in Exchange 2013 yet, so its internal DNS names are functioning.

The Q error for an outbound SMTP mail is 400 4.4.7 Message delayed.

I temporarlly half disabled IP6 (by un-ticking IP6 on the network adaptor) the clients could connect to exchange at all.

OWA and ECP sites are working perfectly and there's plenty of disk space.

it made no difference but I've created a new database and moved a test user to it.


a manual telnet to 25 results in "451 4.7.0 Temporary server error. Please try again later. PRX2"
  • Edited by I-C-B 19 minutes ago
February 26th, 2015 6:26am

Hi ,

Please tell me the messages which is queued up in exchange are all to the external domains ? If so then you need to check your exchange can able to reach the smart host over port no 25 for sending emails to internet.

In case if your exchange server is directly sending the emails to internet then you need to check that your exchange server can able to resolve the external domains and also it should have to communicate with the mail servers on the external world by using port no 25.

Note : You can make use of the telnet commands for the above scenario's to check the communication between your exchange server and internet and also between your exchange server to smart host if you have it on your network.

Note : Message delayed error will occur on the queue viewer only if we don't have the proper route in the exchange server to destination domains

Free Windows Admin Tool Kit Click here and download it now
February 26th, 2015 6:45am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics