
datatracker.ietf.org/doc/draft-crispin-imapv
Preview meta tags from the datatracker.ietf.org website.
Linked Hostnames
10- 84 links todatatracker.ietf.org
- 6 links towww.ietf.org
- 6 links towww.rfc-editor.org
- 2 links togithub.com
- 1 link tomailarchive.ietf.org
- 1 link tostatus.ietf.org
- 1 link totrustee.ietf.org
- 1 link towww.iab.org
Thumbnail

Search Engine Appearance
https://datatracker.ietf.org/doc/draft-crispin-imapv
RFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 (RFC 3501, March 2003; obsoleted by RFC 9051)
Bing
RFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
https://datatracker.ietf.org/doc/draft-crispin-imapv
INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 (RFC 3501, March 2003; obsoleted by RFC 9051)
DuckDuckGo

RFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 (RFC 3501, March 2003; obsoleted by RFC 9051)
General Meta Tags
9- titleRFC 3501 - INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
- charsetutf-8
- X-UA-CompatibleIE=edge
- viewportwidth=device-width, initial-scale=1
- article:sectionIETF - Internet Engineering Task Force
Open Graph Meta Tags
10- og:titleRFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
- og:urlhttps://datatracker.ietf.org/doc/rfc3501/
- og:site_nameIETF Datatracker
- og:descriptionThe Internet Message Access Protocol, Version 4rev1 (IMAP4rev1) allows a client to access and manipulate electronic mail messages on a server. IMAP4rev1 permits manipulation of mailboxes (remote message folders) in a way that is functionally equivalent to local folders. IMAP4rev1 also provides the capability for an offline client to resynchronize with the server. IMAP4rev1 includes operations for creating, deleting, and renaming mailboxes, checking for new messages, permanently removing messages, setting and clearing flags, RFC 2822 and RFC 2045 parsing, searching, and selective fetching of message attributes, texts, and portions thereof. Messages in IMAP4rev1 are accessed by the use of numbers. These numbers are either message sequence numbers or unique identifiers. IMAP4rev1 supports a single server. A mechanism for accessing configuration information to support multiple IMAP4rev1 servers is discussed in RFC 2244. IMAP4rev1 does not specify a means of posting mail; this function is handled by a mail transfer protocol such as RFC 2821. [STANDARDS-TRACK]
- og:typearticle
Twitter Meta Tags
1- twitter:cardsummary_large_image
Link Tags
13- alternate/feed/document-changes/rfc3501/
- apple-touch-iconhttps://static.ietf.org/dt/12.41.0/ietf/images/ietf-logo-nor-180.png
- canonicalhttps://datatracker.ietf.org/doc/rfc3501/
- iconhttps://static.ietf.org/dt/12.41.0/ietf/images/ietf-logo-nor-32.png
- iconhttps://static.ietf.org/dt/12.41.0/ietf/images/ietf-logo-nor-16.png
Emails
4- mrc%40panda.com
- ned.freed%40mrochek.com
- [email protected]?subject=Mail%20regarding%20rfc3501
- [email protected]
Links
104- https://datatracker.ietf.org
- https://datatracker.ietf.org/accounts/create
- https://datatracker.ietf.org/accounts/login/?next=/doc/rfc3501
- https://datatracker.ietf.org/accounts/reset
- https://datatracker.ietf.org/accounts/settings