sarfraj85

Mail Doctor replaces WordPress’ default <code>wp_mail</code> stack with authenticated SMTP or provider APIs plus the operational tooling fast-moving stores need. It is written for merchants, agencies, and reliability teams that want hard proof their receipts, fulfillment notices, and alerts land every time.
<h4>Feature Highlights</h4>
<ul>
<li>Deliverability with guardrails – Route WooCommerce or all site email through your preferred SMTP/API provider, lock the From identity, and fail over gracefully when third-party endpoints go dark.</li>
<li>One-click diagnostics – Send live tests with TLS/auth badges, latency metrics, DNS posture (SPF/DKIM/DMARC), and actionable warnings the moment something drifts.</li>
<li>Reliable retries & queue control – Automatic exponential backoff, manual retry orchestration, Action Scheduler integration, and a “run queue now” control for urgent flushes.</li>
<li>Deep visibility – Searchable logs with <code>.eml</code> downloads, header/body inspection, filterable status views, and CSV exports for audits.</li>
<li>Email template workflow – Version history, diff previews, modal device switcher, and send-test flows for the WooCommerce template editor.</li>
<li>Automation surface – REST API endpoints and WP-CLI commands mirror UI actions so you can script smoke tests, tail logs, or trigger retries in CI/CD pipelines.</li>
<li>Privacy-first options – Hash or redact recipients, tune retention windows, and honour GDPR requests through the bundled exporters/erasers.</li>
<li>Operational alerts – Instant Slack/email failure alerts plus weekly digests summarising throughput, latency, retries, and queue health.</li>
</ul>
<h3>External Services</h3>
This plugin acts as a connector between your WordPress site and third-party email providers. When you configure an external service (SMTP or API), this plugin transmits email data to that provider for delivery.
Data Sent: 
* Sender and Recipient names and email addresses. 
* Email subject, body content (HTML/Text), and headers. 
* Timestamps and potentially the originating IP address.
When Payload is Sent: 
* Immediately whenever an email is triggered by WordPress, WooCommerce, or another plugin, if that specific provider is currently set as your active transport.
Purpose: 
* To reliably deliver transactional emails to user inboxes using the provider’s infrastructure.
Supported Services & Legal Links:
<ul>
<li>
Google / Gmail
<ul>
<li><a href="https://policies.google.com/terms" rel="nofollow ugc">Terms of Service</a></li>
<li><a href="https://policies.google.com/privacy" rel="nofollow ugc">Privacy Policy</a></li>
<li>Endpoints: <code>accounts.google.com</code>, <code>oauth2.googleapis.com</code></li>
</ul>
</li>
<li>
Microsoft / Outlook / Office 365
<ul>
<li><a href="https://www.microsoft.com/en-us/legal/terms-of-use" rel="nofollow ugc">Terms of Use</a></li>
<li><a href="https://privacy.microsoft.com/en-us/privacystatement" rel="nofollow ugc">Privacy Statement</a></li>
<li>Endpoints: <code>login.microsoftonline.com</code>, <code>outlook.office365.com</code></li>
</ul>
</li>
<li>
Twilio SendGrid
<ul>
<li>Links: <a href="https://www.twilio.com/en-us/legal/tos" rel="nofollow ugc">terms of service</a>, <a href="https://www.twilio.com/en-us/legal/privacy" rel="nofollow ugc">privacy policy</a></li>
<li>Endpoints: <code>api.sendgrid.com</code></li>
</ul>
</li>
<li>
Mailgun
<ul>
<li>Links: <a href="https://www.mailgun.com/legal/terms/" rel="nofollow ugc">terms of service</a>, <a href="https://www.mailgun.com/legal/privacy-policy/" rel="nofollow ugc">privacy policy</a></li>
<li>Endpoints: <code>api.mailgun.net</code>, <code>api.eu.mailgun.net</code> (and other region equivalents)</li>
<li>Domain validation: When you click “Verify Domain” in the plugin settings, the plugin queries <code>https://api.mailgun.net/v3/domains/{your-domain}</code> (or the EU equivalent) to check DNS records (SPF, DKIM, MX). Data sent: your Mailgun API key and the domain name. No email content is transmitted during this check.</li>
</ul>
</li>
<li>
Amazon SES
<ul>
<li>Links: <a href="https://aws.amazon.com/service-terms/" rel="nofollow ugc">terms of service</a>, <a href="https://aws.amazon.com/privacy/" rel="nofollow ugc">privacy policy</a></li>
<li>Endpoints: <code>email.us-east-1.amazonaws.com</code>, <code>email-smtp.us-east-1.amazonaws.com</code> (and other <code>*.amazonaws.com</code> region equivalents)</li>
</ul>
</li>
<li>
Postmark
<ul>
<li>Links: <a href="https://postmarkapp.com/terms" rel="nofollow ugc">terms of service</a>, <a href="https://postmarkapp.com/privacy" rel="nofollow ugc">privacy policy</a></li>
<li>Endpoints: <code>api.postmarkapp.com</code></li>
</ul>
</li>
<li>
SparkPost
<ul>
<li>Links: <a href="https://www.sparkpost.com/policies/tou/" rel="nofollow ugc">terms of service</a>, <a href="https://www.sparkpost.com/policies/privacy/" rel="nofollow ugc">privacy policy</a></li>
<li>Endpoints: <code>api.sparkpost.com</code></li>
</ul>
</li>
<li>
Brevo (formerly Sendinblue)
<ul>
<li>Links: <a href="https://www.brevo.com/legal/termsofuse/" rel="nofollow ugc">terms of service</a>, <a href="https://www.brevo.com/legal/privacypolicy/" rel="nofollow ugc">privacy policy</a></li>
<li>Endpoints: <code>smtp-relay.brevo.com</code> (SMTP relay); configurable SMTP host per your provider settings.</li>
<li>This plugin transmits the same email data (sender, recipients, subject, body) to Brevo’s SMTP relay servers when Brevo is configured as the active transport.</li>
</ul>
</li>
</ul>
OAuth Authentication Endpoints:
When you connect Google or Microsoft accounts using OAuth2, this plugin communicates with the following authentication endpoints to obtain and refresh access tokens:
<ul>
<li>
Google OAuth2
<ul>
<li>Authorization: <code>https://accounts.google.com/o/oauth2/v2/auth</code></li>
<li>Token exchange: <code>https://oauth2.googleapis.com/token</code></li>
<li>Data sent: Client ID, authorization code, and redirect URI</li>
<li><a href="https://developers.google.com/terms" rel="nofollow ugc">Google API Terms of Service</a></li>
<li><a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a></li>
</ul>
</li>
<li>
Microsoft OAuth2 (Outlook/Office 365)
<ul>
<li>Authorization: <code>https://login.microsoftonline.com/{tenant}/oauth2/v2.0/authorize</code></li>
<li>Token exchange: <code>https://login.microsoftonline.com/{tenant}/oauth2/v2.0/token</code></li>
<li>Data sent: Client ID, client secret, authorization code, and redirect URI</li>
<li><a href="https://docs.microsoft.com/en-us/legal/microsoft-apis/terms-of-use" rel="nofollow ugc">Microsoft API Terms of Use</a></li>
<li><a href="https://privacy.microsoft.com/en-us/privacystatement" rel="nofollow ugc">Microsoft Privacy Statement</a></li>
</ul>
</li>
</ul>
<h4>Quick Start</h4>
<ol>
<li>Review the documentation link in the Documentation section for the full tour and terminology.</li>
<li>Configure SMTP/API credentials on WooCommerce → Mail Doctor → Settings.</li>
<li>Send a test email from the Status tab and verify DNS/auth posture.</li>
<li>Visit Logs to confirm entries are stored and retries are scheduled as expected.</li>
<li>Enable alerts and weekly digests so the team knows when to act.</li>
</ol>
<h4>Documentation</h4>
Documentation: https://wpdoctorpro.com/docs/mail-doctor/welcome-to-mail-doctor – guides, setup, troubleshooting, and support.
<h4>Privacy controls</h4>
Mail Doctor ships with built-in privacy tooling under Settings → Logging & Privacy:
<ul>
<li>Mask recipient emails: Hashes addresses before storing them in logs.</li>
<li>Redact headers and bodies: Keeps metadata only so sensitive content is not persisted.</li>
<li>Retention windows: Separate sliders for sent, failed, and payload data; shorten for stricter compliance.</li>
<li>GDPR exporter/eraser: WordPress privacy tools are wired to export or anonymise recipient rows on request.</li>
<li>Role-based access: Admin UI and AJAX endpoints are gated by <code>manage_woocommerce</code>/<code>manage_options</code>.</li>
</ul>
<h4>Troubleshooting</h4>
<ul>
<li>Red notices on the Status tab usually indicate DNS or authentication drift—re-run the onboarding checks and confirm credentials with your provider.</li>
<li>If the queue stalls, visit Settings → Retry & Queue and use Run queue now; check your cron runner or Action Scheduler if jobs remain pending.</li>
<li>Use the <code>.eml</code> download from each log entry when escalating to your SMTP provider—they can analyse the exact payload and SMTP transcript.</li>
<li>For privacy incidents, toggle Privacy Mode and shorten retention while you investigate; the GDPR exporter/eraser handles customer requests.</li>
</ul>
<h3>Support & Packaging</h3>
<ul>
<li>Requirements: WordPress 6.0+, WooCommerce (latest), PHP 8.1–8.3 with cURL/JSON; OpenSSL recommended for encrypted secret storage.</li>
<li>Included in download: <code>mail-doctor/</code> plugin folder, <code>Documentation/</code> offline HTML docs, <code>readme.txt</code>, <code>changelog.txt</code>, and <code>LICENSE</code>.</li>
<li>Support/Contact: See the Documentation section for guides and support links. When requesting help, include your WP/Woo versions, provider, and a recent log ID from Mail Doctor → Logs.</li>
</ul>

Mail Doctor

Deliver WooCommerce emails with confidence using authenticated SMTP transports, visual diagnostics, and automated retries.

Nicolas Verlhiac

<h3>Add Mail SMTP settings for WordPress</h3>
Looking to modify the SMTP on your WordPress site? 
Our Custom SMTP solution offers you this possibility, allowing you to easily change your WordPress SMTP settings, ensuring your emails consistently land in the recipient’s inbox.
Custom SMTP solves your email deliverability problems by reconfiguring WordPress to use a proper SMTP provider when sending emails.
What’s more, our intuitive settings page and comprehensive documentation will guide you through the process, making the task of modifying your SMTP settings easier than ever.
Custom SMTP is a free tool, packed with all the essential features you need to send your WordPress emails with absolute confidence!
Built for modern WordPress: WordPress 7.0 ready, PHPMailer 7.0.2 compatible, stateless / cloud-ready (Docker, Kubernetes), and fully translated in English and French.
<h3>Amazon SES API — keyless sending with IAM roles</h3>
Running WordPress on AWS (ECS Fargate, EC2, App Runner)? Custom SMTP can send through the Amazon SES API authenticated entirely by your container or instance IAM role — with no access keys, no secret keys, and no SMTP credentials stored anywhere. The plugin relies on the AWS default credential chain (the ECS task role / EC2 instance role), so your secrets never live in the database or the settings page.
This is the cleanest, most secure way to send from a containerized, 12-factor WordPress:
<ul>
<li>Zero stored secrets — authentication comes from the IAM role attached to the task/instance, not from keys pasted into wp-admin.</li>
<li>Full message fidelity — HTML, attachments, CC/BCC, Reply-To and custom headers are preserved (the message is sent as raw MIME); BCC recipients stay hidden.</li>
<li>SES Configuration Sets — optional, for bounce/complaint tracking and CloudWatch metrics.</li>
<li>Environment-driven — region, sender address and configuration set can be injected as environment variables / PHP constants (<code>SES_REGION</code> / <code>AWS_REGION</code>, <code>SES_FROM_EMAIL</code>, <code>SES_CONFIG_SET</code>), so the same image ships across environments without touching the database.</li>
<li>No extra dependency required — works whether or not the AWS SDK for PHP is present; when it isn’t, a built-in, dependency-free signed API client is used.</li>
<li>One-click test — send a test email and get back the SES MessageId.</li>
</ul>
<h3>Config-as-code & Multisite (immutable deployments)</h3>
For immutable Docker images, <code>DISALLOW_FILE_MODS</code> setups and large networks, every setting can be forced from the environment — no database writes at deploy time:
<ul>
<li>Any setting via a constant or env variable — define <code>CUSTOM_SMTP_<SETTING></code> (e.g. <code>CUSTOM_SMTP_MAILER_TYPE=ses_api</code>, <code>CUSTOM_SMTP_HOST</code>, <code>CUSTOM_SMTP_LOG_RETENTION</code>) and it overrides the saved value everywhere. The Amazon SES shortcuts (<code>SES_REGION</code> / <code>AWS_REGION</code>, <code>SES_FROM_EMAIL</code>, <code>SES_CONFIG_SET</code>) keep working too.</li>
<li>Activate a mailer network-wide with one variable — set <code>CUSTOM_SMTP_MAILER_TYPE=ses_api</code> in the container and every site uses Amazon SES, with zero per-site configuration and no custom <code>option_*</code> filter.</li>
<li>Multisite network settings — on a network, settings are read from the network-wide option (<code>get_site_option</code>) beneath any per-site option, so one configuration can apply to the whole network.</li>
<li>Visible in wp-admin — any field supplied by the environment is shown read-only with a “from <code>VARIABLE</code>” badge, so admins see exactly what the platform controls.</li>
</ul>
<h3>Built-in Email Logging</h3>
Never wonder if your emails were sent again. Custom SMTP automatically logs every email sent from your WordPress site – including WooCommerce order notifications, contact form submissions, and password resets. Preview email content directly in wp-admin, debug delivery issues with detailed error messages, and export logs for compliance.
<h3>Configuration Options</h3>
You can set the following options:
<ul>
<li>From Name & Email – Specify the sender name and email address for all outgoing emails</li>
<li>SMTP Host – Your email provider’s server (e.g., smtp.gmail.com)</li>
<li>SMTP Port – Common ports: 587 (TLS), 465 (SSL), 25 (None)</li>
<li>Encryption – Choose between None, SSL, or TLS</li>
<li>Authentication – Enable/disable SMTP authentication for relay servers</li>
<li>Username & Password – Your SMTP credentials (password stored encrypted)</li>
<li>Provider Presets – One-click configuration for Gmail, Outlook, iCloud, SendGrid, AWS SES, and more</li>
<li>Amazon SES API (IAM role) – Send through the Amazon SES API with no stored credentials, authenticated by your AWS task/instance role</li>
</ul>
<h3>Key Features</h3>
SMTP Configuration 
* Configure any SMTP server (Gmail, Outlook, SendGrid, Mailgun, AWS SES, etc.) 
* Support for SSL/TLS encryption 
* Optional SMTP authentication for relay servers 
* Test connection without sending emails 
* Send test emails to verify configuration
Amazon SES API (keyless, IAM role) 
* Send via the Amazon SESv2 API authenticated by your AWS IAM role — no access keys or SMTP credentials stored 
* Ideal for AWS ECS/Fargate, EC2 and other containerized, stateless deployments 
* Preserves HTML, attachments, CC/BCC, Reply-To and custom headers (raw MIME) 
* Optional SES Configuration Set for bounce/complaint/CloudWatch tracking 
* Region, sender and configuration set configurable via environment variables or constants 
* Works with or without the AWS SDK for PHP (built-in signed API client fallback) 
* “Send Test Email” returns the SES MessageId
Email Logging & Debugging 
* Zero configuration – Logging works out of the box 
* Track all emails sent from WordPress, WooCommerce, Contact Form 7, and any plugin 
* View delivery status (sent/failed) with detailed error messages 
* Debug wp_mail errors easily – See exactly why emails fail 
* Resend failed emails – Re-send a failed message straight from the logs after fixing your configuration 
* Store email headers for advanced troubleshooting 
* Search by recipient, subject, or status 
* Filter by date range (Today, 7 days, 30 days) 
* Export logs to CSV for reporting and compliance
Email Preview & Content 
* Preview email body directly from wp-admin – No need to send test emails 
* View HTML source code of any logged email 
* Outlook-style sidebar for quick preview 
* Download any email as HTML file for archiving 
* Optional content storage (disabled by default for privacy)
Deliverability 
* Cooperates with the automatic Envelope-From / Return-Path behavior introduced in WordPress 6.9 — improves SPF, DKIM and DMARC alignment on strict hosts (AWS SES, Postmark, etc.) 
* PHPMailer 7.0.2 compatible (the version bundled in WordPress 7.0) 
* UTF-8 and emoji handled end-to-end in subjects, bodies, and headers
Privacy & GDPR-friendly 
* SMTP password encrypted at rest (AES-256-CBC) 
* Configurable log retention with automatic purge (30 days by default) 
* Email content storage can be disabled in one click from the settings 
* Email preview rendered in a sandboxed iframe — no JavaScript execution from logged emails 
* All data stays in your WordPress database — no third-party calls
Security 
* SMTP password encrypted in database (AES-256-CBC) 
* All admin actions protected with nonces 
* Capability checks on all operations
Stateless & Cloud-Ready 
* Fully compatible with stateless WordPress hosting (containers, Kubernetes, AWS ECS/Fargate, etc.) 
* Works with Bedrock, Trellis, and other modern WordPress stacks 
* Zero filesystem writes – all data stored in the database 
* No shared storage (EFS/NFS) required between instances 
* Safe to run on read-only filesystems
AI & Workflow Integration (WordPress 6.9+) 
* <code>custom-smtp/connection-health</code> — read the current SMTP state (configured, host/port/encryption/auth, log retention) from any tool 
* <code>custom-smtp/send-test-email</code> — trigger a test email through your configured SMTP server 
* Compatible with MCP-enabled AI assistants, automation tools (n8n, Make), dashboards, and other plugins via the WordPress Abilities API 
* Protected by capability checks (<code>manage_options</code>) — same security boundary as the wp-admin interface

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.

Mail Doctor vs Custom SMTP: Email Deliverability – FREE & Easy-to-use