by Nicolas Verlhiac
5 (1 reviews)
Custom SMTP: Email Deliverability – FREE & Easy-to-use
Effortlessly configure WordPress SMTP and monitor all sent emails. Built-in email logging with preview, error debugging, and WooCommerce support.
Compatible with WP 7.0.2
v2.5.0
Current Version v2.5.0
Updated 1 month ago
Last Update on 10 Jun, 2026
Refreshed 11 hours ago
Last Refreshed on
Rank
#15,329
—
No change
Active Installs
100+
-25.9%
KW Avg Position
17.3
—
No change
Downloads
3.7K
+1 today
Support Resolved
0%
—
No change
Rating
100%
Review 5 out of 5
5
(1 reviews)
Next Milestone 200
100+
200+
2,563
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 61 more installs to reach 200+
Rank Changes
Current
#15,329
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
5.0
1 reviews
Overall
100%
5
1
(100%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 4 of 4| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| email logger | 8 | — | Tag | 1 day ago |
| mail logger | 12 | — | Tag | 1 day ago |
| deliverability | 16 | — | Tag | 1 day ago |
| smtp | 33 | — | Tag | 1 day ago |
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 2.5.0
- Last Updated
- Jun 10, 2026
- Requires WP
- 6.0+
- Tested Up To
- 7.0.2
- PHP Version
- 7.4 or higher
- Author
- Nicolas Verlhiac
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 5
- Reviews
- 1
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
7K+ installs
#2,740
Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template Kits
30K+ installs
#989
Contact Form 7
10M+ installs
#3
WP Mail SMTP by WPForms - The Most Popular SMTP and Email Log Plugin
4M+ installs
#12
MC4WP: Mailchimp for WordPress
1M+ installs
#34
Frequently Asked Questions
Common questions about Custom SMTP: Email Deliverability – FREE & Easy-to-use
Custom SMTP includes presets for popular providers (Gmail, Outlook, AWS SES, SendGrid, etc.). Just select your provider and settings are auto-filled. List of SMTP Servers Here's a reference list of common SMTP servers: Professional Email Services * SendGrid: smtp.sendgrid.net – TLS – Port 587 * Mailgun: smtp.mailgun.org – TLS – Port 587 * Amazon SES: email-smtp.[region].amazonaws.com – TLS – Port 587 * Brevo (Sendinblue): smtp-relay.brevo.com – TLS – Port 587 * Postmark: smtp.postmarkapp.com – TLS – Port 587 * Mailjet: in-v3.mailjet.com – TLS – Port 587 Consumer Email Providers * Gmail: smtp.gmail.com – TLS – Port 587 * Outlook/Office365: smtp.office365.com – TLS – Port 587 * Yahoo Mail: smtp.mail.yahoo.com – TLS – Port 587 * iCloud: smtp.mail.me.com – TLS – Port 587 * Zoho: smtp.zoho.com – TLS – Port 587 * AOL: smtp.aol.com – TLS – Port 587 * GMX: smtp.gmx.com – SSL – Port 465
* Comcast: smtp.comcast.net – Port 587 * Verizon: outgoing.verizon.net – SSL – Port 465 * AT&T: smtp.mail.att.net – SSL – Port 465 * Orange: smtp.orange.net – Port 25 * T-Online: securesmtp.t-online.de – TLS – Port 587 * 1&1 IONOS: smtp.1and1.com – TLS – Port 587 Note: Settings may vary. Contact your provider for exact configuration.
Yes! Custom SMTP logs all emails sent from WordPress, including WooCommerce order confirmations, shipping notifications, and customer emails.
Yes, it works with Contact Form 7, WPForms, Gravity Forms, and any plugin that uses WordPress wp_mail() function.
Yes. Custom SMTP is fully stateless-compatible and works on ephemeral infrastructure (Docker, Kubernetes, AWS ECS/Fargate, Google Cloud Run, etc.) without shared storage like EFS or NFS. The plugin stores all data in the WordPress database: Settings in wp_options Email logs in a custom database table CSV exports streamed directly to the browser (no temp files) Log purge scheduled via WP-Cron (database-backed) It also works with modern WordPress stacks like Bedrock and Trellis, and can run on a read-only filesystem. Notes for stateless deployments: Ensure WordPress salts (LOGGED_IN_KEY, LOGGED_IN_SALT) are consistent across all instances — the SMTP password encryption depends on them. If DISABLE_WP_CRON is set to true, configure an external cron to trigger wp-cron.php so automatic log purge runs properly. On AWS, prefer the Amazon SES (API) mailer with an IAM role (see the SES question below) — it removes the need to store any SMTP credentials at all.
Yes. Custom SMTP includes an Amazon SES (API) mailer that authenticates through your AWS IAM role (the ECS task role or EC2 instance role) using the AWS default credential chain. You never enter or store an access key, secret key, or SMTP credential — ideal for stateless, containerized WordPress on AWS ECS/Fargate. In Settings > Custom SMTP, choose "Amazon SES (API · IAM role)" as the mailer, set the region and a verified sender address (or inject them as environment variables), and you're done. You can also provide a SES Configuration Set for bounce/complaint tracking. The following environment variables / PHP constants take priority over the saved settings, so the same container image works across environments: SES_REGION (falls back to AWS_REGION) — e.g. eu-west-3 SES_FROM_EMAIL — the verified sender address SES_CONFIG_SET — optional SES configuration set The message is sent as raw MIME, so HTML, attachments, CC/BCC, Reply-To and custom headers are all preserved. The mailer works whether or not the AWS SDK for PHP is installed (it falls back to a built-in signed API client), and SES sends are logged in the Email Logs like any other email. This is different from the existing Amazon SES SMTP preset, which uses SMTP credentials — the new mailer uses the SES API and your IAM role instead.
Yes. Every setting can be forced from a PHP constant or environment variable, which takes priority over the value saved in the database — ideal for immutable Docker images and DISALLOW_FILE_MODS deployments. Use CUSTOM_SMTP_<SETTING> in uppercase, for example: CUSTOM_SMTP_MAILER_TYPE — smtp or ses_api CUSTOM_SMTP_HOST, CUSTOM_SMTP_PORT, CUSTOM_SMTP_SECURE, CUSTOM_SMTP_USERNAME, CUSTOM_SMTP_PASSWORD CUSTOM_SMTP_MAILFROM, CUSTOM_SMTP_FROMNAME, CUSTOM_SMTP_LOG_RETENTION The Amazon SES shortcuts also apply: SES_REGION (or AWS_REGION), SES_FROM_EMAIL, SES_CONFIG_SET. To switch an entire Multisite network to Amazon SES with no database changes, set in your container: CUSTOM_SMTP_MAILER_TYPE=ses_api, SES_REGION=eu-west-3, SES_FROM_EMAIL=no-reply@example.com. Values are resolved from PHP constants, then getenv(), $_ENV, and $_SERVER. The $_SERVER source means FrankenPHP (including worker mode) and Bedrock-style stacks work with plain environment variables — no constants required. On Multisite, the plugin also reads a network-wide option (via get_site_option) beneath any per-site option, so a single configuration can apply to all sites. Fields supplied by the environment are shown read-only in the settings page with a badge naming the source variable. (A password supplied via CUSTOM_SMTP_PASSWORD is used as-is; only stored passwords are encrypted at rest.)
Yes, on WordPress 6.9+. Custom SMTP registers two abilities with the WordPress Abilities API: custom-smtp/connection-health returns the current SMTP state (configured, host, port, encryption, auth, logging retention) — useful for diagnostics and monitoring. custom-smtp/send-test-email triggers a test email through the configured SMTP server. Both abilities are accessible to MCP-compatible AI clients, automation workflows (n8n, Make), and other plugins. They enforce the same capability check as the wp-admin interface (manage_options), so unprivileged users or scripts cannot invoke them.