Re: new (?) version of the old nnml problem

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Emanuel Berg <moasen@zoho.com> writes:

> Eric Abrahamsen wrote:
>
>> the two programs are roughly equivalent: they
>> handle creating and checking TLS
>> certificates, and creating and handling
>> TLS-encrypted connections to remote servers.
>
> OK, then how do I specify openssl should be
> used instead? Worth a shot... A search with
> `apropos-value' and "gnutls" reveals

apropos-value is nice! I don't think I've ever used that.

>     starttls-gnutls-program
>        "gnutls-cli"
>
>     tls-program
>        ("gnutls-cli --insecure -p %p %h" "gnutls-cli
>        --insecure -p %p %h --protocols ssl3" "openssl
>        s_client -connect %h:%p -no_ssl2 -ign_eof")

Maybe change this variable so that only the "openssl" string is in
there?

[...]

> If you mean ... then:
>
>     $ gnutls-cli --version
>     gnutls-cli 3.3.8

I meant that if the variable libgnutls-version was non-nil, it probably
meant you were using gnutls. But the variables you found above are more
relevant.

>> You can also try setting gnutls-log-level to
>> 3 or 4 and fetching mail, and see if anything
>> interesting pops up in *Messages*.
>
> This does, over and over again:
>
>     gnutls.c: [3] ASSERT: gnutls_buffers.c:547
>
>     gnutls.c: [3] (Emacs) retry: Resource temporarily unavailable, try again.
>     gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable, try again.
>     gnutls.c: [3] ASSERT: gnutls_buffers.c:1104
>
>> The bad news is that I tried this:
>>
>> gnutls-cli --port 995 pop.zoho.com
>>
>> And it connected just fine. You might try
>> that, and going through with the
>> login procedure.
>
> Login procedure works, the rest seems fine (?).

Here's where I bow out! That's the extent of my meager knowledge. On the
plus side, now you have a real error report to take to emacs.devel :)

Eric