[Mailman-Users] Problem with qrunner and too much incoming mail

Uriah Welcome precision at valinux.com
Fri Nov 3 22:47:43 CET 2000

On Fri, Nov 03, 2000 at 12:53:35PM -0800, J C Lawrence wrote:
> On Fri, 3 Nov 2000 11:35:39 -0800 
> Marc MERLIN <marc_news at valinux.com> wrote:
> > The problem is due to qrunner being single threaded by default and
> > having a global lock. Because some mailing lists have subscribers
> > in domains where DNS is slow and unreliable, the MTA will hang on
> > those rcpt to until DNS resolves or timeouts, and qrunner won't be
> > done in time.  After that, it's all downhill from there, more mail
> > queues up, qrunner falls even further behind, etc, etc...
> Running a cacheing nameserver (I've recommended DJB's dnscache
> before) would help significantly here.  This doesn't of course
> remove the problem, just partially alleviates it.  

We're already running djb's dnscache :)

> Further, in the case of Exim IIRC, it can be configured to not do
> DNS lookups on RCPT addresses messages at the time of receipt by the
> MTA based on the IP address/net of the source.  Thus you could
> configure Exim to not do DNS lookups on everything received from
> localhost.  Nigel -- can you confirm this?  I didn't see this on a
> quick skim on the Exim docs but I seem to recall discussion of how
> to do this previously.

This would be really cool I think this would help quite a bit..

- U

"Memory is like an orgasm. It's a lot better if you don't have
to fake it." -- Seymour Cray commenting on virtual memory
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 248 bytes
Desc: not available
Url : http://mail.python.org/pipermail/mailman-users/attachments/20001103/a47fb0d8/attachment.pgp 

More information about the Mailman-Users mailing list