Titanium Mail SMTP – Smart Routing & Email Delivery

Description

Titanium Mail SMTP is a rule-based WordPress email delivery plugin for websites that need to send different types of email through different providers.

The Free version includes a Primary Connection, one Additional Connection, Gmail / Google Workspace OAuth 2.0, Microsoft 365 / Outlook OAuth 2.0, configurable SMTP Return Path, and advanced visual Smart Routing. Build grouped AND/OR conditions from the source plugin, recipients, sender, subject, email content, or headers. Conditions inside each group use AND logic, while groups are combined with OR logic. Messages that do not match a routing rule continue through the Primary Connection.

This makes it possible, for example, to send WooCommerce messages through Gmail while WordPress system notifications use Amazon SES, or to route messages for a particular recipient domain through the Additional Connection.

Why it is different

Titanium Mail SMTP Free is built around conditional delivery rather than only replacing the default WordPress mail transport. Both connections are usable delivery connections, and the visual rule builder can combine several conditions before selecting the Additional Connection.

What you can do

• Send WordPress email through Gmail / Google Workspace OAuth 2.0, Microsoft 365 / Outlook OAuth 2.0, Postmark, Amazon SES, SendGrid, Mailgun, Brevo, Other SMTP, or WordPress default mail.
• Configure one Primary Connection and one independent Additional Connection.
• Build visual Smart Routing with AND rules inside groups and OR logic between groups.
• Route by source plugin or WordPress core, To, CC, BCC, Reply-To, From Email, From Name, subject, message content, header name, or header value.
• Use the Primary Connection automatically when no routing rule matches.
• Set separate sender details and credentials for the two connections.
• Connect Gmail with the send-only gmail.send OAuth scope and Microsoft with delegated Mail.Send, Mail.ReadWrite, and offline_access.
• Configure a Return Path / envelope sender for WordPress default mail and Other SMTP, with the tmsmtp_return_path filter available for message-level customization.
• Send a real test email through the Primary or Additional Connection.
• Receive a simple administrator alert when WordPress reports a delivery failure.
• Store supported credentials in plugin settings or in wp-config.php constants.
• Import a supported primary connection from WP Mail SMTP without changing or deleting its original settings.
• Keep normal WordPress mail active when no external provider is configured.

Free routing and Pro reliability

The Additional Connection in Free is a routing destination. Free does not automatically use it as a backup when another delivery fails, and it does not add failed messages to an automatic retry queue.

Titanium Mail SMTP Pro is available separately for sites that need unlimited additional connections, backup failover, durable Background Sending, Offline Mode, Multisite Shared Connections, automatic retries, protected attachment storage for background/retry delivery, the Full Email Log, CSV log export, isolated HTML preview, raw message body, redacted headers, SMTP diagnostics, manual resend, grouped email/Slack/Discord/Microsoft Teams failure alerts, weekly webhook summaries, detailed statistics, scheduled reports, portable settings export/import, Easy WP SMTP migration, and migration of supported WP Mail SMTP Pro connections, backup, and routing settings.

Useful for

• WooCommerce stores that separate order email from general site email
• Membership, community, course, and subscription websites
• Websites where several plugins send different types of transactional email
• Agencies that need provider-specific routing without automatic failover
• Contact-form and lead-generation websites

External services

This plugin connects to configured email delivery services when WordPress sends an email, including an administrator-requested test email. OAuth authorization begins only after an administrator saves OAuth application credentials and explicitly clicks Connect. Pricing and checkout connections occur only on the plugin’s admin screens after an administrator explicitly enables current price display or starts the checkout flow.

AdminPlugins pricing API

This plugin connects to the AdminPlugins pricing API at https://adminplugins.com/wp-json/tmsmtp-freemius/v1/pricing to load the current public plan prices, license limits, discount state, and checkout URLs shown on the Upgrade page. The request is made from the WordPress admin area only after an administrator enables current price display. Price loading is disabled by default and can be disabled again at any time from the Upgrade page. The plugin sends a standard server-side HTTPS GET request with source=plugin. No email settings, routing rules, site content, users, passwords, email messages, provider credentials, or license keys are added to this request. If the current admin URL contains no_cache=1, the administrator-authorized request also sends no_cache=1 to refresh the local pricing cache.

This service is provided by AdminPlugins: Terms of Service: https://adminplugins.com/terms-and-conditions/ Privacy Policy: https://adminplugins.com/privacy-policy/

Freemius SDK and Checkout

This plugin uses the Freemius SDK for optional Pro licensing, account management, software updates, and checkout. Free users can skip the Freemius opt-in and continue using all Free email delivery and routing features. The plugin loads the Freemius Checkout JavaScript from https://checkout.freemius.com/js/v1/ only after an administrator clicks an upgrade button, so the secure checkout overlay can open for the selected Pro plan. The checkout script is loaded only in the WordPress admin area and only after the administrator starts checkout from the plugin pricing screen. When an administrator opts in through the Freemius SDK, activates a license, opens the Freemius account/license screens, checks for updates, or clicks an upgrade button, Freemius may receive licensing and site/account data required to provide those services. Checkout-related data can include the product ID, plan ID, pricing ID, selected license quantity, billing cycle, currency, coupon code when active, and license key when upgrading an existing license. If the AdminPlugins pricing API is unavailable, the plugin can use Freemius pricing as a fallback only when the site is registered with Freemius and Freemius tracking permission is currently allowed. If the checkout overlay script is unavailable, the administrator is sent to the normal Freemius checkout URL instead.

This service is provided by Freemius, Inc.: Terms of Service: https://freemius.com/terms/ Privacy Policy: https://freemius.com/privacy/

Gmail / Google Workspace OAuth 2.0

When Gmail / Google Workspace OAuth is selected, an administrator explicitly starts authorization at https://accounts.google.com/o/oauth2/v2/auth. The plugin exchanges and refreshes OAuth tokens through https://oauth2.googleapis.com/token and sends the complete MIME email through https://gmail.googleapis.com/gmail/v1/users/me/messages/send. When an administrator explicitly clicks Disconnect, the plugin also sends the saved Google OAuth token to https://oauth2.googleapis.com/revoke to request authorization revocation before removing the local tokens. Data can include the OAuth Client ID and Client Secret during token requests, OAuth authorization code or refresh token, access token in the Authorization header, sender, recipients, subject, message body, headers, attachments, and inline embeds required to send the email. The Disconnect revocation request sends the saved Google OAuth token. The plugin requests only https://www.googleapis.com/auth/gmail.send and offline access; it does not request Gmail message-reading permissions.

This service is provided by Google: Terms of Service: https://policies.google.com/terms Privacy Policy: https://policies.google.com/privacy

Microsoft 365 / Outlook OAuth 2.0

When Microsoft 365 / Outlook OAuth is selected, an administrator explicitly starts authorization at the Microsoft identity platform endpoint under https://login.microsoftonline.com/. The plugin exchanges and refreshes OAuth tokens through the corresponding Microsoft OAuth 2.0 token endpoint. Small messages can be sent as MIME through https://graph.microsoft.com/v1.0/me/sendMail. When the direct request is not suitable, Titanium creates a temporary outgoing draft through /v1.0/me/messages, adds sub-3 MB attachments through the draft attachments endpoint, uses /attachments/createUploadSession plus Microsoft’s returned pre-authenticated https://outlook.office.com/... upload URL for 3 MB to 150 MB attachments, then sends the draft through /v1.0/me/messages/{id}/send. Microsoft Graph can accept upload-session attachments in that range, but the mailbox or tenant message-size policy can impose a lower effective message limit. Best-effort draft or upload-session deletion is attempted when an attachment/upload operation fails. Data can include the OAuth Client ID and Client Secret during token requests, tenant setting, OAuth authorization code or refresh token, access token in the Authorization header, sender, recipients, subject, message body, headers, attachments, and inline embeds required to send the email. The plugin requests delegated Mail.Send, Mail.ReadWrite, and offline_access. Mail.ReadWrite is required by Microsoft Graph for draft and attachment operations; Titanium uses it for these outgoing-message operations and does not intentionally read existing mailbox messages. Microsoft Disconnect removes the local WordPress tokens; Microsoft account consent may remain until it is revoked in the Microsoft account.

This service is provided by Microsoft: Microsoft Services Agreement: https://www.microsoft.com/servicesagreement Privacy Statement: https://privacy.microsoft.com/privacystatement

Postmark

When Postmark is selected, the plugin sends email data to https://api.postmarkapp.com/email. Data can include the Postmark server token, sender, recipients, subject, message body, headers, attachments, inline embeds, and message stream required to send the email, including an administrator-requested test email.

This service is provided by Postmark: Terms of Service: https://postmarkapp.com/terms-of-service Privacy Policy: https://postmarkapp.com/privacy-policy

Amazon Simple Email Service

When Amazon SES is selected, the plugin connects to the regional Amazon SES endpoint configured by the administrator, in the form https://email.REGION.amazonaws.com/. Data can include the AWS access key ID, signed request headers, session token when configured, sender, recipients, subject, message body, headers, attachments, and inline embeds required to send the email, including an administrator-requested test email. The AWS secret access key is used locally to sign the request and is not intentionally transmitted as a plain request field.

This service is provided by Amazon Web Services: Customer Agreement: https://aws.amazon.com/agreement/ Privacy Notice: https://aws.amazon.com/privacy/

SendGrid

When SendGrid is selected, the plugin sends email data to https://api.sendgrid.com/v3/mail/send. Data can include the SendGrid API key, sender, recipients, subject, message body, headers, attachments, and inline embeds required to send the email, including an administrator-requested test email.

This service is provided by Twilio SendGrid: Terms of Service: https://www.twilio.com/en-us/legal/tos Privacy Notice: https://www.twilio.com/en-us/legal/privacy

Mailgun

When Mailgun is selected, the plugin connects to https://api.mailgun.net or https://api.eu.mailgun.net, depending on the selected region, and uses the configured sending domain. Data can include the Mailgun API key, domain, sender, recipients, subject, message body, headers, attachments, and inline embeds required to send the email, including an administrator-requested test email.

This service is provided by Mailgun: Terms of Service: https://www.mailgun.com/legal/terms/ Privacy Policy: https://www.mailgun.com/legal/privacy-policy/

Brevo

When Brevo is selected, the plugin sends email data to https://api.brevo.com/v3/smtp/email. Data can include the Brevo API key, sender, recipients, subject, message body, headers, and attachments required to send the email, including an administrator-requested test email. The plugin does not send unsupported inline-embed messages through the Brevo API.

This service is provided by Brevo: Terms of Use: https://www.brevo.com/legal/termsofuse/ Privacy Policy: https://www.brevo.com/legal/privacypolicy/

Other SMTP

When Other SMTP is selected, email data and SMTP credentials are sent directly to the SMTP server configured by the administrator. Data can include the SMTP host, port, encryption and authentication settings, username, password, sender, recipients, subject, message body, headers, attachments, and inline embeds. The provider, terms, and privacy policy depend on the SMTP service selected by the administrator.

When Default (WordPress mail) is selected, this plugin does not directly send email data to any of the providers listed above. The server, hosting provider, another WordPress component, or another installed plugin may still handle delivery according to its own configuration.

Privacy

Titanium Mail SMTP Free stores its settings, routing rules, provider configuration, OAuth access and refresh tokens, migration state, and cached public pricing data locally in the WordPress database. Supported provider client secrets and other credentials can instead be defined in wp-config.php constants. The Free version does not include a persistent Full Email Log.

Test-email and OAuth result messages may be stored temporarily in short-lived WordPress transients so the administrator can see the result after the request completes. Complete normal email content is not intentionally retained by the Free plugin after delivery.

The Delete Titanium Mail SMTP settings when the plugin is uninstalled option controls removal of the plugin settings, migration markers, OAuth tokens stored within those settings, and pricing cache. Shared settings are preserved when a related Pro package still requires them.

Data sent to external services is described in the External services section above. Each configured email provider, Freemius, AdminPlugins, the hosting environment, and other WordPress components may process data under their own terms and privacy policies.