PP Not Working With Yahoo Mail?

[mjs]

Thanks for the information.

Have you tried logging into the Yahoo account on-line (using the web)?

If not try doing so to see if you're able to login successfully using the Internet - and let us know what you get trying this.

Whoa, just noticed your POP Peeper "About" screen-shot with all of the "CRC FAIL" results displayed (they should all have a "pass" status).

Did you try an update of POP Peeper using the link provided in this "Announcements" post? -- and if so was it a "successful" update?

[NPeeper]

I tried Oauth2 yesterday but every time I log in they test if I'm not a robot and have to select images, then when they approve it, have to enter the password. (Nuts!) (Now you understand why I didn't have a Yahoo account earlier.) And after all this, I get the message OAuth was not successful.

"As of September 16, 2024, Outlook/Hotmail accounts will require you to use Oauth2". If this is the case, I have no use of Yahoo being on PopPeeper because it wouldn't automatically notify me of incoming emails, just like it's useless for Gmail.

Can you suggest a free email service that works nicely with PopPeeper?

How can I fix all of the "CRC FAIL" results?

[mjs]

All the Email Service providers you've mentioned (i.e. Yahoo, Gmail, Outlook/Hotmail) all work in POP Peeper (I have many accounts using each of these Email Service providers in POP Peeper among others as well that all work fine).

Based on your initial post:

We just opened a Yahoo account and wanted to add it to our Pop Peeper accounts....

In as much as you're adding the "Yahoo account" to your other "Pop Peeper accounts" - It sounds like you are currently using POP Peeper with other Email Service providers than just the one Yahoo account (i.e., presumably at least Outlook/Hotmail, that you've mentioned).

How many other accounts (than the one problematic Yahoo account) are you using in POP Peeper and what are these Service providers?

And presumably these other accounts all work in POP Peeper (since your issue is reportedly just this one Yahoo account)?

Did you try doing a POP Peeper update using the link I posted previously?

As far as what we consider the best "protocol" to use (that is specifically between POP3/IMAP) - we recommend IMAP (if you have no reason to do otherwise) due to advantages in doing so. So if you add or edit an account in POP Peeper, it's usually best to let POP Peeper use what it sets-up "automatically" (that is, when adding new accounts to POP Peeper).

Have you tried deleting this Yahoo account and adding it once again, allowing POP Peeper to use the settings it uses automatically?

Oh, and one last question, what is the "Security" software that you use on your computer?

[Jeff]

The "[SYS/TEMP] Server error" that you're getting is very likely due to not using Oauth2. The post you referred to was specific to Outlook (not Yahoo), but in fact, Yahoo has required Oauth2 for quite some time.

I tested Oauth2 on Win7 -- I had some issues but I did get it to work. I *think* I know the magic formula that made it work, as I'm able to duplicate the error and success by changing this back & forth, but full disclosure -- the first time I did it, it didn't work, though I suspect that there were other factors (just my way of saying, I'm pretty sure this will work, but not with 100% confidence, just 95%):

In the Windows start menu, type and open:
Internet Options
Select the "Advanced" tab
Scroll the list to the very bottom and enable:
- TLS 1.2
Press OK

Now try re-doing Oauth2 in your Yahoo account. If it doesn't work, try exiting and restarting POP Peeper. If it still doesn't work, fear not ranger, there is another alternative which we can proceed with.


As for the CRC failures, this is also a byproduct of using an unsupported OS. It's because Windows 7 doesn't have the root certificates for ssl.com that POP Peeper uses for the digital signature. While this can probably be ignored safely, if you're interested in fixing it (and I can confirm what needs to be done to provide the solution for anyone else using Win7/8) -- please email me (support at esumsoft dot com).

[NPeeper]

Sorry for not getting back to you sooner—I needed some time to work on it. Guess what? I figured it out! The problem was that Chrome wasn’t set as my default program for Oauth2 to receive its initial authorization. Now it’s working perfectly. Thank you very much!

I don’t have Outlook or Hotmail; instead, I use emails from our personal Internet Service Providers, which work well with Pop Peeper. I was looking for emails from a public email service provider, so we rely on our Gmail and Yahoo accounts.

How can I get Gmail to work with Pop Peeper? It used to sign in automatically, but now it doesn’t. They’re asking for extra security measures to sign in, and entering new phone codes every time isn’t practical—especially since I’m working on a desktop.

[NPeeper]

And it was important to check off TLS 1.2 in the Internet Options.

[Jeff]

Glad you got Yahoo to work. Chrome isn't necessarily required (I use Firefox), but the webbrowser that you were trying before could be a problem. Would you mind letting me know what browser that was?

As for Gmail -- gmail has more stringent requirements for their Oauth2 than the others which is why Win7 won't work "out of the box". Here's an article that explains what you can do:
https://www.esumsoft.com/news/notice-gm ... peeper-v4/
(quick answer: you should create an app password)

[NPeeper]

I used Brave but changed it now because of the Yahoo issue in PP.

"Gmail does require you to enable 2-Factor Authentication to use app passwords." That's the problem which is too bad.
"App passwords can only be used with accounts that have 2-Step Verification turned on." Their 2nd Verification is a phone number but I have lots of trouble from them with that.

[Jeff]

I think I have Brave installed somewhere, I'll test it out sometime. Brave is based on Chromium, but it's possible that it's not compatible (or the Win7 thing).

I don't think 2FA requires a phone number. I'd recommend the authenticator app method if that's a possibility for you.

Otherwise, the last resort is to run POP Peeper with admin privileges -- make sure you exit PP, then right-click on poppeeper.exe and select "Run as administrator". Do Oauth2 as normal for your gmail account(s) and if that's successful, I'd highly recommend exiting POP Peeper and then running it as normal. The main problem with this alternative is that if you ever need to re-oauth2 your accounts again, you'll need to remember to do the same thing.

[NPeeper]

The authenticator app method only works after enabling two-step verification, which requires a phone number. I double-checked this.

I tested Gmail accounts with admin privileges and received successful authentication—so it works! However, even though the accounts are set to start automatically at Windows startup, they don't launch as expected. For testing, I scheduled them to run at one-minute intervals, but they didn't check for new emails after a minute. I had to click on the accounts to view incoming messages. I tested this both with admin privileges and while running normally.

The good news is that I don't need to log in to access my Gmail; I can view them directly from the taskbar. Thank you very much for the program and your assistance!

[Jeff]

The authenticator app method only works after enabling two-step verification, which requires a phone number. I double-checked this.

I don't think that's correct. Here's what I get when I go to enable 2FA on one of my non-2FA'd gmail accounts:

The top part says: "To turn on 2-Step Verification you first need to add a second step to your Google Account, like a phone number"
key phrase: *like* a phone number.

If you press the "authenticator" option on the bottom (one of the available "second steps"), I assume this will be sufficient to enable 2FA. If not, (monopolistic joke retracted because... you know...)

For testing, I scheduled them to run at one-minute intervals, but they didn't check for new emails after a minute. I had to click on the accounts to view incoming messages.

I'm not sure what that means ("click on the accounts to view incoming messages"). By default, "clicking on an account" doesn't do anything, and the only thing you can change it to is "view that account", which isn't the same as checking mail. (although, this is somewhat related to something I plan on replying to your email). So some possibilities:
1) If the account is already connected, you may not even notice that PP is checking for mail when using IDLE -- new messages are pushed to PP
2) Make sure that AutoCheck is enabled (the "ball" on the bottom-right of the main window is green, not red)
3) Make sure that the accounts are enabled (edit the account and refer to "enabled" on the bottom-left of 'General')
4) If you have to view the account to see its messages, then Edit account / Advanced / "hide messages from all accounts" is modified (and see forthcoming email for more context)

[NPeeper]

I had noticed yesterday the words "like a phone number", but when I clicked on it, there wasn't any other option.
So now I got the 2-Step Verification turned on with an Authenticator. Now what? How do I get Gmail to open in Pop Peeper normal without having to run it as administrator?

By mistake I wrote clicking instead of "check mail". Whatever it is, I realized the mistake was because I forgot to enable the accounts. Now they're working beautifully by running with admin privileges.

[Jeff]

Now they're working beautifully

How do I get Gmail to open in Pop Peeper normal without having to run it as administrator?

You shouldn't have to run PP as admin as it is. Running as admin is only necessary when you have to go through the Oauth2 process (via webbrowser). It may not happen today, it may not happen tomorrow, but it will happen and you may forget what you have to do (run as admin). Which is why I recommend using app-passwords instead of Oauth2 in this case.
https://support.google.com/accounts/answer/185833?hl=en

If you do decide to create an app password, you'll need to use that password in your gmail account:
edit the account, change the "oauth2" dropdown back to "password" and paste the app password you get from google from the instructions in the link above

[NPeeper]

Got it working with the app password Thanks again.

Now, why would the app password be better than 1-time running as administrator?
The problem with the app password is having the 2-Step Verification turned on, which means, always having to sign in my Gmail account with a password as well as to authenticate it.

[Jeff]

Because it's not necessarily a one-time thing. Google will eventually force you to re-authenticate Oauth2. Some users/accounts require it more than others.

You only need to do 2FA again if google doesn't recognize the device, it's not every time unless you don't allow it to remember.

[rgordon]

Greetings. This morning I am receiving this error on two PCs trying to connect to Yahoo mail via Oauth2:

2024-08-18 11_27_25-Error Overview.png (4.77 KiB) Viewed 5985 times

This is happening on two different accounts. Advice? I can access the account on my PC via regular Yahoo web-based E-mail using my password. The other PC uses Thunderbird which also connects via Oauth2; when I opened it, it asked for the Yahoo password which I supplied and was able to connect to Yahoo mail but I don't know if it stopped using Oauth2 for this (suspect that it did).

Thanks.

Rob

[Jeff]

If you haven't already, you should click the "reset Oauth2" link and follow the procedure to re-authenticate with Oauth2. This will happen sometimes depending on the provider and certain conditions.

If it still doesn't work, it's likely a temporary issue on Yahoo's end. My Yahoo accounts are currently working.