How plus addressing works

An address has two parts: the local part before the @ and the domain after it. With subaddressing, the mail system splits the local part into a user portion and a detail (tag) portion using a separator character. When a message arrives for jane+shopping@gmail.com, the receiving server delivers it to Jane’s mailbox and keeps the full address visible in the message, so her filters can act on the tag.

RFC 5233 formalizes the user and detail parts for Sieve mail filtering. Notably, it does not mandate a separator: + is the common convention, but the encoding is site-specific, and some mail servers are configured to use - or another character instead.

Implementations differ in the details. Microsoft’s documentation for Exchange Online, where plus addressing is on by default, explains that Exchange first tries to match the full address (for example sean+newsletter@contoso.com) to a known mailbox, and only if that fails does it retry without the tag. Administrators can also turn plus addressing off entirely. That means the same tagged address can deliver at one organization and bounce at another.

The + character itself is fully legal. RFC 5322 includes it among the characters permitted in the local part, so any validation rule that rejects it is simply wrong.

Why plus addressing matters for list quality

Over-strict form validation loses real subscribers. Regular expressions that only allow letters, digits, dots, and hyphens reject valid addresses from people who deliberately use tags. Those users rarely retry with their base address.

Duplicates hide behind tags. Someone can sign up multiple times using different tags on the same mailbox (user+promo1@, user+promo2@). A naive dedup process sees separate contacts, but it is one person and one inbox. This matters most for free trials, referral programs, and single-use discounts.

Over-aggressive normalization causes the opposite problem. Stripping tags everywhere can merge genuinely distinct sign-ups, for example a user who keeps separate accounts for work and personal projects. Normalization rules are also provider-specific. Gmail, for instance, ignores dots in consumer addresses, so john.smith@gmail.com and johnsmith@gmail.com reach the same inbox, but Google notes this does not hold for accounts managed by a work or school organization.

Plus addressing as a privacy tactic

Some privacy-conscious users give each company a unique tag so they can see exactly which sender shared or leaked their address, then filter or block that tag. Microsoft describes plus addresses as useful for creating disposable-style, receive-only addresses for this reason. This is not the same as a disposable email address: the mailbox is real and permanent. The practical effect for you is that a subscriber can silently route your mail to a folder or the trash if they lose trust, so respecting their consent matters.

Why verification should treat the full address literally

Because support varies by provider and configuration, verification should check the complete address exactly as submitted, tag included. Stripping the tag first would test a different address. On a server without subaddressing, the tagged address may be rejected with a 550 5.1.1 response (mailbox does not exist) even though the base address is fine, and that is a hard bounce you want to catch before sending.

Practical steps for handling tagged addresses

  1. Accept + in every form field. Use permissive syntax validation and let verification decide deliverability.
  2. Verify and store the address as submitted. Send to that exact address, since the subscriber’s filters may depend on the tag.
  3. Keep a separate normalized key. For dedup and abuse checks, lowercase the address and strip the tag (and, for consumer Gmail only, dots) into a second field. Never overwrite the original.
  4. Rate-limit on the normalized key. Apply one-trial-per-person rules to the normalized value rather than the literal address.
  5. Don’t treat tags as disposable. A plus-tagged address on a real provider is a normal subscriber.

Where RocketVerifier helps

RocketVerifier verifies the full address you submit, tag included, so the result reflects how that specific address behaves on the recipient’s mail server. You can test individual addresses with the free email verifier or check them at signup through the email verification API, keeping your own normalized key alongside the original for deduplication.