What is an alias vs. a mailbox?

Still have a question, spotted an error, or have a better explanation or a source we should cite?

An alias is an alternate email address that forwards mail to a main mailbox without storing anything itself. A mailbox stores mail directly and has its own password, storage quota, and login credentials.

The distinction matters more than you'd think. When you send from an alias, the mail is technically coming from the underlying mailbox's infrastructure. That means authentication records (SPF, DKIM, DMARC) need to be configured for the domain of the alias, not just the mailbox. If you set up support@yourcompany.com as an alias pointing to john@yourcompany.com, and someone sends from the alias, mailbox providers will check authentication against yourcompany.com. If the records aren't set up correctly, the mail can fail authentication even though John's personal mailbox works fine.

Aliases are useful for organizing incoming mail (all sales@ and info@ messages land in one place), but they don't give you separate sending identities. If you need distinct sending reputations for different departments or brands, you need separate mailboxes or separate domains entirely.

Most modern systems support plus addressing (also called sub-addressing), which acts like a built-in alias system. You can send mail to captain+shipping@deepcurrent.io or captain+invoices@deepcurrent.io, and it all arrives in captain@deepcurrent.io. The part after the + acts as a tag for filtering. Gmail, Fastmail, and most ESPs support this natively. It's a quick way to track where signups came from or set up automatic filters without creating formal aliases.

What to check if you're using aliases for sending: Make sure your SPF and DKIM records cover the alias domain. Verify that replies to the alias go where you expect. And if you're sending marketing email from an alias that forwards to a personal mailbox, know that complaints and bounces will affect the underlying mailbox's reputation. For high-volume sending, use a dedicated mailbox instead.

If you're not sure whether your aliases are authenticated correctly, run a test send through our Email Header Analyzer to see what authentication results show up.

Contributors

Who worked on this answer

Every name links to their profile. Every company links to their site. Real people, real accountability.

Ask an AI · tailored to your setup

Get personalized alias setup advice

I read this on the Email Almanac about "What is an alias vs. a mailbox": "An alias forwards mail to a mailbox without storing it. A mailbox stores mail directly. The distinction matters for authentication (SPF/DKIM/DMARC) and sender reputation. When you send from an alias, authentication is checked against the alias domain, not the underlying mailbox. Plus addressing (captain+shipping@sea.com) acts like built-in aliases for filtering." Help me figure out if I should use aliases or mailboxes for MY situation. I need: 1. Alias or mailbox?: Based on my use case, should I create an alias or a dedicated mailbox? 2. Authentication check: What DNS records do I need to configure for my alias to pass SPF/DKIM/DMARC? 3. Reputation impact: If I send marketing email from an alias, how does that affect my main mailbox's deliverability? 4. Testing: How do I verify that my alias is authenticated correctly before sending to my full list? --- My details (the more you share, the better the advice): - Current setup: [Do you already have aliases configured? What mail server/provider?] - Use case: [What will this alias be used for? Support tickets, newsletters, department-specific sending?] - Sending volume: How many emails per day/month from this alias? - Domain setup: Same domain as your main mailbox, or different domain? - Authentication status: Do you have SPF/DKIM/DMARC configured for your domain? - Experience level: [Beginner / intermediate / advanced with DNS and email configuration]

Edit the yellow boxes, then send to the AI of your choice.