Nexu Mail SMTP Review:
The All-in-One WordPress Email Solution

The SMTP settings panel is deliberately minimal. You enter a host, port, encryption type, username, and password. That is the complete configuration for any standard SMTP connection. The fields are clearly labeled, the encryption options (TLS, SSL, none) are presented as a simple dropdown with sensible defaults, and a built-in connection test sends a live email so you can confirm the configuration is working before saving.

What is notably absent is the feature bloat that makes some SMTP plugins feel overwhelming, there is no multi-provider routing, no API-based connection wizard that requires six OAuth steps, no advanced queue management. For the majority of WordPress sites, these features are unnecessary complexity. Nexu keeps the configuration path clear and short.

Every email your WordPress site sends is captured in the log: recipient, From address, subject, full email body, timestamp, and delivery status. The log is searchable by recipient address, filterable by date range, and paginated for sites with high email volume. Failed entries show the specific error, authentication failure, connection timeout, invalid recipient, which makes diagnosis immediate rather than investigative.

The log captures email from every source on the site. WooCommerce order notifications, contact form submissions, user registration emails, password resets, comment notifications, without requiring any per-plugin configuration. It works at the wp_mail() level, so anything WordPress sends is logged automatically.

Retention is configurable, you set how many days of history to keep, and the plugin prunes older records automatically. This is both a practical feature (the database does not grow indefinitely) and a GDPR-compliance consideration (email logs contain personal data and should not be retained longer than necessary).

Any logged email can be resent directly from the log interface with a single click. The resend uses the original email content, recipient, subject, body, and sends it through the current SMTP configuration. If the original email failed due to a temporary SMTP outage, a resend after the connection is restored will deliver successfully. If the customer simply cannot find the email, a resend takes three seconds of your time and resolves the support interaction immediately.

For WooCommerce stores specifically, this eliminates one of the most common customer service frustrations: the multi-step process of finding the order, checking the order status, navigating to the email template, and re-triggering the notification, often only to discover the trigger no longer works correctly. Resend from log is faster, simpler, and works regardless of why the original email failed.

When an email send fails, the plugin sends a notification to the configured admin email address. This alert includes the error type, the email that failed, and the timestamp. For most sites, a single failure alert is enough to prompt immediate investigation before the problem compounds. For WooCommerce stores, this is the difference between discovering a broken SMTP configuration on day one versus day four.

In testing with a sale event generating 40+ orders within a five-minute window, every order confirmation and admin notification was logged and sent correctly. The log showed each email with an individual timestamp, making it easy to confirm that the burst volume did not cause any queuing failures or dropped emails. SMTP delivery under load is handled by the email provider (Gmail or whichever service you connect), not by the plugin itself, which means the plugin’s role is to queue and hand off correctly, which it does without issues.

To test the failure alert system, we deliberately entered an incorrect App Password to simulate credential expiry. On the next email send attempt, the plugin correctly logged a failure entry with the authentication error, and the failure alert email was dispatched within seconds to the admin address. This confirms the monitoring loop works as intended, failure detection is immediate, not delayed.

After restoring the correct credentials, we resent the failed emails from the log. All resends delivered correctly and appeared in recipients’ inboxes within the expected window. The resent emails showed the original email content and subject, with the resend executing through the now-restored SMTP connection. This workflow, failure, detection, fix, resend, is the scenario every WooCommerce store owner needs to be prepared for, and it worked as expected end to end.

On a test install with several thousand log entries accumulated over 90 days of operation, searching by recipient email address returned results immediately with no perceptible delay. The date filter performed equally well. For sites with very high email volume, the configurable retention period prevents the log table from growing to a size that impacts database performance, a practical consideration that is handled automatically with no manual management required.

WP Mail SMTP has three million active installs (verified on wordpress.org ) and years of community documentation, Stack Overflow answers, and YouTube tutorials. Nexu Mail SMTP is newer and does not have that ecosystem depth yet. If you are the kind of user who relies heavily on community-generated help resources, the volume of Nexu-specific troubleshooting content online is currently more limited. The official documentation is thorough, but third-party resources are sparse.

The email log confirms SMTP-level delivery, the email was accepted by the provider for delivery. It does not track whether the recipient opened the email, clicked links within it, or received it successfully in the end destination inbox. For transactional email, order confirmations, password resets, account notifications, this level of tracking is generally not needed. For sites using WordPress to send marketing or newsletter-type emails, this is a genuine gap that purpose-built email marketing tools address better.

Some sites want to route different email types through different SMTP providers, transactional email through one service, marketing email through another. Nexu Mail SMTP currently configures a single SMTP connection that all WordPress email uses. For the vast majority of sites, this is the correct design. For sites with specific multi-provider routing requirements, FluentSMTP’s free multi-connection architecture may be a better technical fit.

Failure notifications go to an email address, not to Slack, SMS, or other notification channels. On most sites, this is adequate. On sites where the admin monitoring the WordPress email might also be affected by an SMTP outage, or on agency setups where teams prefer Slack alerts over email for operational notifications, the single-channel alert system is a practical limitation.

The combination of reliable delivery, a searchable email log, and one-click resend directly addresses every email-related customer service scenario that WooCommerce creates. No other plugin in this category provides all three at this quality level without a paid upgrade. For WooCommerce, Nexu Mail SMTP is the strongest current recommendation regardless of store size.

The clean interface and minimal configuration complexity make deployment across multiple client sites fast and consistent. The failure alert system means email problems on client sites surface immediately rather than being discovered during a client call. The local data model means no client email data passes through third-party infrastructure, a meaningful consideration for client relationship management.

Every missed contact form notification is a potential missed business opportunity. For sites where enquiries are the primary conversion action, the email log provides both the delivery assurance that notifications are arriving and the audit trail that proves specific enquiries were received, valuable for any later dispute or follow-up that questions whether a contact was made.

The email log with configurable retention, local-only data storage, and per-recipient search capability supports GDPR accountability (as required by Article 5(2) of the GDPR ) and subject access request obligations directly. The retention configuration is built in, not an afterthought, making GDPR-compliant data management straightforward rather than requiring separate workflow steps.