Client-Facing
Email marketing and hosting — Your clients' campaigns and your shared sending reputation
Sending reputation is the one asset on a reseller shelf that every client shares and no client owns, and one of them is about to post a newsletter through it.
Straight answer first
Keep hosting for the site, the forms and the mailboxes, put anything at volume through a proper sending platform, and use DNS authentication to stitch the two into one trusted domain. On a reseller shelf that is not a preference, it is protection: campaign-scale sending through hosting SMTP borrows reputation that belongs to every account on the machine.
Below: why reputation is shared, exactly where to draw the line in a client agreement, the DNS work that has to be done once per client, and what to do the morning after a blocklisting.
Written by the Hosting Seller staff · Checked 24 August 2026
24/7
Answered by people, for you and them
1-click
WordPress setup in every account
Free
Certificates on every site you host
Daily
Backups across every account
Whether a campaign reaches inboxes comes down to sender reputation built on dedicated sending infrastructure. That is precisely what an email service provider runs and precisely what hosting SMTP is not built to offer at volume.
For an end user this is advice. For a reseller it is policy, because the consequences of getting it wrong do not stay with the client who caused them.
Reputation is shared, and that is the whole problem
Mail leaving a shared or reseller platform is judged partly on the sending address's history. That history is influenced by every account sending from it.
So a client who exports a purchased list and posts it through hosting SMTP is not only damaging their own delivery. They are spending an asset that the brochure site three accounts along also depends on for its order confirmations.
This is why the policy has to be set before it is tested, and why it should be a term rather than a request. Nobody enjoys the version of this conversation that starts after the damage.
The line to draw in the client agreement
Mailboxes, forwarders, contact-form mail and transactional messages at ordinary volume: hosting. Newsletters, campaigns, announcements to a list, and anything measured in thousands: a sending platform.
State a volume figure rather than a principle, because a principle is arguable and a number is not. Then say what happens if it is exceeded, and mean it.
It is worth offering the alternative in the same breath. A client told what they cannot do resents it; a client shown the arrangement that actually works usually takes it, and often pays you to set it up.
The DNS work, per client, once
An SPF record authorising both the mailbox host and the sending platform, without conflicts and without exceeding the lookup limit. DKIM keys published for each sender. A DMARC policy tying the two together.
One afternoon of DNS work per client decides whether either stream of mail lands. Do it at onboarding rather than in response to a complaint, and record what you set so the next person can read it.
Then keep the signup forms on the client's own site feeding the sending platform. That way the list is built from a domain that is already authenticated rather than from somewhere with no history at all.
The morning after a blocklisting
It happens. The response is to find the sender, stop it, then request delisting with an honest account of what changed, because the second delisting request is much harder than the first.
The plan for this is Pro, with mailboxes on the client's own domain, spam and virus filtering fitted as standard, and a move-in handled by our staff if the mail is arriving from somewhere else.
Bring an existing site and we shift it across at no charge, usually inside 24 hours, with nothing going dark while we work, which matters more with mail than with anything else on the account.
Why we care who you let send
Delivery is a shared asset and we would rather protect it than referee it afterwards. A supplier with loose sending policies is cheaper right up until the week your clients' order confirmations stop arriving.
NVMe disks and LiteSpeed caching sit on the shelf at every price point, not behind a premium tier.
- Filtering fitted to every mailbox as standard
- Mailboxes on the client's own domain, included
- A move-in that carries the mail across too
- A sending policy stated as a number, not a principle
Why Hosting Seller
On every plan, as standard
The plan behind this page
Pro carries the site, the forms and the mailboxes on the client's own domain at one flat price, with the essentials already in it.
Filtering as standard
Spam and virus filtering fitted to every mailbox, which is the baseline before any campaign question arises.
Mail moved with the site
Our free migration brings mailboxes and configuration across, not just files and databases, so nothing arrives after the DNS has changed.
A supplier you can name
IGI Security Services Ltd, registered in England and Wales, with terms published under English law.
One shelf, every size
Shared, VPS and dedicated under one account, so a client whose sending genuinely needs isolation has somewhere to go.
Margin that survives renewal
The order price is the renewal price, so a mail-heavy client does not become more expensive to serve over time.
First Steps
From choosing to live
- 1
Put a volume figure in the agreement
A number is enforceable and a principle is arguable. State what counts as campaign sending and what happens when a client crosses it.
- 2
Do the DNS at onboarding
SPF covering both senders without exceeding the lookup limit, DKIM for each, and a DMARC policy over the top. One afternoon per client, recorded so the next person can read it.
- 3
Offer the alternative in the same sentence
Clients accept the restriction readily when it arrives with a working arrangement attached, and setting that up is usually billable.
In the Box
Packed with every plan
- Mailboxes on the client's own domain, included with every plan
- Spam and virus filtering fitted to every mailbox
- Webmail plus IMAP, POP and SMTP for the client's own software
- DNS records managed from the panel, per client
- Site migration handled by our staff at no charge, mail included
- Free SSL on every site you host, reissued before it lapses
- Daily backups with restores you run yourself
- LiteSpeed caching running at the server rather than by plugin
- Upgrades apply to the account in place, with no move between plans
- The renewal price on the tag matches the order price
Across the Counter
Things people ask us all the time
Why does one client's newsletter affect everybody else's mail?
Because outbound reputation on a shared platform is influenced by everything sending from it. A campaign posted through hosting SMTP borrows an asset that every other account depends on for order confirmations and password resets, and it can spend it very quickly.
Where exactly should I draw the line?
Mailboxes, forwarders, contact-form mail and ordinary transactional messages belong on hosting. Newsletters, list announcements and anything measured in thousands belong on a sending platform. State it as a volume figure in the agreement, because a number is enforceable and a principle is not.
Which DNS records does the arrangement need?
An SPF record authorising both the mailbox host and the sending platform without conflicts or too many lookups, DKIM keys published for each sender, and a DMARC policy tying them together. Do it at onboarding, and write down what you set.
What do I do if a client gets us blocklisted?
Find the sender, stop it, then request delisting with an honest account of what changed. Be thorough the first time, because a second request from the same address is treated far less generously. Then fix the policy that allowed it rather than the incident alone.
Read next
Hosting With Staging Environments
Testing a client's change somewhere safe first, and why that habit pays for itself on a busy book.
Hosting With PostgreSQL
The client whose application would rather talk to Postgres, and what that changes about the account you sell.
Mail Filtering
Spam and virus filtering in front of any mailbox, wherever it is hosted.
Web Hosting
cPanel accounts on NVMe disks, with SSL, the move-in and year-one domain included.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Protect the delivery everybody shares.
Mailboxes on the client's own domain with filtering fitted as standard, and a free move-in that carries the mail across.
See Mail Filtering plans