On this page
What shared SMTP is
Shared SMTP means sending through infrastructure used by several senders, usually a reputable cloud sending service. The provider manages the IPs, their reputation and the underlying servers. You manage your domain, your authentication and your lists.
A good shared pool has consistent, established traffic, which gives receivers enough history to trust it. For a sender with modest volume, that can outperform a dedicated IP that never sees enough mail to build its own reputation.
Shared sending also removes much of the operational work. There is no server to patch, no queue to watch and no IP warm-up to manage for the pool itself. Your responsibilities narrow to authentication, list quality and handling the events the provider sends back, which suits teams whose main job is not email infrastructure.
Who it suits
- Businesses sending newsletters or updates a few times a month.
- Applications with modest transactional volume.
- New senders who haven’t yet established regular patterns.
- Teams that don’t want to run or monitor servers.
We’ll tell you honestly which side of the line you’re on. If your volume is large and steady, dedicated SMTP may serve you better.
What’s included
- Choosing a reputable shared provider suited to your mail type and volume.
- Domain verification with DKIM signing on your own domain.
- A custom return-path or MAIL FROM subdomain so SPF aligns.
- DMARC published and monitored.
- Bounce and complaint notifications connected to your suppression list.
- A custom tracking domain where your platform supports it.
- Connection of your website, app or email platform with individual credentials.
- A written note of when an upgrade to dedicated would make sense.
How we set it up
- Review your volume, mail types and current setup.
- Recommend a provider and plan, and open or configure the account.
- Verify your domain and publish authentication records.
- Connect your applications and platforms, then send test messages to major providers.
- Confirm bounces and complaints flow back into suppression.
- Document the setup and hand over.
Most shared setups can be completed quickly, since there are no servers to build. Provider onboarding or account review is often the longest step.
Why your own domain still matters on shared
Even on shared IPs, mailbox providers increasingly judge the domain that signs and sends your mail. Aligned DKIM on your own domain means the reputation you build stays with you if you ever change provider. Sending with a provider’s default domain means you build nothing of your own.
What we look for in a shared provider
Not all shared sending is equal. The quality of a shared pool depends on how carefully the provider vets and polices its customers. When recommending one, we consider:
- A clear, enforced acceptable-use policy and active abuse handling.
- Support for custom DKIM and return-path domains on your own domain.
- Bounce, complaint and delivery events available by webhook or notification.
- Separate handling or configuration for transactional and marketing mail.
- Suppression management you can see and export.
- Reasonable options to move to dedicated IPs later without changing platform.
What affects timeline and cost
- Number of domains and applications to connect.
- Provider onboarding or review steps.
- Whether bounce and complaint handling needs custom integration.
- Migration from an existing sending setup.
Common mistakes
Sending from the provider’s default domain without your own DKIM. Ignoring bounce notifications because the provider “handles it”. Choosing a provider based only on headline pricing without checking its policies. Assuming shared means no responsibility for list quality.
See all email infrastructure services, read our guide, or contact us.
Frequently asked questions
Will other senders on the shared pool hurt my delivery?
Reputable providers police their pools closely. Your own domain authentication also means much of your reputation is judged separately from other senders.
When should we move to dedicated?
When your volume is large and regular enough to keep a dedicated IP warm. We’ll look at your numbers and tell you honestly.
Can transactional and marketing mail share one account?
They can, but we recommend separating them by configuration or subdomain so a marketing issue never delays a password reset.
Do we still need DMARC on shared sending?
Yes. DMARC protects your domain from spoofing and is expected by major mailbox providers regardless of which infrastructure you use.
Can we use our own tracking domain on shared sending?
On most reputable platforms, yes. We set it up with SSL so your links match your domain rather than the provider’s.
Talk to us about shared smtp solutions
Cost-effective sending for lower volumes without running your own infrastructure.