On Tue, Jul 24, 2001 at 08:09:01PM -0400, Dahnke, Eric allegedly wrote:
>
> Sorry for my abrupt response previously. I recognize you as a long time
> member of the list, and appreciated your help when I was first getting into
> qmail. But on a server level you do need to do this no? That is, qmail can
> be set to do 300 concurrent deliveries but in the tcp layer either inetd or
> tcpserver needs to be upped from their default values as well.
Yes. But there are two different concurrency levels regarding remote
mail. One controls how many *inbound* connections will be accepted
concurrently and that is controlled by the tcpserver -c value. The
other controls how many *outbound* deliveries will be attempted
concurrently and that is controlled by control/concurrencyremote.
You are referring to the former while John is referring to the
latter.
Yes, you do need to tune both of these and yes they are both in the
"tcp layer" as you put it, but they are definitely different beasts
that should be treated entirely separately.
Regards.
>
>
>
>
> -----Original Message-----
> From: John White [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 24, 2001 6:59 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Problem with Qmail Queueing
>
>
> On Tue, Jul 24, 2001 at 06:39:00PM -0400, Dahnke, Eric wrote:
> >
> > Wrong. Look at the last line of my post. "By default, tcpserver allows at
> > most 40 simultaneous qmail-smtpd processes. To raise this limit to 400,
> use
> > tcpserver -c 400. "
>
> I read that.
>
> That doesn't have anything to do with the number of concurrent remote
> deliveries that qmail will do.
>
> John White
