Skip to content

Main content

Mail Display Name Angle Split Tool

Split a simple unquoted display-name and angle-address mailbox. Comments, quoted names and complete RFC 5322 address validation are outside this restricted grammar.

Loading tool…

Description

Reject CR/LF and require a narrow form with a display name followed by an address enclosed in angle brackets with nonwhitespace address parts around @.

Protocol fields often encode several values in a small token. Checking its supported grammar or extracting a component is narrower than validating a complete message or the behavior of its sender.

Reject CR/LF and require a narrow form with a display name followed by an address enclosed in angle brackets with nonwhitespace address parts around @.

When to use this tool

Use Mail Display Name Angle Split when you need to inspect or format the supported protocol field in isolation.

How to use the tool and how it works

  1. Enter mailbox. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read displayName, address. Use the output convention below.

Reject CR/LF and require a narrow form with a display name followed by an address enclosed in angle brackets with nonwhitespace address parts around @. Reject quotes and parentheses in the display part, trim it, and return address unchanged.1

Input fieldMeaning and unitsAccepted input
mailboxMailboxRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
displayNameDisplay NameRequired. Text; maximum UTF-16 length 8192.
addressAddressRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "mailbox": "Ada Lovelace <ada@example.org>"
  },
  "output": {
    "displayName": "Ada Lovelace",
    "address": "ada@example.org"
  }
}

Limitations and assumptions

  • This is not a full mailbox grammar or deliverability check; comments, quoted display names, domain literals, and address validity are not comprehensively handled.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Validate the complete message and its context with the relevant protocol implementation when interoperability matters.

References

  1. Calculation and input contract: parse/mail-display-name-angle-split — tool.io

Similar or alternative tools