You are not logged in.
I get the following error message after I run mbsync -a:
Socket error: secure read from imap.domain (UUID) error:0A000126:SSL routines::unexpected eof while reading
This error appears after updating to openssl3.0 (I did full system update, so mbsync is also up to date)
Last edited by rsaavedra (2022-11-13 16:55:43)
Offline
Offline
Mine one does connect to gmail, but still I get the eof error message.
Offline
Have you tried the patch?
Offline
The error number and function implicated in the bug report are the same as those I faced a couple years ago with a previous openssl update suggesting it's a recurrence of the same problem. But the OP's error number is different, and the function name is empty / absent - so it seems a bit different.
rsaavedra, can you post the verbose output from mbsync (feel free to redact identifying information if there is any, but please specify what is redacted / replaced).
Last edited by Trilby (2022-11-12 21:37:51)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
But the OP's error number is different, and the function name is empty / absent - so it seems a bit different.
I had exactly the same error as the OP. The patch fixed it. ¯\_(ツ)_/¯
Offline
Trilby wrote:But the OP's error number is different, and the function name is empty / absent - so it seems a bit different.
I had exactly the same error as the OP. The patch fixed it. ¯\_(ツ)_/¯
Yeah, reading more about the patch I guess it should work.
To be honest I don't know how to patch.
Should I uninstall the current openssl and then rebuild by myself together with the patch?
Then what would happen on next update?
Perhaps it is better idea if I just wait until they update the archlinux repository...
Offline
The error number and function implicated in the bug report are the same as those I faced a couple years ago with a previous openssl update suggesting it's a recurrence of the same problem. But the OP's error number is different, and the function name is empty / absent - so it seems a bit different.
rsaavedra, can you post the verbose output from mbsync (feel free to redact identifying information if there is any, but please specify what is redacted / replaced).
Here is verbose output:
Reading configuration file /home/USER/.mbsyncrc
C: 0/1 B: 0/1 F: +0/0 *0/0 #0/0 N: +0/0 *0/0 #0/0
Channel EMAILADDR@gmail.com
Opening far side store EMAILADDR@gmail.com-remote...
Resolving imap.gmail.com... ok
Connecting to imap.gmail.com (IPADDR)...
Opening near side store EMAILADDR@gmail.com-local...
Connection is now encrypted
Logging in...
Opening far side box INBOX...
Opening near side box INBOX...
Loading far side box...
Loading near side box...
near side: N messages, 0 recent
far side: N messages, 0 recent
Synchronizing...
C: 1/1 B: 1/1 F: +0/0 *0/0 #0/0 N: +0/0 *0/0 #0/0
Socket error: secure read from imap.gmail.com (IPADDR): error:0A000126:SSL routines::unexpected eof while reading
Offline
jasonwryan wrote:Trilby wrote:But the OP's error number is different, and the function name is empty / absent - so it seems a bit different.
I had exactly the same error as the OP. The patch fixed it. ¯\_(ツ)_/¯
Yeah, reading more about the patch I guess it should work.
To be honest I don't know how to patch.
Should I uninstall the current openssl and then rebuild by myself together with the patch?
Then what would happen on next update?
Perhaps it is better idea if I just wait until they update the archlinux repository...
No, you use ABS to rebuild isync with the patch applied. https://wiki.archlinux.org/title/Arch_Build_System It is pretty straightforward...
Or you could just wait for the next version.
Offline
No, you use ABS to rebuild isync with the patch applied. https://wiki.archlinux.org/title/Arch_Build_System It is pretty straightforward...
Or you could just wait for the next version.
Thank you.
I got lost with all the svn instructions, I prefer git and the patch command.
Besides, I am afraid to break things with this one.
I guess I just wait for the update..
Offline
Asp uses git. And you can't really break anything. If the patched version fails for some reason, you can just install the current version again.
Offline