Description
Your Password Reset Emails Are Probably Landing in Spam Right Now
Here’s the problem: WordPress ships email through your server’s built-in mail() function, and mail servers have learned to distrust it. No authentication, no reputation, no verified sending domain behind it — just a raw handoff that spam filters flag on sight. That means the membership confirmation email your new member is waiting for, the invoice your customer needs for their records, or the password reset link someone is refreshing their inbox for, might never show up. Paid Memberships Pro – SMTP exists to fix exactly that. It reroutes your site’s transactional email through a mail provider that receiving servers actually trust, so those messages get delivered instead of disappearing.
The plugin connects your WordPress site to a generic SMTP server or one of six transactional email APIs: SendGrid, Mailgun, Postmark, Brevo, Resend, or MailerSend. Pick a provider, enter your credentials, send a test message, and you’re done. No code, no server-side configuration files to edit by hand.
The Standout Capability: Backup Failover for API Connectors
Most SMTP plugins give you one connection and hope it holds. Paid Memberships Pro – SMTP lets you configure a second, backup provider that takes over automatically if your primary API connector has an outage or rejects a send. If SendGrid has a bad afternoon, your backup — say, Postmark or Brevo — picks up the slack without you touching a setting. Membership renewal receipts and account emails keep moving even when one provider stumbles.
There’s a catch worth understanding clearly, because it affects how you should set things up. Automatic backup failover only applies when your primary provider is one of the API connectors. If your primary provider is Custom SMTP, WordPress sends through PHPMailer directly, and the backup provider you configured sits unused. So if failover matters to your setup, choose an API connector as your primary and treat Custom SMTP as a fallback path only when that constraint works for your situation.
Complete Feature Set
Beyond the standout failover capability, the plugin covers the ground you’d expect from a serious mail-routing tool, plus a few details that matter specifically to Paid Memberships Pro sites.
- Generic SMTP support for any provider that accepts host, port, encryption, and authentication settings — including Google Workspace and Gmail with an app password.
- Six API-based connectors: SendGrid, Mailgun, Postmark, Brevo, Resend, and MailerSend, each authenticated directly through its API rather than SMTP credentials.
- Optional backup provider support for API connectors, so a second service steps in if the first one fails.
- Sandbox mode, which stops all outgoing email cold — built for staging and development sites where the last thing you need is test orders emailing real customers.
- Compatibility with Paid Memberships Pro email logging, meaning the logging you already rely on inside PMPro keeps working without modification.
- A built-in test email tool with connection diagnostics, right on the settings page, so you can confirm delivery before flipping the switch on a live site.
One detail that trips people up with other SMTP plugins: sender identity. Paid Memberships Pro – SMTP does not touch your from name or from email. Those stay managed by WordPress and by Paid Memberships Pro. The Connection tab shows a “Current Sender” field that reflects whatever is already configured — it’s a mirror, not a control. If you need to change the sender name or address, that happens on the Paid Memberships Pro Email Settings page, or under WordPress Settings > General if PMPro isn’t active. The Current Sender field links straight there, so you’re not hunting through menus.
Email formatting is preserved too. Whether you route mail through Custom SMTP via PHPMailer or through one of the API connectors, PMPro’s email formatting — including the optional email_header and email_footer theme templates — applies the same way on both paths. Switching providers doesn’t mean redesigning your emails.
How It Fits Your Workflow
Setup follows a straightforward sequence. On the Connection tab, you select one provider as your primary sender, or you choose “None (WordPress default)” if you want to leave WordPress email untouched for now. You can store credentials for more than one provider at a time and switch between them whenever you want — useful if you’re testing a new provider without ripping out the old configuration first.
For Custom SMTP, you’ll need a host, port, username, and password, plus whatever encryption setting your provider specifies. Google Workspace and Gmail both work through this connector, but only with an app password — a 16-character password you generate inside your Google account specifically for this connection. Your regular Google password won’t authenticate; Google blocks that on purpose for third-party apps.
Before you point production traffic through a new provider, most transactional email services require your from email address to be on a domain you’ve verified with them. Send from an unverified domain and delivery can fail outright, or land in spam anyway, which defeats the purpose. Verify your sending domain in the provider’s dashboard first, and use a real address on your own domain rather than a free Gmail or Yahoo address. Pairing that verified domain with correct SPF, DKIM, and DMARC records gets you the best deliverability results the plugin can offer — the plugin routes the mail, but your domain’s authentication records are what convince receiving servers to trust it.
Once credentials are saved, send a test email from the settings page. It’s a small step but it saves you from finding out your password reset emails are broken only after a member complains.
Ideal Use Cases
Membership sites running Paid Memberships Pro are the obvious fit, since this Add On requires PMPro installed and activated to work. Think about a fitness membership site sending renewal receipts, cancellation confirmations, and password resets daily — if even a fraction of those land in spam, that’s a support headache and a trust problem with members who think their payment didn’t go through. Routing those through SendGrid or Postmark closes that gap.
Agencies managing several PMPro client sites benefit from the multi-provider flexibility. You might run Custom SMTP through Google Workspace for a client, and an API connector like Brevo for another, all configured through the same plugin interface without needing separate tools per site.
Development and staging environments get real value from sandbox mode. Anyone who has accidentally emailed a client’s live member list from a staging server during testing knows why this matters. Flip on sandbox mode, and outgoing email stops entirely until you’re ready to go live.
Sites with strict deliverability needs — courses with time-sensitive login credentials, subscription boxes with shipping confirmations, or nonprofits sending donation receipts — benefit from the backup provider setup. If uptime on transactional email is business-critical, configuring a primary and backup API connector adds a layer of resilience a single-provider setup can’t match.
It’s worth being clear about what this plugin is not for. This Add On handles transactional email: system messages like receipts, account notifications, and password resets. If you’re planning newsletters or broadcast campaigns, that’s a job for a dedicated email marketing system, not this plugin.
Frequently Asked Questions
Can I connect Gmail or Google Workspace to this plugin?
Yes. Use the Custom SMTP connector with your Google email as the username, port 587, TLS encryption, and authentication enabled. The password field needs a Google app password, not your regular account password — you generate that 16-character app password inside your Google account settings specifically for this connection.
Will this replace the email logging Paid Memberships Pro already does?
No, and it isn’t meant to. PMPro core continues handling email logging on its own, and Paid Memberships Pro – SMTP simply works alongside it. You keep the logging behavior you already have, whichever provider you route mail through.
Do emails look different depending on which provider I use?
No. PMPro’s email formatting, including the optional email_header and email_footer theme templates, applies consistently whether you’re sending through Custom SMTP via PHPMailer or through an API connector like SendGrid or Postmark. Switching providers won’t change how your emails are styled.
Does the backup provider work no matter which primary provider I choose?
Not quite — backup failover only kicks in when your primary provider is one of the API connectors. If Custom SMTP is set as primary, WordPress sends through PHPMailer directly and the backup provider configured on the Connection tab doesn’t get used. Keep that in mind when deciding which provider to set as primary.
Is this plugin licensed under the GPL?
Yes, the Paid Memberships Pro – SMTP WordPress plugin is distributed under the GPL license, consistent with the rest of the Paid Memberships Pro plugin family. Version 0.1.1 is the current release covered in this documentation.
