Transactional mail relays

Does your password reset go through a mail vendor?

When configured with an outside mail provider, SMTP plugins can route password resets, order receipts, and form notifications through that service. Recipient addresses and message content go to the selected provider. Compare the documented setups below.

Based on plugin and vendor documentation, not tests of your site. Your mailer settings decide the path. This is not legal advice or a compliance rating.

Scan your site for third-party requests

This scan checks requests made by a visitor's browser. Server-side SMTP / mail-relay traffic does not appear in a browser scan — check the plugin's mailer settings.

Outside mail relay vs a copy on your site

Optional logs on your WordPress site

Some plugins can keep a local copy of sent messages in WordPress. That log is a second copy. It does not stop the message from going to the mailer you configured.

Mail through an outside service

With an outside provider selected, your server sends the message through that provider's SMTP service or API. The visitor browser is not involved. Delivery and open/click data may also appear in the vendor dashboard.

SMTP plugins and mailers

No paid placement. Vendor-relay rows first, then setups not yet reviewed. Names are alphabetical within each group.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Amazon SES mailer (via SMTP plugin)

With the Amazon SES mailer selected, your server sends recipients and message content to Amazon SES. This transfer happens on the server and is not visible in a visitor browser scan.

Transactional mail relayed through a vendorReceiving domains not verifiedNot assessedNot tested
  • None
Brevo mailer (via SMTP plugin)

When an SMTP plugin’s Brevo (Sendinblue) mailer is selected, transactional mail is sent through Brevo’s API using your account key. Recipients and message content land on Brevo; newsletter signup plugins are a separate path on the email-plugin privacy page. Not a visitor browser host.

Transactional mail relayed through a vendorReceiving domains not verifiedNot assessedNot tested
  • None
Easy WP SMTP

Routes every outgoing message through the configured transactional mailer or SMTP. Free tier logs failed sends; Pro adds a full email log. Vendor dashboards (for example SendLayer) may keep delivery and open/click history. This row covers an outside-provider configuration. With custom SMTP, the destination depends on the host you enter. Server-side — not a visitor browser host.

Transactional mail relayed through a vendorReceiving domains not verifiedNot assessedNot tested
  • None
FluentSMTP

Hands every email to the connected service’s API or SMTP host — password resets, WooCommerce, forms, and other wp_mail() sends. Log Emails can store outgoing messages in a dedicated WordPress table (on by default) with a configurable delete window. Local logs do not replace vendor storage. This row covers an outside-provider configuration. With custom SMTP, the destination depends on the host you enter. Server-side — not a visitor browser host.

Transactional mail relayed through a vendorReceiving domains not verifiedNot assessedNot tested
  • None
Gmail SMTP

Uses OAuth 2.0 to authenticate and sends WordPress email through Gmail's SMTP server. Covers password resets, order emails, and form notifications sent through WordPress mail. An email-logging add-on is available. This transfer happens on the server and is not visible in a visitor browser scan.

Transactional mail relayed through a vendorReceiving domains not verifiedNot assessedNot tested
  • None
Mailgun mailer (via SMTP plugin)

When an SMTP plugin’s Mailgun mailer is selected, the store server sends transactional mail to Mailgun (api.mailgun.net or api.eu.mailgun.net). Recipients and message content land on Mailgun; the Mailgun control panel holds provider-side activity. Not a visitor browser host.

Transactional mail relayed through a vendorReceiving domains not verifiedNot assessedNot tested
  • None
Post SMTP

Routes all wp_mail() through the chosen SMTP or API mailer (Gmail, Microsoft 365, Amazon SES, Brevo, Mailgun, SendGrid, Postmark, Zoho, SparkPost, Other SMTP). Free detailed email logs can keep a copy on WordPress; Pro adds open tracking on the log screen. This row covers an outside-provider configuration. With custom SMTP, the destination depends on the host you enter. Server-side — not a visitor browser host.

Transactional mail relayed through a vendorReceiving domains not verifiedNot assessedNot tested
  • None
SendGrid mailer (via SMTP plugin)

When an SMTP plugin’s SendGrid mailer is selected, the store server posts transactional mail to SendGrid (typically api.sendgrid.com). Recipients and message content land on SendGrid infrastructure; delivery and engagement stats may appear in the SendGrid dashboard. Not a visitor browser host.

Transactional mail relayed through a vendorReceiving domains not verifiedNot assessedNot tested
  • None
WP Mail SMTP

When a mailer is configured, WordPress sends the message (recipients, subject, content, headers, and attachments) plus the credentials you entered to that provider. Covers password resets and other wp_mail() traffic. Email logging is Pro. This row covers an outside-provider configuration. With custom SMTP, the destination depends on the host you enter. Server-side — not a visitor browser host.

Transactional mail relayed through a vendorReceiving domains not verifiedNot assessedNot tested
  • None
SMTP for SendGrid – YaySMTP

We have not reviewed this setup's transactional mail path against a public source we can cite yet.

Not reviewedDocumentation not reviewed yet.Not assessedNot tested
  • None
Web357 SMTP Connect for Gmail

We have not reviewed this setup's transactional mail path against a public source we can cite yet.

Not reviewedDocumentation not reviewed yet.Not assessedNot tested
  • None

What this table does and does not prove

Based on documentation, not a test of your site. Relay rows describe server-side mailers. Local logs are optional second copies. Newsletter and list plugins are covered elsewhere. Consent timing and data retention have not been tested. Not reviewed means we have not assessed that setup.

Documentation snapshot: Oct 8, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-smtp-plugin-privacy