Connection timed out-mail not delivering (build 8768)

Problem reported by Brian Kropf - 1/6/2024 at 9:19 PM

Resolved

I just upgraded to build 8768 and now no incoming emails are being delivered. We use SpamHero for our spam filtering and since the upgrade, all emails from external domains are timing out instead of delivering.

Does anyone know what I'm missing?

7 Replies

Reply to Thread

Manuel Martins Replied

1/7/2024 at 11:31 AM

Hy Brian

I think it's because of the rule SM introduced in Build 8747, all comunications should use TLS or SSL probably you must reconfigure the way SpamHero delivers mail to your Server, you must use a Certificate on the Server an TLS to comunicate with the Server.

Build 8747 (Dec 13, 2023)

IMPORTANT: All secure port bindings must be configured to use a certificate file that includes the private key. Bindings that don’t contain a private key will not function as expected and will show an “Invalid certificate” warning.

Patrick Jeski Replied

1/7/2024 at 12:43 PM

Manuel, I think that note means you have to use a .pfx with the private key now as opposed to a base64 .cer file which is what I had been using. (The private key was in the certificate store). I don’t think it implies you must use tls/ssl.

Brian Kropf Replied

1/7/2024 at 2:56 PM

Thanks for the replies... we've been using .pfx cert files for years so I didn't expect that to be the issue. I ended up downgrading to build 8664 late last night and thought everything was back to normal.

But then this morning I discovered that my server stopped receiving mail around 4:00 am. I've been fighting it ever since and find it very strange because I'm back on my previous build but fighting the "Connection timed out" issue that I did not have before.

Ron Raley Replied

1/7/2024 at 3:19 PM

This begs the question. Can the new .Net 8 version be downgraded without repercussions?

It seems not so much.

Brian Kropf Replied

1/7/2024 at 5:22 PM

Ron, your comment and a suggestion from a colleague sent me looking at the Windows Event viewer. ASP.NET 4.0 is throwing a bunch of errors.

Now I'm wondering if I need to reinstall/repair ASP.NET 4.0 because I downgraded to build 8664.

Event code: 3005

Event message: An unhandled exception has occurred.

Event time: 1/7/2024 5:53:02 PM

Event time (UTC): 1/7/2024 11:53:02 PM

Event ID: 11d190bbb2ce4b6fabb82c77c0fd013b

Event sequence: 162928

Event occurrence: 648

Event detail code: 0

Application information:

Application domain: /LM/W3SVC/1/ROOT-1-133491380113028947

Trust level: Full

Application Virtual Path: /

Application Path: C:\Program Files (x86)\SmarterTools\SmarterMail\MRS\

Machine name: CTG-SMARTERMAIL

Process information:

Process ID: 5108

Process name: w3wp.exe

Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:

Exception type: CommunicationObjectFaultedException

Exception message: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

Server stack trace:

at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposedOrNotOpen()

at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)

at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

at SmarterMail.Interface.Authentication.IAuthenticationService.Login(AuthenticateUserInputs inputs, ProtocolTypes type, String visitorIpAddress, String hostname, Boolean logLoginAttempt, Boolean recordLogin, Boolean impersonationLogin, Boolean& isLoginCached, Boolean returnDomainAlias, Boolean alwaysLogLoginAttemptsFromOurApi, AppPasswordProtocols appPasswordProtocols, Boolean recordIPAuth)

at SmarterMail.Web.SyncProtocols.EAS.EasHelperFunctions.InternalLogin(String username, String password, Boolean logLoginAttempt, AuthenticateUserResult& result)

at SmarterMail.Web.SyncProtocols.EAS.EasHelperFunctions.HandleBasicAuth(String authHeader, UserData& user)

at SmarterMail.Web.SyncProtocols.EAS.EasHelperFunctions.Authenticate(HttpContext context)

at SmarterMail.Web.SyncProtocols.EAS.ActiveSyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)

at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)

at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Request information:

Request URL: https://mail.MYDOMAIN.com:443/Microsoft-Server-ActiveSync 

Request path: /Microsoft-Server-ActiveSync

User host address: 175.175.175.175 {Falsified IP}

User:

Is authenticated: False

Authentication Type:

Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:

Thread ID: 267

Thread account name: NT AUTHORITY\NETWORK SERVICE

Is impersonating: False

Stack trace: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)