Thank you all

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Thank you all

Norman Shapiro-3
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.

Of course. I will, on request, continue to provide feedback about the
problems of inc core dumping and post hanging.



    Norman Shapiro

Reply | Threaded
Open this post in threaded view
|

Re: Thank you all

Valdis Klētnieks
On Mon, 16 Dec 2019 07:39:48 -0800, [hidden email] said:
> 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.

Glad it all worked out for you. :)

attachment0 (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Thank you all

David Levine-3
In reply to this post by Norman Shapiro-3
Morm writes:

> 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])
                   by smtp.gmail.com
                   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.

David

Reply | Threaded
Open this post in threaded view
|

Re: Thank you all

Ralph Corderoy
Hi David,

> Content-Transfer-Encoding: quoted-printable
...
> 10:39:49 +00:00:00 from nad.dad.org (c-NN-NN-NN-NN.hsd1.ca.comcast.net. [=
> NN.NN.NN.NN])
>                    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?

--
Cheers, Ralph.

Reply | Threaded
Open this post in threaded view
|

Re: Thank you all

Norman Shapiro-3
In reply to this post by David Levine-3
David Levine <[hidden email]> writes:

>Is post still hanging for you?

No it's not.
>
>Can you replicate it?

The only way I could replicate it, if at all, would be to revert to my former
setup.

>
> 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.

    Norman Shapiro


Reply | Threaded
Open this post in threaded view
|

Re: Thank you all

Ken Hornstein-2
>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
message).

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.

--Ken

Reply | Threaded
Open this post in threaded view
|

Re: Thank you all

David Levine-3
In reply to this post by Ralph Corderoy
Ralph writes:

> Do you know why the equals-signs in the ‘cipher’ line are not QP quoted?

Because the author did a really bad job of pasting text into a draft after running "mime" on it.

David