I’m not sure what you mean. Once the configuration is set, it should never change. Can you describe the problem you’re having? Are you using the same Client ID on more than one WordPress site?
Hi Jason,
Hope that you are well.
Yes the configuration is set and it is working for the first few weeks
it uses smtp.gmail.com:465 to send out email
and lately i did not receive any email nor server notification, i checked and send test email it said fail
i had to re-setup the whole thing again, and this round instead of using smtp.gmail.com it uses smtp.googleapis.gom:465
log per below:
it keep showing XOAUTH2 not supported
after reconfigure it is working again,
that is why is there any possibility once postman detected error when delivering email
it could notify owner using alternative smtp or contact method so we could fix it?
[Wordfence Alert] ronaldsoo.com Admin Login
Sent 3 mins ago
BPS Security Log – November 3, 2015 – 12:23 pm
Sent 2 hours ago
Postman SMTP Test (ronaldsoo.com)
Sent 2 hours ago
Postman SMTP Test (ronaldsoo.com)
XOAUTH2 authentication mechanism not supported 2 hours ago
BPS Security Log – November 3, 2015 – 11:25 am
XOAUTH2 authentication mechanism not supported 3 hours ago
[Wordfence Alert] ronaldsoo.com Admin Login
XOAUTH2 authentication mechanism not supported 3 hours ago
[Ronald Soo SKY Lounge | a place to eat, sleep, dive, and repeat] Notice of Password Change
XOAUTH2 authentication mechanism not supported 3 hours ago
[Wordfence Alert] ronaldsoo.com Admin Login
XOAUTH2 authentication mechanism not supported 3 hours ago
Unlock email requested
XOAUTH2 authentication mechanism not supported 3 hours ago
Unlock email requested
Delete | View | Transcript | Resend
XOAUTH2 authentication mechanism not supported 3 hours ago
this round instead of using smtp.gmail.com it uses smtp.googleapis.gom:465
Your results are suspicious. Would you please post a session transcript from one of the emails that resulted in XOAUTH2 authentication mechanism not supported.
is there any possibility once postman detected error when delivering email
it could notify owner using alternative smtp or contact method so we could fix it
This is a planned feature, but I don’t think this is your issue. I have a feeling your host is playing a trick on you.
hi Jason,
Hope that you are well.
Below is one of the XOATH2 transcript for your review..
This is the conversation between Postman and your SMTP server. It can be useful for diagnosing problems. DO NOT post it on-line, it may contain your account password.
220-Cloud-Linux-CPanel-04.rocksoft.net ESMTP Exim 4.85 #2 Tue, 03 Nov 2015 11:30:51 +0800
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.
EHLO localhost
250-Cloud-Linux-CPanel-04.rocksoft.net Hello cloud-linux-cpanel-04.rocksoft.net [202.71.110.97]
250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
STARTTLS
220 TLS go ahead
EHLO localhost
250-Cloud-Linux-CPanel-04.rocksoft.net Hello cloud-linux-cpanel-04.rocksoft.net [202.71.110.97]
250-SIZE 52428800
250-8BITMIME
250-PIPELINING
250-AUTH PLAIN LOGIN
250 HELP
AUTH XOAUTH2 dXNlcj1yb25hbGRzb28ud2ViZm9ybUBnbWFpbC5jb20BYXV0aD1CZWFyZXIgeWEyOS5JUUswaUtwUmM1bU5pTFFZMUdrOWlqSE5KNUMxampxYktlRFlCYkx4TG00aEpncXB5QUlyS09xRzdLRE0yV1gwZFFncFM2dwEB
504 XOAUTH2 authentication mechanism not supported
220-Cloud-Linux-CPanel-04.rocksoft.net
250-AUTH PLAIN LOGIN
504 XOAUTH2 authentication mechanism not supported
As I suspected. You haven’t connected to Gmail. You’ve connected to rocksoft.net. Obviously XOAUTH2 is not supported there.
it uses smtp.gmail.com:465 to send out email
Either you’ve haven’t configured it at the socket you say you did or your web host is redirecting the connections meant for Google back to itself. Postman should have detected this and warned you, either during the Connectivity Test or through the Setup Wizard.
previously smtp postman selected smtp.gmail.com:465 to send out the email
but i do not understand why it connect to rocksoft-.net
well rocksoft.net is where wordpress is hosted..
now it is working fine …. after i updated to the latest version and re configure all over again.
Here is what the Connectivity Test looks like when it is run against a host that is redirecting connections:
http://plugins.svn.wordpress.org/postman-smtp/assets/screenshot-11.png
Here is what the Wizard looks like when it is run against a host that is redirecting connections:
http://plugins.svn.wordpress.org/postman-smtp/assets/examples/wizard-mitm.png
You should see something similar on your own website as the text in yellow:
Warning: connected to x instead of y
This means you can not use smtp.gmail.com:465 at rocksoft.net. It’s not due to anything Gmail or the plugin is doing.
Have you talked to your host about the issue?
