IMAP4 Multi-Accessed Mailbox Practice
draft-melnikov-imap-rfc2180bis-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Mike Gahrns , Alexey Melnikov | ||
| Last updated | 2004-10-19 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-melnikov-imap-rfc2180bis-00.txt
Abstract
IMAP4[IMAP4] is rich client/server protocol that allows a client to access and manipulate electronic mail messages on a server. Within the protocol framework, it is possible to have differing results for particular client/server interactions. If a protocol does not allow for this, it is often unduly restrictive.
Authors
Mike Gahrns
(mikega@microsoft.com)
Alexey Melnikov
(alexey.melnikov@isode.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)