Can a business email address contain angle brackets?

For a public-facing small business, prefer a simple role address that avoids angle brackets, such as bookings@<short-name>.au, quotes@<short-name>.au, or sales@<short-name>.au, then test the exact setup before printing or publishing it.

Why angle brackets are a poor public choice

RFC 5321 section 4.1.2 defines the usual SMTP mailbox local part with the atext character set. Angle brackets (< and >) are not ordinary atext characters. They are reserved punctuation in email syntax. In RFC 5322, the common name-addr form wraps the real mailbox in angle brackets after a display name: Jess Noonan <jess@...>. That is header syntax for parsers, not a friendly public brand choice.

Mail providers rarely create or recommend public business addresses that rely on angle brackets inside the local part. Website forms, booking tools, CRMs, accounting packages and imported contact lists often reject or strip < and >, treating them as HTML tags, comparison operators, display-name punctuation, or invalid characters rather than part of a legitimate mailbox.

When customers see angle brackets in or around an address, they typically treat them as optional decoration for a display name, omit them when typing, confuse them with square brackets or parentheses, or ask the business to confirm the real mailbox. The same workflow concerns that make spaces, quotation marks and giving an email address over the phone hard are amplified when angle brackets are part of what customers must reproduce.

Hard to name, easy to confuse with display names

Most everyday addresses people recognise are unquoted local parts made of letters, digits, and a few common separators such as a period or hyphen. Angle brackets sit outside that familiar set.

Picture a business telling a customer an address that puts angle brackets around or inside the local part, such as <sales>@<short-name>.au or sales<desk>@<short-name>.au. The customer hears "less than sales greater than", "open angle bracket sales close angle bracket", "sales in arrows", or simply assumes the business is reading a display-name line and writes down only sales@.... On a phone call, people often skip the marks entirely because they sound like formatting instructions rather than characters to type.

On many mobile keyboards the less-than and greater-than signs sit behind a symbols layer and share keys with commas or periods on some layouts. Customers may type square brackets, parentheses, or nothing at all. That variability does not mean every customer will mistype the address. It means angle brackets introduce an interpretation choice where none would exist if the address were sales@<short-name>.au, bookings@<short-name>.au, or quotes@<short-name>.au instead.

Confusion with HTML, XML and comparison signs

One persistent source of confusion is that angle brackets already mean something else in everyday digital writing. People who edit websites, emails or documents are used to seeing < and > as HTML or XML tags, or as comparison operators in spreadsheets and code. When a public contact line shows angle brackets inside the mailbox, staff and customers may treat them as leftover markup rather than characters they must type.

In print and on screens, angle brackets can also look like chevrons, arrows, or decorative marks, especially at small sizes on a business card or van sign. Related bracket types such as square brackets, parentheses and curly braces create similar naming confusion, which is why a plain role mailbox is safer for cards, vans and website footers.

That mental model makes angle-bracket addresses feel accidental. A customer who cannot see or name the marks will contact the business to ask for the "real" email, or will guess a simpler version and never reach the intended inbox.

Form validation, HTML stripping and CRM rejection

Even where a specially quoted or encoded form that includes angle brackets might be discussed in the email standards, many email validation libraries and form tools reject or flag < and > because they are uncommon in everyday public addresses and appear often in HTML, XML and pasted markup. Form validators often implement stricter rules than the RFC minimum.

Website contact forms, CRM imports, booking systems, accounting packages and quote generators may treat angle brackets as invalid characters, HTML injection risks or typing errors. An address that includes them may be rejected with "Invalid email address", stripped of everything between < and >, escaped into entities such as < and >, flagged for manual review, or accepted and later rejected by a downstream system.

The business may not see the alteration until a reply to a stored address bounces or goes missing. A customer who enters an angle-bracket address into a website form may receive no confirmation, an error asking them to re-enter the address, or a stored mailbox that no longer matches the printed card.

Contact lists and automated systems that validate email addresses often reject or quarantine addresses containing angle brackets because they are rare in everyday business mailboxes and are sometimes associated with pasted HTML fragments. Even when a system accepts the address initially, later integrations may strip or rewrite it.

Print and signage

When printed on a business card, invoice, quote PDF, van sign or website footer, angle brackets in the email address create visual confusion because they look like optional decoration, display-name punctuation or leftover markup rather than characters the customer must type. At small print sizes they are easy to miss or to confuse with similar marks.

The same address that is flagged or rejected in a web form becomes even more problematic when printed on physical materials. A customer looking at an angle-bracket address on a business card, invoice header or van sign may:

Treat the angle brackets as optional display-name punctuation and omit them when typing.

Replace them with square brackets, parentheses or a hyphen.

Type the words "less than" or "greater than" literally into the local part.

Assume the marks wrap a display name and contact the business to confirm the real mailbox.

Skip the characters because they cannot find < and > quickly on a mobile keyboard.

The risk is not that every customer will make one of these errors. It is that angle brackets introduce multiple plausible interpretations where a simpler address like sales@<short-name>.au or bookings@<short-name>.au would be unambiguous.

Safer alternatives for public-facing business addresses

For a public-facing small business, the simplest and most reliable approach is to choose a role or person address that avoids angle brackets entirely. Addresses like quotes@<short-name>.au, bookings@<short-name>.au, sales@<short-name>.au, or info@<short-name>.au work across forms, CRMs, email clients, printed materials and phone dictation without introducing naming confusion, HTML stripping or display-name friction.

If the business currently uses a longer address and is considering a shorter matched .au address as an alternative, the key advantage is that shorter addresses are easier to say, print, type and remember, without requiring special characters that customers struggle to name, find on a keyboard or trust in print. A shorter .au address can forward to the existing inbox (subject to setup and approval), so the business does not need to abandon the existing address or change the website immediately. An account manager confirms fit, availability, .au eligibility requirements, setup steps and provider compatibility manually before anything changes.

How to test before you publish

Before printing a business email address on cards, invoices, quotes, van signs or website footers, test the exact address through the full workflow:

Send a test email from a personal account (Gmail, Outlook, etc.) to the address and confirm that the email arrives in the intended inbox within a few minutes.

Enter the address into the business website contact form (if one exists) and confirm that the form accepts the address, sends a confirmation, and that the confirmation arrives at the intended inbox.

Import the address into a CRM or contact list (such as HubSpot, Salesforce, Mailchimp, or a spreadsheet) and confirm that the address is stored correctly without being rejected, stripped or altered.

Create a test invoice or quote PDF containing the address and ask a colleague or friend (who was not involved in choosing the address) to type the address into their email client from the printed or on-screen PDF. Confirm that they type it correctly without assistance.

Dictate the address over the phone to a colleague or friend and ask them to write it down and type it into their email client. Confirm that they can do so without requiring spelling assistance, clarification or corrections. Pay particular attention to whether they treat angle brackets as display-name punctuation and omit them.

If any step reveals that the address is rejected, altered, mistyped or misunderstood, adjust the address before printing or publishing it. Testing the exact workflow before committing to printed materials or public listings prevents costly reprints, customer confusion and missed communications.