UPDATE 20170322 13:33: I don’t recommend the use of Adium any longer. See https://twitter.com/JoeBeOne/status/844304343864107009 and an RCE in Adium as a result of code in libpurple. http://seclists.org/fulldisclosure/2017/Mar/57
DO NOT USE.
So for a while now there has been a bug in the SIPE plugin for Adium on the Mac that prevented Adium from connecting to MS Lync servers. Bug is documented at http://sourceforge.net/p/sipe/wiki/Frequently%20Asked%20Questions/#after-upgrading-to-nss-3131-or-newerwzxhzdk12wzxhzdk16insert-your-favorite-linux-distribution-herewzxhzdk17-xxxwzxhzdk13windows-pidgin-2107wzxhzdk14mac-os-x-109wzxhzdk15-login-fails-with-read-error
There is now a feasible workaround to the issue. Follow these steps:
- Go get Adium 1.5.10 from the nightly builds page http://nightly.adium.im/?repo_branch=adium-adium-1.5.10
- Download the SIPEAdiumPlugin 3 (1.18.0) from http://sourceforge.net/projects/sipe/files/
- Install Adium 1.5.10
- Install the SIPE plugin
- Configure the Lync/OCS config in Adium to “Disable BEAST mitigations” in the ‘Options’ tab for the Lync account config in Adium.
Yes its a work around. Yes it may possibly be a bad thing to reduce your security stance. No warranties given.