* This is the modus mailing list * I had one weird problem with VOPMail that seems familiar.
I had put several IPs on from different networks. It seemed that the VOPMail did not like using different subnetmasks on the network and also, it would try to reply on the default IP to a request that came in on the alternate IP. I stopped using the alternate IP as my base IP of the server and went back to my original method which was to use the base IP of the base domain as the base IP of the server itself. This was on an NT4 box though. David Payer OMNI Internet www.iowalink.com ----- Original Message ----- From: "Darryl Dunkin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, January 03, 2004 12:18 AM Subject: [Modus] SMTP Connections Not Closing * This is the modus mailing list * It seems I've been having this problem for a few weeks and have finally found what the issue is, although I have no resolution (yes, I have a message into Vircom, but they are out for these few days). I've had to reboot my ModusGate (3.0 build 277, running on Win2k SP4) server twice daily to keep it up and running. The first sign of an issue was that there was no mail delivery, I could not make any outgoing TCP connections from the server, but it was accepting and spooling mail. After a lot of rebooting and watching it happen again, I found thousands of SMTP sessions in a close_wait state to my internal and end user e-mail servers, such as the cropped example I pasted below. I can free up all of the connections by restarting Modus services. Has anyone ever seen anything like this? The servers are both on the same LAN without any firewall in between them, so I do not see why the services are not being closed. Also, I have Modus set to close SMTP connections after 30 seconds. Proto Local Address Foreign Address State TCP 0.0.0.0:25 0.0.0.0:0 LISTENING TCP 0.0.0.0:80 0.0.0.0:0 LISTENING TCP 0.0.0.0:135 0.0.0.0:0 LISTENING TCP 0.0.0.0:445 0.0.0.0:0 LISTENING TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING TCP 0.0.0.0:1027 0.0.0.0:0 LISTENING TCP 0.0.0.0:1028 0.0.0.0:0 LISTENING TCP 0.0.0.0:1029 0.0.0.0:0 LISTENING TCP 0.0.0.0:1030 0.0.0.0:0 LISTENING TCP 0.0.0.0:1031 0.0.0.0:0 LISTENING TCP 0.0.0.0:1032 0.0.0.0:0 LISTENING TCP 0.0.0.0:1033 0.0.0.0:0 LISTENING TCP 0.0.0.0:1034 0.0.0.0:0 LISTENING TCP 0.0.0.0:1035 0.0.0.0:0 LISTENING TCP 0.0.0.0:1036 0.0.0.0:0 LISTENING TCP 0.0.0.0:1037 0.0.0.0:0 LISTENING TCP 0.0.0.0:1038 0.0.0.0:0 LISTENING TCP 0.0.0.0:1039 0.0.0.0:0 LISTENING TCP 0.0.0.0:1040 0.0.0.0:0 LISTENING TCP 0.0.0.0:1041 0.0.0.0:0 LISTENING TCP 0.0.0.0:1042 0.0.0.0:0 LISTENING TCP 0.0.0.0:1043 0.0.0.0:0 LISTENING TCP 0.0.0.0:1044 0.0.0.0:0 LISTENING TCP 0.0.0.0:1045 0.0.0.0:0 LISTENING TCP 0.0.0.0:1046 0.0.0.0:0 LISTENING TCP 0.0.0.0:1047 0.0.0.0:0 LISTENING TCP 0.0.0.0:1048 0.0.0.0:0 LISTENING TCP 216.251.100.19:1084 216.251.100.7:25 CLOSE_WAIT TCP 216.251.100.19:1085 216.251.100.5:25 CLOSE_WAIT TCP 216.251.100.19:1087 216.251.100.5:25 CLOSE_WAIT TCP 216.251.100.19:1088 216.251.100.5:25 CLOSE_WAIT TCP 216.251.100.19:1089 216.251.100.7:25 CLOSE_WAIT TCP 216.251.100.19:1090 216.251.100.7:25 CLOSE_WAIT Thanks, Darryl Dunkin ** To unsubscribe, send an Email to: [EMAIL PROTECTED] with the word "UNSUBSCRIBE" in the body or subject line. ** To unsubscribe, send an Email to: [EMAIL PROTECTED] with the word "UNSUBSCRIBE" in the body or subject line.
