From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Making Gnus ask my IMAP username and password after the recent auth-source changes
Date: Thu, 17 Feb 2011 05:03:41 -0600 [thread overview]
Message-ID: <87k4gyj52q.fsf@lifelogs.com> (raw)
In-Reply-To: <874o834g2q.fsf@fastmail.fm>
On Wed, 16 Feb 2011 20:15:09 -0500 Matt Lundin <mdl@imapmail.org> wrote:
ML> From .authinfo:
ML> machine imap.gmail.com login [username] password [password]
ML> And from the *Messages* buffer:
ML> Opening connection to imap.gmail.com via tls...
ML> Opening TLS connection to `imap.gmail.com'...
ML> Opening TLS connection with `gnutls-cli --insecure -p imaps imap.gmail.com'...done
ML> Opening TLS connection to `imap.gmail.com'...done
ML> auth-source-search: found 2 backends matching (:max 1 :host ("gmail" "imap.gmail.com") :port ("143" "993" "imap" "imaps") :create t)
ML> Quit trying to open server nnimap+gmail
ML> Couldn't open nnimap:gmail
ML> Note: I pressed C-g to exit the user/protocol prompt. (Hence the "Quit
ML> trying to open").
Because you didn't go through the prompts, I don't know the actual
backend that was used (see the second message below).
I made a .authinfo.gpg file to test this with this first line:
machine imap.gmail.com login x password y
And then did
(auth-source-search :max 1 :host '("gmail" "imap.gmail.com") :port '("143" "993" "imap" "imaps") :create t)
I see in *Messages*:
auth-source-search: found 1 backends matching (:max 1 :host ("gmail" "imap.gmail.com") :port ("143" "993" "imap" "imaps") :create t)
auth-source-search: found 1 results (max 1/0) in [object auth-source-backend "~/.authinfo.gpg" netrc "~/.authinfo.gpg" t t t auth-source-netrc-create auth-source-netrc-search] matching (:max 1 :host ("gmail" "imap.gmail.com") :port ("143" "993" "imap" "imaps") :create t)
((:host "imap.gmail.com" :user "x" :secret (lambda (&rest --cl-rest--) (apply #[... "\bJ‡" [G19000] 1] ... --cl-rest--))))
So it worked properly for me. Can you make sure you're loading the
right auth-source.el, too? Do `M-x eval-buffer' in the open file rather
than relying on autoload and require.
Ted
next prev parent reply other threads:[~2011-02-17 11:03 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 2:06 Raphael Kubo da Costa
2011-02-15 13:46 ` Ted Zlatanov
2011-02-15 20:57 ` Raphael Kubo da Costa
2011-02-16 19:13 ` Ted Zlatanov
2011-02-16 20:39 ` Matt Lundin
2011-02-16 20:46 ` Ted Zlatanov
2011-02-17 1:15 ` Matt Lundin
2011-02-17 11:03 ` Ted Zlatanov [this message]
2011-02-17 13:49 ` Matt Lundin
2011-02-17 14:20 ` Matt Lundin
2011-02-17 15:22 ` Steinar Bang
2011-02-18 20:21 ` Ted Zlatanov
2011-02-21 19:40 ` Steinar Bang
2011-02-17 3:34 ` Raphael Kubo da Costa
2011-02-17 11:44 ` Ted Zlatanov
2011-02-17 13:34 ` Raphael Kubo da Costa
2011-02-17 14:16 ` Ted Zlatanov
2011-02-17 23:54 ` Lars Ingebrigtsen
2011-02-18 20:19 ` Ted Zlatanov
2011-02-18 23:10 ` Lars Ingebrigtsen
2011-02-22 21:52 ` Ted Zlatanov
2011-02-23 8:52 ` Lars Ingebrigtsen
2011-02-23 14:47 ` Ted Zlatanov
2011-02-23 17:00 ` Raphael Kubo da Costa
2011-02-23 17:09 ` Ted Zlatanov
2011-02-23 17:56 ` Raphael Kubo da Costa
2011-02-23 18:56 ` Ted Zlatanov
2011-02-25 4:42 ` Lars Ingebrigtsen
2011-02-25 11:31 ` Ted Zlatanov
2011-03-05 12:15 ` Lars Magne Ingebrigtsen
2011-03-08 18:26 ` Ted Zlatanov
2011-03-15 16:28 ` Lars Magne Ingebrigtsen
2011-03-15 16:43 ` Ted Zlatanov
2011-02-23 23:35 ` Lars Ingebrigtsen
2011-02-23 23:36 ` Lars Ingebrigtsen
2011-02-24 5:43 ` Ted Zlatanov
2011-02-24 11:35 ` Lars Ingebrigtsen
2011-02-24 13:06 ` Ted Zlatanov
2011-02-24 13:48 ` Raphael Kubo da Costa
2011-02-24 16:42 ` Ted Zlatanov
2011-02-25 4:47 ` Lars Ingebrigtsen
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=87k4gyj52q.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).