#Adium yahoo messenger password#

(You can tell because it’s filled in in the password prompt. It will ask for your password, even if you have it saved in the Keychain.If you use Finch, you will get disconnected.If you use Pidgin, you will get disconnected.

If you use the official Yahoo! Messenger, you won’t get disconnected.You’ll get disconnected after about six to eight hours (sometimes more, sometimes less).

Meanwhile, we and the Libpurple developers are still investigating the specific cause of the problem, so we know who needs to fix what. The periodic disconnections are a hassle, but you should still be able to chat. This is not a security risk, as you can’t cut or copy from the password field: This is so that, if the error is spurious (as in this case), you can just hit OK. As shown above, Adium fills in your old password. Our users are reporting that the official Yahoo! Messenger client does not get disconnected, so it seems to be a fault in Libpurple, the library that Pidgin and Adium both use.įurthermore, we stress that Adium has not forgotten your password. It’s not specific to Adium: Pidgin users are reporting the same problems. This is not new in 1.3.1: We released 1.3.1 on September 7th, so it was working fine for nearly two weeks before the problems started. The disconnection comes in the form of an authorization error, so Adium responds by presenting a password prompt: Please try it out and let us know on the Trac ticket whether it solves the problem for you.įour days ago, many of our users started getting disconnected from Yahoo! after several hours. This beta contains a new version of Libpurple that we believe fixes the Yahoo! disconnection problem. I should mention that Adium’s development wiki claims that all beta versions of Adium include an Adium -> Debug Window feature, but this does not seem to be the case with the latest beta version (1.3.5rc1), which does not include such a menu item (unfortunately).You are currently browsing the archives for the Pidgin category. In my case, since my work enviroment includes a reverse proxy, I also (for the first time) had to enable proxy settings for my connection to Yahoo! in order to get it working again.

#Adium yahoo messenger update#

Instead of making this change, Adium users can update to a new beta version (by clicking Adium -> Preferences -> General, and enabling “ Update to beta versions when available“, and then Adium -> Check for updates) that seems to have included a fix to this problem. The problem with this fix is that if and when Yahoo! and your client sync up in the future to fix this problem for good, the IP you’ve entered may not be optimal, so you’ll have to remember to go back at some point and change the Login Server setting back to its original value ( ), which is an alias for many Yahoo! Messenger servers. In Adium, this is done via Adium -> Preferences -> Accounts, clicking your Yahoo! account and then clicking Edit (or double-clicking the account), and changing the value for Login Server, as shown below: The quick fix for this is simple: in your client, change the server to which you connect to a fixed IP address that does not yet use the new connection protocol, such as 66.163.181.189. Yahoo! recently made changes to the connection protocols in their Messenger service, which caused all sorts of problems with many instant messaging clients.