Gravity SMTP has been updated to version 2.3.3, which includes important security enhancements along with new integrations and reliability improvements…
- Security enhancements, including a fix for an issue that exposed license keys to users without permission to view them.
- Added the ability to define a Tenant when sending with Amazon SES, enabled the routing of emails through the Members plugin integration, and allowed the sharing of a single license key constant between Gravity Forms core and Gravity SMTP.
- Improved connection reliability for Google, Microsoft 365, and Zoho Mail, so a failed or abandoned OAuth connection attempt no longer shows as an active integration or becomes your primary connector.
We recommend updating to 2.3.3 as soon as possible for the latest protections and improvements.
Smarter routing and setup
Gravity SMTP 2.3 introduced conditional email routing, letting you send messages through different integrations based on rules you define. Version 2.3.3 extends that routing to the Members plugin, so you can route emails using Members plugin criteria alongside your existing rules.
If you send through Amazon SES, you can now define a Tenant when sending, giving you finer control over how messages are organized and delivered in multi-tenant setups.
And if you manage Gravity Forms and Gravity SMTP together, you can now define a single license key constant that both plugins use, so you only have to set it once.
Better email delivery starts here
WordPress’s default mail setup often isn’t built for reliable delivery. Gravity SMTP improves message delivery, increasing inbox placement and reducing the chance your emails get flagged as spam.
It offers an easy setup process, built-in migration tools, support for the email services you already trust, and clear reporting so you always know what happened to your messages.
Key features
- Automatic backup connection – establishes a secondary email route for immediate activation during primary connection failures, keeping your emails flowing.
- Comprehensive email logging – keeps detailed records of every outgoing message, including recipient data and delivery status.
- Insightful reports dashboard – gives you an at-a-glance view of email performance.
- Real-time failure alerts – delivers immediate notifications via webhook or SMS integration when a delivery problem occurs.
Get Gravity SMTP today
Gravity SMTP is available at no extra cost for Gravity Forms Elite, Nonprofit, and Developer license holders. If you don’t already have it installed, visit your Gravity account to download it.
For a full walkthrough of setup and configuration, check out the Ultimate Guide to Gravity SMTP, or dig into the details in our documentation.
Gravity SMTP 2.3.3 changelog
- Security enhancements.
- Added the ability to define a single license key constant to use between GF core and SMTP.
- Added the ability to define a Tenant when sending with Amazon SES.
- Added the routing capabilities to the Members plugin integration.
- Fixed a fatal error in strip_sensitive_log_data() when headers is a string.
- Fixed a PHP warning when a Zoho Mail OAuth token exchange returns an error response.
- Fixed a typo in the fatal error message shown when sending fails.
- Fixed an issue that caused the Zoho Mail integration to fail to connect and send email for accounts on non-US datacenters.
- Fixed an issue that exposed license keys to users without permission to view them.
- Fixed an issue that prevented the Gravity Forms license key from being used on the Gravity SMTP Settings page when the setup wizard was skipped.
- Fixed an issue where a long email subject with multi-byte characters could prevent the message from being logged.
- Fixed an issue where fast typing in the Email Log, Suppressions, and Debug Log search fields could remove entered characters.
- Fixed an issue where removing and re-adding an integration retained its previous settings.
- Fixed an issue where the Google OAuth callback could replay on page refresh, retain a stale connection error, and skip validation of the state parameter.
- Fixed an issue where the integration URL parameter stayed in the address bar after the integration flyout closed, which reopened the flyout on refresh.
- Fixed an issue where the Microsoft OAuth callback could replay on page refresh, retain a stale connection error, and skip validation of the state parameter.
- Fixed an issue where the Zoho Mail OAuth callback could replay on page refresh, retain a stale connection error, and skip validation of the state parameter.
- Fixed an issue where the Zoho Mail sign-in button used the authorization URL for the previously saved datacenter after the Datacenter Region setting changed.
- Fixed an issue where Zoho Mail omitted CC, BCC, and additional To recipients.
- Fixed an issue that can cause expired Zoho tokens not to refresh when the current token fails.
- Fixed integration descriptions being truncated when adding a connection.
- Fixed Microsoft connected account details and improved mailbox error guidance.
- Fixed removed integrations still appearing as Send With options on the Send a Test tool.
- Fixed routing preview access to respect smart routing availability and permissions.
- Fixed an issue that can cause MySQL errors when installing the plugin for the first time.
- Fixed an issue that can cause string-formatted attachment headers to throw a fatal on send.
- Updated the Google / Gmail integration to activate only after the OAuth connection completes, so a failed or abandoned connection attempt no longer shows as an active integration or becomes the primary connector.
- Updated the Google / Gmail settings to require fresh credential entry when no connection exists, which prevents an obfuscated client ID from reaching the Google authorization URL.
- Updated the Microsoft 365 / Outlook integration to activate only after the OAuth connection completes, so a failed or abandoned connection attempt no longer shows as an active integration or becomes the primary connector.
- Updated the Microsoft 365 / Outlook settings to require fresh credential entry when no connection exists, so a reconnect after a failed or abandoned attempt starts clean.
- Updated the Zoho Mail integration to activate only after the OAuth connection completes, so a failed or abandoned connection attempt no longer shows as an active integration or becomes the primary connector.
- Updated the Zoho Mail settings to require fresh credential entry when no connection exists, which prevents an obfuscated client ID from reaching the Zoho authorization URL.
If you have any questions about Gravity SMTP or how to get started with this plugin, our expert Support team is available to help.
Newsletter
If you want to keep up-to-date with what’s happening on the blog sign up for the Gravity Forms newsletter!
"*" indicates required fields
