SMTP2GO: multi-region sending from New Zealand, EU and USA

What is SMTP2GO?

SMTP2GO is a New Zealand mail-sending service, founded in 2008 in Christchurch and with multi-region routing in USA and EU since 2018. Unlike Postmark (US-centric) or Brevo (EU-centric), SMTP2GO offers a pragmatic middle ground: one account, multiple geographic regions, simple UI, clear price ladder. The platform positions itself not as "market leader" or "premium tool" but as a reliable working solution for smaller and medium setups that must be productive without a large learning curve.

As of May 2026, SMTP2GO operates data centers in three regions: Auckland (NZ home, headquarters), Sydney (AU), Dallas (US east-coast proxy), Amsterdam (EU main region), Frankfurt (EU backup). The Amsterdam EU region has been productive since 2020 and is SOC-2 Type-2 certified. DPA per GDPR is automatically available in the dashboard.

Noteworthy is the multi-region routing logic: one account can send mails over multiple regions, automatically routed based on recipient domain (e.g. US recipients via US region, EU recipients via EU region). This lowers latency and respects data-residency preferences. For a Swiss SME with clients in CH, DE, AT, FR, this is interesting -- the data path stays in EU without manually configuring every send call.

Pricing (May 2026): Free 1,000 mails/month (generous, no daily limits), Starter USD 15/month for 10,000 mails, Pro USD 35/month for 40,000 mails, Business USD 90/month for 200,000 mails. Dedicated IP optional from USD 30/month. All plans incl. inbound webhooks, reporting, SMTP and API sending.

Why it matters for Swiss SMEs

SMTP2GO is the right choice in three specific cases: pragmatic setup without API depth, multi-region recipients, and a free tier with a productive threshold.

Pragmatic setup: SMTP2GO was built for teams without dedicated DevOps. The UI is clearly structured (5 main areas: Dashboard, Activity, Settings, Reports, Webhooks), onboarding walks through DKIM/SPF in 10 minutes, the API doc section sits on one page. Whoever finds Brevo too marketing-heavy and Postmark "only for specialists" often lands at SMTP2GO as a good compromise.

Multi-region routing: For a Swiss firm with clients in CH, DE, AT, EU sub-recipients, FR, IT: SMTP2GO routes automatically over the EU region (Amsterdam) based on domain pattern. The data path stays in EU without API configuration effort. Also for SMEs with global recipients (e.g. expat Swiss in NZ/AU): native region choice saves latency.

Free tier 1,000 mails/month: Compared to Postmark Free (100/month, test only) or Mailgun (no free tier), SMTP2GO is usable for small production at 1,000/month. An internal notification tool, a sandbox application, or a small client workflow runs free -- without artificial daily limits.

The compliance corridor for Swiss fiduciaries: SMTP2GO has an EU region in Amsterdam (GDPR/revFADP compliant). The parent group law is New Zealand, which is more unusual for disputes than Swiss or EU law. A TIA must be thought through more strictly than at Brevo or Mailjet, because NZ is not an EU member and the data protection pact is structured differently. For professional-secrecy cases Infomaniak is the better pick. For normal SME workloads without StGB Art. 321 ties, SMTP2GO is a solid option.

How it works

SMTP2GO exposes two send paths: classical SMTP relay and HTTPS API. SDKs are officially available in Node.js, Python, PHP -- more via community.

SMTP relay: Host `mail.smtp2go.com` (global auto-routing) or regional `mail-eu.smtp2go.com` (EU only), port 587 STARTTLS, 465 SMTPS or 2525 STARTTLS. User: the username component generated in the dashboard. Pass: SMTP password.

HTTPS API: Endpoint `https://api.smtp2go.com/v3/email/send`, header `X-Smtp2go-Api-Key`. cURL example:

``` curl -X POST "https://api.smtp2go.com/v3/email/send" \ -H "Content-Type: application/json" \ -d '{ "api_key": "<SMTP2GO_API_KEY>", "sender": "Firm Müller <invoice@firm-müller.ch>", "to": ["[email protected]"], "subject": "Dunning No. 2 - Invoice 2026-104", "text_body": "Dear Mrs Berger, ...", "custom_headers": [{ "header": "X-Region-Pref", "value": "eu" }] }' ```

The endpoint `mail-eu.smtp2go.com` forces EU-region sending, regardless of recipient domain pattern. Recommendation for Swiss SMEs with client data: always use the EU endpoint.

DNS setup: Three DNS records per sender domain: SPF (`v=spf1 include:spf.smtp2go.com ~all`), DKIM (TXT, selector `smtp2go._domainkey.<domain>`, platform-generated), and a return-path CNAME (`em.<domain>` pointing to `track.smtp2go.com`). DMARC recommended `v=DMARC1; p=quarantine; pct=100`.

Webhooks: In the dashboard under "Webhooks", enter endpoint, select event types (sent, delivered, bounced, opened, clicked, unsubscribed, complaint, dropped). HMAC-SHA256 signature in header `X-Smtp2go-Signature`. Retries: 3 attempts over 6 hours.

Inbound routing: SMTP2GO supports inbound streams since 2023: point an MX record subdomain at `mx.smtp2go.com`, then define regex patterns in the dashboard (e.g. `support+.*@<domain>`) with webhook actions. Very similar to the Mailgun Routes system.

Test and monitoring: Dashboard yields a real-time "Activity" feed, "Reports" module with filter per day/sender/domain/status. "Deliverability Insights" module (Pro plan) offers recommendations when inbox rate drops -- e.g. "your DMARC is missing", "spam complaints rising, check content".

SMTP2GO setup in 5 steps

1. 01Create an SMTP2GO account (no credit-card requirement on free plan), add sender domain.
2. 02Choose EU region: set SMTP host to `mail-eu.smtp2go.com` or use API header `X-Region-Pref: eu`.
3. 03Set three DNS records (SPF, DKIM selector, return-path CNAME) in Cloudflare as DNS-only, wait 24h for verification.
4. 04DMARC initially p=none for 14 days, then raise to quarantine. Set bounce and complaint webhooks with HMAC verification.
5. 05Generate API key in dashboard, store in .env (SMTP2GO_API_KEY), send three test mails to Gmail/Outlook/Bluewin, verify Mail-Tester.com 10/10.

When SMTP2GO fits

SMTP2GO is the right choice when (a) a pragmatic setup without large DevOps investment is desired, (b) multi-region recipients across EU and global benefit from the routing feature, or (c) the free tier with 1,000 mails/month suffices for sandbox or small production.

Concrete cases: A Swiss SME with 20,000 mails/month (login notifications, newsletter, order confirmations) -- SMTP2GO Pro USD 35 is a clean middle ground between Brevo and Mailgun. A platform with recipients in CH/DE/AT/FR/USA -- automatic routing over EU region saves manual configuration. An internal tool with 800 notifications/month -- free tier covers it completely, without CC requirement.

For DACH setups: mandatorily use `mail-eu.smtp2go.com` as SMTP host or set header `X-Region-Pref: eu`. Check DPA status in the dashboard, read the sub-processor list. Step DMARC cleanly, inbound streams only if needed.

When not to use

SMTP2GO is the wrong choice when (a) professional secrecy per Art. 321 SCC is involved -- the NZ parent legal structure makes TIA and compliance review heavier than Infomaniak or Brevo, (b) maximum deliverability for legally relevant dunning mail is required -- Postmark beats SMTP2GO by 4 points (99 vs 95 percent), or (c) volume exceeds 500,000 mails per month -- from there Amazon SES is clearly more economical.

More pitfalls: using the standard endpoint `mail.smtp2go.com` (global auto-routing) instead of `mail-eu.smtp2go.com` -- the data path may route via USA, raising GDPR/revFADP issues. Exceeding the free-tier 1,000/month without upgrade -- further mails are 429 rejected. Forgetting to set the DKIM selector -- inbox rate breaks to 75-80 percent because Gmail/Outlook demand DMARC alignment. Activating inbound routing without MX setup -- patterns configured but no mail arrives.

Trade-offs

FAQ

Related topics

Sources

1. SMTP2GO Pricing 2026 · 2026-05
2. SMTP2GO EU Region Documentation · 2026-04
3. SMTP2GO API v3 Reference · 2026-03
4. EmailToolTester -- Multi-Region Email Providers 2026 · 2026-04