Sounds like a general mail problem. Are you using an SMTP plugin? Who is your email provider?
Thanks.
I am not using an SMTP plugin so far as I am aware.
I use gmail.com for email; my friend who also tried uses email from inbox.com.
That email that Mailchimp sent and you received, did it use a From: address of your @gmail.com account? And I’m assuming all the rest (the ones that didn’t work) also use your @gmail.com account as the From: address?
Yes.
On your second question I do not know as they received no confirmation email.
Thanks for the thoughts.
Sounds like a pretty simple fix then. Install an SMTP plugin and point it at smtp.gmail.com. Should solve your problem. Try mine. https://wordpress.org/plugins/postman-smtp/
Thanks.
I’m confused though. MailChimp used to work and I did not change anything but something is clearly different now.
Using a nongmail address to subscribe had the same results as gmail so I am not sure that SMTP plugin solution will fix more than delivering post updates to gmail?
This morning I subscribed from trout@naturalproductsofboonville.com which is hosted by webgator. I received the confirmation email just fine. I confirmed, created a new post at troutsnotes.com, posted it and no notifications were received via any of the, now four, email accounts that have been subscribed specifically to test this.
IN the future I actually do not need to receive a notification that I have made new posts, I’m just trying to determine why other people are not getting notifications from MailChimp.
Thanks.
I don’t work for Google, but I gather it’s something like this. Your email shows up to a @gmail.com recipient, claiming to be from a @gmail.com sender, and Google knows this is false because it never went through authentication at smtp.gmail.com, ergo forgery, ergo spam or virus. This causes the account to lose reputation. There are lots of other checks including content, IP address, SPF and DKIM for custom domains. Eventually you trip a flag that says require increased security, and that’s probably what’s happened to you.
You get really bad and Google simply disables password-authentication.
All this to prevent you from sending mail pretending to be from me … jason@gmail.com for example. Google disabled my password-authentication for my Google Apps account in December, and I’m forced to use OAuth 2.0 now.
See http://googleonlinesecurity.blogspot.ca/2014/04/new-security-measures-will-affect-older.html
Using a nongmail address to subscribe had the same results as gmail
If this “nongmail address” is Hotmail or Yahoo or AOL, they are doing the same SPF/DKIM checks again the sender address, which you said was @gmail.com, and rejecting (black-holing) the email for the same reason Google did.
All this to say, to rule out that you’re not looking in the wrong place for your solution, make sure your email is setup right in the first place.
Thanks, I’ll download and install that. At least the gmail side of the problem will be taken care of.
I’m not sure how it will affect the rest of the subscribers not getting mailchimp notifications though. That is what I am confused by.
The next thing you’re going to have to watch out for is Gmail limits. I believe with Gmail it is 100 recipients per message, up to 500 recipients per day.
If your Mailchimp needs exceed that you need to use another email service, like Google Apps, Mandrill, Mailgun, Sendgrid, etc.
Thanks. There are presently 74 subscribers requesting notifications of new blog posts. A new post usually occurs once every few weeks.
I downloaded and installed your plug in. That was no problem.
When I next tried to configure it to handle the email and was directed to google for obtaining a client ID I became completely lost and confused. Reading their FAQ and instructions left me thinking I may lack education enough to understand what is even being discussed.
When the wizard suggest that you use OAuth 2.0, choose Password instead.
Thanks, I’ll try that now.
That seemed to all go fine up until the test email. That failed to send.
The error message now accompanying hte plug in says “5.7.14 Please log in via your web browser and 5.7.14 then try again. 5.7.14 Learn more at 5.7.14 https://support.google.com/mail/bin/answer.py?answer=78754 sm8sm5206855obb.13 – gsmtp”
That link gives me a missing page notice.
Thanks on any thoughts. I think I may need to find help with better education than me.
I was pasting too many characters.
Google sent me a notice they had blocked my attempt:
“If this was you
You can switch to an app made by Google such as Gmail to access your account (recommended) or change your settings at https://www.google.com/settings/security/lesssecureapps so that your account is no longer protected by modern security standards. “
This is increasingly confusing.
How can MailChimp actually work if google doesn’t respect people requesting it and confirming they want to subscribe? (Or recognizing me due to knowing my own password?) Decreasing protections seems backwards.
Thanks though!
How can MailChimp actually work if google doesn’t respect people requesting it and confirming they want to subscribe?
These problems will all go away once you get your email configured correctly.
Remember what I said about Google disabling password authentication? That’s exactly what’s happened to you… the error 5.7.14
If you are not a Google Apps user, you have two options to make this work 100%. The first is to do what Google suggested, and reduce your account security by clicking on this link : https://www.google.com/settings/security/lesssecureapps
Decreasing protections seems backwards.
Yup š See? Smarter than you think.
Your second option, and the only option if you use Google Apps, is to configure OAuth 2.0. This was the same option you tried above where you said you “became completely lost and confused”.
It’s not that hard… there are only a few steps:
- Go to Google Developer’s Console and choose ‘Create Project’
- Select ‘API’s’ from under ‘APIs & auth’. Find ‘Gmail API’. Select ‘Enable API’.
- Select ‘Consent Screen’ from under ‘APIs & auth’. Into ’email address’ choose the correct Gmail address and in ‘product name’ put ‘WordPress’. Choose ‘Save’.
- Select ‘Credentials’ from under ‘APIs & auth’. Choose ‘Create a new Client ID’.
- In ‘Authorized Javascript origins’ enter the ‘Javascript Origins’ given by the plugin
- In ‘Authorized Redirect URIs’ enter the ‘Redirect URI’ given by the plugin
- Last step. Enter the Client ID and Client Secret that Google generates into the plugin.
