Re: Gack ... boring old nnimap and gmail problem again

[Harry Putnam <reader@newsguy.com>]

Tassilo Horn <tassilo@member.fsf.org> writes:

> Harry Putnam <reader@newsguy.com> writes:
>
> Hi Harry,
>
>> | Opening TLS connection with `gnutls-cli --insecure -p 993
>> | imap.gmail.com'...done
>
> One difference between me and you, although our gmail/gnus settings are
> identical, is that I use an Emacs with built-in GnuTLS support.  So I
> get these messages.
>
> 20120110T081820.817> Opening nnimap server on Gmail...
> 20120110T081820.817> Opening connection to imap.gmail.com via tls...
> Decrypting /home/horn/.authinfo.gpg...done
> 20120110T081821.744> Opening nnimap server on Gmail...done
>
> You said, that you compile emacs yourself, do you?  If so, don't you
> have gnutls installed or do you pass the --without-gnutls option to
> configure?

I do compile myself. This was my ./configure command:

./configure  --with-xft  --with-x-toolkit=lucid 
    --prefix=/usr/local/src/vcs/bzr/test

It may be confused somewhat by the fact that I also have emacs-23
installed thru debians aptitude.  However the emacs that run when I
say ` emacs ' on command line is the emacs-24 that I compiled.

I do have some things with gnutls in the name installed.  If you know
Debian at all then this might be meaningful to you:

aptitude search gnutls |grep ^i

i   gnutls-bin                      - GNU TLS library - commandline utilities   
i A libcurl3-gnutls                 - easy-to-use client-side URL transfer libra
i   libgnutls-openssl27             - GNU TLS library - OpenSSL wrapper         
i   libgnutls26                     - GNU TLS library - runtime library         
i A libneon27-gnutls                - HTTP and WebDAV client library (GnuTLS ena

-------        ---------       ---=---       ---------      --------

There should be no difference now than when it all worked for me with
gmail, a while back. With the exception of new passwd and possibly
newer versions somewhere.  That is, unless I did something unknowingly
that has effected this stuff.

I did mention that I had received notice from gmail that I needed to
set a new passwd because of unusual activity in my account.  I don't
really know what that was, but it would have been on there end, I
guess.

Of course that new passwd was duly updated in .authinfo.