The modern WordPress SMTP that protects your sender reputation.

Comparison reflects each vendor’s default behaviour as of 2026-06. Pricing and feature availability change — verify on each vendor’s page before committing.

• How is SecureSMTP different from WP Mail SMTP?

  Different category. WP Mail SMTP is a credentials adapter — you bring Gmail/SendGrid/SES API keys, it wires them into wp_mail(). SecureSMTP is the relay itself — you don't manage credentials. We also add outbound AI abuse detection, a cross-site dashboard, and per-site rate limiting that WP Mail SMTP doesn't have. They're complementary tools, not replacements; pick what matches your stack.
• Do I need to disable my existing SMTP plugin?

  Yes. SecureSMTP detects competing SMTP plugins (WP Mail SMTP, Post SMTP, FluentSMTP, Easy WP SMTP) and shows a warning in WP-admin pointing you to the conflict. Only one plugin can be in charge of wp_mail() at a time, otherwise the second one silently doesn't run. Disable the old one before flipping SecureSMTP Email Delivery on.
• Will every plugin's emails route through SecureSMTP automatically?

  Yes, as long as the plugin uses wp_mail() (which is the canonical WordPress mail API and what nearly every WP plugin uses). Once you enable Email Delivery in SecureSMTP, every wp_mail() call in WordPress is intercepted via the pre_wp_mail filter and routed through our relay. Plugin authors don't need to integrate anything.
• What if a plugin bypasses wp_mail() and uses PHPMailer directly?

  Caught by our PHPMailer interceptor in plugin v1.18+. A small minority of plugins (some Gravity Forms add-ons, certain WooCommerce extensions) instantiate PHPMailer directly to skip wp_mail. Our interceptor hooks PHPMailer's send method so even those messages route through SecureSMTP. Tested against the most common offenders.
• Can I send from my own domain (yourbusiness.com)?

  Yes — and we strongly recommend it. Add one TXT record to your DNS, and SecureSMTP signs outgoing mail with your domain's DKIM key. Inboxes see authenticated mail from you, not from SecureSMTP. Setup is one click from the dashboard: paste your domain, copy the TXT record value, drop it in your DNS, click 'Verify'. Custom domain is free on all paid plans.
• What about WooCommerce order receipts?

  WooCommerce uses wp_mail() for every transactional email — order confirmations, shipping notifications, refund receipts, password resets for customers. All of them route through SecureSMTP automatically once Email Delivery is enabled. WooCommerce's HTML email templates are preserved verbatim — we don't re-render or strip styling.
• Does SecureSMTP slow down my WordPress site?

  No measurable impact. The plugin's hook does a non-blocking HTTPS POST to our relay (typically 150–300ms server-side, async to the page load). Form submissions return immediately; the email is queued and sent within seconds. We've benchmarked the overhead at less than 10ms on the WordPress request path itself.
• What happens if SecureSMTP is ever unavailable?

  Fail-safe fallback. The plugin detects the unreachable relay and falls back to native wp_mail() automatically — your email is never silently dropped. The fallback is logged in WP-admin → QCS Forms → Mail Log so you know it happened, and you can re-send through SecureSMTP once the relay is back.
• I manage 50 client sites — can I see them all in one place?

  Yes. The dashboard at securessmtp.com/app/forms/sites shows every site you've connected: last-24-hour mail volume, anomaly status, per-site quota usage, DKIM health. Each site has its own API key (rotatable from the dashboard), its own quota, and its own mail log. Agency-friendly by design.
• How is this different from SendGrid or Mailgun?

  SendGrid and Mailgun are raw email infrastructure — you bring your own code (or another SMTP plugin) to integrate WordPress with their APIs. SecureSMTP is the integration: install one WP plugin, get the relay + dashboard + AI + cross-site visibility, no glue code. Under the hood we use Resend as our sending infrastructure — comparable to SendGrid/Mailgun but with better deliverability scores on modern inboxes.
• Is my email content stored?

  Email metadata (subject, to/from/cc, timestamp, status) is stored for 30 days on free plans and 90 days on paid plans, viewable in the mail log. Email body is hashed for de-dupe but not stored in plaintext after the send completes. AI scanner reads the body in-memory at scan time and discards it; we never persist body content for later access.
• What's the catch?

  None on the free tier. 100 routed emails/month with every reliability feature (AI abuse scan included) at $0. Paid plans start at $7/mo for 2,000 emails. The model: we make money on volume, you get a free relay until you outgrow it. If you need more than 100 messages a month you'll have to upgrade — but you'll know it's worth it because you'll have already seen the deliverability difference.