[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 #6 from joesalmeri at verizon.net ---
(In reply to comment #4)
> (In reply to comment #2)
> > A few other things I've tried
> > 
> > Changing the SSL config from SSL/TLS to StartTLS (which has not been needed
> > in the past)
> > 
> > UnChecking the "Use non-blocking SSL/TLS" setting
> > 
> > 
> > It still fails after trying both of those settings.
> > 
> > When StartTLS is selected there is a longer delay before the failure message
> > occurs, whereas when it is set to SSL/TLS the failure is almost immediate.
> 
> Have you tried to search for the certificate in Tools -> SSL/TLS
> certificates ?
> 
> Perhaps remove the certificate and the readd it at next logon.

Hi Michael,

Please see my detailed reply to DJH regarding additional debugging.

The quick summary is that in a VM which is a clean install of Windows 10 and
then installing Clawsmail produces the same error I reported.

Also, installing sylpheed on the same machine works fine and does not get the
IMAP error.

I do think you are on to something though because in the Win10 clean install
when I look in the Tools -> SSL/TLS certificates it does not have any, which to
me indicates the point in the connection attempt where the failure is
occurring.

I just tried your suggestion and removed the Verizon certifications (that's all
of the certifications so now there are none listed) and then ran clawsmail with
--debug.

Here is the relevant part of that debug log:

imap.c:4824:getting session...
message: Account 'Joe - Verizon': Connecting to IMAP server:
imap.aol.com:993...
imap-thread.c:447:found imap 0000025DA754C7C0
imap-thread.c:463:generic_cb
imap-thread.c:447:found imap 0000025DA754C7C0
imap-thread.c:702:connect 43 with imap 0000025DA754C7C0
warning: [12:56:00] 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 : 0s008ms

So, it looks like the IMAP connection occurs

imap-thread.c:702:connect 43 with imap 0000025DA754C7C0

but then when it attempts to get the certificate that fails which is why after
testing out your suggestion there are no certificates installed.

I know that clawsmail was forked from sylpheed and that they have gone off in
their own directions now but possible the source code between the two could be
reviewed for differences to see what is different and why sylpheed works and
clawsmail stopped working?

Are there any other things I can do on this end to help debug further or
provide more details?

Thanks for your help!

Joe

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