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 fitChoose a mail route you can verify
Email security solutions for cPanel, Plesk and hosting
Start with your current hosting environment and the people responsible for it. These pages explain when an inbound gateway fits, what remains on your mail server, and how to test the route before relying on it.
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.
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 fitHosting 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 fitKeep the route explicit
Provider recipes cover manual cPanel and Plesk setup. They do not imply an automatic connector or universal compatibility with other mail platforms.
Confirm one real test
Ownership, routing and TLS checks are separate from the secret code confirmed by the person who receives a test message. One confirmed test is not a guarantee of future delivery or detection accuracy.
Review data processing before onboarding
Read the DPA, privacy information and plan conditions with your organisation or customer. A gateway changes the path of inbound mail and needs an agreed rollback plan.