Plesk mail domains
Protect a Plesk mail domain with a Spamless gateway. Review enabled mail service, authoritative DNS, origin TLS, rollback and mailbox test confirmation.
See setup and fitFor cPanel administrators and domain owners
Spam filtering for cPanel, with your existing mailbox server
When unwanted messages create daily work for a small business, changing every mailbox and mail client adds another project. Spamless can sit in front of the existing cPanel mailbox server: inbound mail is filtered and eligible messages are relayed to the configured origin. Keeping the mailboxes depends on local delivery staying enabled and the host accepting that route.
Eligible accounts: one domain, up to 1,000 messages per day. Complete setup in 7 days; 14 active days start after you confirm the secret code from the test email. The pilot ends within 21 days of the request. No automatic charge.
When this fits
- You run business email on cPanel and want an inbound filtering gateway before the existing mailboxes.
- You can manage the authoritative DNS zone and confirm settings with the hosting provider.
- You want quarantine review, allow/block lists and operational reports alongside the existing mail clients.
Before you change mail routing
- An explicit public hostname for the original mailbox server, with verified STARTTLS on port 25 or 587. It must not resolve back to the Spamless MX.
- Local Mail Exchanger stays selected for local cPanel mailboxes. Ask the host to permit the gateway route and the intended recipients.
- Access to one mailbox on the domain and a copy of the current MX, relevant TXT and mail-routing settings before any change.
A setup path with clear checkpoints
Save the cPanel and DNS baseline
Record the current MX priorities, original mailbox hostname and local-delivery setting. Check whether DNS is actually hosted in cPanel or elsewhere.
Register the domain and prove ownership
Use guided setup, select cPanel and supply the origin server. Publish the unique ownership TXT shown for your claim. A shared MX record by itself proves no ownership.
Check TLS before switching MX
Confirm Local Mail Exchanger and the host’s acceptance rules, then run the origin TLS check. Apply the exact MX values from your account only after saving the rollback snapshot.
Confirm a test from the destination mailbox
Verify TXT and MX, explicitly request one test email, then enter its secret code from the mailbox or spam folder. Gateway processing is a separate observation from your receipt confirmation.
Limits, control and rollback
This is a manual setup recipe, not a cPanel plugin or an automatic connector. A live provider-specific delivery test has not been verified by this documentation.
Keep outgoing SPF/DKIM settings intact unless your documented mail route requires an agreed change. An inbound gateway does not automatically replace the domain’s sending setup.
For rollback, restore the saved DNS and the original local-delivery rules, keep the mailbox server running and check mail flow with the host. Removing a domain in Spamless does not restore DNS.
Questions for this setup
Do I have to move my cPanel mailboxes?
The gateway can relay to the existing cPanel server when local delivery, TLS and recipient acceptance work. Your provider must support that route; keeping mailboxes is conditional on those checks.
My DNS is outside cPanel. Where do I change MX?
Publish records at the authoritative DNS provider. Changing an unused cPanel zone does not change public mail routing. Save the public records and verify the resulting TXT and MX from guided setup.
Why should Local Mail Exchanger stay enabled?
Your mailboxes still live on this server. Selecting remote delivery solely because the public MX changes can send mail back toward the gateway or prevent local delivery. Confirm the correct local setting with the host before cutover.
Read the exact instructions
Review the provider recipe, plan limits and data processing terms before changing DNS. Keep the original mailbox service available until you have checked the route.
Other mail environments
Hosting providers
Manage client email security with verified-owner consent, viewer/operator access and separate subscriptions. Explore cPanel/Plesk setup and operational reporting.
See setup and fitCheck the domain, then choose the next step
The public DNS checker needs no account. If this setup fits, continue with an eligible card-free pilot and the guided domain checks.