3
BUILD 8762 Issue - Multiple IP's
Question asked by Mark Brown - 1/1/2024 at 1:18 PM
Unanswered

I attempted to upgrade to BUILD 8762 (Latest).

The server started but couldn't get an external client to connect on any port. Web interface was down too. 

This server has multiple IP's bound to the mail ports and everything worked correctly with Build 8664.

After the upgrade I could only see the following errors:

21:10:18.961 imap started at 12/31/2023 9:10:18 PM

21:10:18.974 [x.x.x.150:143] Binding(2) Exception: System.Net.Sockets.SocketException (10048): Only one usage of each socket address (protocol/network address/port) is normally permitted.
   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, Boolean disconnectOnFailure, String callerName)
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at SmarterMail.Protocols.Common.PooledTcpServer.StartListening(IPEndPoint ipEndPoint, db_system_binding_port bindingPort)
21:10:18.975 [x.x.x.150:993] Binding(2) Exception: System.Net.Sockets.SocketException (10048): Only one usage of each socket address (protocol/network address/port) is normally permitted.
   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, Boolean disconnectOnFailure, String callerName)
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at SmarterMail.Protocols.Common.PooledTcpServer.StartListening(IPEndPoint ipEndPoint, db_system_binding_port bindingPort)
21:10:18.975 [x.x.x.196:143] Binding(2) Exception: System.Net.Sockets.SocketException (10048): Only one usage of each socket address (protocol/network address/port) is normally permitted.
   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, Boolean disconnectOnFailure, String callerName)
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at SmarterMail.Protocols.Common.PooledTcpServer.StartListening(IPEndPoint ipEndPoint, db_system_binding_port bindingPort)
21:10:18.976 [x.x.x.196:993] Binding(2) Exception: System.Net.Sockets.SocketException (10048): Only one usage of each socket address (protocol/network address/port) is normally permitted.
   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, Boolean disconnectOnFailure, String callerName)
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at SmarterMail.Protocols.Common.PooledTcpServer.StartListening(IPEndPoint ipEndPoint, db_system_binding_port bindingPort)
21:10:18.976 [x.x.x.106:143] Binding(2) Exception: System.Net.Sockets.SocketException (10048): Only one usage of each socket address (protocol/network address/port) is normally permitted.
   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, Boolean disconnectOnFailure, String callerName)
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at SmarterMail.Protocols.Common.PooledTcpServer.StartListening(IPEndPoint ipEndPoint, db_system_binding_port bindingPort)
21:10:18.977 [x.x.x.x:993] Binding(2) Exception: System.Net.Sockets.SocketException (10048): Only one usage of each socket address (protocol/network address/port) is normally permitted.
   at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, Boolean disconnectOnFailure, String callerName)
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at SmarterMail.Protocols.Common.PooledTcpServer.StartListening(IPEndPoint ipEndPoint, db_system_binding_port bindingPort)

~~~
I have since reverted to Build 8664 and everything works correctly.





2 Replies

Reply to Thread
0
Employee Replied
Employee Post
Hi Mark, 

I'm sorry to hear that you had trouble upgrading to Build 8762. I'm going to start a support ticket with you so we can look into this with you. 

Kind regards,
0
Millennium Systems Replied
Haven't upgraded to the latest build, but have a feeling we might have an issue with this as well. We have Binding/Port settings on some IPs that originated years ago on SM 4.x or 5.x and now are apparently no longer valid (aka the box is red and we can't save any changes), but this hasn't prevented protocols from working up until now.

How would making the 'proper' changes effect end users? At the moment we have double check marks on ports 25/110/143 (one with and without TLS). Leaning towards just leaving the TLS selections checked but how will this affect users connecting via clients without the SSL/TLS option enabled in their settings? Would they fall back on using TLS?

Either way, we potentially have a few 1000 end users that might break if POP (110) or POP TLS (110) is uncheck on a particular IP.

Reply to Thread