Description
Format one restricted nonempty local@domain Content-ID in angle brackets; no uniqueness, message identity or full RFC mailbox syntax inference.
A media type has a type/subtype token and may carry named parameters. Multipart content uses explicit boundary delimiter lines around its parts. Token case rules, parameter quoting, repeated records and exact line endings affect how a representation is interpreted; a lexical check is narrower than parsing a complete message.1
Format one restricted nonempty local@domain Content-ID in angle brackets; no uniqueness, message identity or full RFC mailbox syntax inference.
When to use this tool
Use this tool to format one restricted nonempty local@domain Content-ID in angle brackets; no uniqueness, message identity or full RFC mailbox syntax inference.
How to use the tool and how it works
- Enter contentId using the field definitions below.
- Run the operation. Correct input errors before interpreting an output.
- Read result.token. Use the ordering, boundary rules and absence conditions described below.
Require an unbracketed content ID with one separating at-sign and no whitespace or brackets, then add the outer angle brackets.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| contentId | Unbracketed content ID under the declared narrow grammar. | Text, at most 8,192 UTF-16 code units; the operation’s grammar also applies. |
| Output field | Interpretation |
|---|---|
| result | Object containing the named fields below. |
| result.token | Angle-bracketed content-ID token under the narrow accepted syntax. |
{
"input": {
"contentId": "a@b"
},
"output": {
"result": {
"token": "<a@b>"
}
}
}Limitations and assumptions
- No uniqueness, mailbox ownership or MIME part existence is established.
- Supported boundary strings contain 1–70 characters from the declared MIME boundary subset and cannot end in a space. Single-byte envelope budgets are distinct from UTF-8 text byte counts and from a complete MIME transport.
- Every declared top-level input field is required and unexpected fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
- Numeric outputs must be finite and no larger in absolute magnitude than the safe-integer limit; operations returning exact large integers use decimal text. Positions are zero-based and spans end exclusively unless the operation explicitly states a different convention.
Alternative or Complementary methods
Choose the target media-type and multipart conventions explicitly. Use a complete MIME parser for nested messages and encodings; these record and delimiter tools handle only their stated representations.
References
-
RFC 2046: MIME Media Types — RFC Editor
-
Tool behavior and example: Content ID Bracket Token Formatter — tool.io
Similar or alternative tools
- Content ID Bracket Token Parser
Parse one restricted Content-ID angle-bracket token containing exactly one nonempty local@domain without whitespace, comments or quoted local parts; no mailbox validity claim.
- Media Type Record Formatter
Format an explicit MIME media type and ordered parameter observations with token/quoted value serialization; preserves duplicates, no registered-value canonicalization.