What is SMTPPai?

If your WordPress site sends password resets, form notifications, or store order emails, those messages have to leave your server somehow. By default, WordPress often relies on PHP’s built-in mail() function. On many hosts that path is unreliable — messages go to spam, never leave the server, or get blocked without a clear error.

I built SMTPPai so you can send WordPress mail through real email services instead: native APIs (Amazon SES, Mailgun, Postmark, and more) or classic SMTP, including Google Workplace/Gmail and Microsoft 365/Outlook. You keep one free plugin, add as many connections as you need, and see what actually happened in the Email Log.

What SMTPPai does for you

  • Reliable delivery — routes wp_mail() through a provider you control, not opaque PHP mail.
  • Many providers in one place — Amazon SES, Mailgun, Postmark, Brevo, Resend, SendGrid (by Twilio), MailerSend, Mailjet, Elastic Email, Mailchimp Transactional (Mandrill), SparkPost, Zepto Mail, SMTP2GO, SMTP.com, Google Workplace/Gmail, Microsoft 365/Outlook, and Other SMTP.
  • Unlimited connections — name them for WordPress, WooCommerce, or any purpose you like.
  • Specify Connections — use one connection for everything, or separate connections for WordPress and WooCommerce mail.
  • Backup Connection — if the primary send fails, SMTPPai can retry once through a fallback connection.
  • Email Log — see sent and failed messages, open details, and retry failed sends when it makes sense.
  • Safer secrets — store keys encrypted in the database, or keep them in wp-config.php.

Who this documentation is for

These guides are written for site owners and freelancers who may not live in developer tools every day. Each connection guide walks through where to click, what to copy, and what to paste — including the exact labels you see in SMTPPai.

What SMTPPai is not

  • It is not a newsletter builder. If you use MailPai, SMTPPai can sit under that menu and help deliver MailPai-related routes when MailPai is present — but SMTPPai itself is the mailer.
  • It does not claim paid “Pro” feature locks. What you see in the plugin is what you get.
  • Emails that include attachments are not sent through SMTPPai’s custom mail path; WordPress falls back to the default mailer for those messages. Keep that in mind for plugins that attach files.

Suggested reading order

  1. Install SMTPPai
  2. Configure SMTPPai (full tour of every tab)
  3. Add your first connection
  4. The matching guide under Connections Setup for your provider
  5. Send a test email
  6. Optionally Specify Connections and Backup Connection

Why SMTPPai is useful: once a connection is working, everyday WordPress email — resets, form alerts, shop notices — goes through a provider you can monitor, with a log and an optional backup if that provider has a bad day.

Did this article help you?

Your vote shapes what we improve next.

Leave a comment