Bulk email SMTP · 2026

A dedicated SMTP server, tuned for the moment your campaign hits send.

For senders who need their own relay, their own IPs and their own reputation. Point MailWizz, Acelle, Interspire, Mautic or your own application at our PowerMTA-backed SMTP endpoint and watch the queue drain — not stall.

PowerMTA back-end
Dedicated IPs
Per-ISP throttling
SMTP-AUTH + IP whitelist
Up to 10M+ emails/day
From €89/month

See plans Talk to sales Chat on WhatsApp

Why dedicated bulk SMTP

Shared SMTP is cheap. Shared reputation is expensive.

Relay providers priced at a few dollars a month look attractive until you realise what you are paying for. You share the outbound reputation of everyone else on that IP pool. When one of them burns the IPs, your emails start landing in spam. When the provider reacts by throttling the pool, your campaigns take 48 hours to drain. When they rotate IPs to fix it, your warm-up resets.

Dedicated bulk SMTP flips the equation. The IPs are yours. The reputation is yours. The throttling rules are tuned for your workload. Bounces come back to your platform fast enough to update suppression lists before the next campaign goes out. And when something goes wrong, we fix it for you — not for the other sixty clients on the same shared box.

Sustained, not peak

Our quoted capacity is what the server sustains all day at realistic bulk workloads. Not a marketing burst number that collapses under real content.

Bounces back in seconds

Hard bounces, soft bounces, 4xx deferrals — parsed by PowerMTA, classified, and posted back to your platform fast enough to act on them before the next batch.

Global ISP coverage

Pre-tuned for Gmail, Outlook, Yahoo, Apple, Yandex, AOL, GMX, Free.fr, Wanadoo, Mail.ru, and the regional ISPs your international lists depend on.

Clean authentication

SMTP-AUTH credentials, TLS on port 587 and 465, source-IP allow-listing, DKIM signing server-side with selectors you can publish.

2026 reality

The bulk SMTP landscape changed in 2024 — three things are different now.

If you last evaluated dedicated SMTP in 2022, the market shifted in ways that change the calculus. Three concrete changes determine whether SaaS, dedicated SMTP, or a hybrid is the right answer in 2026 — and pretending the old playbook still applies costs money.

First, SaaS provider pricing inflated faster than infrastructure costs. SendGrid Pro is now $89.95/month for 100K emails, with $30/month per additional dedicated IP. Mailgun Foundation is $35/month for 50K. Postmark prices a single dedicated IP add-on at $50/month. The per-email economics make sense at low volume; above 500K monthly emails, the math flips and dedicated bulk SMTP infrastructure becomes the cheaper option even when you account for engineering time. The exact crossover point is around 750K emails/month for typical marketing workloads — verifiable with a spreadsheet.

Second, shared IP pools became more dangerous, not less. Gmail and Microsoft both tightened their reputation models in 2024-2025, and the consequence for shared pools is that one bad sender on the pool drags the whole pool down faster than before. SendGrid's "pool C" reputation issues across 2024 hit dozens of legitimate senders who had no involvement in the bad behaviour that triggered it. Shared-IP cloud SMTP is acceptable below 100K monthly emails; above that, the concentration risk becomes operational liability. Dedicated IPs flip that risk to your own behaviour, which is the only variable you actually control.

Third, the bulk sender requirements (Google/Yahoo February 2024, Microsoft May 2025) made deliverability tooling table-stakes. Pre-2024, you could send from a generic SMTP server with default DKIM and skate by. Now you need SPF aligned with the From domain, DKIM 2048-bit with rotating selectors, DMARC published with monitoring, RFC 8058 one-click unsubscribe in headers, and complaint rates sustained below 0.1% operationally. SaaS providers handle this for you (sometimes); DIY bulk SMTP requires you to handle it yourself or use a managed provider. We handle it as part of every plan.

The takeaway: in 2026, the bulk SMTP decision is less about "self-hosted vs SaaS" and more about "where does my volume put me on the cost curve, and do I want to operate compliance tooling myself". Most operators above 500K monthly emails win by switching to managed dedicated SMTP; most operators below that win by staying on SaaS. We tell you on the discovery call which side of the curve you are on.

Decision framework

SaaS, dedicated SMTP, or hybrid — how to choose.

The decision tree below is the same one we walk through on the discovery call. The branches that lead to "do not buy this" are real — sometimes a SaaS provider is genuinely the right answer at your volume, and sometimes a hybrid (transactional on Postmark + marketing on dedicated SMTP) is better than picking one tool for both jobs.

Two sub-points the diagram does not capture. First: the 500K threshold is conservative — we have moved clients to dedicated SMTP at 250K monthly when their content profile triggers SendGrid throttling regularly, or when their compliance requirements push toward dedicated infrastructure earlier. Second: the hybrid setup is more common than the diagram suggests. Many B2B SaaS companies run Postmark for password resets and 2FA codes (because Postmark optimises specifically for these), and Blue Spirit for bulk marketing newsletters and lifecycle campaigns. The two systems do not interfere — different domains, different IPs, different reputation pools — and the deliverability is better on each workload than it would be on a single-vendor bundle.

Bulk SMTP architecture — what runs underneath the relay endpoint.

The diagram below shows what happens between your application calling our SMTP endpoint and the recipient's mail server accepting the message. Each layer is engineered for high-throughput sustained sending, not the burst-oriented architecture that small SMTP relays use.

Five common mistakes when migrating to dedicated bulk SMTP

About half of our new bulk SMTP clients arrive after running on shared SaaS providers and hitting volume or deliverability walls. We audit the planned migration before flipping traffic. The five mistakes below show up in nearly every poorly-planned migration:

1. Skipping IP warmup because "we already had reputation on SaaS"

Reputation is per-IP, not per-sender. The reputation you built on SendGrid's pool C does not transfer to your fresh dedicated IPs at Blue Spirit. Skipping warmup on day one and pushing 200K daily emails through cold IPs lands you in Gmail "low reputation" within 72 hours. The fix: 14-30 day warmup ramp, starting at 1,000-5,000 emails/IP/day, scaling based on engagement signals from Postmaster Tools. We will not let you skip this even if you push. The only honest exception is when you migrate IPs that already had warm-up history with us (a previous Blue Spirit customer's relinquished IPs, for example) — and we tell you upfront which IPs in your pool fall into that category, with documentation of the prior usage.

2. Pointing both transactional and marketing at the same IPs

Common pattern: client moves both password resets and weekly newsletters to the same 2-IP dedicated pool because "they're all our emails". Then a marginal newsletter campaign generates a 0.4% complaint rate, the IPs get throttled by Gmail, and password resets stop arriving. Critical transactional traffic should be isolated to its own pool with its own DKIM selector, often even its own subdomain. We split them automatically; teams that don't usually learn the hard way. The architecturally clean separation is: transactional traffic on a dedicated 2-IP pool with priority queueing, marketing traffic on a separate 3-5 IP pool with broader throttling tolerance. The two pools never share IPs even if your monthly volume is technically low enough that they could fit on one — the operational hygiene is worth the IP allocation.

3. Migrating during a peak campaign window

Marketing teams sometimes plan the SMTP migration to coincide with their next big campaign because "we want the new IPs ready for it". This is exactly backwards. Peak campaigns are the worst time to test new infrastructure — any deliverability issue compounds with high volume. The right pattern: migrate during a low-traffic period (mid-quarter, post-holiday), warm the new IPs across 2-4 weeks of normal sending, then run the peak campaign on infrastructure that has been validated. We have seen Black Friday campaigns disasters specifically because the team migrated 2 weeks before — the IPs were not warm, the bulk send tanked the reputation, and recovery took 4-6 weeks into Q1. The lesson encoded in our migration playbook: peak campaigns run on stable infrastructure that has at least 60 days of operational history.

4. Not testing DKIM/SPF/DMARC alignment before going live

The new SMTP server is provisioned, MailWizz is configured, the campaign is queued. Nobody verified that the SPF record was updated to include the new sending IPs, or that DKIM signature alignment matched the From domain, or that DMARC was set up correctly for the new path. The first batch goes out, 30% lands in spam silently because the DMARC alignment fails, and the team spends a week diagnosing what should have been caught in 5 minutes of pre-launch testing. Our standard onboarding includes alignment validation against a controlled inbox before any production traffic — we send 20 test messages from your application through the new SMTP path to a Gmail, Outlook, Yahoo, and iCloud test pool, verify SPF passes, DKIM signs and aligns, DMARC reports show pass, and only then do we hand over the credentials for production use.

5. Not configuring bounce processing before sending

The most expensive small mistake. Bounces from PowerMTA accounting files need to flow back to your platform's suppression list — automatically and fast. If bounce processing is not running or is misconfigured, the next campaign re-sends to known hard-bounced addresses, complaint rate spikes from receivers who marked the bounce as spam, reputation tanks within days. Verify the suppression sync is working on day one with a controlled test before any real campaign launches. We send a small batch of test mail to known-bad addresses (deliberately misconfigured DNS, deliberately invalid recipients), confirm PowerMTA correctly classifies them as hard bounces, confirm the webhook posts the suppression update to your platform within 60 seconds, and only then mark the bounce flow as production-ready.

Bulk SMTP providers compared (2026 pricing).

Six providers operators compare against Blue Spirit Bulk SMTP. The matrix below uses 2026 retail pricing, normalised to a 1M emails/month workload with 2 dedicated IPs where applicable. The "best fit" column is the operator profile each provider actually serves well — not the marketing positioning.

Provider	Entry pricing	Cost @ 1M/mo + 2 IPs	Dedicated IP cost	Best fit
SendGrid Pro	$89.95/mo (100K)	~$389/mo	+$30/mo per extra IP	Mid-volume marketing + dashboard needs
Mailgun Foundation	$35/mo (50K)	~$530/mo (with overage)	Included in higher tiers	Developer-first transactional
Amazon SES	$0.10 / 1K emails	~$150/mo	$24.95/mo per IP	Pure cost-optimisation, AWS-integrated
Postmark	$15/mo (10K)	~$1,300/mo	$50/mo per IP add-on	Premium transactional only
Brevo (Sendinblue)	$25/mo (20K)	~$449/mo (Business)	Bundled in higher tiers	EU SMB marketing + transactional bundle
SMTP.com	$25/mo (50K)	~$500/mo (Starter+)	Included in $80+ tiers	Mid-volume marketing relay
Blue Spirit Bulk SMTP	€89/mo (Starter)	~$99/mo (Starter)	2 IPs included	High-volume self-hosted (500K+ emails/mo)

Reading the table honestly: Amazon SES wins on pure cost if you have AWS expertise and are willing to handle deliverability tooling yourself. Postmark wins on transactional reliability for password resets and 2FA codes — their inbox placement on those workloads is genuinely better than anyone else's. SendGrid and Brevo win on bundled feature sets if you want SMTP plus a dashboard plus marketing tools in one place at low-to-mid volume. Blue Spirit wins at high volume (500K+ monthly) where the per-email pricing of SaaS providers exceeds dedicated infrastructure cost, especially with multiple IPs. The honest framing: choose by where your volume puts you on the cost curve, not by brand familiarity.

Cost honesty

Bulk SMTP cost at 1M emails/month — six providers compared.

The chart below normalises monthly cost across providers for a typical workload of 1 million emails per month with 2 dedicated IPs (or shared-pool equivalent). Numbers are 2026 retail pricing from the providers' public pricing pages.

Bulk SMTP monthly cost — 1M emails, 2 dedicated IPs equivalent (USD, 2026)

Direct cost only. Engineering time, deliverability tooling, and tier upgrades not included.

Monthly cost in USD across six bulk SMTP providers for 1M emails with 2 dedicated IPs
Categoría	Monthly cost USD (1M emails, 2 IPs equivalent)
SendGrid Pro (1M)	389
Mailgun Foundation+overage (1M)	530
Amazon SES (1M, 2 dedicated IPs)	150
Postmark (1M, 2 dedicated IPs)	1300
Brevo Business (1M)	449
Blue Spirit Bulk SMTP (1M)	99

SendGrid Pro: $89.95/mo for 100K + 9 × overage at $0.001/email = ~$389/mo total when extending to 1M. Mailgun Foundation: $35/mo for 50K + 950K overage at ~$0.50/1K = ~$530/mo. Amazon SES: 1M emails × $0.10/1K = $100 + 2 × $24.95 dedicated IP = ~$150/mo (engineering time and deliverability tooling not included). Postmark: dedicated transactional pricing scales linearly to ~$1,300/mo at 1M (Postmark optimised for transactional, not bulk marketing). Brevo Business: $449/mo for 1M emails with bundled marketing features. Blue Spirit Bulk SMTP Starter: €89/mo ≈ $99 for 250K emails sustainable; Growth at €249/mo ≈ $270/mo for 1M emails sustainable with 5 dedicated IPs. The chart shows the Starter tier as the entry point — the apples-to-apples comparison at 1M emails with 5 IPs is closer to $270/mo Growth, still well under SaaS competitors at that volume.

How IP allocation scales with sending volume.

Operators new to dedicated SMTP often underestimate the IP count needed at higher volumes. The chart below shows typical IP allocation by monthly volume tier, calibrated against real-world deliverability outcomes for marketing workloads.

IPs needed and plan tier required by monthly bulk SMTP volume

Typical allocation for marketing workloads with engaged audiences.

IPs and plan tier required across monthly bulk SMTP volume levels
Categoría	IPs needed (typical)	Plan tier required
100K/mo	1	1
500K/mo	2	1
1M/mo	2	2
5M/mo	4	2
10M/mo	6	3
50M/mo	12	3

IP allocation reflects operational sweet spot for marketing workloads — enough IPs to sustain volume without per-IP saturation, not so many that warmup becomes the bottleneck. Transactional workloads can sustain higher volume per IP because engagement signals are stronger; cold email workloads need lower volume per IP because complaint rates run higher. Plan tier numbers: 1 = Starter (€89/mo, 2 IPs included), 2 = Growth (€249/mo, 5 IPs), 3 = Scale (€749/mo, 10 IPs). Above 50M monthly we go custom with dedicated PowerMTA clusters.

What platforms we support

Any platform that speaks SMTP-AUTH will connect to our bulk SMTP. In practice that means every email marketing tool we know of: MailWizz, Acelle Mail, Interspire, Mautic, Mailster, Sendy, Klaviyo (via outbound custom SMTP), Brevo (formerly Sendinblue) for overflow, custom Laravel/Rails/Django apps, and the modern cold-email platforms (Instantly, Smartlead, Lemlist, Apollo, Reply.io, Woodpecker) when they allow an external SMTP endpoint. We also support transactional loads — password resets, invoices, order confirmations — when you prefer a dedicated infrastructure over a SaaS API.

Two platforms specifically to call out. WordPress sites using WP Mail SMTP, FluentSMTP, or similar plugins connect cleanly with our SMTP-AUTH endpoint and benefit from dedicated IPs immediately if your monthly transactional volume exceeds 50K. Custom Node.js, Python, Ruby, Go applications using standard SMTP libraries (nodemailer, smtplib, mail gem, gomail) work without modification — you provide the credentials and our endpoint, the library handles the rest. We have onboarded teams from "we just need bulk SMTP for our React app" to "we need PowerMTA powering our SaaS product" in the same week.

Use cases by industry — what bulk SMTP looks like in practice

Five operator profiles dominate our bulk SMTP client base. Each runs a slightly different configuration, calibrated to the workload pattern.

E-commerce platforms sending order confirmations, shipping updates, abandoned-cart reminders, and post-purchase marketing typically run a hybrid: transactional flows on a 2-IP dedicated pool with priority queueing (so password reset arrives in 5 seconds even when a 500K marketing batch is mid-send), marketing flows on a separate 3-5 IP pool with broader throttling tolerance. The infrastructure split prevents marketing complaint signals from bleeding into transactional reputation. Typical volume: 1-5M monthly emails split roughly 70% marketing, 30% transactional.

SaaS companies running product-driven email (signup confirmations, billing notifications, feature announcements, lifecycle nurture) often start on Postmark for transactional and bring marketing to dedicated bulk SMTP when their newsletter list crosses 100K subscribers. The hybrid pattern persists: critical operational mail stays on Postmark for its inbox-placement edge on transactional, marketing moves to dedicated SMTP where the volume economics work. Typical volume: 500K-3M monthly emails, with marketing growing faster than transactional as the user base scales.

Publishers and newsletter operators running 5-10 newsletter brands on a single MailWizz or Sendy installation point all of them at our SMTP endpoint. The advantage over running each newsletter through its own SaaS account: one consolidated set of dedicated IPs, one set of authentication records, one engineering relationship. Reputation is shared across newsletters but isolated from any other Blue Spirit client. Typical volume: 2-15M monthly emails depending on subscriber count, with concentrated weekly send patterns.

Cold-email agencies running outbound for multiple clients use bulk SMTP behind their MailWizz SaaS deployment for marketing-style outreach (warm prospects, post-event follow-ups, content drips). For pure cold outreach to net-new lists they use our Cold Email Infrastructure product instead — different architecture, different IP economics. Typical volume: variable, scaled by client count, with bursty patterns following client campaign cadences.

Internal corporate IT teams running a centralised SMTP relay for all corporate applications (HR systems, ERP notifications, monitoring alerts, internal newsletters) consolidate by pointing every internal mail-emitting system at one Blue Spirit endpoint. The cost-saving versus per-application SaaS subscriptions is real; the deliverability improvement on outbound corporate mail is also real because dedicated IPs avoid the shared-pool reputation drag of Office 365 SMTP submission. Typical volume: 200K-2M monthly, evenly distributed across the day.

How bulk SMTP is priced and why it is not € 19/month

The honest answer is that a genuinely dedicated SMTP with proper deliverability engineering has a lower cost bound, and it is not nineteen dollars. Running PowerMTA 6.0, keeping a dedicated IPv4 in good standing, monitoring blacklists, performing warm-ups, processing bounces and answering real tickets cost money every month. Providers advertising below € 50 for dedicated bulk SMTP are either shared-in-disguise, using throwaway IPs, or cutting corners you will eventually pay for. Our Starter plan at € 89 is as low as a properly operated dedicated bulk SMTP can go. The math: 2 dedicated IPv4 addresses leased + IPv4 reverse DNS + PowerMTA license amortised + bare-metal server share + monitoring + on-call rotation = approximately €70/mo cost-of-goods, plus margin to run the company. If you find a dedicated bulk SMTP at €30/mo, ask what corner is being cut — the answer is usually IP rotation, shared pools sold as dedicated, or absent monitoring.

What is included that competitors hide behind extras

PowerMTA license: the same enterprise MTA the major ESPs use. Included in every plan, configured for your sending profile.
Dedicated IPv4 addresses: 2 on Starter, 5 on Growth, 10 on Scale. With proper rDNS, registered with Postmaster Tools and SNDS, warmed before traffic.
SMTP-AUTH credentials: per-application username/password generation, source-IP allow-listing for additional security.
Authentication setup: SPF aligned with your From domain, DKIM 2048-bit with rotating selectors, DMARC published with reporting endpoint we monitor, MTA-STS, TLS-RPT.
Per-ISP throttling profiles: pre-tuned for Gmail, Microsoft, Yahoo, Apple, Yandex, regional ISPs. Adjusted continuously based on what is working.
Bounce processing: hard bounces, soft bounces, deferrals classified by PowerMTA, posted back to your application via webhook every 60 seconds.
FBL subscriptions: JMRP for Microsoft, Yahoo FBL, AOL FBL, all delivered to your suppression sync.
Postmaster Tools registration: Google, Microsoft SNDS, Yahoo Sender Hub registered to your domain on day one.
Monitoring: Prometheus metrics, Grafana dashboards (read-only access for you), alerts to our on-call rotation.
Updates: PowerMTA versions, OS patches, security updates — handled in low-traffic windows.

What is NOT included (on purpose)

We do not provide a marketing dashboard, list management, template editing, or campaign analytics — that is what your application is for, whether MailWizz, Acelle, or your custom app. We provide the bulk SMTP relay underneath. If you want the platform plus the relay bundled, MailWizz hosting is the bundled product.

We do not provide content writing, list cleaning, or copywriting services. The deliverability engineering only goes so far if your content has structural issues — clickbait subjects, broken HTML, image-only emails, missing unsubscribe — those problems land in spam regardless of how well the SMTP is tuned. We will tell you on the discovery call if your content is the actual problem; some prospects we redirect to fix that first.

We do not host adult content marketing to non-opt-in audiences, MLM/get-rich-quick schemes, sweepstakes traffic without genuine product, or any of the categories listed in our acceptable use policy. The PowerMTA back-end is isolated at the IP-pool level; one client's bad behavior cannot affect another client's IPs, but it can affect our ability to keep accepting clients in the same category. We filter on the discovery call.

Provisioning timeline — what the first month looks like

Day 1: payment received, server provisioned within 24-48 hours. PowerMTA installed and configured for your sending profile. SMTP-AUTH credentials generated and shared via secure channel. SPF/DKIM/DMARC DNS records generated for you to publish on your domain. We confirm DNS propagation before any traffic flows.

Days 2-7: IP warmup ramp begins. Initial traffic at 1,000-5,000 emails/IP/day, calibrated to your typical content profile. Per-ISP throttling profiles tuned based on early signals. Postmaster Tools and SNDS registration confirmed receiving data. We meet briefly mid-week to review early reputation signals (Gmail Postmaster, Microsoft SNDS, Yahoo Sender Hub). At this stage you can start moving small portions of your real campaign traffic, but we recommend keeping shared-pool fallback active for the first 14 days.

Days 8-21: ramp-up phase. Volume scales 1.5-2x per IP per day based on engagement signals. Bounce and complaint rates monitored closely. Any reputation alerts trigger temporary throttling and root-cause review. By day 21 most workloads have reached 50-70% of target capacity with stable reputation signals.

Days 22-30: full production. Volume reaches target capacity. Postmaster Tools showing High reputation in Gmail (or stable Medium for very new domains), Microsoft SNDS Green or Yellow, Yahoo Sender Hub Reputation Score above 70. Daily reporting active in Grafana, you have read-only access to dashboards. The shared-pool fallback can be decommissioned once you are comfortable with the dedicated infrastructure performance.

The 30-day timeline assumes a clean sender profile with established domain reputation. Senders with damaged domain reputation should plan for 60-90 days because the domain reputation rebuild adds 30-60 days to the IP-only timeline above. We diagnose this on the discovery call and set realistic expectations before you commit.

When this is not the right product

If your monthly volume is under 50,000 emails, pay-as-you-go relays (SendGrid Essentials, Brevo, Mailjet) are cheaper per email. If you need transactional-only delivery with no marketing content, a specialised provider like Postmark can beat us on inbox placement for that narrow workload. If you send fewer than 5 million emails a year, the total cost of dedicated infrastructure does not pay back. We are transparent about this because long-term fit matters more to us than a short quarter.

Three additional cases where we redirect prospects elsewhere on the discovery call. You need a marketing dashboard, list management, and templates as part of the SMTP service — that is what MailWizz hosting is for, where we bundle the platform with the SMTP. You are running cold email B2B as primary use case — Cold Email Infrastructure has different architecture optimized for mailbox rotation rather than IP-based sending. You need Microsoft 365 or Google Workspace integration for outbound — bulk SMTP does not replace those; it complements them for the bulk marketing workload while transactional and operational mail stays on the workspace platform.

The honest framing across all of these cases: dedicated bulk SMTP earns its place when monthly volume is above 500K and the application either supports custom SMTP or is custom-built. Below that volume threshold, SaaS providers' bundled feature sets and per-email pricing usually win. Above that threshold, dedicated SMTP wins on cost, control, and reputation isolation. The discovery call is where we figure out which side of the line your specific situation lands on, and we recommend accordingly even if the recommendation is "do not buy from us yet, come back when you cross the threshold". Long-term partnerships matter more to our business than a misaligned engagement that ends in 6 months.

Bulk email SMTP — frequently asked questions

What exactly is a "bulk email SMTP server"?

A dedicated server that exposes an authenticated SMTP relay (your credentials, your IPs) and has been tuned specifically for large-volume outbound: PowerMTA-style queueing, per-ISP throttling, bounce processing, feedback loops, DKIM and SPF alignment and the right OS-level tuning. Your application — whether it is MailWizz, Acelle, an in-house app or a cold email tool — points at that server instead of at Gmail or SES.

Is this the same as PowerMTA hosting?

Under the hood, yes — both are PowerMTA servers managed by us. We keep this page because people search for "bulk email SMTP" and "dedicated SMTP for mass email" independently of the word "PowerMTA". The plans are the same plans. If you already know you want PowerMTA specifically, the PowerMTA hosting page goes deeper into the engine itself.

Can I send cold email from a bulk SMTP server?

You can, with caveats. Cold email has stricter reputation dynamics and is better served by our dedicated Cold Email Infrastructure product, which layers pre-warmed mailboxes, isolated IP pools and specialised monitoring. If you already run outbound from a single IP and know what you are doing, yes, bulk SMTP will work. If you are new to cold email, talk to us first — choosing the wrong product makes the deliverability worse, not better.

What authentication do I configure?

SMTP-AUTH with a username/password we generate for you, plus source-IP whitelisting for extra security. DKIM and SPF are handled server-side; we generate the DNS records you need to publish. DMARC is started at p=none and tightened over time based on the reports. We monitor DMARC aggregate reports for you and surface alignment failures before they hurt deliverability.

What happens if I hit a blacklist?

First, we investigate: was it a single ISP complaint, a spamtrap hit, a public blacklist like Spamhaus? Depending on the cause, we either request delisting, rotate the IP within your pool, or recommend content/list changes. Spamhaus SBL is handled case by case because getting delisted there depends on behaviour, not on asking nicely. We never submit delisting requests until the underlying issue is fixed — premature delisting requests get you re-listed within days, sometimes with worse standing than before.

How does bulk SMTP compare to SendGrid, Mailgun, or Amazon SES?

Three different products at three price points. SendGrid bundles SMTP + dashboard + marketing tools at $19.95-$89.95/month for under 100K emails; their Pro tier ($89.95) is the SMTP-equivalent feature set. Mailgun starts at $35/month for 50K emails and scales up. Amazon SES is the cheapest per email ($0.10/1K emails) but charges $24.95/month per dedicated IP and gives you no marketing layer. Blue Spirit Bulk SMTP is the same dedicated PowerMTA infrastructure that operators built before SaaS providers existed — significantly cheaper at high volume because there is no per-email markup, but it requires you to bring your own application (MailWizz, custom app) or use ours. Use SaaS for low volume and convenience; use dedicated bulk SMTP for high volume and control.

How long does provisioning and warmup take?

Server provisioning is 24-48 hours from payment. Initial IP warmup is 14-30 days for fresh IPs, calibrated to your typical volume profile and content type. We start with low daily caps (1,000-5,000 emails/IP/day) and scale up based on engagement signals from Gmail Postmaster Tools, Microsoft SNDS, and our seed-list testing. Skipping warmup is the fastest way to land on Gmail "low reputation" or get throttled by Microsoft — we will not let you do it even if you push.

Do you handle the new bulk sender requirements (Google/Yahoo/Microsoft 2024-2025)?

Yes — every Bulk Email SMTP deployment is configured for the 2024-2025 enforcement out of the box: SPF aligned with the From domain, DKIM 2048-bit with rotating selectors, DMARC published with reporting endpoint we monitor, RFC 8058 one-click unsubscribe in headers, complaint rate kept below 0.1% through engagement-aware sending. Microsoft May 2025 enforcement (4.7.500-4.7.799 codes, 2K external recipients per 24h limit on Exchange Online) is also handled. When ISPs change requirements, we update server configurations as part of the service.

Can I use Blue Spirit Bulk SMTP with my existing Mailchimp/Klaviyo/HubSpot account?

Most major SaaS marketing platforms do not let you bring your own SMTP. Mailchimp, ActiveCampaign, Klaviyo, HubSpot and similar are closed-loop systems — they own the sending. Where this works is with platforms that explicitly support custom SMTP: MailWizz, Acelle, Interspire, Mautic, Sendy, custom apps, transactional services like Postmark for fallback. If you are evaluating a switch to a self-hosted platform precisely to gain SMTP flexibility, we help with the migration as part of MailWizz hosting onboarding.

Send bulk email from infrastructure that was actually built for it.

Tell us your monthly volume target, current setup (SaaS provider, DIY, mixed), and one operational pain you would like solved. We respond with a specific recommendation — plan tier, migration timeline, hybrid setup if applicable.

Request a quote Chat on WhatsApp