[Users] [Bug 3998] it simply doesn't work any more (gnutls change?)
noreply at thewildbeast.co.uk
noreply at thewildbeast.co.uk
Tue Mar 27 16:55:21 CEST 2018
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3998
--- Comment #9 from thomas.a.kaeding at gmail.com ---
This is what I got, even after generating a new self-signed
certificate for dovecot:
- Status: The certificate is NOT trusted. The certificate issuer is
unknown. The name in the certificate does not match the expected.
*** PKI verification of server certificate failed...
*** Fatal error: Error in the certificate.
*** handshake has failed: Error in the certificate.
Furthermore, the old claws-mail STILL WORKS in spite of this.
GNUTLS "down"graded to stable 3.5.18 already.
New claws-mail says:
This message can't be displayed.
This is probably due to a network error.
Use 'Network Log' in the Tools menu for more information.
Network log says:
[10:50:28] IMAP< * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR
LOGIN-REFERRALS ID ENABLE IDLE STARTTLS LOGINDISABLED] Dovecot ready.
[10:50:28] IMAP> 1 STARTTLS
[10:50:28] IMAP< 1 OK Begin TLS negotiation now.
** IMAP error on quaillake.duckdns.org: stream error
** IMAP connection broken
** Can't start STARTTLS session.
OLD claws-mail network log (no errors):
[10:51:24] IMAP4< * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR
LOGIN-REFERRALS ID ENABLE IDLE STARTTLS LOGINDISABLED] Dovecot ready.
[10:51:24] IMAP4> 1 STARTTLS
[10:51:24] IMAP4< 1 OK Begin TLS negotiation now.
* IMAP connection is un-authenticated
[10:51:34] IMAP4> 2 CAPABILITY
[10:51:34] IMAP4< * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR
LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN
[10:51:34] IMAP4< 2 OK Pre-login capabilities listed, post-login
capabilities have more.
[10:51:34] IMAP4> Logging kaeding to quaillake.duckdns.org using LOGIN
[10:51:34] IMAP4< Logged in
[10:51:34] IMAP4< Login to quaillake.duckdns.org successful
[10:51:34] IMAP4> 4 LIST "" ""
[10:51:34] IMAP4< * LIST (\Noselect) "/" ""
[10:51:34] IMAP4< 4 OK List completed (0.000 + 0.000 secs).
[10:51:34] IMAP4> 5 STATUS INBOX (MESSAGES UIDNEXT UIDVALIDITY UNSEEN)
[10:51:34] IMAP4< * STATUS INBOX (MESSAGES 36 UIDNEXT 37 UIDVALIDITY
1522128198 UNSEEN 11)
[10:51:34] IMAP4< 5 OK Status completed (0.000 + 0.000 secs).
[10:51:34] IMAP4> 6 SELECT INBOX
[10:51:44] IMAP4< * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
[10:51:44] IMAP4< * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted
\Seen \Draft \*)] Flags permitted.
[10:51:44] IMAP4< * 36 EXISTS
[10:51:44] IMAP4< * 0 RECENT
[10:51:44] IMAP4< * OK [UNSEEN 16] First unseen.
[10:51:44] IMAP4< * OK [UIDVALIDITY 1522128198] UIDs valid
[10:51:44] IMAP4< * OK [UIDNEXT 37] Predicted next UID
[10:51:44] IMAP4< * OK [HIGHESTMODSEQ 43] Highest
[10:51:44] IMAP4< 6 OK [READ-WRITE] Select completed (0.000 + 0.000 secs).
[10:51:44] IMAP4- [fetching flags...]
[10:51:44] IMAP4> 7 UID FETCH 1:* (FLAGS UID)
[10:51:44] IMAP4< [FETCH data - 1024 bytes]
[10:51:44] IMAP4< [FETCH data - 207 bytes]
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Users
mailing list