This plugin adds a new settings page for each form created, to allow configuration for sending emails through an SMTP mail server. It gives you a way to have different SMTP server settings for each form you create.
If you do not need it, you can simply leave the settings blank, and it will revert to the site’s default mail sender.
- Browse to the Gravity Form Admin, and click on Settings for the form.
- Click SMTP Settings
- Fill in the details to override the built-in WordPress Mail sender for the form
.1 SMTP password will be be encrypted prior to sending to the WordPress Database. Please note that is uses the WordPress Built-In salts from wp-config. If these change in anyway, you wll need to enter the SMTP password again.
- Download the plugin, unzip it, and upload to your sites
- You can also upload it directly to your Plugins admin
- Activate the plugin through the ‘Plugins’ menu in WordPress
Do I need this plugin if I already use a SMTP plugin?
Not necessarily. This plugin is not meant to replace your sitewide SMTP mail sender, but rather gives you a way to utilize separate SMTP settings for each Gravity Form in your site.
Outlook 365 SMTP Settings are not working… HELP?!
Outlook 365 requires the From email address to be the exact same as the account used to authenticate. Make sure you update your settings.
Does this override the entire site’s mail sending?
No. Instead it overrides it for the form you have the settings configured for only.
- fixed issue with no from address
- was an issue with the way Form Notifications are setup
as defaults in GravityForms itself
- added replyto field in settings
- added logging mechanism
- debug will not longer show on front-end
stricly logs to
- fixed null setting
- fixed sanitization
- more stringent checks for valid email addresses
- strongly type methods
- convert comments to phpdoc format
- fix proper OR for DIE for direct access
- Icon for settings menus
- fixed smtp password not saving
- completely rewrote the encryption/decryption methods
- found out what was happenning was the algorithms were not installed on every machine
- also checking if methodology is available now, if not simply base64 encode/decode
- uses the SECURE_AUTH_* salts from wp-config.php
- Update for 5.8 compliance
- Require PHP 7.3
- Update for 5.7.2 compliance
- Update for GF 2.5 compliance
- Method strong typing
- Update for 5.7 compliance
- check for existing functionality
- Fix deactivate if GF is not activated
- True autoloader
- rename class files to match
- update encrypt/decrypt methods to use WP salt
- will need to re-save settings
- implement proper testing messages