WordPress Email,
Finally Reliable

WordPress sends mail via PHP mail() by default. Most modern hosts block or throttle this function because spammers abuse it — causing password resets, order confirmations and contact form notifications to silently disappear or land in spam. SMTP authenticates you with a real mail server, so messages are delivered reliably.

Yes. You must use a Gmail App Password — Google no longer allows regular account passwords for third-party SMTP clients. Enable 2-Step Verification on your Google account, then generate an App Password under Security → App Passwords. Use smtp.gmail.com, port 587, encryption TLS.

Yes. Use your Microsoft 365 account password or an app password. Set the host to smtp.office365.com, port 587, encryption TLS.

Yes. This plugin hooks into WordPress's wp_mail() function — the same function WooCommerce, Contact Form 7, WPForms, Gravity Forms and virtually every other plugin uses to send email. No extra configuration is needed for any of them.

When monitoring is enabled, WordPress Cron opens a real connection to your SMTP server at your chosen interval and runs EHLO, STARTTLS, and AUTH — not just a TCP port check. No email is sent on a successful check. If it fails consecutively beyond your threshold, the plugin checks whether the failure looks like a known outage on your provider's end, then posts an alert instantly to whichever channel you've configured — Slack, Microsoft Teams, Google Chat, Discord, or a custom webhook.

Your SMTP password is encrypted at rest before being stored in the WordPress wp_options table — never stored as plaintext. They are never transmitted to ByteCore Stack servers. The password field is masked in the admin UI and never exposed in email logs or headers.

No. This plugin is designed for transactional email — order confirmations, password resets, contact form notifications. For bulk marketing campaigns use a dedicated service such as Mailchimp, Klaviyo or Brevo.

Yes, if you've enabled "Store failed email content" in the Config tab first — it's off by default, and email bodies are otherwise never stored. When enabled, the content of an email is stored only if it fails to send, so a "Resend" button appears on that row in the Email Log. Resending creates a fresh log entry with its own delivery status; stored content auto-purges after a configurable number of days (default 7), independent of your overall log retention setting.

Yes. wp bcs-smtp test you@example.com sends a test email, wp bcs-smtp resend <log_id> resends a failed email by its log ID (same requirement as the admin Resend button — "Store failed email content" must have been enabled when it failed), and wp bcs-smtp log list lists recent log entries with --status, --days, and --format options. Handy for CI/deploy pipelines or server automation.

Log entries are pruned automatically once per day via WordPress Cron. In the Config tab you choose to keep either the last 30 days of records or the last 1,000 records. Older entries are deleted automatically — no manual cleanup needed.