Thats a clever idea.  I'll give it a try and let you know how it goes.

Bill


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Len Conrad
Sent: Wednesday, November 19, 2003 5:03 PM
To: [EMAIL PROTECTED]
Subject: [IMGate] Re: throttling




>What is the best way to throttle mail from IMGate to the backend mail
>server?  I've set IMGate to use only 1 delivery process

"smtp" process? that's ok

>, but I'm running
>into problems where the backend server will refuse a few connections, so
>Postfix will begin to backoff, then a few minutes later it will pound the
>backend server with lots of mail one after another... causing further
>connection refusals, and kicking in the backoff again.

I just saw a weird comment on throttling on postfix list.

I haven't tried this:

in transport.map

mydomain.tld  smtp:mbx.mydomain.tld

this causes postfix to deliver query dns for MX of mbx.mydomain.tld and try
to send the the MX records.

you set up two mx records.

mbx.mydomain.tld. MX 10 mx1.mydomain.tld.
mbx.mydomain.tld. MX 20 mx2.mydomain.tld.

and their A records

mx1.mydomain.tld.  a.b.c.d
mx2.mydomain.tld.  ip.ad.re.ss

Where a.b.c.d is not a real address, so when posfix tries it, postfix times
out ( see postconf | grep timeout ) and then tries   ip.ad.re.ss which is
your real mailbox server.

if set smtp connect timeout to 3 or 4 seconds, then you will get that
timeout between each msg to ip.ad.re.ss.

as I said, I have not tried this. the timeouts for postfix, so this affects
your outbound mail, too.

Len




Reply via email to