New guide: how to warm up a dedicated IP without hurting your reputation. Read now →
Log in
MigoSMTP
Getting startedUpdated 26 Oct 2026

Plus Addressing and Email Aliases: How user+tag@domain Works, Its Uses and Its Limits

How plus addressing (sub-addressing) and aliases work in Gmail, Outlook and custom domains, uses for testing and filtering, signup form handling, validation pitfalls, deliverability and privacy considerations.

VR
Written by Valentina Reyes
E-commerce Email Specialist
Reviewed by Hannah Mitchell
  • Published18 Sep 2025
  • Read time6 min
  • Length1,202 words
Share this guide

An email address such as [email protected] looks different from [email protected], yet on many providers both reach the same inbox. This feature, called plus addressing or sub-addressing, is popular with people who want to filter mail or trace which company sold their address, and with developers who need many test accounts without creating many mailboxes. It also causes trouble: web forms reject the plus sign, duplicate-account checks treat the variants as different people, bulk senders find that "unique" subscribers share a mailbox, and abusers use it to create endless accounts. This guide explains how plus addressing and related alias methods work, where they are supported, how to handle them correctly in sign-up forms and email systems, and when other solutions fit better.

Plus addressuser+tag@domain delivers to user@domain at providers that support it
SupportGmail, Outlook.com, Fastmail, many Google Workspace and Microsoft 365 setups and custom servers
Form ruleAccept the plus sign; it is a valid character in the local part
CautionDo not assume that plus variants are different people, nor that they are the same

How it works

The local part of an address, the text before the @, is interpreted by the receiving mail system. Many systems treat the first plus sign as a separator: everything before it is the mailbox and everything after is a tag that is ignored for delivery. The delivery agent can use the tag for filtering. The convention is described in RFC 5233 (the Sieve subaddress extension), but it is a convention, not a requirement of SMTP. Your sending system sees a different address string; the receiving system maps it to the mailbox.

Provider or setupPlus addressingNotes
Gmail and Google WorkspaceYesGmail also ignores dots in the local part for consumer accounts
Outlook.com and Microsoft 365Yes (Outlook.com by default; Microsoft 365 needs the setting enabled in some tenants)Check tenant configuration
Yahoo and othersGenerally no; they use disposable address features insteadVerify before relying on it
Postfix and other self-hosted MTAsConfigurable with recipient_delimiterOften set to the plus sign
Fastmail and similarYes, plus subdomain addressingAlso supports wildcard aliases
Corporate systemsVariesSome reject unknown tags

Aliases and other methods

  • Aliases. An extra address that forwards to a mailbox. It must be created in advance, and it can be removed without affecting the main address.
  • Catch-all. Any address at the domain reaches one mailbox. Convenient but a magnet for spam and mistyped addresses. See catch-all domains and validation.
  • Dot variants. Gmail ignores dots, so [email protected] and [email protected] are the same mailbox. Other providers do not.
  • Subdomain addressing. [email protected] with wildcard DNS, supported by some providers.
  • Masked or relay addresses. Services that generate a unique forwarding address per website, hiding the real one.
  • Distribution groups and shared mailboxes. For teams: a single address delivered to several people.

Good uses

  1. Filtering. A rule that sends everything tagged +billing to a folder.
  2. Source tracking. Use a different tag per website to see who shares or leaks the address.
  3. Testing. A developer can create [email protected], [email protected] and so on, all received in one inbox. See staging and testing.
  4. Role separation for a small team before aliases are set up.

Handling plus addresses in sign-up forms

The plus sign is valid in the local part of an address, so forms must accept it. Rejecting it frustrates customers and loses sign-ups. Use a validation approach that checks structure rather than banning characters, and confirm ownership by sending a verification link. See sign-up forms and double opt-in and email validation.

QuestionRecommendation
Reject plus signs?No. Accept them, subject to ordinary validation
Treat plus variants as the same user?Do not merge automatically; the same person may use tags, but different people at a shared domain cannot be told apart this way
Prevent free-trial abuse?Normalise for the abuse check only, with care, and combine with other signals such as payment method and device
Store which address?Store exactly what the user entered and use it for sending. Normalised copies can be kept separately for comparison
Case sensitivity?Domains are case-insensitive; local parts are technically case-sensitive but nearly all providers ignore case
URL encodingIn query strings the plus sign is read as a space; encode it as %2B

That last point causes many bugs: an unsubscribe or confirmation link containing [email protected] in a URL query can arrive as asha [email protected] and fail. Encode addresses in URLs, or better, use opaque tokens instead of addresses in links. See one-click unsubscribe.

Implications for senders

  • List size. Several plus variants of one mailbox inflate the subscriber count and distort engagement rates. Deduplicating by normalised form may be justified for reporting, but keep sending to the original address the subscriber gave.
  • Suppression. If a mailbox complains or bounces, suppression applies to the exact address. A plus variant may still deliver. Consider the effect when you manage suppressions. See suppression lists.
  • Spam traps. Plus tags do not make an address a trap, but unverified sign-ups with random tags may signal bot activity. Use verification.
  • Consent. Consent attaches to the address entered. Keep a record. See consent records.
  • Reputation. Mailbox providers see the delivered mailbox, so complaints from tags reach the same user history.

Privacy and security

Tags make tracking easy, but they are not secret: anyone who sees the address knows the base mailbox by deleting the tag. They are therefore a filtering tool, not an anonymity tool. For privacy, use masked relay addresses. Security teams should not rely on a tag in a password-reset flow, and systems should avoid treating the tag as an identity. Also consider that attackers use plus variants to bypass per-address rate limits, so apply limits to the normalised address and to IP and device signals as well.

Examples from real workflows

A software team creates test accounts named dev+signup1, dev+signup2 and dev+reset on the company domain and routes them to one shared inbox; automated tests read the inbox through an API and delete messages afterwards. A shop owner gives each marketplace a tagged address and filters tagged mail into folders, quickly spotting which service shares the address with advertisers. A school sets up aliases such as admissions and accounts that forward to staff and can be reassigned when people change roles. In each case the choice fits the need: tags for informal filtering, aliases for stable role addresses and masked relays for privacy. Choose by asking who must be able to manage the address over time.

Practical rules

  1. Accept plus signs in every form and API.
  2. Encode addresses in URLs, or avoid addresses there.
  3. Send to the exact address supplied; deduplicate only for analysis.
  4. Verify ownership with a confirmation email before adding to marketing lists.
  5. Document the behaviour for your support team, since customers will ask why plus addresses fail elsewhere.
  6. For test environments, use a catch-all or plus pattern on a domain you control, and block those test addresses from production sending.

Plus addressing is a small feature with useful applications and a few traps. Handle it as valid input, avoid assumptions about identity, and your forms and sending systems will treat all customers fairly.

Validate addresses before you send Catch typos and risky addresses early.

Open the email validator

References and further reading

Frequently asked questions

Is the plus sign valid in an email address?

Yes. It is allowed in the local part, and forms should accept it.

Does plus addressing work everywhere?

No. Gmail and Outlook.com support it, but some providers and corporate systems do not.

Should I treat plus addresses as the same subscriber?

Not automatically for sending. You may normalise for analytics or abuse checks, but send to the address supplied.

Why does my confirmation link fail for plus addresses?

The plus sign in a URL query is read as a space. Encode it as %2B or use tokens.

Is plus addressing private?

No. The base mailbox is obvious by removing the tag, so use masked relay addresses for privacy.

Topics#plus addressing#aliases#validation#signup#testing
Was this guide helpful?Your answer helps us improve our documentation.

Start sending in minutes.

Create an account, add your domain and send your first email.

Get started Talk to sales