Exchange 2013 - Email Stuck in Draft

I have recently installed exchange 2013 on a server and have yet to provide it with Send Connectors.

To ensure that everything is working correctly internally wise, I have send an email internally to another member of staff.

However the problem is that the email is stuck in draft and will not deliver, I have the exact same problem with an exchange 2013 server running on a vm where there are connectors but the connectors do not show in the queue.

According to other staff an update was done for CU 10 which may have caused this problem? Looking online i have tried adding alternative DNS servers to the ECP/Server Section which could apparently be a possible reason to why its not sending.

Summary:
2 Servers - Exchange 2013 (Server 2012 R2) 1 Running AVG and One Running Sophos AV.
LVL 1
LewisNetworking Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott CSenior EngineerCommented:
Try opening the draft and clicking on "Send" again.

I've seen this before where someone had a message in draft, they make a change to it, then save the change.

The issue comes from touching the draft and making it "dirty".  This term comes straight from a MS Outlook engineer.

When you hit "Send" you remove the "dirty" attribute.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
LewisNetworking Author Commented:
The Email just gets stuck in the Drafts. I have tried this but no success still ends up in draft.
Scott CSenior EngineerCommented:
I doubt CU10 is the cause of this.  Try a reboot of the server and make sure all of the Exchange services are started.
HariomExchange ExpertsCommented:
First telnet to your local exchange server and send e-mail using telnet and post the results.

http://exchangeserverpro.com/how-to-send-email-via-telnet/
LewisNetworking Author Commented:
This  did not resolve the problem however content provided was useful.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Servers

From novice to tech pro — start learning today.