Gnus development mailing list
 help / color / mirror / Atom feed
From: Bruno Tavernier <tavernier.bruno@gmail.com>
To: gnus <ding@gnus.org>
Subject: Re: nnimap ignoring server options?
Date: Tue, 12 Oct 2010 13:00:51 +0900	[thread overview]
Message-ID: <878w243vrg.fsf@gmail.com> (raw)
In-Reply-To: <m3d3rgehdh.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 11 Oct 2010 20:03:54 +0200")


Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Andrew J Cosgriff <ajc@polydistortion.net> writes:
>
>> (nnimap "some.host.name"
>> 	(nnimap-address "10.x.y.z")
>> 	(nnimap-server-port imap)
>> 	(nnimap-stream network))
>>
>> ...but it seems that these configured things are never used - for
>> instance, if I change nnimap-address to be "localhost", I still see Gnus
>> saying in the echo area that it's making a TLS connection to
>> some.host.name instead.
>
> Are you sure that that's the server definition the groups use?  `G E' on
> a group to have a look.

I think the culprit is that Gnus force starttls if the server is
starttls capable. No matter if `nnimap-stream' is set to network.
Connecting from a vpn, ssh or localhost to a starttls capable server
*always* enable starttls.

I am refering to this portion of the code in nnimap.el
,----
| ;; If this is a STARTTLS-capable server, then sever the
| ;; connection and start a STARTTLS connection instead.
| (cond
|  ((and (or (and (eq nnimap-stream 'network)
|   (member "STARTTLS"
|    (nnimap-capabilities nnimap-object)))
`----

Could we assume that users who set (nnimap-stream network) know what
they're doing? :-)

-- 
Bruno



  parent reply	other threads:[~2010-10-12  4:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11  1:30 Andrew J Cosgriff
2010-10-11 18:03 ` Lars Magne Ingebrigtsen
2010-10-11 21:19   ` Andrew J Cosgriff
2010-10-12 12:43     ` Lars Magne Ingebrigtsen
2010-10-13 22:33       ` Andrew J Cosgriff
2010-10-13 22:59         ` Lars Magne Ingebrigtsen
2010-10-14 23:29           ` Andrew J Cosgriff
2010-10-15  7:43             ` Lars Magne Ingebrigtsen
2010-10-15  9:53               ` Andrew J Cosgriff
2010-10-15 14:02                 ` Lars Magne Ingebrigtsen
2010-10-17 21:54                   ` Andrew J Cosgriff
2010-10-17 22:00                     ` Lars Magne Ingebrigtsen
2010-10-18 21:07                       ` Andrew J Cosgriff
2010-10-18 21:59                         ` Lars Magne Ingebrigtsen
2010-10-18 23:47                           ` Andrew J Cosgriff
2010-10-18 23:52                             ` Lars Magne Ingebrigtsen
2010-10-19  0:41                               ` Katsumi Yamaoka
2010-10-19 17:52                                 ` Lars Magne Ingebrigtsen
2010-10-19 18:36                                 ` Andreas Schwab
2010-10-19 18:30                               ` Andreas Schwab
2010-10-19 14:13                           ` Ted Zlatanov
2010-10-19 17:54                             ` Lars Magne Ingebrigtsen
2010-10-19 18:28                               ` Ted Zlatanov
2010-10-19 18:30                                 ` Lars Magne Ingebrigtsen
2010-10-12  4:00   ` Bruno Tavernier [this message]
2010-10-12  8:23     ` Andrew J Cosgriff
2010-10-12 12:43     ` Lars Magne Ingebrigtsen

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=878w243vrg.fsf@gmail.com \
    --to=tavernier.bruno@gmail.com \
    --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).