Postie wp app install#

Scroll down the screen and click ADD URI. You can skip the next step ( Scopes) as it’s an optional step and continue with the OAuth Client ID, where you need to select Web application as the application type. Then, provide the app information like your App Name, User Support Email, and Developer Email Address, and click SAVE AND CONTINUE.

Next in the process is to create credentials for SMTP configuration. If it’s for the first time then you need to register your application for Gmail API, or simply Create a project and click Continue.Īfter a few seconds, the next screen will appear. To get the Client ID and the Client Secret, visit Google API Console and log in to your Gmail Account if asked. In the Authentication screen, you will need to input two parameters: Client ID and Client Secret to configure it. The wizard will automatically recommend and select: SMTP-STARTTLS with OAuth 2.0 authentication to host on port 587. The wizard will run a Connectivity Test and after that, you will see the connection screen.

Within a few moments, the plugin will auto-resolve the Gmail SMTP server. To power the plugin, I have also introduced the handy troubleshooting screen on the right.Ĭlick on the “ Start The Wizard” button, and enter your Email Address and Name. This is the main screen of the WordPress Post SMTP plugin.

Postie wp app install#

Step 11: Add Copy Client ID and Client Secrettĭownload and install Post SMTP directly from the WordPress plugin repository.Īfter installing and activating the plugin, you will see a message inviting you to start configuring the plugin.Step 9: Gmail API in Google API Console.Let me take you to a step-by-step guide on setting up the Post SMTP WordPress plugin with Gmail/Google Apps and 0Auth so that Postman SMTP users and others can set it up properly. Within a few days, the Post SMTP plugin got more than thousands of active installs and now the plugin has more than 200,000 active installations.

I have named the fork “Post SMTP Mailer/Email Log”, and you can get it from the WordPress repository. While Jason Hendriks, the man behind the plugin, had created an excellent tool for WordPress users, he was unable to maintain the plugin later.Īs a WordPress developer and active user of Postman SMTP, I decided to fork the plugin so that all of Jason’s hard work didn’t just end up in the bin. Some security researchers even tried, unsuccessfully, to contact the plugin’s author. The plugin had not just been removed because of the vulnerability – it had also not been updated in the last sixteen months, making it incompatible with the latest release. Follow October 2017, popular SMTP plugin Postman SMTP, with 100k+ active installs, was removed from the WordPress repository due to an XSS vulnerability.