imap.sonic.net connect error (aka no email)

[mball]

wtf now?

Code: Select all

gnutls_handshake: A TLS packet with unexpected length was received.

mutt running on home computer.
For the previous week or so there has been an error message (presumably the same one) on the 1st attempt to connect, but on 2nd attempt connect would go on to authentication as normal. Something changed 2 or 3 days ago.

[gkeller]

We updated the frontend mail servers in our cluster 6 days ago. I haven't noticed any issues with mutt connecting to the new hosts, would you mind sharing your config and mutt version?

[mball]

Code: Select all

System: Linux 2.6.43.8-1.fc15.x86_64 (x86_64)
ncurses: ncurses 5.8.20110319 (compiled with 5.8)
libidn: 1.19 (compiled with 1.19)
hcache backend: tokyocabinet 1.4.46
Compile options:
-DOMAIN
-DEBUG
-HOMESPOOL  -USE_SETGID  -USE_DOTLOCK  -DL_STANDALONE  +USE_FCNTL  -USE_FLOCK   
+USE_POP  +USE_IMAP  +USE_SMTP  
-USE_SSL_OPENSSL  +USE_SSL_GNUTLS  +USE_SASL  +USE_GSS  +HAVE_GETADDRINFO  
+HAVE_REGCOMP  -USE_GNU_REGEX  
+HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET  
+HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM  
+CRYPT_BACKEND_CLASSIC_PGP  +CRYPT_BACKEND_CLASSIC_SMIME  -CRYPT_BACKEND_GPGME  
-EXACT_ADDRESS  -SUN_ATTACHMENT  
+ENABLE_NLS  -LOCALES_HACK  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET  +HAVE_LANGINFO_YESEXPR  
+HAVE_ICONV  -ICONV_NONTRANS  +HAVE_LIBIDN  +HAVE_GETSID  +USE_HCACHE  
ISPELL="/usr/bin/hunspell"
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/etc"
EXECSHELL="/bin/sh"
-MIXMASTER

Was dss or rsa encryption from the new servers?

[mike.ely]

Hi there. Thanks for responding to Grant. The first thing that jumps out to me is literally the first line of output you pasted:

Code: Select all

System: Linux 2.6.43.8-1.fc15.x86_64 (x86_64)

It's been a good while since I've seen Fedora Core 15 anywhere - congratulations on maintaining that level of stability!

The new IMAP frontend servers are running Rocky 9 which has OpenSSL 3.2.x, whereas FC15 would have been either 1.0.x or 1.1.x. While we could (and will, if you wish) compare cipher compatibility it's almost certain that the root cause here is going to be a lack of current cipher support on the part of FC15. Given that, my advice would be to either bring in a new OpenSSL version and then compile mutt against it or perhaps upgrade to a more recent distro release.

I apologize for the inconvenience.

[kgc]

Moreover, Fedora Core 15 has been End of Life for more than a decade.
https://docs.fedoraproject.org/en-US/releases/eol/

I *strongly* encourage you to upgrade the OS. Even mutt is laden with exploits that have been fixed since then.

https://nvd.nist.gov/vuln/search/result ... arch=false

[mball]

Looks like timeout really did eat my earlier reply.

Yeah, FC16 is old, almost as old as the Dell E520N its running on. Many attempts at something new. Always a fight. One which I lose.

Probably give y'all a coronary, but I just put back into service RedHat 9 (Shrike). Fun fact: with RH9 my daily 40:40 long video takes 41-43 minutes to play and 54+ minutes with Debian 12 even though the hardware (TP770zx) is slightly slower (TP770xz).

[rant]
Wouldn't even be tying to run mutt at home if sonic hadn't killed its shell. Run mutt there, run mutt here--no problem. Wrong. Problems beyond this TLS issue.
At least there's webmail so I at least know when to walk to the PO to get my real mail.
[/rant]