Exchange 2013: Messages Stuck In Drafts
Recently while helping on technet I identified this issue which is very rarely seen so I thought of sharing it here.
Issue:
All outbound email messages are getting stuck in the Drafts Folder.
Cause:
Permission change on the following GPO for the object – “Access this computer from the network”.
“Default domain policy” –>Local Policies –> User Right Assigments
to only domainAdministrator user and domainDomain Users group on both GPO.
Resolution:
-Checked – no changes on the receive connectors
-Checked – Exchange verbs were normal as below:
250-EXCHANGE2K13.XXXXXXXXXXXXX Hello [x.x.x.x]
250-SIZE 37748736
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-X-ANONYMOUSTLS
250-AUTH NTLM
250-X-EXPS GSSAPI NTLM
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 XRDST
-Checked – Transport Agent
–Changed the Permission on the following GPO for the object – “Access this computer from the network”.
“Default domain policy” –>Local Policies –> User Right Assigments
- Administrators
- Backup Operators
- Power Users
- Users
- Everyone
“Default Domain Controller Policy”–>Local Policies –> User Right Assigments:
- Administrators
- Authenticated Users
- Everyone
-Then ran GPupdate /force on domain Controllers and Exchange servers
-Restarted Microsoft Exchange Transport Service.
Reference:
http://technet.microsoft.com/en-us/library/cc740196(WS.10).aspx
http://social.technet.microsoft.com/Forums/exchange/en-US/b7f0bc4e-2237-4e99-bc7f-128e87f76250/exchange-2013-cu2v2-messages-stuck-in-drafts-folder
MSExchangeGuru team is thankful of Luca Urbinati for sharing the root cause and resolution.
Prabhat Nigam
Microsoft MVP | Exchange Server
Team @MSExchangeGuru
July 22nd, 2014 at 9:00 am
Sir,
I’m stuck since last week with this problem and I tried all the proposed solutions on the internet (dns changes, updating GPO as per your article) but still cannot at least send e-mails internally between users.
Would you please advise where to look and how to continue troubleshooting as we need to publish this exchange online before first of august.
Thank you,
Regards,
July 28th, 2014 at 12:57 am
@Maroon
This is one of the cause. So we need to see the error in queue viewer or in the get-queue output.
You might have submission service stopped.