Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: Leee on October 27, 2024, 05:50:01 AM
-
I'm trying to configure mutt for IMAP and SMTP and I've got it working for receiving but when I try to send an email I get the following error:
SSL failed: error:1408F10B:SSL routines:ssl3_get_record:wrong version numberI wonder if mutt needs to be recompiled for the latest ssl libraries?
I'm using Tiny Core 15.0 on x86_64
Note: This is the first time I've ever even come close to getting mutt to work (and I've been fooling with it, very occasionally, for many years) so I may just have something horribly wrong. Right now, I'm following the procedures in this youtube video: https://www.youtube.com/watch?v=2jMInHnpNfQ (https://www.youtube.com/watch?v=2jMInHnpNfQ)
Is anyone using mutt successfully?
-
a humble request. i also have kicked mutt around(very briefly a few times over the last couple of decades) and would really appreciate any clues you find and/or are willing to share. thanks!
-
It's possible that mutt needs openssl-1.1.1 - what does this give:
ldd /usr/local/bin/mutt
-
usually when i search and get directed to stackoverflow i look for topics that have lots of action. this one is at 349 currently(not saying it will provide the answer but maybe some clues?)
https://stackoverflow.com/questions/50840101/curl-35-error1408f10bssl-routinesssl3-get-recordwrong-version-number
DDG gave two hits for "mutt" and "SSL failed: error:1408F10B:SSL routines:ssl3_get_record:wrong version number"
https://github.com/neomutt/neomutt/issues/1035
https://github.com/poolpOrg/poolp.org/discussions/106
20241027-0655am-cdt-usa-modified: added more links
-
mutt dep file adjusted
-
mutt dep file adjusted
Thanks... though it looks like that wasn't the whole issue since I had already had openssl-1.1.1.tcz loaded as a dependency of something else.
Thanks to the links provided by @gadget42, I found thesolution to be that, in muttrc, the smtp_url value has to start with smtp:// instead of smtps:// even though the server port is 993 and not 25. This leaves me with some doubt as to the security of the connection, though I'm -mostly- sure it is actually using ssl.
re. ldd ...tc@dolly:~$ ldd /usr/local/bin/mutt
linux-vdso.so.1 (0x00007ffccc7db000)
libsqlite3.so.0 => /usr/local/lib/libsqlite3.so.0 (0x00007f85f1964000)
libncursesw.so.6 => /usr/local/lib/libncursesw.so.6 (0x00007f85f190f000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f85f18f9000)
libssl.so.1.1 => /usr/local/lib/libssl.so.1.1 (0x00007f85f187e000)
libcrypto.so.1.1 => /usr/local/lib/libcrypto.so.1.1 (0x00007f85f15f8000)
libsasl2.so.3 => /usr/local/lib/libsasl2.so.3 (0x00007f85f15de000)
libgdbm.so.6 => /usr/local/lib/libgdbm.so.6 (0x00007f85f15cc000)
libidn2.so.0 => /usr/local/lib/libidn2.so.0 (0x00007f85f1200000)
libunistring.so.2 => /usr/local/lib/libunistring.so.2 (0x00007f85f0e00000)
libgpgme.so.11 => /usr/local/lib/libgpgme.so.11 (0x00007f85f158f000)
libassuan.so.0 => /usr/local/lib/libassuan.so.0 (0x00007f85f157e000)
libgpg-error.so.0 => /usr/local/lib/libgpg-error.so.0 (0x00007f85f1561000)
libc.so.6 => /lib/libc.so.6 (0x00007f85f0c0d000)
libm.so.6 => /lib/libm.so.6 (0x00007f85f149b000)
libdl.so.2 => /lib/libdl.so.2 (0x00007f85f1496000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f85f1491000)
libresolv.so.2 => /lib/libresolv.so.2 (0x00007f85f1482000)
/lib/ld-linux-x86-64.so.2 (0x00007f85f1a63000)
tc@dolly:~$
-
Thanks to both of you for your help with this.
My long-term inability to get mutt configured correctly was a tiny little thorn in my side for a -very- long time, but it's better now. :)