Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: nnimap ports and protocols
Date: Fri, 01 Oct 2010 20:47:19 +0200	[thread overview]
Message-ID: <m3zkuxvjgo.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87ocbdhi25.fsf@lifelogs.com>

Ted Zlatanov <tzz@lifelogs.com> writes:

> That could be mapped in the Server buffer.  We already have a standard
> way of editing forms in Gnus (server edit, topic/group parameter edit,
> etc.) so this is not a bad way, usability-wise.

Yeah, that's true.  I think that's the way to go, then.

What about questions from the tls layer about "do you want to accept
this invalid certificate from the server?" and stuff?  If that's to be
stored in the server, then open-gnutls-stream should return both the
stream and, er, something that says something about this.  Perhaps a
plist of properties, like :certificate :invalid-but-accepted or
something.

Or is that a more global thing?  "I accept this certificate" sounds a
bit more global...  and it's user-generated, too.

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




  reply	other threads:[~2010-10-01 18:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30 22:55 Lars Magne Ingebrigtsen
2010-10-01  1:00 ` Daniel Pittman
2010-10-01 13:43   ` Ted Zlatanov
2010-10-01 14:52     ` Ted Zlatanov
2010-10-01 15:19 ` Lars Magne Ingebrigtsen
2010-10-01 15:29   ` Frank Schmitt
2010-10-01 15:34     ` Lars Magne Ingebrigtsen
2010-10-01 15:46       ` Ted Zlatanov
2010-10-01 16:25         ` Lars Magne Ingebrigtsen
2010-10-01 16:45           ` Ted Zlatanov
2010-10-01 18:29             ` Lars Magne Ingebrigtsen
2010-10-01 18:41               ` Ted Zlatanov
2010-10-01 18:47                 ` Lars Magne Ingebrigtsen [this message]
2010-10-01 19:05                   ` Ted Zlatanov
2010-10-01 19:17                     ` Lars Magne Ingebrigtsen
2010-10-01 19:44                       ` Ted Zlatanov
2010-10-01 18:18           ` Sivaram Neelakantan

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=m3zkuxvjgo.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).