

Dashboard overview — SMTP authentication status and recent email log activity at a glance
Is your WordPress site silently failing to send emails? Order confirmations, password resets, contact form notifications, shipping updates — when they don’t land in the inbox, you’re usually the last person to find out, often from an angry customer. ByteCoreStack – SMTP & Health Monitor fixes email deliverability at the source, logs every single send, and alerts your team the instant delivery breaks again — on Slack, Microsoft Teams, Google Chat, or Discord, at no extra cost.
This plugin doesn’t stop the moment your email starts sending again. It keeps going: continuous SMTP health monitoring, a fully searchable email log with CSV export, scheduled delivery reports, and real-time failure alerts, all included.
By default, WordPress sends email through your server’s PHP mail() function. PHP mail has no authentication — no SPF, no DKIM, nothing that proves to Gmail, Outlook, or Yahoo that the message is legitimate. Most inbox providers either bin it as spam or drop it outright. That’s why “WordPress not sending email” is one of the most common WordPress problems there is, and why every serious site needs proper SMTP — authenticated, encrypted mail delivery through a real mail server or transactional email provider.
The plugin reconfigures wp_mail() to send through the authenticated SMTP server you configure — your hosting provider, Gmail, Microsoft 365, or any transactional email service (SendGrid, Mailgun, Amazon SES, Brevo, Zoho, SMTP.com, and others all work over standard SMTP). Every email is logged with its delivery status, and an automated health check keeps testing your connection in the background — so instead of finding out about a broken mail server from an angry customer, you find out from a Slack message.
wp_mail() sendswp bcs-smtp test, wp bcs-smtp resend <id>, and wp bcs-smtp log list for scripting test sends, resends, and log lookups from the command line or a CI/deploy pipelineIncluded at no extra cost:
event, site_name, error_msg, consecutive_failures, and more) for Zapier, Make, n8n, or your own endpointwp_safe_remote_post(), so a misconfigured webhook can’t be used to reach internal network addressesWooCommerce, Contact Form 7, WPForms, Gravity Forms, Elementor Forms, user registration/password reset emails, and literally any other plugin or theme that sends mail through WordPress’s standard wp_mail() function — because that’s exactly what this plugin hooks into. Nothing to reconfigure on the form/store plugin side.
Anything that speaks standard SMTP with host/port/username/password authentication works, because the plugin talks SMTP directly rather than locking you into a specific provider’s proprietary API:
Getting your email sending again is only half the job. If the connection breaks next month — expired app password, host changed something, provider outage — you need to know before a customer tells you. ByteCoreStack – SMTP & Health Monitor treats failure alerting as core functionality, included for every user, because a delivery plugin that can’t tell you when delivery breaks isn’t finished doing its job.
Full plugin details: bytecorestack.com/plugins/smtp-manager. For SMTP protocol background, see the WordPress wp_mail() developer reference.
This plugin may contact the following external services. All connections are either user-initiated or require explicit configuration by the site administrator.
1. Your SMTP server (user-configured)
The plugin routes all WordPress emails through the SMTP server credentials you enter in Settings SMTP Manager. The hostname, port, username, and password are provided entirely by you. No data is sent to any ByteCore Stack server.
2. Slack Incoming Webhooks (optional)
If you enable Slack alerts, the plugin will POST a JSON failure notification to the Slack Incoming Webhook URL you provide when consecutive SMTP failures are detected. This URL is specific to your Slack workspace and is created by you.
* Service: Slack Technologies, LLC
* Privacy policy: https://slack.com/privacy-policy
* Terms of service: https://slack.com/terms-of-service
3. Microsoft Teams Incoming Webhooks (optional)
If you enable Teams alerts, the plugin will POST a JSON failure notification to the Teams Incoming Webhook URL you provide when consecutive SMTP failures are detected. This URL is specific to your Teams channel and is created by you.
* Service: Microsoft Corporation
* Privacy policy: https://privacy.microsoft.com/en-us/privacystatement
* Terms of service: https://www.microsoft.com/en-us/servicesagreement
4. Google Chat Incoming Webhooks (optional)
If you enable Google Chat alerts, the plugin will POST a JSON failure notification to the Google Chat Incoming Webhook URL you provide when consecutive SMTP failures are detected. This URL is specific to your Chat space and is created by you.
* Service: Google LLC
* Privacy policy: https://policies.google.com/privacy
* Terms of service: https://policies.google.com/terms
5. Discord Incoming Webhooks (optional)
If you enable Discord alerts, the plugin will POST a JSON failure notification to the Discord Incoming Webhook URL you provide when consecutive SMTP failures are detected. This URL is specific to your Discord channel and is created by you.
* Service: Discord Inc.
* Privacy policy: https://discord.com/privacy
* Terms of service: https://discord.com/terms
6. Custom Webhook (optional)
If you enable the Custom Webhook channel, the plugin will POST a structured JSON failure notification to the URL you provide when consecutive SMTP failures are detected. This URL is entirely user-supplied — point it at Zapier, Make, n8n, or your own server. No data is sent unless you configure this channel.
7. ipify.org (automatic, no configuration)
When determining the server’s outbound IP address for connection diagnostics (used only if the server’s own SERVER_ADDR is unavailable, e.g. in some local/Docker/proxy environments), the plugin makes a GET request to the ipify.org public IP-lookup API. No data is sent beyond the request itself; the response is just an IP address string.
* Service: ipify (Randomize.io)
* Privacy policy: https://www.ipify.org/
8. Microsoft 365 Service Status API (automatic, only when your configured SMTP host is Microsoft 365/Outlook)
When the automated SMTP health check (see “Real-time failure alerts”) detects a connection failure and your configured SMTP host is office365 or outlook, the plugin queries Microsoft’s public service status API to check whether the failure is a known Microsoft-side outage before sending you an alert. No site or email data is sent — only an outbound GET request is made.
* Service: Microsoft Corporation
* Privacy policy: https://privacy.microsoft.com/en-us/privacystatement
No data is collected, transmitted to, or processed by ByteCore Stack servers.