⌕ Поиск по атласу

IETF · RFC · RFC2180

RFC2180 · IMAP4 Multi-Accessed Mailbox Practice

IMAP4 Multi-Accessed Mailbox Practice

The behavior described in this document reflects the practice of some existing servers or behavior that the consensus of the IMAP mailing list has deemed to be reasonable. The behavior described within this document is believed to be [RFC-2060] compliant. However, this document is not meant to define IMAP4 compliance, nor is it an exhaustive list of valid IMAP4 behavior. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

Официальная английская аннотация

The behavior described in this document reflects the practice of some existing servers or behavior that the consensus of the IMAP mailing list has deemed to be reasonable. The behavior described within this document is believed to be [RFC-2060] compliant. However, this document is not meant to define IMAP4 compliance, nor is it an exhaustive list of valid IMAP4 behavior. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

Связи документа

Официальный источник · 1997-07-01

Полные импортированные сведения карточки
{
  "id": "RFC2180",
  "number": 2180,
  "title_en": "IMAP4 Multi-Accessed Mailbox Practice",
  "title_ru": "",
  "summary_ru": "",
  "purpose_ru": "",
  "use_ru": "",
  "full_translation_path": "",
  "full_translation_checked_at": "",
  "full_translation_source_sha256": "",
  "architect_note_ru": "",
  "topics_ru": [],
  "translation_state": "not_prepared",
  "verification_level": "not_prepared",
  "verification_level_ru": "Русская выжимка не подготовлена",
  "verification_note_ru": "",
  "abstract_en": "The behavior described in this document reflects the practice of some existing servers or behavior that the consensus of the IMAP mailing list has deemed to be reasonable. The behavior described within this document is believed to be [RFC-2060] compliant. However, this document is not meant to define IMAP4 compliance, nor is it an exhaustive list of valid IMAP4 behavior. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.",
  "authors": [
    "M. Gahrns"
  ],
  "organizations": [],
  "publication_date": "1997-07-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "Legacy",
  "stream_ru": "Исторический поток",
  "area": "",
  "area_ru": "",
  "working_group": "",
  "source_draft": "draft-gahrns-imap-practice-01",
  "page_count": 14,
  "doi": "10.17487/RFC2180",
  "keywords": [
    "Internet",
    "Message",
    "Access",
    "Protocol",
    "Client",
    "Server"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc2180/",
    "html": "https://www.rfc-editor.org/rfc/rfc2180.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc2180.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc2180/"
  }
}