Back to Community Threads
1
Services not binding after reboot SM Pro 15.7 System.Net.Sockets.SocketException
Problem reported by Ian Ralph - 3/16/2025 at 5:08 AM
Submitted
Running Smartermail Pro 15.7 and everything works fine normally, SMTP, IMAP, POP etc however if we reboot the machine, then none of the services start properly, looks like they are not binding correctly. Manually stopping and restarting each service in the web interface under Manage / Services fixes the issue. 

SMTP log shows this after the reboot.

01:55:08 smtp stopped at 16/03/2025 01:55:08
01:57:06 smtp started at 16/03/2025 01:57:06
01:57:06 System.Net.Sockets.SocketException (0x80004005): The requested address is not valid in its context
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at MailService.TcpServerLib.Common.PooledTcpServer.#I5(IPEndPoint #L8i)
01:57:06 System.Net.Sockets.SocketException (0x80004005): The requested address is not valid in its context
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at MailService.TcpServerLib.Common.PooledTcpServer.#I5(IPEndPoint #L8i)
01:57:06 System.Net.Sockets.SocketException (0x80004005): The requested address is not valid in its context
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at MailService.TcpServerLib.Common.PooledTcpServer.#I5(IPEndPoint #L8i)
01:57:06 System.Net.Sockets.SocketException (0x80004005): The requested address is not valid in its context
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at MailService.TcpServerLib.Common.PooledTcpServer.#I5(IPEndPoint #L8i)

Same for POP and IMAP

POP

01:57:06 System.Net.Sockets.SocketException (0x80004005): The requested address is not valid in its context
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at MailService.TcpServerLib.Common.PooledTcpServer.#I5(IPEndPoint #L8i)
01:57:06 System.Net.Sockets.SocketException (0x80004005): The requested address is not valid in its context
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at MailService.TcpServerLib.Common.PooledTcpServer.#I5(IPEndPoint #L8i)

IMAP

01:55:08 imap stopped at 16/03/2025 01:55:08
01:57:06 imap started at 16/03/2025 01:57:06
01:57:06 System.Net.Sockets.SocketException (0x80004005): The requested address is not valid in its context
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at MailService.TcpServerLib.Common.PooledTcpServer.#I5(IPEndPoint #L8i)
01:57:06 System.Net.Sockets.SocketException (0x80004005): The requested address is not valid in its context
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at MailService.TcpServerLib.Common.PooledTcpServer.#I5(IPEndPoint #L8i)

4 Replies

Reply to Thread
0
Ian Ralph Replied
3/16/2025 at 5:19 AM
Just to add, we have SMTP bound to two IP addresses 127.0.0.1 and one other IP xx.xx.xx.xx. The SMTP service DOES start and run on the local IP address but as mentioned above, not on the other IP addresses ( along with IMAP and POP )
1
Kyle Kerst Replied
3/17/2025 at 7:42 AM
Employee Post
I'm not sure why this works, but I've seen this work in the past in older environments. Try adjusting the SmarterMail system service properties to do a delayed start instead of starting up with Windows. It'll add 30 seconds to a minute of boot time but I bet it'll resolve this restart issue you're having!
Kyle Kerst Acting IT Manager SmarterTools Inc. www.smartertools.com
1
J. LaDow Replied
3/17/2025 at 2:55 PM
We've had Kyle's solution make a huge difference on some services that require the network interfaces be up and connected before they can start.
MailEnable survivor / convert --
3
Douglas Foster Replied
3/17/2025 at 4:57 PM
Here is one reason why it works:
My data is on an iscsi drive.  Delayed start ensures that the iscsi disks are visible before the service starts and tries to use them.
Back to Community Threads

Reply to Thread

Enter the verification text

Related Knowledge Base Articles

Deploying Rspamd For Use With SmarterMailSmarterMail > Server Configuration and Management
System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:17001SmarterMail > Troubleshooting
Set up SmarterMail as an IIS Site (IIS 7.0/7.5)SmarterMail > Server Configuration and Management
Set up SmarterMail as an IIS Site in IIS 10SmarterMail > Server Configuration and Management
Set up SmarterMail as an IIS Site in IIS 8SmarterMail > Server Configuration and Management