Jared Atchison
Forum Replies Created
-
This can be triggered by a handful or things, but the most common things we see that cause it is:
– Changing/resetting the password on your Google account
– Enabling 2 factor auth on your Google accountThese actions, or similar ones, typically will invalidate the existing tokens. When that happens you have to disconnect the auth in the plugin settings and run through the setup process again.
Hey brody182,
Thanks for clarifying! We take security very seriously at WPForms.
Unfortunately, without additional information we can’t assume this was due to WPForms. What your describing can also occur from incorrect file permissions and/or site setup, being hosted with a shared web host (where another site on the server gets hacked), etc.
If further details become available that point in our directions then we definitely want to know. However, at this point, with over 1 million active installs we have not had any reports of similar issues.
Sorry about that. This is a know issue with 1.3.x.
You can see more details here: https://ww.wp.xz.cn/support/topic/google-api-problem-2/#post-10448740
The short version of this is our release conflicts with Updraft because they are using an older version of the Google API than we are.
We’ll have this resolved next week. In the mean time there are steps in the link above you can use to downgrade as a temporary work around.
We never said there was not an issue with the Google API.
The issues that the original posters were describing in the other threads, which you decided to jump in on, were not – in any way shape or form – related to the Google API. I want to be clear about that. All those issues have since been resolved.
So to summarize: yes, you are correct, there is an issue in some cases with the Google API. However, you are causing confusion by posting in other threads that were created to report completely unrelated issues.
The previous implementation of the Google API library causes many various issues for users using the Gmail mailer. The update we did resolved most of these issues, but unfortunately the unintended side effect of that conflicts with other plugins that are using older versions of the API. Either way there are issues. We’re not going back, though. Instead next week we’ll figure out how to get around the issue and release an update that puts all this behind us.
In the mean time, you can downgrade as mentioned in the steps above, if you are affected by this.
- This reply was modified 7 years, 11 months ago by Jared Atchison.
Hey Nigel,
It’s definitely a tricky situation.
The root of the issue (or one of them) is that your web server’s IP address is not “clean”, which then hurts any emails that are sent from it.
The most common cause of this is shared hosting. When your site is on shared hosting, it means any where from a dozen to several hundred sites share the same IP. All it takes is one bad actor – at any point in time – and that IP is now “dirty” for the foreseeable future. The end result is similar to what you describe.
Few things you can try.
If you are in fact on shared hosting, most providers offer an addon feature to get a static IP for an additional monthly charge. This means an IP is then given to your site, and only your site, and will never change (under normal circumstances).
If you are not on shared hosting and already have static/dedicated IP, you see if your host can give you a new IP and hope it’s less tarnished. From what I’ve seen, this is hit or miss though. The thing his web hosting companies aren’t in the business of email delivery, so generally it’s semi-common (depending on the hosting company) that the IPs are not “clean”.
If you’re stuck with the IP, you can try messing with you SPF and/or DKIM. But be warned this is a super technical and complex process, that not only can I not explain here, but don’t fully understand 🙂 – check out https://blog.woodpecker.co/cold-email/spf-dkim/ for more information.
Lastly, the issue you’re running into is exactly why transaction email services such as Mailgun, SendGrid, Postmark, Amazon SES, etc are so popular. Because their entire business is around email delivery, so it’s in their best interest to have IPs in good standing and they take a bunch of measure to try to ensure this.
Hope that helps!
Happy to hear that. Thanks for reporting back.
Have a great weekend! 😎
Typically this happens because you contact form plugin is using a different “from email”.
The test email uses the “From Email” you have defined in your WP Mail SMTP settings. Your
contact form settings likely have something else configured.In your WP Mail SMTP settings, check to “Force From Email” setting (https://cl.ly/3u1I0Q2t1C3h) – this setting was added in v1.3 so you may need to update first to see this setting.
This will force your Google email address to always be used regardless of what other plugins try to do.
First, I really apologize for the trouble.
In 1.3.0 we updated our PHP Google API library. A side effect of that, in some cases, it causes a conflict with plugins which are using older versions of the Google API library.
We’re working on a plan to resolve the problem! I don’t have an exact ETA, but we should have it fixed next week.
If you’re affected by this, you can either temporarily deactivate WP Mail SMTP until next week when we address this issue, or if things worked for you prior to 1.3, you can downgrade.
To downgrade:
– On the WP Mail SMTP plugin page, go to Advanced (https://cl.ly/43321D403Z3v)
– Look for the “PREVIOUS VERSIONS” at the bottom of the page.
– Select 1.2.5 and it will download the previous version.Again, sorry about this. We’ll have a fix out as soon as we can 🙂
- This reply was modified 7 years, 11 months ago by Jared Atchison.
Just a heads up for future readers, we are no longer following are responding to this specific thread.
The original issue was around the error
Parse error: syntax error, unexpected ‘[‘.This issue was resolved in the 1.3.1 update.
If you’re having a PHP Google API error (or similar), please post to this existing issue https://ww.wp.xz.cn/support/topic/google-api-problem-2/
For other issues please create a new issue, do not reply to or bump this thread. It makes it too hard to keep track of things and we don’t want to miss bug reports!
Thanks!
Just a heads up for future readers, we are no longer following are responding to this specific thread.
The original issue was around a compatibility conflict with
tgmpa.This issue should be resolve as of version 1.3.2.
If you are having problems please create a new issue, do not reply to or bump this thread.
Just a heads up for future readers, we are no longer following are responding to this specific thread.
The original issue was around a compatibility conflict with
tgmpa.This issue should be resolve as of version 1.3.2.
If you are having problems please create a new issue, do not reply to or bump this thread.
Buried in the debug information is this line
Client host rejected: Access denied.This means that WP Mail SMTP is about to successfully connect to your SMTP host, but the SMTP host is rejected the connection.
This usually is due to a few reasons: SMTP username/password is incorrect, SMTP host is not setup to allow outside connections, SMTP host has a firewall and is blocking the connection, etc.
The best way to resolve this is to contact your SMTP host (or if the SMTP host is your web server, contact your web host), provide them the username/password you’re trying to connect with, and ask them to look why it’s stopping the connection.
Yes we do have a filter available for this, which should work for what you’re trying to do.
$phpmailer = apply_filters( 'wp_mail_smtp_custom_options', $phpmailer );For reference that is
wp-mail-smtp/src/Processor.php.Hope that helps!
Today version 1.3 was released and should address this issue. When you get a chance update to 1.3 and run though the setup steps again 🙂
This happens because Contact For 7 is using a different “from email”.
The test email uses the “From Email” you have defined in your WP Mail SMTP settings. Your CF7 form settings likely have something else configured.
To resolve you can do 1 of 2 things:
– Go into your CF7 settings and change the from email setting to match that inside the WP Mail SMTP settings.
– In your WP Mail SMTP settings, check to “Force From Email” setting (https://cl.ly/3u1I0Q2t1C3h) – this setting was added in v1.3 so you may need to update first to see this setting.