I have about 22 clients. I had these settings before I set the TIMEOUT
higher.
NCHILDREN=60
MAXCONNECTS=20
TIMEOUT=1000
These are very similar to yours but I tried your setings. It did not
help. I still have the problem...
Aron
Paul J Stevens wrote:
Try these:
Set NCHILDREN higher.
Set MAXCONNECTS and TIMEOUT *much* lower.
example: If you run a 1.2.11 machine with 10 clients:
NCHILDREN=50
MAXCONNECTS=10
TIMEOUT=600
This will eat connections with the database for lunch though. So
experiment. Especially NCHILDREN is critical. dbmail-1.2 doesn't have
dynamic preforking so if your process pool is drained you're in trouble.
It may also be a dbmail issue.
Thunderbird will drop TCP sessions dead on the floor if it doesn't
like the server response. Earlier dbmail versions had a hard time
dealing with those situations. It took me a couple of hours tracing
with ethereal to realize what was going on. It's still something I do
when I run into unresponsive thunderbird clients.
Preisinger Aron wrote:
Sorry, I was wrong. The problem still exists, but not so
frequently... It can be reproduced with any kind of mailclients...
It is a very big problem.
Please help me!
Aron
