re: why does CHECK | SELECT only sometimes return EXISTS

re: why does CHECK | SELECT only sometimes return EXISTS - why?

Mark Crispin <MRC@panda.com> Wed, 01 December 1993 08:02 UTC

Errors-To: owner-imap@cac.washington.edu
Date: Tue, 30 Nov 1993 23:43:07 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mark Crispin <MRC@panda.com>
Subject: re: why does CHECK | SELECT only sometimes return EXISTS - why?
To: "Steven D. Majewski" <sdm7g@elvis.med.virginia.edu>
Cc: IMAP Interest List <IMAP@cac.washington.edu>
In-Reply-To: <199312010431.AA17311@elvis.med.Virginia.EDU>
Message-Id: <MailManager.754731787.8471.mrc@Ikkoku-Kan.Panda.COM>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET="US-ASCII"

Hi -

     SELECT should *always* return a value for EXISTS.  If it doesn't, it is a
bug in the server.

     The version you are running, 6.0(30), is very old.  Please get a current
version of the IMAP toolkit from ftp.cac.washington.edu, file mail/imap.tar.Z

     The CHECK command does not necessarily return an EXISTS or RECENT value;
if it does not, you should use the current value (if nothing else, what you
got from SELECT).

     The current draft is draft-ietf-imap-imap2bis-02.txt, available from the
ftp.cac.washington.edu archive or from your favorate Internet drafts server.
It is going to be updated very soon (a matter of days).

Regards,

-- Mark --

why does CHECK | SELECT only sometimes return EXI… Steven D. Majewski
re: why does CHECK | SELECT only sometimes return… Mark Crispin