From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/87777 Path: news.gmane.org!.POSTED!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.gnus.general Subject: Re: new (?) version of the old nnml problem Date: Fri, 20 Oct 2017 20:40:21 +0200 Message-ID: <86lgk5zmqy.fsf@zoho.com> References: <86wp3p28u5.fsf@zoho.com> <86shed284o.fsf@zoho.com> <86o9p127p4.fsf@zoho.com> <8760b9kewf.fsf@ericabrahamsen.net> <86376d24n7.fsf@zoho.com> <87wp3piytm.fsf@ericabrahamsen.net> <86tvytzqtp.fsf@zoho.com> <87vaj94ss4.fsf@ericabrahamsen.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1508524936 28789 195.159.176.226 (20 Oct 2017 18:42:16 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 20 Oct 2017 18:42:16 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) To: ding@gnus.org Original-X-From: ding-owner+m35991@lists.math.uh.edu Fri Oct 20 20:42:12 2017 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from mxfilter-048035.atla03.us.yomura.com ([107.189.48.35]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e5cFA-0005mH-1g for ding-account@gmane.org; Fri, 20 Oct 2017 20:42:04 +0200 X-Yomura-MXScrub: 1.0 Original-Received: from lists1.math.uh.edu (unknown [129.7.128.208]) by mxfilter-048035.atla03.us.yomura.com (Halon) with ESMTPS id 5475a1a3-b5c6-11e7-b60e-b499baabecb2; Fri, 20 Oct 2017 18:41:48 +0000 (UTC) Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.87) (envelope-from ) id 1e5cEH-0003xV-L1; Fri, 20 Oct 2017 13:41:09 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1e5cED-0003wj-Mm for ding@lists.math.uh.edu; Fri, 20 Oct 2017 13:41:05 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.87) (envelope-from ) id 1e5cEC-0002X7-93 for ding@lists.math.uh.edu; Fri, 20 Oct 2017 13:41:05 -0500 Original-Received: from [195.159.176.226] (helo=blaine.gmane.org) by quimby.gnus.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1e5cE9-00032t-Kw for ding@gnus.org; Fri, 20 Oct 2017 20:41:01 +0200 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1e5cDp-00053V-Jy for ding@gnus.org; Fri, 20 Oct 2017 20:40:41 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: ding@gnus.org Original-Lines: 56 Original-X-Complaints-To: usenet@blaine.gmane.org Mail-Copies-To: never Cancel-Lock: sha1:tpizz0A7JxPxwxPTpYZDcCiE4Pc= List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:87777 Archived-At: Eric Abrahamsen wrote: > the two programs are roughly equivalent: they > handle creating and checking TLS > certificates, and creating and handling > TLS-encrypted connections to remote servers. OK, then how do I specify openssl should be used instead? Worth a shot... A search with `apropos-value' and "gnutls" reveals starttls-gnutls-program "gnutls-cli" tls-program ("gnutls-cli --insecure -p %p %h" "gnutls-cli --insecure -p %p %h --protocols ssl3" "openssl s_client -connect %h:%p -no_ssl2 -ign_eof") Neither set by me, but can be incorrect anyway, of course. Eheh. > I actually was just assuming you are using > gnutls, you can probably check the > libgnutls-version. If you mean ... then: $ gnutls-cli --version gnutls-cli 3.3.8 > You can also try setting gnutls-log-level to > 3 or 4 and fetching mail, and see if anything > interesting pops up in *Messages*. This does, over and over again: gnutls.c: [3] ASSERT: gnutls_buffers.c:547 gnutls.c: [3] (Emacs) retry: Resource temporarily unavailable, try again. gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable, try again. gnutls.c: [3] ASSERT: gnutls_buffers.c:1104 > The bad news is that I tried this: > > gnutls-cli --port 995 pop.zoho.com > > And it connected just fine. You might try > that, and going through with the > login procedure. Login procedure works, the rest seems fine (?). -- underground experts united http://user.it.uu.se/~embe8573