Received: from cnri by ietf.org id aa05842; 31 Oct 96 19:20 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa25501; 31 Oct 96 19:20 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id PAA21814 for imap-out; Thu, 31 Oct 1996 15:50:31 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from aminet.co.kr (aminet.co.kr [202.30.143.20]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id PAA21798 for ; Thu, 31 Oct 1996 15:50:22 -0800 Received: from bcpark ([205.219.121.64]) by aminet.co.kr (8.6.12h2/8.6.12) with SMTP id IAA27151 for ; Fri, 1 Nov 1996 08:49:26 +0900 To: IMAP@cac.washington.edu Subject: subscribe From: =?EUC-KR?B?udq6tML5?= Date: Fri, 01 Nov 1996 08:49:10 -0800 Message-ID: <16614.846866950@bcpark> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit Please, send me any information about IMAP...   Received: from cnri by ietf.org id aa27751; 1 Nov 96 14:53 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa18482; 1 Nov 96 14:53 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id KAA10379 for imap-out; Fri, 1 Nov 1996 10:58:57 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from feyuri.microsoft.com (feyuri.microsoft.com [131.107.243.53]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id KAA10375 for ; Fri, 1 Nov 1996 10:58:55 -0800 Message-Id: <199611011858.KAA10375@mx2.cac.washington.edu> Received: by FEYURI with IMAIL 2.0 id <01BBC7E3.AF8BA9D0@FEYURI>; Fri, 1 Nov 1996 10:58:59 -0800 From: "Larry Osterman (Exchange)" To: imap@cac.washington.edu, 'John Gardiner Myers' Subject: RE: IMAP and SSL Date: Fri, 1 Nov 1996 10:58:55 -0800 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (4.5.1353.4) Content-Type: text/plain; charset="iso-8859-1" Why bother - what does that give us that the current AUTHENTICATE command does not? Larry Osterman Sent from a Dell OptiPlex GXM 5166, running NT 4.0, via Exchange 4.5. Please notify the sender of any difficulties > ---------- > From: > owner-imap@cac.washington.edu[SMTP:owner-imap@cac.washington.edu] on > behalf of John Gardiner Myers[SMTP:jgm@CMU.EDU] > Sent: Friday, November 1, 1996 10:27 AM > To: imap@cac.washington.edu > Subject: Re: IMAP and SSL > > And there's option three: > > 3) Define a new command for "turning on" SSL on the > current connection. > > -- > _.John Gardiner Myers Internet: jgm+@CMU.EDU > LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up > >   Received: from cnri by ietf.org id aa28656; 1 Nov 96 15:07 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa18887; 1 Nov 96 15:07 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id KAA03085 for imap-out; Fri, 1 Nov 1996 10:27:48 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from po10.andrew.cmu.edu (PO10.ANDREW.CMU.EDU [128.2.10.110]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id KAA03081 for ; Fri, 1 Nov 1996 10:27:44 -0800 Received: (from postman@localhost) by po10.andrew.cmu.edu (8.8.2/8.8.0) id NAA00794 for imap@cac.washington.edu; Fri, 1 Nov 1996 13:27:41 -0500 Received: via switchmail; Fri, 1 Nov 1996 13:27:40 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Fri, 1 Nov 1996 13:27:29 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Fri, 1 Nov 1996 13:27:27 -0500 (EST) Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.54 via MS.5.6.hogtown.andrew.cmu.edu.sun4_51; Fri, 1 Nov 1996 13:27:25 -0500 (EST) Message-ID: <0mSY4Ba00WBw0L3Rs0@andrew.cmu.edu> Date: Fri, 1 Nov 1996 13:27:25 -0500 (EST) From: John Gardiner Myers To: imap@cac.washington.edu Subject: Re: IMAP and SSL In-Reply-To: <199610310127.RAA18734@mx1.cac.washington.edu> References: <199610310127.RAA18734@mx1.cac.washington.edu> And there's option three: 3) Define a new command for "turning on" SSL on the current connection. -- _.John Gardiner Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up   Received: from cnri by ietf.org id aa11263; 1 Nov 96 17:49 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa22879; 1 Nov 96 17:49 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id OAA08841 for imap-out; Fri, 1 Nov 1996 14:05:25 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from moon.nbn.com (moon.nbn.com [199.4.65.1]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id OAA08819 for ; Fri, 1 Nov 1996 14:05:06 -0800 Received: from candle.brasslantern.com (srf-70.nbn.com [199.4.64.70]) by moon.nbn.com (8.7.3/8.7.3) with ESMTP id OAA01703 for ; Fri, 1 Nov 1996 14:04:49 -0800 (PST) Received: (from schaefer@localhost) by candle.brasslantern.com (8.6.12/8.6.12) id OAA18969 for imap@cac.washington.edu; Fri, 1 Nov 1996 14:08:09 -0800 From: Bart Schaefer Message-Id: <961101140808.ZM18968@candle.brasslantern.com> Date: Fri, 1 Nov 1996 14:08:08 -0800 Reply-To: schaefer@nbn.com X-Mailer: Z-Mail (4.0b.820 20aug96) To: IMAP Interest List Subject: Unilateral UIDVALIDITY response codes? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Section 7.1, Server Responses - Status Responses, lists OPTIONAL response codes that MAY appear in any tagged or untagged status response (OK, NO, BAD, PREAUTH and BYE). One of those response codes is UIDVALIDITY. Although the usage of UIDVALIDITY is described only in conjuction with responses to SELECT, EXAMINE, and STATUS commands, its appearance in the list in section 7.1 raises the spectre that a server might unilaterally include a new UIDVALIDITY code in *any* OK, NO, or BAD response to *any* command. Is it really intended that this be possible? If not, should that point be clarified in section 7.1 (possibly with similar clarifications for other response codes)? If so, how should a reasonable client be expected to react? -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.nbn.com/people/lantern   Received: from cnri by ietf.org id aa17223; 1 Nov 96 18:49 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa23900; 1 Nov 96 18:49 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id PAA10545 for imap-out; Fri, 1 Nov 1996 15:13:18 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id PAA10541 for ; Fri, 1 Nov 1996 15:13:16 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id PAA22716; Fri, 1 Nov 1996 15:13:06 -0800 (PST) Date: Fri, 1 Nov 1996 14:24:36 -0800 (PST) From: Mark Crispin Subject: re: Unilateral UIDVALIDITY response codes? To: schaefer@nbn.com cc: IMAP Interest List In-Reply-To: <961101140808.ZM18968@candle.brasslantern.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 1 Nov 1996 14:08:08 -0800, Bart Schaefer wrote: > Although the usage of UIDVALIDITY is described only in conjuction with > responses to SELECT, EXAMINE, and STATUS commands, its appearance in the > list in section 7.1 raises the spectre that a server might unilaterally > include a new UIDVALIDITY code in *any* OK, NO, or BAD response to *any* > command. Ugh. What an ugly prospect! *What* it means seems clear; the validity of UIDs has changed, and all previous knowledge of UIDs is invalidated. However, that is prohibited by the text of the last paragraph of 2.3.1.1 on page 5 of draft 07: The unique identifier of a message MUST NOT change during the session, and SHOULD NOT change between sessions. [...] I would treat an unexpected UIDVALIDITY as this: for some reason, the server decided to change the UIDVALIDITY value. However, by the rule in 2.3.1.1. all of the UIDs are unchanged, so they must carry over to this new UIDVALIDITY. So, just note the change in value, and continue as if nothing happened.   Received: from cnri by ietf.org id aa10436; 4 Nov 96 13:15 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa17115; 4 Nov 96 13:15 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id JAA06451 for imap-out; Mon, 4 Nov 1996 09:13:24 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from po10.andrew.cmu.edu (PO10.ANDREW.CMU.EDU [128.2.10.110]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id JAA06438 for ; Mon, 4 Nov 1996 09:13:19 -0800 Received: (from postman@localhost) by po10.andrew.cmu.edu (8.8.2/8.8.0) id MAA00819 for imap@cac.washington.edu; Mon, 4 Nov 1996 12:13:15 -0500 Received: via switchmail; Mon, 4 Nov 1996 12:13:13 -0500 (EST) Message-ID: Received: from johnstown.andrew.cmu.edu via qmail ID ; Mon, 4 Nov 1996 12:11:52 -0500 (EST) Received: from johnstown.andrew.cmu.edu via qmail ID ; Mon, 4 Nov 1996 12:11:49 -0500 (EST) Date: Mon, 4 Nov 1996 12:11:49 -0500 (EST) From: Derrick J Brashear To: imap@cac.washington.edu Subject: buglet in imap-4 toolkit final release The auth drivers in the final release of the imap-4 toolkit do not work with a Kerberos-capable Cyrus server, for instance; The following diff to src/c-client/imap4.c fixes that. *** imap4.c~ Mon Nov 4 12:10:01 1996 --- imap4.c Mon Nov 4 12:03:11 1996 *************** *** 1990,1996 **** if (!strcmp (t,"IMAP4")) LOCAL->imap4 = T; else if (!strcmp (t,"STATUS")) LOCAL->use_status = T; else if (!strcmp (t,"SCAN")) LOCAL->use_scan = T; ! else if (!strncmp (t,"AUTH-",5) && (i = mail_lookup_auth_name (t+5)) && (--i < MAXAUTHENTICATORS)) LOCAL->use_auth |= (1 << i); /* ignore other capabilities */ } --- 1990,1996 ---- if (!strcmp (t,"IMAP4")) LOCAL->imap4 = T; else if (!strcmp (t,"STATUS")) LOCAL->use_status = T; else if (!strcmp (t,"SCAN")) LOCAL->use_scan = T; ! else if (!strncmp (t,"AUTH=",5) && (i = mail_lookup_auth_name (t+5)) && (--i < MAXAUTHENTICATORS)) LOCAL->use_auth |= (1 << i); /* ignore other capabilities */ } -D   Received: from cnri by ietf.org id aa14638; 4 Nov 96 14:32 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa19201; 4 Nov 96 14:32 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id KAA08553 for imap-out; Mon, 4 Nov 1996 10:34:52 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id KAA08545 for ; Mon, 4 Nov 1996 10:34:48 -0800 Received: from Ikkoku-Kan.Panda.COM (UW-Gateway.Panda.COM [192.107.14.65]) by mailhost2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id KAA29671; Mon, 4 Nov 1996 10:34:42 -0800 Date: Mon, 4 Nov 1996 10:28:47 -0800 (PST) From: Mark Crispin Subject: re: buglet in imap-4 toolkit final release To: Derrick J Brashear cc: imap@cac.washington.edu In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 4 Nov 1996 12:11:49 -0500 (EST), Derrick J Brashear wrote: > The auth drivers in the final release of the imap-4 toolkit do not work > with a Kerberos-capable Cyrus server I'm sorry, you're mistaken. That patch will break when using an IMAP4 server that offers authentication names. In IMAP4, the prefix was "AUTH-", not "AUTH=". It was changed to "AUTH=" in IMAP4rev1. I will leave to your co-worker who wanted this change to 'fess up and admit responsibility. I thought that it was bogus to change it. Cyrus will have to offer AUTH- as well if it wants to work with IMAP4 clients that depend upon the AUTH- extension.   Received: from cnri by ietf.org id aa17458; 4 Nov 96 15:34 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa20913; 4 Nov 96 15:34 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id LAA05035 for imap-out; Mon, 4 Nov 1996 11:49:13 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from alycia.dementia.org (ALYCIA.DEMENTIA.ORG [128.2.35.149]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id LAA05022 for ; Mon, 4 Nov 1996 11:49:03 -0800 Received: from johnstown.andrew.cmu.edu (JOHNSTOWN.ANDREW.CMU.EDU [128.2.35.156]) by alycia.dementia.org (8.7.2/8.6.12) with SMTP id OAA04709 for ; Mon, 4 Nov 1996 14:48:52 -0500 (EST) Date: Mon, 4 Nov 1996 14:48:50 -0500 (EST) From: "Derrick J. Brashear" Reply-To: "Derrick J. Brashear" Subject: Re: buglet in imap-4 toolkit final release To: imap@cac.washington.edu In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > On Mon, 4 Nov 1996 12:11:49 -0500 (EST), Derrick J Brashear wrote: > > The auth drivers in the final release of the imap-4 toolkit do not work > > with a Kerberos-capable Cyrus server > > I'm sorry, you're mistaken. That patch will break when using an IMAP4 server > that offers authentication names. > > In IMAP4, the prefix was "AUTH-", not "AUTH=". It was changed to "AUTH=" in > IMAP4rev1. I will leave to your co-worker who wanted this change to 'fess up > and admit responsibility. I thought that it was bogus to change it. > > Cyrus will have to offer AUTH- as well if it wants to work with IMAP4 clients > that depend upon the AUTH- extension. I'll buy that, as I found AUTH= only in rev1, but I found *nothing* to indicate one way or another in 1730. Where is it documented prior to rev1? (Just curious mostly) -D   Received: from cnri by ietf.org id aa19416; 4 Nov 96 16:32 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa22346; 4 Nov 96 16:32 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id MAA12023 for imap-out; Mon, 4 Nov 1996 12:37:04 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id MAA12019 for ; Mon, 4 Nov 1996 12:37:01 -0800 Received: from Ikkoku-Kan.Panda.COM (UW-Gateway.Panda.COM [192.107.14.65]) by mailhost2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id MAA02537; Mon, 4 Nov 1996 12:36:54 -0800 Date: Mon, 4 Nov 1996 12:27:11 -0800 (PST) From: Mark Crispin Subject: Re: buglet in imap-4 toolkit final release To: "Derrick J. Brashear" cc: imap@cac.washington.edu In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 4 Nov 1996 14:48:50 -0500 (EST), Derrick J. Brashear wrote: > I'll buy that, as I found AUTH= only in rev1, but I found *nothing* to > indicate one way or another in 1730. Where is it documented prior to rev1? > (Just curious mostly) It started life as a private UW extension, like STATUS. Later, it and STATUS were documented in the rev1 drafts. Then some people wanted some of the names tweaked to make the protocol look prettier. ;-( This is a good object lesson about why these sorts of little tweaks are a bad idea.   Received: from cnri by ietf.org id aa24344; 4 Nov 96 18:33 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa25523; 4 Nov 96 18:33 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id OAA09988 for imap-out; Mon, 4 Nov 1996 14:59:17 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from po10.andrew.cmu.edu (PO10.ANDREW.CMU.EDU [128.2.10.110]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id OAA09984 for ; Mon, 4 Nov 1996 14:59:14 -0800 Received: (from postman@localhost) by po10.andrew.cmu.edu (8.8.2/8.8.0) id RAA01171 for imap@cac.washington.edu; Mon, 4 Nov 1996 17:59:11 -0500 Received: via switchmail; Mon, 4 Nov 1996 17:59:10 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 4 Nov 1996 17:58:49 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 4 Nov 1996 17:58:47 -0500 (EST) Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.54 via MS.5.6.hogtown.andrew.cmu.edu.sun4_51; Mon, 4 Nov 1996 17:58:46 -0500 (EST) Message-ID: Date: Mon, 4 Nov 1996 17:58:46 -0500 (EST) From: John Gardiner Myers To: imap@cac.washington.edu Subject: Re: buglet in imap-4 toolkit final release CC: imap@cac.washington.edu In-Reply-To: References: Mark Crispin writes: > This is a good object lesson about why these sorts of little tweaks are a bad > idea. No, this is a good object lesson about the disadvantages of releasing code based on intermediate revisions of internet drafts. Look, there was no installed base using AUTH-. If you had changed the code when you changed the document, we wouldn't have this problem. -- _.John Gardiner Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up   Received: from cnri by ietf.org id aa25933; 4 Nov 96 19:24 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa26498; 4 Nov 96 19:24 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id PAA11162 for imap-out; Mon, 4 Nov 1996 15:43:03 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id PAA11158 for ; Mon, 4 Nov 1996 15:43:00 -0800 Received: from Ikkoku-Kan.Panda.COM (UW-Gateway.Panda.COM [192.107.14.65]) by mailhost2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id PAA06872; Mon, 4 Nov 1996 15:42:50 -0800 Date: Mon, 4 Nov 1996 15:17:25 -0800 (PST) From: Mark Crispin Subject: Re: buglet in imap-4 toolkit final release To: John Gardiner Myers cc: imap@cac.washington.edu In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 4 Nov 1996 17:58:46 -0500 (EST), John Gardiner Myers wrote: > No, this is a good object lesson about the disadvantages of releasing > code based on intermediate revisions of internet drafts. No. The support for AUTH- predates any drafts by several months. When I wrote the text for the drafts, I was documenting what was already part of our installed base. imap-4 toolkit supports RFC 1730 plus certain UW extensions. These extensions include AUTH- capabilities and STATUS, but both of these changed in IMAP4rev1 (at your insistance). imap-4 toolkit supports the original UW version, to protect the installed base. > Look, there was no installed base using AUTH-. This is incorrect. There was an installed base. Not only is there an installed base for AUTH-, but the code is widely distributed in commerical products. I thought that you understood this when you when you insisted on changing the names. I wondered why you were pushing so hard on this, but I decided that I didn't want to argue the point. I'm sorry if I failed to make this clear to you. > If you had changed the > code when you changed the document, we wouldn't have this problem. It was changed in imap-4.1 code. I was not going to apply piecemeal changes to imap-4 code to support some IMAP4rev1 changes. The whole purpose for creating IMAP4rev1 instead of changing IMAP4 was to protect the IMAP4 installed base. imap-4 toolkit's function was frozen long ago; the imap-4 code is also frozen forever. The only AUTH* capability names in imap-4 (and in RFC 1730 IMAP4 protocol) are the experimental UW AUTH- capability names. You need imap-4.1 code to get IMAP4rev1 support including AUTH= capability names. imap-4.1 is released in beta, and this is what Pine 4.00 will be based upon. You should use imap-4.1 for developing your clients instead of imap-4.   Received: from cnri by ietf.org id aa26836; 4 Nov 96 20:23 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa27592; 4 Nov 96 20:23 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id QAA18551 for imap-out; Mon, 4 Nov 1996 16:42:02 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from venus.Sun.COM (venus.Sun.COM [192.9.25.5]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id QAA18545 for ; Mon, 4 Nov 1996 16:41:59 -0800 Received: from Eng.Sun.COM ([129.146.1.25]) by venus.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id QAA08076; Mon, 4 Nov 1996 16:41:46 -0800 Received: from roam.eng.sun.com by Eng.Sun.COM (SMI-8.6/SMI-5.3) id QAA22224; Mon, 4 Nov 1996 16:41:37 -0800 Received: from roam by roam.eng.sun.com (8.7.1/SMI-SVR4) id QAA10349; Mon, 4 Nov 1996 16:35:21 -0800 (PST) Date: Mon, 4 Nov 1996 16:35:21 -0800 (PST) From: Bill Yeager Reply-To: Bill Yeager Subject: Re: buglet in imap-4 toolkit final release To: John Gardiner Myers cc: imap@cac.washington.edu In-Reply-To: "Your message with ID" Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII >No, this is a good object lesson about the disadvantages of releasing >code based on intermediate revisions of internet drafts. > >Look, there was no installed base using AUTH-. If you had changed the >code when you changed the document, we wouldn't have this problem. Really. We've an installed base of about 2000 users and it is growing. I need to support both AUTH- and AUTH= and will. Bill *Bill++ = jouer; /* jouer is "to play." * If you are having fun, * then life has no seg faults ! */   Received: from cnri by ietf.org id aa26720; 5 Nov 96 11:18 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa13391; 5 Nov 96 11:18 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id HAA01619 for imap-out; Tue, 5 Nov 1996 07:36:09 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from server21.digital.fr (server21.digital.fr [193.56.15.21]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id HAA01615 for ; Tue, 5 Nov 1996 07:36:03 -0800 Received: from mail.vbo.dec.com (mail.vbo.dec.com [16.36.208.34]) by server21.digital.fr (8.7.5/8.7) with ESMTP id QAA09496 for ; Tue, 5 Nov 1996 16:38:41 +0100 (MET) Received: from vbormc.vbo.dec.com (vbormc.vbo.dec.com [16.36.208.94]) by mail.vbo.dec.com (8.7.3/8.7) with ESMTP id PAA07625 for ; Tue, 5 Nov 1996 15:53:48 +0100 (MET) Received: from mrrat.reo.dec.com (mrrat.reo.dec.com [16.36.112.53]) by vbormc.vbo.dec.com (8.7.3/8.7) with SMTP id PAA18652 for ; Tue, 5 Nov 1996 15:53:25 +0100 Received: from mrrat.reo.dec.com [16.36.112.53] (HELO mrrat) by mrrat.reo.dec.com (AltaVista Mail F2.0/2.0 BL24 listener) id 0000_016b_327f_5415_89bd; Tue, 05 Nov 1996 14:49:57 +0000 Message-ID: <327F5415.7237@mrmog.reo.dec.com> Date: Tue, 05 Nov 1996 14:49:57 +0000 From: Paul Kingsnorth X-Mailer: Mozilla 3.0 (WinNT; I) MIME-Version: 1.0 To: imap@cac.washington.edu Subject: Search response if no messages match? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit A minor inconsistency in draft-crispin-imap-base-07.txt. The SEARCH response is described first in 7.2.5: 7.2.5. SEARCH Response Contents: zero or more numbers ... whereas section 9 has mailbox_data ::= ... "SEARCH" [SPACE 1#nz_number] / ... i.e. 1 or more numbers. I don't really care which is correct, I was just trying to check on the correct response if no messages matched the search. Paul Kingsnorth   Received: from cnri by ietf.org id aa26721; 5 Nov 96 11:18 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa13392; 5 Nov 96 11:18 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id HAA01651 for imap-out; Tue, 5 Nov 1996 07:37:55 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from alycia.dementia.org (ALYCIA.DEMENTIA.ORG [128.2.35.149]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id HAA01647 for ; Tue, 5 Nov 1996 07:37:52 -0800 Received: from johnstown.andrew.cmu.edu (JOHNSTOWN.ANDREW.CMU.EDU [128.2.35.156]) by alycia.dementia.org (8.7.2/8.6.12) with SMTP id KAA15696 for ; Tue, 5 Nov 1996 10:37:52 -0500 (EST) Date: Tue, 5 Nov 1996 10:37:48 -0500 (EST) From: "Derrick J. Brashear" Reply-To: "Derrick J. Brashear" Subject: Re: buglet in imap-4 toolkit final release To: imap@cac.washington.edu In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII > imap-4.1 is released in beta, and this is what Pine 4.00 will be based upon. > You should use imap-4.1 for developing your clients instead of imap-4. Which is of course all fine and wonderful, but at the moment I don't have time to make patches and test for incompatibility while building ml 2.3 and whatever the other thing is that I'm forgetting at the moment that I build against imap-4.0, and I suspect other people will be bitten by the same thing. Complaining and arguing now that the change has been made won't help, and while I realize the code is frozen perhaps the message here will be helpful if someone else runs into the same problem. Or maybe I'm losing my mind.   Received: from cnri by ietf.org id aa02638; 5 Nov 96 12:47 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa15438; 5 Nov 96 12:47 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id IAA26667 for imap-out; Tue, 5 Nov 1996 08:45:36 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id IAA26663 for ; Tue, 5 Nov 1996 08:45:34 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id IAA29628; Tue, 5 Nov 1996 08:43:01 -0800 (PST) Date: Tue, 5 Nov 1996 08:25:17 -0800 (PST) From: Mark Crispin Subject: re: Search response if no messages match? To: Paul Kingsnorth cc: imap@cac.washington.edu In-Reply-To: <327F5415.7237@mrmog.reo.dec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 05 Nov 1996 14:49:57 +0000, Paul Kingsnorth wrote: > A minor inconsistency in draft-crispin-imap-base-07.txt. The SEARCH > response is described first in 7.2.5: > Contents: zero or more numbers > whereas section 9 has > mailbox_data ::= ... > "SEARCH" [SPACE 1#nz_number] / > ... > i.e. 1 or more numbers. > > I don't really care which is correct, I was just trying to check on the > correct response if no messages matched the search. Hello Paul. The answer is "both are correct"! I can understand why you were confused, since I had to do a double-take myself. Here's where you got misled: Remember that the descriptions of the "Contents:" are "by function, not by syntax" (introduction to section 7). In other words, interpret these descriptions in a functional manner, and not as a syntax specification. Now, look carefully at the SEARCH response in mailbox_data, and note that the what follows SEARCH is in brackets: "[SPACE 1#nz_number]". This means that this whole expression is optional. In other words, if no messages match the SEARCH, there must be no space after "SEARCH". If one or more messages match the SEARCH, then there is a space followed by one or more messages delimited with comma. As a functional description, "zero or more numbers" is correct. The functional description does not deal in the syntax, which also deals with the presence or absence of a space. Do you have any suggestions for how this may have been clearer? Remember that the document is not intended to be pedagogical, and is already too bloated; so we need to be concise. The best I can come up with is to change "zero or more numbers" to "OPTIONAL one or more numbers" but I don't like it.   Received: from cnri by ietf.org id aa11793; 5 Nov 96 14:47 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa18210; 5 Nov 96 14:47 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id JAA28582 for imap-out; Tue, 5 Nov 1996 09:55:31 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from THOR.INNOSOFT.COM (THOR.INNOSOFT.COM [192.160.253.66]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id JAA28578; Tue, 5 Nov 1996 09:55:25 -0800 Received: from eleanor.innosoft.com ("port 35344"@ELEANOR.INNOSOFT.COM) by INNOSOFT.COM (PMDF V5.0-7 #8694) id <01IBHDXMQ0689ODPL9@INNOSOFT.COM>; Tue, 05 Nov 1996 09:54:47 -0800 (PST) Date: Tue, 05 Nov 1996 09:55:20 -0800 (PST) From: Chris Newman Subject: Re: buglet in imap-4 toolkit final release In-reply-to: To: Mark Crispin Cc: IMAP Discusson List Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT Now we're stuck with three authentication mechanism detection systems: 1) RFC 1730 style: probe AUTHENTICATION mechanisms 2) c-client 4.0 style: check for AUTH- capabilities 3) IMAP4rev1: check for AUTH= capabilities Mark, I'm sure everyone involved would appreciate it if you added support for either (1) or (3) to your c-client 4.0 toolkit. The fact is that c-client 4.0's authentication routines don't interoperate with either RFC 1730 or IMAP4bis compliant servers. That is a bug, regardless of the history. I do recall some discussion of AUTH- vs. AUTH=. If it had been stated that there was an installed base of clients which required AUTH- in order to function correctly, I would certainly have supported leaving it as AUTH-. I suspect John would have done the same. I was under the impression at the time that c-client had no authentication support. This is obviously a problem of mis-communication and thus nobody's fault. Now we have to go fix this mess. For my part, I'll try to make sure that the Innosoft server emits both AUTH- and AUTH= when we add authentication mechanisms. If you could adjust the c-client 4.0 end, that would be appreciated and I believe it would be beneficial for the IMAP community. I'm sorry we got into this mess, but we are all human after all.   Received: from cnri by ietf.org id aa09505; 5 Nov 96 20:19 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa25165; 5 Nov 96 20:19 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id PAA08173 for imap-out; Tue, 5 Nov 1996 15:57:37 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from po10.andrew.cmu.edu (PO10.ANDREW.CMU.EDU [128.2.10.110]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id PAA08166 for ; Tue, 5 Nov 1996 15:57:33 -0800 Received: (from postman@localhost) by po10.andrew.cmu.edu (8.8.2/8.8.0) id SAA01148 for imap@cac.washington.edu; Tue, 5 Nov 1996 18:57:30 -0500 Received: via switchmail; Tue, 5 Nov 1996 18:57:29 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 5 Nov 1996 18:57:00 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Tue, 5 Nov 1996 18:56:58 -0500 (EST) Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.54 via MS.5.6.hogtown.andrew.cmu.edu.sun4_51; Tue, 5 Nov 1996 18:56:56 -0500 (EST) Message-ID: <8mTxF8e00WBw0NXss0@andrew.cmu.edu> Date: Tue, 5 Nov 1996 18:56:56 -0500 (EST) From: John Gardiner Myers To: imap@cac.washington.edu Subject: Re: buglet in imap-4 toolkit final release In-Reply-To: References: Then there is the problem that both the IMAP4 and IMAP4rev1 documents contain the section: Capability names MUST either begin with "X" or be standard or standards-track IMAP4 extensions, revisions, or amendments registered with IANA. A server MUST NOT offer unregistered or non-standard capability names, unless such names are prefixed with an "X". Since there are no "AUTH-" capabilities that are standards-track, there is no IANA registry, and "AUTH-" is not prefixed with an "X", any server that advertises AUTH- capabilities is nonconformant with both IMAP4 and IMAP4rev1. Mark, if you had been properly protecting the installed base, you would have considered the servers in production outside UW, which supported authentication services in conformance to RFC 1730, the relevant standards document at the time. Instead, you developed your own nonstandard mutation of the protocol and released clients which depended on the existence of this nonstandard extension in order to perform functions that existed in the base spec. My understanding is at at the time, the installed base of AUTH- was mostly contained within UW, which is relatively small and easy to get transitioned. At the time, you could have had the servers advertise both AUTH- and AUTH=, and you could have had the clients fallback to the 1730 smantics of trying all mechanisms for which you have credentials in the case where there are no AUTH= capabilities. But now, there is a much larger mess to clean up. -- _.John Gardiner Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up   Received: from cnri by ietf.org id aa00658; 6 Nov 96 0:00 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa01088; 6 Nov 96 0:00 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id TAA18481 for imap-out; Tue, 5 Nov 1996 19:59:16 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from mailhost1.cac.washington.edu (mailhost1.cac.washington.edu [140.142.32.2]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id TAA18477 for ; Tue, 5 Nov 1996 19:59:13 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mailhost1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id TAA12225; Tue, 5 Nov 1996 19:59:06 -0800 Date: Tue, 5 Nov 1996 19:59:06 -0800 (PST) From: Terry Gray To: John Gardiner Myers cc: imap@cac.washington.edu Subject: Re: buglet in imap-4 toolkit final release In-Reply-To: <8mTxF8e00WBw0NXss0@andrew.cmu.edu> Message-ID: Organization: University of Washington; Computing & Communications MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > My understanding is at at the time, the installed base of AUTH- was > mostly contained within UW, which is relatively small and easy to get > transitioned. At the time, you could have had the servers advertise > both AUTH- and AUTH=, and you could have had the clients fallback to > the 1730 smantics of trying all mechanisms for which you have > credentials in the case where there are no AUTH= capabilities. There certainly seems to have been a disconnect somewhere, since --as far as I know-- there is not now nor has there ever been any use of any form of AUTH at UW... (That's not to say that there won't be in the future...) -teg   Received: from cnri by ietf.org id aa13728; 6 Nov 96 6:42 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa07142; 6 Nov 96 6:42 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id CAA23959 for imap-out; Wed, 6 Nov 1996 02:33:44 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from server21.digital.fr (server21.digital.fr [193.56.15.21]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id CAA23952; Wed, 6 Nov 1996 02:33:34 -0800 Received: from mail.vbo.dec.com (mail.vbo.dec.com [16.36.208.34]) by server21.digital.fr (8.7.5/8.7) with ESMTP id LAA06781; Wed, 6 Nov 1996 11:36:14 +0100 (MET) Received: from vbormc.vbo.dec.com (vbormc.vbo.dec.com [16.36.208.94]) by mail.vbo.dec.com (8.7.3/8.7) with ESMTP id LAA04946; Wed, 6 Nov 1996 11:35:13 +0100 (MET) Received: from mrrat.reo.dec.com (mrrat.reo.dec.com [16.36.112.53]) by vbormc.vbo.dec.com (8.7.3/8.7) with SMTP id LAA13125; Wed, 6 Nov 1996 11:34:52 +0100 Received: from mrrat.reo.dec.com [16.36.112.53] (HELO mrrat) by mrrat.reo.dec.com (AltaVista Mail F2.0/2.0 BL24 listener) id 0000_016b_3280_690a_9f57; Wed, 06 Nov 1996 10:31:38 +0000 Message-ID: <32806909.C15@mrmog.reo.dec.com> Date: Wed, 06 Nov 1996 10:31:37 +0000 From: Paul Kingsnorth X-Mailer: Mozilla 3.0 (WinNT; I) MIME-Version: 1.0 To: Mark Crispin CC: imap@cac.washington.edu Subject: Re: Search response if no messages match? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mark Crispin wrote: > ... look carefully at the SEARCH response in mailbox_data, and note > that what follows SEARCH is in brackets: "[SPACE 1#nz_number]". This > means that this whole expression is optional. Got it, thanks. > Do you have any suggestions for how this may have been clearer? You could extend the example at the end of 6.4.4. I mostly read the examples first, the bnf second. Thanks, Paul Kingsnorth.   Received: from cnri by ietf.org id aa00970; 6 Nov 96 11:27 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa13775; 6 Nov 96 11:27 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id HAA22409 for imap-out; Wed, 6 Nov 1996 07:36:24 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from brooklyn.bug.com (brooklyn.bug.com [198.74.12.17]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id HAA22405 for ; Wed, 6 Nov 1996 07:36:21 -0800 Received: from bug.bug.com by brooklyn.bug.com (AIX 3.2/UCB 5.64/4.03) id AA07371; Wed, 6 Nov 1996 10:26:26 -0500 Received: from mail00.isg.bug.com by mac-risc.isg.bug.com (AIX 3.2/UCB 5.64/4.03) id AA18345; Wed, 6 Nov 1996 10:35:45 -0500 Received: from tsmith (tsmith.isg.bug.com [199.16.15.168]) by mail00.isg.bug.com (8.8.2/8.6.12) with SMTP id KAA06798 for ; Wed, 6 Nov 1996 10:33:17 -0500 (EST) Message-Id: <199611061533.KAA06798@mail00.isg.bug.com> Comments: Authenticated sender is From: Tim Smith Organization: Brooklyn Union To: imap@cac.washington.edu Date: Wed, 6 Nov 1996 10:35:55 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Subject: Bad Login Reply-To: tsmith@bug.com Priority: normal X-Mailer: Pegasus Mail for Win32 (v2.42a) A cry from bsdi land... Compiled the server for plain old unix-password authentication (bsdi 2.1). The compile went fine (w/ minor tweaks) and is running, but I can't log into the server at all. Can't login as root, can't login as the cyrus user, can't login as anybody (the log message is "badlogin: server[address] plaintext user wrong password"). Any thoughts? Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Tim Smith Programmer/Analyst Brooklyn Union 718.403.6359 tsmith@bug.com   Received: from cnri by ietf.org id aa19063; 7 Nov 96 7:35 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa08282; 7 Nov 96 7:35 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id DAA05475 for imap-out; Thu, 7 Nov 1996 03:36:15 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from server21.digital.fr (server21.digital.fr [193.56.15.21]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id DAA05471 for ; Thu, 7 Nov 1996 03:36:08 -0800 Received: from mail.vbo.dec.com (mail.vbo.dec.com [16.36.208.34]) by server21.digital.fr (8.7.5/8.7) with ESMTP id MAA03383 for ; Thu, 7 Nov 1996 12:38:46 +0100 (MET) Received: from vbormc.vbo.dec.com (vbormc.vbo.dec.com [16.36.208.94]) by mail.vbo.dec.com (8.7.3/8.7) with ESMTP id MAA29116 for ; Thu, 7 Nov 1996 12:38:02 +0100 (MET) Received: from mrrat.reo.dec.com (mrrat.reo.dec.com [16.36.112.53]) by vbormc.vbo.dec.com (8.7.3/8.7) with SMTP id MAA23530 for ; Thu, 7 Nov 1996 12:37:39 +0100 Received: from mrrat.reo.dec.com [16.36.112.53] (HELO mrrat) by mrrat.reo.dec.com (AltaVista Mail F2.0/2.0 BL24 listener) id 0000_016b_3281_c925_acb6; Thu, 07 Nov 1996 11:33:57 +0000 Message-ID: <3281C924.1CD7@mrmog.reo.dec.com> Date: Thu, 07 Nov 1996 11:33:56 +0000 From: Paul Kingsnorth X-Mailer: Mozilla 3.0 (WinNT; I) MIME-Version: 1.0 To: imap@cac.washington.edu Subject: \Recent and EXAMINE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I've just been trying to get up to date on the refined definition of \Recent in draft-crispin-imap-base-07.txt, and there's one case which bothers me. Suppose I log in and EXAMINE the inbox. A new message arrives; and on the next NOOP (or similar) I'll get told about the new message, and the new message will have the \Recent flag set. I then log out. Sometime later I log in and SELECT the inbox. Should that new message still have the \Recent flag? Section 6.3.2 says: The EXAMINE command is identical to SELECT and returns the same output; however, the selected mailbox is identified as read-only. No changes to the permanent state of the mailbox, including per-user state, are permitted. However section 2.3.2 describes the meaning of \Recent as: Message is "recently" arrived in this mailbox. This session is the first session to have been notified about this message; subsequent sessions will not see \Recent set for this message. Section 1.2 makes it clear that 'session' covers both SELECT and EXAMINE. I'd be inclined to say that EXAMINE really should be read-only and that when I SELECT the inbox, the message should still be marked as \Recent. Paul Kingsnorth   Received: from cnri by ietf.org id aa20773; 7 Nov 96 8:19 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa09215; 7 Nov 96 8:19 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id EAA06140 for imap-out; Thu, 7 Nov 1996 04:17:09 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from ingsun1 (ingsun1.univ.trieste.it [140.105.61.71]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id EAA06136 for ; Thu, 7 Nov 1996 04:17:02 -0800 Received: by ingsun1 (5.0/SMI-SVR4) id AA13883; Thu, 7 Nov 1996 13:17:04 --100 Date: Thu, 7 Nov 1996 13:17:04 --100 From: Massimiliano VIOLA Message-Id: <9611071217.AA13883@ingsun1> To: imap@cac.washington.edu Subject: unsubscribe unsubscribe viola@ingsun1.univ.trieste.it   Received: from cnri by ietf.org id aa11132; 7 Nov 96 13:37 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa17290; 7 Nov 96 13:37 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id JAA19951 for imap-out; Thu, 7 Nov 1996 09:36:09 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from feyuri.microsoft.com (feyuri.microsoft.com [131.107.243.53]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id JAA19947 for ; Thu, 7 Nov 1996 09:36:07 -0800 Message-Id: <199611071736.JAA19947@mx2.cac.washington.edu> Received: by FEYURI with IMAIL 2.0 id <01BBCC8F.1DD50530@FEYURI>; Thu, 7 Nov 1996 09:36:13 -0800 From: "Jithendra Veeramachaneni (Exchange)" To: imap@cac.washington.edu Subject: unsubscribe Date: Thu, 7 Nov 1996 09:36:11 -0800 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (4.5.1358.4) Content-Type: text/plain unsubscribe jithendv@microsoft.com   Received: from cnri by ietf.org id aa16544; 7 Nov 96 20:14 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa27319; 7 Nov 96 20:14 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id QAA01782 for imap-out; Thu, 7 Nov 1996 16:34:12 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id QAA01778 for ; Thu, 7 Nov 1996 16:34:09 -0800 Received: from localhost (mrc@localhost) by shiva1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id QAA09243; Thu, 7 Nov 1996 16:34:05 -0800 Date: Thu, 7 Nov 1996 16:34:04 -0800 (PST) From: Mark Crispin To: Paul Kingsnorth cc: imap@cac.washington.edu Subject: Re: \Recent and EXAMINE In-Reply-To: <3281C924.1CD7@mrmog.reo.dec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 7 Nov 1996, Paul Kingsnorth wrote: > I'd be inclined to say that EXAMINE really should be read-only > and that when I SELECT the inbox, the message should still be > marked as \Recent. For what it's worth, I would tend to agree.   Received: from cnri by ietf.org id aa21188; 7 Nov 96 21:06 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa28152; 7 Nov 96 21:06 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id RAA03182 for imap-out; Thu, 7 Nov 1996 17:19:20 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from lacroix.wildbear.on.ca (lacroix.wildbear.on.ca [199.246.132.198]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id RAA03178 for ; Thu, 7 Nov 1996 17:19:07 -0800 Received: by lacroix.wildbear.on.ca from localhost (router,SLmailNT V3.0 (alpha 1)); Thu, 7 Nov 1996 20:14:05 -0500 Received: by lacroix.wildbear.on.ca from tester.wildbear.on.ca (199.246.132.199::mail daemon,SLmailNT V3.0 (alpha 1)); Thu, 7 Nov 1996 20:14:04 -0500 Message-Id: <3.0.32.19961107201759.00d4c5d0@lacroix> X-Sender: "Jack De Winter" X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Thu, 07 Nov 1996 20:18:00 -0500 To: imap@cac.washington.edu From: Jack De Winter Subject: question for the microsoft people on the list... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit could one of you folk out there please tell me what the 'AUTH twinkie' command that the Microsoft Mailer is doing is? Will it be supported for IMAP? Is it going to be an internet spec, or should it be renamed to something that denotes it is a vendor specific AUTH type? regards, Jack   Received: from cnri by ietf.org id aa22644; 7 Nov 96 21:22 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa28405; 7 Nov 96 21:22 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id RAA25618 for imap-out; Thu, 7 Nov 1996 17:39:54 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from INET-02-IMC.microsoft.com (mail2.microsoft.com [131.107.3.42]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id RAA25614 for ; Thu, 7 Nov 1996 17:39:51 -0800 Received: by INET-02-IMC.microsoft.com with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.994.63) id <01BBCCD2.5CF74CD0@INET-02-IMC.microsoft.com>; Thu, 7 Nov 1996 17:37:35 -0800 Message-ID: From: Nat Ballou To: "'imap@cac.washington.edu'" Subject: RE: question for the microsoft people on the list... Date: Thu, 7 Nov 1996 17:38:36 -0800 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.994.63 Encoding: 38 TEXT Jack, The 'AUTH twinkie' is a bit of a hack in Microsoft Internet Mail to deal with security package negotiation in POP3. This was done since no standard was defined when the software was written. I am going to write a draft and submit it to the IETF for a POP3 extension such that an 'AUTH' command with no arguments will result in a +OK response followed by a space separated list of security package names supported by the server. This is seen as less work than adding a capabilities command and logic to POP3 - as in IMAP and the next version of NNTP. The next version of Microsoft Internet Mail will use AUTH with no arguments to negotiate authentication packages. Thanks, Nat >---------- >From: Jack De Winter[SMTP:jack@Wildbear.ON.CA] >Sent: Thursday, November 07, 1996 5:18 PM >To: imap@cac.washington.edu >Subject: question for the microsoft people on the list... > >could one of you folk out there please tell me what >the 'AUTH twinkie' command that the Microsoft Mailer >is doing is? Will it be supported for IMAP? Is it >going to be an internet spec, or should it be renamed >to something that denotes it is a vendor specific AUTH >type? > >regards, >Jack >   Received: from cnri by ietf.org id aa07903; 7 Nov 96 23:46 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa00843; 7 Nov 96 23:46 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id UAA05741 for imap-out; Thu, 7 Nov 1996 20:05:40 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from malibu.software.com (malibu.software.com [198.17.234.35]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id UAA05737 for ; Thu, 7 Nov 1996 20:05:37 -0800 Received: from bonn.software.com ([10.3.91.11]) by malibu.software.com (post.office MTA v2.0 0813 ID# 0-1001) with ESMTP id AAA367; Thu, 7 Nov 1996 20:05:36 -0800 X-Mailer: exmh version 1.6.6 3/24/96 To: Nat Ballou cc: imap@cac.washington.edu Subject: Re: question for the microsoft people on the list... In-reply-to: Your message of "Thu, 07 Nov 1996 17:38:36 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Nov 1996 20:03:46 -0800 From: Michael D'Errico Message-ID: <19961108040536648.AAA367@bonn.software.com> > I am going to write a draft and submit it to the IETF for a POP3 > extension such that an 'AUTH' command with no arguments will result > in a +OK response followed by a space separated list of security > package names supported by the server. Although this has nothing to do with IMAP and I'm not a Microsoft person, it would be better IMHO to send a multi-line response containing the authentication types: S: +OK host-s.microsoft.com POP3 server C: AUTH S: +OK S: ding-dong S: twinkie S: cupcake S: . C: AUTH twinkie S: ... Mike   Received: from cnri by ietf.org id aa09551; 8 Nov 96 1:13 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa02385; 8 Nov 96 1:13 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id VAA28935 for imap-out; Thu, 7 Nov 1996 21:18:12 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from lacroix.wildbear.on.ca (lacroix.wildbear.on.ca [199.246.132.198]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id VAA28931 for ; Thu, 7 Nov 1996 21:18:08 -0800 Received: by lacroix.wildbear.on.ca from localhost (router,SLmailNT V3.0 (alpha 1)); Fri, 8 Nov 1996 00:12:31 -0500 Received: by lacroix.wildbear.on.ca from tester.wildbear.on.ca (199.246.132.199::mail daemon,SLmailNT V3.0 (alpha 1)); Fri, 8 Nov 1996 00:12:30 -0500 Message-Id: <3.0.32.19961108001644.006e21ac@lacroix> X-Sender: "Jack De Winter" X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Fri, 08 Nov 1996 00:16:45 -0500 To: michael.derrico@software.com, Nat Ballou From: Jack De Winter Subject: Re: question for the microsoft people on the list... Cc: imap@cac.washington.edu Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I know that John Meyers (if memory serves, he is in charge of the SASL draft) is trying to keep it consistant across different platforms. Perhaps he would be a good person to get an opinion on this. Personally, I just hate trying to explain that 'AUTH twinkie' is Microsoft's way of checking for Authentication to our customers. ;-) regards, Jack At 08:03 PM 11/7/96 -0800, michael.derrico@Software.COM wrote: >> I am going to write a draft and submit it to the IETF for a POP3 >> extension such that an 'AUTH' command with no arguments will result >> in a +OK response followed by a space separated list of security >> package names supported by the server. > >Although this has nothing to do with IMAP and I'm not a Microsoft person, >it would be better IMHO to send a multi-line response containing the >authentication types: > > S: +OK host-s.microsoft.com POP3 server > C: AUTH > S: +OK > S: ding-dong > S: twinkie > S: cupcake > S: . > C: AUTH twinkie > S: ...   Received: from cnri by ietf.org id aa25513; 8 Nov 96 18:04 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa24768; 8 Nov 96 18:04 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id OAA26516 for imap-out; Fri, 8 Nov 1996 14:24:44 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from alycia.dementia.org (ALYCIA.DEMENTIA.ORG [128.2.35.149]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id OAA26506 for ; Fri, 8 Nov 1996 14:24:40 -0800 Received: from johnstown.andrew.cmu.edu (JOHNSTOWN.ANDREW.CMU.EDU [128.2.35.156]) by alycia.dementia.org (8.7.2/8.6.12) with SMTP id RAA23939 for ; Fri, 8 Nov 1996 17:23:24 -0500 (EST) Date: Fri, 8 Nov 1996 17:23:23 -0500 (EST) From: "Derrick J. Brashear" Reply-To: "Derrick J. Brashear" Subject: IMAP to HTML gateway? To: imap@cac.washington.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Hi, Assume for the purpose of discussion that I have a read-only IMAP mailbox which I wish to export via a Web page. Do any of you know of anything of this nature? Thanks -D   Received: from cnri by ietf.org id aa06616; 9 Nov 96 17:09 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa15701; 9 Nov 96 17:09 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id NAA11120 for imap-out; Sat, 9 Nov 1996 13:26:33 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from io.org (io.org [198.133.36.1]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id NAA11115 for ; Sat, 9 Nov 1996 13:26:22 -0800 Received: from SPRY194967 (tdac.net3.io.org [199.166.238.210]) by io.org (8.6.12/8.6.12) with SMTP id QAA26029; Sat, 9 Nov 1996 16:26:13 -0500 Message-Id: <199611092126.QAA26029@io.org> X-Sender: tcox@io.org (Unverified) X-Mailer: Windows Eudora Version 1.4.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 09 Nov 1996 16:23:26 -0500 To: "Derrick J. Brashear" , imap@cac.washington.edu From: "Timothy D. A. Cox" Subject: Re: IMAP to HTML gateway? At 05:23 PM 11/8/96 -0500, Derrick J. Brashear wrote: >Hi, > >Assume for the purpose of discussion that I have a read-only IMAP mailbox which >I wish to export via a Web page. Do any of you know of anything of this nature? You could check out my e-mail client written in Java. Try the page: http://www.ki.net/~tdac This will allow you to read your 'inbox' via the web. It currently supports IMAP2 but IMAP4 will soon be added. Tim ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Timothy D. A. Cox TDAC Software Inc. e-mail - tcox@io.org URL - http://www.io.org/~tcox - tdac@ki.net   Received: from cnri by ietf.org id aa27003; 10 Nov 96 7:47 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa07898; 10 Nov 96 7:47 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id EAA24885 for imap-out; Sun, 10 Nov 1996 04:21:31 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from rocknet (ns.rocknet.net.au [198.142.78.3]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id EAA24881 for ; Sun, 10 Nov 1996 04:21:25 -0800 Received: from thor.blmnet.com.au (modem05.rocknet.net.au [198.142.78.20]) by rocknet (8.8.2/8.6.9) with SMTP id WAA04107 for ; Sun, 10 Nov 1996 22:27:18 +1000 Message-ID: <3285C8B9.422B@rocknet.net.au> Date: Sun, 10 Nov 1996 22:22:18 +1000 From: Brendan Millard Reply-To: bmillard@rocknet.net.au Organization: BLM Networking X-Mailer: Mozilla 3.0Gold (Win95; I) MIME-Version: 1.0 To: imap@cac.washington.edu Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit unsubscribe bmillard@rocknet.net.au   Received: from cnri by ietf.org id aa27279; 10 Nov 96 8:00 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa08057; 10 Nov 96 8:00 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id EAA21327 for imap-out; Sun, 10 Nov 1996 04:33:26 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from nmi-gate.netmanage.co.il (nmi-gate.netmanage.co.il [194.90.33.10]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id EAA21323 for ; Sun, 10 Nov 1996 04:33:22 -0800 From: ofer@netmanage.co.il Received: from ofer.netmanage.co.il (ofer.netmanage.co.il [194.90.33.178]) by nmi-gate.netmanage.co.il (8.6.9/8.6.9) with SMTP id OAA12290 for ; Sun, 10 Nov 1996 14:33:42 +0200 Date: Sun, 10 Nov 96 14:21:33 Israel Standard Time Subject: implementing move To: imap@cac.washington.edu X-Mailer: Chameleon ATX BCNT_43, TCP/IP for Windows, NetManage Inc. X-Priority: 3 (Normal) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII maybe someone can help me with the following, regarding an imap client: trying to implement a move command of imap msgs, i use a sequence of uid copy/store/expunge. the question: when mass uid copying from one folder to another, what will be the uid's of the copied folders. tnx in advance - ofer ------------------------------------- E-mail: ofer@netmanage.co.il Date: 11/10/96 Time: 14:21:34 -------------------------------------   Received: from cnri by ietf.org id aa04560; 10 Nov 96 14:46 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa14194; 10 Nov 96 14:46 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id LAA29372 for imap-out; Sun, 10 Nov 1996 11:28:09 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from tide03.microsoft.com (tide03.microsoft.com [131.107.3.13]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id LAA29368 for ; Sun, 10 Nov 1996 11:28:06 -0800 Received: by tide03.microsoft.com; id LAA00451; Sun, 10 Nov 1996 11:28:02 -0800 (PST) Received: from unknown(157.54.17.74) by tide03.microsoft.com via smap (V3.1) id xma000442; Sun, 10 Nov 96 11:27:46 -0800 Received: from IMSMAIL ([157.55.65.201]) by imail2.microsoft.com (8.7.3/8.7.1) with ESMTP id LAA00638; Sun, 10 Nov 1996 11:27:21 -0800 (PST) Received: from natba - 157.54.20.17 by ims.microsoft.com with Microsoft SMTPSVC; Sun, 10 Nov 1996 11:32:24 -0800 From: Nat Ballou To: michael.derrico@software.com MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US Cc: imap@cac.washington.edu MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US Subject: Re: question for the microsoft people on the list... Date: Sun, 10 Nov 1996 11:27:25 -0800 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.71.0201.0 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <018012432190ab6IMSMAIL@ims.microsoft.com> I just got private mail from John Myers that he was planning on proposing something like you specify below. Thanks, Nat ---------- > From: michael.derrico@Software.COM > To: Nat Ballou > Cc: imap@cac.washington.edu > Subject: Re: question for the microsoft people on the list...=20 > Date: Thursday, November 07, 1996 8:03 PM >=20 > > I am going to write a draft and submit it to the IETF for a POP3 > > extension such that an 'AUTH' command with no arguments will result > > in a +OK response followed by a space separated list of security > > package names supported by the server. >=20 > Although this has nothing to do with IMAP and I'm not a Microsoft = person, > it would be better IMHO to send a multi-line response containing the > authentication types: >=20 > S: +OK host-s.microsoft.com POP3 server > C: AUTH > S: +OK > S: ding-dong > S: twinkie > S: cupcake > S: . > C: AUTH twinkie > S: ... >=20 > Mike >=20 >=20 >=20 >   Received: from cnri by ietf.org id aa04578; 10 Nov 96 14:47 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa14210; 10 Nov 96 14:47 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id LAA29047 for imap-out; Sun, 10 Nov 1996 11:03:19 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id LAA29043 for ; Sun, 10 Nov 1996 11:03:16 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id LAA07333; Sun, 10 Nov 1996 11:03:12 -0800 (PST) Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA20963; Sun, 10 Nov 96 11:03:06 -0800 Date: Sun, 10 Nov 1996 10:56:29 -0800 (PST) From: Mark Crispin Subject: re: implementing move To: ofer@netmanage.co.il Cc: imap@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Sun, 10 Nov 96 14:21:33 Israel Standard Time, ofer@Netmanage.CO.IL wrote: > maybe someone can help me with the following, regarding an imap client: > trying to implement a move command of imap msgs, i use a sequence of > uid copy/store/expunge. the question: when mass uid copying from one > folder to another, what will be the uid's of the copied folders. There is no way to know the UID of the messages in the copied folder, except by opening the folder and hunting for the messages (e.g. by message ID). There has been discussion of a server feature to return the UID on a COPY or APPEND, but more than one server implementor has stated that this feature would be very difficult and expensive for them to implement. So it is unlikely that you will see this feature made widely available. By the way, your mailer (Chameleon ATX BCNT_43, TCP/IP for Windows, NetManage Inc.) generated a date header of: Date: Sun, 10 Nov 96 14:21:33 Israel Standard Time "Israel Standard Time" is not a valid time zone. A valid timezone consist of a + or - followed by four digits representing hours and minutes from UTC. I believe that Israel is two hours later than UTC, hence this would be +0200. There are a few letter timezones, but they are all obsolete. If you want to include "Israel Standard Time", you can do so inside a comment, e.g.: Date: Sun, 10 Nov 96 14:21:33 +0200 (Israel Standard Time)   Received: from cnri by ietf.org id aa07502; 10 Nov 96 15:35 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa14977; 10 Nov 96 15:35 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id LAA29645 for imap-out; Sun, 10 Nov 1996 11:50:17 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from lacroix.wildbear.on.ca (lacroix.wildbear.on.ca [199.246.132.198]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id LAA29641 for ; Sun, 10 Nov 1996 11:50:13 -0800 Received: by lacroix.wildbear.on.ca from localhost (router,SLmailNT V3.0 (alpha 1)); Sun, 10 Nov 1996 14:43:40 -0500 Received: by lacroix.wildbear.on.ca from tester.wildbear.on.ca (199.246.132.199::mail daemon,SLmailNT V3.0 (alpha 1)); Sun, 10 Nov 1996 14:43:39 -0500 Message-Id: <3.0.32.19961110144750.006e72fc@lacroix> X-Sender: "Jack De Winter" X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Sun, 10 Nov 1996 14:47:51 -0500 To: ofer@netmanage.co.il, imap@cac.washington.edu From: Jack De Winter Subject: Re: implementing move Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit At 02:21 PM 11/10/96 Time, ofer@Netmanage.CO.IL wrote: >maybe someone can help me with the following, regarding an imap client: >trying to implement a move command of imap msgs, i use a sequence of >uid copy/store/expunge. the question: when mass uid copying from one >folder to another, what will be the uid's of the copied folders. a clarification: what will be the uid's of the folders themselves, or of the messages within the folders? regards, Jack   Received: from cnri by ietf.org id aa02155; 11 Nov 96 7:29 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa01111; 11 Nov 96 7:29 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id AAA09229 for imap-out; Mon, 11 Nov 1996 00:25:13 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from nmi-gate.netmanage.co.il (nmi-gate.netmanage.co.il [194.90.33.10]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id AAA09225 for ; Mon, 11 Nov 1996 00:25:08 -0800 From: ofer@netmanage.co.il Received: from ofer.netmanage.co.il (ofer.netmanage.co.il [194.90.33.178]) by nmi-gate.netmanage.co.il (8.6.9/8.6.9) with SMTP id KAA28234; Mon, 11 Nov 1996 10:25:28 +0200 Date: Mon, 11 Nov 96 10:06:54 Israel Standard Time Subject: re: implementing move To: Mark Crispin Cc: imap@cac.washington.edu X-Mailer: Chameleon ATX BCNT_43, TCP/IP for Windows, NetManage Inc. X-Priority: 3 (Normal) References: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII thanks for the quick response. you are right about the mailer. question/suggestion: supponse we copy msgs of uid 1,2,3 to a folder which holds msgs with uid's 4,5,6, and as a result this folder has uid's 4,5,6,10,12,14: 1. ui'd 1,2,3 were copied into uid's 10,12,14 2. but which witch is which ? 3. do you know if in practice all known servers maintain copy order, i.e. uid 1 was copied into uid 10, uid 2 into 12, uid 3 into uid 12. because if so - it is possible to support mass copy. alternatively - do you think that servers that do maintain copy order would be interested in flagging themselves, so their clients would be able to support a more efficient mass copy ?. tnx in advance - ofer ------------------------------------- E-mail: ofer@netmanage.co.il Date: 11/11/96 Time: 10:06:55 -------------------------------------   Received: from cnri by ietf.org id aa17524; 11 Nov 96 13:10 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa10301; 11 Nov 96 13:10 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id JAA16601 for imap-out; Mon, 11 Nov 1996 09:17:36 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from lacroix.wildbear.on.ca (lacroix.wildbear.on.ca [199.246.132.198]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id JAA16597 for ; Mon, 11 Nov 1996 09:17:32 -0800 Received: by lacroix.wildbear.on.ca from localhost (router,SLmailNT V3.0 (alpha 1)); Mon, 11 Nov 1996 12:11:18 -0500 Received: by lacroix.wildbear.on.ca from tester.wildbear.on.ca (199.246.132.199::mail daemon,SLmailNT V3.0 (alpha 1)); Mon, 11 Nov 1996 12:11:17 -0500 Message-Id: <3.0.32.19961111121505.006ff428@lacroix> X-Sender: "Jack De Winter" X-Mailer: Windows Eudora Pro Version 3.0 Demo (32) Date: Mon, 11 Nov 1996 12:15:06 -0500 To: ofer@netmanage.co.il, Mark Crispin From: Jack De Winter Subject: re: implementing move Cc: imap@cac.washington.edu, Jack De Winter Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit At 10:06 AM 11/11/96 Time, ofer@Netmanage.CO.IL wrote: >thanks for the quick response. you are right about the mailer. >question/suggestion: >supponse we copy msgs of uid 1,2,3 to a folder which holds msgs with uid's 4,5,6, >and as a result this folder has uid's 4,5,6,10,12,14: >1. ui'd 1,2,3 were copied into uid's 10,12,14 >2. but which witch is which ? >3. do you know if in practice all known servers maintain copy order, i.e. >uid 1 was copied into uid 10, uid 2 into 12, uid 3 into uid 12. >because if so - it is possible to support mass copy. >alternatively - do you think that servers that do maintain copy order >would be interested in flagging themselves, so their clients would be able to support >a more efficient mass copy ?. See, for me, it is more of a question of whether or not a uid, that is a unique id, should change if a message is moved. So for me, the question starts off as: If you move a message from a mailbox to another, should the uid change? And I would think that the answer is no. (If I am wrong, let me know) The harder question is: If you copy a message from a mailbox to another, should the uid change? This gets nitty gritty. The uid uniquely identifies the message. The message has not changed, so there is an argument for not changing it. There is also an equal argument for the message then being a copy, so generating a new uid for it could be valid. If so, using a message id or uid that denotes the copying from the original message might be a good thing. Ideas? Also, what form of UIDs are people using for messages? Still the Message-Id thingy? If not, I would be interested to hear them. regards, Jack   Received: from cnri by ietf.org id aa19310; 11 Nov 96 13:50 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa11302; 11 Nov 96 13:50 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id KAA17506 for imap-out; Mon, 11 Nov 1996 10:12:12 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id KAA17502 for ; Mon, 11 Nov 1996 10:12:09 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id KAA09134; Mon, 11 Nov 1996 10:12:07 -0800 (PST) Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA25108; Mon, 11 Nov 96 10:12:02 -0800 Date: Mon, 11 Nov 1996 10:06:41 -0800 (PST) From: Mark Crispin Subject: re: implementing move To: ofer@netmanage.co.il Cc: imap@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 11 Nov 96 10:06:54 Israel Standard Time, ofer@Netmanage.CO.IL wrote: > supponse we copy msgs of uid 1,2,3 to a folder which holds msgs with uid's > 4,5,6, > and as a result this folder has uid's 4,5,6,10,12,14: > 1. ui'd 1,2,3 were copied into uid's 10,12,14 > 2. but which witch is which ? > 3. do you know if in practice all known servers maintain copy order, i.e. > uid 1 was copied into uid 10, uid 2 into 12, uid 3 into uid 12. The only way to know is to open the mailbox, get envelopes, and compare. There are servers which can not maintain copy order, and in fact may reorder a mailbox each time you select it. In effect, the act of copying a message to another mailbox creates a new message. move is nothing more than copy+delete. There probably is no hope of being able to copy/move a message to another mailbox and treat it as anything other than a newly delivered message. As far as "how do other protocols solve this problem", the answer is that no other protocols offer multiple remote mailboxes. POP and DMSP both have just an INBOX.   Received: from cnri by ietf.org id aa19503; 11 Nov 96 13:57 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa11452; 11 Nov 96 13:57 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id KAA13736 for imap-out; Mon, 11 Nov 1996 10:04:12 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id KAA13732 for ; Mon, 11 Nov 1996 10:04:08 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id KAA09095; Mon, 11 Nov 1996 10:04:04 -0800 (PST) Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA25058; Mon, 11 Nov 96 10:03:59 -0800 Date: Mon, 11 Nov 1996 09:56:13 -0800 (PST) From: Mark Crispin Subject: re: implementing move To: Jack De Winter Cc: ofer@netmanage.co.il, imap@cac.washington.edu In-Reply-To: <3.0.32.19961111121505.006ff428@lacroix> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 11 Nov 1996 12:15:06 -0500, Jack De Winter wrote: > If you move a message from a mailbox to another, should the uid change? This is a meaningless question. There is no such operation as "MOVE" in IMAP. A "MOVE" is a COPY plus a STORE +FLAGS \DELETED plus an EXPUNGE. See the answer to the next question for a continuation. > If you copy a message from a mailbox to another, should the uid change? In IMAP, every mailbox has a UID validity which can be thought of as being a constant high order 32 bits of a 64 bit integer UID. If the destination mailbox has a different UID validity, it is impossible not to change the UID. Furthermore, UIDs must be strictly ascending in the mailbox. If you move a message with UID 23 to a mailbox whose last message has UID 12345, then the moved message must have a UID of at least 12346. In other words, a UID identifies a particular message in a mailbox. > Also, what form of UIDs are people using for messages? Still the > Message-Id thingy? If not, I would be interested to hear them. UIDs in IMAP are 32bit integers by definition. You must be thinking about POP, which has character UIDs (which actually are MD5 checksums). There is a way to get an optional MD5 checksum of a body part in IMAP, but not of an entire message.   Received: from cnri by ietf.org id ac29057; 13 Nov 96 9:13 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa27015; 12 Nov 96 19:18 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id PAA19365 for imap-out; Tue, 12 Nov 1996 15:33:30 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from relay-5.mail.demon.net (punt2.demon.co.uk [194.217.242.1]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id PAA19360 for ; Tue, 12 Nov 1996 15:33:27 -0800 Received: from wits-end.demon.co.uk ([158.152.27.49]) by relay-6.mail.demon.net id aa605767; 12 Nov 96 23:30 GMT Message-ID: <328907E5.467A@wits-end.demon.co.uk> Date: Tue, 12 Nov 1996 23:27:33 +0000 From: Phil Smyth Reply-To: phil@wits-end.demon.co.uk X-Mailer: Mozilla 3.0Gold (Win95; I) MIME-Version: 1.0 To: imap@cac.washington.edu Subject: (no subject)   Received: from cnri by ietf.org id aa02888; 15 Nov 96 14:02 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa17271; 15 Nov 96 14:02 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id JAA03512 for imap-out; Fri, 15 Nov 1996 09:56:24 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from THOR.INNOSOFT.COM (THOR.INNOSOFT.COM [192.160.253.66]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id JAA03506 for ; Fri, 15 Nov 1996 09:56:17 -0800 Received: from eleanor.innosoft.com ("port 37966"@ELEANOR.INNOSOFT.COM) by INNOSOFT.COM (PMDF V5.0-7 #8694) id <01IBVCVNF03G9OE5WJ@INNOSOFT.COM> for imap@cac.washington.edu; Fri, 15 Nov 1996 09:55:15 -0800 (PST) Date: Fri, 15 Nov 1996 09:55:51 -0800 (PST) From: Chris Newman Subject: I-D ACTION:draft-newman-url-imap-02.txt (fwd) To: IMAP Discusson List Message-id: Content-id: MIME-version: 1.0 Content-type: MULTIPART/MIXED; BOUNDARY="-559023410-684387517-848080551=:26694" Content-transfer-encoding: 7BIT This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---559023410-684387517-848080551=:26694 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: I got some useful feedback on the IMAP URL document in a BOF at the IMAP meeting in Seattle and have updated the document. At this point, I think it's done. So I'd like to do a last call on this list, please respond within one week. I'm aware that page-formatting tweaks are necessary and it should probably wait for IMAP4rev1. Recent changes: 1) There was a general agreement that it shouldn't be necessary to encode the "/" character as "%2f" in mailbox names. This required some signficant re-structuring of the format. 2) The "UIDVALIDITY" attribute is now optional in all formats. 3) I improved the formal grammar a bit. 4) Added examples of how a client might translate the URLs to IMAP4 commands. Does anyone know a good URL mailing list where I could get feedback before going into a 4-week last call? ---------- Forwarded message ---------- Date: Thu, 14 Nov 1996 09:26:07 -0500 From: Internet-Drafts@ietf.org To: IETF-Announce: ; Subject: I-D ACTION:draft-newman-url-imap-02.txt A Revised Internet-Draft is available from the on-line Internet-Drafts directories. Title : IMAP URL Scheme Author(s) : C. Newman Filename : draft-newman-url-imap-02.txt Pages : 8 Date : 11/12/1996 IMAP [IMAP4] is a rich protocol for accessing remote message stores. It provides an ideal mechanism for accessing public mailing list archives as well as private and shared message stores. This document defines a URL scheme for referencing objects on an IMAP server. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-newman-url-imap-02.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-newman-url-imap-02.txt Internet-Drafts directories are located at: o Africa: ftp.is.co.za o Europe: nic.nordu.net ftp.nis.garr.it o Pacific Rim: munnari.oz.au o US East Coast: ds.internic.net o US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-newman-url-imap-02.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e., documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ---559023410-684387517-848080551=:26694 Content-Type: MULTIPART/ALTERNATIVE; BOUNDARY="-559023410-1903590565-848080551=:26694" Content-ID: Content-Description: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---559023410-1903590565-848080551=:26694 Content-Type: MESSAGE/EXTERNAL-BODY; ACCESS-TYPE=mail-server; SERVER="mailserv@ds.internic.net" Content-ID: ---559023410-1903590565-848080551=:26694 Content-Type: MESSAGE/EXTERNAL-BODY; NAME="draft-newman-url-imap-02.txt"; SITE="ds.internic.net"; ACCESS-TYPE=anon-ftp; DIRECTORY=internet-drafts Content-ID: ---559023410-1903590565-848080551=:26694-- ---559023410-684387517-848080551=:26694--   Received: from cnri by ietf.org id aa17449; 17 Nov 96 6:22 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa05684; 17 Nov 96 6:22 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id CAA07945 for imap-out; Sun, 17 Nov 1996 02:45:22 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from aun.uninett.no (aun.uninett.no [129.241.1.99]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id CAA07938 for ; Sun, 17 Nov 1996 02:45:17 -0800 Received: from dale.uninett.no (actually trhm6.or.uninett.no) by aun.uninett.no with SMTP (PP); Sun, 17 Nov 1996 11:44:57 +0100 Received: from dale.uninett.no (localhost [127.0.0.1]) by dale.uninett.no (8.6.9/8.6.12) with ESMTP id LAA12223; Sun, 17 Nov 1996 11:27:00 +0100 From: Harald.T.Alvestrand@uninett.no To: Chris Newman cc: IMAP Discusson List Subject: Re: I-D ACTION:draft-newman-url-imap-02.txt (fwd) In-reply-to: Your message of "Fri, 15 Nov 1996 09:55:51 PST." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12219.848226419.1@dale.uninett.no> Date: Sun, 17 Nov 1996 11:26:59 +0100 Message-ID: <12221.848226419@dale.uninett.no> 1) The message has gone to the RFC-Editor that we accepted rev 7 of IMAP4rev1 as a valid editorial update of rev 5, and that it could be published without any new IESG action. So that's done. 2) uri@bunyip.com gets you at least some people with experience in URL writing. See also my Web page: http://www.apps.ietf.org/apps/url-schemes.html Harald A   Received: from cnri by ietf.org id aa17537; 17 Nov 96 6:59 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa06053; 17 Nov 96 6:59 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id DAA08472 for imap-out; Sun, 17 Nov 1996 03:32:39 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from TYO2.gate.nec.co.jp (TYO2.gate.nec.co.jp [203.180.98.33]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id DAA08457; Sun, 17 Nov 1996 03:31:34 -0800 Received: from mailsv.nec.co.jp ([133.200.254.203]) by TYO2.gate.nec.co.jp (8.7.6+2.6Wbeta7/3.3Wb-NEC-TYO2) with ESMTP id UAA25215; Sun, 17 Nov 1996 20:31:32 +0900 (JST) Received: from engvan.do.mms.mt.nec.co.jp (engvan.do.mms.mt.nec.co.jp [10.16.3.202]) by mailsv.nec.co.jp (8.7.6+2.6Wbeta7/3.4W-96111415) with ESMTP id UAA20649; Sun, 17 Nov 1996 20:31:32 +0900 (JST) Received: from red.channel.or.jp ([10.40.1.43]) by engvan.do.mms.mt.nec.co.jp (8.7.5/3.3W9-02/01/96) with SMTP id UAA17273; Sun, 17 Nov 1996 20:34:32 +0900 (GMT) Date: Sun, 17 Nov 1996 20:34:32 +0900 (GMT) From: Fujio Ishii Abiko Message-Id: <199611171134.UAA17273@engvan.do.mms.mt.nec.co.jp> To: imap@cac.washington.edu, c-client@cac.washington.edu Subject: Please add me to this mailing list Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP X-Mailer: WeMail32[1.04] ID:1A1054 Please add me to this mailing list ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Fujio ISHII / SO Service Division / NEC Information Service,Ltd. ________________________________________________________________ email: fisii@neis.nec.co.jp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~   Received: from cnri by ietf.org id aa18515; 17 Nov 96 10:55 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa08752; 17 Nov 96 10:55 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id HAA09428 for imap-out; Sun, 17 Nov 1996 07:24:39 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from mail.car.chula.ac.th (mail.car.chula.ac.th [161.200.145.4]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id HAA09424 for ; Sun, 17 Nov 1996 07:24:21 -0800 Received: from localhost (kung@localhost) by mail.car.chula.ac.th (8.7.6/8.7.3) with SMTP id WAA14927 for ; Sun, 17 Nov 1996 22:25:17 +0700 (GMT+0700) Date: Sun, 17 Nov 1996 22:25:17 +0700 (THA) From: Tikumporn Oontiarnunt To: imap@cac.washington.edu Subject: The popular imap's engine. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Please suggest me about the most popular imap's engine. Thanks, Tikumporn Oontiarnunt.   Received: from cnri by ietf.org id aa22117; 17 Nov 96 18:36 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa23995; 17 Nov 96 18:36 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id PAA16371 for imap-out; Sun, 17 Nov 1996 15:02:28 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from THOR.INNOSOFT.COM (THOR.INNOSOFT.COM [192.160.253.66]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id PAA16367 for ; Sun, 17 Nov 1996 15:02:25 -0800 Received: from eleanor.innosoft.com ("port 38348"@ELEANOR.INNOSOFT.COM) by INNOSOFT.COM (PMDF V5.0-7 #8694) id <01IBYG5VG4P89OE2O3@INNOSOFT.COM>; Sun, 17 Nov 1996 15:01:23 -0800 (PST) Date: Sun, 17 Nov 1996 15:01:59 -0800 (PST) From: Chris Newman Subject: Re: I-D ACTION:draft-newman-url-imap-02.txt (fwd) In-reply-to: <12221.848226419@dale.uninett.no> To: Harald.T.Alvestrand@uninett.no Cc: IMAP Discusson List Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT On Sun, 17 Nov 1996 Harald.T.Alvestrand@uninett.no wrote: > 1) The message has gone to the RFC-Editor that we accepted rev 7 of > IMAP4rev1 as a valid editorial update of rev 5, and that it could > be published without any new IESG action. So that's done. That is good news. > 2) uri@bunyip.com gets you at least some people with experience in > URL writing. See also my Web page: > http://www.apps.ietf.org/apps/url-schemes.html Thanks for the info. I believe the IMAP URL meets all your requirements, except that I haven't considered relative URLs. I think there is a bug in RFC 1808 for handling multiple parameters on relative URLs -- it doesn't allow a relative URL to replace some but not all of the parameters. I'll bring this up on the uri list. Based on RFC 1808, I will have to swap the order of the ";" and the "?" in the imap scheme.   Received: from cnri by ietf.org id aa29474; 18 Nov 96 14:43 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa18672; 18 Nov 96 14:43 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id KAA02578 for imap-out; Mon, 18 Nov 1996 10:13:14 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from po10.andrew.cmu.edu (PO10.ANDREW.CMU.EDU [128.2.10.110]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id KAA02574 for ; Mon, 18 Nov 1996 10:13:11 -0800 Received: (from postman@localhost) by po10.andrew.cmu.edu (8.8.2/8.8.2) id NAA00889 for imap@cac.washington.edu; Mon, 18 Nov 1996 13:13:02 -0500 Received: via switchmail; Mon, 18 Nov 1996 13:13:01 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 18 Nov 1996 13:10:59 -0500 (EST) Received: from hogtown.andrew.cmu.edu via qmail ID ; Mon, 18 Nov 1996 13:10:57 -0500 (EST) Received: from BatMail.robin.v2.14.CUILIB.3.45.SNAP.NOT.LINKED.hogtown.andrew.cmu.edu.sun4m.54 via MS.5.6.hogtown.andrew.cmu.edu.sun4_51; Mon, 18 Nov 1996 13:10:54 -0500 (EST) Message-ID: <4mY_Oiy00WBw01jdE0@andrew.cmu.edu> Date: Mon, 18 Nov 1996 13:10:54 -0500 (EST) From: John Gardiner Myers To: imap@cac.washington.edu Subject: POP3 authentication draft I have recently submitted new internet drafts for the base SASL spec, as well as the POP3 and SMTP AUTH commands. They should show up in a few days. Announcements of the new drafts should go to ietf-sasl@imc.org, where discussion of the drafts should take place. -- _.John Gardiner Myers Internet: jgm+@CMU.EDU LoseNet: ...!seismo!ihnp4!wiscvm.wisc.edu!give!up   Received: from cnri by ietf.org id aa11155; 18 Nov 96 16:11 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa21009; 18 Nov 96 16:11 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id MAA07517 for imap-out; Mon, 18 Nov 1996 12:11:51 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from mailhub.hcl.com (mhoutside.hcl.com [205.211.178.111]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id MAA07507 for ; Mon, 18 Nov 1996 12:11:45 -0800 Received: from alexk4.hcl.com (alexk.hcl.com [198.231.99.15]) by mailhub.hcl.com (8.7.6/8.7.3) with SMTP id PAA02593 for ; Mon, 18 Nov 1996 15:11:41 -0500 (EST) Date: Mon, 18 Nov 1996 15:11:41 -0500 (EST) From: "Alexander.Kvache" Message-Id: <199611182011.PAA02593@mailhub.hcl.com> To: imap@cac.washington.edu Content-Transfer-Encoding: Quoted-Printable X-Mailer: Hummingbird Columbus 2.0 Content-Type: text/plain Mime-Version: 1.0 help   Received: from cnri by ietf.org id aa11528; 18 Nov 96 16:20 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa21234; 18 Nov 96 16:20 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id MAA07210 for imap-out; Mon, 18 Nov 1996 12:39:46 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from mailhub.hcl.com (mhoutside.hcl.com [205.211.178.111]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id MAA07206 for ; Mon, 18 Nov 1996 12:39:42 -0800 Received: from alexk4.hcl.com (alexk.hcl.com [198.231.99.15]) by mailhub.hcl.com (8.7.6/8.7.3) with SMTP id PAA03499 for ; Mon, 18 Nov 1996 15:39:35 -0500 (EST) Date: Mon, 18 Nov 1996 15:39:35 -0500 (EST) From: "Alexander.Kvache" Message-Id: <199611182039.PAA03499@mailhub.hcl.com> To: imap@cac.washington.edu Content-Transfer-Encoding: Quoted-Printable X-Mailer: Hummingbird Columbus 2.0 Content-Type: text/plain Mime-Version: 1.0 help   Received: from cnri by ietf.org id aa11762; 18 Nov 96 16:29 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa21440; 18 Nov 96 16:29 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id MAA06963 for imap-out; Mon, 18 Nov 1996 12:32:16 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from lacroix.wildbear.on.ca (lacroix.wildbear.on.ca [199.246.132.198]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id MAA06959 for ; Mon, 18 Nov 1996 12:32:11 -0800 Received: by lacroix.wildbear.on.ca from localhost (router,SLmailNT V3.0 (alpha 1)); Mon, 18 Nov 1996 15:26:30 -0500 Received: by lacroix.wildbear.on.ca from tester.wildbear.on.ca (199.246.132.199::mail daemon,SLmailNT V3.0 (alpha 1)); Mon, 18 Nov 1996 15:26:29 -0500 Message-Id: <3.0.32.19961118153036.00ce94c0@lacroix> X-Sender: "Jack De Winter" X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 18 Nov 1996 15:30:37 -0500 To: imap@cac.washington.edu From: Jack De Winter Subject: Do we have address books for IMAP? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I was reading an article in one of the newsgroups over the weekend, and their seems to be a suggestion that the IMAP protocol, or an extension, provided for global address books within a given domain (i.e. company wide and personal books). I know we have the ACLs to take care of the 'who can access it' parts, but do we have something to perform the action of the address books themselves? regards, Jack   Received: from cnri by ietf.org id aa12171; 18 Nov 96 16:34 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa21581; 18 Nov 96 16:34 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id MAA07283 for imap-out; Mon, 18 Nov 1996 12:42:24 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from mailhub.hcl.com (mhoutside.hcl.com [205.211.178.111]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id MAA07275 for ; Mon, 18 Nov 1996 12:42:03 -0800 Received: from alexk4.hcl.com (alexk.hcl.com [198.231.99.15]) by mailhub.hcl.com (8.7.6/8.7.3) with SMTP id PAA03569 for ; Mon, 18 Nov 1996 15:41:57 -0500 (EST) Date: Mon, 18 Nov 1996 15:41:57 -0500 (EST) From: "Alexander.Kvache" Message-Id: <199611182041.PAA03569@mailhub.hcl.com> To: imap@cac.washington.edu Content-Transfer-Encoding: Quoted-Printable X-Mailer: Hummingbird Columbus 2.0 Content-Type: text/plain Mime-Version: 1.0 unsubscribe   Received: from cnri by ietf.org id aa16262; 18 Nov 96 17:12 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa22872; 18 Nov 96 17:12 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id NAA09777 for imap-out; Mon, 18 Nov 1996 13:25:33 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from THOR.INNOSOFT.COM (THOR.INNOSOFT.COM [192.160.253.66]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id NAA09773 for ; Mon, 18 Nov 1996 13:25:27 -0800 Received: from eleanor.innosoft.com ("port 39704"@ELEANOR.INNOSOFT.COM) by INNOSOFT.COM (PMDF V5.0-8 #8694) id <01IBZR26SUPE9OEFKV@INNOSOFT.COM> for imap@cac.washington.edu; Mon, 18 Nov 1996 13:24:34 -0800 (PST) Date: Mon, 18 Nov 1996 13:25:10 -0800 (PST) From: Chris Newman Subject: Re: Do we have address books for IMAP? In-reply-to: <3.0.32.19961118153036.00ce94c0@lacroix> To: IMAP Discusson List Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT On Mon, 18 Nov 1996, Jack De Winter wrote: > I was reading an article in one of the newsgroups over > the weekend, and their seems to be a suggestion that the > IMAP protocol, or an extension, provided for global > address books within a given domain (i.e. company wide > and personal books). I know we have the ACLs to take > care of the 'who can access it' parts, but do we have > something to perform the action of the address books > themselves? IMAP has no support for address books because it is a "Message Access" protocol and not a "Directory Service" or "Application Configuration" protocol. Most clients access company directories through CSO/PH or LDAP. IMSP/ACAP is the place to go for personal address books and other application configuration info.   Received: from cnri by ietf.org id aa24111; 18 Nov 96 18:47 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa24666; 18 Nov 96 18:47 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id OAA13304 for imap-out; Mon, 18 Nov 1996 14:51:11 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from lacroix.wildbear.on.ca (lacroix.wildbear.on.ca [199.246.132.198]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id OAA13298 for ; Mon, 18 Nov 1996 14:51:07 -0800 Received: by lacroix.wildbear.on.ca from localhost (router,SLmailNT V3.0 (alpha 1)); Mon, 18 Nov 1996 17:45:31 -0500 Received: by lacroix.wildbear.on.ca from tester.wildbear.on.ca (199.246.132.199::mail daemon,SLmailNT V3.0 (alpha 1)); Mon, 18 Nov 1996 17:45:31 -0500 Message-Id: <3.0.32.19961118174936.00cf2140@lacroix> X-Sender: "Jack De Winter" X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 18 Nov 1996 17:49:36 -0500 To: Chris Newman , IMAP Discusson List From: Jack De Winter Subject: Re: Do we have address books for IMAP? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Chris wrote: >> and personal books). I know we have the ACLs to take >> care of the 'who can access it' parts, but do we have >> something to perform the action of the address books >> themselves? > >IMAP has no support for address books because it is a "Message Access" >protocol and not a "Directory Service" or "Application Configuration" >protocol. Most clients access company directories through CSO/PH or LDAP. >IMSP/ACAP is the place to go for personal address books and other >application configuration info. Fiar enough. How about me rephrasing my question to: is there any means or plan for an IMAP client to allow access to a company directory through LDAP or CS/PH or ACAP? Or is it a matter of opening multiple connections (for company and personal with the above information, I would assume 3 connections) to provide the access to both company and personal directories while using IMAP? regards, Jack   Received: from cnri by ietf.org id aa07084; 18 Nov 96 23:26 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa00475; 18 Nov 96 23:26 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id TAA18138 for imap-out; Mon, 18 Nov 1996 19:48:22 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from moon.nbn.com (moon.nbn.com [199.4.65.1]) by mx1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id TAA18134 for ; Mon, 18 Nov 1996 19:48:15 -0800 Received: from candle.brasslantern.com (srf-69.nbn.com [199.4.64.69]) by moon.nbn.com (8.8.2/8.8.2/MOON) with ESMTP id TAA02537; Mon, 18 Nov 1996 19:48:02 -0800 (PST) Received: (from schaefer@localhost) by candle.brasslantern.com (8.6.12/8.6.12) id TAA00332; Mon, 18 Nov 1996 19:51:28 -0800 From: Bart Schaefer Message-Id: <961118195127.ZM331@candle.brasslantern.com> Date: Mon, 18 Nov 1996 19:51:27 -0800 In-Reply-To: "Jack De Winter" "Re: Do we have address books for IMAP?" (Nov 18, 5:49pm) References: <3.0.32.19961118174936.00cf2140@lacroix> Reply-To: schaefer@nbn.com X-Mailer: Z-Mail (4.0b.820 20aug96) To: Jack De Winter , IMAP Discusson List Subject: Re: Do we have address books for IMAP? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Nov 18, 5:49pm, Jack De Winter wrote: } Subject: Re: Do we have address books for IMAP? } } is there any means or plan for an IMAP client to allow access to a } company directory through LDAP or CS/PH or ACAP? Or is it a matter of } opening multiple connections (for company and personal with the above } information, I would assume 3 connections) to provide the access to } both company and personal directories while using IMAP? I believe the answer to each question is, "Yes, of course." Or did you mean, in your first question, to ask whether there are any IMAP *servers* that plan to provide an extension for directory access? In those *clients* that plan to provide such access, the client will simply open all necessary connections. Does it make a difference? -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.nbn.com/people/lantern   Received: from cnri by ietf.org id aa10221; 26 Nov 96 12:41 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa17058; 26 Nov 96 12:41 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id IAA22976 for imap-out; Tue, 26 Nov 1996 08:28:43 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from socrates.nca.asu.edu (socrates.ED.ASU.EDU [129.219.88.66]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id IAA22972 for ; Tue, 26 Nov 1996 08:28:40 -0800 Received: from kirk.nca.asu.edu (kirk.nca.asu.edu [129.219.88.141]) by socrates.nca.asu.edu (8.6.12/8.6.12) with SMTP id JAA04581 for ; Tue, 26 Nov 1996 09:28:36 -0700 Date: Tue, 26 Nov 1996 09:26:29 -0700 () From: "C. R. Oldham" Reply-To: "C. R. Oldham" To: imap@cac.washington.edu Subject: procmail and imap. Message-ID: X-X-Sender: cro@socrates.nca.asu.edu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Greetings, What are the implications of using procmail as the delivery agent on a server running SunOS 4.1.3 or Solaris 2.5.1 and the UW imapd version 4.beta where users retrieve their mail via IMAP clients? Does it work? What about file locking? It seems that procmail uses locking techniques that are compatible with the UW imapd (according to http://www.cac.washington.edu/pine/tech-notes/low-level.html#locking and http://www.cac.washington.edu/pine/QandA/sysadmins.html#xtocid7145 but I just wanted a little confirmation from someone who was using it. Thanks, -- | Charles R. (C. R.) Oldham | NCA Commission on Schools | | cro@nca.asu.edu | Arizona St. Univ., PO Box 873011 | | V:602/965-8700 F:602/965-9423 |________ Tempe, AZ 85287-3011_ | | "I like it!"--Citizen G'Kar, Babylon 5 | #include X_>|   Received: from cnri by ietf.org id aa26188; 26 Nov 96 17:04 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa25158; 26 Nov 96 17:03 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id NAA00555 for imap-out; Tue, 26 Nov 1996 13:11:39 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id NAA00551 for ; Tue, 26 Nov 1996 13:11:37 -0800 Received: from shiva1.cac.washington.edu (dlm@localhost) by shiva1.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id NAA05314; Tue, 26 Nov 1996 13:11:28 -0800 Date: Tue, 26 Nov 1996 13:11:21 -0800 (PST) From: David L Miller To: "C. R. Oldham" cc: imap@cac.washington.edu Subject: Re: procmail and imap. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Yes, it does work. If you are using the default mbox (aka bezerk) format folders, you shouldn't need anything special. If you are using an alternate format, such as Tenex, you can deliver mail from procmail using tmail (see ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z) with a rule like :0 | sed -e 1d | tmail $USER The sed is there to get rid of the "From " line that sendmail prepends to the message. --DLM -- |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing, Box 354841 4545 15th Ave NE, Seattle WA 98105, USA Stardate: [-31]8484.41 On Tue, 26 Nov 1996, C. R. Oldham wrote: > Sendmail-From: imap-request@cac.washington.edu Tue Nov 26 09:03:15 1996 > Errors-To: owner-imap@cac.washington.edu > Sender: owner-imap@cac.washington.edu > Date: Tue, 26 Nov 1996 09:26:29 -0700 () > From: "C. R. Oldham" > To: imap@cac.washington.edu > Subject: procmail and imap. > Message-ID: > X-X-Sender: cro@socrates.nca.asu.edu > > Greetings, > > What are the implications of using procmail as the delivery agent on a > server running SunOS 4.1.3 or Solaris 2.5.1 and the UW imapd version > 4.beta where users retrieve their mail via IMAP clients? Does it work? > What about file locking? It seems that procmail uses locking techniques > that are compatible with the UW imapd (according to > > http://www.cac.washington.edu/pine/tech-notes/low-level.html#locking > > and > > http://www.cac.washington.edu/pine/QandA/sysadmins.html#xtocid7145 > > but I just wanted a little confirmation from someone who was using it. > > Thanks, > > -- > | Charles R. (C. R.) Oldham | NCA Commission on Schools | > | cro@nca.asu.edu | Arizona St. Univ., PO Box 873011 | > | V:602/965-8700 F:602/965-9423 |________ Tempe, AZ 85287-3011_ | > | "I like it!"--Citizen G'Kar, Babylon 5 | #include X_>| > > >   Received: from cnri by ietf.org id aa02867; 26 Nov 96 18:26 EST Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa27224; 26 Nov 96 18:26 EST Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id SAA15294 for uri-out; Tue, 26 Nov 1996 18:11:43 -0500 Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id SAA15289 for ; Tue, 26 Nov 1996 18:11:41 -0500 Received: from THOR.INNOSOFT.COM by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA20053 (mail destined for uri@services.bunyip.com); Tue, 26 Nov 96 18:11:38 -0500 Received: from eleanor.innosoft.com ("port 42573"@ELEANOR.INNOSOFT.COM) by INNOSOFT.COM (PMDF V5.0-8 #8694) id <01ICB139XYPQ9ODRDJ@INNOSOFT.COM>; Tue, 26 Nov 1996 15:10:29 -0800 (PST) Date: Tue, 26 Nov 1996 15:11:07 -0800 (PST) From: Chris Newman Subject: Re: IMAP URLs In-Reply-To: <96Nov26.073043pdt."135"@palimpsest.parc.xerox.com> To: Larry Masinter Cc: URI list , IMAP Discusson List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: owner-uri@bunyip.com Precedence: bulk On Tue, 26 Nov 1996, Larry Masinter wrote: > The generic URL syntax allows "=" and ";" in the part of > , so you could use > > imap://;auth=KERBEROS_V4@minbari.org/ > > to put the authentication method in the user field. The generic syntax > for the IMAP URL scheme should be careful to document which things are > URL-encoded, though. Right now, RFC 1730 says that a user name can > either be an atom or a string, but the draft-newman-url-imap-02 says > that the 'login' terminal follows 1738 syntax. These are good comments. I have submitted a new document, and placed an htmlized version at: The major changes from version -02 are: (1) moving the ";AUTH=" as suggested and (2) adding a section on relative IMAP URLs. If I don't get any substantive complaints by the end of the IETF meeting, I'll ask for this to move to proposed standard.   Received: from cnri by ietf.org id aa10357; 26 Nov 96 19:27 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa28594; 26 Nov 96 19:27 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) id PAA05082 for imap-out; Tue, 26 Nov 1996 15:51:14 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.100.202]) by mx2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with ESMTP id PAA05078 for ; Tue, 26 Nov 1996 15:51:12 -0800 Received: from localhost (skramer@localhost) by shiva2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id PAA05576 for ; Tue, 26 Nov 1996 15:51:11 -0800 Date: Tue, 26 Nov 1996 15:51:07 -0800 (PST) From: Stefan Kramer Reply-To: Stefan Kramer To: imap@cac.washington.edu Subject: 9 presentations from 2nd Int'l. IMAP Meeting online Message-ID: Organization: "University of Washington, Computing and Communications" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII For those interested in the presentations of the Second International IMAP Meeting: we now have links to nine of them available at http://www.washington.edu/imap/meeting.2nd/present/ ------------------------------------------------------------ Stefan Kramer skramer@cac.washington.edu University of Washington Computing & Communications ------------------------------------------------------------   Received: from cnri by ietf.org id aa10999; 26 Nov 96 19:36 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa28773; 26 Nov 96 19:36 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) id PAA03714 for imap-out; Tue, 26 Nov 1996 15:56:27 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.100.202]) by mx1.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) with ESMTP id PAA03707; Tue, 26 Nov 1996 15:56:20 -0800 Received: from localhost (skramer@localhost) by shiva2.cac.washington.edu (8.8.2+UW96.10/8.8.2+UW96.10) with SMTP id PAA05698; Tue, 26 Nov 1996 15:55:18 -0800 Date: Tue, 26 Nov 1996 15:55:15 -0800 (PST) From: Stefan Kramer Reply-To: Stefan Kramer To: "Contacts for (and people interested in) products supporting IMAP": ; Subject: Inventory of IMAP products now on World Wide Web Message-ID: Organization: "University of Washington, Computing and Communications" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Greetings, You are receiving this message because you are either a subscriber to the University of Washington's IMAP mailing list, or (to the best of our knowledge) a contact for a software product supporting IMAP, the Internet Message Access Protocol. We have completed converting the "Inventory of known software supporting IMAP" formerly found at the URL ftp://ftp.cac.washington.edu/imap/imap.software to HTML format; the result can now be found at the URL http://www.imap.org/products.html The purpose of this message is both to inform you of the completion of this update, and to ask for your assistance in making, and keeping, the Inventory up-to-date. If you are the creator of an IMAP-supporting product listed in the Inventory, or know of one that *should* be listed there, please take a moment to visit the Inventory and review the information we have listed there (for your product). If any of the information is incorrect or incomplete, please let us know by completing the comments form, a link to which appears at the bottom of individual product and product listing pages; or by sending email to: software-list@imap.org For each product, we are attempting to show the following information: Source: (the creator/vendor/publisher of the software) Software type: Client / Server/ Tool / Development Kit / Other Supports MIME: Yes / No (for client software) Supports disconnected use: No / Yes (for client software) Latest IMAP version incorporated: 2bis / 4 / 4rev1 Development status: Released / Planned or in development / Obsolete Distribution method: Commercial / Shareware / Free of Charge Platforms: DOS / Windows 3.X / Windows 95 / Windows NT / Unix (GUI) / Unix (character) / Macintosh / OS/2 / NeXT Product description URL: Press release URL: Contact email address: Mailing list about product: Subscription request email address: Participation email address: Usenet newsgroup about product: Additional Comments: (Note: unless there are significant differences between versions relating to the product's IMAP support, we are not showing the "current version" since that information should be readily accessible via the Product description URL.) Thank you in advance for information you can provide that helps to bring and keep the inventory up-to-date. ------------------------------------------------------------ Stefan Kramer skramer@cac.washington.edu The IMAP Connection WWW site: http://www.imap.org/ Computing & Communications University of Washington ------------------------------------------------------------   Received: from cnri by ietf.org id aa27204; 27 Nov 96 16:26 EST Received: from mx1.cac.washington.edu by CNRI.Reston.VA.US id aa22620; 27 Nov 96 16:26 EST Received: (from daemon@localhost) by mx1.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) id MAA25697 for imap-out; Wed, 27 Nov 1996 12:25:40 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from Tomobiki-Cho.CAC.Washington.EDU (tomobiki-cho.cac.washington.edu [128.95.135.58]) by mx1.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) with ESMTP id MAA25690 for ; Wed, 27 Nov 1996 12:25:35 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (8.7.5/UW-NDC Revision: 2.28 ) id MAA16269; Wed, 27 Nov 1996 12:25:32 -0800 (PST) Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67e/UW-NDC/Panda Revision: 2.27.MRC ) id AA02675; Wed, 27 Nov 96 12:25:27 -0800 Date: Wed, 27 Nov 1996 12:24:48 -0800 (PST) From: Mark Crispin Subject: re: Saving sent mail on remote folders? To: Jose Agustin Lopez Bueno Cc: IMAP Interest List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 27 Nov 1996 20:19:20 +0100 (MET), Jose Agustin Lopez Bueno wrote: > I ll like that my > program (on IMAP mode) could save the sent message on a remote folder > in the IMAP server automatically (like Pine do in sentmail folder) > and copy local PC messages on remote folders. > Is it possible using IMAP protocol? I have read the IMAP rfcs and I do not > find that topic. Please, every pointer well be welcomed. Isn't the APPEND command what you want for this case?   Received: from cnri by ietf.org id ad29226; 27 Nov 96 16:59 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa21479; 27 Nov 96 15:38 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) id LAA25159 for imap-out; Wed, 27 Nov 1996 11:22:40 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from iluso.ci.uv.es (iluso.ci.uv.es [147.156.1.1]) by mx2.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) with SMTP id LAA25090 for ; Wed, 27 Nov 1996 11:19:44 -0800 Received: by iluso.ci.uv.es (1.37.109.4/16.2) id AA21267; Wed, 27 Nov 96 20:19:21 +0100 Date: Wed, 27 Nov 1996 20:19:20 +0100 (MET) From: Jose Agustin Lopez Bueno To: imap@cac.washington.edu Subject: Saving sent mail on remote folders? Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, all. I have a question for the list. I have implemented a IMAP and POP windows client (Winbox, version 3.0, see my sygnature below for get it). I am implementing the release 3.1. I ll like that my program (on IMAP mode) could save the sent message on a remote folder in the IMAP server automatically (like Pine do in sentmail folder) and copy local PC messages on remote folders. Is it possible using IMAP protocol? I have read the IMAP rfcs and I do not find that topic. Please, every pointer well be welcomed. Best regards, Agustin =============================== | Jose Agustin Lopez Bueno | | E-Mail: Agustin.Lopez@uv.es | | | | http://www.uv.es/~lopezj/ | | | | Tel: +34-6-3864310 | | Fax: +34-6-3864200 | | Servicio de Informatica | | Universidad de Valencia | ===============================   Received: from cnri by ietf.org id aa07780; 30 Nov 96 4:04 EST Received: from mx2.cac.washington.edu by CNRI.Reston.VA.US id aa04365; 30 Nov 96 4:04 EST Received: (from daemon@localhost) by mx2.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) id AAA15170 for imap-out; Sat, 30 Nov 1996 00:11:54 -0800 Errors-To: owner-imap@cac.washington.edu Sender: owner-imap@cac.washington.edu Received: from thymaster.interaccess.com (thymaster.interaccess.com [198.80.0.36]) by mx2.cac.washington.edu (8.8.2+UW96.11/8.8.2+UW96.10) with ESMTP id AAA15166 for ; Sat, 30 Nov 1996 00:11:50 -0800 Received: from milleniumfalcon (d104.nnb.interaccess.com [204.148.86.104]) by thymaster.interaccess.com (8.8.3/8.8.3) with SMTP id CAA11764 for ; Sat, 30 Nov 1996 02:11:47 -0600 (CST) Date: Sat, 30 Nov 1996 02:11:47 -0600 (CST) Message-Id: <199611300811.CAA11764@thymaster.interaccess.com> From: Slippery Jim DiGriz X-Priority: Normal Content-Type: text/plain To: imap@cac.washington.edu Subject: unsubscribe X-Mailer: Pronto Mail [ver 3.04 (1006)] Mime-Version: 1.0 Content-Transfer-Encoding: 7bit