Re: mutt 1.05 TLS socket terminated?
On Sun, Aug 25, 2019 at 09:39:42AM +0200, li...@2ion.de wrote: > 1st step: Does it happen with other email clients and the same remote > server? E.g. do use msmtp, Thunderbird etc against the same server for a > while. > > Guess: This looks more like the server / the remote end is shutting the > TLS connection down. As you know the server and the port, connect with > openssl s_client a couple of times (it also supports STARTTLS with EHLO, > though you need to get the exact command from the man page > openssl-s_client(1)) and speak some SMTP. Perhaps you can reproduce the > problem? > > Guess: Could it be that the remote end drops you when under load? Do you > have access to the remote server logs? If not, your service provider > might be able to look up potential errors in their log. Thanks for suggestions, use only if the problem recurrs which it hasn't yet. Tom Fowle
Re: mutt 1.05 TLS socket terminated?
1st step: Does it happen with other email clients and the same remote server? E.g. do use msmtp, Thunderbird etc against the same server for a while. Guess: This looks more like the server / the remote end is shutting the TLS connection down. As you know the server and the port, connect with openssl s_client a couple of times (it also supports STARTTLS with EHLO, though you need to get the exact command from the man page openssl-s_client(1)) and speak some SMTP. Perhaps you can reproduce the problem? Guess: Could it be that the remote end drops you when under load? Do you have access to the remote server logs? If not, your service provider might be able to look up potential errors in their log.
mutt 1.05 TLS socket terminated?
Since I posted this problem, I did a apt-get update for other reasons and the tls problem seems to have disappeared. (So far anyhow) Tom Fowle WA6IVG Using mutt 1.5.23 with Debian 8 jessie. I am getting the following problem while reading messages. approximately: "The TLS socket was improperly terminated. can not copy messages." This appears on the screen for only just long enough for my screen reader to grab it but dissappears before I can copy or check it.. I then have the usual top line menu and a blank screen. Being simplistic by nature I just exit mutt and restart but all messages which have been marked for deletion remain in the inbox and unless i have kept carefull track of the last read message number before the TLS error I have to trundle through all the previously read messages till I find the first unmarked message. This problem is becomming more frequent, often two occurrences in a hundred message session. Before I get into just updating mutt and debian as the most likely resolutions, would like to know if this is a known problem and whether the mutt or "OS" updates are more likely to fix it. PLS don't yell at me for not being up to date, I hate updating. So now I'm paying the price. TNX Tom Fowle WA6IVG
Re: mutt 1.05 TLS socket terminated?
On Wed, Jun 26, 2019 at 12:10:06PM -0700, Kevin J. McCarthy wrote: > On Wed, Jun 26, 2019 at 10:39:01AM -0700, Tom Fowle wrote: > >Before I get into just updating mutt and debian as the most likely > >resolutions, would like to know if this is a known problem and whether the > >mutt or "OS" updates are more likely to fix it. > > No, I don't think upgrading will help with the problem. I get it too when I > use IMAP, so I more often use mbsync and work locally. > > >PLS don't yell at me for not being up to date, I hate updating. So now > >I'm paying the price. > > No yelling, but perhaps some enticing. :-) Starting with mutt 1.11.0, there > is a new config variable, $imap_qresyc, which I've tested against Fastmail. > It's still a "beta" thing, and may have some glitches, but you may want to > give it a try if you get the opportunity to upgrade. > > -- > Kevin J. McCarthy > GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA Thanks Kevin, I'll hang on to this till the number of errors makes me upgrade then try it. Tom Fowle
Re: mutt 1.05 TLS socket terminated?
On Wed, Jun 26, 2019 at 10:39:01AM -0700, Tom Fowle wrote: Before I get into just updating mutt and debian as the most likely resolutions, would like to know if this is a known problem and whether the mutt or "OS" updates are more likely to fix it. No, I don't think upgrading will help with the problem. I get it too when I use IMAP, so I more often use mbsync and work locally. PLS don't yell at me for not being up to date, I hate updating. So now I'm paying the price. No yelling, but perhaps some enticing. :-) Starting with mutt 1.11.0, there is a new config variable, $imap_qresyc, which I've tested against Fastmail. It's still a "beta" thing, and may have some glitches, but you may want to give it a try if you get the opportunity to upgrade. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
mutt 1.05 TLS socket terminated?
Using mutt 1.5.23 with Debian 8 jessie. I am getting the following problem while reading messages. approximately: "The TLS socket was improperly terminated. can not copy messages." This appears on the screen for only just long enough for my screen reader to grab it but dissappears before I can copy or check it.. I then have the usual top line menu and a blank screen. Being simplistic by nature I just exit mutt and restart but all messages which have been marked for deletion remain in the inbox and unless i have kept carefull track of the last read message number before the TLS error I have to trundle through all the previously read messages till I find the first unmarked message. This problem is becomming more frequent, often two occurrences in a hundred message session. Before I get into just updating mutt and debian as the most likely resolutions, would like to know if this is a known problem and whether the mutt or "OS" updates are more likely to fix it. PLS don't yell at me for not being up to date, I hate updating. So now I'm paying the price. TNX Tom Fowle WA6IVG
