Critical fix: emails failed with "Message has to belong to at least one mailbox". The plugin now finds a fallback mailbox automatically.<\/p>","1.3.2":"
Critical fix: emails were blocked when the JMAP server had no Sent mailbox with role "sent". Update immediately.<\/p>","1.3.1":"
Bug fix: resolves a fatal syntax error that prevented the plugin from loading. Update immediately.<\/p>","1.3.0":"
UI polish update with empty states, toast notifications, and improved setup wizard. No database changes \u2014 safe to upgrade.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3588268,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3588268,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3588268,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3588268,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.3.5"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3588268,"resolution":"1","location":"assets","locale":"","width":1200,"height":750},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3588268,"resolution":"2","location":"assets","locale":"","width":1200,"height":750},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3588268,"resolution":"3","location":"assets","locale":"","width":1200,"height":750},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3588268,"resolution":"4","location":"assets","locale":"","width":1200,"height":750},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3588268,"resolution":"5","location":"assets","locale":"","width":1200,"height":750}},"screenshots":{"1":"General tab \u2014 enable\/disable toggle, sender information, automatic retry settings, and open tracking configuration.","2":"Connection tab \u2014 JMAP server credentials, identity selection with auto-resolve, and live connection testing with step-by-step feedback.","3":"Mail Log tab \u2014 expandable log entries showing recipient, subject, status badges, JMAP IDs, and error details.","4":"Setup wizard \u2014 guided first-time configuration: server connection, sender information, and activation.","5":"Routing rules editor \u2014 condition builder with field\/value pairs and match operator (ANY\/ALL).","6":"Accounts tab \u2014 multiple JMAP account cards showing status, server URL, and username.","7":"Routing tab \u2014 routing rules table with priority ordering, condition summary, account badges, and enable\/disable status."}},"plugin_section":[],"plugin_tags":[267,269134,450,6696,48586],"plugin_category":[41],"plugin_contributors":[266135],"plugin_business_model":[],"class_list":["post-331679","plugin","type-plugin","status-publish","hentry","plugin_tags-email","plugin_tags-jmap","plugin_tags-mail","plugin_tags-smtp","plugin_tags-transactional-email","plugin_category-communication","plugin_contributors-mustafatahhan","plugin_committers-mustafatahhan"],"banners":{"banner":"https:\/\/ps.w.org\/tahhan-jmap-mailer\/assets\/banner-772x250.png?rev=3588268","banner_2x":"https:\/\/ps.w.org\/tahhan-jmap-mailer\/assets\/banner-1544x500.png?rev=3588268","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/tahhan-jmap-mailer\/assets\/icon-128x128.png?rev=3588268","icon_2x":"https:\/\/ps.w.org\/tahhan-jmap-mailer\/assets\/icon-256x256.png?rev=3588268","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/tahhan-jmap-mailer\/assets\/screenshot-1.png?rev=3588268","caption":"General tab \u2014 enable\/disable toggle, sender information, automatic retry settings, and open tracking configuration."},{"src":"https:\/\/ps.w.org\/tahhan-jmap-mailer\/assets\/screenshot-2.png?rev=3588268","caption":"Connection tab \u2014 JMAP server credentials, identity selection with auto-resolve, and live connection testing with step-by-step feedback."},{"src":"https:\/\/ps.w.org\/tahhan-jmap-mailer\/assets\/screenshot-3.png?rev=3588268","caption":"Mail Log tab \u2014 expandable log entries showing recipient, subject, status badges, JMAP IDs, and error details."},{"src":"https:\/\/ps.w.org\/tahhan-jmap-mailer\/assets\/screenshot-4.png?rev=3588268","caption":"Setup wizard \u2014 guided first-time configuration: server connection, sender information, and activation."},{"src":"https:\/\/ps.w.org\/tahhan-jmap-mailer\/assets\/screenshot-5.png?rev=3588268","caption":"Routing rules editor \u2014 condition builder with field\/value pairs and match operator (ANY\/ALL)."}],"raw_content":"\n
Tahhan JMAP Mailer replaces WordPress's built-in mailer with the modern JMAP protocol<\/strong> (RFC 8620 \/ RFC 8621). JMAP is the successor to IMAP and SMTP, designed from scratch for the modern web. It communicates over standard HTTPS, works through firewalls and NAT without any special port configuration, and is natively supported by leading mail servers such as Stalwart Mail Server, Fastmail, and Cyrus IMAP.<\/p>\n\n Unlike SMTP plugins that require relay credentials, third-party services, or open ports, Tahhan JMAP Mailer connects directly to your own JMAP-capable mail server using HTTP Basic authentication over an encrypted HTTPS connection. The JMAP session is auto-discovered from Tahhan JMAP Mailer is built as a proper WordPress plugin: it uses Every send attempt is logged (recipient, subject, status, JMAP IDs) in a capped mail log \u2014 message bodies are never stored. The plugin ships with a full admin UI including a setup wizard, live connection testing, multi-account management, conditional routing rules, a retry queue with exponential backoff, open tracking, CSV log export, and WooCommerce email type detection.<\/p>\n\n Tahhan JMAP Mailer works with any mail server that implements RFC 8621 (JMAP for Mail):<\/p>\n\n JMAP (JSON Meta Application Protocol) is a modern, open-standard protocol (RFC 8620 \/ RFC 8621) designed as the successor to IMAP and SMTP. It communicates over HTTPS using JSON, works through firewalls without special port configuration, and is significantly more efficient than legacy email protocols.<\/p><\/dd>\n SMTP was designed in 1982 and requires specific TCP ports (25, 465, 587) that are often blocked by firewalls and hosting providers. JMAP works over standard HTTPS (port 443), requires no relay configuration, has no port restrictions, and uses a modern JSON-based API that is far easier to work with programmatically.<\/p><\/dd>\n Stalwart Mail Server, Fastmail, Cyrus IMAP, and Apache James all support JMAP fully. Any server implementing RFC 8621 will work with Tahhan JMAP Mailer.<\/p><\/dd>\n Yes. Tahhan JMAP Mailer includes WooCommerce email type detection. You can create routing rules that detect WooCommerce emails (order confirmations, customer invoices, admin notifications) and route them to a dedicated transactional email account for better deliverability.<\/p><\/dd>\n Yes. The Accounts tab lets you configure multiple JMAP accounts. You can set one as the Primary account (used by default) and configure additional accounts such as a dedicated transactional account for WooCommerce or a support-specific account.<\/p><\/dd>\n Routing rules are evaluated in order from top to bottom. The first matching rule wins. Each rule can match on recipient email, recipient domain, sender email, subject content, or plugin\/email type. You can match ANY condition (OR logic) or ALL conditions (AND logic). Non-matching emails fall back to the Primary account.<\/p><\/dd>\n When an email fails to send, Tahhan JMAP Mailer can automatically retry it via WP-Cron. You configure the maximum number of retry attempts (1-5) and an initial delay (5 minutes to 1 hour). Each subsequent retry doubles the delay (exponential backoff). Permanently failed emails are marked as \"exhausted\" in the mail log.<\/p><\/dd>\n Open tracking embeds a 1x1 transparent pixel in outgoing HTML emails. When a recipient opens the email, the pixel loads from your WordPress site, recording the open event. Plain-text emails are never tracked. All tracking data stays on your own server \u2014 nothing is sent to external services. You should disclose tracking in your privacy policy.<\/p><\/dd>\n The mail log records every send attempt: timestamp, recipient address, subject line, send status (sent\/failed), JMAP account and identity IDs, email object ID, and any error message. Message bodies, CC\/BCC addresses, and attachment contents are never stored. The log is capped at 100 entries.<\/p><\/dd>\n Yes. On the Mail Log tab, click \"Export CSV\" to download all log entries as a CSV file. The export includes timestamp, recipient, subject, status, account ID, identity ID, email ID, and error message.<\/p><\/dd>\n PHP 7.4 or higher. The plugin is tested with PHP 7.4, 8.0, 8.1, 8.2, and 8.3.<\/p><\/dd>\n WordPress 5.8 or higher. The plugin is tested up to WordPress 6.7.<\/p><\/dd>\n The Primary account is the fallback account used for all emails that do not match a routing rule. It is created automatically during setup from your initial JMAP credentials. You can edit the Primary account's credentials on the Connection tab or in the Accounts tab.<\/p><\/dd>\n A JMAP identity defines the \"From\" name and email address used when sending. Tahhan JMAP Mailer can auto-resolve the correct identity by matching your configured From Email to an identity on the JMAP server. You can also manually select a specific identity from the Connection tab by clicking \"Load identities\" after saving your credentials.<\/p><\/dd>\n Go to Tahhan JMAP Mailer -> Connection<\/strong> and click \"Test connection\". The plugin will discover the JMAP session, resolve your sender identity, and verify server capabilities. You can also click \"Send test email\" to fire a real email through the full send pipeline to your configured test recipient.<\/p><\/dd>\n\n<\/dl>\n\n\n\/.well-known\/jmap<\/code> \u2014 no manual API URL configuration needed.<\/p>\n\nwp_remote_get\/post<\/code>, WP_Error<\/code>, WordPress nonces, and the standard sanitization and escaping APIs throughout. There are zero external PHP dependencies. It hooks into pre_wp_mail<\/code> to intercept every wp_mail()<\/code> call site-wide and deliver the email through a two-step JMAP pipeline: Email\/set<\/code> to create the email object, followed by EmailSubmission\/set<\/code> to submit it for delivery.<\/p>\n\nFeatures<\/h3>\n\n
\n
\/.well-known\/jmap<\/code><\/li>\nCompatible Servers<\/h3>\n\n
\n
\n
\n
What is JMAP?<\/h3><\/dt>\n
How is JMAP different from SMTP?<\/h3><\/dt>\n
Which mail servers support JMAP?<\/h3><\/dt>\n
Does Tahhan JMAP Mailer work with WooCommerce?<\/h3><\/dt>\n
Can I use multiple JMAP accounts?<\/h3><\/dt>\n
How do routing rules work?<\/h3><\/dt>\n
What is the retry queue?<\/h3><\/dt>\n
What is open tracking?<\/h3><\/dt>\n
What is the mail log?<\/h3><\/dt>\n
Can I export the mail log?<\/h3><\/dt>\n
What PHP version is required?<\/h3><\/dt>\n
What WordPress version is required?<\/h3><\/dt>\n
What is the Primary account?<\/h3><\/dt>\n
How do sender identities work?<\/h3><\/dt>\n
How do I test the connection?<\/h3><\/dt>\n
1.3.5<\/h4>\n\n
\n
1.3.4<\/h4>\n\n
\n
1.3.3<\/h4>\n\n
\n
1.3.2<\/h4>\n\n
\n
1.3.1<\/h4>\n\n
\n
1.3.0<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n
\/.well-known\/jmap<\/code><\/li>\n