X-notifier not checking Yahoo emails for several days. Clicking email account brings up Yahoo logon screen
X-notifier has stopped checking my Yahoo email accounts. This has been happening for about a week since about June 20th. It seemed to correlate with the approximate time of the last Firefox update.
X-notifier is not showing when an email is received or count the number of emails. When I click any of my individual email accounts, it takes me to the main Yahoo logon page for that account.
When I try to logon manually with the user name and password, I get this message:
"The browser you're using refuses to sign in. (cookies rejected)"
This is getting very frustrating because I have to use Google Chrome to check my emails. X-notifier is working properly on Google Chrome.
There are also others complaining of this same problem on the X-notifier forum. Whoever is responsible for this malfunction, please fix it !
すべての返信 (3)
Not really a Firefox support issue. X-notifier support is here - http://xnotifier.tobwithu.com/dp/forum
If that is a Bug in Firefox, you can report it here: https://bugzilla.mozilla.org/
この投稿は the-edmeister により に変更されました
I know of the X-notifier support forum. I made reference to it in my post.
I have also posted the problem there (as have others) experiencing the same symptoms only recently as I have.
It is either related to something with the latest Firefox updates or something that caused X-notifier not to be compatible with recent Firefox updates because prior to the most recent updates, everything had been working perfectly.
There was also a very recent X-notifier update which it asked me to install and I did as I had before with no problems.
All I know is that nothing I did has caused this email checking problem.
Whether or not a Firefox update created a problem with that extension, it is up to the developer of that extension to fix it. I mentioned that forum because that's where you're gonna find the largest number of users of that extension.
Personally, I quit using that type of "notifier" extension about 8 years ago because it quit working all too often and the developer was too slow in fixing his product.