Closed
Bug 646863
Opened 14 years ago
Closed 14 years ago
Getting the "Negative Vibes" error message from all Yahoo! accounts when trying to download messages.
Categories
(Thunderbird :: Security, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: chocovore, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.2.16) Gecko/20110319 Firefox/3.6.16 GTB7.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT5.1;en-GB;rv:1.9.2.15)Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
Message seen when trying to download mail from any Yahoo! account: "Sending of password did not succeed. Mail server localhost responded: negative vibes from *@yahoo.com"
Corresponding message in Error Console: "login.yahoo.com : server does not support RFC 5746, see CVE-2009-3555"
I began receiving this error message this morning and from what I found on Google, I am not the only one in this situation. I can connect to my Yahoo! accounts directly via the website.
Reproducible: Always
Steps to Reproduce:
1.File
2.Get new messages for...
Actual Results:
"Sending of password did not succeed. Mail server localhost responded: negative vibes from *@yahoo.com"
Expected Results:
Download new messages.
Theme used: Nuvola 1.9.4. The problem happens whatever I do, no matter the theme used. I also tried to disable all the add-ons I use, with the exception of course of WebMail 1.3.11 and WebMail Yahoo 1.4.7.
If I understand correctly, this is a security issue that should be fixed rapidly. However, it happens on a regular basis.
Comment 1•14 years ago
|
||
This error message is not generated by Thunderbird itself - the localhost server is likely to be set up by the webmail extension, and the "negative vibes" is either generated by that localhost server (i.e. the webmail extensions) or by yahoo webmail.
Either way this doesn't look like a Thunderbird issue. I would suggest contacting Yahoo or the WebMail add-on authors.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•