From: lee <lee@yagibdah.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] broken seamonkey :(
Date: Thu, 03 Sep 2015 21:53:39 +0200 [thread overview]
Message-ID: <87oahjmg8s.fsf@heimdali.yagibdah.de> (raw)
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.
next reply other threads:[~2015-09-03 19:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 19:53 lee [this message]
2015-09-03 20:10 ` [gentoo-user] broken seamonkey :( Fernando Rodriguez
2015-09-03 23:39 ` lee
2015-09-04 0:08 ` Fernando Rodriguez
2015-09-04 1:23 ` Dale
2015-09-04 7:54 ` Peter Weilbacher
2015-09-04 10:43 ` Mick
2015-09-04 19:50 ` lee
2015-09-04 20:25 ` Fernando Rodriguez
2015-09-04 23:05 ` lee
2015-09-05 0:43 ` Fernando Rodriguez
2015-09-05 12:06 ` lee
2015-09-05 1:08 ` Fernando Rodriguez
2015-09-05 10:14 ` Mick
2015-09-05 16:22 ` lee
2015-09-05 17:16 ` Mick
2015-09-06 14:29 ` lee
2015-09-06 18:35 ` Mick
2015-09-12 11:54 ` lee
2015-09-06 19:17 ` Fernando Rodriguez
2015-09-13 14:23 ` lee
2015-09-05 13:06 ` lee
2015-09-05 17:09 ` Mick
2015-09-05 21:40 ` Fernando Rodriguez
2015-09-05 22:24 ` Mick
2015-09-06 13:18 ` lee
2015-09-06 13:03 ` lee
2015-09-06 18:44 ` Fernando Rodriguez
2015-09-06 2:45 ` lee
2015-09-06 18:12 ` Mick
2015-09-12 11:20 ` lee
2015-09-12 11:23 ` [gentoo-user] SOLVED: " lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oahjmg8s.fsf@heimdali.yagibdah.de \
--to=lee@yagibdah.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox