Mailbox vs Alias vs Group: The Real Difference

Why Your Email Setup Matters More Than You Think

You didn’t just choose an email address to send messages. You chose who sees your data, how your team collaborates, and whether your digital identity stays under your control.

Your mailbox isn’t just a inbox—it’s the foundation of your privacy, your deliverability, and your workflow. Using the wrong type of email address—confusing a mailbox for an alias, or a group address for a real inbox—can leak your activity, break mail routing, or make team coordination a mess.

Understanding the difference between a mailbox, alias, and group address isn't just technical jargon. It’s how you keep your email private, your messages reliable, and your workspace truly under your control—especially when you’re self-hosting or using a sovereign alternative like Unifiedesk.

Key takeaways

A mailbox is a full email account with storage, authentication, and per-user encryption—use it for personal or team ownership.
An alias is a secondary address pointing to an existing mailbox, useful for privacy and managing sender reputation without cluttering inboxes.
A group address routes mail to multiple recipients (like team@) and is ideal for shared workflows, but must be managed to prevent inbox pollution and data leakage.

What Is a Mailbox? The Foundation of an Email Identity

A mailbox is your unique, full-featured email account on your domain — a personal inbox with storage, calendar, Drive access, and end-to-end encryption, tied to your identity. It's not just an address; it’s your digital workspace, with its own password, 2FA, and full control over files, events, and data.

It’s Your Real Identity, Not Just an Address

Think of a mailbox as the core of your online presence. Unlike a disposable alias, it’s a persistent identity with permissions, settings, and long-term access to files, meetings, and contacts. Every action — sending a message, uploading a file, scheduling a call — is tied to this account and protected under your personal key.

According to the IETF’s RFC 5321, a mailbox is defined as a "unique destination for electronic mail" that supports full mail handling, including delivery, storage, and access — not just routing. That’s exactly what a mailbox does. It’s not a shared pipe or a forwarding hop. It’s your seat at the table.

How a Unifiedesk Mailbox Works — In Real Life

With Unifiedesk, each mailbox is a self-contained identity. You can have [email protected] with her own password, 2FA, and full access to calendar, Drive, Docs, and the AI assistant — all encrypted at rest with AES-256-GCM and secured in transit with TLS.

Let’s say you run a small business. You create a mailbox for each team member. Alice gets her own inbox, calendar, and 25 GB of Drive space. She can collaborate on documents, schedule meetings with screen-sharing, and use the AI assistant to draft replies — all under her control. Her data never leaves her key, even if someone gains access to the server.

Unlike aliases (which are just forwarders) or groups (which are delivery lists), a mailbox has storage, permissions, and sovereignty. You can’t use an alias to schedule meetings or upload files to a shared Drive. But you can with a mailbox — because it’s not just an address. It’s a user.

For full control, your domain can be self-hosted. You decide where data lives, whether to sync to local devices, and who can access what. No third parties, no shared pools. Your inbox, your rules. Set it up on your own server if you want complete ownership — or use the hosted service, where encryption is end-to-end by default.

What Is an Alias? A Secondary Name for Your Inbox

An alias is an alternative email address that delivers to your primary mailbox—no new inbox, no separate storage. It’s a shortcut: you send or receive at [email protected], but the message lands in your real inbox. Replies appear to come from the alias, protecting your real address and streamlining outreach. You can set up dozens of aliases quickly for different purposes.

Aliases Are Not Separate Inboxes

Think of an alias like a nickname for your existing mailbox. It doesn’t create a new inbox or require extra storage. All emails sent to [email protected] or [email protected] arrive in your main inbox. When you reply, the "from" field shows the alias, so the other side sees a professional email—without you exposing your personal address.

Use Cases That Matter: Privacy, Outreach, and Control

Want to avoid spam when signing up for services? Use an alias like [email protected] instead of your real email. If it starts flooding with spam, just disable that alias—no need to change your primary. For outreach, you can manage campaigns under [email protected], [email protected], or even [email protected] from one place.

This is how services like Gmail and Proton Mail handle aliases internally, and it’s an industry-standard practice backed by RFC 5321 (SMTP) and RFC 5322 (email format), which define how addresses are routed and interpreted across the web.

You can set up aliases quickly with Unifiedesk using your own domain. No complex configs—just sign up, add your domain, and create aliases in minutes. And because each message is encrypted at rest with AES-256-GCM, your privacy stays intact, even when using multiple aliases. Set up your custom domain and aliases today.

What Is a Group Address? A Recipient List, Not a Sender

A group address is a distribution list that forwards incoming emails to multiple recipients, like [email protected] sending messages to your entire support team. It doesn’t have a dedicated mailbox—there’s no inbox to check—and it can’t send replies. Anyone can send to it, and the message gets delivered to all members in the list. It’s managed by an admin and exists only to route mail, not store it.

How Group Addresses Work in Practice

Let’s say you set up [email protected]. Anyone—customers, partners, even automated systems—can send to that address, and the message arrives in every person’s inbox on the sales team. That’s a group. It’s not a mailbox; it’s a forwarding rule defined in your email system. You don’t log in to group addresses, and they don’t keep copies of messages unless you explicitly enable archiving.

Some services default to storing group messages in a shared mailbox. But that’s optional. In a truly group-based setup, the mail flows through and vanishes from system logs once delivered. It’s designed for efficiency, not persistence. This reduces risk—no single inbox holds all your team’s correspondence.

Group Addresses vs. Mailboxes and Aliases

Think of a mailbox as your personal email account—your inbox, your sent items, your stored messages. An alias is like a nickname: it points to your main account, so messages to [email protected] go into your inbox. But a group is different: it sends the same message to multiple people at once.

For example, if you use Unifiedesk, you can create a group address like [email protected]. You’d assign it to a list of journalists or PR contacts. Unlike a mailbox, no one logs into it. Unlike an alias, it doesn’t just redirect to one person—it broadcasts. You manage it through your admin interface, not your mail client.

As the Internet Engineering Task Force (IETF) notes in RFC 5322, mail routing principles emphasize that mailing lists (groups) should not assume ownership of mail by users. They’re meant to deliver, not store. That’s why group addresses are typically transient in design.

For teams that want shared workspaces without shared inboxes, Unifiedesk offers group addresses with full control over membership and routing. Whether you're managing customer support or internal announcements, you get precise control over who receives what, without cluttering individual mailboxes. Learn how Unifiedesk handles group setups with privacy and clarity.

Mailbox vs Alias vs Group: The Core Differences

You use a mailbox when you need full control, personal settings, and long-term message storage. An alias lets you receive mail under a different address—ideal for privacy or outreach—without a full inbox. A group address sends messages to multiple users at once, perfect for team comms without managing individual mailboxes. Each serves a different purpose, and choosing the right one depends on your workflow.

Use a Mailbox When You Need a Full Inbox

Use a full mailbox when you need personal settings: custom signatures, filters, storage limits, and access across devices.
Mailboxes store messages indefinitely and support features like calendar invites, shared folders, and full message history.
They’re best for primary or long-term accounts, where you want accountability and continuity—like your main work or personal email.
For full privacy and control, consider using a self-hosted deployment: your data, your rules.

Use an Alias When You Want Simplicity or Privacy

Use an alias to receive mail under a different address—great for signing up for newsletters or reducing inbox clutter.
Aliases don’t need their own password; they route to your primary mailbox, so you don’t manage multiple logins.
They’re ideal for protecting your primary address: if one gets spammed, you can discard the alias without changing your main email.
You can create unlimited aliases with a custom domain—set up with just a few DNS records, like SPF, DKIM, and DMARC. Learn how from DMARC standards.
See how aliases work in practice: set up an alias with Unifiedesk.

Use a Group Address When Messages Need to Reach Multiple People

Use a group when you want one address to reach several people—like support@ or marketing@ team meetings.
Everyone in the group receives the message, and replies go to all members (or just the sender, depending on settings).
Groups don’t require individual mailboxes. No one needs to log in—just send to the group name.
Perfect for team communication, event invites, or shared project updates—you can manage membership and access centrally.
For team collaboration, combine groups with shared Drive spaces and Docs: secure file sharing and real-time editing.

Real-World Use Cases: When to Choose Each Type

You use a mailbox when you need a full, independent email account with its own inbox, storage, and authentication—like a personal email address. An alias acts as a forwarding name, letting you send and receive from a different address without a separate inbox. A group address routes messages to multiple people automatically, ideal for shared responsibilities like support or billing. Let’s break this down with real examples.

Freelancer: Mailbox and Alias for Professional Outreach

Let’s say you’re a freelance designer with your own domain. You create a dedicated mailbox at [email protected]—your personal, secure inbox where you manage your day-to-day emails. But when pitching clients, you want to appear more professional. So you set up an alias: [email protected]. This alias forwards incoming mail to your mailbox, and it shows clients a clean, branded address. You stay in control, no extra inbox overhead. This works because, unlike a group or shared mailbox, an alias doesn’t require shared access—just a single inbox behind the scenes. RFC 5322 describes how email addresses are structured and routed, which makes aliases feasible across any compliant system.

Company: Group and Shared Mailboxes for Team Workflows

Now imagine a small business. They need a billing address—[email protected]. But they don’t want to give one person full access to a mailbox. Instead, they assign this as a group address. Anyone on the finance team receives invoices, and replies go to all members. This avoids bottlenecks. Importantly, the group address isn’t tied to a single mailbox or an alias—it’s a distribution list managed behind the scenes. Meanwhile, they also use a shared mailbox, like [email protected], for customer support. Multiple agents can reply, archive, and organize messages together—ideal for collaborative workflows where ownership isn’t individual. You manage this all in Unifiedesk’s email system, with granular control over who gets what.

Aliases are lightweight; they don’t require full mailbox storage or team permissions. Group addresses distribute mail to multiple people without cluttering inboxes. Shared mailboxes combine the inbox with team collaboration—great for customer service, project coordination, or project-based teams.

How Unifiedesk Handles Mailboxes, Aliases, and Groups

On Unifiedesk, a mailbox is a full email account with its own inbox, storage, and encryption keys. An alias is a secondary email address that delivers to the same mailbox, letting you use different addresses without creating extra storage or encryption overhead. A group address routes mail to multiple recipients and is managed centrally by admins, with delivery rules and full SPF/DKIM/DMARC enforcement applied to every message. All work seamlessly across mail, calendar, and Drive.

Mailboxes and Aliases: One Account, Many Addresses

You get a primary mailbox, like [email protected], which stores all your mail, calendar events, and Drive files — secured with AES-256-GCM encryption at rest, and TLS in transit. You can add as many aliases as needed — [email protected], [email protected] — each routing to that same mailbox.

Aliasing is simple: no extra storage, no separate encryption keys. You control each alias individually, turning them on or off as needed, with no impact on performance or privacy. This means you can use a different alias for a newsletter, a client, or a temporary project, all without juggling separate inboxes. For reference, RFC 5322 defines how email addresses are structured and validated, ensuring interoperability across systems.

Groups: Centralized, Secure, and Configurable

Groups are set up in the admin panel and send mail to multiple members — like [email protected] or [email protected]. You can define which users are in the group, set delivery rules (e.g., “only admins can send”), and manage membership in minutes.

All inbound mail to group addresses is checked against SPF, DKIM, and DMARC records in real time. If a message fails any of these checks, it’s rejected before it ever reaches an inbox — meaning no phishing or spoofing gets through. This is a standard practice enforced by email providers like Google and Microsoft, and is critical for domain security.

Whether you’re managing a single mailbox, juggling aliases, or running a team with shared responsibilities, Unifiedesk gives you full control. You can explore the full suite — from email and calendar to video meetings and Drive — at our mail features page. For teams needing more control, self-hosting is available with complete data residency and audit capabilities. More details on deploying it yourself are at our self-hosted guide.

Setting Up Aliases and Groups in Unifiedesk: Step-by-Step

You can use aliases to forward mail to a user without creating a new mailbox, groups to send to multiple people at once with a single address, and mailboxes for full email accounts with storage and access. In Unifiedesk, both aliases and groups are easy to set up in the admin panel and work seamlessly with your domain’s DNS records — no technical delays.

Set up aliases for flexible email routing

Log in to your Unifiedesk admin panel. You’ll need admin access to manage mailboxes, aliases, and groups.
Navigate to the 'Mailboxes' section and select the user account that will receive the alias’s mail. Aliases don’t need their own mailbox — they forward into an existing one.
Go to the 'Aliases' tab and click 'Add Alias'. Enter the new email address you want to use, like [email protected]. This doesn’t require a new inbox — it just routes mail.
Save the alias. Unifiedesk automatically handles DNS configuration in the background. As long as your domain’s MX, SPF, DKIM, and DMARC records are correct, email will route properly.

Create group addresses for team communication

Go to the 'Groups' section in your admin panel. Groups act like mailing lists — one email address, many recipients.
Click 'Create Group' and enter a group email, such as [email protected]. This becomes the address people send to.
Add members to the group by selecting them from your user list. Anyone in the group will receive incoming mail sent to the group address.
Save the group. Unifiedesk instantly generates the necessary DNS records for the new group, and it’s ready to use — no wait for propagation.

Aliasing and grouping let you manage email flow without overloading users or cluttering inboxes. Unlike some services that charge extra for aliases or limit group size, Unifiedesk handles all of this at no extra cost on your plan.

For full control and data residency, consider self-hosting with Unifiedesk. Your email stays under your control, and you retain full ownership of DNS, encryption keys, and data.

Understanding how mail systems work is key. The RFC 5322 standard governs email structure, including how aliases and group addresses are routed. Unifiedesk follows these standards strictly to ensure compatibility and deliverability.

Once set up, use aliases for roles (e.g. sales@, hr@) and groups for teams (e.g. team@, dev@). You can also manage calendar invites, drive files, and documents through the same centralized admin panel.

For all your team’s communication needs — email, calendar, meet, drives, and AI — Unifiedesk provides a single, unified interface built for privacy and control. Check out the full suite: email, calendar, meet, drive, documents, contacts, and AI assistant.

Key Limitations to Know: What Alias and Group Addresses Can't Do

You can’t receive mail independently from an alias — it always forwards to your primary mailbox. Groups don’t store messages unless a shared mailbox is set up, and you can’t send from a group address without assigning a sender identity, like a shared mailbox. These aren’t features — they’re hard limits built into how email routing works. Let’s break them down so you aren’t surprised.

Aliases: Not Independent Mailboxes

Aliases are just additional email addresses pointing to your main inbox — they don’t have their own mailbox storage.
Any message sent to an alias automatically lands in your primary mailbox, just like a forwarded address.
Because of this, you can’t archive, filter, or manage an alias separately — it shares all settings with the primary account.
Think of them like phone extensions: they ring the same phone, not a new one. For more on how this works, see the official RFC 5322 on email address syntax and routing.

Groups: Require Explicit Setup to Work

By default, a group address only routes incoming mail — it doesn’t store messages unless you configure a shared mailbox.
Without a shared mailbox, any mail to the group vanishes unless you’ve set up rules or forwarding — a common oversight.
You cannot send as a group address unless you assign a sender identity (like a shared mailbox or delegated sender).
Even then, some providers may block sending from groups by default, especially if not tied to a real user account.
This isn’t a flaw — it’s a security design choice. You can’t “send from” an address you don’t control.

These limits don’t mean aliases and groups are useless — they’re powerful when used correctly. But you need to know the system before you build on it. Want to explore how Unifiedesk handles these with clear controls? Check out email features, contacts, and self-hosting for full flexibility.

Best Practices for Choosing the Right Email Type

You need a mailbox when you're an individual requiring full access to calendar, Drive, meetings, and documents—this is your primary identity. Use aliases for temporary or role-based addresses (like [email protected]) without setting up a full account. Reserve group addresses for broadcast messages only—never for personal or sensitive replies. Groups are not a substitute for shared mailboxes when tracking replies is essential. Let’s sort this out with clear rules.

Mailboxes: For Full, Personal Workspaces

Use a mailbox if you’re a person who needs calendar sync, Drive access, real-time collaboration on Docs, and video meetings with screen sharing.
Each mailbox is a full account: it has its own storage, password, and permissions. It’s ideal for employees or founders who manage their own work.
With Unifiedesk, that means you get full email control from any device, plus integrated calendar, video meetings, and team Drive.

Aliases: Lightweight Identities, No Overhead

Use an alias for role-based addresses (e.g., [email protected] or [email protected]) without creating a full account.
Aliases are free, easily created, and forward mail to an existing mailbox—perfect for temporary projects, event signups, or public-facing roles.
They’re not meant for shared access or long-term collaboration. Think of them as temporary identities, not permanent workspaces.
According to RFC 5321, aliases are functionally valid and standard for routing, but don’t carry identity or access rights—only routing rules.

Groups: Broadcast Only, No Reply Tracking

Use a group to broadcast a message to a list (e.g., all team members) or announce a company-wide update.
Do not use groups for one-on-one conversations, sensitive data, or when replies need to be tracked.
Never replace a shared mailbox with a group. Group replies are untracked and can’t be archived properly.
If you need replies tracked or shared access to email, use a shared mailbox instead—this keeps accountability intact and follows industry best practices.

Take Control of Your Email Identity Today

Understanding the difference between a mailbox, alias, and group address isn't just technical trivia — it's how you take real control over your digital identity, privacy, and team workflows.

With Unifiedesk, you define how your email works: full control over encryption, your domain, and who sees what — no trade-offs, no hidden data collection.

Start with a free @unifiedesk.com mailbox, or add your own domain in minutes. No compromises on privacy, performance, or security. Every message, file, and calendar invite stays private and under your control.

Keep reading

Ready to put this into practice? Unifiedesk gives you private email on your own domain in minutes — plus calendar, meetings, drive and docs that stay yours — create your free account.

Frequently asked questions

Can I send emails from an alias in Unifiedesk?

Yes — an alias is linked to a mailbox and can send from the primary address. Replies appear as the alias, but are sent from the mailbox’s identity.

Can a group address have a mailbox?

A group address does not store mail by default. To receive and track messages, pair it with a shared mailbox.

Do aliases affect email deliverability?

No — aliases are treated as valid addresses by email systems. Deliverability depends on SPF, DKIM, and DMARC, not alias usage.

Can I use the same alias across multiple domains?

Yes — Unifiedesk allows unlimited domains. An alias on one domain can point to any mailbox, even across domains.

Are aliases encrypted in Unifiedesk?

Yes — all mail, including messages sent to or from aliases, is encrypted at rest (AES-256-GCM) and in transit (TLS) on hosted deployments.

Can I make a group address private?

Yes — group members are not visible to external senders. Internal visibility is controlled by admin settings.

Is a group address anonymous to senders?

Yes — senders only see the group email address. The actual recipients are not exposed unless the group is set to disclose members.

How many aliases can I create per mailbox?

There is no limit. You can create as many aliases as needed for your domain.

Can I use aliases in calendars or Docs?

Yes — aliases appear in event invites and document collaboration, showing the owner’s name and role.

Can I convert an alias to a mailbox?

Yes — just create a new mailbox and assign the alias to it. The mailbox can inherit the alias without data loss.

Do groups support reply-to behavior?

No — replies go to the sender’s address. To enable group-wide replies, assign a shared mailbox as the sender.

What happens if I delete a mailbox?

All aliases linked to it stop working. The group address remains, but messages sent to it will fail unless a new mailbox is assigned.