Found the culprit.... in the release notes, you are told if you want to improve database performance, add the following keys to the registry:
UseMultiConnect MaxConnect We were running an external database through access and of course I made these changes. After removing them, pop has stayed up for over a week and never grows over 10-12MB's in size. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Sanford Whiteman Sent: Sunday, July 21, 2002 1:04 AM To: Bill Anderson Subject: Re[2]: [IMail Forum] Pop3d32.exe hanging... > =========================================================================== > Active Routes: > Network Destination Netmask Gateway Interface Metric > 0.0.0.0 0.0.0.0 199.108.225.1 199.108.225.98 1 > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 > 199.108.225.0 255.255.255.0 199.108.225.99 199.108.225.98 1 > 199.108.225.98 255.255.255.255 127.0.0.1 127.0.0.1 1 > 199.108.225.99 255.255.255.255 127.0.0.1 127.0.0.1 1 > 199.108.225.255 255.255.255.255 199.108.225.99 199.108.225.98 1 > 224.0.0.0 224.0.0.0 199.108.225.99 199.108.225.98 1 > 255.255.255.255 255.255.255.255 199.108.225.99 199.108.225.98 1 > =========================================================================== On a test dual-homed, single-NIC machine, my table is actually different: =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.189.1 192.168.189.12 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.189.0 255.255.255.240 192.168.189.12 192.168.189.12 1 192.168.189.12 255.255.255.255 127.0.0.1 127.0.0.1 1 192.168.189.13 255.255.255.255 127.0.0.1 127.0.0.1 1 192.168.189.255 255.255.255.255 192.168.189.12 192.168.189.12 1 224.0.0.0 224.0.0.0 192.168.189.12 192.168.189.12 1 255.255.255.255 255.255.255.255 192.168.189.12 192.168.189.12 1 =========================================================================== Note that the routes to my local and multicast networks are through the primary IP of the interface, while yours hop through the secondary IP--which is wrong. It wouldn't hurt to double-check, maybe redo your bind order. Also let us know if you are seeing localhost network traffic mirroting your logs, like I said. > I am not able to shutdown imail and run something else on > 127.0.0.2:110 since Imail is critical to our business. If it's crashing all the time, you're gonna need some troubleshooting time. That's a fact of support. But I understand that this may not be the best week for it. -Sandy Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Please visit the Knowledge Base for answers to frequently asked questions: http://www.ipswitch.com/support/IMail/ Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Please visit the Knowledge Base for answers to frequently asked questions: http://www.ipswitch.com/support/IMail/
