[EMAIL PROTECTED] wrote:
>the qmail-send page says that sending it an ALRM makes it re-scan the
>queue. Well, somebody demanded that his qmail-send gets ALRMed every
>15 minutes to minimize mail delivery time.
That's ignorant. qmail tries to deliver messages immediately. Messages
sitting in the queue are there for one of two reasons:
1) the previous delivery attempt failed
2) qmail hasn't had a chance to send the message yet
In the case of (1), the best policy is almost always to allow qmail to
retry the message according to its own schedule. If this user is on a
part-time connection, you should use serialmail's
maildir2smtp/AutoTURN to send the messages when the connection comes
up. In the case of (2), ALRM qmail-send won't speed anything up
because qmail is already going as fast as it can.
>BUT: He has a slow link
>and queued some 20+ megs of mail at once, in pieces around 3-7 meg each.
>His mail got NOT delivered for over a day while the link was constantly
>glowing.
No messages were delivered?
>When I stopped that cron job the mail was out in about an
>hour. The exact command this cronjob executes is
>
>/usr/local/bin/svc -a /var/qmail/run/qmail
>
>So what gives? Did I assume correctly that sending the ALRM interrupted
>the ongoing transfers and restarted them?
No.
>The log file mentions "SMTP connection died" several times...
That means the other end hung up.
>If so, how do I have the queue run every 15 minutes w/o disturbing
>the deliveries already in progress?
I think the problem is that the ALRM is causing too many qmail-remotes
to talk to the remote system at once, so it's choking.
qmail isn't designed to do deliveries on a fixed schedule. The ALRM
hack is intended for occasional use only.
-Dave
