My pop3d is locking up every time I check email. Has this happened
before? I don't want to re-invent the wheel. Let me tell you guys about
what's up, and if there's no previously known solution I'm ready to dive
into the code and see what's fixable.
Details: I was using dbmail 1.0 since Dec 10, no problems. Redhat 8.0,
mysql 3.23.53, about 24 users. IMap remains working fine, but now when I
connect to pop3, I leave behind a locked dbmail-pop3d process. I am
connecting through a NAT-ing firewall with Eudora on a PC. On my redhat
box, when I run a netstat -n, I see a connection from the redhat box port
110 back to my firewall in the state 'CLOSE_WAIT'. I've left this for
hours and nothing has changed. (It doesn't time out after 5 mins like I
was hoping). I've tried telnet localhost 110 and I cause the same lockup
problem.
What's changed in the last week? Well, I discovered this mailing list and
went through the archives and applied a few changes (oops):
* To the /etd/dbmail.conf file to set [POP] MAXCONNECTS=1 -- to prevent
people
getting other people's email.
* To debug.c, I changed the initial debug level to 2 not 5. Ditto in
the /etc/dbmail.conf file.
That's it! And I've reversed these changes, with no effect. Still have
the locked pop3d problem.
So. Any clues to this? I've rebooted the server, and I've re-installed
the original 1.0 source with the original /etc/dbmail.conf file. The
problem still persists.
Any solutions? Any suggestions?
Thanks for reading this far!
Kenn Frankel
[EMAIL PROTECTED]
