Setting up email in Plesk is a straightforward process, but the exact steps depend on whether you want to create a new mailbox, connect an existing domain, configure mail clients, or manage DNS records for reliable email delivery. In a hosting environment, Plesk gives you central control over mailboxes, aliases, forwarding, authentication, and spam protection, making it a practical choice for managing business email from one panel.
This guide explains how to set up email in Plesk step by step, how to verify that your domain is ready for mail, and which DNS records you should check to avoid delivery problems. It is written for hosting customers and site owners who manage domains and email directly from Plesk.
Before You Start: What You Need
Before creating email accounts in Plesk, make sure the domain is correctly added to the server and that mail service is enabled for it. In most hosting setups, Plesk can handle both the mailbox creation and the DNS configuration required for mail delivery.
Check that your domain is active in Plesk
Your domain should already be added to the subscription or server in Plesk. If the domain is not present, you will need to add it first through your hosting account or in the control panel, depending on your access level.
Confirm that mail service is enabled
Plesk can host email only if the mail feature is enabled for the domain. This is usually available under the domain’s mail settings. If mail is disabled, email addresses cannot be created and mail routing may not work as expected.
Decide where DNS is managed
Email setup depends heavily on DNS. If your domain uses Plesk DNS, you can manage records directly in the panel. If DNS is hosted elsewhere, such as with a registrar or external DNS provider, you must update records there instead. In either case, the correct MX, SPF, DKIM, and DMARC records are important for deliverability.
Create an Email Account in Plesk
Once your domain is ready, you can create a mailbox in Plesk. This mailbox will be used to send and receive email under your domain, such as [email protected] or [email protected].
Steps to create a new mailbox
- Log in to Plesk.
- Open Websites & Domains and select the domain you want to use.
- Click Mail or Email Addresses, depending on your Plesk version.
- Select Create Email Address.
- Enter the mailbox name, for example info or sales.
- Set a strong password.
- Choose the mailbox size or disk quota if available.
- Save the changes.
After saving, the account is active and ready to be used in webmail or in an email client such as Outlook, Apple Mail, Thunderbird, or a mobile mail app.
Recommended mailbox naming conventions
To keep your hosting email organized, use clear and role-based mailbox names. Common examples include:
- [email protected] for general inquiries
- [email protected] for pre-sales communication
- [email protected] for customer support
- [email protected] for invoices and payments
- [email protected] for system or account notifications
If you do not need separate inboxes for every address, you can also use aliases or forwarding, which are covered later in this article.
Enable and Configure Mail Service for the Domain
Plesk domain mail settings control whether the domain can send and receive messages on the server. If this is not configured properly, mail clients may connect, but messages could fail to arrive or be rejected by recipient servers.
Turn on mail hosting
In the domain’s mail settings, make sure mail service is enabled. Depending on your hosting plan, Plesk may offer local mail hosting on the server or allow you to route mail through a remote mail server.
Choose the right mail routing mode
Plesk commonly supports the following mail routing options:
- Local mail server - Plesk handles incoming and outgoing mail for the domain.
- External mail service - DNS and routing are set so mail is processed by another provider.
- Automatic - Plesk detects the preferred configuration based on DNS.
For most hosting customers who want Plesk to manage email directly, the local mail server option is the expected choice. If you use an external service like Microsoft 365 or Google Workspace, avoid duplicate mail routing by ensuring Plesk is not also trying to host mail for the same domain.
Set Up DNS Records for Email Delivery
DNS configuration is one of the most important parts of email setup in Plesk. Even if the mailbox exists, messages may fail to deliver if MX and authentication records are missing or incorrect.
MX record
The MX record tells the internet where to deliver email for your domain. If Plesk hosts the mail, the MX record typically points to the mail server hostname configured for your domain or server.
Make sure there is only one correct MX setup unless you intentionally use multiple mail servers for redundancy. If you migrate email from another provider, update the MX record carefully to avoid mail being delivered to the old system.
SPF record
SPF helps receiving servers verify that your server is allowed to send mail for your domain. This reduces the risk of spoofing and improves deliverability.
A typical SPF record includes your mail server or hosting provider. In Plesk, SPF can often be managed through DNS settings or mail settings depending on the server configuration.
DKIM record
DKIM adds a digital signature to outgoing messages, helping receiving systems confirm that the email was not altered in transit. This is strongly recommended for any domain used for business email.
Plesk can often generate DKIM keys automatically and publish the required DNS record. If your DNS is external, copy the DKIM record from Plesk and add it to the correct DNS zone.
DMARC record
DMARC builds on SPF and DKIM by defining how mail servers should handle messages that fail authentication. It also gives you visibility into who is sending mail using your domain.
A basic DMARC policy can start with monitoring, then later move to stricter enforcement once you confirm that legitimate mail is passing authentication checks.
Common DNS mistakes to avoid
- Leaving an old MX record active after migration
- Publishing conflicting SPF records instead of one combined record
- Forgetting to enable DKIM signing for outgoing mail
- Creating a DMARC policy that is too strict before testing
- Editing DNS in Plesk when the domain actually uses external DNS
Configure Webmail Access
Plesk typically includes webmail access so users can log in through a browser without needing an email application. This is useful for quick access, travel, or checking mail from multiple devices.
How to access webmail
Webmail access is usually available through a URL provided by the hosting environment. The exact path can vary by server configuration, but it often follows a format similar to webmail.yourdomain.com or a provider-specific webmail login page.
To log in, use the full email address and the password you created in Plesk.
Benefits of webmail
- No need to install a mail client
- Accessible from any device with a browser
- Useful for checking account settings quickly
- Good fallback if your local email app is not configured yet
Connect an Email Client to Plesk Mail
After creating the mailbox, you may want to connect it to a desktop or mobile email client. To do that, you need the correct IMAP/POP3 and SMTP settings from your hosting platform or Plesk configuration.
Use IMAP or POP3
IMAP is the best choice for most users because it keeps messages synchronized across devices. If you read a message on your phone, it will remain marked as read on your laptop as well.
POP3 downloads messages to one device and is less suitable for modern multi-device workflows, although it may still be used in some cases.
Typical mail client settings
The exact server names vary by hosting setup, but the standard fields you need are:
- Incoming mail server - IMAP or POP3 host name
- Outgoing mail server - SMTP host name
- Username - the full email address
- Password - the mailbox password
- Ports and encryption - SSL/TLS or STARTTLS, depending on the server
Recommended connection method
Use encrypted connections whenever possible. In hosted environments, IMAP over SSL/TLS and SMTP with authentication and encryption are the standard best practices. This protects your credentials and message content during transmission.
Example client setup checklist
- Open the email app on your device.
- Add a new account.
- Select manual setup if automatic detection fails.
- Enter your full email address and password.
- Choose IMAP for incoming mail.
- Enter the SMTP server details for outgoing mail.
- Enable authentication for the outgoing server.
- Save and test sending and receiving messages.
Set Up Email Forwarding and Aliases
Not every business needs a separate mailbox for every address. Plesk lets you manage aliases and forwarding rules so messages can be routed efficiently.
Email aliases
An alias is an additional address that delivers mail to the same mailbox. For example, [email protected] can point to [email protected].
Aliases are useful when you want professional-looking addresses without managing multiple inboxes.
Forwarding
Email forwarding sends incoming messages from one address to another mailbox. This can be inside the same domain or to an external address.
For example, [email protected] can forward to a team member’s inbox while still presenting a shared contact address on the website.
When to use a shared mailbox instead
If multiple people need to reply from the same address and track communication, a shared inbox or group mailbox may be better than simple forwarding. The best choice depends on your workflow and hosting plan.
Manage Mailbox Quotas and Storage
Email storage can fill up quickly, especially if attachments are common. Plesk allows you to define mailbox quotas so storage stays under control.
Why quotas matter
A mailbox with no quota can use more server storage than expected. A mailbox with a very small quota may stop receiving mail too early. Setting the right limit helps balance usability and resource management.
How to choose a quota
For general business use, choose a size based on how many messages and attachments the account receives. High-volume departments such as support or billing may need larger limits than a general contact inbox.
Signs a mailbox is reaching its limit
- Users cannot receive new messages
- Mail client sync fails or stalls
- System notifications about storage usage appear
- Attachments and older mail need archiving
Improve Email Security in Plesk
Email security should be part of every hosting configuration. Plesk includes several tools and settings that can help reduce spam, abuse, and unauthorized access.
Use strong passwords
Every mailbox should have a strong, unique password. Avoid using shared credentials across multiple inboxes or services.
Enable spam filtering
Plesk can work with spam filtering tools to reduce unwanted mail. Depending on the hosting environment, this may include server-side filtering or integration with additional anti-spam features.
Protect against authentication issues
Always use encrypted login methods for webmail and mail clients. If possible, disable insecure or outdated protocols that are no longer necessary for your users.
Monitor account activity
Check mailbox usage and logs when available. Unexpected outbound mail volume can indicate a compromised account, while repeated login failures may point to a password issue or attempted abuse.
Troubleshooting Common Email Issues in Plesk
If email is not working after setup, the issue is often related to DNS, mail routing, or client settings. The following checks solve many common problems in a Plesk hosting environment.
Problem: I cannot receive email
Check that the domain’s MX record points to the correct mail server and that mail hosting is enabled in Plesk. Also confirm that the mailbox exists and has enough storage quota.
Problem: I can send email, but recipients do not receive it
Verify SMTP settings, authentication, and SPF/DKIM configuration. Messages may be rejected or marked as spam if the server identity is not properly authenticated.
Problem: Mail client keeps asking for a password
This is often caused by an incorrect username, password, or server name. Make sure you are using the full email address as the username and that the client is configured for secure authentication.
Problem: Emails go to spam
Check the SPF, DKIM, and DMARC records. Also review the content of the message, sender reputation, and whether your domain has been newly activated or migrated. New domains may need some time to build trust with recipient servers.
Problem: Mailbox was working before migration, but now it does not
Review the migration process carefully. A common issue is that DNS still points to the old provider, or the local Plesk mail server and an external provider are both trying to handle the same domain.
Best Practices for Hosting Email in Plesk
To keep your email service reliable, use a consistent setup and review it after any domain or DNS change.
- Keep one authoritative DNS source for each domain.
- Use IMAP for multi-device access.
- Enable DKIM and publish SPF and DMARC records.
- Use clear mailbox names for business roles.
- Monitor mailbox quotas and clean up old mail regularly.
- Recheck DNS after moving the domain to a different server.
- Use encrypted connections for all mail clients and webmail access.
FAQ
Can I create multiple email accounts in Plesk?
Yes. You can create as many mailboxes as your hosting plan and server resources allow. Each mailbox can have its own password, quota, and mail client settings.
Do I need to set DNS records manually?
Not always. If your DNS is managed in Plesk, some records can be created automatically. If DNS is hosted elsewhere, you must add MX, SPF, DKIM, and DMARC records there manually.
What is the difference between email aliases and forwarding?
An alias delivers mail to the same mailbox, while forwarding sends mail from one address to another destination. Aliases are better for simple alternate addresses; forwarding is useful when messages need to reach another inbox.
Which is better for email in Plesk: IMAP or POP3?
IMAP is usually better because it synchronizes mail across devices. POP3 is less flexible and is generally used only in special cases.
Why is my outgoing email not working?
The most common causes are incorrect SMTP settings, missing authentication, blocked ports, or missing SPF/DKIM records. Check your mail client configuration and the domain’s authentication records.
Can I use external email services with a domain hosted in Plesk?
Yes. You can point your DNS records to an external provider such as Microsoft 365 or Google Workspace. In that case, make sure Plesk is not also configured to host mail for the same domain.
How do I access Plesk webmail?
Webmail access depends on your hosting setup. In many cases, your hosting provider provides a webmail URL, or you can reach it through the domain’s mail services page in Plesk.
Conclusion
Setting up email in Plesk involves three main parts: creating the mailbox, enabling mail service for the domain, and configuring DNS correctly. When these elements are aligned, your hosting email becomes reliable for everyday business communication.
For the best results, use secure passwords, verify MX, SPF, DKIM, and DMARC records, and test both incoming and outgoing mail after setup. If you manage multiple domains in a hosting environment, keeping DNS and mail routing organized will help prevent delivery issues and simplify future maintenance.