Initial release of NimblyMail.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3562596,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3562596,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3562596,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3562596,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3562596,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.0.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3562596,"resolution":"1","location":"assets","locale":"","width":1440,"height":900},"screenshot-10.png":{"filename":"screenshot-10.png","revision":3562596,"resolution":"10","location":"assets","locale":"","width":1440,"height":900},"screenshot-11.png":{"filename":"screenshot-11.png","revision":3562596,"resolution":"11","location":"assets","locale":"","width":1440,"height":900},"screenshot-12.png":{"filename":"screenshot-12.png","revision":3562596,"resolution":"12","location":"assets","locale":"","width":1440,"height":900},"screenshot-13.png":{"filename":"screenshot-13.png","revision":3562596,"resolution":"13","location":"assets","locale":"","width":1440,"height":900},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3562596,"resolution":"2","location":"assets","locale":"","width":1440,"height":900},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3562596,"resolution":"3","location":"assets","locale":"","width":1440,"height":900},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3562596,"resolution":"4","location":"assets","locale":"","width":1440,"height":900},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3562596,"resolution":"5","location":"assets","locale":"","width":1440,"height":900},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3562596,"resolution":"6","location":"assets","locale":"","width":1440,"height":900},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3562596,"resolution":"7","location":"assets","locale":"","width":1440,"height":900},"screenshot-8.png":{"filename":"screenshot-8.png","revision":3562596,"resolution":"8","location":"assets","locale":"","width":1440,"height":900},"screenshot-9.png":{"filename":"screenshot-9.png","revision":3562596,"resolution":"9","location":"assets","locale":"","width":1440,"height":900}},"screenshots":{"1":"Dashboard \u2014 Delivery stats, connection status, queue health, deliverability summary, and recent email activity at a glance.","2":"Email Log \u2014 Searchable log table with status filters, bulk actions, and per-email detail view.","3":"Settings: Connection \u2014 Choose from nine supported mailers including Gmail OAuth, Outlook \/ Microsoft 365 OAuth, Amazon SES, Resend, SendLayer, Brevo, and ZeptoMail.","4":"Settings: Connection (Outlook \/ Microsoft 365) \u2014 Connect your Microsoft account in one click via NimblyMail's secure OAuth proxy \u2014 no Azure app registration required.","5":"Setup Wizard \u2014 Guided first-run configuration with auto-detection of existing SMTP plugins.","6":"Settings: Mail Queue \u2014 Turn on the background queue to defer wp_mail() calls; configure max attempts, batch size, exponential backoff, default priority, and a pause toggle.","7":"Mail Queue admin \u2014 Live view of pending, processing, and failed deliveries with per-row retry \/ cancel actions, last-error preview, and counts grouped by status.","8":"Settings: Developer Sandbox \u2014 Stop staging environments from sending real email. Log Only or Redirect mode, with an allowlist for addresses that should still be delivered.","9":"Deliverability Health Audit \u2014 Automated SPF \/ DKIM \/ DMARC \/ PTR audit of the active sender domain with mailer-aware requirements.","10":"Tools: Email Tester \u2014 Send a test email to verify your configuration works.","11":"Settings: Email Controls \u2014 Toggle individual WordPress notification emails on or off (over 25 triggers across 8 categories).","12":"Network Dashboard \u2014 Aggregated delivery stats, top failing sites, and per-site totals across the whole multisite network.","13":"Network Sites \u2014 Per-site summary table showing the active mailer, override count, and recent sent\/failed counts, with a one-click editor for each site's overrides."}},"plugin_section":[],"plugin_tags":[26736,98133,193628,6696,48586],"plugin_category":[41],"plugin_contributors":[266000],"plugin_business_model":[],"class_list":["post-306287","plugin","type-plugin","status-publish","hentry","plugin_tags-email-log","plugin_tags-gmail-smtp","plugin_tags-outlook-smtp","plugin_tags-smtp","plugin_tags-transactional-email","plugin_category-communication","plugin_contributors-nimblymail","plugin_committers-nimblymail"],"banners":{"banner":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/banner-772x250.png?rev=3562596","banner_2x":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/banner-1544x500.png?rev=3562596","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/icon.svg?rev=3562596","icon":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/icon.svg?rev=3562596","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/screenshot-1.png?rev=3562596","caption":"Dashboard \u2014 Delivery stats, connection status, queue health, deliverability summary, and recent email activity at a glance."},{"src":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/screenshot-2.png?rev=3562596","caption":"Email Log \u2014 Searchable log table with status filters, bulk actions, and per-email detail view."},{"src":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/screenshot-3.png?rev=3562596","caption":"Settings: Connection \u2014 Choose from nine supported mailers including Gmail OAuth, Outlook \/ Microsoft 365 OAuth, Amazon SES, Resend, SendLayer, Brevo, and ZeptoMail."},{"src":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/screenshot-4.png?rev=3562596","caption":"Settings: Connection (Outlook \/ Microsoft 365) \u2014 Connect your Microsoft account in one click via NimblyMail's secure OAuth proxy \u2014 no Azure app registration required."},{"src":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/screenshot-5.png?rev=3562596","caption":"Setup Wizard \u2014 Guided first-run configuration with auto-detection of existing SMTP plugins."},{"src":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/screenshot-6.png?rev=3562596","caption":"Settings: Mail Queue \u2014 Turn on the background queue to defer wp_mail() calls; configure max attempts, batch size, exponential backoff, default priority, and a pause toggle."},{"src":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/screenshot-7.png?rev=3562596","caption":"Mail Queue admin \u2014 Live view of pending, processing, and failed deliveries with per-row retry \/ cancel actions, last-error preview, and counts grouped by status."},{"src":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/screenshot-8.png?rev=3562596","caption":"Settings: Developer Sandbox \u2014 Stop staging environments from sending real email. Log Only or Redirect mode, with an allowlist for addresses that should still be delivered."},{"src":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/screenshot-9.png?rev=3562596","caption":"Deliverability Health Audit \u2014 Automated SPF \/ DKIM \/ DMARC \/ PTR audit of the active sender domain with mailer-aware requirements."},{"src":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/screenshot-10.png?rev=3562596","caption":"Tools: Email Tester \u2014 Send a test email to verify your configuration works."},{"src":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/screenshot-11.png?rev=3562596","caption":"Settings: Email Controls \u2014 Toggle individual WordPress notification emails on or off (over 25 triggers across 8 categories)."},{"src":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/screenshot-12.png?rev=3562596","caption":"Network Dashboard \u2014 Aggregated delivery stats, top failing sites, and per-site totals across the whole multisite network."},{"src":"https:\/\/ps.w.org\/nimblymail-smtp\/assets\/screenshot-13.png?rev=3562596","caption":"Network Sites \u2014 Per-site summary table showing the active mailer, override count, and recent sent\/failed counts, with a one-click editor for each site's overrides."}],"raw_content":"\n
NimblyMail is a comprehensive SMTP and email logging plugin designed to fix WordPress email deliverability issues. By default, WordPress uses the unreliable PHP Whether you need to connect via a standard SMTP host, Gmail OAuth, Microsoft 365 OAuth, Amazon SES, Resend, SendLayer, Brevo, or ZeptoMail, NimblyMail ensures your emails reach the inbox. Plus, with comprehensive email logging, a background queue, a developer sandbox, and an automated deliverability audit, you get full delivery monitoring and one-click troubleshooting.<\/p>\n\n Every outgoing email is logged with recipient, subject, status, headers, and optional body capture. Search and filter logs by status (sent, failed, pending), resend failed emails with one click, and view full message details in a modal preview.<\/p>\n\n Turn the queue on under NimblyMail > Settings > Mail Queue and every wp_mail() call returns immediately. Messages are persisted to a database queue, dispatched by Action Scheduler in priority order (high \/ normal \/ bulk), and retried with exponential backoff on transient failures. Attachments are staged on enqueue so request-scoped tmp files cannot break delayed delivery. The Queue admin screen lists pending and failed items with retry \/ cancel actions, and the dashboard surfaces a queue-health widget. Test emails and admin alerts continue to send synchronously by default so you always get immediate feedback.<\/p>\n\n Working on a staging copy or local clone? Turn on the sandbox to guarantee no real customer ever receives an accidental email. Pick Log Only<\/strong> to capture and short-circuit every wp_mail() call so they show up in the Email Log without leaving the host, or Redirect<\/strong> to rewrite every recipient to a single safe address with the originals preserved in NimblyMail runs an automated DNS audit of the active sender domain on a schedule (and on demand) and surfaces the result on the Deliverability page and the dashboard. The audit covers four pillars \u2014 SPF, DKIM, DMARC, and PTR \u2014 and is mailer-aware: required SPF includes and DKIM selectors are sourced from whichever provider you have configured (Gmail, Outlook 365, SES, etc.), with skip explanations for cases where a check does not apply. Findings are human-readable: each pillar shows pass\/warn\/fail with a one-line reason and a link to the relevant provider documentation.<\/p>\n\n Selectively disable WordPress notification emails you don't need \u2014 comment notifications, password reset emails, new user registrations, automatic update notices, and more. Over 25 individual email types across 8 categories can be toggled on or off.<\/p>\n\n Receive instant alerts when emails fail to deliver. Configure alert recipients with optional CC and BCC addresses. Alerts are sent via PHP's native mail function to bypass the broken transport.<\/p>\n\n Credentials (SMTP passwords, API keys) are encrypted at rest using AES-256-CBC with HMAC-SHA256 verification. Settings can be locked via PHP constants in wp-config.php, making sensitive fields read-only in the admin UI.<\/p>\n\n Migrating from another SMTP plugin? NimblyMail automatically detects existing SMTP-plugin configurations and offers one-click import through the setup wizard.<\/p>\n\n First-class multisite support. Network-activate the plugin once and every sub-site inherits the network defaults until a site admin explicitly overrides a field. Super admins get a Network Admin \u2192 NimblyMail surface with an aggregated dashboard, a sites table, per-field locks, and a per-site override editor.<\/p>\n\n Built with Vue 3 and Ant Design, the dashboard is fast, responsive, and designed to feel native to WordPress. A guided setup wizard helps you configure everything in minutes, while the main dashboard provides a clear overview of your email delivery health.<\/p>\n\n The complete, human-readable source code for NimblyMail is maintained in the public WordPress.org SVN repository for this plugin. Browse it directly in your web browser via the Trac UI:<\/p>\n\n The repository The minified JavaScript and CSS files under Inside the SVN The full version history of the plugin is also browsable on its WordPress.org page at https:\/\/wordpress.org\/plugins\/nimblymail-smtp\/.<\/p>\n\n NimblyMail does not contact any third-party service on its own. Outbound network requests only happen when you actively configure and select a mailer<\/strong> that uses an external provider, and only at the time of sending an email (or, for OAuth providers, when authorizing the connection).<\/p>\n\n The plugin connects to the following services depending on which mailer you choose. None of these are contacted unless you select that mailer and enter credentials.<\/p>\n\n NimblyMail OAuth Proxy<\/strong> ( Other SMTP<\/strong> \u2014 When configured, every email is sent over SMTP to the server you specify (host, port, encryption, credentials). The data sent is the email itself: From \/ To \/ CC \/ BCC \/ Subject \/ Body \/ attachments. The remote SMTP server is operated by you or your provider; NimblyMail does not select it.<\/p><\/li>\n Gmail \/ Google Workspace<\/strong> \u2014 Uses Google's OAuth 2.0 service (via the NimblyMail OAuth Proxy described above) to authorize sending, and Outlook \/ Microsoft 365<\/strong> \u2014 Uses Microsoft's OAuth 2.0 service (via the NimblyMail OAuth Proxy described above) to authorize sending, and Amazon SES<\/strong> \u2014 When configured, emails are sent over SMTP to the AWS SES endpoint you select (e.g. Resend<\/strong> \u2014 When configured, emails are sent via HTTPS POST to SendLayer<\/strong> \u2014 When configured, emails are sent via HTTPS POST to Brevo<\/strong> \u2014 When configured, emails are sent via HTTPS POST to ZeptoMail<\/strong> \u2014 When configured, emails are sent via HTTPS POST to the regional endpoint you select (e.g. Default (PHP)<\/strong> \u2014 No external service. Emails are handed to the PHP In addition, NimblyMail logs each outgoing email locally<\/strong> to a database table on your own WordPress site. No log data is ever transmitted off-site.<\/p>\n\n The Deliverability Health Audit performs DNS-only lookups for the configured sender domain. When the host's PHP Go to NimblyMail > Settings > Connection, select \"Other SMTP\" as your mailer, then enter your SMTP host, port, encryption type, and credentials. Click \"Save Changes\" and use the Email Tester under NimblyMail > Tools to verify delivery.<\/p><\/dd>\n Yes. Select \"Gmail \/ Google Workspace\" as your mailer and click \"Connect to Google\" to authorize. NimblyMail uses a centralized OAuth proxy so you don't need to register your own Google Cloud project \u2014 just click, approve, and you're connected. NimblyMail handles token refresh automatically.<\/p><\/dd>\n Yes. Select \"Outlook \/ Microsoft 365\" as your mailer and click \"Connect to Microsoft\" to authorize. As with Gmail, NimblyMail uses a centralized OAuth proxy so you don't need to register your own Azure app \u2014 sign in with the mailbox you want to send from and you're connected. Mail is delivered through Turn it on under NimblyMail > Settings > Sandbox. Choose Log Only to capture every email locally without sending, or Redirect to rewrite every recipient to a single safe address. You can also configure an allowlist (exact email or NimblyMail encrypts all stored credentials (passwords, API keys) using AES-256-CBC. For additional security, you can define credentials as PHP constants in wp-config.php instead of storing them in the database. For example: By default, all data is preserved when you deactivate. To remove all data on uninstall, enable \"Remove Data on Uninstall\" under NimblyMail > Settings > Misc before deactivating.<\/p><\/dd>\n Yes. NimblyMail can import settings from several existing SMTP plugins. The setup wizard detects supported plugins automatically, or you can import manually from NimblyMail > Tools > Import.<\/p><\/dd>\n Go to NimblyMail > Settings > Alerts, enable \"Enable Alerts\", and enter one or more recipient email addresses. You can also add CC and BCC recipients. Alerts are sent whenever an email fails to deliver.<\/p><\/dd>\n\n<\/dl>\n\n\nmail()<\/code> function, which often causes emails to land in the spam folder or never deliver. NimblyMail solves this by reconfiguring WordPress to securely route your site's emails through a proper SMTP server or dedicated email provider.<\/p>\n\nAt a glance<\/h4>\n\n
\n
mail()<\/code> so a broken transport can't silence them.<\/li>\nSupported Email Providers<\/h4>\n\n
\n
smtp.office365.com<\/code> without registering your own Azure application.<\/li>\nEmail Logging<\/h4>\n\n
Background Queue<\/h4>\n\n
Developer Sandbox<\/h4>\n\n
X-NimblyMail-Original-*<\/code> headers and a configurable subject prefix. An allowlist (exact email or *@domain.com<\/code>) lets through addresses you do want delivered for testing. Sandboxing is settings-driven, switchable from the Network Admin on multisite, and visible at a glance via an admin-bar badge.<\/p>\n\nDeliverability Health Audit<\/h4>\n\n
Email Controls<\/h4>\n\n
Failure Alerts<\/h4>\n\n
Security<\/h4>\n\n
Settings Import<\/h4>\n\n
WordPress Multisite<\/h4>\n\n
Clean Dashboard<\/h4>\n\n
Development and source code<\/h3>\n\n
\n
svn checkout https:\/\/plugins.svn.wordpress.org\/nimblymail-smtp\/trunk\/ nimblymail-smtp<\/code><\/li>\n<\/ul>\n\ntrunk\/<\/code> directory contains:<\/p>\n\n\n
src\/<\/code> \u2014 the PHP backend (PSR-4 autoloaded, plain readable PHP).<\/li>\napps\/<\/code> \u2014 the Vue 3 + TypeScript single-page apps (Dashboard, Settings, Email Logs, Tools, Setup Wizard, Network Admin) that get compiled into the minified bundles under dist\/<\/code>.<\/li>\npackage.json<\/code>, package-lock.json<\/code>, tsconfig.json<\/code>, tsconfig.node.json<\/code>, vite.config.ts<\/code> \u2014 the build configuration needed to reproduce the exact dist\/<\/code> bundles.<\/li>\ndist\/<\/code> build output plus per-bundle source-map files (*.js.map<\/code>, *.css.map<\/code>).<\/li>\n<\/ul>\n\ndist\/<\/code> are produced from the Vue\/TypeScript sources under apps\/<\/code> using Vite. To rebuild them yourself from a trunk\/<\/code> checkout:<\/p>\n\n\n
composer install<\/code> to install PHP dependencies (PSR-4 autoloader + Action Scheduler).<\/li>\nnpm install<\/code> to install the JavaScript build dependencies declared in package.json<\/code>.<\/li>\nnpm run build<\/code> to regenerate the dist\/<\/code> bundle from the apps\/<\/code> sources. For local development with hot-module replacement, run npm run dev<\/code> (Vite dev server) after adding define( 'HMR_DEV', 'nimblymail-smtp' );<\/code> to your wp-config.php<\/code>.<\/li>\n<\/ol>\n\nHow files under `dist\/` map to readable source<\/h4>\n\n
trunk\/<\/code>, every minified JavaScript and CSS file under dist\/<\/code> is accompanied by a .map<\/code> source-map file (e.g. dist\/dashboard.<hash>.js<\/code> ships with dist\/dashboard.<hash>.js.map<\/code>). The source map fully describes how each minified file was produced from the readable Vue \/ TypeScript files under apps\/<\/code>, and any modern browser DevTools panel or build tool can use it to inspect the original source line-by-line. The high-level mapping is:<\/p>\n\n\n
dist\/<entry>.<hash>.js<\/code> \u2014 the entry-point bundle for one of the admin apps. Direct source: apps\/<entry>\/index.ts<\/code> (e.g. dist\/dashboard.<hash>.js<\/code> comes from apps\/dashboard\/index.ts<\/code>). Entry names are: dashboard<\/code>, settings<\/code>, email-logs<\/code>, queue<\/code>, tools<\/code>, wizard<\/code>, deliverability<\/code>, network-sites<\/code>, network-dashboard<\/code>.<\/li>\ndist\/chunks\/<name>.<hash>.js<\/code> \u2014 shared chunks auto-emitted by Vite\/Rollup whenever a module is imported by two or more entry points. They contain no plugin-specific code that is not also visible in the readable sources under apps\/<\/code> (and in node_modules\/<\/code> for upstream dependencies like Vue, Ant Design Vue, Vue Router, and Pinia). The dist\/chunks\/AppHeader.<hash>.js<\/code> chunk in particular bundles the shared admin shell (apps\/shared\/AppHeader.vue<\/code>, apps\/shared\/theme.ts<\/code>, apps\/shared\/i18n.ts<\/code>, the Axios HTTP client in apps\/shared\/api.ts<\/code>) together with the Vue runtime and Ant Design Vue components, because every admin page imports them.<\/li>\ndist\/assets\/<name>.<hash>.css<\/code> \u2014 compiled CSS extracted from the corresponding Vue Single-File Components under apps\/<\/code>. Source-maps are emitted for these too (*.css.map<\/code>).<\/li>\n<\/ul>\n\nExternal services<\/h3>\n\n
\n
https:\/\/oauth.nimblymail.com<\/code>) \u2014 Used only when you choose Gmail or Outlook \/ Microsoft 365 as your mailer<\/strong>. The proxy is operated by the plugin author (NimblyMail Team) and exists so you don't have to register your own Google Cloud project or Azure application. Endpoints contacted: https:\/\/oauth.nimblymail.com\/authorize\/{google|microsoft}<\/code>, https:\/\/oauth.nimblymail.com\/token\/{google|microsoft}<\/code>, https:\/\/oauth.nimblymail.com\/refresh\/{google|microsoft}<\/code>, https:\/\/oauth.nimblymail.com\/revoke\/{google|microsoft}<\/code>. Data sent<\/strong>: your site URL (get_home_url()<\/code>), an OAuth state value and PKCE challenge generated by the plugin, the authorization code returned by Google\/Microsoft after consent, the refresh token (signed with a per-install HMAC secret) on every token refresh. No email content, recipient lists, or message metadata is ever sent to the proxy<\/strong> \u2014 actual mail delivery goes directly from your site to Gmail's \/ Microsoft's SMTP servers. NimblyMail Terms of Service: https:\/\/nimblymail.com\/terms-of-service\/ \u2014 NimblyMail Privacy Policy: https:\/\/nimblymail.com\/privacy-policy\/<\/p><\/li>\nsmtp.gmail.com:587<\/code> (XOAUTH2) to deliver mail. Direct endpoints contacted: https:\/\/accounts.google.com\/o\/oauth2\/v2\/auth<\/code> (consent screen), https:\/\/www.googleapis.com\/oauth2\/v2\/userinfo<\/code> (read the authorized email address for the SASL user=<\/code> field), smtp.gmail.com<\/code> (SMTP delivery). Data sent directly to Google: the email envelope and message content at send time. Google Terms of Service: https:\/\/policies.google.com\/terms \u2014 Google Privacy Policy: https:\/\/policies.google.com\/privacy<\/p><\/li>\nsmtp.office365.com:587<\/code> (XOAUTH2) to deliver mail. Direct endpoints contacted: https:\/\/login.microsoftonline.com\/common\/oauth2\/v2.0\/authorize<\/code> (consent screen), https:\/\/graph.microsoft.com\/v1.0\/me<\/code> (read the authorized email address), smtp.office365.com<\/code> (SMTP delivery). Data sent directly to Microsoft: the email envelope and message content at send time. Microsoft Services Agreement: https:\/\/www.microsoft.com\/en\/servicesagreement\/ \u2014 Microsoft Privacy Statement: https:\/\/privacy.microsoft.com\/privacystatement<\/p><\/li>\nemail-smtp.us-east-1.amazonaws.com<\/code>). Data sent: email envelope and content, plus AWS access key ID and secret. AWS Service Terms: https:\/\/aws.amazon.com\/service-terms\/ \u2014 AWS Privacy Notice: https:\/\/aws.amazon.com\/privacy\/<\/p><\/li>\nhttps:\/\/api.resend.com\/emails<\/code>. Data sent: API key, email envelope and content. Resend Terms of Service: https:\/\/resend.com\/legal\/terms-of-service \u2014 Resend Privacy Policy: https:\/\/resend.com\/legal\/privacy-policy<\/p><\/li>\nhttps:\/\/console.sendlayer.com\/api\/v1\/email<\/code>. Data sent: API key, email envelope and content. SendLayer Terms: https:\/\/sendlayer.com\/terms-of-service\/ \u2014 SendLayer Privacy Policy: https:\/\/sendlayer.com\/privacy-policy\/<\/p><\/li>\nhttps:\/\/api.brevo.com\/v3\/smtp\/email<\/code>. Data sent: API key, email envelope and content. Brevo Terms of Service: https:\/\/www.brevo.com\/legal\/termsofuse\/ \u2014 Brevo Privacy Policy: https:\/\/www.brevo.com\/legal\/privacypolicy\/<\/p><\/li>\nhttps:\/\/api.zeptomail.com\/v1.1\/email<\/code>, with eu<\/code>, in<\/code>, com.cn<\/code>, or com.au<\/code> available). Data sent: Send Mail Token, email envelope and content. Zoho Terms of Service: https:\/\/www.zoho.com\/zeptomail\/terms.html \u2014 Zoho Privacy Policy: https:\/\/www.zoho.com\/privacy.html<\/p><\/li>\nmail()<\/code> function and routed by your server.<\/p><\/li>\n<\/ul>\n\ndns_get_record()<\/code> is unavailable or restricted, NimblyMail falls back to public DNS-over-HTTPS resolvers (https:\/\/cloudflare-dns.com\/dns-query<\/code> and https:\/\/dns.google\/resolve<\/code>) to retrieve SPF, DKIM, DMARC, and PTR records. Only the sender domain (and DKIM selector when applicable) is sent in the query \u2014 no mail content. Cloudflare DoH Privacy: https:\/\/developers.cloudflare.com\/1.1.1.1\/privacy\/public-dns-resolver\/ \u2014 Google Public DNS Privacy: https:\/\/developers.google.com\/speed\/public-dns\/privacy<\/p>\n\n\n\n
nimblymail-smtp<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n\n
How do I configure SMTP?<\/h3><\/dt>\n
Can I use Gmail to send emails?<\/h3><\/dt>\n
Can I use Outlook or Microsoft 365 to send emails?<\/h3><\/dt>\n
smtp.office365.com:587<\/code> using XOAUTH2.<\/p><\/dd>\nHow does the Developer Sandbox work?<\/h3><\/dt>\n
*@domain.com<\/code>) for addresses that should still be delivered for testing. The sandbox status is visible on the WordPress admin bar so you never forget it's on.<\/p><\/dd>\nHow do I secure my credentials?<\/h3><\/dt>\n
define( 'NIMBLYMAIL_SMTP_PASS', 'your-password' );<\/code><\/p><\/dd>\nWhat happens to my email logs when I uninstall?<\/h3><\/dt>\n
Can I import settings from another SMTP plugin?<\/h3><\/dt>\n
How do I set up failure alerts?<\/h3><\/dt>\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n