I wanted to let the list know something about this topic. Sorry if this has
been covered, but I just started following the list again because of I'm
having this same problem.
I'm running qmail on Redhat 6.x with a 2.2.12-20smp kernel. It has been
running for well over a year (I don't remember the exact date I installed
everything). But, over the last couple of months, I started getting a few
complaints of emails not being sent out in a timely manner. Every time I
received the complaint, I checked my processes with 'ps ax | grep qmail' and
low and behold there would 20 or so copies of qmail-remote that were sitting
doing nothing. In fact, they had been sitting doing nothing for so long,
they were swapped out. The first few times, I just killed the qmail-remote
processes and watched as qmail again started sending messages across the
Internet. After a while though, I noticed a pattern. Every time I killed
all the stuck qmail-remote processes, almost all the mail going out vis the
newly revived qmail-remote processes was directed to
[EMAIL PROTECTED] (XX being a number in the range of 01 to
about 37 or so). After some further investigation, I found that all of the
messages going to edirectnetwork.net were bounce messages stating that the
user they were trying to send mail to no longer existed. So, I sent an
email to [EMAIL PROTECTED] to try to explain the situation to
her/him and offered to help solve the problem as she/he was needlessly
waisting both their and my bandwidth. After a few days and no response
whatsoever, I simply found the IP address for every optXX.edirectnetwork.net
server and added it to my tcpserver rules to be blocked so that they could
no longer send mail to my server.
Here's the good part. I setup the block over 48 hour ago, and have since
not had a single qmail-remote process lock-up. Before I made the change, I
would normally have at least two to three stuck qmail-remote processes in
that same amount of time.
I don't know how and/or if the two are even related. I hope this helps.
Again, I apologize if this has already been covered.
Eric Calvert
Caveland Connection
