LemonChannels.
View Source
RFC 2822 message identifiers: parsing, listing and rendering.
Message ids arrive in every shape a mail provider can invent — bracketed
(<abc@host>), bare, whitespace- or comma-separated in a References
header, already split into a list, or as a {name, value} header tuple. The
adapter, the thread store and outbound delivery all have to agree on what an
id is, so the parsing lives here rather than three times over.
Lists are capped at 25 entries, keeping the newest ones. References
grows without bound on a long thread and a mail server will reject an
oversized header, so the tail — the nearest ancestors, which is what a client
threads on — is the part worth keeping.
Summary
Functions
Renders an id for a header, or nil so the header can be omitted.
Renders a list of ids for a References header, or nil when empty.
Generates a new message id for a message sent from address.
Every id in a References-style value, oldest first.
The cap applied to reference chains.
Flattens several reference sets into one deduplicated, capped chain.
The bare id, brackets and whitespace stripped, or nil if there is none.
Functions
Renders an id for a header, or nil so the header can be omitted.
Renders a list of ids for a References header, or nil when empty.
Generates a new message id for a message sent from address.
Every id in a References-style value, oldest first.
Prefers bracketed ids; falls back to splitting on whitespace and commas for providers that hand over an unbracketed list.
@spec max_references() :: pos_integer()
The cap applied to reference chains.
Flattens several reference sets into one deduplicated, capped chain.
The bare id, brackets and whitespace stripped, or nil if there is none.