When you set up mailboxes for a new domain in Plesk, the goal is to create a simple, reliable email structure that works well from day one. A clean mailbox setup helps your team send and receive messages professionally, avoids confusion later, and supports better deliverability across European mailbox providers and business networks.
In Plesk, mailbox creation is usually straightforward, but it is worth planning the addresses before you click through the wizard. A thoughtful setup makes it easier to manage access, forwarding, aliases, and shared roles such as sales, support, and billing.
What to prepare before creating mailboxes
Before you add mailboxes for a new domain, decide how your business will use email. This avoids creating unnecessary accounts or missing important role-based addresses.
Check the domain is active in Plesk
Make sure the domain has been added to your Plesk subscription and is ready to use. The domain should already be pointing to the correct hosting platform, and DNS should either be managed in Plesk or at your DNS provider.
Plan the mailbox structure
For a new domain, think about both individual and department addresses. Common examples include:
- [email protected] for personal mailboxes
- [email protected] for general enquiries
- [email protected] for leads and orders
- [email protected] for customer tickets
- [email protected] for invoices and payments
- [email protected] for technical or account-related messages
If your team is small, you may not need a separate mailbox for every role. In that case, you can create one mailbox and use aliases or forwarding addresses for related contacts.
Confirm mailbox naming rules
Plesk usually allows standard mailbox names made of letters, numbers, dots, hyphens, and sometimes underscores depending on server policy. Keep names easy to remember and professional. Avoid complicated abbreviations unless your internal team already uses them.
Check storage and quota requirements
Each mailbox should have enough space for the expected volume of email. A small business can often start with a modest quota, then increase it later. If you expect large attachments, long conversation histories, or shared use of one mailbox, assign a higher limit from the start.
How to create a mailbox in Plesk
The exact screen labels may vary slightly depending on the Plesk version and hosting configuration, but the process is typically similar across managed hosting platforms.
Step 1: Open the domain’s mail settings
Log in to Plesk and select the domain you want to configure. Open the Mail section for that domain. If mail services are not enabled yet, turn mail on first.
Step 2: Add a new email address
Choose the option to create a new mailbox or email account. Enter the mailbox name, such as info or john.smith. Plesk will combine it with your domain to form the full address.
Step 3: Set a secure password
Create a strong password that meets your hosting provider’s security rules. Use a long passphrase or a complex password with a mix of uppercase and lowercase letters, numbers, and symbols. If the mailbox will be accessed by multiple devices or mail clients, store the password securely in a password manager.
Step 4: Set the mailbox quota
Assign a mailbox size limit that matches the purpose of the account. Personal mailboxes can often use a smaller quota than shared addresses such as support@ or billing@. If your hosting plan has limited storage, monitor usage regularly to prevent mail delivery failures.
Step 5: Save the mailbox
Confirm the settings and create the mailbox. Once saved, the address should be available for login and for receiving mail, provided DNS and mail routing are configured correctly.
Recommended mailbox setup for a new business domain
A good mailbox structure should support both professionalism and day-to-day operations. For many companies, the following setup works well:
- Primary personal mailbox for each team member who needs direct email access
- info@ as the main public contact address
- support@ for customer service requests
- sales@ for enquiries and lead generation
- billing@ for finance-related communication
If you do not want to manage multiple inboxes, you can route some of these addresses to a single mailbox using forwarding. That is often useful at the start of a project or for smaller teams.
Use aliases for flexibility
An alias lets one mailbox receive mail sent to another address. For example, messages sent to [email protected] can arrive in [email protected]. This is useful when you want a polished public address without creating a separate login for every role.
Use forwarding when an address should not have its own inbox
Forwarding sends incoming mail from one address to another mailbox. It is a practical choice for addresses that only need to redirect enquiries, such as press@ or jobs@. If several staff members need access, consider a shared mailbox or a group workflow instead of forwarding to one person only.
DNS and mail delivery checks for new domains
Creating a mailbox in Plesk is only part of the setup. For email to work reliably, the domain must be configured correctly in DNS. This is especially important for business email in the EU, where users expect consistent delivery and secure handling of messages.
Verify the MX record
The MX record tells the internet where to deliver incoming email for your domain. If your mail is hosted on the same platform as your website, Plesk may set this automatically. If DNS is managed elsewhere, make sure the MX record points to the correct mail server.
Check SPF, DKIM, and DMARC
These records help prove that your messages are legitimate and reduce the chance of being flagged as spam.
- SPF defines which servers may send email for the domain
- DKIM adds a digital signature to outgoing messages
- DMARC tells receiving servers how to handle unauthenticated mail
In a Plesk environment, these records are often available in the mail settings or DNS management area. Enable them early, before sending real business mail, so that your address reputation starts in a good state.
Allow time for DNS propagation
If you changed DNS records recently, email may not work instantly everywhere. Propagation can take time depending on TTL settings and the DNS provider. During this period, test mail from several networks and devices before assuming there is a problem.
How to access the mailbox after creation
Once the mailbox is created, users can access it through webmail or a mail client such as Outlook, Apple Mail, Thunderbird, or mobile apps.
Webmail access
Plesk installations often include webmail access, allowing users to sign in from a browser. This is useful for quick checks, travel, or when configuring a new device.
Mail client setup
To connect the mailbox to a mail app, you usually need the following details:
- Email address
- Password
- Incoming mail server and port
- Outgoing mail server and port
- Encryption method such as SSL/TLS
Your hosting provider or Plesk panel will show the correct server names and ports for IMAP, POP3, and SMTP. For most business users, IMAP is the better choice because it keeps messages synchronized across devices.
Test sending and receiving
After setup, send a test message to and from the mailbox. Check whether it arrives in the inbox, whether outgoing mail is accepted, and whether replies preserve the correct From address. Testing early helps catch DNS, authentication, or password issues before users depend on the account.
Best practices for mailbox planning
Good mailbox setup is not just about creating accounts. It is about making email easy to manage as your business grows.
Keep addresses simple
Use short, clear names that are easy to dictate over the phone and easy to type on mobile devices. Simple addresses also reduce the chance of misdirected mail.
Separate personal and role-based email
Whenever possible, keep personal mailboxes separate from shared business functions. This helps if staff change roles or leave the company. Shared contact points like support@ should not depend on one employee’s inbox.
Limit access based on need
Only grant mailbox access to people who actually need it. If several users need to monitor the same address, use shared access carefully and review permissions regularly. This improves security and makes account management more predictable.
Use a consistent naming scheme
For growing teams, consistency matters. A pattern such as [email protected] for staff and role-based names for departments makes administration much easier later.
Review quotas regularly
Mailbox usage grows over time. Large attachments, newsletters, and long conversations can fill storage faster than expected. Check usage from Plesk at regular intervals and increase quotas before mail starts bouncing.
Common problems when setting up mailboxes in Plesk
Even with a simple mailbox setup, a few common issues can affect delivery or access.
Mailbox created but no email arrives
This is usually a DNS issue. Check the MX record, domain status, and whether mail is enabled for the domain in Plesk. If the domain uses external DNS, make sure the records there match the hosting platform setup.
Cannot log in to webmail
Confirm that the password is correct and that the mailbox was created under the right domain. Also verify that the mail service is running and that the login URL is correct for your Plesk environment.
Outgoing messages go to spam
Review SPF, DKIM, and DMARC records. Make sure the domain name in the From address matches the authenticated sending domain. Avoid sending too many messages from a brand-new mailbox in a short time, since that can look suspicious to receiving providers.
Mailbox reaches quota too quickly
Increase the quota, clean up old messages, or move heavy attachments to shared storage. If the mailbox is used by a team, consider whether a shared inbox or ticketing tool would be more efficient.
Alias or forwarding does not work
Check that the alias is attached to the correct mailbox and that forwarding rules do not conflict with spam filters or mail routing settings. If mail is forwarded externally, confirm the target address accepts messages from your domain.
When to use a mailbox, alias, or forwarder
Choosing the right email type helps keep your domain tidy and easier to support.
Create a mailbox when someone needs a login
Use a real mailbox if a user must sign in, store mail, reply as that address, or manage messages independently.
Use an alias when one inbox should receive multiple addresses
Aliases are best when you want several public addresses to land in the same mailbox without extra logins.
Use forwarding when mail should be redirected elsewhere
Forwarding is useful for simple redirection, but it is not always ideal for shared business processes. If the mailbox is important to operations, a dedicated inbox is often safer.
FAQ
Can I create multiple mailboxes for the same domain in Plesk?
Yes. You can create as many mailboxes as your hosting plan and domain configuration allow. Each mailbox will have its own username, password, and quota.
Do I need to configure DNS before creating the mailbox?
You can create the mailbox first, but the domain’s DNS must be correct before email will reliably flow. MX, SPF, DKIM, and DMARC should be checked as part of the full setup.
Is IMAP better than POP3 for business mail?
In most cases, yes. IMAP keeps messages synchronized across multiple devices, which is better for teams using laptops, phones, and webmail together.
Can I change a mailbox name later?
Usually you cannot rename a mailbox directly in a way that preserves the same login and history. A common approach is to create a new mailbox, move or forward mail, and update contacts where needed.
What is the best mailbox setup for a new company?
A typical starting point is one personal mailbox per employee plus shared addresses such as info@, sales@, support@, and billing@. This keeps communication organized and easy to scale.
Why do I need SPF, DKIM, and DMARC if the mailbox already exists?
The mailbox only receives and stores mail. SPF, DKIM, and DMARC help other mail servers trust your messages and reduce delivery problems, especially for business domains.
Conclusion
Setting up mailboxes in Plesk for a new domain is most effective when you combine the technical steps with a clear email plan. Create only the addresses you need, choose simple names, secure each mailbox properly, and verify DNS before relying on the domain for business communication. A well-structured mailbox setup makes everyday email easier for your team and supports better deliverability from the start.
If you are preparing a new domain for business use, the safest approach is to set up the mailboxes, confirm MX and authentication records, test access from webmail and a mail client, and then review quota and forwarding rules once real traffic begins.