I have a relatively active mail server that runs qpopper for POP3 service.
I have been using an old version of 2.xx for a long time, and didn't even
realize there were vulnerabilities with it until I was doing some research
on a problem I am having.
Apparently, my server is getting attacked, and I cannot figure out how to
remedy the situation. The old version of Qpopper had been running
FLAWLESSLY for the last 3-4 years with using inetd to start it up.
Recently, I have been having problems where nobody can connect to my POP3
server, and it just sits there and hangs until the connection times out.
The (temporary) solution is to kill off inetd and restart it. 5-10
minutes later, it does the same thing over again, where nobody can connect
to the POP3 server.
Next, I downloaded the newest version of Qpopper from the Eudora site
yesterday, compiled it up and started it up just fine. I compiled it in
daemon mode, just because it actually seems to run faster that way on my
system, and the SAME EXACT PROBLEM happens. I can start up qpopper by
issuing a "qpopper -S" command, and it runs in server mode... Then less
than 5 minutes later, it will not take any incoming connections.
Somebody, PLEASE help me figure this out. My customers are getting very
irritated over this whole thing and I cannot figure it out. I also have
better things to do than to sit in front of the terminal and restart my
POP3 server every 5-10 minutes throughout the day.
(The strangest thing is that the server worked fine all last night,
throughout the night, and worked fine this morning until about 8:30am...
It starts "crapping out" at the same time every day, these last 3 days or
so).
Ricky
