SendForce Mail SMTP Relay — Free WP SMTP & Email API Plugin for Amazon SES, SendGrid, Mailgun, Brevo, Postmark, Zoho ZeptoMail & Gmail

Changelog

For the complete release history with full detail on every change, see CHANGELOG.md (also bundled with the plugin) or open the What’s New tab inside SendForce in your WordPress admin. The section below is condensed to fit within WordPress.org’s 5,000-word changelog limit.

1.0.33

• Security: Hardened alert webhooks against SSRF (server-side request forgery). User-supplied webhook URLs (Slack, Discord, Microsoft Teams, Google Chat, and the generic Webhook channel) are now validated before SendForce sends to them — any URL that resolves to a private, loopback, link-local, or reserved IP range (including the cloud metadata address 169.254.169.254) is refused. Both IPv4 and IPv6 are checked. A new sendforce_allow_private_webhook_hosts filter lets self-hosted setups opt back in for legitimate internal collectors.
• Fix: Attachment filenames with non-ASCII or special characters now encode correctly across all API providers. Filenames are RFC 5987 / RFC 2231 encoded (multipart/form-data for Mailgun; raw MIME for Amazon SES and Gmail), so UTF-8 names — e.g. WooCommerce invoices named with accents or non-Latin scripts — arrive intact instead of as garbled text or being silently dropped by the provider. Also closes an edge case where a CR/LF character in a filename could inject MIME headers.
• Performance: Dashboard and chart statistics are now cached. The dashboard’s lifetime sent/failed counts and the daily-activity chart (which previously ran up to 180 COUNT queries per load on the 90-day range) are cached for one hour and refreshed automatically whenever an email is logged or logs are deleted. The admin dashboard is noticeably faster on sites with large email logs.

1.0.32

• Compatibility: Verified compatible with WordPress 7.0 — bumped the “Tested up to” header so the wp.org compatibility warning clears for sites already running the latest WordPress.
• Maintenance: Refreshed the wp.org plugin directory tags (email, email log, gmail, outlook, smtp) to better match how users actually search. gmail and outlook in particular are high-intent searches that match our existing Gmail and Microsoft 365 OAuth flows but weren’t previously tagged.

1.0.31

• Fix: Email Log “Connection” filter was dropped when paginating or exporting (regression introduced with the new dropdown in 1.0.30). Picking a connection, then clicking page 2 or “Export CSV/JSON”, silently reset the filter and returned all providers. Both the pagination base URL and the export URL now preserve the active provider value, so paging through SendGrid-only results stays SendGrid-only and “Export CSV” of a filtered view exports just the filtered rows.
• Polish: Accessibility — icon-only View button on the Email Log row and the Retry / Delete buttons on the Queue row now expose an aria-label so screen readers announce them correctly (was relying on title alone, which most assistive tech ignores).
• Polish: Bulk action counter on the Email Log (“X item(s)”) now uses proper plural forms via _n(), so non-English locales can translate the singular and plural cases separately instead of inheriting the awkward English “(s)” suffix.
• Polish: Settings → Developer Debug toggle label changed from “Mirror SMTP & API debug output” to “Mirror SMTP and API debug output” (a literal & in a translation string is a portability gotcha for some PO editors).
• Polish: Alerts tab — added viewBox (camelCase) to the SVG wp_kses whitelist alongside the existing lowercase viewbox, so channel-logo SVGs render correctly regardless of which casing the source file uses.
• Internal: Renamed $current_user to $sendforce_current_user in the Email Test template for prefix consistency with the rest of the file (avoids accidentally shadowing WP’s globally-scoped $current_user in deeply included contexts).

1.0.30

• New: Filter Email Log by connection. A new “Connection” dropdown in the Email Log filter bar lets you narrow the table down to emails sent through a specific provider (Amazon SES, SendGrid, Microsoft 365, etc.). Useful when you run several connections side-by-side and want to audit just one — e.g. “show me everything WooCommerce sent via SendGrid this week”. Options are populated from connections that actually have log entries (no empty dropdown choices). Existing log rows from before 1.0.30 don’t carry a provider value and stay visible under the “All connections” default.
• New: “Copy diagnostic snapshot” button on the Email Log detail modal. Bundles the log ID, timestamp, status, error, headers, attachments, and the (already-redacted) raw API request/response into one clipboard-friendly text block — pre-formatted for pasting straight into a support ticket. Plugin / WordPress / PHP versions are included automatically. No more copy-paste-merge of six different fields when reporting an issue.
• Internal: Added provider column to wp_sendforce_logs (varchar(50), indexed). Populated automatically going forward from the captured debug payload (when available) or the active connection’s configured provider. Existing rows are not back-filled; only new log entries get the column populated. dbDelta handles the schema migration on plugin upgrade.

1.0.29

• Fix: Stray gray “pill” elements rendering on the What’s New tab (introduced in 1.0.28). The changelog accordion’s markdown-to-HTML converter wrapped backtick-delimited text in <code> tags but didn’t escape the inner content first — so when a bullet contained literal <tag> text inside backticks (very common in technical changelogs), the browser interpreted the embedded text as a real HTML tag and produced floating empty <code> elements that rendered as gray pills against the page background. Fix: esc_html() the raw line before applying the markdown transformations. The two regex rules (**bold** → <strong> and backtick → <code>) now run on already-escaped text, guaranteeing balanced tags and no HTML injection from bullet content. Affects 1.0.28 only.
• Fix: WordPress 6.7+ “Translation loading triggered too early” notice caused by the custom cron schedule’s display label being translated inside the cron_schedules filter. The filter fires whenever WP looks up scheduled events (which can happen before init, during plugins_loaded or even setup_theme), so calling __( …, 'sendforce-mail-relay' ) there ran the translation function before the textdomain was loaded. Both filter callbacks (in the activator and the mailer) now use a literal English string for the cron schedule’s display label — that label is only shown in dev tools like WP Crontrol or wp-cli cron list, never user-facing, so leaving it untranslated is harmless. Resolves the deprecation notice on sites running WP_DEBUG with WP 6.7 or newer.

1.0.28

• New: Test send now shows the full provider response inline on the Email Test page. When a test fails the headline shows the short reason (“Failed to send via Microsoft 365 API”) and a new “Provider response” panel below it shows the raw HTTP response body — pretty-printed when it’s JSON, with a one-click Copy button for support tickets. Previously the full Graph/SES/Mailgun response was only visible by clicking into the Email Log; users debugging a misconfiguration now see everything they need without leaving the test page.
• New: HTTPS warning on webhook URL fields (Slack, Discord, Microsoft Teams, Google Chat, generic Webhook). As soon as you paste/type a URL starting with http:// an inline red warning appears explaining that the alert message (site name, failed recipient, error details) would be sent unencrypted. Catches typos and homemade webhook receivers before save.
• New: “Welcome to v{X.Y.Z}” admin notice after the plugin updates, with a one-click button to the in-admin “What’s New” tab. Per-user dismissible, only shows once per version, never on fresh installs or on SendForce’s own settings pages (where the tab is already visible). Helps users discover what changed without having to read the wp.org changelog page.
• New: Failure-alert rate limiting, default 5-minute window per channel. A burst of failed sends (e.g. WooCommerce sending 100 order emails through an expired API key) no longer floods Slack/Telegram/Discord/Teams with 100 identical pings — within the window the first one fires, the rest are counted and rolled up into a “(+N additional failures were suppressed)” note on the next alert after the window expires. Filter sendforce_alerts_throttle_seconds to change the window length, set it to 0 to disable throttling entirely.
• Docs: Added CHANGELOG.md with the complete, full-detail release history for every version (no length limit). The condensed Changelog in this readme.txt covers the WordPress.org 5,000-word cap; CHANGELOG.md carries the full story for anyone who wants it.
• In-admin: The What’s New tab now reads from CHANGELOG.md when present (falls back to readme.txt). Browse every release’s full bullet list inline in WordPress without going to wp.org or GitHub.
• Older entries (1.0.0 – 1.0.20) in this readme.txt are now one-line summaries; their full detail lives in CHANGELOG.md and the in-admin Changelog accordion. Recent releases (1.0.21+) remain fully detailed in both places.

1.0.27

• Security (defense-in-depth): Bulk-delete logs and queue retry/delete actions now require manage_options capability in addition to the existing nonce check. The forms that issued these requests already live on admin-only pages, so a non-admin couldn’t normally obtain a valid nonce — but explicit capability checks match WordPress.org Plugin Check expectations and protect against any future flow that might mint a nonce in a less-restricted context.
• Privacy: Email Log now stores only the filename basenames of attachments instead of full filesystem paths. Previously rows like /var/www/example.com/wp-content/uploads/woocommerce_uploads/2026/invoice-12345.pdf were stored verbatim — leaking the server directory layout, shared-hosting username paths, and customer order IDs from WooCommerce invoice filenames. From 1.0.27 the same row stores only invoice-12345.pdf. Existing rows are not rewritten; only new log entries get basename-only.

1.0.26

Sending — attachments and multipart_text across all 18 API providers.

• New: Attachments now work in API mode for every supported provider. 1.0.25 added it for Amazon SES and Gmail; 1.0.26 closes the gap for the remaining 16: SendGrid, Brevo, Mailgun, Postmark, Mailjet, MailerSend, Mandrill, Pepipost / Netcore, SocketLabs, SMTP2GO, SMTP.com, SendLayer, SparkPost, Elastic Email, Resend, and Moosend. Plugin-attached files (WooCommerce PDF invoices, Contact Form 7 / WPForms / Gravity Forms uploads, LearnDash / LifterLMS certificates, anything passed to wp_mail()‘s 5th argument) are now base64-encoded into each provider’s native JSON schema and delivered through the API.
• New: “Multi-Part Plain Text” setting now applies to API-mode sends across the board. When the message is HTML and the toggle is on, the auto-derived text/plain alternative is included via each provider’s native multipart fields. Improves deliverability — Gmail and other inbox providers favour multipart-alternative messages, and plain-text-only clients get a readable fallback. Previously this setting was silently ignored in API mode for the 16 providers covered here.
• Known limitation: Moosend’s transactional API has a single Content field with no IsContentHtml companion for both parts, so it can’t represent multipart_text — its attachments work, just not the dual-body part.
• Special-case: Mailgun’s attachment endpoint requires multipart/form-data (not JSON like the other 17), so a new build_multipart_form_data() helper in the base class assembles the request body correctly while still capturing the response into the debug log.
• Internal: Two new base-class helpers — prepare_attachments() (base64 + MIME-type detection + safe file reads) and get_plain_text_alt() (HTML→plain conversion when multipart_text is on) — give each provider ~5 lines of mapping code instead of duplicating the same boilerplate 18 times.

Email Queue — actual error messages + on-demand processing.

• Fix: Queued emails that fail now record the actual provider error in the queue row’s error column. Previously every failure showed a generic “Failed to send email.” message, regardless of whether the cause was an expired OAuth token, an unverified sender domain, a wrong API key, or a network glitch. The queue processor now hooks wp_mail_failed during each send attempt and stores the real WP_Error message (e.g. AADSTS70008: refresh token expired, MessageRejected: Email address is not verified, Domain not found). Users on the Queue tab can finally see WHY a send failed without digging into the Email Log.
• New: “Process Queue Now” button on the Queue tab. Triggers the same processor that WP-Cron runs every 5 minutes, but on demand — useful right after fixing a connection or when testing the queue end-to-end. Disabled when there’s nothing queued; only visible when the queue is actually enabled in Settings.
• New: Queue-disabled info notice on the Queue tab. Previously visiting the tab with the feature off showed an empty table with no explanation; now there’s a clear “Queue is disabled — emails are sent immediately. Enable in Settings → Email Queue.” banner with a deep link.
• New: “Next automatic run” timestamp shown above the queue list when the queue is enabled, formatted using the site’s date/time format. Removes the mystery of “when will my queued emails actually go out”.
• Fix: Test sends bypass the queue. With queue mode enabled, clicking “Send Test” used to queue the message and report immediate success — but the actual delivery wouldn’t happen until the next cron run, which made the test page useless for verifying provider configuration. A new one-shot SendForce_Queue::$bypass_once flag tells the queue interceptor to skip the next wp_mail call, so test sends always go out synchronously regardless of queue mode.

Admin — release history and roadmap in one place.

• New: “What’s New” tab combines the upcoming-features roadmap (formerly “What’s Next”) and the full release history into one navigation entry. Roadmap cards render at the top as before; the changelog sits below as a collapsible accordion.
• New: Collapsible changelog accordion, FAQ-style. Each release row shows version + change count; click to expand the bullets. The current installed version auto-expands; everything else stays collapsed by default — ~60% less vertical space than rendering everything flat. Uses native HTML <details>/<summary> so it’s keyboard-accessible and works without JavaScript.
• Renamed: “What’s Next” → “What’s New”. The old ?tab=upcoming and ?tab=changelog URLs both still resolve as back-compat aliases so any bookmarks or in-plugin links keep working.

1.0.25

• New: Email attachments now work with Amazon SES and Gmail API modes (multipart/mixed). Multi-Part Plain Text setting also applies in API mode.
• Fix: Non-ASCII subjects and From-names (Café, résumé, 주문) are now RFC 2047 base64-encoded.
• Refactor: SES and Gmail mailers share a single build_raw_mime() helper. Full release detail in CHANGELOG.md.

1.0.24

• Fix (critical): Microsoft 365 / Gmail OAuth AADSTS50011 redirect URI mismatch. Root cause was add_query_arg() not URL-encoding values, leaving & characters bare inside redirect_uri. Switched to http_build_query() with PHP_QUERY_RFC3986.
• New: OAuth consent now opens in a popup window with graceful redirect fallback; callback splash signals the parent via localStorage + postMessage + closed-polling (survives COOP severance).
• Fix: Microsoft 365, Amazon SES, Gmail, and Mailgun send failures now surface the actual provider error in the UI and Email Log (all four mailers now route through make_request()).
• New: Tolerate users pasting Bearer TOKEN / Zoho-enczapikey TOKEN prefixes — auto-stripped before constructing the auth header. All API keys are also auto-trimmed.
• New: Per-provider API-key hint under the field. Client-side + server-side rejection of GUID-shaped Azure Secret IDs pasted into the Client Secret field. Rewrote Gmail and Microsoft 365 OAuth setup instructions. Full release detail in CHANGELOG.md.

1.0.23

• Fix: OAuth redirect URI is now constructed defensively against third-party admin_url filters (Wordfence, LiteSpeed Cache).
• i18n: Email Log “Next run” timestamp now uses the site’s configured date/time format.
• Hardening: Expanded wp_kses SVG whitelist used for channel logos on the Alerts tab.

1.0.21

• New: “Clean Now” button on the Email Log + auto-clean status row showing retention, next run, and a deep-link to settings.
• New: “via rule: ” badge on Email Log entries when an email was redirected by a Smart Routing rule.
• New: “Connection missing” warning on routing rule cards when a rule points at a deleted connection.
• New: Real channel logos on the Alerts tab (Slack, Discord, Teams, Telegram, Google Chat, Pushover, Webhook).
• Improvement: Test Routing tool now uses the exact same matcher as the live mailer (no drift between predicted and actual routing).
• Fix: Alert channels were occasionally wiped when saving the Summary Email form. Full release detail in CHANGELOG.md.

1.0.20

• Admin top navigation layout fixes at narrow widths (tablet/mobile, mid-size laptops). Tab labels collapse to icon-only below 1340px. Logo gets proper left padding on mobile.

1.0.19

• New: Smart Routing Rules — send different emails through different connections by recipient domain/pattern, source plugin (auto-detected for WooCommerce, CF7, WPForms, Gravity Forms, Ninja Forms, Fluent Forms, Forminator, EDD, MemberPress, LearnDash, MailPoet, BuddyPress, bbPress), subject contains, time of day, weekday. Top-down evaluation, first match wins. Includes Routing tab, inline rule editor, master enable toggle, from_email / from_domain conditions, “via rule” badge in Email Log, starter presets, “What’s Next” roadmap tab, styled confirm dialogs.

1.0.18

• Fixed misleading “Connected” status on Gmail / Microsoft 365 OAuth panel — now checks API mode + Client ID + Client Secret + refresh token all present (not just any password field value). Added amber “partial credentials” state. Hint to switch to API mode when in SMTP. Polished status indicator dot.

1.0.17

• Initialize oauth_email field on newly created connections so the schema is consistent from save time.

1.0.16

• New: One-click “Connect with Google” and “Connect with Microsoft” OAuth buttons replace manual refresh-token generation via OAuth Playground / Azure CLI. Refresh token captured automatically, stored encrypted, panel shows “Connected as user@example.com” with Disconnect button. Bring-your-own-credentials — no third-party OAuth proxy. Microsoft 365 supports both delegated and app-only flows. Setup help panel with copy-able redirect URI.

1.0.15

• Audited all 20 provider integrations against current docs. 18 verified spec-compliant. Fixed Moosend HTML content-type detection (explicit IsContentHtml flag in both HTML and plain-text paths).

1.0.14

• Fixed Email Queue orphan-row bug: rows stuck in “processing” state after cron timeout / PHP crash now recover via a 10-minute lease (next_retry_at) on the next cron run.

1.0.13

• Security: hardened PHP-mail fallback against header injection (strips CR/LF/null from To, Subject, headers). Validated attachment paths against safe roots (prevents path traversal). Sanitized fallback-connection label. Server-side wp_strip_all_tags on provider errors returned to the browser.

1.0.12

• Renamed “Default Connection” → “Primary Connection” throughout the admin UI (internal storage key unchanged). Provider status dot reflects configuration status (not brand colour). Fixed fallback flow so wp_mail() returns true on fallback success; clearer recovery message. Suppressed spurious SMTP-warning when active path was API or PHP-Mail.

1.0.11

• Plugin Name header is now clean brand name “SendForce Mail Relay” (was long SEO title); Description is a single-line summary. WordPress.org listing keeps the longer SEO title for directory search.

1.0.10

• New UI controls for Developer Debug toggle and Max Retry Attempts (1–10). Hardened From-email validation (admin notice on invalid). Replaced native <select> dropdowns with branded styled component (full keyboard support — Arrow/Enter/Escape). Default/Fallback selectors auto-refresh after connection save. Form-control polish (chevron, focus ring, hover, disabled states).

1.0.9

• WordPress.org listing title tuned to “SendForce Mail SMTP Relay — Free WP SMTP & Email API Plugin for Amazon SES, SendGrid, Mailgun, Brevo, Postmark, Zoho ZeptoMail & Gmail” for better directory search. Internal product name unchanged.

1.0.8

• New: Automatic fallback connection — when primary send fails, SendForce retries via configured fallback. Works across any API → API, API → SMTP, SMTP → API, SMTP → SMTP, or any → PHP-mail combination. Both attempts logged; recovered emails get a “Recovered via fallback” badge. Improved readme Description for WordPress.org discoverability.

1.0.7

• Public display name updated for WordPress.org search index discoverability. Refreshed Tags to highest-volume search terms. Polished connection-row Edit/Delete buttons with dashicons. Added Dashboard / Settings / Email Log / Queue / Test / Alerts sub-menu entries.

1.0.6

• Shortened WordPress admin sidebar label to “SF Mail Relay” so it fits one line. Added sub-menu entries reachable from sidebar fly-out.

1.0.5

• Removed accidental .DS_Store file from assets/images/providers/. Added phpcs:ignore annotations with rationale to interpolated table-name $wpdb queries. Restructured WP-CLI log-delete query for proper phpcs handling.

1.0.4

• Updated bundled Chart.js to 4.5.0. Expanded External Services section in readme. Removed inline <style>/<script> blocks from PHP output (proper enqueue). Surface actual provider HTTP status / response body in failure messages. Added “Raw API request / response” panel to Email Log detail modal. Masked-dots placeholder for saved password/API-key fields. Hardened secret redaction (covers client_secret, response bodies, malformed-JSON fallback). Defused CSV formula injection on log export. Gated on-load DB schema upgrade to admin/WP-CLI. Added confirmation prompts to destructive WP-CLI commands.

1.0.3

• Added WP-CLI commands (wp sendforce test, queue, log, sysinfo). Added developer hooks (sendforce_before_send, sendforce_after_send, sendforce_log_entry, sendforce_api_request, sendforce_api_response). Added Developer Debug setting to mirror SMTP/API debug to debug.log. Added raw API request/response capture in new debug_data log column (with Authorization redaction). Email Log export as CSV/JSON. “Copy Debug Info” button on Email Test screen. Replaced stale “SMTP-Manager” User-Agent on Resend with “SendForce-Mail-Relay”.

1.0.1

• Added Microsoft 365 Graph API and Gmail API support. Added 5 new providers (SendLayer, Mailjet, MailerSend, Mandrill, Resend). Added Zoho ZeptoMail API. Added 3 new notification channels (Microsoft Teams, Google Chat, Custom Webhook). SVG provider logos. Collapsible provider grid. Fixed multiple API mailer bugs (SendLayer field names, Pepipost endpoint, SparkPost CC, SES BCC, MailerSend Reply-To). Added CC/BCC/Reply-To to Elastic Email, SMTP2GO, SMTP.com, SocketLabs, Moosend, Pepipost. Auto-set first connection as Default. Bundled Chart.js locally. Fixed all Plugin Check warnings. Renamed main file to sendforce-mail-relay.php.

1.0.0

• Initial release. SMTP with 18 provider presets. HTTP API for 12 providers (SendGrid, Mailgun, SES, Brevo, SparkPost, Postmark, Elastic Email, SMTP2GO, Pepipost, SMTP.com, SocketLabs, Moosend). From name/email override. Email logging with search/filter. Email queue with exponential backoff retry. Email Test page with live SMTP debug. AES-256-CBC encrypted credential storage. Auto log cleanup. Modern admin dashboard with 7-day send chart.