MBOX-Line: From dave at cridland.net  Tue Mar 27 03:53:48 2007
To: imap-protocol@u.washington.edu
From: Dave Cridland <dave@cridland.net>
Date: Fri Jun  8 12:34:39 2018
Subject: [Imap-protocol] IMAP features: which clients use them? 
In-Reply-To: <07Mar26.165721pst."57996"@synergy1.parc.xerox.com>
References: <07Mar20.114847pst."57996"@synergy1.parc.xerox.com>
	<07Mar24.114611pst."57996"@synergy1.parc.xerox.com>
	<07Mar26.165721pst."57996"@synergy1.parc.xerox.com>
Message-ID: <6000.1174989228.195272@peirce.dave.cridland.net>

On Mon Mar 26 18:57:11 2007, Bill Janssen wrote:
> I've pushed an updated page, with some suggestions incorporated, 
> data
> folded in, and links to the appropriate RFC for each extension.
> 
> 
Looks good. Polymer does CHILDREN, too. It uses LISTEXT in preference 
to CHILDREN if available, and uses LIST-EXTENDED in preference to 
LISTEXT/CHILDREN if that's available.


> Anyone know where in IETF space the use of the IMAP protocol over 
> SSL
> is defined?  I see there's no "imaps" URI scheme in the registry.

Indeed. It's non-standard. "imaps" was largely an interim solution 
used by some whilst waiting for STARTTLS (RFC2595, then later 
incorporated into RFC3501).

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@jabber.org
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

