> According to last draft for IMAP server is allowed to return the folloing:
Yes, however today's IMAP4 *protocol* *standard* operates as I
described.
If and when a particular draft becomes an internet *standard* we
can then debate its characteristics. Internet standards based
applications are w
Lyndon Nerenberg wrote:
> The IMAP4 specification is quite clear on this.
>
> The text after "* OK" in the greeting is freeform (other than any
> elements). The appearance of "IMAP4" or "IMAP4rev1"
> there is meaningless when determining which version of IMAP4 is
> supported.
According to last
The IMAP4 specification is quite clear on this.
The text after "* OK" in the greeting is freeform (other than any
elements). The appearance of "IMAP4" or "IMAP4rev1"
there is meaningless when determining which version of IMAP4 is
supported.
You discover the level of IMAP4 the server supports by
Cillian Sharkey wrote:
>
> The current server greeting is:
>
> * OK Cyrus IMAP4 server ready
>
> Should the server greeting display IMAP4rev1 instead of IMAP4? i.e:
>
> * OK Cyrus IMAP4rev1 server ready
>
> The NetxAP perl modules check for and require th
The current server greeting is:
* OK Cyrus IMAP4 server ready
Should the server greeting display IMAP4rev1 instead of IMAP4? i.e:
* OK Cyrus IMAP4rev1 server ready
The NetxAP perl modules check for and require the presence of IMAP4rev1 in the
greeting text (so it needs to be tweaked