cPanel mailboxes
Add Spamless filtering before your cPanel mail server. Keep local mailboxes when routing supports it; follow ownership, TLS, DNS and test-mail checks.
See setup and fitFor Plesk subscriptions that keep local mail service
Add a spam-filtering gateway to your Plesk mail domain
A mail-routing change in Plesk affects more than a DNS record: the domain still needs a working local mail service, the correct mailbox host and compatible recipient rules. Spamless filters inbound mail before relaying to that host. The guided route separates those prerequisites from ownership checks and from the test code you receive in the mailbox.
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
- Your business mailboxes are managed through Plesk and should remain on their current host when the relay checks pass.
- You want the inbound security workflow separate from managing mailbox passwords and mail clients.
- The domain owner or an approved operator can coordinate DNS, provider settings and a controlled test.
Before you change mail routing
- Keep the Plesk mail service enabled for the domain. Do not select “Not configured” as a gateway setup step; that mode can remove existing mailboxes.
- Use the actual origin hostname with a trusted TLS certificate and reachable STARTTLS on port 25 or 587, rather than the domain’s new public MX.
- Confirm where authoritative DNS is managed and retain a baseline of the domain’s mail-service and DNS settings.
A setup path with clear checkpoints
Record the current Plesk mail configuration
Check the domain subscription and active mailbox service, identify the original receiving host and save its DNS records. Keep a separate rollback copy.
Choose the Plesk recipe and verify ownership
Add the domain in guided setup with the original host, choose Plesk and publish the claim-specific ownership TXT at the authoritative DNS provider.
Validate the receiving route before MX cutover
Run the verified origin TLS check and confirm recipient and firewall rules with the provider. Apply the account’s MX instructions without disabling local mailbox service.
Check the test mailbox and keep the receipt code
Verify the resulting DNS records, request a test email and enter the secret code it contains. Check both inbox and spam folder; an observed gateway decision alone is not final delivery proof.
Limits, control and rollback
Plesk configuration remains manual. The recipe does not install a native connector, access the hosting panel or certify every Plesk/provider configuration.
Preserve the domain’s outgoing authentication records and mailbox service. Review any local filtering alongside the gateway so you know which system holds a message.
Rollback means restoring saved MX and provider routing settings, then checking delivery. DNS changes take time to propagate; stopping the gateway account is not a DNS rollback.
Questions for this setup
Should I switch the Plesk mail service to “Not configured”?
No. The existing mailbox service must remain enabled for this route. The “Not configured” mode can remove existing mailboxes; confirm the appropriate active configuration with the hosting provider.
What if the origin’s TLS certificate does not match?
Resolve the hostname or certificate issue with the provider before cutover. Guided preflight requires a verified TLS route; it should not be treated as a reason to bypass certificate verification.
Does Spamless change the Plesk subscription automatically?
No. You or your hosting operator apply the panel and DNS changes. The account supplies a provider recipe, checks and test-receipt confirmation, not an automatic panel integration.
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.