First release.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"The General tab, where the sender identity and delivery behaviour are set.","2":"A server tab configured for SMTP, with the connection test.","3":"A server tab configured for provider API delivery.","4":"The Test tab, showing which routes are ready and sending a test message.","5":"The debug log."}},"plugin_section":[],"plugin_tags":[17561,267,450,6696,41812],"plugin_category":[41],"plugin_contributors":[281803],"plugin_business_model":[],"class_list":["post-357014","plugin","type-plugin","status-publish","hentry","plugin_tags-deliverability","plugin_tags-email","plugin_tags-mail","plugin_tags-smtp","plugin_tags-wp-mail","plugin_category-communication","plugin_contributors-cshubh832","plugin_committers-cshubh832"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/dualsend-smtp-failover.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
WordPress sends email with PHP's Dualsend SMTP Failover routes your site's email through a mail server you control. What makes it different from other SMTP plugins is the second server: configure a fallback, and if the primary one is down, rate limited or refusing connections, the message is retried on the backup automatically. Nothing is lost while you work out what went wrong with the first one.<\/p>\n\n Each message is offered to the configured routes in order, and the first one that accepts it wins:<\/p>\n\n If every route fails, the message is handed back to WordPress so its own mail handling still gets a turn.<\/p>\n\n Many hosts close outgoing SMTP ports. Where a provider offers an HTTP API, you can use it instead of SMTP by pasting in an API key \u2014 no ports involved. These providers are supported:<\/p>\n\n Brevo, Elastic Email, MailerSend, Mailgun, Mailjet, Mandrill, Postmark, Resend, SendGrid, SendLayer, SMTP.com, SMTP2GO, SparkPost.<\/p>\n\n Any other provider, including Amazon SES, Gmail, Google Workspace, Microsoft 365, Outlook.com and Zoho Mail, works over standard SMTP.<\/p>\n\n This plugin does not contact any service on its own. It has no telemetry, no licence check, and no connection to any service run by the plugin author.<\/p>\n\n The only outgoing connections it makes are to the email provider you<\/strong> configure, and only when it is sending your mail or when you press one of the test buttons. Endpoints below are API hostnames, not web pages.<\/p>\n\n When a message is sent, the data passed to your chosen provider is the message itself: recipients, subject, body, and the sender address you configured. That is the same data any mail server would receive. Nothing is sent anywhere else.<\/p>\n\n If you configure a plain SMTP server instead of an API, the plugin connects only to the host you entered.<\/p>\n\n\n No. The plugin works with just the primary server. The fallback is there for sites where a missed email costs something \u2014 a shop, a booking form, a support desk.<\/p><\/dd>\n Ideally not. If both servers belong to the same provider, one outage takes out both. Pairing two different providers is what makes the failover worth having.<\/p><\/dd>\n Choose a provider that offers an API \u2014 SendGrid, Brevo, Postmark, Mailgun and most others in the list above \u2014 and set the connection type to Provider API<\/strong>. API delivery runs over ordinary HTTPS, which is not blocked.<\/p><\/dd>\n In the WordPress options table, in the same database as the rest of your site, and only readable by users who can already manage plugin settings. They are never sent back to the browser once saved, and they are masked before anything is written to the debug log.<\/p>\n\n For extra safety on a shared host, keep your provider's API key scoped to sending only, rather than full account access.<\/p><\/dd>\n Almost always because the From address does not match a domain your provider is authorised to send for. Set up SPF, DKIM and DMARC records with your provider, and use a From address on that domain.<\/p><\/dd>\n Yes, and it treats form submissions specially: while a visitor is waiting on a form, timeouts are shortened and the long retry pause is skipped, so a slow mail server never leaves the page hanging.<\/p>\n\n Any plugin that sends through Not unless you ask it to. By default a plugin that sets its own From address keeps it. Switch on Override other plugins<\/strong> on the General tab if you want your configured address used everywhere.<\/p><\/dd>\n The message is handed back to WordPress, which tries its own PHP mail handling. Switch on the debug log to see exactly which route failed and why.<\/p><\/dd>\n\n<\/dl>\n\n\nmail()<\/code> function by default. Most hosts either block it or send it in a way that lands in spam, which is why contact form notifications, password resets and order confirmations go missing.<\/p>\n\nHow delivery works<\/h4>\n\n
\n
Sending over an API instead of SMTP<\/h4>\n\n
Features<\/h4>\n\n
\n
wp_mail()<\/code><\/li>\n<\/ul>\n\nExternal services<\/h3>\n\n
\n
\n
\n
Do I need a fallback server?<\/h3><\/dt>\n
Should the fallback use the same provider as the primary?<\/h3><\/dt>\n
My host blocks SMTP ports. What do I do?<\/h3><\/dt>\n
Where are my passwords stored?<\/h3><\/dt>\n
Why did my message send but land in spam?<\/h3><\/dt>\n
Does it work with Contact Form 7?<\/h3><\/dt>\n
wp_mail()<\/code> works, including WooCommerce, Gravity Forms, WPForms and the WordPress core notifications.<\/p><\/dd>\nWill it interfere with other plugins that set their own sender address?<\/h3><\/dt>\n
What happens when every route fails?<\/h3><\/dt>\n
1.0.0<\/h4>\n\n
\n