WPForms Blog

WordPress Tutorials, Tips, and Resources to Help Grow Your Business

Coming Soon – New & Improved WP Mail SMTP 1.0 [Sneak Peek]

by Keri Engel on Dec 6, 2017

Six months ago, we announced that we acquired the best SMTP plugin for WordPress.

Our goal: Make it easy to solve the email deliverability problems that the entire WordPress community faces.

After months of development, we’re excited to share with you that WP Mail SMTP 1.0 is nearly ready!

Before the release, in the interest of transparency, we wanted to give all WP Mail SMTP users a heads up on what’s coming.

WP Mail SMTP 1.0 – What’s New?

This is no ordinary update. In fact, we’ve spent the past 6 months completely rewriting the plugin from the ground up, using modern standards and practices and adding new features.

But don’t worry – if youโ€™re currently using WP Mail SMTP on your site, rest assured it will continue to work as normal.

Also, WP Mail SMTP will continue to operate as an independent plugin. There’s no need to use WPForms in order to use WP Mail SMTP – although we do recommend it as the best drag & drop form builder for WordPress ๐Ÿ™‚

After updating, you won’t even notice a difference until you check out the settings page.

There you’ll see our new pigeon mascot, Suzie…

…and several new options for securely enabling SMTP on your site – quickly and easily.

Previously the only option was to set up SMTP using your Gmail, Yahoo or Microsoft Live/Hotmail/Outlook email account. However, this method is less secure because it stores your email login and password in your WordPress dashboard, where other WordPress administrators have access to it.

In the new version of WP Mail SMTP, you’ll have four different options:

  • SMTP
  • Mailgun
  • SendGrid
  • Google (G Suite or Gmail)

In other words, WP Mail SMTP will now do the job of 4 plugins in 1. The non-SMTP methods will be more secure, since you fill in your API key and other info without having to store a password in plaintext.

Now we’ll actually have native integrations with those providers. That means if your web host is blocking the common SMTP ports, which is common, you can use any of those other services to bypass the problem.

Plus, support for these providers was built in a modular way. This means in the future it will be easy for us (or other developers) to add support for other popular providers such as Postmark, Amazon SES, and more.

When Is the Launch Planned?

Weโ€™re planning to release WP Mail SMTP 1.0 release next week, so stay tuned and be ready to update!

If you have any questions, please feel free to get in touch.

Thanks for all your support! We’re excited to bring you these new features and look forward to developing more soon.

Keri and the WPForms Team

Comments

  1. This is awesome. Great work!! look forward to the updated plugin. I have used it on many sites over the years and it is such a life saver.

    1. Thanks so much, Julian! Happy it’s helping you out ๐Ÿ™‚ Do let us know if you ever have any suggestions to improve it further.

  2. I am using gmail with this plugin
    December 5 I can not connect to STMP
    It may be caused by security of gmail
    ???

    I am sorry for my poor English.

    1. Hi Kumiko,

      Yes, that’s certainly possible. There are a couple things you’ll need to check:

      1) That less secure apps are enabled for your Gmail account
      2) That your Gmail account hasn’t blocked the SMTP (you should have received a ‘Someone has your password’ email if this happened)

      For more details on both of these, please see our tutorial on how to set up WP Mail SMTP.

      Last, if neither of these seem to be the issue I would recommend next contacting your site’s hosting provider (they may be blocking the port you need).

      I hope that helps! ๐Ÿ™‚

  3. Hi,

    Terrific news but really hope you consider Amazon SES in the near future.
    Would also be great to have features to add a header and footer/signature to all outgoing emails.
    Thanks,
    Dale.

    1. Hi Dale,

      Thanks for the suggestions! We’re keeping our options open to add additional mailers like Amazon SES down the road, though for now we’re going to mainly focus on the providers mentioned here. As far as headers and footers, this is an interesting idea — though the challenge is that many emails that go out from your site (including our WPForms form notifications) already include these. We’ll keep that idea in mind, though!

      Have a good one ๐Ÿ™‚

    1. Hi Salo,

      Great question, however SSL certification for emails is actually configured via your server, by your site’s hosting provider. So if you’d like to get this in place, the best next step is to reach out to your host for more details.

      Hope that helps!

  4. I have used this plugin and recommended it for so many years, it was simple and got the job done, but with email services (google in particular) preferring API and OAuth it has become less useful.

    It’s great to see that it’s coming with some new updates, and look forward to recommending it again!

    Will the Google option be using OAuth?

    1. Hi Marcus,

      Yes, that’s correct — our Google option will be using OAuth. So it’ll require some extra steps to set up within your Google account, but will be much more secure than the current method (though the old method will still work as well).

      Hope that helps! ๐Ÿ™‚

  5. Hi, can you tell me what will happen to websites that currently use WP Mail SMTP with Pepipost? What will happen if we upgrade the plugin? Will everything continue to work as normal, or will it break?

    1. Hi Chris,

      Don’t worry, everything will continue to work normally when you upgrade — even if you’re currently using Pepipost.

      Our team has carefully designed the update so that anyone already using Pepipost will be able to continue with that as a main option (no changes needed) — and if you’d like to use it on any new sites, you can still do so by using our “Other SMTP” option (shown in this screenshot).

      I hope that helps! ๐Ÿ™‚

    1. Hi Shahmoon,

      Absolutely — any SMTP settings that you already have in place will continue to work just the same. So while you’re welcome to switch to one of these new, more secure methods if you’d like, you can also continue using your current options (no need to change anything).

      I hope that helps! ๐Ÿ™‚

    1. Hi Duncan,

      You can absolutely use Pepipost if you’d like, however we’re no longer offering that as one of the main options. So if you already have Pepipost in place, it’ll continue to operate just as before (no changes needed). And if you want to use Pepipost on a new site, you can do that by choosing our “Other SMTP” option.

      Thanks! ๐Ÿ™‚

  6. Thank you for this – really excited about the provider integrations, as that will alleviate the concerns re: password exposure in the admin dashboard.

    1. Hi Ryan,

      Absolutely, the security issue was the highest priority for us to address in this update. Please be sure to check in after the update rolls out and let us know what you think!

      Have a good one ๐Ÿ™‚

  7. Hello,

    I am a web designer. I use your plugin on hundreds of websites. Thank you so much.

    We are excited about the update. ๐Ÿ™‚

    You guys are great. ๐Ÿ™‚

    Best regards.

  8. Suggestion for the app: Would love to have a setting that allows the plugin to send me a test message on designated basis. I’ve had some sites with problems with sending emails. If I could get a weekly (for example) email from the site, that would make it easier to keep an eye on it. I had a site that had a lot of intermittent issues that drove me crazy but my only option was to remember to keep checking to see if the plugin was still working. I’d like to know there is a problem before my clients do. Thanks!

  9. Many thanks to you for your work!
    We are looking forward to the release of a new version of the much needed plug-in!

    1. Thanks ะะปะตะบัะตะน, please check back after its release to let us know what you think! ๐Ÿ™‚

  10. My server has a limit of 800 emails per hour that can be sent out, can we set a hourly limit or throttle the emails sent out some way? Can we cache the emails and send them via a WP crone job in some way?

    1. Hi Forest,

      To solve a limit issue like this, we’d recommend you look into an email sending service such as SendGrid or Mailgun. These are designed to handle very large email needs like you’re describing.

      I hope that helps!

  11. Hi,

    I’m very happy to hear about this upgrade. But why is there no way to dismiss the large message you’ve placed in every single one of my websites’ dashboards — and on every single page of the admin area, no less? ๐Ÿ™‚

    It is very intrusive and disturbs our work. How can it be removed please?

    Thank you!

    1. Hey Biranit,

      Thanks for reaching out. We appreciate your support!

      You should be able to dismiss the notice by clicking one of the buttons in the message. If for some reason that isn’t doing the trick, there may be a conflict on your site with the AJAX we use to dismiss the message. I really apologize for this. Rest assured we definitely don’t want to intrude or annoy our users.

      The good news is with the new update going out next week this message will forever go away! If after the update you still can’t get rid of the message please reach out so we can investigate the issue further ๐Ÿ™‚

    1. Hey Clint,

      In the next version the password will not show in the settings page (it will be a password field, so it will show *****), however because the password has to be sent to the SMTP host in plain text, it is still stored in the database as plain text.

      With that said, we will offer an alternative (and much more secure) method to define your password by pasted a few lines of code in your site’s wp-config.php file. After you upgrade, you’ll see more details about this in the password field description ๐Ÿ™‚

Add a Comment

We're glad you have chosen to leave a comment. Please keep in mind that all comments are moderated according to our privacy policy, and all links are nofollow. Do NOT use keywords in the name field. Let's have a personal and meaningful conversation.