How Email Routing Rules Combine (Priority, Overrides & Delivery Flow)

Created by Curtis Hammock, Modified on Sun, 15 Nov at 7:22 PM by Curtis Hammock

When an incoming email arrives for your custom domain, Purelymail processes the address through an ordered sequence of checks to determine where the message should be delivered.


The Complete Delivery Flow (How Incoming Mail Is Processed)

When an email arrives at your domain, Purelymail processes it in this exact order:

  1. Symbolic Subaddressing Normalization (If Enabled): If Symbolic Subaddressing is enabled on your domain, any tag starting with a symbol (+, _, -) is stripped so the address resolves to the base username (for example, user+receipts@yourdomain.com resolves to user@yourdomain.com). Dots are also ignored.
  2. Account Routing Rules: Purelymail checks the rules configured under Routing in your Account Admin portal. If a rule matches, the message redirects to that rule's destination address.
  3. Account Sieve Scripts: If your administrator configured an account-wide script under Routing > per-account Sieve scripts, it executes next across matching incoming messages before mail reaches individual mailboxes.
  4. User Sieve Filters: Once an email resolves to a specific user mailbox, that user's personal filters (configured in Webmail under Settings > Filters or via ManageSieve) run to sort mail into folders, flag messages, or set vacation auto-replies.
  5. Final Mailbox Delivery (or External Forwarding): The message is placed into the destination mailbox folder or forwarded out to an external email provider.

If any rule or script redirects an email to another address on your account, the delivery flow repeats for the new address from step 1, with built-in circular loop protection.


Rule Priority (Which Rule Wins?)

If an incoming email could match more than one routing rule on your domain, Purelymail resolves the destination using this priority order:

  1. Exact Address Matches ("The exact address")
    • Takes first priority over all other routing rules.
    • If an incoming address matches an exact rule, it routes immediately to that rule's destination.
    • Example: An exact rule for contact@yourdomain.com will always handle mail sent to contact@yourdomain.com, even if you have prefix rules or a domain catch-all.
  2. Prefix Matches ("Any address starting with")
    • Evaluated if no exact match exists.
    • If multiple prefix rules match the same incoming address, the longest matching prefix wins.
    • Example: If you have a prefix rule for news- and another for newsletter-, an email sent to newsletter-special@yourdomain.com matches the longer newsletter- rule.
  3. Universal Matches ("Any address")
    • Matches every address sent to your domain.
    • Redirects all incoming mail for the domain to the specified destination, overriding all user mailboxes on the domain.
  4. Catch-All Rules ("Any address except valid user addresses")
    • Evaluated last among routing rules.
    • Redirects incoming mail only if the recipient address does not belong to an existing user mailbox.
    • If a matching user mailbox exists, the message delivers straight to that user instead.

How Routing Rules Interact with User Mailboxes

Routing rules act as permanent redirects for incoming messages:

  • Routing Rules Override User Mailboxes: If an exact rule, prefix rule, or universal rule matches an address that also exists as a User mailbox, the routing rule takes precedence. Incoming mail is redirected away from the mailbox, leaving the mailbox empty.
  • Catch-All Protects User Mailboxes: The only routing rule that yields to user mailboxes is Any address except valid user addresses (catchall). If an email is sent to user@yourdomain.com and that mailbox exists, it delivers to the mailbox. If the address does not exist, the catch-all rule routes it.
  • Delivering to a Mailbox and Forwarding at the Same Time: If you want an incoming email to land in a user mailbox while also forwarding a copy elsewhere:
    • Add both the user mailbox address and the external address to the rule's Send To field, separated by a comma (for example: user@yourdomain.com, backup@external.com).
    • Alternatively, leave routing rules alone and configure a user filter in Webmail under Settings > Filters using a copy redirect.

Recursive Routing (Chaining Rules)

Routing rules apply recursively until the recipient stops changing:

  • If you configure a rule that redirects info@yourdomain.com to team@yourdomain.com, and a second rule that redirects team@yourdomain.com to alex@yourdomain.com, an incoming email sent to info@yourdomain.com will deliver to alex@yourdomain.com.
  • You can chain rules between internal addresses on your domain or forward them outward to external providers.

Circular Loop Protection

If routing rules accidentally point back to each other in a circle (for example, address A redirects to address B, and address B redirects back to address A):

  • Purelymail tracks the path of each redirected message.
  • When a circular loop is detected, Purelymail halts further redirects and delivers the message to the last valid address before the loop repeated.
  • This prevents emails from getting stuck in an endless loop or bouncing unnecessarily.

Related Guides


Still Need Help?

If you've followed these steps and are still running into trouble, check our Purelymail Support guide.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article