SMTP2GO plugin for WordPress

SMTP2GO plugin for WordPress

Install the official SMTP2GO plugin if the site has already decided on SMTP2GO and wants the delivery stats visible inside wp-admin. Install WP Mail SMTP with its built-in SMTP2GO mailer if the site is likely to run more than one provider, or wants the Pro tier’s logging, fallback, and per-sender routing. Both paths reach SMTP2GO through the same HTTP API and authenticate with the same key; the choice is about what the plugin does around the send, not about how the send itself works.

For the case for or against SMTP2GO as the sending service (the 1,000-a-month free tier, the 200-per-day cap that turns into a real ceiling on busy days, the Starter plan crossover), start at the SMTP2GO review. This page is the setup walk-through. It assumes the decision to use SMTP2GO has already been made.

Which plugin to install

The six plugins below reach SMTP2GO through its API, and two are the answer for most sites.

SMTP2GO (the official plugin) is the fastest path to the Stats tab inside wp-admin. One API key, one region setting, one from-address; no host or port to configure because the plugin talks to SMTP2GO’s HTTP API rather than SMTP. The Stats tab pulls delivery, bounce, open, and click counts from SMTP2GO’s reporting API for the current billing period, which is the one feature no generic mailer plugin ships. Pick it when SMTP2GO is the final decision and having provider-side delivery numbers visible without a second browser tab is worth the loss of plugin-side logging.

WP Mail SMTP with its SMTP2GO mailer is the recommended path for sites that want a general-purpose mailer plugin around the send. WP Mail SMTP ships a dedicated SMTP2GO option in its mailer picker, uses the same API key as the official plugin, and adds the surrounding features the official plugin deliberately omits: a setup wizard and, on the Pro tier, email logging, backup connections and smart routing. Pick it when the site might change providers later, or when the operator wants the full mailer-plugin feature set from day one.

FluentSMTP ships a dedicated SMTP2GO connection that takes the same API key, and its generic-SMTP mode reaches mail.smtp2go.com with SMTP credentials from the SMTP2GO dashboard. FluentSMTP is free and open-source with no upsell path, and its per-address routing rules are cleaner than WP Mail SMTP’s free tier. Pick it when the site runs multiple senders and needs per-address routing without paying for WP Mail SMTP Pro.

Post SMTP offers the same two routes: an SMTP2GO mailer on the API key, or generic-SMTP mode to mail.smtp2go.com. Its differentiator is real-time failure notifications (Chrome push, Slack, Teams, and SMS on the paid tier); if a bounced order confirmation needs to page an operator within minutes, Post SMTP is the plugin.

Easy WP SMTP and Meow Mailer also ship SMTP2GO mailers that take the same API key.

For the plugin-by-plugin comparison in the general case (not SMTP2GO-specific), see best WordPress SMTP plugins.

Before touching WordPress

SMTP2GO requires verified senders. A sender can be a whole domain or a single email address, and a domain is verified with three CNAME records that cover SPF, DKIM and link tracking. A new account also starts on a review quota of 1,000 emails a day, and mail over that quota waits in a queue. Two things sit upstream of the WordPress install: a verified sending domain, and an API key scoped to it.

Verify the sending domain

Log in to the SMTP2GO dashboard, then Sending > Verified Senders > Sender domains > Add sender domain. Enter the domain the WordPress site sends From:, meaning example.com, not mail.example.com. SMTP2GO returns three CNAME records to publish, each with a hostname shown in your dashboard:

Record Hostname Points at Covers
Return path em<number>.example.com return.smtp2go.net SPF
DKIM s<number>._domainkey.example.com dkim.smtp2go.net DKIM
Tracking link.example.com (editable) track.smtp2go.net HTTPS for tracked links

Copy the hostnames from the dashboard rather than typing them; use the values shown for your domain. On Cloudflare, set each record to DNS only (grey cloud) and turn off CNAME flattening, or the records will not verify.

Leave the domain’s SPF record alone. SMTP2GO rewrites each message’s envelope sender to an address on the return-path subdomain, receivers check SPF against that subdomain, and the CNAME hands the check to SMTP2GO’s own SPF record. Its SPF, DKIM and DMARC overview says the existing SPF record does not need updating. Because the return-path subdomain sits under your domain, SPF still aligns for DMARC under its default relaxed alignment. The one exception is SMTP2GO’s Maintain Return-path option, for the few recipient domains (old email-to-fax and email-to-SMS gateways) that cannot handle a rewritten return path. Mail to those domains goes out with your own address as the envelope sender, so your SPF record needs include:spf.smtp2go.com. If the domain already has an SPF record, add the include to it rather than publishing a second one: two SPF records at the same name are a permanent error under RFC 7208. The SPF merger folds the include into an existing string and counts the DNS lookups against the ten-lookup ceiling.

Return to the SMTP2GO dashboard and click Verify. The dashboard reports each record’s status, and the domain is ready to send when it shows as Verified. Most DNS changes are live within minutes; SMTP2GO says some providers take up to an hour.

DMARC is not SMTP2GO-specific but is required for domains sending more than 5,000 messages per day to Gmail or Yahoo under their 2024 bulk-sender rules. Publish _dmarc.example.com as TXT v=DMARC1; p=none; rua=mailto:[email protected] as a safe starting point; tighten to p=quarantine or p=reject once reports show no legitimate mail failing alignment. The bulk sender authentication checklist has the full order of operations.

Generate an API key and pick a region

In the SMTP2GO dashboard, Sending > API Keys > Add API Key. Give the key a description that identifies the WordPress site. The permissions default to Full Access, which is what the mailer plugins need; a key scoped narrower (send-only, no stats read) will not populate the Stats tab in the official plugin. Copy the generated key; SMTP2GO displays the value once, at creation.

A site with a data-residency requirement (an EU-only policy, an AU-only contract) has two things to get right, and the account comes first. SMTP2GO’s dashboard footer identifies the data centre where it says mail is sent and data is stored and processed. Its documentation does not say whether an API request accepted outside the account’s data centre changes where that message is processed. SMTP2GO places sign-ups from the US, Europe and Oceania in the matching data centre automatically. To check, read the footer at the bottom left of the SMTP2GO dashboard, which says Hosted in the USA, Hosted in the EU or Hosted in Australia. Moving an account to another data centre goes through a ticket to SMTP2GO support.

The second is the endpoint. SMTP2GO operates regional API endpoints in the US, EU, and AU. The global endpoint (api.smtp2go.com) picks whichever is closer to the request, which is the default and what most WordPress sites want. That request comes from the web server, so a site on a US host reaches the US endpoint wherever the account sits. A site with a residency requirement should confirm with SMTP2GO that its account and chosen endpoint meet that requirement. The choice is the API Region setting in the official plugin (v1.16.0 and later); older installs fall back to the global endpoint.

Installing and configuring the official SMTP2GO plugin

The plugin install is standard: Plugins > Add New > search SMTP2GO > Install > Activate. Ignore any competing mailer plugin still active on the site; SMTP2GO detects other mailers overriding wp_mail() at once and warns in the admin, because two mailers active at once is the most common cause of an SMTP2GO install appearing to do nothing.

In the SMTP2GO settings screen, the Settings tab holds four fields worth setting deliberately. Paste the SMTP2GO API key generated earlier into API Key; when constants are preferred (multi-environment deployments, credentials outside the database), set SMTP2GO_USE_CONSTANTS to true in wp-config.php and define SMTP2GO_API_KEY there instead. Leave API Region on Default unless you have a reason to choose a regional endpoint; for a data-residency requirement, confirm the account and endpoint requirements with SMTP2GO. Set From Email to an address at the domain verified with SMTP2GO and check Force From Email, which stops plugins that set their own from-address (WooCommerce order emails, some form plugins) from overriding it. Set From Name to the site or brand name and check Force From Name for the same reason.

Save. The plugin does not run a validate-connection check on save; the Test tab is the confirmation.

Under the Test tab, send a test message to an address you can read. The plugin round-trips the send through SMTP2GO’s HTTP API and reports the API response in the admin. A 200 response with a success payload confirms the API key, region, and sender identity are wired up correctly; verify the message actually arrived at the destination before treating the setup as done, and open the message headers to confirm Authentication-Results shows dkim=pass for the selector shown in your SMTP2GO dashboard and spf=pass for the sending IP. If either fails, the DNS records did not propagate or were entered incorrectly at the DNS host; return to the SMTP2GO dashboard’s sender domain page and re-check.

For WP Mail SMTP with the built-in SMTP2GO mailer, the equivalent settings live under WP Mail SMTP > Settings > Mailer > SMTP2GO. Paste the same API key, set the from-address, and use Force From Email. WP Mail SMTP’s Email Test tab handles the test send. This mailer has no region setting and always calls the global endpoint, as does Post SMTP’s SMTP2GO mailer; FluentSMTP’s mailer has a region choice. For FluentSMTP or Post SMTP over generic SMTP, the settings are Host mail.smtp2go.com, Port 2525 (or 587), Encryption STARTTLS, Authentication PLAIN or LOGIN, Username and Password from the SMTP2GO dashboard’s SMTP Users section (SMTP credentials are separate from API keys). To pin a region over SMTP, replace the host with mail-us.smtp2go.com, mail-eu2.smtp2go.com (EU only), mail-eu.smtp2go.com (EU and UK) or mail-au.smtp2go.com; in WP Mail SMTP, that means its Other SMTP mailer.

Sending the first test and reading the failure

The two error patterns worth naming.

Sender not verified or the API returns a domain-related error. The from-address is at a domain SMTP2GO has not verified, or the DKIM CNAMEs have not propagated. Check the SMTP2GO dashboard’s sender domain page shows all records verified for the exact domain in the from-address. [email protected] is a different domain to [email protected] under DKIM alignment rules; verify the domain the site actually sends from, not the domain the site is hosted at.

Invalid API key or a 401 from the API. The key was regenerated in the dashboard, was scoped narrower than Full Access, or belongs to a different SMTP2GO account than the one holding the verified sender domain. Regenerate a full-access key against the account that owns the sender domain and paste that one. The plugin encrypts the key at rest in the WordPress database (v1.10.0 and later), so pasting the same key twice by hand is safe.

The SMTP2GO Activity page shows every send in near-real-time with its delivery status and any bounce reason. Point it at the last hour and the test sends appear near the top; a message that shows Delivered in the activity log but has not arrived at the destination is a receiver-side delivery decision, not an SMTP2GO problem, and the message headers (Authentication-Results, Received-SPF) are where the reason lives.

SMTP2GO-specific things to know

The free tier has a hard daily cap, not just a monthly one. The free plan allows 1,000 messages per month, but the plan also enforces a 200-messages-per-day ceiling. A site that runs a Black Friday campaign, a WooCommerce sale, or a bulk password reset can hit the daily cap and see later sends rejected even with the monthly allowance still unspent. Sites with any traffic spike pattern should size the plan against the peak day, not the monthly total.

Reporting retention is short on Free and Starter. The Activity log retains 5 days on Free and 30 days on Starter. Sites that need longer retention should either mirror sends to a WordPress email log (Check & Log Email, Log Emails, or WP Mail SMTP’s own log tier) in parallel, or move to Professional for extended retention.

The region setting does not move the account. API Region selects the endpoint the plugin calls. The dashboard footer still identifies the account’s assigned data centre; SMTP2GO does not document what happens to mail accepted outside that centre.

The dedicated IP tier starts at Professional. SMTP2GO’s dedicated IP offering is bundled into the Professional plan ($75/month for 100,000 messages), not sold as an add-on. A site on Starter cannot buy a dedicated IP without upgrading the plan. As with any provider, a dedicated IP is worth the money only when the monthly volume clears the roughly 50,000-message threshold below which the IP has too little traffic to build its own reputation.

Windows and IIS are unsupported. SMTP2GO’s official plugin explicitly advises against Windows/IIS hosting. Sites on that stack should use FluentSMTP or WP Mail SMTP with the SMTP2GO mailer instead, both of which handle Windows PHP without issue.

When another provider fits better

If the WordPress site is already running Mailchimp for marketing and wants one bill, Mailchimp Transactional may fit the operational picture better even though it is priced higher. If the site sends fewer than 300 messages per day and can accept a slower reporting dashboard, Brevo‘s day-based free tier is the alternative shape. Above about 100,000 messages per month, Postmark, Amazon SES, and Mailgun all price per-send below SMTP2GO’s block model. The SMTP cost calculator runs the crossover math against a site’s actual monthly send volume.

When you are ready to go further:

Corrections
  • 2026-11-12: an earlier version said to add include:spfa.smtp2go.com to the domain’s SPF record, or to publish v=spf1 include:spfa.smtp2go.com -all on a domain with none. That hostname carries no SPF record, so any SPF check that reaches the include ends in a permanent error. SMTP2GO verifies a domain with three CNAME records (return path, one DKIM record and link tracking) and needs no SPF change. The earlier version also described two DKIM records under fixed s1 and s2 selectors; SMTP2GO issues one DKIM record, with the selector shown in the dashboard.
  • 2026-11-05: an earlier version said SMTP2GO accepts sends from an unverified domain during a demo period. SMTP2GO requires a verified sender.
  • 2026-11-05: an earlier version said FluentSMTP has no SMTP2GO mailer, that Post SMTP reaches SMTP2GO only over generic SMTP, and that WP Mail SMTP’s email logging is free. FluentSMTP and Post SMTP both ship a dedicated mailer, and the log is a Pro feature.
  • 2026-11-05: an earlier version said the WP mail config generator returned a paste block and a define() block for this plugin. The generator does not offer this plugin as a delivery method.
  • 2026-11-05: an earlier version said picking an API region meets a data-residency requirement, that the EU endpoint decides the outbound IPs, and that WP Mail SMTP’s SMTP2GO mailer has a region setting. SMTP2GO’s dashboard identifies the account’s data centre, but its documentation does not explain how an API message accepted outside that centre is processed. WP Mail SMTP’s SMTP2GO mailer has no region setting.