info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
sendmail 8.15.2: "cmd read" timeout
81 views
Skip to first unread message
Sergey
Apr 11, 2017, 11:03:22 AM4/11/17
to
Hello.
Which timeout is used for "cmd read" ? I have a strange problem - too
long timeout for command:
# ps ax| grep "send.*\.125\.186"
9286 ? S 0:00 sendmail: server [x.x.125.186] cmd read
9943 ? S 0:00 sendmail: server [x.x.125.186] cmd read
10892 ? S 0:00 sendmail: server [x.x.125.186] cmd read
# date
Fri Apr 7 17:27:14 +04 2017
# ps ax| grep "send.*\.125\.186"
9286 ? S 0:00 sendmail: server [x.x.125.186] cmd read
9943 ? S 0:00 sendmail: server [x.x.125.186] cmd read
10892 ? S 0:00 sendmail: server [x.x.125.186] cmd read
# date
Tue Apr 11 18:42:30 +04 2017
Unfortunately, I can't say exactly when problem appeared.
I use conncontrol feature and it became interfere sometimes.
--
Regards, Sergey
Which timeout is used for "cmd read" ? I have a strange problem - too
long timeout for command:
# ps ax| grep "send.*\.125\.186"
9286 ? S 0:00 sendmail: server [x.x.125.186] cmd read
9943 ? S 0:00 sendmail: server [x.x.125.186] cmd read
10892 ? S 0:00 sendmail: server [x.x.125.186] cmd read
# date
Fri Apr 7 17:27:14 +04 2017
# ps ax| grep "send.*\.125\.186"
9286 ? S 0:00 sendmail: server [x.x.125.186] cmd read
9943 ? S 0:00 sendmail: server [x.x.125.186] cmd read
10892 ? S 0:00 sendmail: server [x.x.125.186] cmd read
# date
Tue Apr 11 18:42:30 +04 2017
Unfortunately, I can't say exactly when problem appeared.
I use conncontrol feature and it became interfere sometimes.
--
Regards, Sergey
Sergey
Apr 12, 2017, 5:18:34 AM4/12/17
to
Sergey wrote:
> # ps ax| grep "send.*\.125\.186"
> 9286 ? S 0:00 sendmail: server [x.x.125.186] cmd read
> # ps ax| grep "send.*\.125\.186"
> 9286 ? S 0:00 sendmail: server [x.x.125.186] cmd read
> # date
> Fri Apr 7 17:27:14 +04 2017
>
> # ps ax| grep "send.*\.125\.186"
> 9286 ? S 0:00 sendmail: server [x.x.125.186] cmd read
> Fri Apr 7 17:27:14 +04 2017
>
> # ps ax| grep "send.*\.125\.186"
> 9286 ? S 0:00 sendmail: server [x.x.125.186] cmd read
> # date
> Tue Apr 11 18:42:30 +04 2017
Hm... I use SMTP authentication via Cyrus SASL (v2.1.26) and this
> Tue Apr 11 18:42:30 +04 2017
is related. Old Sendmail's processes was closed when saslauthd was
restarted. Obviously what sendmail wait of suspended saslauthd
processes. So, this is a problem of saslauthd.
Is it possible to limit the waiting sasl reply as workaround ?
--
Regards, Sergey
Claus Aßmann
Apr 12, 2017, 9:27:19 AM4/12/17
to
Sergey wrote:
> restarted. Obviously what sendmail wait of suspended saslauthd
> processes. So, this is a problem of saslauthd.
> Is it possible to limit the waiting sasl reply as workaround ?
Seems you have the check with the Cyrus-SASL people, as sendmail
> restarted. Obviously what sendmail wait of suspended saslauthd
> processes. So, this is a problem of saslauthd.
> Is it possible to limit the waiting sasl reply as workaround ?
"just" uses the library (and AFAICT there isn't an option for
sendmail to change that kind of behaviour of the library).
--
Note: please read the netiquette before posting. I will almost never
reply to top-postings which include a full copy of the previous
article(s) at the end because it's annoying, shows that the poster
is too lazy to trim his article, and it's wasting the time of all readers.
Claus Aßmann
Apr 12, 2017, 10:16:10 AM4/12/17
to
Sergey wrote:
> Which timeout is used for "cmd read" ? I have a strange problem - too
The conveniently named
> Which timeout is used for "cmd read" ? I have a strange problem - too
command In server SMTP, the time to wait for
another command. [1h, 5m].
See the fine documentation (doc/op/op.*):
4.1. Timeouts
0 new messages