Messages stuck in drafts: Exchange 2013 issue


Many organization are complaining that when they install Exchange 2013, The user are facing the issue . when the send the E mail it stuck into drafts. Really it is a painful situation for administrator. It is the issue of DNS settings . following are the steps :


  1. Open Exchange control Panel
  2. Go to servers .
  3. Check external and internal DNS settings.
  4. If it is All IP addresses , change it and specify manually both DNS address.
  5. Check host file Entries. Add FQDN and IP of Exchange server .
  6. restart Exchange Services.
  7. Here you bingo. 

Comments

Rob said…
Did not work. My exhcnage server has an address of 172.17.10.100 and i added that to it. Restarted the entire server and still email goes to the draft folder. All the receive connectors are there. This is a brand new install and testing. Nothing was altered prior to reading your article.
Rob said…
Found the issue. I added the Exchange Server IP to it's own HOST file as both FQDN and Friendly name. After that, all email delivered correctly.
LucVC said…
Hi Rob, I had the same issue and tried your hosts-solution and bingo. :-) Thanks.
Unknown said…
Rob, could you detail your solution?

Thank you.
Chris M. said…
Had the same issue, fixed it using Rob's recommendation. The problem was that the Exchange 2013 server was resolving its local hostname to an IPv6 IP. Putting the local IP in the hosts under c:\windows\system32\drivers\etc\hosts forces windows to use IPv4 to connect for routing locally and transport will then work.
Anonymous said…
Thank you so much Rob, your fix saved me from going insane...
Lakhan Sankaye said…
Basically more or less the issues are related to IP configuration only. either it is in DNS settings or host file entries.
Tung Tung said…
After i change the hosts files, i still ping the server in ipv6. Any advice?
Unknown said…
We have the same issue as Tung Tung, has anyone figured this out?
Flopper said…
I found several 'workarounds, but THIS one is the only one that worked, thank you so much!
Erik said…
Nope, no luck mail still get stuck in draft box and dont get send or received at all, I dear someone to solve this problem for me, it is a multy Tenancy exchange 2013 server.

Regards Erik
Danny said…
Robs HOST suggestion worked for me too.
Shoaib Nawaz said…
Wow.. Thank you so much Man.. finally my issue has been resolved. i spent weeks to find out the issue.
For Erik:
buddy i am also using Multi-Tenancy in Exchange 2013. Check your DNS setting in ecp under servers.
if you are using two NICs than external NIC DNS assign your ISP DNS or Google DNS. Internal DNS should be your DC.
My issue is different, i am not able to receive any external email but after include host entries with my Exchange IP. All emails are received.
Host entry like this.
FQDN: IP
webmail: IP
Anonymous said…
Thanks a lot it worked...
Anonymous said…
hello... me too got the same problem.. i tried your solution. it worked..
But i restarted the exchange server 2013 installed in windows server 2012. And again i tried to send a mail to one of my user, mail got stucked in draft. Then i checked the services and found that Mcrosoft Exchange Transport --services stopped automatically. After some tries service got started, then mail was sent to the user from draft. So if we reboot our PC, then we should always restart that service again and again ? Is there a solution to avoid this ? plz reply anyone plzzzzzzzz...............
Anonymous said…
This fixed my fresh install of exchange 2013 in a virtual environment with 1 other server, a DC, both server 2012 standard.

Thanks so much!

Anonymous said…
Worked for me too.

2 hours of rebuilding
send and receive connectors
security settings, dns etc and restating services.

added line to hosts file as per suggestion and instantly it worked.

you'd think it would work out of the box.
Anonymous said…
Worked for me too.

2 hours of rebuilding
send and receive connectors
security settings, dns etc and restating services.

added line to hosts file as per suggestion and instantly it worked.

you'd think it would work out of the box.
Anonymous said…
Thanks, Lakhan, fast simple fix. I'm so glad I came across your site early.
Unknown said…
Hi I still have an issue. Now the emails dont get stuck in the drafts folder. However, when I send an e-mail to a domain like hotmail.com it returns saying:

#554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain ##


In the list of accepted domains I only have the default one. Any ideas?

Thanks.
Unknown said…
It was a DNS issue. I was able to install it successfully. Thanks
Unknown said…
All I had to do was to follow the steps 1,2,3,4, and it worked.
Thank you very much.
George
Anonymous said…
GARRRR!!!! Thank you. Finally after adding name and ip to the local /etc/hosts file.... mail is started to go through.
Anonymous said…
I tried all of the above - no joy. THEN ... I noticed I was low on hard disk space!!! 780M free of 60GB. I increased this to 80GB (it is a VM) and everything started working again
Eyeman said…
I struggled with this and was just about to give up and pay MS for help when I noticed that the Web Management Service wasn't started and it through an error when I tried to start it manually.

I removed this feature and then re-added the Web Management Service back in. As soon as the service started, all the email stuck in queues was suddenly processed. Problem resolved.
Anonymous said…
RESOLVED - by increasing disk space.

It seems as though there is a disk space threshold where the transport service will quit picking up and delivering mail and it stays in the drafts folder.

I did not catch this earlier as the transport service stays running just doesn't pickup / deliver mail.

In my case, once the VM (test lab) dropped below 1GB free, all mail flow stopped.

Hope this helps,
Andre
Anonymous said…
Thanks. This worked perfectly. Changed my IP after having to set through hosts file. All of the steps you listed were exactly what I needed to get server back operational again.
Benudhar Sahoo said…
Adding host entry on the server solved the issue. The server was resolving the 2nd adapter's IP for some reason.
Anonymous said…
Fixed by Increasing Disk Size.
C drive of Exchange server was running low (1.1GB)
Increased to 5 GB and All emails started sending/receiving.
thank you.
Unknown said…
Adding host entry also fixed issue with Exchange 2016. Thank you!
eddyshaw9272711 said…
This site is really a walk-via for all the data you wanted about this and didn’t know who to ask. Glimpse right here, and you’ll positively discover it. online casinos
Anonymous said…
good evening,
i create in
the unique dns server domain controller 2012 datacenter
the reverse ip address of the unique exchange 2013 server in the zone reverse lookup
Immediately started all the message in drafts.

Popular posts from this blog

Top 7 Technical Support Best practices to ensure the positive customer experience

Application compatibility update for Windows 7- KB2791765