From: Tim Landscheidt <tim@tim-landscheidt.de>
To: ding@gnus.org
Subject: Re: ssl problems
Date: Wed, 07 Jul 2010 19:15:03 +0000 [thread overview]
Message-ID: <m31vbfhzns.fsf@passepartout.tim-landscheidt.de> (raw)
In-Reply-To: <35988.3149889812$1278528824@news.gmane.org>
Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> [...]
>> Unfortunately, the whole SSL shebang with separate pro-
>> cesses, not to speak of two different clients, seems to be
>> *very* fragile. It would be *really* nice if it could be
>> included properly in Emacs.
> I've considered several times just using external tools for the whole
> mail-fetching process altogether, though that might no longer be worth
> it if things develop as indicated in Ted's link…
Well, there are lots of other timeouts that can make Gnus
fail or hold up Emacs :-). In the end, I personally avoid
using external tools because they add another level of com-
plexity, and I don't find the thought of losing mail very
comforting :-).
Tim
prev parent reply other threads:[~2010-07-07 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 17:38 Eric Abrahamsen
2010-07-07 18:28 ` Tim Landscheidt
2010-07-07 18:33 ` Ted Zlatanov
2010-07-07 18:53 ` Eric Abrahamsen
2010-07-07 19:15 ` Tim Landscheidt [this message]
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=m31vbfhzns.fsf@passepartout.tim-landscheidt.de \
--to=tim@tim-landscheidt.de \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).