Plesk Email Marketing

Offer email marketing as an upsell without risking mailbox reputation

A native Plesk extension for hosting providers. Spin up an isolated campaign stack per domain, send through dedicated marketing SMTP, and automate SPF/DKIM.

Apply for partner beta

Campaign traffic on shared mail servers costs you money

  • Clients send newsletters through the same mail server as everyday mail. One bad campaign can hurt IP reputation for every mailbox on the host.
  • Manual Mailchimp or SendGrid setup becomes ticket load: DNS records, API keys, and “why did my mail go to spam” every week.
  • Clients buy email tools elsewhere, so you miss the upsell. You still deal with deliverability issues when they try to send from your host.

A plug-and-play Plesk module. Enable per domain. The rest is automatic.

Install once. Enable email marketing on a domain. The extension spins up an isolated Docker stack, creates a dedicated SendGrid subaccount, adds SPF and DKIM to the domain’s DNS, and opens the marketing app from the panel.

Campaign mail never shares the pipe with everyday mailbox delivery. Disable removes the stack—containers, DNS, and SMTP subaccount included.

Engines your clients can choose

  • Listmonk Available
  • Keila Available
  • Mailtrain Available
  • Mautic Available

You choose which engines clients can enable.

Marketing SMTP

  • SendGrid Available
  • Mailgun Soon
  • SparkPost Soon
  • Amazon SES Soon

Per-client subaccounts keep quotas and reputation isolated.

Built for how hosting businesses make money

  • More revenue

    Sell email marketing as a paid add-on or higher hosting plan. Clients get a working campaign tool on day one.

  • Fewer tickets

    No more hand-holding on SPF, DKIM, or “how do I send newsletters.” Setup, DNS auth, and teardown run automatically inside Plesk. Faster onboarding. Less support load.

  • Safer isolation

    Marketing SMTP stays off your everyday mail server. Each client gets its own containers and SMTP subaccount, so one noisy sender does not drag the others down.

From enable to send in three steps

  1. Enable on a domain

    Pick an engine in Plesk. The extension creates an isolated Docker stack for that domain.

  2. Isolate & authenticate

    A dedicated SMTP subaccount is created. SPF and DKIM records are added to the domain’s DNS automatically.

  3. Launch from the panel

    The client opens their marketing app from Plesk and starts sending on the dedicated marketing path.

Questions your ops team will ask

What is the CPU and RAM overhead per install?
Each domain runs its own Docker stack. Lightweight engines (Listmonk, Keila) use less; heavier ones (Mailtrain, Mautic) need more—plan capacity by which engines you offer. Campaign mail goes out through external marketing SMTP, not your local mail server.
How does licensing work across multiple Plesk servers?
Partner beta access is per provider. Install the extension on each Plesk host you manage, use your shared SendGrid parent key, and choose which engines clients can enable. Production licensing terms ship with general availability.
How are updates and engine versions handled?
The extension updates like any other Plesk extension. Engine images are pulled from official Docker registries when a domain is provisioned. Existing installs keep running until you disable or recreate them.

Get early access. Help shape the product.

We are inviting a limited set of hosting providers. Tell us about your Plesk setup and how email marketing fits your offers. Partners get beta access and a direct say on engines, SMTP providers, and packaging.

Thanks — we’ll review your request and follow ups.