> With Comcast as my Internet Provider, Gmail as my Email server, and nmh as my
> Email client, all seems to be well. Thank you so much.
Great! Your message did indeed originate from a comcast.com address and was sent via Gmail:
10:39:49 +00:00:00 from nad.dad.org (c-NN-NN-NN-NN.hsd1.ca.comcast.net. [NN.NN.NN.NN])
with ESMTPSA id y62sm24356178pfg.45.2019.12.16.07.39.49 (version=TLS1_2 cipher�DHE-RSA-AES128-GCM-SHA256 bits8/128)
10:39:51 +00:00:02 by mail-pj1-x1034.google.com
with SMTP id v93so3137948pjb.6
for <[hidden email]>
> Of course. I will, on request, continue to provide feedback about the
> problems of inc core dumping and post hanging.
The problem of inc core dumping has been attributed to a known problem that has been fixed.
Is post still hanging for you? Can you replicate it? My guess is that with proper invocation of send/post, it won't be a problem for you or anyone else.
> Content-Transfer-Encoding: quoted-printable
> 10:39:49 +00:00:00 from nad.dad.org (c-NN-NN-NN-NN.hsd1.ca.comcast.net. [=
> by smtp.gmail.com
> with ESMTPSA id y62sm24356178pfg.45.2019.12.16.07.39.4=
> 9 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128)
> 10:39:51 +00:00:02 by mail-pj1-x1034.google.com
> with SMTP id v93so3137948pjb.6
> for <[hidden email]>
Do you know why the equals-signs in the ‘cipher’ line are not QP quoted?
The only way I could replicate it, if at all, would be to revert to my former
> My guess is that with proper invocation of send/post, it won't be a problem
> for you or anyone else.
My experience certainly confirms that.
But should post hang even if send/post is improperly invoked? Maybe the
contexts in which they operate is sufficiently complex and so dependent on
external systems that never hanging is an impractical goal.
>But should post hang even if send/post is improperly invoked? Maybe the
>contexts in which they operate is sufficiently complex and so dependent on
>external systems that never hanging is an impractical goal.
In a perfect world, no, send/post should never hang. But we never got good
details on what was going wrong there. I believe you said running it with
-snoop returned no messages, it still was silently hung.
If you're using the "smtp" or "sendmail/smtp" MTAs, there should never be
a hang. There may be a network timeout along the way, but you should see
some notification with -snoop as to what it is doing (the timeouts could
be up to a few minutes, depending on the operating system). I could maybe
see problems contacting a DNS server, but you would think that would
show up in others ways (and even then, eventually you'd get an error
If you're using "sendmail/pipe", all bets are off.
If you have a setup which uses a custom postproc, again, all bets are off.