Excahnge 2013 not sending emails

I have a exchange 2013 server that has been running for at least 3 months with no problems. All of a sudden today the server will not send emails externally. I can send emails to internal users without any issues. The server will just not send externally.
joshrosenAsked:
Who is Participating?
 
I QasmiTechnical LeadCommented:
check your send connector configuration
Also do check whether you have low disk space
Exchange folders have been added to the exclusion list or not.
check the event viewer for any warning or error event
0
 
joshrosenAuthor Commented:
This is the error in event viewaer that I am getting.

RpcHttp] Marking ClientAccess 2010 server GCEXCHANGE-01.gccorp.local as unhealthy due to exception: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.HttpProxy.BackEndHealthManager.TestServer(String fqdn)
0
 
NiceCuppaTeaCommented:
Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

Looks like you have problems somewhere with the external relay you are using.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
172pilotSteveCommented:
Sounds like you're on a blacklist, and the remote hosts are disconnecting from you before you can send mail...
Check   http://www.mxtoolbox.com/blacklists.aspx

it will see if your outbound IP addresss is on any blacklists.
0
 
joshrosenAuthor Commented:
Checked all blacklist sites and my Ip address is not listed on any of them.
0
 
172pilotSteveCommented:
What roles are on this server?   Is it your only Exchange server?  Have you tried to reboot it, or at least restart the Exchange services?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.