Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Debugging Emacs Gnus to determine the starttls command working with No Gnus
Date: Thu, 07 Oct 2010 22:06:10 +0200	[thread overview]
Message-ID: <m3bp757op9.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <7b53d541c6e42c68a4855cbf60d17682@hcoop.net>

JJ <ding_gnus.org@sumou.com> writes:

> (setq gnus-select-method '(nnnil))
> (setq gnus-secondary-select-methods '((nnimap "mail.hcoop.net"
> 				   (nnimap-address "mail.hcoop.net")
> 			           (nnir-search-engine imap))))

This probably means that you're using TLS and not STARTTLS, so
tls-program is used.

> So I assume it's using tls;
> tls-program is ("gnutls-cli -p %p %h" "gnutls-cli -p %p %h --protocols
> ssl3" "openssl s_client -connect %h:%p -no_ssl2 -ign_eof") which means I
> have it set to default, i.e. hasn't been modified by anything.
>
> And that's what I need to decipher, which of these with which port the
> GNU Emacs Gnus uses to connect, as it connects.

Since it's TLS, it's port 993.  If you want STARTTLS, you should
probably say `(nnimap-stream starttls)', which will make it connect to
the normal imap port instead of imaps.

nnimap should do some probing, however, to automate this.

> So how can I determine which command exactly it is using to connect, so
> that I may set it explicitly and can use the Git Gnus, until tls is used
> internally?

gnutls-cli is probably failing because you're not using --insecure, so
it's falling through to the openssl s_client, would be my guess.  Do you
have that installed?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




  reply	other threads:[~2010-10-07 20:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 15:59 JJ
2010-09-29 19:19 ` Lars Magne Ingebrigtsen
2010-10-06 14:33   ` JJ
2010-10-07 20:06     ` Lars Magne Ingebrigtsen [this message]
2010-10-20  9:25       ` JJ

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=m3bp757op9.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --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).