error:0A000126:SSL routines
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
isync (Ubuntu) |
Fix Released
|
Undecided
|
Sergio Durigan Junior | ||
Jammy |
Fix Released
|
Undecided
|
Sergio Durigan Junior | ||
Kinetic |
Fix Released
|
Undecided
|
Sergio Durigan Junior | ||
Lunar |
Fix Released
|
Undecided
|
Sergio Durigan Junior |
Bug Description
[ Impact ]
Users who rely on isync/mbsync to fetch emails from certain IMAP servers may experience the following error after the synchronization finishes:
Socket error: secure read from imap.gmail.com ([2607:
This does not happen with all email providers (only with those that fail to send a close notification before closing the TCP socket), but can be easily reproduced with Gmail and (apparently) Outlook.
[ Test Plan ]
One needs to have a Gmail/Outlook email account in order to reproduce this problem. The following ~/.mbsyncrc file should be adjusted accordingly, and is enough to reproduce the problem:
# cat ~/.mbsyncrc
Create Near
IMAPAccount gmail
Host imap.gmail.com
Port 993
User <email address hidden>
Pass YOUPASSWORD
SSLType IMAPS
IMAPStore gmail-remote
Account gmail
MaildirStore gmail-local
Path ~/Mail/gmail/
INBOX ~/Mail/gmail/INBOX
SubFolders Verbatim
Channel gmail
Far :gmail-remote:
Near :gmail-local:
Create Both
# mkdir -p ~/Mail/gmail
# mbsync -a
[ Where problems could occur ]
The upstream patch being backported isn't part of an official release yet; as such, the test coverage for it is reduced. The good news is that other distributions (Arch Linux, for example) have already backported the patch and released a version of their package with it.
The change is well contained and just handles the case when the expected EOF doesn't come. The software is now more flexible when it comes to accepting TLS connections that are not properly closed, but that should not affect the correct behaviour performed by other servers.
[ Original Description ]
I have been using isync with our corporate mail at outlook.
After upgrade from 20.04 to 20.04 after every syncronisation mbsync produces a message
Socket error: secure read from outlook.
The sync seems to work fine, so I do not know if this is a real error or just a
forgotten error message.. Any help would be appreciated. Thank you!
Changed in isync (Ubuntu Lunar): | |
status: | New → In Progress |
Changed in isync (Ubuntu Kinetic): | |
assignee: | nobody → Sergio Durigan Junior (sergiodj) |
Changed in isync (Ubuntu Jammy): | |
assignee: | nobody → Sergio Durigan Junior (sergiodj) |
status: | New → Triaged |
Changed in isync (Ubuntu Kinetic): | |
status: | New → Triaged |
description: | updated |
Changed in isync (Ubuntu Jammy): | |
status: | Triaged → In Progress |
Changed in isync (Ubuntu Kinetic): | |
status: | Triaged → In Progress |
description: | updated |
Thanks for the bug report.
This is also affecting me, and I believe it's actually a problem with openssl. I'm investigating and will post my results later.