On Tue, Oct 19, 1999 at 01:23:18PM -0600, Charles Cazabon wrote:
> It's not really a qmail issue. If a particular mailhost is bogging down
> because it is accepting more SMTP connections than it can actually handle,
> it's due to:
> -poor configuration. Solution: tell the sysadmin.
> -poor administration. Solution: tell the sysadmin.
> -poor choice of MTA on their end. Solution: tell the sysadmin.
I don't agree.
1) There are mailservers that don't accept more than n concurrent
connections from the same IP (while they still have the capability for
open slots for other IPs).
However this causes them to first "see" the connection and then
dropping them. I wouldn't call that "poor [conf/admin/mta]".
This also leads to 2)
2) If a system is only accepting n connections a time, I have
concurrencyremote set to 4*n and I just received a bulk with 3*n
messages to that host, I will probably get n-m messages through and
2*n messages get blocked by either tcpto and/or the messages become
marked as "unreachable" and go to the backoff list.
Chances would be IMHO good to get them through smoothly if I could
set the max concurrency for that host to e.g. n/2. Then qmail
wouldn't even try to deliver more messages -> less errors, less
backoff delays, more throughput for the other mails in MY queue
(as they wouldn't have to wait for the others producing errors).
But I may be wrong ;-)
\Maex
--
SpaceNet GmbH | http://www.Space.Net/ | Yeah, yo mama dresses
Research & Development | mailto:[EMAIL PROTECTED] | you funny and you need
Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | a mouse to delete files
D-80807 Muenchen | Fax: +49 (89) 32356-299 |
