Zero inbound mail movement. Windows Updates (4/4/24), had to restart server.

Question asked by Curtis Kropar www.HawaiianHope.org - 4/4/2024 at 3:48 PM

Unanswered

Has anyone else experienced this in the past 24 hours or so ? (4/4/24)

Yesterday I noticed that I was not getting as much email as normal. Today, I realized I did not get a single email. Then a client of ours called in and reported the same, no email inbound.

I logged in to the server and SM reports were showing zero inbound emails across 200 accounts. However, everything else looked normal with SmarterMail.

What I did notice though was that Windows Updates were insisting that an update needed to restart the server (2022) SO I restarted the server (and our exterior firewall as well, just in case) and email started flowing again. Is this normal that a windows update waiting, would cause SM to stop processing email ? Has anyone else seen this ? Or am i seeing correlation, and not causation ?

www.HawaiianHope.org - Providing technology services to non profit organizations, low income families, homeless shelters, clean and sober houses and prisoner reentry programs. Since 2015, We have refurbished over 11,000 Computers !

7 Replies

Reply to Thread

Brian Replied

4/4/2024 at 4:46 PM

Sometimes it happens. I usually restart the server immediately after an update.

Curtis Kropar www.HawaiianHope.org Replied

4/4/2024 at 5:13 PM

Same here, But I was not aware an update was out there waiting...

Webio Replied

4/6/2024 at 9:42 PM

Does SMTP logs from that day contains any exceptions?

Jay Dubb Replied

4/8/2024 at 6:23 AM

May have something to do with the new version being on .NET Core. I haven't seen in the past where SM stops working when Windows Updates are applied and waiting for a reboot.

We HAVE noticed that in certain cases, our Exchange Server stops passing traffic while an update is being installed, but it usually returns to service once the install is finished (even though it is still waiting for a reboot).

Webio Replied

4/8/2024 at 8:20 AM

I'm asking because I've experienced problem in february and november (when I was testing . NET core version as gateways only) and both of them had errors like this:

09:25:53.235 [IPADDRESSOFGATEWAY:25] Binding Exception: System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Net.Sockets.Socket>.GetResult(Int16 token)
at SmarterMail.Protocols.Common.PooledTcpServer.StartListening(IPEndPoint ipEndPoint, db_system_binding_port bindingPort)

08:28:25.628 [IPADDRESSOFGATEWAY2:25] Binding Exception: System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Net.Sockets.Socket>.GetResult(Int16 token)
at SmarterMail.Protocols.Common.PooledTcpServer.StartListening(IPEndPoint ipEndPoint, db_system_binding_port bindingPort)

00:41:29.680 [IPADDRESSOFGATEWAY3:25] Binding Exception: System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Net.Sockets.Socket>.GetResult(Int16 token)
at SmarterMail.Protocols.Common.PooledTcpServer.StartListening(IPEndPoint ipEndPoint, db_system_binding_port bindingPort)

Only thing which helped in both occurences was to return to .NET Framework latest build. Since february issue I keep 2 of my gateways on .NET Framework and one on .NET Core version and try to replicate this two issues which occured in past. Gateways (all three of them) stopped to receive new messages on the same day - there was only few hour differences. This might be related to gateways being updated on the same day but on different hours.

Error is telling about binding exception but for sure there was no other software running on this port and especially that all incoming gateways where affected.

Matt Petty Replied

4/8/2024 at 9:39 AM

Employee Post

"An existing connection was forcibly closed by the remote host." is pretty normal. Just means they disconnected from us, you'll see this in all versions

Matt Petty

Senior Software Developer

SmarterTools Inc.

www.smartertools.com

Brian Replied

4/10/2024 at 9:38 AM

For what its worth... latest servicepacks waiting to install rendered all our RRAS servers unusable due to waitning updates. Install and restart and the RRAS came back no issues....

Nothing we could do made the VPN's connect.

Back to Community Threads

Reply to Thread

Enter the verification text