1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
IMAP4 Capabilities Registry (RFC2060)
Capability names MUST either begin with "X" or be standard or
standards-track IMAP4rev1 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".
Client implementations SHOULD NOT require any capability name other
than "IMAP4rev1", and MUST ignore any unknown capability names.
Capability Name Reference
--------------- ---------
ACL [RFC2086]
AUTH [RFC2060]
ID [RFC2971]
IDLE [RFC2177]
LITERAL+ [RFC2088]
LOGIN-REFERRALS [RFC2221]
LOGINDISABLED [RFC2595]
MAILBOX-REFERRALS [RFC2193]
NAMESPACE [RFC2342]
QUOTA [RFC2087]
STARTTLS [RFC2595]
UIDPLUS [RFC2359]
References
----------
[RFC2060] Crispin, M., "Internet Message Access Protocol Version
4rev1", RFC 2060, December 1996.
[RFC2086] Myers, J., "IMAP4 ACL extension", RFC 2086, January 1997.
[RFC2087] Myers, J., "IMAP4 QUOTA extension", RFC 2087, January 1997.
[RFC2088] Myers, J., "IMAP4 non-synchronizing literals", January 1997.
[RFC2177] Leiba, B., "IMAP4 IDLE command", RFC 2177, June 1997.
[RFC2193] Gahrns, M., "IMAP4 Mailbox Referrals", RFC 2193,
September 1997.
[RFC2221] Gahrns, M., "IMAP4 Login Referrals", RFC 2221, October 1997.
[RFC2342] Gahrns, M., Newman, C., "IMAP4 Namespace", RFC 2342, May 1998.
[RFC2359] Myers, J., "IMAP4 UIDPLUS extension", RFC 2359, June 1998.
[RFC2595] Newman, C., "Using TLS with IMAP, POP3 and ACAP", RFC 2595,
June 1999.
[RFC2971] Showalter, T. "IMAP4 ID extension", RFC 2971, October 2000.
(last updated Mar 23 2001)
[]
|
