Hi Haris,

Any updates?

Please also make sure all Exchange services are running.

If you have any feedback on our support, please click here

same happens here - but only if the users have an 2nd-mailbox attached.

users working with outlook 2010 - os+office FULLY patched!

if i remove the 2nd-mailbox from the account & re-add it, everything is working OK!

all exchange-services are running!

Hi Haris,

Any updates?

I am also having this issue.

server 2012 VM with exchange 2013. plenty of resources, more than recommended so cannot be a BAck Pressure issue especially as no clients are connected yet.

In the early stages of setup and testing, mail sent to other mailboxes worked fine in outlook 2007 and OWA but after a few issue that developed and are now resolved, any e-mail send within outlook or OWA just goes straight into the drafts folder.

I tried, DNS setting changes under roles, on the server, on DNS server, MX DNS records, increased resources, looked at received connectors, changed and even deleted send connectors as this is not required for internal mail. Tried changing authentication types but then outlook won't connect to, staying with Basic Auth.

Have not been able to test inbound e-mail as this is going to replace a production server and is not ready, although I could probably simulate a route from another server and push e-mail to it. Will try tomorrow.

I have spent about 20 hours trying to figure this out and made probably 40 changes. Change, test, rollback etc. Been searching through loads of forums and technet sites all with no help.

All services are started, server has been rebooted several times.

It is also an AD server and has both Exchange roles installed. There is no reason why it should not work. This is so frustrating, we don't have these issues with the now end of life Scalix, or MDaemon or Zimbra. Pity the client wanted a Microsoft solution. To be honest there are not a lot of things that cannot be changed in ECP although there is more under exchange powershell however I am not familiar with all the commands yet. I have resorted to watching training videos even though I am a seasoned IT Pro, although not so much with exchange it seems.

I have seen many people have this issue on Exchange 2007, 2010 and 2013. Someone must know how to resolve this or find a work around?

So far I have an expensive solution the client has purchased that I cannot get running properly.

Aside from this issue, I really like the new Server 2012 and new Hyper-V.

I am also having this issue.

server 2012 VM with exchange 2013. plenty of resources, more than recommended so cannot be a BAck Pressure issue especially as no clients are connected yet.

In the early stages of setup and testing, mail sent to other mailboxes worked fine in outlook 2007 and OWA but after a few issue that developed and are now resolved, any e-mail send within outlook or OWA just goes straight into the drafts folder.

I tried, DNS setting changes under roles, on the server, on DNS server, MX DNS records, increased resources, looked at received connectors, changed and even deleted send connectors as this is not required for internal mail. Tried changing authentication types but then outlook won't connect to, staying with Basic Auth.

Have not been able to test inbound e-mail as this is going to replace a production server and is not ready, although I could probably simulate a route from another server and push e-mail to it. Will try tomorrow.

I have spent about 20 hours trying to figure this out and made probably 40 changes. Change, test, rollback etc. Been searching through loads of forums and technet sites all with no help.

All services are started, server has been rebooted several times.

It is also an AD server and has both Exchange roles installed. There is no reason why it should not work. This is so frustrating, we don't have these issues with the now end of life Scalix, or MDaemon or Zimbra. Pity the client wanted a Microsoft solution. To be honest there are not a lot of things that cannot be changed in ECP although there is more under exchange powershell however I am not familiar with all the commands yet. I have resorted to watching training videos even though I am a seasoned IT Pro, although not so much with exchange it seems.

I have seen many people have this issue on Exchange 2007, 2010 and 2013. Someone must know how to resolve this or find a work around?

So far I have an expensive solution the client has purchased that I cannot get running properly.

Aside from this issue, I really like the new Server 2012 and new Hyper-V.

I was about to install Exchange Server 2013 on a physical machine due to this f#ckin' issue. But a post for the DNS change has saved my life:

http://social.technet.microsoft.com/Forums/en-US/exchangeserverpreview/thread/04c0147b-f4e3-4041-a566-310854e71068/ (rafael9908's answer)

And thanks Jesper Bernle for excellent info provided by your link.

Hi ,

I didn't found the link copied over here (http://social.technet.microsoft.com/Forums/en-US/exchangeserverpreview/thread/04c0147b-f4e3-4041-a566-310854e71068/ )

and followed all  link in this replay but no lock , if any one resolved and other suggestion are most welcome .

Hi Frank Wang ,

Could you please let me know if any solution you knows about this problem.

Hi Satya11,

I also have this issue with the stucked emails to the draft folder.

This link seems broken. ( http://social.technet.microsoft.com/Forums/en-US/exchangeserverpreview/thread/04c0147b-f4e3-4041-a566-310854e71068/ )

Have you found any solution?

Ps. I have tried to open the link by rafael9908's profile (http://social.technet.microsoft.com/search/en-us/?query=rafael9908#refinementChanges=&pageNumber=2&showMore=false) but still not working.

• Proposed as answer by Dimitris_V Exchange 2013 Admin Monday, December 09, 2013 2:41 PM
• Unproposed as answer by Dimitris_V Exchange 2013 Admin Monday, December 09, 2013 2:41 PM

The complete solution for me is in the link below:

http://community.spiceworks.com/topic/309145-exchange-2013-messages-stuck-in-drafts

• Proposed as answer by FaberX1 Friday, December 13, 2013 10:17 PM

Just thought I'd add this... If the hubtransport service is in maintenance mode, messages will be stuck in draft.

http://michaelvh.wordpress.com/tag/maintenance-mode/

I just had the same problem, you just need to configure the DNS server settings under the Server properties in ECP, heres the link:-

http://thoughtsofanidlemind.com/2013/03/25/exchange-2013-dns-stuck-messages/

As I had a physical server (DC), I could utilise the same licence on hyper-v. Having the same problem I just made sure the DNS was pointing to my physical server IP.

I had a similar issue and none of the recommended solutions worked: DNS, receive connectors, SCP, etc. In the end it was a default domain policy which was applied to the OU in which the exchange 2013 server was located.

Solution: http://exchangekb.com/2014/03/19/exchange-2013-emails-stuck-in-drafts/

Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment enable who can access this computer over the network select 

Administrators
Backup Operators
Users 
Everyone 

and all ok now

• Edited by SavvyXeus Tuesday, March 25, 2014 3:41 PM

Exchange 2013 issues - (new send email Stuck in Drafts folder not send)

• Proposed as answer by JayceRhodes Friday, April 04, 2014 8:21 AM
• Unproposed as answer by JayceRhodes Friday, April 04, 2014 8:21 AM
• Edited by JayceRhodes Friday, April 04, 2014 8:22 AM

In owa, i also had this problem.

After I manually selected my local DNS in the DNS lookups in 'servers' menu and restarted the exchange server it worked. Of course the exchange it's joined to the local domain and has the latest updates.

I think this solved the problem even if meanwhile I added other certificates issued by the local AD CS.

If this is after a new install or update, exchange might still be inactive

https://gallery.technet.microsoft.com/exchange/SetExchangeComponentToActiv-874bcd4b

-Brad

• Proposed as answer by Lonnie Thibodeaux Sunday, November 23, 2014 9:08 PM
• Unproposed as answer by Lonnie Thibodeaux Sunday, November 23, 2014 9:08 PM

Well,

as the linked solution perfectly states: Never delete or modify the default receive connectors. This has been true with previous versions of Exchange as well.

The only change that I apply in customer scenarios is the modification of the remote IP address ranges. But such a change might require Manual changes when you add a new Exchange Server into your infrastructure.

Well,

as the linked solution perfectly states: Never delete or modify the default receive connectors. This has been true with previous versions of Exchange as well.

The only change that I apply in customer scenarios is the modification of the remote IP address ranges. But such a change might require Manual changes when you add a new Exchange Server into your infrastructure.