References (Email Header)
ID references
DatatypeNot PIIidentifier
Value of the References header of an email message (RFC 5322, section 3.6.4): the Message-IDs of the earlier messages of the thread, separated by whitespace. A reply copies the References of the message it answers and appends that message's Message-ID, so mail clients can rebuild a thread even when some of its messages are missing.
- Categories
- Internet
- Countries
- Global (not tied to a country)
- Languages
- Common to most languages
- Quality
- 90/100 · missing: mapping (Wikidata, Schema.org, ...)
- Metacrafter rules
- 1 rule (1 by field name, 0 by value)
referencesfieldfield, common/internet.yaml
- Supported by tools
- metacrafter
Regular expression
^<[^<>@\s]+@[^<>@\s]+>(?:\s+<[^<>@\s]+@[^<>@\s]+>)*$Python re syntax.
Examples
| Value | Description |
|---|---|
| <1234@local.machine.example> <3456@example.net> | Second reply of the thread in RFC 5322, appendix A.2 |
| <1234@local.machine.example> | First reply of the thread in RFC 5322, appendix A.2 |
| 1234@local.machine.example, 3456@example.net invalid | No angle brackets |
Translations
| Language | Name | Description |
|---|---|---|
| Russian | Заголовок письма References | Значение заголовка References: Message-ID предыдущих писем цепочки через пробел (RFC 5322). |
Sources
- wikipedia: https://en.wikipedia.org/wiki/Message-ID
- doc: https://www.rfc-editor.org/rfc/rfc5322.html#section-3.6.4
Use this record
- Page URL:
http://registry.apicrafter.io/datatype/references - JSON: API v1 · legacy shape (used by metacrafter) · Markdown (for LLMs)
- Improve it: edit
data/datatypes/any/internet/references.yamlon GitHub