Hi,
That's your culprit. You had bounces turned on, but were not running outgoing.pl regularly to deliver the bounces. They piled up over time, and you are probably on a ext2/3 filesystem. It slows down dramatically after you start hitting 20-30k files, so the time it took to write out a bounce reply, was longer then your pop server was willing to wait, so it cut the connection.
Solution: make sure outgoing.pl is running in cron. Set it to run ever 10 or 15 minutes (the frequency determines how fast a bounce/forward or autoreply will come back to a user).
Cheers,
Alex
--
Gossamer Threads Inc.
That's your culprit. You had bounces turned on, but were not running outgoing.pl regularly to deliver the bounces. They piled up over time, and you are probably on a ext2/3 filesystem. It slows down dramatically after you start hitting 20-30k files, so the time it took to write out a bounce reply, was longer then your pop server was willing to wait, so it cut the connection.
Solution: make sure outgoing.pl is running in cron. Set it to run ever 10 or 15 minutes (the frequency determines how fast a bounce/forward or autoreply will come back to a user).
Cheers,
Alex
--
Gossamer Threads Inc.