WT SMTP

By Webmasters.Team

0+ active installationsVersion 1.0.11

Lightweight SMTP for WordPress with first-class diagnostics. Connect any mail provider, log delivery and troubleshoot from one panel.

Description

WT Waitlist sends back-in-stock emails, WT Hardening logs security events, and now WT SMTP makes sure those emails actually arrive, and tells you exactly why they do not.

Built by the Webmasters.Team team. Open-source, no external dependencies, no Pro upsell.

Why another SMTP plugin?

Because most SMTP plugins tell you whether a send returned true or false. WT SMTP tells you why mail goes to spam before you even press Send: the Settings page runs a live SPF / DKIM / DMARC / MX check against your From domain and flags missing, broken and weak records inline, with what to fix. No external tool, no copy-pasting domain names into third-party validators.

Key features

  • Drop-in SMTP for any provider, with generic host/port/encryption/auth settings plus one-click presets for a hosting mailbox (cPanel, DirectAdmin, Plesk), Gmail, Outlook / Microsoft365, SendGrid, Brevo, Mailgun, Amazon SES and MailHog (dev).
  • Import from WP Mail SMTP: switching plugins? One click copies the SMTP host, port, encryption, username, password and From settings, including passwords WP Mail SMTP stored encrypted.
  • AES-256 password encryption at rest when you define WTSMTP_KEY in wp-config.php, falling back to plaintext storage with a visible warning if the key is missing.
  • Mail log in a dedicated table ({prefix}wtsmtp_log) with metadata only (no bodies or attachments), one-click resend for failed messages and configurable retention (default 30 days).
  • Live DNS health check for the From domain, not just “record exists” but full validation: SPF syntax, the 10-DNS-lookup limit (followed through every include:), the all policy and whether your SMTP provider is authorized; DKIM keys that are revoked, truncated, shorter than 2048 bits or in testing mode (for any selectors you configure; defaults: default, google, selector1); DMARC policy, pct, subdomain inheritance and report-address authorization; MX hosts that do not resolve or a null MX. Cached for 1 hour, with a “Re-check now” button.
  • Test email with full PHPMailer ErrorInfo surfaced on failure, showing the actual reason wp_mail() returned false.
  • Conflict detection: warns when another SMTP plugin (WP Mail SMTP, FluentSMTP, Post SMTP, Easy WP SMTP…) is also active and would fight over phpmailer_init.
  • Copy diagnostic info: paste-ready text block with environment, config, log counts, DNS results and conflict notes for support tickets.
  • GDPR-friendly recipient anonymization in the log (opt-in, e.g. j***@example.com).
  • Zero external dependencies: no Composer, no JS framework, no call-home.

External services

WT SMTP sends your site’s outgoing email through an SMTP server, and it can look up your domain’s email DNS records for the built-in deliverability diagnostic. Both are described below.

Your SMTP server / provider

When WordPress sends an email (wp_mail()), WT SMTP hands the message to the SMTP server you configure under Webmasters.Team -> WT SMTP -> Settings. The email (its headers, subject, recipients and body) and the SMTP username and password you entered are transmitted to that server whenever WordPress sends a message.

The SMTP server can be your own mail server or a third-party provider. For convenience the plugin ships connection presets for the providers below; choosing a preset only fills in the host and port. You still enter your own credentials, and nothing is sent anywhere until WordPress actually sends an email:

  • Gmail / Google Workspace: terms https://policies.google.com/terms and privacy https://policies.google.com/privacy
  • Microsoft 365 / Outlook: terms https://www.microsoft.com/servicesagreement and privacy https://privacy.microsoft.com/privacystatement
  • SendGrid (Twilio): terms https://www.twilio.com/legal/tos and privacy https://www.twilio.com/legal/privacy
  • Brevo (Sendinblue): terms https://www.brevo.com/legal/termsofuse/ and privacy https://www.brevo.com/legal/privacypolicy/
  • Mailgun: terms https://www.mailgun.com/legal/terms/ and privacy https://www.mailgun.com/legal/privacy-policy/
  • Amazon SES: terms https://aws.amazon.com/service-terms/ and privacy https://aws.amazon.com/privacy/

If you use a different SMTP server, its own terms and privacy policy apply. WT SMTP does not send your data to Webmasters.Team or any of its own servers.

Domain DNS lookup (deliverability diagnostic)

The optional “DNS health check” on the settings screen performs standard public DNS lookups (MX, SPF, DMARC and DKIM records) for your site’s own email domain, using PHP’s dns_get_record(). It is a normal DNS query and the result is cached for one hour. No personal data is sent, and the lookup only runs when you open the diagnostic.

Installation

  1. Install and activate WT SMTP.
  2. Open Webmasters.Team → WT SMTP → Settings in the admin.
  3. (Recommended) Add define('WTSMTP_KEY', 'a long random string'); to wp-config.php to enable AES-256 password encryption.
  4. Pick a provider preset (or enter your own host), add credentials, set the From email, save.
  5. Click Send test email to admin to verify the pipeline.

FAQ

Where do I get SMTP credentials?

From your mail provider. Most providers (Gmail, Outlook, Brevo, SendGrid, Mailgun, Amazon SES) require an app password or API-key-as-password, not your regular account password.

Why is the password stored in plaintext?

It is not, if you defined WTSMTP_KEY in wp-config.php. Without it, the plugin falls back to plaintext and shows a visible warning in the Settings panel. Defining the key takes 30 seconds and is strongly recommended.

The DNS health check shows “DNS lookups blocked by host”. What now?

Some low-cost shared hosts disable dns_get_record(). Use an external DNS lookup tool (mxtoolbox.com) for your From domain, or move to a host that allows DNS queries. The rest of the plugin still works.

I see “WP Mail SMTP is also active” in the System status.

Two SMTP plugins on one site will fight over the phpmailer_init hook. Only one wins, and you cannot predict which. Disable one.

Will this slow down my site?

No. SMTP wire-up only happens when wp_mail() is actually called. The DNS health check is cached for 1 hour. Logging is a single INSERT per send.

Can I forward the log to my own monitoring?

Yes. Hook the wtsmtp/after_send action (fires after each log INSERT) and pipe the row anywhere you like.

Will old log entries clog the database?

No. The plugin schedules a daily purge of entries older than the configured retention (default 30 days).

Changelog

1.0.11

  • Translations: the Polish translation follows the WordPress Polish team glossary (for example the “Mail Log” tab is now “Dziennik wiadomości”, and “email” is written without a hyphen).

1.0.10

  • New: WT SMTP now lives in the shared Webmasters.Team menu, with Settings and Mail Log as tabs of one page and a new About tab (version, links, changelog). The Webmasters.Team menu also lists our other plugins. Old page addresses redirect to the new tabs.
  • Added the plugin homepage link.
  • Tweak: clearer wording and consistent typography (curly quotes, no dashes in sentences) in the plugin texts and this readme.

1.0.9

  • Fix: the log table is now created or updated after a plugin update, not only on activation, and creating it is retried if it failed.
  • Fix: when the plugin is network-activated on a multisite, every site now gets its own log table (previously only the main site had one and subsites logged nothing).
  • Fix: network deactivation now removes the cleanup cron on every site, not only on the main site.
  • Fix: uninstalling now also removes the plugin’s cached DNS check results and import notices, clears the cleanup cron completely, and cleans every site on a multisite network.
  • Housekeeping: internal classes renamed to the WebmastersTeam\Smtp namespace; the old Webmasters\Smtp names are kept as aliases for this release, so updating from 1.0.8 and code referring to the old names keep working. Options, database table, hooks and settings are unchanged.
  • Housekeeping: resolved Plugin Check findings.
  • New: on PHP older than 8.2 administrators see a notice (Dashboard, Plugins screen and the plugin’s own pages, dismissible for 30 days) and a Site Health recommendation: version 1.1.0 will require PHP 8.2. No external requests are made for this.
  • Translations: Polish translation included.

1.0.8

  • New: import settings from WP Mail SMTP. When its configuration is found, the Settings page offers a one-click import of host, port, encryption, username, password (decrypted and re-encrypted with WT SMTP’s own key) and From settings. Works whether WP Mail SMTP is active or not, and supports its WPMS_* wp-config.php constants.
  • New: “Hosting mailbox” preset (cPanel, DirectAdmin, Plesk) with guidance on finding the SMTP server name.
  • Tweak: clearer credentials hint (app passwords are only needed for Gmail / Microsoft 365; hosting mailboxes use the mailbox password).
  • Compatibility: tested with WordPress 7.1.4.

1.0.7

  • Fix: raised the minimum PHP version to 8.1 to match the code (the plugin uses readonly properties, introduced in PHP 8.1); this prevents a parse error when activated on PHP 8.0.

1.0.6

  • Housekeeping: renamed internal code identifiers (defines, options, hooks, transients, admin-page slugs) to the unique wtsmtp prefix to avoid conflicts. The public action hook is now wtsmtp/after_send; the encryption constant is now WTSMTP_KEY.

1.0.5

  • Docs: documented the external services the plugin uses (the configured SMTP server/provider and the domain DNS deliverability lookup).
  • New: the documented wtsmtp/after_send action now fires after each mail-log entry is written.
  • Housekeeping: moved “Tested up to” out of the main plugin file (readme is the single source), removed the plugin header URI.

1.0.4

  • Compatibility: tested up to WordPress 7.1.

1.0.3

  • Raised the minimum required WordPress version to 6.7 and use wp_get_wp_version() (the recommended replacement for the global $wp_version) for the WordPress version shown in the System Status diagnostics. No user-facing change.

1.0.2

  • Compatibility: use wp_get_wp_version() (WordPress 6.7+) instead of reading the global $wp_version in the System Status diagnostics, with a fallback for older cores. No user-facing behaviour change.

1.0.1

  • Pre-approval hardening: addressed Plugin Check findings on the initial submission. No user-facing behaviour change.
    • Explicit wp_unslash() + absint() on all $_GET reads in the Mail Log list table.
    • Documented phpcs:ignore annotations on nonce checks that happen later in the same flow (Mail Log resend, list-table filters).
    • Class-level phpcs:disable with rationale on the mail-log repository, because every query targets the plugin’s own {prefix}wtsmtp_log table built from $wpdb->prefix, no user-controlled identifiers anywhere.
    • Same annotation on the uninstall.php DROP TABLE.

1.0.0

First public release.

  • SMTP configuration with one-click provider presets (Gmail, Outlook / Microsoft365, SendGrid, Brevo, Mailgun, Amazon SES, MailHog).
  • AES-256 password encryption at rest using WTSMTP_KEY (fallback to AUTH_KEY or plaintext with a warning).
  • Custom mail-log table ({prefix}wtsmtp_log) with metadata only, no bodies or attachments.
  • Mail log admin screen with filtering, search, bulk delete and one-click resend.
  • Test email AJAX with PHPMailer ErrorInfo surfaced on failure.
  • Live DNS health check (MX / SPF / DMARC / DKIM with configurable selectors).
  • Conflict detection for other SMTP plugins (WP Mail SMTP, FluentSMTP, Post SMTP, Easy WP SMTP, WP SMTP, WP Mail Bank).
  • Copy-to-clipboard support diagnostic snippet.
  • Opt-in GDPR recipient anonymization in the log.
  • Daily purge cron with configurable retention (default 30 days).