From: Ace Suares (listssuares.an)
Date: Mon Dec 11 2006 - 15:29:59 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>
> This may not help much with a large list with low frequency posts,
> because one jumbo-recipient message is either deferred or active
> at any given time, and when active all its recipients are scheduled
> for delivery as soon as possible... Tuning the various timers only
> helps when the queue is not dominated by a small number of messages.

I think this is a huge part of the problem.
It's a mailing list server - it handles no other mail.

at Wednesday 12:00 a mail is sent to 4500 recpients
about 80 of them are for omroep.nl

normal situation:
- postfix bundles 50 emails into one connection and 30 others in another
connection. Swell: 2 connections, each one delivery, all done.

current situation:
- mailserver at omroep.nl (and some others) *refuse* more then 10 or 15
rcpt to: in one message. The rest is deferred.
- so, concurrency is set very low. 1 email per connection. But still there
is too many simultaneous connections, according to the log. What else can
I do ?

By the way, I think the concurrency is per domain, not per mailserver, am
I right ? This means that mail for tros.nl and rvu.nl, which are both
handled by mx1.mail.omroep.nl, can occur *simultaneously* even if
concurrency_limit = 1, right ?

How can the time *between* connections be spaced out more evenly ? For
instance I want to make only one connection every 10 seconds to a
specific host ? Is that possible ?

It seems that even with concurrency_limit = 1, which I think is
ridiculous, the various mailservers *still* see too many connections from
my server. How is that possible !?

Cheers,
_Ace

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]