Pkg exim4 users - Mar 2007 - Throttle or limit deliveries to smarthost?

I would like to limit the speed, or number of processes spanned to
upload to a smarthost - is there a directive to do this?

-- 
aloha,
dave

Mark,

Shaping might work, but this host does a lot of other LAN traffic over
the same eth0 that exim uses for smtp ... so I would have to shape for
smtp only.

What I was really hoping for was an exim4-specific option that says:

Do not launch/spawn more than x queue processes at once.
Do not send more than y bytes or z messages per second to smart_host

I only use a single smart_host for outside deliveries, and I want to
prevent flooding of my internet connection or smarthost when I send
mail to a distribution list.

aloha,
dave


On 3/19/07, mark david mcCreary <mdm@one-man-isp.com> wrote:
> Dave
>
> Hopefully somebody else knows an answer.
>
> In my case I''ve been using the CBQ traffic shaping portion of the
Linux
> Kernel.
>
> HTB is another traffic shaping module in Linux, and I think that it is
> considered a bit newer and better.
>

On Mon, Mar 19, 2007 at 05:01:39PM -0600, Dave Price
wrote:
> Do not launch/spawn more than x queue processes at once.
This is possible, see load control in spec.txt
> Do not send more than y bytes or z messages per second to smart_host
This is not possible with exim''s means.
> I only use a single smart_host for outside deliveries, and I want to
> prevent flooding of my internet connection or smarthost when I send
> mail to a distribution list.
If you are delivering via a smarthost, your exim will anyway only send
out a single copy of the message with the appropriate envelope.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don''t trust Computers. They | Mailadresse
im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 72739835

On Tue, 2007-03-20 at 13:57 +0100, Marc Haber wrote:
> On Mon, Mar 19, 2007 at 05:01:39PM -0600, Dave Price wrote:
> > Do not launch/spawn more than x queue processes at once.
> 
> This is possible, see load control in spec.txt
> 
> > Do not send more than y bytes or z messages per second to smart_host
> 
> This is not possible with exim''s means.
> 
> > I only use a single smart_host for outside deliveries, and I want to
> > prevent flooding of my internet connection or smarthost when I send
> > mail to a distribution list.
> 
> If you are delivering via a smarthost, your exim will anyway only send
> out a single copy of the message with the appropriate envelope.
Unless the mailing list uses VERP, i.e., makes a custom sender address
for each recipient.

The mailing list software (if you''re using any) might have a way to
throttle the delivery rate also.
-- 
Ross Boylan                                      wk:  (415) 514-8146
185 Berry St #5700                               ross@biostat.ucsf.edu
Dept of Epidemiology and Biostatistics           fax: (415) 514-8150
University of California, San Francisco
San Francisco, CA 94107-1739                     hm:  (415) 550-1062

Marc Haber wrote:
>> I only use a single smart_host for outside deliveries, and I want to
>> prevent flooding of my internet connection or smarthost when I send
>> mail to a distribution list.
>>     
>
> If you are delivering via a smarthost, your exim will anyway only send
> out a single copy of the message with the appropriate envelope.
>
> Greetings
> Marc
>
>   
I think this is not always the case. I think Mailman for example splits 
the distribution list into batches and sends several different mails 
with no more than a configurable number of recipients (100 by default 
IIRC). Also some (many?) ISPs mailservers now limit the number of 
recipients on a single message to 100 or less as a way to reduce spam.


I had a similar problem where a mailserver wasn''t sending to a
smarthost
but directly using DNS lookups, and it sometimes killed the internet 
connection when a client host sent out large mail-list messages to many 
destinations. The best answer in the end was to rate limit the outgoing 
traffic on port 25 using tc (the linux traffic control tool).

Cheers,

Alex