[Mailman-Users] delay before sending out emails
Dan.Mick at West.Sun.COM
Fri Dec 8 04:18:57 CET 2000
I believe this is how it's designed to work. *All* outgoing mails
are queued, and eventually delivered by qrunner.
# Immediately queue the message for the qrunner to deliver, mostly likely
# about a minute from now. The advantage to this approach is that
# messages should never get lost -- some MTAs have a hard limit to the
# time a filter prog can run. Postfix is a good example; if the limit is
# hit, the proc is SIGKILL'd giving us no chance to save the message. It
# could take a long time to acquire the lock. This way we're fairly safe
# against catastrophe at the expense of more disk I/O.
Is the average of the extra 30 seconds a problem?
> i'm running version 2.0 and have upgraded from beta5 then beta6 and still
> have the same problem.
> When a mail is sent to the list (looking at /var/log/maillog we
> see: status=sent ("| /home/mailman/mail/wrapper post old") ) it gets to
> the right place. I am under the impression that it should deliver
> immediately, but it doesn't. Instead it waits for the next minute to
> arrive and the failed delivery part of the cronjob takes over
> (/usr/bin/python -S /home/mailman/cron/qrunner).
> I'm running RedHat 6.2 with postfix as the MTA, apart from not sending the
> mails out immediately, everything is fine. I've spoken to a friend of
> mine, also running postfix (albeit under NetBSD) and his mails out
> This has got me a little stumped.. i welcome any input!
More information about the Mailman-Users