Initial release.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":1},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3554620,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3554620,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3554620,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3554620,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Connections table with Active radio, per-row From email override, last-error column, Send test and Disconnect actions.","2":"Connect Gmail \/ Connect Microsoft buttons with provider logos.","3":"Sender settings: From name, Reply-To, Bulk sending, and From header options.","4":"Email Controls: opt-in suppression of WordPress core admin\/editor self-notifications.","5":"Suppression Log: every suppressed notification with type filter and bulk delete.","6":"Site-wide admin notice surfaced when a connection has failed recently."}},"plugin_section":[],"plugin_tags":[897,4906,2061,6696,48586],"plugin_category":[38,41],"plugin_contributors":[265055],"plugin_business_model":[],"class_list":["post-319950","plugin","type-plugin","status-publish","hentry","plugin_tags-gmail","plugin_tags-notifications","plugin_tags-oauth","plugin_tags-smtp","plugin_tags-transactional-email","plugin_category-authentication","plugin_category-communication","plugin_contributors-redigit","plugin_committers-redigit"],"banners":{"banner":"https:\/\/ps.w.org\/emerge-mail\/assets\/banner-772x250.png?rev=3554620","banner_2x":"https:\/\/ps.w.org\/emerge-mail\/assets\/banner-1544x500.png?rev=3554620","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/emerge-mail\/assets\/icon-128x128.png?rev=3554620","icon_2x":"https:\/\/ps.w.org\/emerge-mail\/assets\/icon-256x256.png?rev=3554620","generated":false},"screenshots":[],"raw_content":"\n
Emerge Mail replaces SMTP plugins for transactional WordPress email. Connect one or more Gmail or Microsoft 365 mailboxes via OAuth, and every Because the From address is your own authenticated mailbox, messages benefit from SPF, DKIM, and DMARC alignment that PHP's When you connect a mailbox, an access + refresh token pair is encrypted with a per-site key and stored as a WordPress option. From that point on, your site talks directly to Gmail or Microsoft Graph; no third party sits in the send path.<\/p>\n\n The plugin hooks To deliver mail, Emerge Mail communicates with three external services. By installing and using this plugin you agree to use of these services. Nothing is contacted until you click Connect Gmail<\/strong> or Connect Microsoft<\/strong> in the plugin settings.<\/p>\n\n What it is and what it's used for:<\/strong> A stateless OAuth proxy operated by the plugin author. It exists to broker the OAuth authorization handshake between your WordPress site and Google or Microsoft so the plugin can be authorized to send mail from your mailbox. The proxy holds the OAuth client secrets that Google and Microsoft would otherwise require every site to register individually.<\/p>\n\n What data is sent, when:<\/strong><\/p>\n\n Terms and privacy:<\/strong><\/p>\n\n What it is and what it's used for:<\/strong> Used only when you connect a Gmail mailbox. Once authorized, the plugin sends every What data is sent, when:<\/strong><\/p>\n\n Terms and privacy:<\/strong><\/p>\n\n What it is and what it's used for:<\/strong> Used only when you connect a Microsoft mailbox. Once authorized, the plugin sends every What data is sent, when:<\/strong><\/p>\n\n Terms and privacy:<\/strong><\/p>\n\n As soon as a connection is active, Yes. Anything that uses No. Authorization is handled by the Emerge OAuth service. You sign in with your normal Google or Microsoft account; no developer setup is required.<\/p><\/dd>\n Tokens are encrypted with a key generated locally on your site on first activation and stored as a WordPress option. They never leave your install. The OAuth proxy used during sign-in does not persist tokens.<\/p><\/dd>\n Access tokens expire roughly hourly. The plugin refreshes them automatically \u2014 both on a schedule and inline if a send happens to coincide with an expiry. You don't need to do anything.<\/p><\/dd>\n The plugin returns an error from its Yes. Connect as many as you like; the connection marked Active<\/strong> is used first. If a send fails (or the Active connection is in cooldown after a recent error), the plugin automatically falls through to the next available connection. You can switch the Active mailbox at any time from the Connections table.<\/p>\n\n For high-volume sites, turn on Bulk sending<\/strong> in Sender settings to spread bursts of sends across all connected mailboxes instead of always hitting the Active one.<\/p><\/dd>\n Yes. Enter a different address in the From email<\/strong> column on the Connections table. It must be a verified send-as alias on the connected mailbox (Gmail: Settings \u2192 Accounts \u2192 Send mail as<\/em>; Microsoft: Mail \u2192 Aliases<\/em> or admin-configured), otherwise the provider will reject the send.<\/p><\/dd>\n Yes. Set it in Sender settings \u2192 From name<\/strong> on the main settings page. Leave it blank to use your site title as the default.<\/p><\/dd>\n Yes. Open Emerge Mail \u2192 Email Controls<\/strong> and tick the notifications you want stopped. Eight WordPress core admin\/editor notifications are listed (comment moderation, new comments, password reset notices, new user registrations, and automatic-update results). Suppressed notifications are recorded in Emerge Mail \u2192 Suppression Log<\/strong> so you still have an audit trail. End-user notifications (password resets, account changes, new-user welcome) are intentionally not listed \u2014 users need those.<\/p><\/dd>\n No. The OAuth scope requested is sufficient only to send mail. The plugin does not call any read endpoints and cannot access existing messages.<\/p><\/dd>\n Yes. Yes. Deleting the plugin from the Plugins screen runs wp_mail()<\/code> call your site makes \u2014 password resets, comment notifications, WooCommerce receipts, contact-form submissions \u2014 is delivered through that mailbox's API.<\/p>\n\nmail()<\/code> function cannot provide. This typically results in dramatically better inbox placement than default WordPress mail.<\/p>\n\nKey features<\/h4>\n\n
\n
wp_mail<\/code> compatibility: To\/Cc\/Bcc (including from headers), HTML bodies, multipart alternative, attachments, custom headers, RFC 2822 address formats including comma-separated lists and quoted display names, non-UTF-8 charsets.<\/li>\nHow it works<\/h4>\n\n
pre_wp_mail<\/code>. If at least one connection is active, the message is routed through the chosen provider API. If the provider returns an error \u2014 or if no connections are configured \u2014 WordPress's default mail delivery takes over transparently.<\/p>\n\nWhat this is not<\/h4>\n\n
\n
External services<\/h3>\n\n
1. Emerge OAuth service (emerge.redigit.net)<\/h4>\n\n
\n
https:\/\/emerge.redigit.net\/oauth\/{provider}\/authorize<\/code> with a PKCE code challenge and a state token generated by your site. No personal data is sent.<\/li>\nhttps:\/\/emerge.redigit.net\/oauth\/{provider}\/token<\/code> to receive the access and refresh tokens. The tokens are returned directly to your site and stored locally, encrypted, in wp_options<\/code>. The proxy does not persist them.<\/li>\nhttps:\/\/emerge.redigit.net\/oauth\/{provider}\/refresh<\/code> to obtain a new access token. Again, nothing is persisted on the proxy.<\/li>\n\n
2. Google APIs (Gmail)<\/h4>\n\n
wp_mail()<\/code> message directly to the Gmail API (gmail.googleapis.com<\/code>) from your WordPress site. Periodically the plugin also calls the Google OAuth userinfo endpoint (www.googleapis.com\/oauth2\/v2\/userinfo<\/code>) to verify the access token is still valid.<\/p>\n\n\n
wp_mail()<\/code> call routed through a Gmail connection: the full outbound message (To\/Cc\/Bcc, subject, body, attachments, custom headers) is POSTed to https:\/\/gmail.googleapis.com\/gmail\/v1\/users\/me\/messages\/send<\/code> as a base64-encoded RFC822 message. This is what's required for the message to reach the recipient.<\/li>\nhttps:\/\/www.googleapis.com\/oauth2\/v2\/userinfo<\/code>. No message data is included.<\/li>\n<\/ul>\n\n\n
3. Microsoft Graph (Outlook \/ Microsoft 365)<\/h4>\n\n
wp_mail()<\/code> message directly to Microsoft Graph (graph.microsoft.com<\/code>) from your WordPress site. Periodically the plugin also calls Graph's \/me<\/code> endpoint to verify the access token is still valid.<\/p>\n\n\n
wp_mail()<\/code> call routed through a Microsoft connection: the full outbound message (To\/Cc\/Bcc, subject, body, attachments, custom headers) is POSTed to https:\/\/graph.microsoft.com\/v1.0\/me\/sendMail<\/code> as a JSON payload. This is what's required for the message to reach the recipient.<\/li>\nhttps:\/\/graph.microsoft.com\/v1.0\/me<\/code>. No message data is included.<\/li>\n<\/ul>\n\n\n
\n
emerge-mail<\/code> folder to \/wp-content\/plugins\/<\/code>, or install via the Plugins screen.<\/li>\nwp_mail()<\/code> routes through it automatically.<\/p>\n\n\n\n
Does this work with WooCommerce, Contact Form 7, WPForms, etc.?<\/h3><\/dt>\n
wp_mail()<\/code> \u2014 which is virtually every WordPress plugin that sends email \u2014 works without modification.<\/p><\/dd>\nDo I need a Google Cloud or Microsoft Azure account?<\/h3><\/dt>\n
Where are my OAuth tokens stored?<\/h3><\/dt>\n
What happens when an access token expires?<\/h3><\/dt>\n
What happens if Gmail or Microsoft is unreachable?<\/h3><\/dt>\n
pre_wp_mail<\/code> hook, which causes WordPress to fall back to its default mail delivery. The failure is recorded in the Last error<\/strong> column of the settings page and surfaced as an admin notice for 24 hours.<\/p><\/dd>\nCan I send from multiple mailboxes?<\/h3><\/dt>\n
Can I override the From email?<\/h3><\/dt>\n
Can I customize the From display name?<\/h3><\/dt>\n
Can I suppress noisy WordPress notifications I don't care about?<\/h3><\/dt>\n
Does the plugin read my mailbox?<\/h3><\/dt>\n
Is `wp_mail` still available to other plugins after activation?<\/h3><\/dt>\n
wp_mail<\/code> continues to function normally. The plugin only changes how the underlying send is performed; it doesn't change any of wp_mail<\/code>'s public behavior.<\/p><\/dd>\nWill the plugin work without an active mailbox connection?<\/h3><\/dt>\n
wp_mail<\/code> falls through to WordPress's default delivery when no connection is available. The plugin never blocks email.<\/p><\/dd>\nHow do I remove all stored data on uninstall?<\/h3><\/dt>\n
uninstall.php<\/code>, which removes every stored connection, all encrypted tokens, the per-site encryption key, sender\/control settings, the suppression-log table, and all scheduled jobs.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.0<\/h4>\n\n
\n
wp_mail<\/code> mapping: attachments, Cc\/Bcc from headers, multipart alternative, comma-separated address lists with quoted display names, non-UTF-8 charsets, RFC 2047 header encoding.<\/li>\n