Suspension recovery: what to do when SendGrid / Mailgun / SES kicks you out
This is one of the more common entry paths to our service. The pattern is recognisable: you ran a campaign that performed perfectly normally for your business, the SaaS provider's automated reputation system flagged it, your account was suspended without warning, and the support response was either non-existent or some variation of "the decision is final". You are now looking at a dead campaign tool, an unscheduled sales pipeline gap, and a deliverability problem to solve in under a week.
The recovery protocol we use is structured. Day 1: discovery call to understand the suspension reason (read the suspension email carefully — sometimes there is a real signal in there worth fixing). We audit your domain, IP history (if you owned them), DKIM keys and DMARC reports. Day 2-4: provision a new dedicated PowerMTA server with fresh IPs (your old SaaS-shared IPs are unrecoverable; do not try). Configure VMTAs, install authentication, enroll in postmaster tools. Day 5: parallel send with a small subset of your engaged audience to validate placement. Day 6-30: progressive warmup of the new IPs across your full list, with daily monitoring of Gmail Postmaster and Microsoft SNDS, automatic backoff if signals deteriorate.
The realistic timeline to full sending volume is 30-45 days. Anyone who promises faster is selling you a recipe for re-suspension on a different platform. The reason it takes this long is that the new IPs need to build their own reputation from zero, and the receivers will throttle you aggressively until that reputation is established. Skipping the warmup is what got you suspended in the first place; we are not going to repeat the mistake.
Compliance, abuse and the adult content question
Blue Spirit Hosting has always taken email policy seriously. We operate under the assumption that legitimate sending — permission-based marketing to people who asked for it and cold outreach within the limits of applicable law — is entirely lawful and commercially vital. We do not operate under the fiction that all bulk email is spam.
That said, we do not host what we do not host. No purchased or scraped lists. No phishing, credential harvesting, malware distribution, affiliate laundering or political disinformation. No adult content solicitation to non-opted-in audiences. No CSAM, ever — and yes, we cooperate with INHOPE and Interpol on that. Every client signs our acceptable use policy before activation and we verify the first week of traffic by hand.
When a legitimate complaint arrives — a DMCA takedown, a regulator inquiry, an abuse report — we investigate properly and work with you to resolve it. We do not suspend accounts over a single unverified complaint. We do not hand out data without legal process. We do not practise the kind of reflexive "suspend first, ask questions never" policy that drives serious senders away from the major platforms.
Migrating from another provider
Most new Blue Spirit PowerMTA clients come from somewhere else: a homegrown Postfix they have outgrown, a SendGrid account that was suspended, a competitor whose support stopped answering. Migration is part of the service, not an extra.
Our migration protocol is roughly: a 30-minute call to understand your stack, platform, list size, audience distribution and sending pattern; a staged migration plan (which domains, which campaigns, which audiences move first); parallel sending for the first one to two weeks so you can compare deliverability; DNS changes scheduled at low-traffic windows; and a two-week post-migration health check to confirm Gmail, Microsoft and Yahoo are all happy before we consider the job done. There is no extra charge for this on Growth and above.
Jurisdictional positioning: why we operate from Panama
We operate from Panama. That has three concrete operational implications worth understanding before you sign with us versus a UK, US or EU-headquartered managed PowerMTA provider.
First, jurisdiction. Panama operates under Law 81 of 2019 (a GDPR-aligned data protection regime that came into force in March 2021), but sits outside the EU's GDPR enforcement perimeter and the Five Eyes intelligence-sharing arrangement. For senders whose own GDPR compliance posture requires that DMARC reports, sending logs and metadata residency be evaluated as a vendor-risk question under DORA (effective January 2025) or under standard GDPR Article 28 processor agreements, working with a non-EU processor on a SCC framework is operationally simpler than navigating intra-EU vendor-risk questionnaires that increasingly assume the processor is EU-based. We provide standard SCCs and Article 28 contracts; the data we hold for clients is technical metadata (DMARC RUA reports, sending logs, headers), not subscriber personal data, which simplifies the lawful basis analysis substantially.
Second, time-zone coverage. Our engineering rotation spans EU, Americas and APAC business hours through a globally distributed team. When a deliverability issue surfaces at 03:00 GMT on a Tuesday — Asia-Pacific dawn, US west coast late evening — you reach an on-call engineer who answers in minutes, not the next-morning ticket queue you get from a UK or US-only support model. For senders operating real-time transactional flows where a 6-hour mailbox provider rejection cycle costs measurable revenue, follow-the-sun support is the operational difference.
Third, cost structure. Operating from Panama allows our pricing to be 50-70% below UK/US-headquartered managed PowerMTA providers — Growth at €149/month delivers the same technical depth that the major UK and US managed providers charge $300-700/month for. The technical operation is identical: PowerMTA 6.0, Tier-3 datacentres in Frankfurt, Amsterdam, Ashburn and Phoenix, same engineering experience derived from running the platform at scale across 100+ client engagements. The difference is operating jurisdiction overhead, not corner-cutting on infrastructure quality, license compliance, or engineering depth. For senders whose total deliverability budget is the constraint that decides whether they invest in dedicated IPs and managed PowerMTA versus stay on shared SaaS — the structural cost difference matters.
