[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On Sat, 17 Feb 2001, Charles Cazabon wrote:
> >
> > 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.
> 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.
To play devil's advocate, you could also look at this situation in terms of
"if this server handles enough mail that all remoteconcurrency is sucked up
by one domain, than it's busy enough to justify raising the remote
concurrency limits, and upgrading the hardware if necessary".
I find that even a modest box can easily handle a remote concurrency of
100 or better with qmail.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
-----------------------------------------------------------------------