Create Email Alias: A Simple Setup Guide + Naming Conventions (2026)

You are likely paying for more email seats than you use. If you are on Google Workspace or Microsoft 365, creating a separate user for sales@, support@, and billing@ triples your monthly cost and fragments your data.

The solution is the email alias.

An alias is a routing instruction, not a mailbox. It accepts mail at the edge and routes it to an existing destination. It has no storage, no login, and—crucially—no per-seat cost.

This guide covers the technical implementation of aliases across major providers, the naming conventions used by scalable organizations, and the specific SMTP mechanics required to ensure your aliases don't trigger spam filters.

For a broader architectural view, refer to Email Alias: What It Is, When to Use It, and How to Set It Up on Your Domain (2026).

---

The Mechanics: Envelope vs. Header

To configure aliases correctly, you must understand the difference between the Envelope and the Header. Most alias issues ("Send As" failures, "On Behalf Of" tags) stem from a misunderstanding of these two layers.

1. The Envelope (RFC 5321): This is the MAIL FROM and RCPT TO commands used by the servers during the SMTP handshake. It determines where the email goes. When you email an alias, the Envelope Recipient is the alias (sales@domain.com). The server rewrites this to the destination mailbox (bob@domain.com) for delivery.
2. The Header (RFC 5322): This is what the user sees in their email client (To, From, Date).

The Disconnect:
When receiving mail, the server handles the rewrite automatically. When replying, however, your email client (Outlook, Apple Mail) defaults to authenticating as the User (bob@), not the Alias (sales@). If the server detects a mismatch between the Authenticated User and the "From" header, it will either:

• Block the email (5.7.1 Client does not have permissions).
• Tag it ("Bob on behalf of Sales").
• Leak the primary identity in the Return-Path header.

Your setup must account for this outbound alignment.

---

Step-by-Step Setup Guide

1. Microsoft 365 (Exchange Online)

Microsoft 365 treats aliases as "Proxy Addresses." While you can add them via the GUI, enabling the ability to send as an alias without the "On Behalf Of" tag requires PowerShell.

Step 1: Add the Alias (GUI)

1. Go to Exchange Admin Center > Recipients > Mailboxes.
2. Select the user.
3. Click Manage email address types.
4. Add the alias (SMTP) and save.

Step 2: Enable "Send From Alias" (PowerShell)
By default, M365 rewrites the From header to the primary SMTP address. You must disable this behavior tenant-wide.

    # Connect to Exchange Online

Connect-ExchangeOnline

 

# Enable Send from Alias for the entire organization

Set-OrganizationConfig -SendFromAliasEnabled $true

 

# Verify the setting

Get-OrganizationConfig | Format-List SendFromAliasEnabled

 

Note: Propagation of this setting can take up to 24 hours.

2. Google Workspace

Google refers to aliases as "Alternate email addresses."

Step 1: Add the Alias

1. Admin Console > Directory > Users.
2. Select the user > Add Alternate Emails.
3. Enter the alias (e.g., support) and save.

Step 2: Configure the Client (The "Treat as Alias" Trap)
The user must manually configure their Gmail interface to send as the alias.

1. User logs into Gmail > Settings > Accounts.
2. Under "Send mail as," click Add another email address.
3. Enter the alias name and address.
4. CRITICAL: Uncheck "Treat as an alias."
• Checked: Google uses the primary mailbox's credentials and may leak the primary address in the headers.
• Unchecked: Google treats it as an independent identity for the Reply-To and From headers.

3. Postfix / Linux (For Self-Hosters)

If you manage your own MTA, aliases are defined in the /etc/aliases file or a SQL map.

File-Based Setup:

    # Edit the alias file

nano /etc/aliases

 

# Format: alias: destination

sales: bob

support: bob, alice

 

# Regenerate the database

newaliases

 

Virtual Map Setup (Postfix):
Ensure your main.cf points to virtual_alias_maps.

code Bash

downloadcontent_copy

expand_less

    # /etc/postfix/virtual

sales@example.com    bob@example.com

 

Run postmap /etc/postfix/virtual and postfix reload to apply.

4. The "Easy Button": TrekMail

TrekMail is architected for multi-identity management. We do not require PowerShell scripts or client-side verification codes for aliases on the same domain.

Setup:

1. Log in to the TrekMail Dashboard.
2. Navigate to Mailboxes.
3. Select the target mailbox.
4. Enter the desired address in the field.
5. Click Save.

Why It’s Different:

• Native Header Support: TrekMail’s SMTP servers automatically authorize the authenticated user to send mail using any alias associated with their account. You simply change the "From" dropdown in your email client (Outlook, Thunderbird, etc.), and it works.
• Pooled Storage: Traffic to sales@ counts toward your domain's total storage pool (e.g., 200GB), not a per-user quota.

---

Naming Conventions: The "Smart Operator" Standard

Inconsistent naming creates "technical debt" in your address book. Adopting a strict convention prevents collisions and ensures scalability.

Role-Based Aliases

These addresses survive employee turnover. Never print a specific person's email on a business card or contract.

Function	Standard Alias	Anti-Pattern (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 Required)

Note: RFC 2142 mandates the existence of postmaster@ and abuse@ for domain administration. Ensure these are aliased to a monitored mailbox.

The "Burner" Strategy

Use aliases to track data leaks. If you sign up for a service, use a unique alias.

• Pattern: vendor-name@yourdomain.com
• Example: hubspot-admin@yourdomain.com
• Benefit: If you receive spam at this address, you know exactly which vendor was compromised. You can then delete the alias to stop the spam without changing your primary email.

Plus Addressing (RFC 5233)

Most modern servers (including TrekMail) support "Plus Addressing" automatically. You do not need to create these in the admin panel.

• Syntax: user+tag@domain.com
• Example: bob+newsletter@domain.com
• Use Case: On-the-fly filtering. You can set up inbox rules to automatically move anything with +newsletter to a specific folder.

---

Troubleshooting: The Matrix

If your alias isn't working, it is usually a DNS propagation issue or a loop. Use this matrix to diagnose.

Symptom	Error Code	Root Cause	Fix
Bounce (Immediate)	550 5.1.1 User Unknown	Alias does not exist or typo in DNS.	Verify spelling. Check if the domain MX records point to the correct server.
Bounce (Delayed)	5.4.14 Hop count exceeded	Routing Loop.	You have an alias pointing to a user, who auto-forwards back to the alias. Break the chain.
Send Failure	5.7.1 Client does not have permissions	"Send As" restriction.	The authenticated user is not authorized to send as the alias. Check Set-OrganizationConfig (M365) or TrekMail alias association.
Spam Folder	SPF Softfail	Alignment Mismatch.	You are forwarding the alias to an external service (Gmail) without SRS.

A Note on Forwarding vs. Aliasing

If you attempt to use an alias to route mail to an external destination (e.g., sales@yourdomain.com -> you@gmail.com), you are leaving the realm of aliasing and entering Forwarding.

This is dangerous territory.

• The Risk: When client@bank.com emails sales@yourdomain.com, and you forward it to Gmail, Gmail sees the email coming from your server IP, but the "From" address says bank.com.
• The Result: SPF fails. Gmail puts it in spam.
• The Fix: You must use a provider that supports SRS (Sender Rewriting Scheme) and ARC (Authenticated Received Chain).

TrekMail handles SRS automatically for outbound forwarding, but we strongly recommend keeping business mail inside your business domain (using aliases) rather than forwarding to consumer Gmail accounts.

---

Conclusion

An email alias is the most efficient way to scale your professional presence without scaling your costs. It allows a single operator to manage sales@, support@, and legal@ from one unified command center.

Summary Checklist:

1. Map the Route: Ensure the destination mailbox exists.
2. Configure the Server: Add the alias in your Admin Panel (or TrekMail Dashboard).
3. Align the Client: Configure your email client to "Send As" the alias to prevent identity leaks.
4. Test: Verify inbound delivery and outbound header alignment.

Stop paying per-user fees for routing addresses.
TrekMail gives you unlimited aliases and professional control for a flat monthly rate.
Try TrekMail for free.