On Wed, 10 Nov 1999 23:36:37 -0500, scott f. lanes wrote:
>I have just moved a mailing list to qmail/ezmlm. The list has a little over
>1800 users and I am finding that the mailq is running at about 20K
>messages. I added the /var/qmail/control/concurrencyremote file with a
>value of 75. Sometimes it is running at 75 remotes but more often it is at
>13-15. Is there any way to get qmail to push more of the messages through?
Something is screwed up. ezmlm generates one message per post, not one
per recipient. 20K queued messages come from somewhere else (do you
process a lot of other mail?)
If you don't saturate concurrency, and there are no pointers in the log
(a la "memory exhausted - can't fork"), then there is nothing to push
through. You queue is full of messages that are deferred. This is
normal for a busy system, i.e. when you handle e.g. 20 K messages/day
and 14% are deferred for > queue life (more commonly 50 K messages and
10% deferred for varying amounts of time). If you handle much less mail
that that, you have some network or config problem (see log).
If you're an open relay, your system may be busy due to spam :-(
ezmlm may generate a lot of messages in one circumstance: You migrate a
list from e.g. majordomo (no automated bounce handling), then run your
list the first time. A large fraction of bad messages bounce. After
about 11 days, ezmlm will send a warning message to all of these.
Another fraction will be "permanently" deferred. They come back to
ezmlm after 7 days. After another 11 days ezmlm sends warnings. These
warnings will be deferred as well. Still, that's at most one per
subscriber, i.e. << 1800.
-Sincerely, Fred
(Frederik Lindberg, Infectious Diseases, WashU, St. Louis, MO, USA)