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 hosting support teams and managed-service providers
Manage customer email security with their explicit consent
Hosting support teams investigate spam, delayed messages and DNS settings across many independent customer domains. Spamless provides an account-scoped way to assist: the verified customer owner grants viewer or operator access, you select the approved client context, and each client keeps control of access and their own subscription. Operational reports help investigate mail flow without presenting filtering counts as proven attacks.
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 support businesses with their own mail domains, especially existing cPanel or Plesk mailbox environments.
- You need a clear distinction between read-only investigation and approved operational work.
- Your customers retain independent accounts and direct subscriptions instead of sharing an unrestricted administrator login.
Before you change mail routing
- Each invited customer already has an account and a verified owner who can explicitly approve the requested permission.
- Your team agrees on who controls DNS and the original mail server, and who can read the destination test mailbox.
- Set customer expectations for supported operations, separate billing and the documented provider setup limits.
A setup path with clear checkpoints
Choose viewer or operator access for the job
Start with viewer access for investigation. Use operator access for supported domain, quarantine and list operations only when the customer agrees to that permission.
Share a private invitation for owner approval
Create the invitation and share its private link yourself through an agreed channel. No invitation email is sent automatically. The verified existing owner must approve; creating a link does not confirm whether an account exists.
Select the approved client and prepare their route
Check the displayed actor and client identity before working. Save each client’s own DNS baseline and follow their cPanel or Plesk recipe; one client’s approval grants no access to another.
Confirm a test and review the client’s evidence
The person controlling the test mailbox confirms the secret code after an explicitly requested message. Review the client’s filtering and delivery observations separately. Eligible pilot timing starts from that code confirmation, not from a gateway decision.
Limits, control and rollback
Each customer subscribes and is billed independently. Reference list prices are not invoice amounts or partner revenue; consolidated billing and commission payouts are not provided by this workflow.
The customer can revoke delegation. Disabling a partner profile removes its approved access and pending invitations; enabling it again requires fresh customer approval.
Revoking account access does not restore MX or provider mail settings. Keep a rollback plan per customer, and verify the mail route when restoring it. Provider recipes remain manual, with no native hosting-panel connector.
Questions for this setup
Can clients withdraw access without changing their MX?
Yes. Delegation controls partner access to the account; it does not itself change DNS. The client’s subscription and mail route remain separate concerns. A routing rollback requires the saved DNS and provider settings.
Can an operator manage the client’s billing or account ownership?
Delegated operator access is limited to supported operational actions in the approved client context. Owner-only account, team and billing controls are not delegated by that permission.
Can we put all clients on one Spamless invoice?
This workflow keeps independent client subscriptions and billing. The client overview and CSV help review operations and reference plan prices; they are not consolidated invoices or a partner earnings statement.
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
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 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.