Hi joewal72,
I didn't mention this before because I wasn't sure it would make a difference but your are running on an older version of POP Peeper. There have been 3 version releases since v4.3 on Oct 25, 2016 as you can see by checking out the POP Peeper Version History page. I'm not so sure this will help in regards to Yahoo "Webmail" (Server type "Yahoo") of which these accounts will probably revert back to "Login Error: Check your Login Name and Password." presumably due to changes Yahoo is rolling out to their "Webmail" protocol that will will likely necessitate a new PP "Webmail plugin release, but it may help with "IMAP" and/or "POP3". So if updating to the current POP Peeper version v4.4.2 released on June 16, 2017 fixes the "IMAP" protocol for Yahoo then you can then change all your accounts to this preferred protocol.
You can update POP Peeper by going HERE and simply update over the current version (it is advisable to exit POP Peeper when doing this).
Please report back with your results after updating POP Peeper to the current v4.4.2 build.
Can no longer login to Yahoo mail
Re: Can no longer login to Yahoo mail
Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers
Re: Can no longer login to Yahoo mail
joewal72 -- The subsequent *webmail* releases since your webmail v4.4.3 (current webmail is v4.4.6) have all been targeted for Yahoo and you would certainly need v4.4.6 for it to work (v4.4.4 specifically mentions the -11 error). After you update POP Peeper to v4.4 as suggested by lakrsrool, make sure that you have the latest webmail version under Help / About; make sure that both "auto update" checkboxes are enabled there and press the "check version" button.
That being said, I was under the impression that the "login error" was more of a permanent one. So if you have accounts that were showing the "login error" and are now able to login (with webmail v4.4.6), I would be very interested to know about that.
And as for the imap "bad connection" errors -- you had mentioned that the ping test timed out which is indicative of a general issue that is specific to your computer. That is, something must be blocking that server. If you're behind a corporate firewall (e.g. at your workplace), then it may be that they don't want you checking your email (although, why they wouldn't also block http://mail.yahoo.com...). But more likely, you probably have some security software that isn't setup correctly, such as AntiVirus.
That being said, I was under the impression that the "login error" was more of a permanent one. So if you have accounts that were showing the "login error" and are now able to login (with webmail v4.4.6), I would be very interested to know about that.
And as for the imap "bad connection" errors -- you had mentioned that the ping test timed out which is indicative of a general issue that is specific to your computer. That is, something must be blocking that server. If you're behind a corporate firewall (e.g. at your workplace), then it may be that they don't want you checking your email (although, why they wouldn't also block http://mail.yahoo.com...). But more likely, you probably have some security software that isn't setup correctly, such as AntiVirus.
Re: Can no longer login to Yahoo mail
Hi @all,
many thanks for your information and support.
I have to report a quite astonishing development after installing the updated software is advised.
I did that on Saturday and immediately afterwards all accounts worked, not only the ones which were converted to IMAP and OAuth2, but also the other ones, which were still using the YAHOO server type method.
Then it was good, that I did wait with the feedback to you until today, since starting this morning, the accounts using the YAHOO server type method were still working, but not longer the ones which I already had converted to IMAP and OAuth2.
For these I got the following error messages:
--- Version ---
OS: Windows 7 (x64)
POP Peeper: 4.4.2.0
Webmail: 4.4.6.0
SSL: 1.0.2.11
IMAP: 4.4.2.0
SendMail: 4.4.2.0
--- Error ---
YYYYY [1000: IMAP] ['imap.mail.yahoo.com' (993) SSL: 1] [Smtp: 'smtp.mail.yahoo.com' (465) SSL: 1] [Consec: 2]
- Bad Connection
YYYYY [1000: IMAP] ['imap.mail.yahoo.com' (993) SSL: 1] [Smtp: 'smtp.mail.yahoo.com' (465) SSL: 1] [Consec: 2]
- Bad Connection
Strange, isn’t it?
So I will probably revert these accounts back to the again working YAHOO server type method.
Best Regards
Jo
many thanks for your information and support.
I have to report a quite astonishing development after installing the updated software is advised.
I did that on Saturday and immediately afterwards all accounts worked, not only the ones which were converted to IMAP and OAuth2, but also the other ones, which were still using the YAHOO server type method.
Then it was good, that I did wait with the feedback to you until today, since starting this morning, the accounts using the YAHOO server type method were still working, but not longer the ones which I already had converted to IMAP and OAuth2.
For these I got the following error messages:
--- Version ---
OS: Windows 7 (x64)
POP Peeper: 4.4.2.0
Webmail: 4.4.6.0
SSL: 1.0.2.11
IMAP: 4.4.2.0
SendMail: 4.4.2.0
--- Error ---
YYYYY [1000: IMAP] ['imap.mail.yahoo.com' (993) SSL: 1] [Smtp: 'smtp.mail.yahoo.com' (465) SSL: 1] [Consec: 2]
- Bad Connection
YYYYY [1000: IMAP] ['imap.mail.yahoo.com' (993) SSL: 1] [Smtp: 'smtp.mail.yahoo.com' (465) SSL: 1] [Consec: 2]
- Bad Connection
Strange, isn’t it?
So I will probably revert these accounts back to the again working YAHOO server type method.
Best Regards
Jo
Re: Can no longer login to Yahoo mail
Hi joewal72,
I have found that my Yahoo account using Webmail ("Yahoo" Server type) is now working after over 48 hours of getting the "Login Error: Check your Login Name and Password" Error so it would appear that Webmail is currently working again for Yahoo in my case and in your case as well. I would add that just as you have reported, others are reporting errors for Yahoo accounts using "IMAP" this morning (although I am not getting any errors myself for Yahoo accounts using IMAP however).
So based on the current situation with Yahoo as far as random errors occurring in some cases using "IMAP", you might as well change your IMAP accounts back to the "Yahoo" Server type.
Yes, it is strange to say the least.
I'm inclined to think that Yahoo has been making changes to their own protocol (Webmail) lately and messed things up for awhile doing so and have apparently finally got it right again. 
I have found that my Yahoo account using Webmail ("Yahoo" Server type) is now working after over 48 hours of getting the "Login Error: Check your Login Name and Password" Error so it would appear that Webmail is currently working again for Yahoo in my case and in your case as well. I would add that just as you have reported, others are reporting errors for Yahoo accounts using "IMAP" this morning (although I am not getting any errors myself for Yahoo accounts using IMAP however).
So based on the current situation with Yahoo as far as random errors occurring in some cases using "IMAP", you might as well change your IMAP accounts back to the "Yahoo" Server type.
Yes, it is strange to say the least.


Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers
Re: Can no longer login to Yahoo mail
My test Yahoo accounts also passed this morning, for the first time in a while. I was so surprised that I re-tested them to make sure it wasn't a fluke, and I tested them again just now -- still passed successfully
I'm very biased toward IMAP, so I would still recommend using IMAP over the "Yahoo" webmail protocol. The "bad connection" may very likely have been a temporary issue on Yahoo's end, as it means that a connection couldn't be made to the server. Your settings are correct so there's nothing else that can be done.

I'm very biased toward IMAP, so I would still recommend using IMAP over the "Yahoo" webmail protocol. The "bad connection" may very likely have been a temporary issue on Yahoo's end, as it means that a connection couldn't be made to the server. Your settings are correct so there's nothing else that can be done.