Internet Message Access Protocol (IMAP) - URLAUTH Extension
RFC 4467
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['imap url', 'imapurl']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "M. Crispin": changed name from "Mark Crispin" to "M. Crispin", cleared country (was "Seattle, WA 98105-4527"), changed order from "0" to "1" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This document describes the URLAUTH extension to the Internet Message Access Protocol (IMAP) (RFC 3501 … Received changes through RFC Editor sync (changed abstract to 'This document describes the URLAUTH extension to the Internet Message Access Protocol (IMAP) (RFC 3501) and the IMAP URL Scheme (IMAPURL) (RFC 2192). This extension provides a means by which an IMAP client can use URLs carrying authorization to access limited message data on the IMAP server. An IMAP server that supports this extension indicates this with a capability name of "URLAUTH". [STANDARDS-TRACK]') |
|
2015-10-14
|
(System) | Notify list changed from gparsons@nortel.com, eburger@brooktrout.com to (None) |
|
2006-05-30
|
Amy Vezza | [Note]: 'RFC 4467' added by Amy Vezza |
|
2006-05-26
|
(System) | RFC published |