Orchestrator.Pro - Email Infrastructure

0 Domains

0 Live

0 Needs attention

Server Default server for this batch. You can override it per domain in the preview below, and we'll fill IPs from the chosen server's pool.

Domains 0 One domain per line.

IPs 0 One IP per line, matched to the domain on the same line.

Default email prefix

@domain

What will happen

Each row shows the domain → IP pair we'll provision.

Add domains and IPs above to preview the deployment.

IP	Domain	Email	Server	Status

Name	Host	IPs	Status	Actions
Loading...

DNS

Domain DNS (Namecheap)

Sets DNS for new domains. Whitelist these IPs in Namecheap → Profile → Tools → API Access (the first is sent as ClientIp).

API user

API key

Whitelisted IPs

Deployment

Code source (Git)

The code Plesk pulls onto each new domain. Use a personal access token for private repos.

Repository

Access token

Plesk service plan Must match a hosting plan that exists on your Plesk servers exactly. Preflight warns if it's missing.

New campaign

Compose once, then send or schedule to any deployed domain.

Domains 0 selected

Loading domains…

Tick every domain this campaign should go to — the same newsletter is sent to each.

Sending list Pick an existing list or type a new name to create it. Leave blank to use “My First List”. (Suggestions come from the first selected domain.)

Recipients 0 valid These are added to the sending list (as confirmed subscribers) before the campaign goes out. Already-subscribed and invalid addresses are skipped. Optional — leave empty to send to whoever is already on the list.

Campaign name

Email subject *

HTML newsletter *

TEXT version (optional — sent as multipart when filled)

Sender name

Sender email

Reply-To

Bounce email

Sending speed (emails/hour)

Schedule date & time

Click the field to pick from the calendar. Empty = send immediately.

Unsubscribe link Web version link Queue for sending (uncheck = draft)

Campaign activity

Recent campaigns and test sends from the dashboard.

When	Domain	Subject	Type	Status	To
Loading…

Defaults for every new domain

Identity

Admin login & branding

Your own Interspire login used on every NEW install (existing domains keep theirs), plus the app name shown in the panel.

Admin username

Admin password

This is the saved Interspire admin password — click the eye to reveal it and hand it to the client (no email-based resets).

Application name

License key Applied to every new install. Leave blank only for unlicensed/testing.

Content

Starter email template

Installed as the first newsletter on every new domain. Leave HTML empty for the built-in default.

Subject line

HTML template Merge tokens: %%firstname%%, %%unsubscribelink%%, %%webversion%%.

Compliance

Sender identity

Shown in every email footer. A real postal address is required by CAN-SPAM and helps land in the inbox.

Company name

Postal address Falls back to the domain name if left blank.

User	Role	Status	Actions
Loading users…