Hi all,

I have started encountering this issue with "emails stuck in outbox", while setting up a new exchange 2013 server in my exchange 2007 enviornment. I have moved a couple of test accounts to Exchange 2013.

When clients try to send emails they get stuck in the outbox with no errors either in, outlook, the client computer, or on the exchange server.

It happens for all clients that are inside the network, or using OWA the emails get stuck in drafts. The same users connecting from out on the intenet via rpc over http are ok. i.e, if I run outlook 2010 from a 2012 Terminal server inside the network I get the issue. If I start outlook 2013 and use rpc over https it seems ok.

Our domain uses company.local internally, but I have changed all URL's to use the external uri of "company.com" and have a public cert on all these services that match.

the clients that have the isuse do not open any other email accounts, and I have tried specifying DNS servers in the DNS settings for the new 2013 server.

As there are no error messages I have no idea how to start fault finding this.

Any ideas anyone?

This is pretty common even on new Exchange installations. Usually, when you restart Transport services on MBX servers, mail flow will start to work. Manually setting up DNS,  can also help in some cases, but you already tried this.
Try also to add this line:
<add key= "DnsIpv6Enabled"  value = "false />
to the following configuration files located in the BIN folder:Edgetransport.exe.config, Msexchagnesubmission.exe.config, MSExchangedelivery.exe.config

Just add the entry for the MSExchangeSubmission.exe.config and MSExchangeDelivery.exe.config.   The EdgeTransport.exe.config  has the entry but it is sent to true.    Then restart  MSExchange Transport, Submission and Delivery services and see if the messages go out.

Thanks for the reply Damird, I will try some of these settings tomorrow. I have changed some of the DNS settings without luck, but not all you suggested.

Do you know if there is anyway to enable logging what is going on here with the transport? and exactly what services are involved in moving moving emails out of outbox/drafts?

I'd like to be able to get to the bottom of the issue.

Cheers

After making these changes MSExchange Transport, Submission and Delivery services cannot start at all

any other suggestions?

All outlook client uses rpc over https for exchange 2013 because mapi does not work in Exchange 2013

revert the previous step

mark this forum unresolved so that others can also have a look. I just open this post to see the resolution and most of the techs will not be opening it thinking it has been answered.

-Did you change any receive connector setting.

Check if these blogs helps -

http://msexchangeguru.com/2013/09/03/e2013stuckindrafts/

http://msexchangeguru.com/2013/08/03/e2013-2010mailflowissue/

 http://msexchangeguru.com/2013/07/29/troubleshooting-mail-flow-issues/

If you have IPv6 enabled then try to disable it using registry. You will have to restart the server.

The key is a 32 bit dword key named DisabledComponents value should be fffffff

these are 8 Fs

Search for Disabledcomponents on bing and you will find the location in the registry.

Microsoft does not recommend to disable it but if it helps then keep it disabled else revert the change

I just wanted to add my HUGE thanks for this reply.  I have a new Exchange 2013 implementation (to replace a 2007 box) in a VM, and the DNS is hosted on the Hyper-V that hosts it, so single Exchange, single DNS model.  This drafts issue has been plaguing me since I installed it - it's really only noticeable when I use OWA when I'm away from the LAN, or using Touchdown etc. as a client.  I researched this loads on the 'net, and most of the answers talk about making DNS changes (which I've done:  didn't work) or installing a second Exchange server (overkill, that seriously cannot be the solution!).  I even disabled IPv6 on the network adaptor and it didn't work.  So thanks to the info here, it's finally working.  So what I did was (within the ECP):

1. On each of the receive connectors (Mail Flow, Receive Connectors, Scoping) ensured only the IPv4 address I was using was specified)
2. Servers, [server name], DNS Lookups, External DNS Lookups:  made sure the adaptor was specified (rather than "all adaptors" which is the default), and specified the IPv4 address of my DNS server.  Repeat for Internal DNS Lookups
3. I removed all IPv6 scope and references as I made the above changes, just in case
4. Applied the config changes as detailed above i.e. disable DNS IPv6 from the three config files (Edgetransport.exe.config, MSExchangesubmission.exe.config and MSExchangedelivery.exe.config) and I rebooted.  I noticed that certain services either didn't start (or maybe I wasn't patient enough) so I made sure that the Win2k12 server showed all services started.
5. Tested, and - FINALLY - it works.

Thanks once again for those config file changes - for me, personally, it took ALL the steps I found on the internet being added together to finally get my solution.  If this helps anyone at all, you're welcome because I think I've lost more hair than is healthy trying to fix this over the past week....

I fought this for a while before figuring out it was an IPv6 problem. Did not like the idea of disabling Ipv6 altogether in case it was needed in certain situations.

Ran a microsoft fix on all clients found at

https://support.microsoft.com/kb/929852?wa=wsignin1.0

to grant preference to IPv4 over IPv6. Fully resolved the problem.

HI

I am facing similar issue in my organization, but it only in outlook 2010.

Emails remain in outbox and same time new emails not appears into outlook.

once reopen outlook, issue solved.

But its create problem for users.

Let me know if any have solution.

Reg

Aditya