IMAP MESSAGELIMIT Extension
RFC 9738
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed author "L. Alves": changed name from "Luis Alves" to "L. Alves" |
|
2026-05-20
|
(System) | Changed author "V. Nagulakonda": changed name from "Vikram Nagulakonda" to "V. Nagulakonda" |
|
2026-05-20
|
(System) | Changed author "A. P. Achuthan": changed name from "ArunPrakash Achuthan" to "A. P. Achuthan" |
|
2026-05-20
|
(System) | Changed author "A. Melnikov": changed name from "Alexey Melnikov" to "A. Melnikov", changed affiliation from "Isode Limited" to "Isode" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2025-03-03
|
(System) | Received changes through RFC Editor sync (created document RFC 9738, created became rfc relationship between draft-ietf-extra-imap-messagelimit and RFC 9738, set abstract to 'The … Received changes through RFC Editor sync (created document RFC 9738, created became rfc relationship between draft-ietf-extra-imap-messagelimit and RFC 9738, set abstract to 'The MESSAGELIMIT extension of the Internet Message Access Protocol (RFCs 3501 and 9051) allows servers to announce a limit on the number of messages that can be processed in a single FETCH, SEARCH, STORE, COPY, or MOVE command (or their UID variants), or in a single APPEND or UID EXPUNGE command. This helps servers to control resource usage when performing various IMAP operations. This helps clients to know the message limit enforced by the corresponding IMAP server and avoid issuing commands that would exceed such limit.', set pages to 11, set standardization level to Experimental, added RFC published event at 2025-03-03) |
|
2025-03-03
|
(System) | RFC published |