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

IETF · RFC · RFC6409

RFC6409 · Message Submission for Mail

Message Submission for Mail

This memo splits message submission from message relay, allowing each service to operate according to its own rules (for security, policy, etc.), and specifies what actions are to be taken by a submission server. Message relay is unaffected, and continues to use SMTP over port 25. When conforming to this document, message submission uses the protocol specified here, normally over port 587. This separation of function offers a number of benefits, including the ability to apply specific security or policy requirements. [STANDARDS-TRACK]

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

This memo splits message submission from message relay, allowing each service to operate according to its own rules (for security, policy, etc.), and specifies what actions are to be taken by a submission server. Message relay is unaffected, and continues to use SMTP over port 25. When conforming to this document, message submission uses the protocol specified here, normally over port 587. This separation of function offers a number of benefits, including the ability to apply specific security or policy requirements. [STANDARDS-TRACK]

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

obsoletes: RFC4409

updated_by: RFC8314

is_also: STD72

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

Полные импортированные сведения карточки
{
  "id": "RFC6409",
  "number": 6409,
  "title_en": "Message Submission for Mail",
  "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": "This memo splits message submission from message relay, allowing each service to operate according to its own rules (for security, policy, etc.), and specifies what actions are to be taken by a submission server. Message relay is unaffected, and continues to use SMTP over port 25. When conforming to this document, message submission uses the protocol specified here, normally over port 587. This separation of function offers a number of benefits, including the ability to apply specific security or policy requirements. [STANDARDS-TRACK]",
  "authors": [
    "R. Gellens",
    "J. Klensin"
  ],
  "organizations": [],
  "publication_date": "2011-11-01",
  "current_status": "INTERNET STANDARD",
  "current_status_ru": "Стандарт Интернета",
  "publication_status": "INTERNET STANDARD",
  "publication_status_ru": "Стандарт Интернета",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "app",
  "area_ru": "app",
  "working_group": "yam",
  "source_draft": "draft-ietf-yam-rfc4409bis-03",
  "page_count": 20,
  "doi": "10.17487/RFC6409",
  "keywords": [
    "Text",
    "Internationalization",
    "ASCII",
    "Unicode",
    "UTF-8"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [
      "RFC4409"
    ],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC8314"
    ],
    "is_also": [
      "STD72"
    ],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc6409/",
    "html": "https://www.rfc-editor.org/rfc/rfc6409.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc6409.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc6409/"
  }
}