[Users] [Bug 4227] ClawsMail IMAP to Verizon email imap.aol.com started failing with *** SSL/TLS handshake failed

[noreply at thewildbeast.co.uk]

https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4227

--- Comment #5 from joesalmeri at verizon.net ---
(In reply to comment #3)
> "What can I do to debug the problem further?"
> 
> Are you running with logging at debug level?
> 
> If not, that might be worth a try.
> 
> https://www.claws-mail.org/faq/index.php/Claws_Mail_on_Windows

Thanks, I just tried that and reviewed the log.

Everything seems to be working fine in the initial part that reads the
files/etc up to the point where it makes the IMAP connection.

Here is that part of the log

imap.c:4824:getting session...
message: Account 'Joe - Verizon': Connecting to IMAP server:
imap.aol.com:993...
imap-thread.c:447:found imap 000002915787E450
imap-thread.c:463:generic_cb
imap-thread.c:447:found imap 000002915787E450
imap-thread.c:702:connect 43 with imap 000002915787E450
warning: [12:28:01] SSL/TLS handshake failed
alertpanel.c:253:Creating alert panel dialog...
alertpanel.c:211:called inc_lock (lock count 2)
alertpanel.c:221:called inc_unlock (lock count 1)
alertpanel.c:105:return value = 0
folder.c:2183:Scanning folder Inbox for cache changes.
imap.c:4587:get_num_list
imap.c:4597:get_num_list: nothing to update
imap.c:4604:don't know the list length...
imap.c:4623:getting session...
folder.c:2187:Error fetching list of message numbers
folderview.c:1260:called inc_unlock (lock count 0)
file-utils.c:58:TIMING : 0s010ms

I do't really see any addition details in that do you?

Other things I've tried since your message were to setup a VM with a clean
installation of Win10, install ClawsMail and config for the IMAP account to
eliminate everything else config wise.

That setup gets the same error.

I just installed sylpheed on this machine and configured the verizon IMAP
account and sylpheed works fine and does not have the issue so it appears that
something with the SSL negotiation for ClawsMail only is having an issue.  

I also setup the Windows 10 email app for the Verizon IMAP and it works.

And lastly I wrote a quick test program in Python using imaplib and it also
connects to the verizon IMAP and that works fine.

Basically everything except Clawsmail works and does not have the IMAP issues.  

It's weird that it just started happening as clawsmail has worked fine for
years.

I suspect that something is wrong in the negotiation phase that has to do with
the getting the certificate.

Since the clean install still fails with the error and since sylpheed works
fine it definitely seems to be a bug in Clawsmail.

What else can I do to assist in debugging and getting this addressed?

Thanks for your help!

Joe

-- 
You are receiving this mail because:
You are the assignee for the bug.