Is It Time to Move from Dotdigital to Owned Email Infrastructure?
Dotdigital is the omnichannel marketing automation platform (UK-based). Founded in 2000 and headquartered in London, UK, it serves UK and European mid-market wanting omnichannel on a European platform. This comparison examines where Dotdigital's platform model creates constraints that dedicated email infrastructure — dedicated IPs on PowerMTA + MailWizz managed by Cloud Server for Email — is designed to resolve.
Dotdigital's primary strengths are UK/EU company, omnichannel. Organizations choose it for good automation, strong customer success team. The platform abstracts infrastructure management — users don't need to understand IP warming, per-ISP SMTP configuration, or reputation management to launch campaigns. This abstraction is genuinely valuable for organizations within its intended use case.
The question this comparison addresses is specific: at what point does Dotdigital's platform abstraction shift from an advantage to a constraint? The answer depends on sending volume, geographic target (particularly EU compliance requirements), IP reputation requirements, and the technical sophistication of the team managing the email program.
Every email marketing platform including Dotdigital uses shared IP pools. Your messages share IP addresses with other senders — some careful, some less so. When a co-tenant on your shared IP generates spam complaints, gets blacklisted, or violates ISP sending guidelines, your delivery suffers. ISPs track reputation at the IP level, and that reputation is influenced by every sender on that IP.
This co-tenant risk is invisible at low volume. At moderate to high volume, it becomes a significant variable that you cannot control. You can have excellent list hygiene, high engagement, clean content, and proper authentication — and still see inbox placement degradation because of another sender's behavior on your shared IP pool.
Dedicated IPs eliminate this variable. Your IP reputation is determined entirely by your own sending behavior. Your inbox placement reflects your list quality and content relevance, not the behavior of co-tenants you can't see or control.
Dotdigital's infrastructure is UK/EU-based (post-Brexit nuance). While this addresses basic EU data residency, shared infrastructure still means subscriber data may be co-located with non-EU subscriber data on shared storage systems.
Cloud Server for Email operates from globally distributed infrastructure. Subscriber data processed through our infrastructure stays in the EU throughout its lifecycle. We provide a Data Processing Agreement (DPA) under GDPR Article 28 covering processing instructions, security measures, sub-processor disclosure, and breach notification. For EU-based senders or senders targeting EU recipients, this eliminates the compliance overhead associated with cross-border data transfer arrangements.
Dotdigital's pricing at 100,000 monthly emails is ~$100–300. At 1,000,000 monthly emails, it's ~$500–1,000. At 5,000,000 monthly emails, it's ~$1,200–2,800. Dedicated PowerMTA + MailWizz infrastructure on Cloud Server for Email at these volumes costs €150–250, €250–450, and €400–700 per month respectively — including managed service, monitoring, and technical support.
The financial case for dedicated infrastructure typically materializes between 500,000 and 1,500,000 monthly emails. Below this threshold, the operational simplicity of a managed platform usually outweighs the cost premium. Above this threshold, dedicated infrastructure provides significant cost savings while delivering better operational control and IP reputation isolation. Use our Infrastructure Cost Calculator to model your specific situation with editable pricing.
When deliverability problems occur — and at scale they will — Dotdigital provides dashboard metrics: open rate, click rate, bounce rate. What it doesn't provide is SMTP-level diagnostic data: which ISP is returning 421 deferrals, what specific diagnostic text accompanies those deferrals, which of your IPs (if you had multiple) has the reputation issue, and whether the problem is trending better or worse over the past 6 hours.
PowerMTA's SMTP accounting log records every delivery event with full diagnostic data. Query it to identify exactly which ISP domain is deferring and the exact error text they're returning. This visibility enables problems to be diagnosed and resolved in 2–4 hours instead of the days it typically takes when working from dashboard-level aggregate metrics and waiting for ESP support to investigate on your behalf.
Migrating from Dotdigital to dedicated infrastructure requires IP warming — the 8–12 week process of building reputation on new dedicated IPs before running full production volume. New IPs have no reputation history; ISPs apply conservative filtering while reputation signals accumulate. Warming must be managed correctly: too aggressive a ramp produces 421 deferrals that damage the IP's reputation during the critical early weeks.
Cloud Server for Email manages IP warming for clients: configuring PowerMTA warming schedules per ISP, monitoring Google Postmaster Tools domain/IP reputation daily, adjusting volume ramp based on observed delivery signals, and identifying and resolving any issues before they compound. The warming period is when per-ISP visibility matters most — the difference between a smooth 8-week warming and a 16-week struggle is daily monitoring discipline during the ramp.
The migration process from Dotdigital to dedicated infrastructure requires 3–6 weeks (CSV export, automation rebuild). The technical sequence is:
Dedicated infrastructure is not the right choice for every organization. Dotdigital remains appropriate when: monthly volume is below 300,000 sends and deliverability has been consistently strong, the team doesn't have (or want to acquire) infrastructure management expertise and prefers full managed service, the email program is a minor channel rather than a revenue-critical function, or Dotdigital's platform-specific features (like specific integrations or automation builders) provide genuine value that outweighs the constraints.
Dedicated infrastructure is the better choice when: volume exceeds 750,000 monthly sends and the cost comparison favors infrastructure, GDPR data residency is a hard compliance requirement, IP reputation isolation is needed for transactional email separation or brand protection, your team needs the diagnostic visibility to manage deliverability proactively, or you've experienced co-tenant IP contamination that Dotdigital hasn't been able to resolve.
We provide a no-obligation technical assessment for organizations evaluating migration from Dotdigital. We'll review your sending program, model the infrastructure configuration, estimate IP warming timeline and cost, and provide a clear comparison. Contact infrastructure@cloudserverforemail.com or +372 602-7190.
When you migrate from Dotdigital to dedicated infrastructure on Cloud Server for Email, your email sending is handled by PowerMTA — the industry-standard commercial MTA for high-volume email operations. PowerMTA's domain block system allows per-ISP configuration that Dotdigital's platform cannot provide. Here's what a production configuration looks like:
<domain gmail.com>
virtual-mta-pool production-pool
max-smtp-out 10 # Concurrent connections to Gmail
max-msg-rate 3500/h # Hourly message limit to Gmail
retry-after 15m # Retry interval after 421 deferral
max-msg-per-conn 100 # Messages per SMTP session
mx-rollup gmail.com # Group all Gmail MX records
dkim-sign yes # DKIM signing enabled
</domain>
<domain outlook.com>
virtual-mta-pool production-pool
max-smtp-out 5 # Microsoft is more conservative
max-msg-rate 2000/h
retry-after 30m # Outlook benefits from longer retry interval
mx-rollup outlook.com
</domain>
<domain yahoo.com>
virtual-mta-pool production-pool
max-smtp-out 6
max-msg-rate 2500/h
retry-after 20m
</domain>This per-ISP granularity is what drives the deliverability improvement over Dotdigital's shared infrastructure. Gmail, Outlook, and Yahoo each have different throttling models, different reputation systems, and different response patterns to high volume. Treating them identically — as shared ESPs must — produces suboptimal results for at least two of the three. PowerMTA's domain blocks allow each ISP to be handled according to its own requirements.
Dedicated infrastructure gives you full control over email authentication — but that also means you're responsible for configuring it correctly. Cloud Server for Email handles this as part of the infrastructure setup, but here's what the authentication stack looks like for a properly configured dedicated sending environment:
While PowerMTA handles delivery (the MTA layer), MailWizz provides the campaign management layer — list management, campaign creation, scheduling, bounce processing, and reporting. MailWizz replaces the front-end interface that Dotdigital provides, running on your own dedicated server or Cloud Server for Email's managed infrastructure.
MailWizz's key features for senders migrating from shared ESPs:
The MailWizz interface is functional rather than polished — it's not as visually refined as Dotdigital's UI, and some workflows require more clicks than equivalent operations on a modern ESP. This is the trade-off for infrastructure ownership: you gain control and cost efficiency, but the platform UX is more utilitarian. For high-volume senders where deliverability and economics matter more than UI aesthetics, this trade-off is consistently worthwhile.
The primary objection to dedicated infrastructure is operational overhead: someone needs to monitor PowerMTA daily, manage IP reputation events, apply configuration updates, and handle incidents. For organizations without a dedicated infrastructure team, this overhead is real.
Cloud Server for Email operates the infrastructure on your behalf. The managed service includes:
The managed service model provides the deliverability management capability of a dedicated infrastructure team — at a fraction of the cost of hiring that team, and significantly less than the premium pricing of Dotdigital at scale. Contact infrastructure@cloudserverforemail.com for specific pricing for your volume.
High-volume email delivery is ultimately a relationship between your infrastructure and the major ISPs — primarily Gmail, Microsoft (Outlook/Hotmail/Live), and Yahoo/AOL, plus European providers including GMX, Web.de, T-Online, Orange, and Free. Each ISP has its own reputation system, filtering criteria, and response patterns to high-volume senders. Understanding these relationships — and having the infrastructure to manage them — is what separates consistent inbox placement from unpredictable delivery.
Gmail is typically the largest destination for B2C email senders, representing 35–40% of consumer inboxes globally. Gmail's filtering is primarily domain reputation-based rather than IP-based — your sending domain's reputation at Google determines inbox placement more than your IP's reputation. This domain reputation is tracked at postmaster.google.com (Google Postmaster Tools) and updated daily.
Postmaster Tools provides: spam rate (percentage of your mail users mark as spam — threshold for action: >0.10%, serious concern: >0.30%), domain reputation tier (Bad/Low/Medium/High), IP reputation tier, delivery errors (authentication failures, DNS issues, policy violations), and feedback loop data. Monitoring these metrics daily during IP warming and ongoing operations is the foundational monitoring discipline for Gmail deliverability.
Dedicated infrastructure enables daily Postmaster Tools monitoring to be integrated into your operational routine: check domain reputation tier, review spam rate trend, verify authentication status, check IP reputation for each sending IP. Any negative trend triggers a defined response protocol — reduce volume at the affected reputation tier, increase engagement-based segmentation, isolate if possible to identify the traffic segment driving the problem.
Microsoft's filtering at Outlook.com (including Hotmail and Live.com) uses a combination of IP reputation via the Smart Network Data Services (SNDS) portal and domain-level filtering. SNDS provides per-IP data: trap hit rate (spam trap hits — indicates list quality problems), complaint rate from users, and an overall status (Green/Yellow/Red). JMRP (Junk Mail Reporting Program) provides complaint feedback loop data.
Microsoft's filtering is more IP-centric than Gmail's. An IP with Red SNDS status will experience significant deferral or blocking at Outlook.com regardless of domain reputation. Managing Outlook deliverability requires: keeping SNDS status in the Green range for all sending IPs, monitoring complaint rate (target below 0.3%), and implementing SNDS IP removal requests promptly when Yellow/Red status appears.
On shared ESP infrastructure, you share SNDS status with other senders. Your SNDS status reflects every sender on your shared IP — not just your sending behavior. On dedicated IPs, your SNDS status reflects only your list quality and sending practices, making it actionable data rather than a measurement of co-tenant behavior you can't control.
European ISPs are critical for EU-market senders and are often underweighted in deliverability planning focused primarily on US ISPs. GMX and Web.de (both Ionos/United Internet) together represent the largest email provider in Germany and much of German-speaking Europe. T-Online/Telekom.de is the second major German provider. Orange and Free are primary French consumer email providers.
European ISPs tend to be more conservative than Gmail in their filtering thresholds and have less sophisticated feedback mechanisms. GMX and Web.de have their own feedback loop and postmaster resources (postmaster.gmx.net). T-Online provides limited postmaster data. European ISPs frequently use regional blacklists in addition to global lists like Spamhaus, requiring monitoring of EU-specific blacklist data.
Cloud Server for Email's EU datacenter location provides a geographic advantage for European ISPs: connections from infrastructure IP addresses to European ISPs have lower latency than connections from US infrastructure, and EU-origin sending is viewed more favorably by some European ISP filtering systems than non-EU-origin sending.
For organizations migrating from a shared ESP to dedicated infrastructure, the 12-month journey looks like this:
Infrastructure configuration (PowerMTA, MailWizz, authentication), IP acquisition, warming schedule setup. Begin sending Week 1 volume to highest-engagement subscribers only. Daily monitoring of Postmaster Tools and SNDS. Expect lower throughput than production capacity during this phase — warming is designed to build reputation safely, not to maximize volume immediately.
Most warming schedules reach 80–100% of target volume by Week 10–12. By Month 3, the infrastructure should be approaching full production capacity. Continue monitoring ISP reputation signals daily. Any reputation signals that indicate problems (rising spam rate, Yellow SNDS status) trigger immediate volume reduction and investigation before continuing the ramp.
Full production volume on dedicated infrastructure. Monthly configuration review adjusts domain block parameters based on observed delivery data. Quarterly authentication review verifies DKIM rotation schedule, DMARC report analysis, SPF coverage. Reputation monitoring is continuous but less intensive than during warming.
By Month 9, the infrastructure investment is paying consistent dividends: lower cost per million emails than the previous ESP, full IP reputation isolation producing consistent inbox placement, EU data residency compliance without contractual overhead, and operational visibility enabling proactive response to deliverability events. The 12-month ROI comparison almost always favors dedicated infrastructure for organizations that send above 750,000 monthly emails.
One of the most consistent findings across high-volume sending environments is that list hygiene and infrastructure quality are not independent variables — they interact in ways that either compound or counteract each other. A clean list on degraded infrastructure still delivers poorly. Excellent infrastructure with a poorly maintained list still produces deliverability problems. The combination of good list hygiene and proper dedicated infrastructure is what produces consistently strong inbox placement.
List hygiene for high-volume senders involves: removing hard bounces within 24 hours of the bounce event (automatic with PowerMTA's bounce processing), suppressing FBL complaint addresses within 48 hours (automatic with feedback loop processing), removing addresses that haven't engaged in 90 days before they reach 180 days of inactivity, validating new subscriber addresses at the point of acquisition (syntax and domain verification, MX record checking), and running re-engagement campaigns for addresses showing declining engagement before they become inactive.
On shared ESP infrastructure, list hygiene partially compensates for co-tenant reputation problems — but only partially. On dedicated infrastructure, list hygiene directly determines your IP reputation. There's no shared pool to average out your performance; every complaint rate and bounce rate signal comes from your list, and every reputation consequence flows directly to your IPs. This makes dedicated infrastructure a stronger incentive for list hygiene discipline than shared infrastructure, where poor performance is partially absorbed by pool averaging.
Bounce processing — automatically updating subscriber status based on SMTP delivery responses — is the foundational list maintenance function. Shared ESPs handle bounce processing for you, but with limited transparency: you see that addresses were bounced, but not the specific SMTP diagnostic text that determined the bounce classification, and you have no control over the classification rules.
With PowerMTA, bounce classification is configurable at the pattern-list level. The smtp-pattern-list can be customized with ISP-specific rules: Google's '5.1.1 The email account that you tried to reach does not exist' pattern is classified as a hard bounce and triggers immediate suppression. A Yahoo '421 4.7.0' pattern is classified as a temporary deferral and retried. Classification accuracy directly affects list quality — misclassified bounces either leave invalid addresses on the list (producing ongoing complaint signals) or remove valid addresses prematurely (reducing list size without justification).
The technical migration — exporting lists, configuring MailWizz, setting up PowerMTA — takes 1–2 weeks. The IP warming process adds 8–12 weeks. Total elapsed time from the migration decision to full production on new infrastructure is typically 10–14 weeks. During this period, you can continue sending via the shared ESP while warming new IPs, maintaining continuity.
Adding IPs to your pool is a straightforward process: acquire the new IP(s), add them to your PowerMTA virtual-mta-pool configuration, and warm the new IPs according to the same warming schedule used for the original pool. New IPs can be warmed in parallel with existing production IPs — the existing IPs continue handling production volume while the new IPs warm up separately. Cloud Server for Email manages this process for infrastructure clients.
Yes — and isolating them is recommended. PowerMTA's virtual-mta-pool system allows dedicated IP pools for transactional and marketing traffic. Transactional IPs (for password resets, order confirmations, etc.) carry only low-volume, high-priority mail, maintaining a clean reputation baseline that isn't affected by marketing campaign performance. Marketing IPs handle bulk campaigns with their own reputation profile. This isolation means that a reputation event in your marketing program doesn't affect transactional delivery to customers who need password resets or purchase confirmations.
Cloud Server for Email's managed infrastructure service includes: daily accounting log review and anomaly detection, daily Google Postmaster Tools monitoring (domain and IP reputation), daily SNDS monitoring (Outlook IP reputation), daily blacklist monitoring across 50+ lists, monthly configuration review and optimization, IP warming management for new IPs, authentication maintenance (DKIM rotation, SPF updates), and incident response with a 4-hour response time SLA for delivery events. Contact infrastructure@cloudserverforemail.com for pricing specific to your sending volume.
Cloud Server for Email operates managed PowerMTA + MailWizz environments from EU servers.
Dedicated IPs, daily monitoring, GDPR compliance by design.
