From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 8B5EC1399CE for ; Thu, 3 Sep 2015 19:53:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2335B14318; Thu, 3 Sep 2015 19:53:47 +0000 (UTC) Received: from acheron.yagibdah.de (acheron.yagibdah.de [185.55.75.245]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0856E142AD for ; Thu, 3 Sep 2015 19:53:45 +0000 (UTC) Received: from br-dmz-ip.yagibdah.de ([192.168.1.1] helo=heimdali.yagibdah.de) by acheron.yagibdah.de with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.85) (envelope-from ) id 1ZXaZq-0002bU-Fs for gentoo-user@lists.gentoo.org; Thu, 03 Sep 2015 21:53:42 +0200 Received: from lee by heimdali.yagibdah.de with local (Exim 4.84) (envelope-from ) id 1ZXaZq-0008QL-Dh for gentoo-user@lists.gentoo.org; Thu, 03 Sep 2015 21:53:42 +0200 From: lee To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] broken seamonkey :( Date: Thu, 03 Sep 2015 21:53:39 +0200 Organization: my virtual residence Message-ID: <87oahjmg8s.fsf@heimdali.yagibdah.de> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) Mail-Followup-To: gentoo-user@lists.gentoo.org Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain X-Archives-Salt: c0f61a9d-83d0-428d-81ef-310aa11b99cb X-Archives-Hash: bc45638b2b0c2111482142c0709fb743 Hi, since quite a while, seamonkey and its relatives are completely broken when it comes to use self-signed certificates. They just refuse the connection to the server, blocking you from accessing your email. Is there still no solution for this problem? I'm totally fed up with it by now. At work, I have frozen seamonkey at version 2.31 and thunderbird at some outdated version that still works with the certificates. Googling for a solution doesn't reveal one, either. Now I need seamonkey to access the email, and I can't very well turn it back to an outdated version just for that. BTW, if this won't be fixed, what are the replacements? -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable.