Re: [Mailman-Developers] Huge lists
claw@kanga.nu said:
Actually on the input side it would be 2M/SMTP_MAX_RCPTS where SMTP_MAX_RCPTS defaults to 500. Additionally, Exim (I haven't checked Postfix, but I doubt it) does not collapse identical spool entries with different RCPT TO lists, so you're still left with the same number (checking for identicallity is expensive).
You pedant :-)
Granted although that raises the other issue... Barry mentioned yesterday that he was putting the dropped SMTP_MAX_RCPTS functionality back in... but I thought it had deliberately gone on the basis that mailman was giving the mail delivery job to the MTA and not trying to second guess it.
If we do split the list, then ideally it should be sorted.... at least so identical domains go together and maybe more intelligently than that.... and we're back to trying to second guess the MTA at its own job.
I would expect them to have configured their MTA to not attempt pre-lookups for messages arriving from MailMan.
I guess that we need a per MTA tuning/configuration document. I pretty much have that in the exim mailman howto (always willing to take contributions/comments on that BTW - especially if they suggest solutions rather than just raising criticisms). Have we got that data for the other MTAs? Of course we could have comparisons of the suitabilities of different MTAs if people enjoy a decent flamefest.
Nigel.-- [ - Opinions expressed are personal and may not be shared by VData - ] [ Nigel Metheringham Nigel.Metheringham@VData.co.uk ] [ Phone: +44 1423 850000 Fax +44 1423 858866 ]
At 3:52 PM +0100 5/24/2000, Nigel Metheringham wrote:
If we do split the list, then ideally it should be sorted.... at least so identical domains go together and maybe more intelligently than that.... and we're back to trying to second guess the MTA at its own job.
If you VERP, so you have one piece of email per subscriber per message, you stop trying to outguess the MTA, since it can look at everything and decide a delivery strategy (although even then, you can affect the MTA by what order you submit messages). When you start chunking things together, you start limiting the MTA's ability to optimize, so you have to get smarter.
Sorting by domain is better than no sorting, but sorting by MX is preferable -- but non-trivial and time-expensive. You basically get back into becoming an MTA again, so it's probably better to go with a domain sort and VERP, and just make sure you're configured to feed the MTA fast enough to keep it busy without overloading it.
-- Chuq Von Rospach - Plaidworks Consulting (mailto:chuqui@plaidworks.com) Apple Mail List Gnome (mailto:chuq@apple.com)
And they sit at the bar and put bread in my jar and say 'Man, what are you doing here?'"
participants (2)
-
Chuq Von Rospach -
Nigel Metheringham