datatracker.ietf.org/doc/html/rfc3501

Preview meta tags from the datatracker.ietf.org website.

Linked Hostnames

4

Thumbnail

Search Engine Appearance

Google

https://datatracker.ietf.org/doc/html/rfc3501

RFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1

INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 (RFC 3501, ; obsoleted by RFC 9051)



Bing

RFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1

https://datatracker.ietf.org/doc/html/rfc3501

INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 (RFC 3501, ; obsoleted by RFC 9051)



DuckDuckGo

https://datatracker.ietf.org/doc/html/rfc3501

RFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1

INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 (RFC 3501, ; obsoleted by RFC 9051)

  • General Meta Tags

    9
    • title
      RFC 3501 - INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
    • charset
      utf-8
    • X-UA-Compatible
      IE=edge
    • viewport
      width=device-width, initial-scale=1
    • description
      INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 (RFC 3501, ; obsoleted by RFC 9051)
  • Open Graph Meta Tags

    10
    • og:title
      RFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
    • og:url
      https://datatracker.ietf.org/doc/html/rfc3501
    • og:site_name
      IETF Datatracker
    • og:description
      The 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:type
      article
  • Twitter Meta Tags

    1
    • twitter:card
      summary_large_image
  • Link Tags

    12
    • alternate
      /feed/document-changes/rfc3501/
    • apple-touch-icon
      https://static.ietf.org/dt/12.40.0/ietf/images/ietf-logo-nor-180.png
    • canonical
      https://datatracker.ietf.org/doc/html/rfc3501
    • icon
      https://static.ietf.org/dt/12.40.0/ietf/images/ietf-logo-nor-32.png
    • icon
      https://static.ietf.org/dt/12.40.0/ietf/images/ietf-logo-nor-16.png

Emails

2

Links

61