Frumbik

WordPress uses the PHP <code>mail()</code> function by default, which often results in emails being marked as spam or not delivered at all. Frumbik SMTP replaces the default mail function with authenticated SMTP or API-based email delivery through your chosen provider.
Connect Gmail, SendGrid, Amazon SES, or any SMTP server — and all emails WordPress sends will be properly authenticated, encrypted, and delivered.
<h4>Key Features</h4>
Frumbik SMTP provides the following capabilities, all included in the free version:
🔄 Automatic Failover — If your primary provider goes down, emails automatically route to your backup provider.
📊 Dashboard — Real-time delivery stats, success rates, and charts. See what is happening with your emails at a glance.
📋 Complete Email Log — Every email logged with status, timestamps, headers, and source plugin. Search, filter, resend, or export — all from one screen.
🔐 Strong Security — AES-256-CBC encryption for all credentials. Security scoring dashboard with actionable recommendations.
⚡ Background Queue — High-traffic site? Queue emails for async delivery so your pages load fast while emails send in the background.
🎯 Smart Routing — Route WooCommerce emails through SendGrid, contact forms through Mailgun, and newsletters through Amazon SES — all automatically.
<h4>9 Providers, One Plugin</h4>
Connect to any email service without installing separate add-ons:
<ul>
<li>Other SMTP — Any SMTP server (Gmail, Outlook, Yahoo, your hosting, custom servers)</li>
<li>SendGrid — Transactional email API by Twilio</li>
<li>Mailgun — Email API by Sinch</li>
<li>Postmark — Transactional email delivery by ActiveCampaign</li>
<li>Brevo (formerly Sendinblue) — Marketing and transactional email</li>
<li>SparkPost — Email delivery by MessageBird</li>
<li>Amazon SES — AWS Simple Email Service (v2 API with Signature v4)</li>
<li>Microsoft 365 / Outlook — Microsoft Graph API with OAuth 2.0</li>
<li>Gmail API — Google Gmail API with OAuth 2.0</li>
</ul>
All providers are included in the plugin.
<h4>Core Features</h4>
📨 Reliable Email Delivery
<ul>
<li>Replace WordPress’s unreliable <code>wp_mail()</code> with authenticated SMTP or native API connections</li>
<li>Supports TLS and SSL encryption protocols</li>
<li>Proper SPF, DKIM, and DMARC alignment through your provider</li>
<li>Works with any WordPress theme, plugin, or page builder</li>
</ul>
📋 Comprehensive Email Logging
<ul>
<li>Every outgoing email logged automatically — sent, failed, or queued</li>
<li>Full details: recipients, subject, body, headers, attachments, timestamps</li>
<li>Automatic source detection — know which plugin triggered each email</li>
<li>One-click resend for failed or bounced emails</li>
<li>CSV export with advanced search and filtering</li>
<li>Configurable log retention (auto-cleanup old logs)</li>
</ul>
🔄 Multi-Connection & Failover
<ul>
<li>Configure multiple mail providers simultaneously</li>
<li>Automatic failover — if Provider A fails, Provider B takes over instantly</li>
<li>No manual intervention needed. No lost emails during outages.</li>
<li>Connection health monitoring with success rate tracking</li>
</ul>
🎯 Smart Routing Rules
<ul>
<li>Route emails to different providers based on conditions:
<ul>
<li>Recipient email address or domain</li>
<li>Email subject containing specific keywords</li>
<li>The WordPress plugin that triggered the email</li>
</ul>
</li>
<li>Example: WooCommerce orders → SendGrid, contact forms → Mailgun</li>
<li>Priority ordering with drag-free interface</li>
</ul>
⚡ Email Queue (Async Sending)
<ul>
<li>Queue emails for background delivery via WP-Cron</li>
<li>Pages load faster — no waiting for SMTP connections during page loads</li>
<li>Failed emails automatically retried with exponential backoff</li>
<li>Configurable batch size and retry limits</li>
<li>Real-time queue dashboard with cancel/retry controls</li>
</ul>
🔔 Failure Notifications
<ul>
<li>Get alerted instantly when emails fail to send</li>
<li>4 notification channels: Email, Slack, Discord, Telegram</li>
<li>Per-event subscription — choose exactly which events trigger alerts</li>
<li>Notification history with delivery status tracking</li>
</ul>
🔐 Security
<ul>
<li>AES-256-CBC encryption for all stored credentials (passwords, API keys, OAuth tokens)</li>
<li>Security Score Dashboard — real-time security posture with actionable fix recommendations</li>
<li>Dedicated encryption key support via <code>wp-config.php</code></li>
<li>Rate limiting on all REST API endpoints</li>
<li>Six custom WordPress capabilities for role-based access control</li>
<li>Full audit log tracking every configuration change</li>
<li>CSRF protection, nonce verification, input sanitization throughout</li>
</ul>
🧙 Setup Wizard
<ul>
<li>Guided 7-step wizard for first-time configuration</li>
<li>Automatic import from WP Mail SMTP, Post SMTP, Fluent SMTP, and Easy WP SMTP</li>
<li>Provider presets with pre-filled configuration fields</li>
<li>Built-in connection test with real-time feedback</li>
</ul>
🛠️ Import / Export & Tools
<ul>
<li>Export your complete configuration as a JSON file (settings, connections, routing rules)</li>
<li>Import on another site to replicate your setup instantly</li>
<li>Debug Info page with system diagnostics for troubleshooting</li>
<li>Multisite-compatible import/export</li>
</ul>
🖥️ Modern Admin Interface
<ul>
<li>React-powered single-page application — fast and responsive</li>
<li>Real-time dashboard with delivery charts and statistics</li>
<li>Responsive design for desktop, tablet, and mobile</li>
<li>Built with WordPress accessibility standards (WCAG 2.1)</li>
<li>Full internationalization support (i18n-ready)</li>
</ul>
🌐 Multisite Ready
<ul>
<li>Full WordPress Multisite support out of the box</li>
<li>Network-wide or per-site configuration</li>
<li>Network admin management panel</li>
<li>Settings propagation across all network sites</li>
</ul>
<h4>For Developers</h4>
<ul>
<li>Hooks & Filters — 30+ action and filter hooks for complete customization</li>
<li>IoC Container — Laravel-inspired dependency injection container</li>
<li>PSR-4 Autoloading — Clean, namespaced codebase via Composer</li>
<li>REST API — Full REST API for headless or programmatic management</li>
<li>Extensible Providers — Add custom mail providers by implementing <code>MailProviderInterface</code></li>
<li>Strategy Pattern — Clean architecture with strategy, repository, and service provider patterns</li>
</ul>
<h3>External services</h3>
This plugin connects to third-party email delivery services and notification platforms to send emails and alerts on your behalf. No data is sent to any service unless you explicitly configure and enable that provider or notification channel in the plugin settings.
<h4>Gmail API (Google)</h4>
When configured as a mail provider, this plugin connects to the Gmail API to send emails using your Google account via OAuth 2.0.
<ul>
<li>Endpoints: <code>https://gmail.googleapis.com</code>, <code>https://accounts.google.com</code>, <code>https://oauth2.googleapis.com</code></li>
<li>Data sent: email content (recipients, subject, body, headers, attachments), OAuth tokens for authentication</li>
<li>When: each time WordPress sends an email through this provider, and during OAuth authentication</li>
<li><a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a></li>
<li><a href="https://policies.google.com/terms" rel="nofollow ugc">Google Terms of Service</a></li>
</ul>
<h4>Microsoft 365 / Outlook (Microsoft Graph API)</h4>
When configured as a mail provider, this plugin connects to the Microsoft Graph API to send emails using your Microsoft 365 or Outlook account via OAuth 2.0.
<ul>
<li>Endpoints: <code>https://graph.microsoft.com</code>, <code>https://login.microsoftonline.com</code></li>
<li>Data sent: email content (recipients, subject, body, headers, attachments), OAuth tokens for authentication</li>
<li>When: each time WordPress sends an email through this provider, and during OAuth authentication</li>
<li><a href="https://privacy.microsoft.com/en-us/privacystatement" rel="nofollow ugc">Microsoft Privacy Statement</a></li>
<li><a href="https://www.microsoft.com/en-us/servicesagreement" rel="nofollow ugc">Microsoft Services Agreement</a></li>
</ul>
<h4>SendGrid (Twilio)</h4>
When configured as a mail provider, this plugin sends emails through the SendGrid API.
<ul>
<li>Endpoint: <code>https://api.sendgrid.com/v3</code></li>
<li>Data sent: email content (recipients, subject, body, headers, attachments), API key for authentication</li>
<li>When: each time WordPress sends an email through this provider</li>
<li><a href="https://www.twilio.com/en-us/legal/privacy" rel="nofollow ugc">Twilio Privacy Policy</a></li>
<li><a href="https://www.twilio.com/en-us/legal/tos" rel="nofollow ugc">Twilio Terms of Service</a></li>
</ul>
<h4>Mailgun (Sinch)</h4>
When configured as a mail provider, this plugin sends emails through the Mailgun API.
<ul>
<li>Endpoints: <code>https://api.mailgun.net/v3</code> (US region) or <code>https://api.eu.mailgun.net/v3</code> (EU region)</li>
<li>Data sent: email content (recipients, subject, body, headers, attachments), API key for authentication</li>
<li>When: each time WordPress sends an email through this provider</li>
<li><a href="https://www.mailgun.com/legal/privacy-policy/" rel="nofollow ugc">Mailgun Privacy Policy</a></li>
<li><a href="https://www.mailgun.com/legal/terms/" rel="nofollow ugc">Mailgun Terms of Service</a></li>
</ul>
<h4>Brevo (formerly Sendinblue)</h4>
When configured as a mail provider, this plugin sends emails through the Brevo API.
<ul>
<li>Endpoint: <code>https://api.brevo.com/v3</code></li>
<li>Data sent: email content (recipients, subject, body, headers, attachments), API key for authentication</li>
<li>When: each time WordPress sends an email through this provider</li>
<li><a href="https://www.brevo.com/legal/privacypolicy/" rel="nofollow ugc">Brevo Privacy Policy</a></li>
<li><a href="https://www.brevo.com/legal/termsofuse/" rel="nofollow ugc">Brevo Terms of Use</a></li>
</ul>
<h4>SparkPost (MessageBird)</h4>
When configured as a mail provider, this plugin sends emails through the SparkPost API.
<ul>
<li>Endpoints: <code>https://api.sparkpost.com/api/v1</code> (US) or <code>https://api.eu.sparkpost.com/api/v1</code> (EU)</li>
<li>Data sent: email content (recipients, subject, body, headers, attachments), API key for authentication</li>
<li>When: each time WordPress sends an email through this provider</li>
<li><a href="https://www.sparkpost.com/policies/privacy/" rel="nofollow ugc">SparkPost Privacy Policy</a></li>
<li><a href="https://www.sparkpost.com/policies/tou/" rel="nofollow ugc">SparkPost Terms of Use</a></li>
</ul>
<h4>Postmark (ActiveCampaign)</h4>
When configured as a mail provider, this plugin sends emails through the Postmark API.
<ul>
<li>Endpoint: <code>https://api.postmarkapp.com</code></li>
<li>Data sent: email content (recipients, subject, body, headers, attachments), server API token for authentication</li>
<li>When: each time WordPress sends an email through this provider</li>
<li><a href="https://postmarkapp.com/privacy-policy" rel="nofollow ugc">Postmark Privacy Policy</a></li>
<li><a href="https://postmarkapp.com/terms-of-service" rel="nofollow ugc">Postmark Terms of Service</a></li>
</ul>
<h4>Amazon SES (Amazon Web Services)</h4>
When configured as a mail provider, this plugin sends emails through the Amazon SES v2 API using AWS Signature v4 authentication.
<ul>
<li>Endpoint: <code>https://email.{region}.amazonaws.com</code> (region depends on your configuration)</li>
<li>Data sent: email content (recipients, subject, body, headers, attachments), signed with AWS access key credentials</li>
<li>When: each time WordPress sends an email through this provider</li>
<li><a href="https://aws.amazon.com/privacy/" rel="nofollow ugc">AWS Privacy Notice</a></li>
<li><a href="https://aws.amazon.com/service-terms/" rel="nofollow ugc">AWS Service Terms</a></li>
</ul>
<h4>Telegram Bot API</h4>
When configured as a notification channel, this plugin sends failure alerts to a Telegram chat using the Telegram Bot API.
<ul>
<li>Endpoint: <code>https://api.telegram.org/bot{token}/sendMessage</code></li>
<li>Data sent: notification messages containing email failure details (recipient, subject, error message, timestamp)</li>
<li>When: each time a configured notification event occurs (e.g., email delivery failure)</li>
<li><a href="https://telegram.org/privacy" rel="nofollow ugc">Telegram Privacy Policy</a></li>
<li><a href="https://telegram.org/tos" rel="nofollow ugc">Telegram Terms of Service</a></li>
</ul>
<h4>Slack</h4>
When configured as a notification channel, this plugin sends failure alerts to a Slack channel using incoming webhooks.
<ul>
<li>Endpoint: user-configured Slack webhook URL (<code>https://hooks.slack.com/services/...</code>)</li>
<li>Data sent: notification messages containing email failure details (recipient, subject, error message, timestamp)</li>
<li>When: each time a configured notification event occurs (e.g., email delivery failure)</li>
<li><a href="https://slack.com/trust/privacy/privacy-policy" rel="nofollow ugc">Slack Privacy Policy</a></li>
<li><a href="https://slack.com/terms-of-service" rel="nofollow ugc">Slack Terms of Service</a></li>
</ul>
<h4>Discord</h4>
When configured as a notification channel, this plugin sends failure alerts to a Discord channel using webhooks.
<ul>
<li>Endpoint: user-configured Discord webhook URL (<code>https://discord.com/api/webhooks/...</code>)</li>
<li>Data sent: notification messages containing email failure details (recipient, subject, error message, timestamp)</li>
<li>When: each time a configured notification event occurs (e.g., email delivery failure)</li>
<li><a href="https://discord.com/privacy" rel="nofollow ugc">Discord Privacy Policy</a></li>
<li><a href="https://discord.com/terms" rel="nofollow ugc">Discord Terms of Service</a></li>
</ul>

Frumbik SMTP

Send WordPress emails via SMTP or API providers (SendGrid, SES, Gmail, M365) with smart routing, failover, email logging, and queue.

Redigit

Emerge Mail replaces SMTP plugins for transactional WordPress email. Connect one or more mail accounts and every <code>wp_mail()</code> call your site makes — password resets, comment notifications, WooCommerce receipts, contact-form submissions — is delivered through that account.
Seven providers, one unified send path:
<ul>
<li>Gmail (OAuth) — sign in to your Google account; no SMTP password needed.</li>
<li>Microsoft 365 / Outlook (OAuth) — sign in to personal Outlook/Hotmail/Live or Microsoft 365 work/school accounts.</li>
<li>SendGrid (API key) — paste a v3 API key with Mail Send permission.</li>
<li>Mailgun (API key) — paste a private API key, sending domain, and pick your region (US or EU).</li>
<li>Amazon SES (Sigv4) — paste an IAM access key + secret with <code>ses:SendEmail</code> permission. No AWS SDK dependency.</li>
<li>Brevo (API key) — paste a v3 API key.</li>
<li>Generic SMTP — host + port + encryption + username + password for any SMTP server (your own host, an SES SMTP endpoint, Postmark SMTP, Fastmail, mailcow, etc.).</li>
</ul>
Because the From address is your own authenticated mailbox or verified sender, messages benefit from SPF, DKIM, and DMARC alignment that PHP’s <code>mail()</code> function cannot provide. This typically results in dramatically better inbox placement than default WordPress mail.
<h4>Key features</h4>
<ul>
<li>Seven providers (above), all sharing the same routing, failover, and From-email overrides.</li>
<li>Multiple connections per site with automatic failover. The Active connection sends first; if it fails, the next available connection is tried, with a 10-minute cooldown on failed connections. Mix-and-match across providers — e.g. SendGrid primary, an SMTP fallback, and a Gmail mailbox as the last-resort backup.</li>
<li>Optional bulk-send throttle: when a burst of sends is detected, rotate through your connected accounts instead of hammering the Active one.</li>
<li>Per-connection From email override for verified send-as aliases / verified senders.</li>
<li>Configurable sender defaults: a custom From name and an opt-in “Reply-To = admin email when sender differs” setting.</li>
<li>Full <code>wp_mail</code> compatibility: To/Cc/Bcc (including from headers), HTML bodies, multipart alternative, attachments, custom headers, RFC 2822 address formats including comma-separated lists and quoted display names, non-UTF-8 charsets.</li>
<li>RFC 2047 encoding for non-ASCII subjects and display names.</li>
<li>One-click Send test button per connection.</li>
<li>Email Controls page: opt-in suppression of WordPress core self-notifications you don’t want to receive (comment moderation, automatic updates, new-user registered, etc.) — recorded to the Activity Log instead.</li>
<li>Activity Log page: unified record of suppressed notifications, provider send errors, and recipient bounces — with type and severity filters, bulk delete, and automatic 30-day pruning.</li>
<li>Bounce classification: provider-specific error patterns map to a unified <code>send.bounce.*</code> / <code>send.error.*</code> taxonomy so per-recipient bounces are distinguished from transport outages across all seven providers.</li>
<li>Last-error visibility per connection and a site-wide admin notice on recent failures.</li>
<li>Automatic hourly token refresh for OAuth connections (Action Scheduler when available, WP-Cron fallback). API-key connections require no maintenance.</li>
<li>Safe fallback to default WordPress mail delivery on any failure — the plugin never blocks email.</li>
<li>Extensible via filters: cooldown, bulk thresholds, HTTP timeouts, token-refresh timing, MIME output, suppression catalog.</li>
</ul>
<h4>How it works</h4>
When you connect an account, the credentials (OAuth tokens, or your API key / SMTP password) are encrypted with a per-site key and stored as a WordPress option. From that point on, your site talks directly to the provider’s API or SMTP endpoint; no third party sits in the send path.
The plugin hooks <code>pre_wp_mail</code>. If at least one connection is active, the message is routed through it. If the provider returns an error — or if no connections are configured — WordPress’s default mail delivery takes over transparently.
<h4>What this is not</h4>
<ul>
<li>Not a marketing or bulk email tool. No subscriber lists, no campaigns, no broadcasts.</li>
<li>Not a shared-IP SMTP relay. Each site sends from its own connected accounts.</li>
<li>Not a way to spoof arbitrary From addresses. The provider will reject anything that isn’t an authorized sender on the connected account.</li>
</ul>
<h3>External services</h3>
To deliver mail, Emerge Mail can communicate with up to eight external services depending on which providers you connect. An optional ninth service (anonymous usage reporting) is off by default and only activated when the operator explicitly opts in. By installing and using this plugin you agree to use of these services. Nothing is contacted until you connect at least one provider in the plugin settings — every external call below is gated on the corresponding connection existing or the telemetry toggle being enabled.
<h4>1. Emerge OAuth service (emerge.redigit.net)</h4>
What it is and what it’s used for: A stateless OAuth proxy operated by the plugin author. It exists to broker the OAuth authorization handshake between your WordPress site and Google or Microsoft so the plugin can be authorized to send mail from your mailbox. The proxy holds the OAuth client secrets that Google and Microsoft would otherwise require every site to register individually.
What data is sent, when:
<ul>
<li>When you click Connect Gmail or Connect Microsoft, your browser is redirected to <code>https://emerge.redigit.net/oauth/{provider}/authorize</code> with a PKCE code challenge and a state token generated by your site. No personal data is sent.</li>
<li>When the provider redirects back, your site posts the authorization code and PKCE verifier to <code>https://emerge.redigit.net/oauth/{provider}/token</code> to receive the access and refresh tokens. The tokens are returned directly to your site and stored locally, encrypted, in <code>wp_options</code>. The proxy does not persist them.</li>
<li>When an access token nears expiry, your site posts the refresh token to <code>https://emerge.redigit.net/oauth/{provider}/refresh</code> to obtain a new access token. Again, nothing is persisted on the proxy.</li>
<li>No email content, recipient lists, or message metadata is ever sent to the proxy.</li>
</ul>
Terms and privacy:
<ul>
<li>Terms of Service: <a href="https://emerge.redigit.net/terms-of-service" rel="nofollow ugc">https://emerge.redigit.net/terms-of-service</a></li>
<li>Privacy Policy: <a href="https://emerge.redigit.net/privacy-policy" rel="nofollow ugc">https://emerge.redigit.net/privacy-policy</a></li>
</ul>
<h4>2. Google APIs (Gmail)</h4>
What it is and what it’s used for: Used only when you connect a Gmail mailbox. Once authorized, the plugin sends every <code>wp_mail()</code> message directly to the Gmail API (<code>gmail.googleapis.com</code>) from your WordPress site. Periodically the plugin also calls the Google OAuth userinfo endpoint (<code>www.googleapis.com/oauth2/v2/userinfo</code>) to verify the access token is still valid.
What data is sent, when:
<ul>
<li>On each <code>wp_mail()</code> call routed through a Gmail connection: the full outbound message (To/Cc/Bcc, subject, body, attachments, custom headers) is POSTed to <code>https://gmail.googleapis.com/gmail/v1/users/me/messages/send</code> as a base64-encoded RFC822 message. This is what’s required for the message to reach the recipient.</li>
<li>On token validation: a Bearer token is sent to <code>https://www.googleapis.com/oauth2/v2/userinfo</code>. No message data is included.</li>
</ul>
Terms and privacy:
<ul>
<li>Google Terms of Service: <a href="https://policies.google.com/terms" rel="nofollow ugc">https://policies.google.com/terms</a></li>
<li>Google Privacy Policy: <a href="https://policies.google.com/privacy" rel="nofollow ugc">https://policies.google.com/privacy</a></li>
<li>Google API Services User Data Policy: <a href="https://developers.google.com/terms/api-services-user-data-policy" rel="nofollow ugc">https://developers.google.com/terms/api-services-user-data-policy</a></li>
</ul>
<h4>3. Microsoft Graph (Outlook / Microsoft 365)</h4>
What it is and what it’s used for: Used only when you connect a Microsoft mailbox. Once authorized, the plugin sends every <code>wp_mail()</code> message directly to Microsoft Graph (<code>graph.microsoft.com</code>) from your WordPress site. Periodically the plugin also calls Graph’s <code>/me</code> endpoint to verify the access token is still valid.
What data is sent, when:
<ul>
<li>On each <code>wp_mail()</code> call routed through a Microsoft connection: the full outbound message (To/Cc/Bcc, subject, body, attachments, custom headers) is POSTed to <code>https://graph.microsoft.com/v1.0/me/sendMail</code> as a JSON payload. This is what’s required for the message to reach the recipient.</li>
<li>On token validation: a Bearer token is sent to <code>https://graph.microsoft.com/v1.0/me</code>. No message data is included.</li>
</ul>
Terms and privacy:
<ul>
<li>Microsoft Services Agreement: <a href="https://www.microsoft.com/en/servicesagreement" rel="nofollow ugc">https://www.microsoft.com/en/servicesagreement</a></li>
<li>Microsoft Privacy Statement: <a href="https://privacy.microsoft.com/en-us/privacystatement" rel="nofollow ugc">https://privacy.microsoft.com/en-us/privacystatement</a></li>
</ul>
<h4>4. SendGrid (api.sendgrid.com)</h4>
What it is and what it’s used for: Used only when you add a SendGrid connection. The plugin sends every <code>wp_mail()</code> message routed through that connection directly to the SendGrid Mail Send API. The connect-time validation also calls SendGrid’s <code>/v3/user/profile</code> to confirm the API key works.
What data is sent, when:
<ul>
<li>On each <code>wp_mail()</code> call routed through a SendGrid connection: the outbound message (recipients, subject, body, attachments, custom headers) is POSTed to <code>https://api.sendgrid.com/v3/mail/send</code> as a JSON payload.</li>
<li>On connect: an authenticated GET is sent to <code>https://api.sendgrid.com/v3/user/profile</code> to validate the API key. No message data is included.</li>
</ul>
Terms and privacy:
<ul>
<li>SendGrid Terms: <a href="https://www.twilio.com/legal/tos" rel="nofollow ugc">https://www.twilio.com/legal/tos</a></li>
<li>SendGrid Privacy Statement: <a href="https://www.twilio.com/legal/privacy" rel="nofollow ugc">https://www.twilio.com/legal/privacy</a></li>
</ul>
<h4>5. Mailgun (api.mailgun.net or api.eu.mailgun.net)</h4>
What it is and what it’s used for: Used only when you add a Mailgun connection. The plugin sends every <code>wp_mail()</code> message routed through that connection directly to the Mailgun Messages API on the region (US or EU) you select at connect time.
What data is sent, when:
<ul>
<li>On each <code>wp_mail()</code> call routed through a Mailgun connection: the outbound message (recipients, subject, body, attachments, custom headers) is POSTed as multipart/form-data to <code>https://api.mailgun.net/v3/{your-domain}/messages</code> (or the EU equivalent).</li>
<li>On connect: an authenticated GET is sent to <code>/v3/domains/{your-domain}</code> to validate the API key + domain pairing. No message data is included.</li>
</ul>
Terms and privacy:
<ul>
<li>Mailgun Terms of Service: <a href="https://www.mailgun.com/legal/terms/" rel="nofollow ugc">https://www.mailgun.com/legal/terms/</a></li>
<li>Mailgun Privacy Policy: <a href="https://www.mailgun.com/legal/privacy-policy/" rel="nofollow ugc">https://www.mailgun.com/legal/privacy-policy/</a></li>
</ul>
<h4>6. Amazon SES (email.{region}.amazonaws.com)</h4>
What it is and what it’s used for: Used only when you add an Amazon SES connection. The plugin sends every <code>wp_mail()</code> message routed through that connection directly to the SES v2 SendEmail API in the AWS region you select at connect time. Requests are signed with AWS Signature V4 using the IAM credentials you provided.
What data is sent, when:
<ul>
<li>On each <code>wp_mail()</code> call routed through a SES connection: the outbound message (recipients, subject, body, custom headers) is POSTed to <code>https://email.{region}.amazonaws.com/v2/email/outbound-emails</code> as a JSON payload.</li>
<li>On connect: a signed GET is sent to <code>/v2/email/account</code> in the same region to validate the credentials. No message data is included.</li>
</ul>
Terms and privacy:
<ul>
<li>AWS Customer Agreement: <a href="https://aws.amazon.com/agreement/" rel="nofollow ugc">https://aws.amazon.com/agreement/</a></li>
<li>AWS Privacy Notice: <a href="https://aws.amazon.com/privacy/" rel="nofollow ugc">https://aws.amazon.com/privacy/</a></li>
</ul>
<h4>7. Brevo (api.brevo.com)</h4>
What it is and what it’s used for: Used only when you add a Brevo connection. The plugin sends every <code>wp_mail()</code> message routed through that connection directly to the Brevo Transactional Email API.
What data is sent, when:
<ul>
<li>On each <code>wp_mail()</code> call routed through a Brevo connection: the outbound message (recipients, subject, body, attachments, custom headers) is POSTed to <code>https://api.brevo.com/v3/smtp/email</code> as a JSON payload.</li>
<li>On connect: an authenticated GET is sent to <code>https://api.brevo.com/v3/account</code> to validate the API key. No message data is included.</li>
</ul>
Terms and privacy:
<ul>
<li>Brevo Terms of Use: <a href="https://www.brevo.com/legal/termsofuse/" rel="nofollow ugc">https://www.brevo.com/legal/termsofuse/</a></li>
<li>Brevo Privacy Policy: <a href="https://www.brevo.com/legal/privacypolicy/" rel="nofollow ugc">https://www.brevo.com/legal/privacypolicy/</a></li>
</ul>
<h4>8. Your own SMTP server (Generic SMTP)</h4>
What it is and what it’s used for: Used only when you add a Generic SMTP connection. The plugin opens an SMTP connection to whatever host:port you specify, authenticates with the username and password you provide, and sends <code>wp_mail()</code> messages via SMTP. WordPress’s bundled PHPMailer library handles the SMTP protocol.
What data is sent, when:
<ul>
<li>On each <code>wp_mail()</code> call routed through this connection: the outbound message (recipients, subject, body, attachments, custom headers) is transmitted over SMTP to your configured host.</li>
<li>On connect: PHPMailer opens the SMTP connection, runs EHLO + STARTTLS (if enabled), and authenticates — no message is sent.</li>
</ul>
Terms and privacy: Determined by whichever SMTP server you choose to connect to. This plugin does not introduce any third-party SMTP relay; you control the destination.

Emerge Mail

Route wp_mail through Gmail, Microsoft, SendGrid, Mailgun, Amazon SES, Brevo, or any SMTP server. OAuth or bring-your-own-key, with multi-mailbox fail …

Frumbik SMTP vs Emerge Mail