[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: new user with problems :)

To: Simon Josefsson <jas@pdc.kth.se>
Subject: Re: new user with problems :)
From: Lyndon Nerenberg <lyndon@esys.ca>
Date: Wed, 5 Aug 1998 10:32:48 -0600
Cc: Julio.Barreiro@cern.ch, gnus-imap@vic20.dzp.se, Donald Hunter <dhunter@atlan-tech.com>
In-Reply-To: <iluaf5jbpkg.fsf@xiphias.pdc.kth.se>
References: <iluaf5jbpkg.fsf@xiphias.pdc.kth.se> <199808041704.TAA28044@ion02.cern.ch> <vslnp3bzcz.fsf@atlan-tech.com>

Message-ID: <SIMEON.9808051048.A3838@warhol.esys.ca>
Priority: NORMAL
X-Mailer: Simeon for Aix Motif Version Mercury a8 Build (11)
MIME-Version: 1.0
Content-Type: Text/PLAIN; CHARSET=US-ASCII


> Fix in 0.3.15, I thought all IMAP4rev1 servers were backwards
> compatible with IMAP4, if so they should list IMAP4 as the first token
> in the CAPABILITY response.

The IMAP4 capability indicates conformance to RFC1730. The IMAP4rev1 
capability indicates conformance to RFC2060. It's allowed for a server to be 
1730 compliant, 2060 compliant, or both 1730 and 2060 compliant. A well 
written IMAP4* client will pay close attention to the IMAP4 and IMAP4rev1 
capabilities, and will only enable protocol features matching the capabilities 
advertised by the server. (And yes, all three permutations of the above exist 
in the field.)

--lyndon

References:
- Re: new user with problems :)
  - From: Simon Josefsson <jas@pdc.kth.se>
- new user with problems :)
  - From: Julio Barreiro Barreiro <julio.barreiro@cern.ch>
- Re: new user with problems :)
  - From: Donald Hunter <dhunter@atlan-tech.com>
- Re: new user with problems :)
  - From: Simon Josefsson <jas@pdc.kth.se>

Prev by Date: Re: new user with problems :)
Next by Date: Can't login with 0.3.14!
Prev by thread: Re: new user with problems :)
Next by thread: Re: new user with problems :)
Index(es):
- Date
- Thread