From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Gack ... boring old nnimap and gmail problem again
Date: Wed, 11 Jan 2012 08:41:27 -0500 [thread overview]
Message-ID: <87pqeq9x14.fsf@lifelogs.com> (raw)
In-Reply-To: <87y5te1j4l.fsf@newsguy.com>
On Wed, 11 Jan 2012 08:08:58 -0500 Harry Putnam <reader@newsguy.com> wrote:
HP> from config.log at lines 351[78]
HP> configure:11720: checking for gnutls >= 2.6.6
HP> configure:11740: result: no
You really should try GnuTLS support :) Just install libgnutls-dev as
was suggested.
HP> I really am sorry for being so sloppy and consequently wasting you and
HP> Ted Z's time.
Your question, coupled with Richard Riley's question, made me realize we
needed the `auth-source-user-and-password' function. Something good
came out of it! And of course there's no shame in screwing up, I do it
all the time :)
Ted
next prev parent reply other threads:[~2012-01-11 13:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 19:01 Harry Putnam
2012-01-10 9:35 ` Stefan Nobis
2012-01-10 10:28 ` Tassilo Horn
2012-01-11 3:18 ` Harry Putnam
2012-01-11 3:36 ` Harry Putnam
2012-01-11 7:58 ` Tassilo Horn
2012-01-11 13:08 ` Harry Putnam
2012-01-11 13:41 ` Ted Zlatanov [this message]
2012-01-11 9:13 ` Adam Sjøgren
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=87pqeq9x14.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).