On Sat, 17 Feb 2001, Charles Cazabon wrote:
> Geoffrey Gussis <[EMAIL PROTECTED]> wrote:
> > I saw a mention in the archives about a per-domain concurrency patch
> > - which would help make sure that a qmail server would not overload a
> > recipient smtp server when a higher volume of mail was being sent
> > out.
>
> It's a broken idea. The admin of the remote server should set their
> concurrency limits to something their system can handle -- if they don't,
> then that's their problem, not yours.
I agree, but there is a different class of problem that one might want to
solve, which leads to the original problem. 'our' problem is that all of
the concurrency remote outgoing slots are being used to transfer mail to
one domain, whereas it /might/ be desireable for qmail to send sendable[0]
mail to a variety of domains.
For example, if I only have 40 outbound connect slots I might not want
all of them to bet consumed sending mail to AOL, I might want dedicate
some of my resources to delivering mail to other domains.
RjL
[0]sendable in the sense that there is a message that is on the 'a
delivery attempt should be made now' queue rather than any knowledge about
the sucess/failure of trying to deliver it
