Not yet 30 days in the repository, however, since SSLv3 support has been dropped for good reason by various major email providers during the past weeks/months, all previous versions in portage are virtually rendered useless. Hence, I would already like to start the stabilization process. Complete list would be: =dev-libs/libdbusmenu-12.10.2 =dev-libs/libindicate-12.10.1 =mail-client/claws-mail-3.11.1 Reproducible: Always
I would like to add that I am running these on an otherwise stable amd64 environment without any issues; previously in my local overlay since the moment claws-mail-3.11.1 was released.
Why would it be useless? What 3.11.1 does is change the defaults to prefer TLS, which still works fine with all those e-mail providers.
SSL handshake fails when using <mail-client/claws-mail-3.11 and attempting to connect to email providers that have disabled SSLv3 due to POODLE vulnerability. I ran into this issue with both gmx.net and t-online.de. There is also a workaround [1] available, however, it is probably more convenient for most users to simply upgrade to the latest version. [1] http://lists.claws-mail.org/pipermail/users/2014-October/011046.html
Another option is to backport 2 patches mentioned in bug 525588 [1] to claws-mail-3.10.1 and stabilize that version instead. https://bugs.gentoo.org/show_bug.cgi?id=525588#c1
(In reply to Alexander Tsoy from comment #4) First patch fixes problem with direct SSL/TLS mentioned by Christian. Current stable claws-mail support TLS 1.0-1.2 out of the box only when using STARTTLS. Second patch disables SSLv3.
*** This bug has been marked as a duplicate of bug 525588 ***