Hello all,
This may not be the right forum, but you gotta start someplace....
I am a small ISP. I have a client who has a large (300K) email list and uses some mailer software to send bulk mail via an install of Imail 8.whatever_is_current . Here's what happens.
The server will move along fine for a few days and then, in the middle of the transmission session, will begin to get 'MX connect fail' errors. This means that the Imail smtp service has gone out to DNS, gotten the address of the recipient mail server, attempted to connect to it, and failed to initiate a session.
As time goes on, over thenext few hours, more and more of these failures occur.
Further, if you then go to a dos-box and try to telnet to the ip address port 25 (as a test), it fails to connect!
Now, these are mail servers for MCI, AOL, Hotmail, earthlink and so on, not just little guys like me with 50 or so domains.
What I am thinking is there is some memory leak, or protocol stack problem that after extended xmission, the nic or the driver just looses its mind. Or some internal DNS cache gets corrupted. It seems odd that servers who take mail and connect at say, 7:00 AM, start 'failing to connect' at say 3:30, but, will, after a reboot, start taking mail and responding appropriately.
Keep in mind also that not all of my transactions fail. Many work. But once this server starts to fail, many more failures of the same type occur, and then I generally reboot the server, and it clears up. Till today.
Other info: server runs IIS 5, sqlserver 2000, coldfusion 6.1 (MX) and is a dell poweredge 1400SC dual cpu unit. I am not using the onboard NIC, I am using a 3com 3c905 series nic.
Any thoughts, or directions?
Marty
This may not be the right forum, but you gotta start someplace....
I am a small ISP. I have a client who has a large (300K) email list and uses some mailer software to send bulk mail via an install of Imail 8.whatever_is_current . Here's what happens.
The server will move along fine for a few days and then, in the middle of the transmission session, will begin to get 'MX connect fail' errors. This means that the Imail smtp service has gone out to DNS, gotten the address of the recipient mail server, attempted to connect to it, and failed to initiate a session.
As time goes on, over thenext few hours, more and more of these failures occur.
Further, if you then go to a dos-box and try to telnet to the ip address port 25 (as a test), it fails to connect!
Now, these are mail servers for MCI, AOL, Hotmail, earthlink and so on, not just little guys like me with 50 or so domains.
What I am thinking is there is some memory leak, or protocol stack problem that after extended xmission, the nic or the driver just looses its mind. Or some internal DNS cache gets corrupted. It seems odd that servers who take mail and connect at say, 7:00 AM, start 'failing to connect' at say 3:30, but, will, after a reboot, start taking mail and responding appropriately.
Keep in mind also that not all of my transactions fail. Many work. But once this server starts to fail, many more failures of the same type occur, and then I generally reboot the server, and it clears up. Till today.
Other info: server runs IIS 5, sqlserver 2000, coldfusion 6.1 (MX) and is a dell poweredge 1400SC dual cpu unit. I am not using the onboard NIC, I am using a 3com 3c905 series nic.
Any thoughts, or directions?
Marty