A small corrections: there are also a number of mails for local delivery (and
forwarding).
I witness the following behaviour:
the first x mails go through without any problems (no problem with the
concurrency: the number of remote processes is always less then 30).
Then, at a sudden point, I see for all newly queued mails (the rest of the
3000) in the logfiles:
918738205.279362 delivery 14284: deferral:
qmail-spawn_unable_to_create_pipe._(#4.3.0)/
This goes on for all queued emails, and after that newly arrived emails go
through again without problems...
The same if I send an alarm to qmail-send.
Am I hitting the concurrencylocal limit here? Do I need to reload or restart
qmail for this parameter to take effect?
Mark Delany wrote:
> At 10:47 AM 2/11/99 +0100, Franky Van Liedekerke wrote:
> >Hi,
> >
> >I have a list of approx. 3000 addresses, and I need to send a mail to
> >them. What I do now is plit this list in pieces of 50 addresses ech, and
> >then send the mail via talking to smtp port 25 directly.
>
> I wouldn't bother. Send that lot as one submission via qmail-inject.
>
> >Now, the time between sending and delivery (all remote addresses) can be
> >up to 13 hours! This is kind of slow, isn't it?
>
> Is that on the first attempt or final delivery?
>
> >Can I configure some parameters?
> >I now have
> ># tcp connections=150
> >concurrencylocal=40
> >concurrencyremote=40
>
> We need to know what your log files are saying. Is the system at full
> concurrencyremote for hours at a time? If so, increase this until you hit a
> system resource limit.
>
> >Do I need to change these, and or some of the timeout parameters?
> >Anybody has a suggestion on how they did this?
>
> Yes. Assess why the delay is there and whether you have spare system
> resources to reduce that delay. Only you have the info to do that
> assessment, only you have the info to determine whether you have spare
> resources. We can only guess unless you disclose all of that info.
>
> Regards.
