# Mailbox

> Source: Courseiva IT Certification Glossary — https://courseiva.com/glossary/mailbox

## Quick definition

A mailbox is like a digital inbox where emails you receive and send are stored. It lives on a mail server and can be accessed from different devices. Each user typically has their own mailbox, but shared mailboxes exist for teams. The server manages the storage, security, and delivery of messages to and from the mailbox.

## Simple meaning

Think of a mailbox like a physical mailbox at your home. When someone sends you a letter, the postal carrier delivers it to your physical mailbox and it stays there until you open it. A digital mailbox works the same way for email. Your email messages are stored on a mail server, which is like a giant post office computer. When someone sends you an email, the sender's email server talks to your email server, and the message is placed into your mailbox on that server. When you open your email app on your phone, laptop, or tablet, the app connects to the server and downloads the messages from your mailbox so you can read them. The mailbox also stores messages you have sent, which are kept in a separate folder called Sent Items. 


 A mailbox is not just a single folder. It usually contains many folders like Inbox, Sent Items, Drafts, Junk Email, and Deleted Items. You can create your own folders to organize messages. The mailbox has limits on how much space it can use, called mailbox quotas. If you exceed the quota, you might not be able to send or receive new messages. 


 The mailbox is a key part of how email systems work. Whether you use a free service like Gmail, a corporate system like Microsoft 365, or your own email server, the concept is the same. The mail server holds your mailbox and manages the protocols that allow other servers and your email client to access it. Understanding how a mailbox works helps you troubleshoot common email problems, such as not receiving messages, messages going to the wrong folder, or hitting storage limits.

## Technical definition

A mailbox is a data structure or storage container on a mail server that holds email messages for a specific user or group. In modern email systems, a mailbox is implemented as a database or a set of files managed by the Mail Transfer Agent (MTA) and Mail Delivery Agent (MDA). The most common protocols used to access mailboxes are IMAP (Internet Message Access Protocol), POP3 (Post Office Protocol version 3), and the more modern Microsoft Exchange Web Services (EWS) or Graph API. 


 IMAP is the most widely used protocol for accessing mailboxes because it synchronizes messages across multiple devices. When a user reads, deletes, or moves a message, the change is reflected on the server and then synced to all clients. IMAP works over port 143 (unencrypted) or port 993 (IMAPS, encrypted). POP3, on the other hand, downloads messages from the mailbox to the local device and typically deletes them from the server, making it less suitable for multi-device access. POP3 uses port 110 (unencrypted) or port 995 (POP3S, encrypted). 


 In a corporate environment like Microsoft Exchange or Microsoft 365, mailboxes are stored in the Exchange database (EDB files). Each mailbox consists of folders that map to MAPI (Messaging Application Programming Interface) folder IDs. Exchange uses the MAPI protocol internally and exposes connectivity through MAPI over HTTP, EWS, and the newer RESTful Graph API. The mailbox database handles indexing, replication, and high availability. Mailboxes have configurable quotas for three levels: Issue Warning, Prohibit Send, and Prohibit Send and Receive. 


 For on-premises Linux systems, mailboxes are often stored in the Maildir or mbox format. Maildir stores each email as a separate file within a directory structure, while mbox stores all messages in a single file. Both formats are used with MTAs like Postfix or Exim and MDAs like Dovecot. Dovecot, a popular IMAP and POP3 server, manages mailboxes from these file stores, providing access via IMAP or POP3. 


 Mailboxes are also integral to compliance and legal discovery. In enterprise systems, administrative tools allow an IT professional to place a mailbox on litigation hold, which preserves all content including deleted items. Journaling can copy all messages from a mailbox to another location for archiving. Understanding mailbox permissions is crucial for shared mailboxes, where multiple users can access the same mailbox to manage a team inbox (e.g., support@company.com). Shared mailboxes require Send As or Send on Behalf permissions to be configured correctly. 


 From an exam perspective, you need to know the difference between a mailbox and a user account. A user account is an identity in a directory service (like Active Directory), while a mailbox is the storage container for email. In cloud systems like Microsoft 365, a user account can have a mailbox, but you can also have mailboxes without a user account, such as resource mailboxes for rooms or equipment, and shared mailboxes. The distinction is critical for exam questions about licensing, provisioning, and access control.

## Real-life example

Imagine you live in an apartment building and the building has a central mailroom. Each resident has their own locked mailbox compartment in that mailroom. When a package arrives for you, the mailroom attendant puts it into your compartment. You can come to the mailroom and open your compartment with your key to collect your mail. Now, think of the mailroom as the mail server, and your compartment as your mailbox. 


 Your email app (like Outlook or Gmail on your phone) is like a person you hire to go to the mailroom for you. Whenever you open your email app, it goes to the mailroom, checks your mailbox compartment, and brings back any new letters (emails) to show you. If you reply to an email, the app takes your reply back to the mailroom and puts it in the outgoing mailbox so the postal service can send it. 


 If you want to check your mail from multiple places (your phone, laptop, and tablet), you need the mailroom to keep copies of all your mail for you. This is exactly what IMAP does: it keeps your emails on the server so all your devices see the same thing. If instead you want to take all your mail home and not leave any in the mailroom (like the old way with POP3), you can do that, but then your other devices won't see it. 


 The locked compartment is like the security of your mailbox. Only you have the key (your password and authentication). A shared mailbox is like having a compartment that multiple people in your family have keys to. You can all put in and take out mail, and you all see the same contents. This analogy helps understand why servers have quotas (the compartment can only hold so many letters), why backups are important, and why permissions matter.

## Why it matters

Understanding mailboxes is fundamental for any IT professional who manages communication systems or supports end users. Email is still the backbone of business communication, and most problems users face are related to their mailbox: missing emails, cannot send, full mailbox, or access denied. Knowing how mailboxes work allows you to troubleshoot these issues effectively. 


 For IT support staff, the first step in diagnosing email problems is often checking the mailbox status. Is the mailbox over its quota? Is it enabled? Are permissions correct? Is the mailbox database mounted? These checks require an understanding of how mailboxes are stored and accessed. In a Microsoft environment, you would use the Exchange Admin Center or PowerShell cmdlets like Get-Mailbox and Set-Mailbox to check and modify mailbox properties. 


 Mailboxes are also central to security and compliance. IT professionals must configure mailbox policies for retention, litigation hold, and archiving. They need to ensure that mailboxes are protected from unauthorized access using strong authentication, and that mailbox auditing logs who accessed which mailbox and when. A compromised mailbox can lead to data breaches or email-based attacks like phishing or business email compromise. 


 In exam contexts, mailbox concepts appear in questions about email protocols, server roles, user management, and troubleshooting. For example, you might need to decide which protocol (IMAP vs. POP3) to recommend for a user who checks email on multiple devices. Or you might be asked why a user cannot send email even though they can receive, the answer could be due to a prohibit send quota. Understanding mailbox concepts prepares you to answer these questions correctly and to design and manage email systems in real-world IT roles.

## Why it matters in exams

Mailbox is a topic that appears in multiple IT certification exams, particularly those focused on messaging, collaboration, and administration. In exams like Microsoft 365 Fundamentals (MS-900) and Microsoft 365 Messaging Administrator (MS-203), mailbox concepts are core objectives. MS-203 devotes significant coverage to managing mailboxes, including creating and configuring mailboxes, setting permissions, managing mailbox features, and troubleshooting mailbox issues. The exam often includes scenario-based questions where you must decide the correct action to resolve a mailbox problem, such as enabling litigation hold, increasing quota, or granting Send As permissions. 


 In CompTIA Network+ (N10-008) and Security+ (SY0-601), mailbox knowledge is less directly tested but appears in the context of email protocols and security. For Network+, you might see questions about IMAP vs. POP3 ports and which protocol maintains server-side storage. For Security+, you may encounter scenarios involving email security, such as mailbox compromise or configuring secure email gateways. Understanding how a mailbox works helps you grasp the bigger picture of email security controls like DMARC, SPF, and DKIM, which protect mailbox integrity. 


 For the Microsoft 365 Fundamentals exam (MS-900), questions might ask about the difference between a user mailbox, shared mailbox, and resource mailbox, and the licensing requirements for each. Answering these correctly requires knowing that shared mailboxes do not need a license if under 50 GB, while resource mailboxes are used for rooms and equipment. 


 In Linux Administrator exams like LPIC-1 or Red Hat RHCSA, mailbox concepts show up in questions about mail transfer agents (Postfix, Sendmail) and mail delivery agents (Dovecot). You might need to configure a local mailbox for a user, set quotas, or troubleshoot mail delivery using log files. 


 The key to answering mailbox questions on exams is to focus on the purpose and behavior of different mailbox types, the protocols used to access them, and the administrative tools available. Exam questions often include a scenario with a specific symptom, and the answer requires you to identify the underlying mailbox issue. For example, a user who can receive but not send emails likely has a prohibit send quota exceeded. A user who sees old emails on their desktop but not on their phone might be using POP3 instead of IMAP. These distinctions are critical.

## How it appears in exam questions

Exam questions about mailboxes typically fall into several categories. Scenario-based questions are the most common. For example, you might be given a situation where a user reports they cannot send emails but can receive them. The question then asks for the most likely cause. The options might include DNS issues, SMTP server down, mailbox quota exceeded, or incorrect IMAP settings. The correct answer, assuming the SMTP server is functional, is that the mailbox has reached its prohibit send quota. 


 Another pattern involves protocol selection. You could be asked to recommend an email protocol for a sales team that accesses email from a smartphone, laptop, and tablet. The question tests whether you know that IMAP is the correct choice because it keeps messages on the server and syncs across devices. POP3 would be wrong because it downloads and typically deletes messages from the server. 


 Configuration questions appear in exams like MS-203, where you may be asked to perform a step in PowerShell to grant a user full access to a shared mailbox. For example, the cmdlet Add-MailboxPermission -Identity shared@company.com -User user@company.com -AccessRights FullAccess. You might also be asked how to place a mailbox on litigation hold or how to enable archiving. 


 Troubleshooting questions often present a scenario where an admin cannot connect to a mailbox, and you must check if the mailbox database is mounted, if the user is licensed, or if the account is disabled. In Network+, you might be given a scenario where a user's email client times out, and you must identify the correct port (993 for IMAP over SSL) or the need to enable SSL on the server. 


 Finally, mail servers require mail exchange (MX) records in DNS, and these are often relayed requests. I keep it appropriate. Mailbox access relies on proper DNS resolution, authentication, and network connectivity. Exam questions may combine mailbox access with DNS concepts, such as why an email to a user bounces back, which could be due to a missing MX record or a full mailbox. 


 Multiple-choice questions also test definitions directly. For example, "Which of the following is a shared mailbox?" with options like A) user@company.com, B) conference room A, C) the CEO's mailbox, D) a distribution group. The answer is B, as a resource mailbox for a room is a type of shared mailbox. These direct questions test your ability to distinguish mailbox types.

## Example scenario

You work as an IT support specialist for a mid-sized company. A user named Maria calls the help desk because she cannot send emails from her Outlook client on her laptop today. She says she can still receive new emails, but when she tries to send, she gets an error message that says "You do not have permission to send messages." You ask her to check if she can send from her phone, and she says she only uses her laptop. 


 First, you check Maria's mailbox in Exchange Admin Center. You see her mailbox properties and notice that the "Prohibit Send" quota is set to 5 GB, and her mailbox size is currently 5.1 GB. This means her mailbox has exceeded the Prohibit Send quota, which is why she cannot send emails. She can still receive because the receive limit is separate. 


 The solution is to either increase Maria's mailbox quota to a higher value, such as 10 GB, or ask her to clean up old emails from her sent items and inbox to free up space. You choose to increase the quota temporarily while guiding her to archive old messages. After adjusting the quota in Exchange Admin Center, Maria tests sending an email, and it works. 


 This scenario illustrates how understanding mailbox quotas and their three levels (Issue Warning at 4 GB, Prohibit Send at 5 GB, Prohibit Send and Receive at 5.5 GB) is essential for real-world support. In an exam, the scenario might be similar, and you would need to correctly identify the quota level that causes the specific symptom. You would also need to know the appropriate PowerShell command: Set-Mailbox -Identity maria@company.com -ProhibitSendQuota 10GB.

## Common mistakes

- **Mistake:** Thinking that a shared mailbox requires a separate user license in Microsoft 365.
  - Why it is wrong: A shared mailbox in Microsoft 365 does not require a license if it is under 50 GB. A license is only needed for user mailboxes. Many learners assume all mailboxes need a license, which leads to incorrect cost estimates and provisioning mistakes.
  - Fix: Remember that shared mailboxes up to 50 GB are free; only user mailboxes require a license. For larger shared mailboxes, a license is needed.
- **Mistake:** Confusing POP3 and IMAP when recommending a protocol for multi-device access.
  - Why it is wrong: POP3 downloads messages and typically deletes them from the server, so other devices will not see those messages. IMAP keeps messages on the server and syncs across devices. Recommending POP3 for a user who checks email on multiple devices causes frustration.
  - Fix: Always recommend IMAP (or MAPI for Exchange) for users who access email from more than one device.
- **Mistake:** Believing that deleting a user account automatically deletes the mailbox permanently.
  - Why it is wrong: In many systems, deleting a user account soft-deletes the mailbox, but the mailbox data is retained for a recovery period (30 days in Exchange Online). It is not instantly destroyed. This misconception can lead to accidental data loss if the recovery window is missed.
  - Fix: Know the retention period for deleted mailboxes and that you can recover a mailbox even after the user account is deleted, within that window.
- **Mistake:** Assuming that a mailbox's send and receive quotas are the same.
  - Why it is wrong: Many mail systems allow separate quotas for sending and receiving. A user might hit the Prohibit Send quota while still able to receive email. This mismatch is a common exam trap.
  - Fix: Remember that there are three quota levels: Issue Warning, Prohibit Send, and Prohibit Send and Receive. The Prohibit Send quota blocks sending but not receiving.

## Exam trap

{"trap":"A question asks which protocol keeps a copy of emails on the server for access from multiple devices. The options include IMAP, POP3, SMTP, and MAPI.","why_learners_choose_it":"Learners may choose POP3 because they think \"post office\" implies storing mail at the post office (server). But POP3 typically downloads and deletes from the server. SMTP is only for sending. MAPI is proprietary to Exchange but not as commonly known. Learners often mix up POP3 and IMAP.","how_to_avoid_it":"Memorize the key difference: IMAP keeps messages on the server (multi-device sync), POP3 downloads and deletes. SMTP does not store messages. MAPI is for Exchange but also keeps messages on the server. When in doubt, recall the word \"Internet Message Access Protocol\", accessing messages remotely on the server."}

## Commonly confused with

- **Mailbox vs Email Account:** An email account is the identity or login you use to access an email service. A mailbox is the storage container for messages. In Microsoft 365, you can have a mailbox without a licensed user account (shared mailbox), but you cannot have a user account without a mailbox if you want to send and receive email. The misconception is that they are the same, but they are separate objects in the directory. (Example: You can create a shared mailbox for support@company.com without creating a new user account. People send to that mailbox, but there is no human user login associated with it.)
- **Mailbox vs Distribution Group:** A distribution group is a collection of recipients that expands to send messages to all members. A mailbox is a single storage container for messages. A distribution group does not have a mailbox; it just forwards emails to the members' mailboxes. Learners often confuse a shared mailbox with a distribution group, but a shared mailbox stores messages that multiple people can read, while a distribution group just forwards messages. (Example: support@company.com as a shared mailbox stores all support emails so agents can see previous replies. info@company.com as a distribution group just sends a copy to each member's own mailbox without storing a central copy.)
- **Mailbox vs Public Folder:** A public folder is a shared mailbox-like container used for sharing information in an organization, but it is not tied to a specific user or group. Public folders have a hierarchical structure and can store messages, contacts, and calendar items. They are different from a shared mailbox, which is typically a single folder set for a specific team or purpose. Public folders are older and sometimes used for legacy applications. (Example: A public folder called "Company Announcements" can be seen by everyone, whereas a shared mailbox named "HR" is accessible only to the HR team and stores HR-related emails.)

## Step-by-step breakdown

1. **User sends or receives email** — The process starts when a user drafts an email and clicks Send, or when an external server sends email to the user's domain. This triggers the flow of email to or from the mailbox.
2. **Mail delivery to server** — The outgoing email is sent via SMTP to the mail server (MTA). For incoming mail, the sender's server looks up the recipient's MX record in DNS to find the correct mail server.
3. **Mailbox identification** — The mail server identifies the recipient mailbox by looking up the email address in its directory (e.g., Active Directory or local user database). It verifies that the mailbox exists and is active.
4. **Message storage in mailbox** — The server writes the email message to the mailbox database (e.g., Exchange EDB file, Maildir folder). The message is stored with metadata like subject, sender, date, and folder assignment (Inbox by default).
5. **Access via client protocol** — When the user opens their email client, the client connects to the server using IMAP or MAPI (for Exchange). It authenticates with credentials, then requests the message headers and bodies from the mailbox folders.
6. **Synchronization and presentation** — The server delivers the messages to the client. For IMAP, the client caches locally but maintains server sync. Changes (read, delete, move) are sent back to the server to keep the mailbox consistent across devices.
7. **Management and maintenance** — Admins manage mailboxes using tools like Exchange Admin Center or PowerShell. Tasks include setting quotas, granting permissions, enabling archiving, placing holds, and monitoring mailbox size to ensure smooth operation.

## Practical mini-lesson

In practice, managing mailboxes involves a mix of administrative tasks, troubleshooting, and capacity planning. As an IT professional, you will spend a lot of time diagnosing why users cannot send or receive email. The first thing to check is often the mailbox itself. In a Microsoft Exchange environment, open the Exchange Admin Center and navigate to Recipients > Mailboxes. Check the mailbox properties: look at the mailbox usage to see if it is over quota, check the mailbox features to ensure it is enabled, and verify the email address policy. 


 For on-premises Exchange, you also need to know the database status. If a mailbox database is dismounted, no one can access the mailboxes in that database. Use Get-MailboxDatabase -Status | fl to check. For shared mailboxes, you need to configure permissions properly. Grant Full Access allows a user to open and read the mailbox, but to send as that mailbox, you must also assign Send As permission using Add-ADPermission. Many helpdesk tickets arise because Send As was not set. 


 Quotas are another key area. You should set appropriate quotas based on organizational policy. A common approach is to set Issue Warning at 1.5 GB, Prohibit Send at 2 GB, and Prohibit Send and Receive at 2.5 GB. When users approach the limit, they receive warning emails. You can also automate mailbox cleanup with retention policies and archiving. In Microsoft 365, you can enable auto-expanding archives for mailboxes over 100 GB. 


 Troubleshooting mailbox issues often involves checking logs. In Exchange, use the message tracking log to see if a message was delivered to the mailbox. In Linux, check /var/log/maillog. You can also test connectivity using telnet to the appropriate port (143 for IMAP, 993 for IMAPS). If a client cannot connect, check firewall rules, service status, and certificate validity for SSL connections. 


 Finally, always consider security. Mailboxes are prime targets for attackers. Enable Multi-Factor Authentication for user mailboxes, implement mailbox auditing to track access, and configure anti-phishing policies. A compromised mailbox can lead to sending spam or phishing emails to contacts. Regular audits of mailbox permissions help ensure only authorized users have access. In exams, you will be expected to know how to secure mailboxes, set policies, and troubleshoot access issues.

## Memory tip

To remember the three mailbox quota levels, think WPS: Warning (Issue Warning), Prohibit Send, Prohibit Send and Receive. The severity increases from left to right.

## FAQ

**What is the difference between a user mailbox and a shared mailbox?**

A user mailbox is tied to an individual user account and requires a license. A shared mailbox is used by multiple people and does not require a license if under 50 GB in Microsoft 365.

**Can I access a mailbox from multiple devices at the same time?**

Yes, if you use IMAP or MAPI (in Exchange), you can access the same mailbox from multiple devices and see the same messages because they are stored on the server.

**Why can I receive emails but not send them?**

This usually means your mailbox has exceeded the Prohibit Send quota. Check your mailbox size and either delete old messages or ask your admin to increase the quota.

**Do I need a license for every mailbox in Microsoft 365?**

No. User mailboxes require a license, but shared mailboxes up to 50 GB do not. Resource mailboxes for rooms and equipment also do not require a license.

**What happens to my mailbox if my account is deleted?**

The mailbox is soft-deleted and retained for a period (default 30 days in Exchange Online). It can be recovered by an admin within that window.

**What is the best protocol for checking email on a phone and a laptop?**

IMAP is the best choice because it keeps emails on the server and syncs across devices. POP3 will download and remove emails from the server, causing inconsistency.

## Summary

A mailbox is the fundamental storage container for email messages on a mail server. It stores incoming and outgoing messages in folders, and it can be accessed via protocols like IMAP, POP3, or MAPI. Understanding how a mailbox works is essential for IT professionals who manage email systems, troubleshoot user issues, and secure communication. 


 Key concepts include mailbox types (user, shared, resource), quota levels (Issue Warning, Prohibit Send, Prohibit Send and Receive), and protocol differences (IMAP vs. POP3). Exam questions often test your ability to identify the correct protocol for a scenario, troubleshoot a mailbox quota issue, or configure permissions for shared mailboxes. 


 For exams like MS-203, MS-900, and CompTIA Network+, you need to know the administrative tools, common PowerShell commands, and the relationship between mailboxes and directory objects. Remember that mailboxes are not the same as user accounts, a shared mailbox can exist without a user login. By mastering mailbox concepts, you will be better prepared for certification exams and real-world IT responsibilities.

---

Practice questions and the full interactive page: https://courseiva.com/glossary/mailbox