From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 14380@debbugs.gnu.org
Subject: bug#14380: 24.3; `network-stream-open-tls' fails in some imap servers on w32
Date: Fri, 10 May 2013 21:44:12 +0100 [thread overview]
Message-ID: <CALDnm52Ly7QDvL0bOShCK-PMd0ecJmbXVQALm3oZWcWHuA3MHg@mail.gmail.com> (raw)
In-Reply-To: <83haiabvq2.fsf@gnu.org>
OK, I see.
Honestly I thought builtin tls was some kind of tls library in elisp.
Needing external libraries doesn't make it very builtin :-), but
that's just my opinion.
In any case, my description shows how it "almost worked" with whatever
tls client it found (it was probably cygwin's, but I didn't check).
You might want to avoid these bug reports by fixing it the way I
suggested or some other way. Or not. All is OK from my part.
Thanks for the support,
João
On Fri, May 10, 2013 at 6:17 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: João Távora <joaotavora@gmail.com>
>> Date: Fri, 10 May 2013 17:00:32 +0100
>> Cc: 14380@debbugs.gnu.org
>>
>> If the builtin tls fixes this and its the "recommended way" it should
>> be the default no?
>
> It _is_ the default, AFAIK, but you need to install the GnuTLS
> libraries (DLLs) for it to work. Try installing this one:
>
> http://sourceforge.net/projects/ezwinports/files/gnutls-3.0.9-w32-bin.zip/download
>
>> btw: how to I configure emacs to use builtin gnutls?
>
> I think you just need to install the above (and restart Emacs, if it's
> already running).
--
João Távora
next prev parent reply other threads:[~2013-05-10 20:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k3mw79iv.fsf@lifelogs.com>
2013-05-18 13:05 ` bug#14380: [gmane.emacs.bugs] bug#14380: 24.3; `network-stream-open-tls' fails in some imap servers on w32 João Távora
2013-05-19 3:17 ` Ted Zlatanov
[not found] ` <87zjvr64lt.fsf_-_@lifelogs.com>
2013-05-19 11:45 ` João Távora
2013-05-19 15:32 ` Eli Zaretskii
2013-05-20 13:56 ` Ted Zlatanov
2013-05-20 16:28 ` Eli Zaretskii
2013-05-24 19:48 ` Ted Zlatanov
2013-05-24 20:27 ` Eli Zaretskii
2013-05-10 12:49 ` João Távora
2013-05-10 14:00 ` Eli Zaretskii
2013-05-10 16:00 ` João Távora
2013-05-10 17:17 ` Eli Zaretskii
2013-05-10 20:44 ` João Távora [this message]
2013-05-11 7:06 ` Eli Zaretskii
2013-05-17 13:12 ` Ted Zlatanov
2013-05-24 22:20 ` Ted Zlatanov
2013-05-25 6:49 ` Eli Zaretskii
[not found] ` <CALDnm50KHS7wOKUpQJQHb4V_PLfQs6VkjEsRmPgY=R5x0eEuUg@mail.gmail.com>
2013-05-19 15:44 ` Eli Zaretskii
2013-05-19 17:57 ` João Távora
2013-05-19 19:01 ` Eli Zaretskii
2013-05-19 23:05 ` Ted Zlatanov
[not found] ` <87txly4ll9.fsf@lifelogs.com>
2013-05-20 2:08 ` Juanma Barranquero
2013-05-20 22:07 ` João Távora
[not found] ` <CALDnm51-4aTee3NGoRp+=T6MuTV3xD9P4Ed1yZLU_E5k_r5hGw@mail.gmail.com>
2013-06-05 15:06 ` Ted Zlatanov
[not found] ` <87obbk1trn.fsf@lifelogs.com>
2013-06-05 16:42 ` Glenn Morris
2013-06-05 18:10 ` Ted Zlatanov
2013-06-08 0:58 ` Glenn Morris
2013-06-06 8:15 ` João Távora
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALDnm52Ly7QDvL0bOShCK-PMd0ecJmbXVQALm3oZWcWHuA3MHg@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=14380@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).