Managing email accounts and automatic message routing is a core part of domain administration in Plesk. If you host websites and mailboxes on the same platform, knowing how to create mailboxes and forwarders helps you keep communication organized, reduce missed messages, and support different working workflows for teams, departments, and individual domains.
In Plesk, you can create full mailboxes for users who need to send and receive email, or set up mail forwarders when messages should be delivered to another address. This is especially useful in hosting environments where a domain may need role-based addresses such as info@, sales@, or support@, without creating separate inboxes for every account.
Understanding mailboxes and forwarders in Plesk
Before making changes in the control panel, it helps to understand the difference between a mailbox and a forwarder.
What is a mailbox?
A mailbox is a full email account hosted on your server. It has its own login credentials, storage space, and can send and receive email independently. A mailbox is the right choice when a user needs a dedicated inbox, IMAP or POP3 access, and the ability to manage mail from webmail, an email client, or mobile device.
What is a forwarder?
A forwarder is an email address that automatically redirects incoming messages to one or more destination addresses. A forwarder does not normally store messages in its own inbox unless you specifically configure it to keep a copy. Forwarders are useful when you want to centralize communication or route messages to an existing mailbox.
When to use each option
- Use a mailbox when a person or team needs a dedicated account.
- Use a forwarder when messages should arrive in another mailbox automatically.
- Use both if you want an address to forward messages and also keep a local copy on the server.
For hosting providers and website owners, choosing the right setup helps avoid confusion, reduces storage use, and makes email administration more efficient.
Prerequisites before you create mailboxes or forwarders
To manage email in Plesk, the domain must be hosted on the server and email service must be enabled for that domain. In most managed hosting environments, this is already available, but it is worth checking if mail features are active.
Check domain and mail service status
- Make sure the domain is present in Plesk.
- Confirm that Mail service is enabled for the subscription or domain.
- Verify that the domain’s DNS records point to the correct mail server if you plan to receive messages externally.
- Ensure you have permission to manage mail settings in the control panel.
If DNS records such as MX, SPF, DKIM, or DMARC are not configured correctly, mailboxes may be created successfully but incoming or outgoing mail can still fail. For best results, review those settings as part of your email setup.
How to create a mailbox in Plesk
Creating a mailbox in Plesk is straightforward and usually takes only a few minutes. The steps may vary slightly depending on your hosting plan, theme, or Plesk version, but the general workflow is the same.
Step 1: Open the domain’s mail settings
Log in to Plesk and select the domain where you want to create the email account. From the domain dashboard, open the Mail section.
Depending on the interface, you may see a button such as Create Email Address, Add Email Account, or Mail Settings.
Step 2: Start a new email account
Click the option to add a new address. Enter the local part of the email address, for example info if you want [email protected]. Plesk will combine it with the selected domain name.
You may also be prompted to define the mailbox size, password, and optional settings such as forwarding or antivirus behavior.
Step 3: Set a secure password
Choose a strong password that meets your hosting policy or internal security standard. For managed hosting environments, strong passwords are important because mailboxes are often targeted by spam bots and credential stuffing attacks.
Use a combination of uppercase and lowercase letters, numbers, and special characters. Avoid reusing passwords from other services.
Step 4: Configure mailbox storage
Specify the mailbox size quota if your plan allows it. This determines how much email data can be stored on the server. A small mailbox quota is useful for shared departmental addresses, while a larger quota may be better for users who work with attachments or receive high message volume.
If the plan includes unlimited or server-managed storage, still consider applying reasonable limits to avoid one account consuming all available disk space.
Step 5: Save the mailbox
After entering the required information, save the changes. The mailbox is then created and can be accessed through webmail or an email client configured with the correct server settings.
How to access and configure the new mailbox
Once the account exists, you may need to share settings with the mailbox owner or connect it to mail applications.
Webmail access
Most Plesk environments include webmail access, allowing users to log in from a browser without additional software. This is convenient for checking mail while traveling or when setting up a new email client.
Email client settings
To use Outlook, Apple Mail, Thunderbird, or a mobile mail app, provide the user with the correct server details. These often include:
- Incoming server: IMAP or POP3 host name
- Outgoing server: SMTP host name
- Username: full email address
- Password: mailbox password
- Ports and encryption: typically SSL/TLS for secure mail
IMAP is usually preferred in hosting environments because it keeps messages synchronized across devices. POP3 is still supported in some setups, but it is less flexible for multi-device use.
How to create an email forwarder in Plesk
Forwarders are useful when you do not want to create another full mailbox. They can simplify operations for contact addresses, small teams, and alias-based email routing.
Step 1: Open the forwarders section
Go to the domain’s mail management area in Plesk and look for Forwarding, Email Forwarders, or a similar option. If you are editing an existing address, open its settings and enable forwarding there.
Step 2: Add the forwarding address
Select the email address that will act as the forwarder. This may be an address such as [email protected] or [email protected].
Then enter one or more destination addresses where incoming messages should be delivered. Plesk usually supports forwarding to multiple recipients, which is helpful if several team members need to receive the same inquiry.
Step 3: Decide whether to keep a local copy
In many cases, you can choose whether the original mailbox should retain a copy of each forwarded message. This is useful when you want both centralized delivery and archive retention on the server.
If you disable local delivery, the address functions as a pure forwarder. If you keep a copy, make sure mailbox storage is sized appropriately to avoid quota issues.
Step 4: Save and test the forwarder
After saving your configuration, test the forwarding behavior by sending a message to the address and confirming that it arrives in the destination inbox. Testing is important because forwarding issues can occur if DNS, spam filtering, or mail routing settings are not aligned.
Common mailbox and forwarding use cases
Different hosting customers use mailboxes and forwarders for different reasons. Below are some common scenarios.
Role-based email addresses
Addresses such as info@, sales@, and support@ are often role-based rather than personal. They can be created as:
- Mailboxes, if a team manages them directly
- Forwarders, if messages should be delivered to existing staff accounts
- Shared routing addresses, if several people need visibility into incoming requests
Temporary project aliases
If a project needs a dedicated contact address for a limited time, a forwarder can route mail to a primary mailbox without adding another full account to maintain.
Employee transitions
When a team member leaves or changes roles, forwarding can be used temporarily to ensure no important messages are lost while mail ownership is reassigned.
Multi-domain or multi-brand setups
Hosting clients with several domains may want all customer communication to land in a single support inbox. Forwarders make this easy without needing separate logins for every branded address.
Best practices for email management in Plesk
Good email administration improves deliverability, security, and day-to-day usability. In a hosting or control panel environment, the following practices are recommended.
Use clear naming conventions
Choose mailbox names that are easy to understand and maintain. Common patterns include:
- personal names: [email protected]
- departmental addresses: [email protected]
- functional aliases: [email protected]
Consistent naming helps admins and users quickly identify the purpose of each address.
Review quotas regularly
Mailbox quotas should match real usage. Oversized mailboxes may waste server resources, while undersized ones can cause delivery failures when the inbox becomes full.
Keep forwarding chains simple
Avoid creating complex nested forwarders across several addresses. Deep forwarding chains can make troubleshooting harder and may increase the chance of delivery delays or message loops.
Monitor spam and filtering settings
Use the mail filtering tools provided by your hosting environment to reduce unwanted traffic. Mailboxes with public-facing addresses tend to receive spam, so filtering and antivirus protection should be enabled where possible.
Use secure authentication
Always encourage users to access mail through encrypted protocols. For hosted email, TLS encryption is a standard baseline for protecting credentials and message content during transfer.
Troubleshooting common issues
Even when a mailbox or forwarder is created correctly, users may still experience delivery or login problems. Here are some common causes and how to approach them.
Emails are not arriving
If messages do not reach the mailbox or forwarded destination, check the following:
- MX records point to the correct mail server
- The mailbox exists and is not full
- Forwarding rules are active and saved
- Spam filters are not blocking the message
- The sender has the correct recipient address
Forwarded messages are missing
When a forwarder does not seem to work, verify whether the original address is configured to keep a local copy or only forward messages. Also check whether destination mailboxes are rejecting forwarded mail due to policy or spam classification.
Login credentials fail
If a user cannot sign in to webmail or an email client, confirm:
- The password was entered correctly
- The full email address is used as the username
- The correct IMAP/SMTP ports are set
- SSL/TLS encryption is enabled where required
Mailbox size errors appear
If the mailbox reaches its quota, delete unnecessary messages, archive old mail, or increase the quota if your hosting plan allows it. In managed hosting, admins may need to adjust server policy or plan limits from the hosting control panel.
Security and deliverability considerations
Email setup is not just about creating accounts. A properly configured mail service also needs domain authentication and security controls.
SPF, DKIM, and DMARC
These DNS records help receiving servers validate that your messages are legitimate. They are important for delivery success and should be configured for domains that send email from Plesk.
- SPF specifies which servers may send mail for the domain.
- DKIM signs outgoing mail to prove it was not altered.
- DMARC defines policy and reporting for authentication results.
Forwarding and sender reputation
Forwarding can sometimes affect message authenticity, especially if the destination server checks SPF strictly. If forwarded mail is rejected or marked as suspicious, review authentication settings and consider using proper sender rewriting or mailbox-based workflows where needed.
Protect administrative access
Use strong passwords for all mail accounts and limit access to users who truly need it. Where possible, enable additional security features offered by the hosting environment, and regularly remove unused accounts or aliases.
Frequently asked questions
Can I create a mailbox and a forwarder with the same address?
Yes, in some configurations you can keep a mailbox and also forward copies to other recipients. This is useful when one address needs both local storage and team distribution. The exact behavior depends on the forwarding options available in your Plesk setup.
Does a forwarder need a password?
No. A pure forwarder does not require a mailbox password because it is not meant to be logged into like a regular inbox. If the address is also a mailbox, then the mailbox itself will have login credentials.
Can I forward to multiple email addresses?
Yes, Plesk typically allows forwarding to more than one destination. This is useful for shared inbox workflows and internal distribution across several team members.
Why is my forwarded email going to spam?
Forwarded mail may be flagged if the destination server views the message as unauthenticated or if the sender’s domain has weak email authentication. Check SPF, DKIM, and DMARC records, and review the spam filter settings of both the source and destination mail servers.
Which is better for support addresses: mailbox or forwarder?
If a support team actively works from the address, a mailbox or shared mailbox workflow is usually better. If the address only routes messages to an existing inbox, a forwarder is simpler and easier to manage.
Can I edit a mailbox later?
Yes. In Plesk, mailbox settings such as password, quota, forwarding, and related mail options can usually be changed after the account is created.
Step-by-step summary
If you need a quick reference, the basic workflow is:
- Open the domain in Plesk.
- Go to the Mail section.
- Create a new mailbox if the user needs full email access.
- Set a password and mailbox quota.
- Or configure a forwarder if messages should be redirected elsewhere.
- Save the changes and test delivery.
- Check DNS and authentication records if mail delivery issues appear.
Conclusion
Creating mailboxes and forwarders in Plesk is a practical part of domain and email management in hosting environments. Mailboxes are best for users who need a complete inbox with login access, while forwarders are ideal for routing messages to one or more existing accounts. With the right setup, you can keep email organized, improve workflow efficiency, and avoid common delivery problems.
For reliable email operation, remember to review mailbox quotas, use secure passwords, and verify DNS authentication settings such as SPF, DKIM, and DMARC. In a managed hosting or control panel environment, these small configuration details make a major difference in deliverability and day-to-day usability.