Jan Stanik writes:
Monday, August 11, 2003, 1:08:15 PM, you wrote:
Sunday, August 10, 2003, 6:57:40 PM, you wrote:
I noticed slow delivery when queue is under higher load
(e.g. delivering mail to thousands customers) New mails are
delayed from 10 min. to 2 hours. I tried to set queuehi, queuelo
and queuefill but with no effect. Can anyone give me some hints
how to set queue parameters please?
Well, obviously when you have thousands of messages in the queue new mail
has to go to the end of the line, and wait until its turn comes up.
Where could be the bottleneck of delivering? Can I allow more
concurrent delivery attempts?
You can tune the delivery limits by editing $sysconfdir/module.* files. The
MAXDELS, MAXHOST, and MAXRCPT settings are described in
http://www.courier-mta.org/queue.html. You better know what you're doing;
if the parameters aren't set right the server may not even start. As such,
always back them up first, before messing around with them.
For esmtp, MAXDELS is the maximum number of messages sent via SMTP at any
given time, and MAXHOST is the maximum number of messages sent via SMTP to
the same domain, at any given time.
Thank You Sam. I searched the log file and it seems the problem
occurs when "wakeup time=none" string appears in courierd records.
I the same time new incoming mails are stored in var/tmp directory and
dont move to queue.
This situation persists from 10 minutes to few hours.
It's strange because queuefill is set to 1 minute and in the queue are
not more than 100 messages. What does exactly mean "wakeup time=none" and
how can I affect it?
It means that all available outgoing mail delivery slots are being used, so
at least one mail delivery attempt must conclude before any more mail will
be processed.
9 messages in net.sourceforge.lists.courier-users[courier-users] Re: slow delivery
