Title: SMTP Manager – Email Logs, Monitoring & Alerts Author: bytecorestack Published: Jen 11, 2026 Last modified: Jen 20, 2026 --- Search plugins ![](https://ps.w.org/bcs-smtp-manager/assets/banner-772x250.png?rev=3568827) ![](https://ps.w.org/bcs-smtp-manager/assets/icon-256x256.png?rev=3568869) # SMTP Manager – Email Logs, Monitoring & Alerts By [bytecorestack](https://profiles.wordpress.org/bytecorestack/) [Download](https://downloads.wordpress.org/plugin/bcs-smtp-manager.1.1.0.zip) * [Details](https://hat.wordpress.org/plugins/bcs-smtp-manager/#description) * [Reviews](https://hat.wordpress.org/plugins/bcs-smtp-manager/#reviews) * [Installation](https://hat.wordpress.org/plugins/bcs-smtp-manager/#installation) * [Development](https://hat.wordpress.org/plugins/bcs-smtp-manager/#developers) [Support](https://wordpress.org/support/plugin/bcs-smtp-manager/) ## Description **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. SMTP Manager – Email Logs, Monitoring & Alerts is the WordPress SMTP plugin that 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, completely free. Most WordPress SMTP plugins stop the moment your email starts sending again. This one keeps going: continuous SMTP health monitoring, a fully searchable email log with CSV export, scheduled delivery reports, and real-time failure alerts that many competing SMTP plugins lock behind a paid upgrade. #### Why your WordPress emails are failing 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. #### How SMTP Manager fixes it 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. #### ✅ Core features * **Universal SMTP connection** — host, port, and encryption (SSL / TLS / none) for any standard SMTP provider, with auto-TLS upgrade support * **Built-in quick-reference for popular providers** — Gmail / Google Workspace, Microsoft 365 / Outlook, Yahoo Mail, SendGrid, Amazon SES, and Mailgun host/port/ encryption settings, right inside the settings page * **Full email log** — date, subject, sender, recipient, delivery status, and the actual error message for every email `wp_mail()` sends * **AJAX-driven search and filtering** — live search-as-you-type plus date-range presets (today through all time), no page reloads * **CSV export** of the filtered log for record-keeping or support tickets * **One-click “Send Test Email”** to verify your configuration instantly, with failure-type classification (authentication failure, SMTP rejection, or plugin/ system error) so you know exactly what’s wrong * **Scheduled HTML delivery reports** — daily, weekly, or monthly summary emails with a visual chart of sent/failed/unconfirmed volume * **Automatic log retention** — keep the last 30 days or the last 1,000 records, pruned automatically * **WordPress Dashboard widget** — SMTP health and 30-day send volume at a glance, without opening the plugin’s settings page * **Encrypted password storage** — your SMTP password is encrypted at rest, not stored as plaintext * **Dark-mode admin UI** built for clarity, not just decoration #### 🔔 Real-time failure alerts — completely free This is the feature most SMTP plugins put behind a premium plan. Here, it’s free: * **Automated SMTP health checks** via WordPress Cron — a real connection + EHLO + STARTTLS + AUTH test on the interval you choose, with no test email sent on success * **Five alert channels**: Slack, Microsoft Teams, Google Chat, Discord, and a Custom Webhook option that POSTs a structured JSON payload (`event`, `site_name`,` error_msg`, `consecutive_failures`, and more) for Zapier, Make, n8n, or your own endpoint * **Configurable failure threshold** — alert after 1 failure or wait for N consecutive failures, your choice * **Notification cap** so a prolonged outage doesn’t spam your channel forever * **External provider status check** — when an alert fires, the plugin checks whether the failure looks like an outage on your provider’s end before notifying you * All webhook URLs are validated against the provider’s real domain and sent over` wp_safe_remote_post()`, so a misconfigured webhook can’t be used to reach internal network addresses #### 🔌 Works with everything that uses wp_mail() WooCommerce, 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. #### 🌐 Supported SMTP providers 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: * [Gmail / Google Workspace](https://myaccount.google.com/apppasswords) (App Passwords, or [Workspace SMTP relay](https://support.google.com/a/answer/2956491) for higher volume) * [Microsoft 365 / Outlook](https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365) * [SendGrid](https://docs.sendgrid.com/for-developers/sending-email/getting-started-smtp) * [Mailgun](https://documentation.mailgun.com/docs/mailgun/user-manual/sending-messages/) * [Amazon SES](https://docs.aws.amazon.com/ses/latest/dg/send-email-smtp.html) * [Brevo](https://help.brevo.com/hc/en-us/articles/209462765) * [Zoho Mail](https://www.zoho.com/mail/help/) * Yahoo Mail, SMTP.com, or your own hosting provider’s mail server #### 🆚 How this is different Most SMTP plugins solve half the problem: they get your email sending again, and stop there. If the connection breaks again next month — expired app password, host changed something, provider outage — you won’t know until someone tells you. Many plugins in this category also reserve email alerting (Slack, Teams, Discord notifications) for their paid tier. SMTP Manager – Email Logs, Monitoring & Alerts treats failure alerting as core functionality, not an upsell, because a delivery plugin that can’t tell you when delivery breaks isn’t finished doing its job. #### Documentation & support Full plugin details: [bytecorestack.com/plugins/smtp-manager](https://bytecorestack.com/plugins/smtp-manager/). For SMTP protocol background, see the [WordPress wp_mail() developer reference](https://developer.wordpress.org/reference/functions/wp_mail/). ### External Services 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. Google Fonts API** The admin settings page loads two typefaces (DM Sans and DM Mono) from the Google Fonts API to render the admin UI. This request is made only by the administrator’s browser when visiting the plugin settings page. No personal data from site visitors is ever transmitted. * Service: Google LLC * Privacy policy: https://policies.google.com/privacy * Terms of service: https://policies.google. com/terms * Font API endpoint: https://fonts.googleapis.com/ No data is collected, transmitted to, or processed by ByteCore Stack servers. ## Screenshots [⌊Dashboard overview — SMTP authentication status and recent email log activity at a glance⌉⌊Dashboard overview — SMTP authentication status and recent email log activity at a glance⌉[ Dashboard overview — SMTP authentication status and recent email log activity at a glance [⌊SMTP server connection panel — host, port, encryption, and credentials in one place⌉⌊SMTP server connection panel — host, port, encryption, and credentials in one place⌉[ SMTP server connection panel — host, port, encryption, and credentials in one place [⌊Email log — full delivery history with search, status filters, and automatic log retention⌉⌊Email log — full delivery history with search, status filters, and automatic log retention⌉[ Email log — full delivery history with search, status filters, and automatic log retention [⌊Email report — visual delivery chart with scheduled report configuration⌉⌊Email report — visual delivery chart with scheduled report configuration⌉[ Email report — visual delivery chart with scheduled report configuration [⌊Send Test Email — verify your SMTP configuration and delivery instantly⌉⌊Send Test Email — verify your SMTP configuration and delivery instantly⌉[ Send Test Email — verify your SMTP configuration and delivery instantly [⌊Alerts tab — enabling automated SMTP health monitoring⌉⌊Alerts tab — enabling automated SMTP health monitoring⌉[ Alerts tab — enabling automated SMTP health monitoring [⌊Alert channel setup — Slack, Microsoft Teams, Google Chat, Discord, or a custom webhook⌉⌊Alert channel setup — Slack, Microsoft Teams, Google Chat, Discord, or a custom webhook⌉[ Alert channel setup — Slack, Microsoft Teams, Google Chat, Discord, or a custom webhook [⌊SMTP configuration — encryption, authentication, and provider-specific settings⌉⌊ SMTP configuration — encryption, authentication, and provider-specific settings⌉[ SMTP configuration — encryption, authentication, and provider-specific settings [⌊A live failure alert delivered to a chat channel — real-time SMTP notification in action⌉⌊A live failure alert delivered to a chat channel — real-time SMTP notification in action⌉[ A live failure alert delivered to a chat channel — real-time SMTP notification in action ## Installation 1. Upload the `bcs-smtp-manager` folder to `/wp-content/plugins/`, or install directly from the WordPress Plugins screen. 2. Activate the plugin through the **Plugins** menu in WordPress. 3. Go to **Settings SMTP Manager** and enter your SMTP host, port, encryption, and credentials (use the built-in provider quick-reference if you’re not sure what to enter). 4. Click **Save Settings** — the plugin runs a connection test immediately and tells you if it worked. 5. Use **Send Test Email** to confirm an actual message is delivered end-to-end. 6. Open the **Alerts** tab, enable a channel (Slack, Teams, Google Chat, Discord, or a custom webhook), and turn on automated health monitoring so you’re notified the next time something breaks. ## FAQ ### What is SMTP and why do I need it for WordPress? SMTP (Simple Mail Transfer Protocol) is the standard, authenticated way to send email. WordPress’s default `mail()` function has no authentication, which is why its messages are frequently marked as spam or rejected outright by Gmail, Outlook, and Yahoo. Routing through a real SMTP connection — your host, Gmail, Microsoft 365, or a transactional provider — fixes that. ### Why isn’t my WordPress site sending emails right now? The most common causes are: your host has disabled the PHP `mail()` function, your SMTP credentials are wrong or expired (Gmail/Microsoft App Passwords expire or get revoked), the wrong port/encryption combination is selected, or your host blocks outbound SMTP ports entirely. Use **Send Test Email** in this plugin — it classifies the failure (authentication, rejection, or system error) so you know which of these it is instead of guessing. ### Does this work with Gmail? 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](https://myaccount.google.com/apppasswords). ### Does this work with Outlook / Microsoft 365? Yes. Use your Microsoft 365 account password or an app password. Set the host to` smtp.office365.com`, port `587`, encryption `TLS`. See Microsoft’s [official SMTP relay setup guide](https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-microsoft-365-or-office-365) if you need app-specific credentials or hit a sending limit. ### Does this work with Google Workspace (not just regular Gmail)? Yes. Google Workspace also supports a [dedicated SMTP relay service](https://support.google.com/a/answer/2956491) for higher sending limits than a personal Gmail App Password allows — useful if you’re sending a high volume of transactional email. ### Does this work with SendGrid, Mailgun, Amazon SES, Brevo, or Zoho? Yes — any provider that offers SMTP relay credentials works, since this plugin speaks standard SMTP rather than a provider-specific API. Grab your SMTP host/port/username/ password from each provider’s own setup docs: * [SendGrid SMTP setup](https://docs.sendgrid.com/for-developers/sending-email/getting-started-smtp)* [Mailgun SMTP setup](https://documentation.mailgun.com/docs/mailgun/user-manual/sending-messages/)* [Amazon SES SMTP setup](https://docs.aws.amazon.com/ses/latest/dg/send-email-smtp.html)* [Brevo SMTP relay](https://help.brevo.com/hc/en-us/articles/209462765) * [Zoho Mail help center](https://www.zoho.com/mail/help/) ### Does this work with WooCommerce? Yes. WooCommerce order emails, and any other plugin that sends email through `wp_mail()`, automatically use the SMTP settings configured here — no separate configuration needed on the WooCommerce side. ### Does this work with Contact Form 7, WPForms, Gravity Forms, or Elementor Forms? Yes. Any plugin that uses the standard WordPress `wp_mail()` function routes through your configured SMTP settings automatically. ### Can I use this for bulk email marketing or newsletters? No. This plugin is built for transactional email — order confirmations, password resets, contact form notifications, account emails. For bulk marketing sends, use a dedicated service such as Mailchimp, Klaviyo, or Brevo’s marketing product. ### Can I switch from another SMTP plugin to this one? Yes, and there’s nothing destructive about it. Deactivate your current SMTP plugin( or leave it active and just enable this plugin’s “Enable SMTP” toggle — whichever hooks `phpmailer_init` last wins), enter your SMTP credentials here, and send a test email to confirm. Nothing about switching SMTP plugins affects your site’s actual email content or past history. ### How does the free real-time alerting work? Enable monitoring in the Alerts tab and pick a channel — Slack, Microsoft Teams, Google Chat, Discord, or a Custom Webhook. WordPress Cron then opens a real connection to your SMTP server at the interval you set (EHLO, STARTTLS, and AUTH are all tested, not just a TCP port check) with no email actually sent on a successful check. If it fails for as many consecutive checks as your configured threshold, an alert goes out immediately. ### How do I set up Slack alerts? In the Alerts tab, enable the Alert Channel toggle, select Slack, paste your Incoming Webhook URL, and save. Create the webhook at [api.slack.com/messaging/webhooks](https://api.slack.com/messaging/webhooks). ### How do I set up Microsoft Teams alerts? In the Alerts tab, enable the Alert Channel toggle, select Microsoft Teams, paste your Incoming Webhook URL, and save. Follow Microsoft’s [official guide to adding an Incoming Webhook to a Teams channel](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook) to create the URL. ### How do I set up Google Chat alerts? In the Alerts tab, enable the Alert Channel toggle, select Google Chat, paste your Incoming Webhook URL, and save. Follow Google’s [official Chat webhooks quickstart](https://developers.google.com/workspace/chat/quickstart/webhooks) to create the URL from your Chat space’s Apps & Integrations menu. ### How do I set up Discord alerts? In the Alerts tab, enable the Alert Channel toggle, select Discord, paste your Incoming Webhook URL, and save. Follow Discord’s [official “Intro to Webhooks” guide](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks) to create the URL from your channel’s Server Settings Integrations Webhooks. ### How do I set up a custom webhook for Zapier, Make, or n8n? In the Alerts tab, enable the Alert Channel toggle, select Custom Webhook, and paste the URL of your endpoint. Unlike the chat-app channels, this sends a structured JSON payload — `event`, `site_name`, `error_msg`, `consecutive_failures`, and more— built for automation tools to parse rather than for a human to read directly. Docs for the most common automation tools: * [Webhooks by Zapier](https://zapier.com/page/webhooks/)— trigger a Zap from this plugin’s alert payload * [Make (Integromat) webhooks](https://www.make.com/en/help/tools/webhooks)— use a “Custom webhook” trigger module * [n8n Webhook node](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.webhook/)— for self-hosted automation ### Does this support multisite networks? The plugin activates and works on individual sites within a multisite network, but there’s currently no centralized network-wide settings screen — each site is configured independently. ### How does log pruning work? Log entries are pruned automatically once per day via WordPress Cron. Choose to keep either the last 30 days or the last 1,000 records — older entries beyond your choice are removed automatically so the table doesn’t grow unbounded. ### Is my SMTP password stored securely? Yes. The password is encrypted at rest using a key derived from your WordPress installation’s own salts before it’s saved, not stored as plaintext. ### Where are my SMTP credentials stored, and are they sent anywhere? Credentials are stored in the WordPress options table (`wp_options`) on your own server using the standard `update_option()` API. They are never transmitted to ByteCore Stack or any third party — the only network connection your credentials are used for is the SMTP server you configured them for. ### What external services does this plugin use? See the “External Services” section below for a full breakdown — your SMTP server, and optionally whichever alert channel(s) you choose to enable. ### I found a bug or have a feature request — where do I report it? Use the Support forum on this plugin’s WordPress.org page, or reach out via [bytecorestack.com](https://bytecorestack.com/). ## Reviews There are no reviews for this plugin. ## Contributors & Developers “SMTP Manager – Email Logs, Monitoring & Alerts” is open source software. The following people have contributed to this plugin. Contributors * [ bytecorestack ](https://profiles.wordpress.org/bytecorestack/) [Translate “SMTP Manager – Email Logs, Monitoring & Alerts” into your language.](https://translate.wordpress.org/projects/wp-plugins/bcs-smtp-manager) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/bcs-smtp-manager/), check out the [SVN repository](https://plugins.svn.wordpress.org/bcs-smtp-manager/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/bcs-smtp-manager/) by [RSS](https://plugins.trac.wordpress.org/log/bcs-smtp-manager/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.1.0 **Renamed** from “SMTP Manager by ByteCore Stack” to “SMTP Manager – Email Logs, Monitoring & Alerts” — display name only, the plugin slug and all your settings are unchanged. **New alert channels** — Google Chat and Discord join Slack and Microsoft Teams, plus a Custom Webhook channel for Zapier/Make/n8n/your own endpoint. The Custom Webhook channel POSTs a structured JSON payload (`event`, `site_name`, `error_msg`,` consecutive_failures`, etc.) instead of a formatted chat message. All webhook URLs are validated against the provider’s real domain and sent via `wp_safe_remote_post()`. **New WordPress Dashboard widget** — SMTP health status and a 30-day sent/failed/ unconfirmed volume summary, visible without opening the plugin’s settings page. **Admin UI redesign** — full-width layout, boxed/gradient header, cards split into header/body sections, icon tiles on stat boxes, a “Common SMTP Providers” quick- reference card, full mobile/tablet responsive pass (dropdowns, pagination, button widths, tab bar scrolling), a show/hide eye icon on the password field, and AJAX- driven Email Log filtering with a skeleton loading state. **Security** * The SMTP password is now encrypted at rest instead of stored in plaintext (existing installs migrate automatically on next save). * All alert webhook URLs are validated against the provider’s real domain and sent via `wp_safe_remote_post()`, closing an SSRF vector where a malicious/misconfigured webhook URL could make the server POST to internal addresses. * Stopped storing full email message bodies and headers in the Email Log table — only delivery metadata is retained, matching what the UI has always claimed. * Added a 30-second rate limit to “Run Health Check Now” to match the other test/send actions. **Reliability** * Fixed a bug where the automated SMTP health check could report“ healthy” after a bare EHLO even when the server’s STARTTLS upgrade failed, TLS was selected but STARTTLS wasn’t offered, or SMTP auth was never actually verified over an unencrypted connection. * Scheduled/manual delivery reports now report exactly which recipients succeeded and which failed, instead of one pass/fail flag for the whole batch. **Performance**: composite database index on (status, sent_at) for the common Email Log filter combination; CSV export capped at 50,000 rows. **Compatibility**: bumped minimum WordPress version to 5.3 (`wp_timezone_string()`/` wp_date()` require it — the plugin previously declared 5.0 but used functions that didn’t exist yet). **Accessibility & i18n**: AJAX status messages use `role="status" aria-live="polite"`; nearly every user-facing string is now wrapped for translation (previously ~2 out of hundreds, despite declaring a text domain). #### 1.0.0 * Initial release. ## Meta * Version **1.1.0** * Last updated **1 week ago** * Active installations **Fewer than 10** * WordPress version ** 5.3 or higher ** * Tested up to **7.0** * PHP version ** 7.2 or higher ** * Language * [English (US)](https://wordpress.org/plugins/bcs-smtp-manager/) * Tags * [deliverability](https://hat.wordpress.org/plugins/tags/deliverability/)[email](https://hat.wordpress.org/plugins/tags/email/) [email log](https://hat.wordpress.org/plugins/tags/email-log/)[smtp](https://hat.wordpress.org/plugins/tags/smtp/) * [Advanced View](https://hat.wordpress.org/plugins/bcs-smtp-manager/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/bcs-smtp-manager/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/bcs-smtp-manager/reviews/) ## Contributors * [ bytecorestack ](https://profiles.wordpress.org/bytecorestack/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/bcs-smtp-manager/)