Create Email Alias: Setup Guide + Naming Conventions That Scale
If you're running a business on Google Workspace or Microsoft 365, you're probably paying for email seats you don't need. A separate user for sales@, support@, and billing@ triples your monthly bill and scatters your data across isolated inboxes. The fix? Create email alias addresses instead.
An alias isn't a mailbox. It's a routing rule. It accepts mail at one address and delivers it to an existing inbox. No storage, no login credentials, no per-seat cost. One person can manage five addresses from a single account. For the full picture on what aliases are and when they make sense, see our Email Aliases pillar guide.
This article shows you how to create email alias addresses across four platforms, covers naming conventions that hold up at scale, and explains why your alias might be landing in spam folders.
Envelope vs. Header: Why Your Alias Replies Break
Before you create email alias addresses on any platform, you need to understand the two layers of every email message. Most alias problems — "Send As" failures, "On Behalf Of" tags, leaked primary addresses — come from confusing these two layers.
The Envelope (RFC 5321) is what servers use during the SMTP handshake. It's the MAIL FROM and RCPT TO commands that decide where a message actually goes. When someone emails your alias (sales@domain.com), the server rewrites the envelope recipient to the real mailbox (bob@domain.com).
The Header (RFC 5322) is what your recipient sees in their email client: To, From, Date, Subject.
Here's where it gets tricky. Receiving works fine — the server handles the rewrite silently. But when you reply, your email client authenticates as bob@, not sales@. If the server detects a mismatch between the authenticated user and the From header, one of three things happens:
- The email gets blocked (
5.7.1 Client does not have permissions) - It gets tagged: "Bob on behalf of Sales"
- Your real identity leaks in the Return-Path header
Every setup below accounts for this outbound alignment problem.
How to Create Email Alias Addresses: Platform-by-Platform Setup
The steps to create email alias addresses differ significantly between providers. Here's exactly what each platform requires, including the hidden configuration steps most guides skip.
Microsoft 365 (Exchange Online)
When you create email alias addresses in M365, they're called "Proxy Addresses." Adding one through the GUI is straightforward. Sending from it without the "On Behalf Of" tag requires PowerShell.
Add the alias:
- Open Exchange Admin Center > Recipients > Mailboxes
- Select the user
- Click Manage email address types
- Add the alias as SMTP type, then save
Enable "Send From Alias" via PowerShell:
By default, M365 rewrites the From header to the primary SMTP address. You need to disable this at the tenant level:
Connect-ExchangeOnline
Set-OrganizationConfig -SendFromAliasEnabled $true
Get-OrganizationConfig | Format-List SendFromAliasEnabled
Propagation takes up to 24 hours.
Google Workspace
Google calls these "Alternate email addresses."
Add the alias:
- Admin Console > Directory > Users
- Select user > Add Alternate Emails
- Enter the alias prefix (e.g., support), save
Configure the client (watch the "Treat as Alias" checkbox):
- User logs into Gmail > Settings > Accounts
- Under "Send mail as," click Add another email address
- Enter the alias name and address
- Uncheck "Treat as an alias" — if checked, Google uses the primary mailbox credentials and may leak your real address in the headers
Postfix / Linux (Self-Hosted)
If you run your own mail server, aliases live in /etc/aliases or a virtual map.
File-based setup:
# /etc/aliases
sales: bob
support: bob, alice
# Then regenerate:
newaliases
Virtual map setup (Postfix):
# /etc/postfix/virtual
sales@example.com bob@example.com
# Apply:
postmap /etc/postfix/virtual && postfix reload
Make sure main.cf includes virtual_alias_maps = hash:/etc/postfix/virtual.
TrekMail
TrekMail makes it trivial to create email alias addresses. It's built for multi-identity management. No PowerShell, no client-side verification codes.
- Log in to the TrekMail Dashboard
- Go to Mailboxes
- Select the target mailbox
- Enter the desired alias address
- Click Save
TrekMail's SMTP servers automatically authorize the authenticated user to send from any associated alias. Pick the address from the "From" dropdown in your client — Outlook, Thunderbird, Apple Mail — and it works. Storage counts toward your domain's total pool (up to 200 GB), not a per-user quota.
Email Alias Naming Conventions That Actually Scale
Every time you create email alias addresses, naming matters. Bad alias naming creates technical debt that compounds with every new hire and vendor signup. Here's the naming standard used by organizations that don't want to rename everything in two years.
Role-Based Aliases
These addresses survive employee turnover. Never print a person's individual email on a business card or contract.
| Function | Standard Alias | Avoid |
|---|---|---|
| Inbound Leads | sales@, growth@ | newbiz@ (confusing) |
| Customer Care | support@, help@ | questions@ (vague) |
| Finance | billing@, accounts@ | invoices@ (too specific) |
| Human Resources | careers@, jobs@ | hr-dept@ (redundant) |
| Security/Abuse | abuse@, postmaster@ | None (RFC 2142 required) |
RFC 2142 mandates that postmaster@ and abuse@ exist on every domain. Alias them to a monitored inbox.
The Vendor-Tracking Strategy
You can also create email alias addresses for vendor tracking. Use disposable aliases to track data leaks. Sign up for a service using vendorname@yourdomain.com (e.g., hubspot-admin@yourdomain.com). If spam hits that address, you know which vendor was compromised. Delete the alias to kill the spam without touching your primary address.
Plus Addressing (RFC 5233)
Most modern mail servers — including TrekMail — support plus addressing out of the box. No admin setup required.
Syntax: user+tag@domain.com (e.g., bob+newsletter@domain.com). Use it for on-the-fly filtering: set inbox rules to route anything with +newsletter to a specific folder.
Troubleshooting: When Your Email Alias Doesn't Work
If you create email alias addresses and they aren't delivering or sending properly, use this diagnostic matrix to pinpoint the issue fast.
| Symptom | Error Code | Root Cause | Fix |
|---|---|---|---|
| Immediate bounce | 550 5.1.1 | Alias doesn't exist or typo in DNS | Verify spelling. Confirm MX records point to the right server. |
| Delayed bounce | 5.4.14 Hop count exceeded | Routing loop | An alias points to a user who auto-forwards back to the alias. Break the chain. |
| Send failure | 5.7.1 | "Send As" restriction | Authenticated user isn't authorized for the alias. Check M365 Set-OrganizationConfig or TrekMail alias association. |
| Lands in spam | SPF Softfail | Alignment mismatch | You're forwarding to an external service without SRS. See our Email Forwarding Setup & Fix guide. |
Forwarding vs. Aliasing: Know the Difference
When you route alias mail to an external destination — say, sales@yourdomain.com to you@gmail.com — you've left aliasing territory and entered email alias forwarding. The distinction matters for deliverability.
Here's the problem: when client@bank.com emails sales@yourdomain.com and your server forwards it to Gmail, Gmail sees the message coming from your server IP but the From address says bank.com. SPF fails. The email hits spam.
The fix requires SRS (Sender Rewriting Scheme) and ARC (Authenticated Received Chain). TrekMail handles SRS automatically on outbound forwards. But the better move is to keep business mail inside your business domain using aliases, not forwards to consumer accounts. If you're weighing the options, our Domain Email Alias vs Mailbox comparison breaks down the tradeoffs.
TrekMail Pricing for Alias Management
| Plan | Price | Aliases | Key Feature |
|---|---|---|---|
| Free | $0 | Limited | No credit card required |
| Starter | $3.50/mo | Unlimited | Custom domain + Send As |
| Pro | $10/mo | Unlimited | Priority support + SRS forwarding |
| Agency | $23.25/mo | Unlimited | Multi-domain + team management |
Paid plans come with a 14-day free trial (card required). The Nano plan needs no card at all.
Wrapping Up
When you create email alias addresses correctly, one inbox handles sales@, support@, billing@, and any vendor-tracking address you dream up — without adding seats or splitting your workflow. The setup takes five minutes on TrekMail, a bit longer on M365 or Google Workspace if you need proper Send As alignment.
Quick checklist:
- Map the route — confirm the destination mailbox exists
- Add the alias — in your admin panel or TrekMail dashboard
- Align outbound sending — configure Send As to prevent identity leaks
- Test both directions — verify inbound delivery and outbound header alignment
Stop paying per-user fees for routing addresses. TrekMail gives you unlimited aliases and full header control on every plan. Start free — no card needed.
Need to set up aliases on a custom domain? That's the logical next step.
