From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: TLS problems on nnimap (emacs22 and maybe emacs23)
Date: Fri, 27 Jan 2012 14:55:15 +0100 [thread overview]
Message-ID: <yb07h0ddzcs.fsf@dod.no> (raw)
I saw this problem (at least I seem to remember that it had the same
offending commit) on emacs 23 on debian testing yesterday. But it was
more elusive there. After I had reset the bisect and had gone to head,
it went away, so I didn't report it there (I will check when I get home
that I actually correctly ended the git bisect).
Today I saw the issue on emacs22 on CentOS5.
The issue is that nnimap fails to open an IMAPS connection:
Opening connection to imap.mydomain.no via tls...
Opening TLS connection to `imap.mydomain.no'...
Opening TLS connection with `gnutls-cli --insecure -p 993 imap.mydomain.no'...failed
Opening TLS connection with `gnutls-cli --insecure -p 993 imap.mydomain.no --protocols ssl3'...failed
Opening TLS connection with `openssl s_client -connect imap.mydomain.no:993 -no_ssl2 -ign_eof'...done
Opening TLS connection to `imap.mydomain.no'...done
proto-stream-get-response: Wrong type argument: stringp, nil
git bisect tells me this:
~/git/gnus$ git bisect good
978b28444a45be09524682cacbd95fca9e9d28f5 is the first bad commit
commit 978b28444a45be09524682cacbd95fca9e9d28f5
Author: Lars Ingebrigtsen <larsi@rusty.(none)>
Date: Thu Jan 26 20:30:11 2012 +0100
Wait for :end-of-capability, not :end-of-command.
:040000 040000 29e1ce17851ae3f872f8ba5657e94089046c25fc f2ebff9b74dfbe864057207112b062e3933c02de M lisp
next reply other threads:[~2012-01-27 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 13:55 Steinar Bang [this message]
2012-01-27 15:46 ` Steinar Bang
2012-01-27 16:06 ` Lars Ingebrigtsen
2012-01-27 16:42 ` Steinar Bang
2012-01-30 21:25 ` Steinar Bang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yb07h0ddzcs.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).