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

IETF · RFC · RFC4096

RFC4096 · Policy-Mandated Labels Such as "Adv:" in Email Subject Headers Considered Ineffective At Best

Policy-Mandated Labels Such as "Adv:" in Email Subject Headers Considered Ineffective At Best

This memo discusses policies that require certain labels to be inserted in the "Subject:" header of a mail message. Such policies are difficult to specify accurately while remaining compliant with key RFCs and are likely to be ineffective at best. This memo discusses an alternate, \%standards-compliant approach that is significantly simpler to specify and is somewhat less likely to be ineffective. This memo provides information for the Internet community.

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

This memo discusses policies that require certain labels to be inserted in the "Subject:" header of a mail message. Such policies are difficult to specify accurately while remaining compliant with key RFCs and are likely to be ineffective at best. This memo discusses an alternate, \%standards-compliant approach that is significantly simpler to specify and is somewhat less likely to be ineffective. This memo provides information for the Internet community.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC4096",
  "number": 4096,
  "title_en": "Policy-Mandated Labels Such as \"Adv:\" in Email Subject Headers Considered Ineffective At Best",
  "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 discusses policies that require certain labels to be inserted in the \"Subject:\" header of a mail message. Such policies are difficult to specify accurately while remaining compliant with key RFCs and are likely to be ineffective at best. This memo discusses an alternate, \\%standards-compliant approach that is significantly simpler to specify and is somewhat less likely to be ineffective. This memo provides information for the Internet community.",
  "authors": [
    "C. Malamud"
  ],
  "organizations": [],
  "publication_date": "2005-05-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "",
  "area_ru": "",
  "working_group": "NON WORKING GROUP",
  "source_draft": "draft-malamud-subject-line-05",
  "page_count": 14,
  "doi": "10.17487/RFC4096",
  "keywords": [],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc4096/",
    "html": "https://www.rfc-editor.org/rfc/rfc4096.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc4096.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc4096/"
  }
}