Title: Incorrect authentication data
Last modified: August 24, 2016

---

# Incorrect authentication data

 *  Resolved [charmedlife](https://wordpress.org/support/users/charmedlife/)
 * (@charmedlife)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/incorrect-authentication-data/)
 * hmmm… (if my name seems familiar to you, it is because you were just answering
   me at wp-easy-smtp support. I clicked on you and saw this and figured, “let’s
   go!”…
 * It seems to be as you suggested there, 465 and 587 are blocked. I decided to 
   roll with the port 25 settings (no other choices being available with my level
   of knowledge). You wizard tells me in green that I am configured correctly but
   when I send the test email, I get “Incorrect authentication data”. What’s next?(
   and thank you!)
 * Dan
 * [https://wordpress.org/plugins/postman-smtp/](https://wordpress.org/plugins/postman-smtp/)

Viewing 11 replies - 1 through 11 (of 11 total)

 *  Plugin Author [Jason Hendriks](https://wordpress.org/support/users/jasonhendriks/)
 * (@jasonhendriks)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/incorrect-authentication-data/#post-5999667)
 * Hi again!
 * Can you post your diagnostic info from the Tips and Diagnostic menu?
 *  Thread Starter [charmedlife](https://wordpress.org/support/users/charmedlife/)
 * (@charmedlife)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/incorrect-authentication-data/#post-5999680)
 * OS: Linux p3plcpnl0870.prod.phx3.secureserver.net 2.6.32-531.29.2.lve1.3.11.1.
   el6.x86_64 #1 SMP Thu Dec 18 06:49:17 EST 2014 x86_64
    HTTP User Agent: Mozilla/
   5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko)
   Chrome/41.0.2272.118 Safari/537.36 Platform: PHP Linux 5.4.37 / WordPress 4.1.1
   en PHP Dependencies : iconv=Yes : spl_autoload=Yes : openssl=Yes : allow_url_fopen
   =Yes WordPress Plugins : Gravity Forms : Advanced iFrame : Advanced Image Styles:
   Akismet : Better Anchor Links : BJ Lazy Load : Builder Style Manager – BETA :
   Cloudinary : coolEye : Easy Theme and Plugin Upgrades : Google Doc Embedder :
   Google XML Sitemaps : Gravity Forms iContact Add-On : Gravity Forms Zapier Add-
   on : GZip Ninja Speed Compression : .html on PAGES : Huzzaz Video Gallery : Supremacy
   Plugin : Insert Headers and Footers : WPBakery Visual Composer : Media Grid :
   mPress Hide from Search : P3 (Plugin Performance Profiler) : Postman SMTP : Q
   and A FAQ and Knowledge Base for WordPress : S3Bubble Amazon S3 Video And Audio
   Streaming : iThemes Slideshow : WP-Juicebox : WP Realtime Sitemap WordPress Theme:
   Air – Custom Postman Version: 1.5.11 Postman Sender: [dan@mulhollandsecurity.com](https://wordpress.org/support/topic/incorrect-authentication-data/dan@mulhollandsecurity.com?output_format=md)
   Postman Transport URI: smtp:tls:plain://dan@mulhollandsecurity.com:************
   @smtp.gmail.com:25 Postman Transport Status (Configured|Ready|Connected): Yes
   |Yes|Yes Postman Deliveries (Success|Fail): 0|0 Postman Bind (Success|Fail): 
   Yes|No Postman Available Transports : SMTP (1.5.11) Postman LogLevel: 40000 Postman
   TCP Timeout (Connection|Read): 10|60
 *  Thread Starter [charmedlife](https://wordpress.org/support/users/charmedlife/)
 * (@charmedlife)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/incorrect-authentication-data/#post-5999687)
 * I will turn off a bunch of these plugins and see if that cures. (edit) I ran 
   it again with a lot of the plugins disabled. Still did not work, see following.
 * OS: Linux p3plcpnl0870.prod.phx3.secureserver.net 2.6.32-531.29.2.lve1.3.11.1.
   el6.x86_64 #1 SMP Thu Dec 18 06:49:17 EST 2014 x86_64
    HTTP User Agent: Mozilla/
   5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko)
   Chrome/41.0.2272.118 Safari/537.36 Platform: PHP Linux 5.4.37 / WordPress 4.1.1
   en PHP Dependencies : iconv=Yes : spl_autoload=Yes : openssl=Yes : allow_url_fopen
   =Yes WordPress Plugins : Gravity Forms : Better Anchor Links : BJ Lazy Load :
   Builder Style Manager – BETA : Cloudinary : Google XML Sitemaps : Gravity Forms
   iContact Add-On : Gravity Forms Zapier Add-on : .html on PAGES : Huzzaz Video
   Gallery : Postman SMTP : WP-Juicebox : WP Realtime Sitemap WordPress Theme: Air–
   Custom Postman Version: 1.5.11 Postman Sender: [dan@mulhollandsecurity.com](https://wordpress.org/support/topic/incorrect-authentication-data/dan@mulhollandsecurity.com?output_format=md)
   Postman Transport URI: smtp:tls:plain://dan@mulhollandsecurity.com:************
   @smtp.gmail.com:25 Postman Transport Status (Configured|Ready|Connected): Yes
   |Yes|Yes Postman Deliveries (Success|Fail): 0|1 Postman Bind (Success|Fail): 
   Yes|No Postman Available Transports : SMTP (1.5.11) Postman LogLevel: 40000 Postman
   TCP Timeout (Connection|Read): 10|60
 *  [luutaa](https://wordpress.org/support/users/luutaa/)
 * (@luutaa)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/incorrect-authentication-data/#post-5999735)
 * Hi It does same with me. I am pretty sure that the login information and the 
   settings are correct. I tried using GMail and SendGrid.
 * Can you please check the code? There seems to be some odd bug.
 *  Plugin Author [Jason Hendriks](https://wordpress.org/support/users/jasonhendriks/)
 * (@jasonhendriks)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/incorrect-authentication-data/#post-5999775)
 * [@luutaa](https://wordpress.org/support/users/luutaa/) please start your own 
   post, your problem is likely not the same.
 * [@charmedlife](https://wordpress.org/support/users/charmedlife/) did the wizard
   suggest that configuration? Or did you manually enter port 25? Because if your
   site is hosted at GoDaddy, then I would have expected port 25 to be **closed**,
   just like 465 and 587.
 * Would you please run the Connectivity Test to (smtp.gmail.com) and post the results
   here. I just ran it on my GoDaddy test site and the results look like this [[screenshot](http://plugins.svn.wordpress.org/postman-smtp/assets/examples/Screen%20Shot%202015-04-10%20at%209.35.52%20AM.png)].
   I would have expected yours to be the same.
 * At GoDaddy, I also expect port 443 to be open, which means using the [Postman Gmail API Extension](https://wordpress.org/plugins/postman-gmail-extension/)
   to send your mail.
 *  Thread Starter [charmedlife](https://wordpress.org/support/users/charmedlife/)
 * (@charmedlife)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/incorrect-authentication-data/#post-5999790)
 * [http://screencast.com/t/zB7gTYmvoZ](http://screencast.com/t/zB7gTYmvoZ)
 * Given a choice between doing things on my own and following a wizard, I ALWAYS
   follow the wizard! 25 was what the wizard dictated.
 * I am pretty sure that when I used the wizard last night that 443 did not come
   up as a choice, but here it is now in all its splendor!
 * I will install your Postman Gmail extension now and let you know what occurs.
 *  Plugin Author [Jason Hendriks](https://wordpress.org/support/users/jasonhendriks/)
 * (@jasonhendriks)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/incorrect-authentication-data/#post-5999791)
 * Thanks for the faith you put in my software! 😉
 * Your GoDaddy screenshot is not what I expected. I am obviously going to have 
   to add the NAME of the detected server in that table, because even though you
   ran the test again smtp.gmail.com, that’s not Google you’ve connected to!!
 * I’ll tell you what’s going on here, GoDaddy is intercepting all outbound connections
   to **anywhere** on port 25 and **redirecting** them to their own SMTP server,
   which is why your Google credentials are not working. I know this because Google’s
   mail server would have reported OAuth 2.0 as available.
 * Oh, GoDaddy. I don’t like when ISP’s mess with sensitive data like that, especially
   when that data is your name and password. If I could I would disable port 25 
   in Postman, because it [allows all kinds of nastiness](http://it.slashdot.org/story/14/11/11/2349244/isps-removing-their-customers-email-encryption).
 * Install the Postman Gmail Extension and re-run the wizard. **You’ll have to override
   the wizard’s recommendation to force googleapis.com:443, as the Wizard prefers
   STARTTLS over HTTPS.** I’ll have to change that.
 * But that should solve your issue.
 *  Thread Starter [charmedlife](https://wordpress.org/support/users/charmedlife/)
 * (@charmedlife)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/incorrect-authentication-data/#post-5999797)
 * Thanks.
 * I opted for 443 and then was directed to set up a new Client ID and Secret, and
   began to follow the instructions to do that.
 * Here is what I got, with some notes:
 * [http://screencast.com/t/zS8R6rzbeaw](http://screencast.com/t/zS8R6rzbeaw)
 * So, I am guessing that I should just follow through and click “Create New Client
   ID” under the OAuth heading and get my information to cut and paste from what
   follows. (That’s a little different than the wizard’s instructions.)
 * So, I am asking the wizard behind the wizard!
 * I don’t want to do something wrong, blow up the internet and leave millions of
   google programmers broke and homeless!
 *  Thread Starter [charmedlife](https://wordpress.org/support/users/charmedlife/)
 * (@charmedlife)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/incorrect-authentication-data/#post-5999801)
 * I talked it all over with my priest (thankfully he is pretty internet savvy) 
   and he told me that he thought that it would work if I went ahead and that I 
   would be absolved of all my sins if it did not work and so I went ahead and went
   through with my guess and it all configured nicely with little green “Success!”
   stuff from your wizard all over the place.
 * Do you know the song, Mr. Postman, from, I think, the Shirelles? Youtube it!
 * Dan
 *  Plugin Author [Jason Hendriks](https://wordpress.org/support/users/jasonhendriks/)
 * (@jasonhendriks)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/incorrect-authentication-data/#post-5999804)
 * Hi Dan. Sorry, where are you stuck? I couldn’t figure out from the screenshot.
 * Did you enable the Gmail API under ‘APIs’ ?
    Then just create the Client ID, 
   which is the blue button on the screen you sent me.
 * Or maybe you’re not stuck anymore? If there was a point in the FAQ that was confusing
   please let me know, Google changed this screen recently and I’m so used to it
   I can do it blindfolded by now.
 *  Thread Starter [charmedlife](https://wordpress.org/support/users/charmedlife/)
 * (@charmedlife)
 * [11 years, 1 month ago](https://wordpress.org/support/topic/incorrect-authentication-data/#post-5999850)
 * It pretty much all worked out. In the screenshot. The only thing is there is 
   a small little change in the step between 1 & 2 in the screenshot, where google
   wants you to click the 0Auth heading. After that, your documentation syncs up
   again with what’s actually happening. It took me a few minutes to figure out,
   and I think most will, even if you don’t update the documentation.
 * Thanks so very much for sticking with me and I am very impressed with the plugin
   and your support. I wish you the very best.

Viewing 11 replies - 1 through 11 (of 11 total)

The topic ‘Incorrect authentication data’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/postman-smtp_7c7b78.svg)
 * [Postman SMTP Mailer/Email Log](https://wordpress.org/plugins/postman-smtp/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/postman-smtp/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/postman-smtp/)
 * [Active Topics](https://wordpress.org/support/plugin/postman-smtp/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/postman-smtp/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/postman-smtp/reviews/)

 * 11 replies
 * 3 participants
 * Last reply from: [charmedlife](https://wordpress.org/support/users/charmedlife/)
 * Last activity: [11 years, 1 month ago](https://wordpress.org/support/topic/incorrect-authentication-data/#post-5999850)
 * Status: resolved