Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Richard Riley <rileyrgdev@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: Gnus and pgp
Date: Thu, 14 Jan 2010 01:19:38 +0100	[thread overview]
Message-ID: <hilnuq$s1e$1@ger.gmane.org> (raw)
In-Reply-To: <87k4vlvg15.fsf@lifelogs.com>

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Wed, 06 Jan 2010 01:42:48 +0100 Richard Riley <rileyrgdev@gmail.com> wrote: 
>
> RR> Ted Zlatanov <tzz@lifelogs.com> writes:
>>> Let's debug it.  Run the following in a clean (emacs -q) instance:
>>> 
>>> (require 'epa-file)
>>> (require 'auth-source)
>>> (require 'cl)
>>> (epa-file-enable)
>>> (setq auth-source-debug t ; use `message' to log messages
>>> epa-file-cache-passphrase-for-symmetric-encryption t
>>> auth-sources '((:source "~/.authinfo.gpg" :host t :protocol t)))
>>> (auth-source-user-or-password "login" "richardriley.net" "imap")
>>> 
>>> What does the last call return (should be your login name)?  What's in
>>> *Messages*?
>
> RR> It returns my login name ok. 
>
> RR> *Messages* just has
>
> RR> auth-source-user-or-password: found (login)=(shamrock) for richardriley.net (imap)
> RR> "shamrock"
>
> RR> I also got prompted for a symmetric password to unlock the authinfo.gpg
>
> RR> Note that my login name for the remote host is, in this case, the same
> RR> as my local login id.
>
> If this works, it should work for all other IMAP cases as well.  Look at
> nnimap.el, it has the same call in nnimap-open-connection.  Can you try
> the auth-source-user-or-password call inside your regular sessions
> (instead of `emacs -q'), where auth-source.el doesn't work for you?  Is
> there something you see that might hint what the problem is?
>
> Ted

The issue was with nntp selects not other IMAPS as  recall.

-- 
Google Talk : rileyrgdev@googlemail.com  http://www.google.com/talk

  reply	other threads:[~2010-01-14  0:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.11779.1259519753.2239.info-gnus-english@gnu.org>
2009-12-01 20:28 ` Ted Zlatanov
2009-12-02 19:08   ` Richard Riley
2009-12-02 19:20   ` Richard Riley
     [not found]   ` <mailman.12043.1259780939.2239.info-gnus-english@gnu.org>
2009-12-02 21:41     ` Ted Zlatanov
2009-12-03  0:54       ` Richard Riley
     [not found]       ` <mailman.12065.1259801678.2239.info-gnus-english@gnu.org>
2009-12-03 18:02         ` Ted Zlatanov
2009-12-03 19:11           ` Richard Riley
2009-12-07 18:54       ` Richard Riley
2009-12-22 18:08       ` Richard Riley
     [not found]       ` <mailman.2.1261505407.18930.info-gnus-english@gnu.org>
2010-01-05 19:28         ` Ted Zlatanov
2010-01-06  0:42           ` Richard Riley
     [not found]           ` <mailman.814.1263114758.18930.info-gnus-english@gnu.org>
2010-01-13 21:41             ` Ted Zlatanov
2010-01-14  0:19               ` Richard Riley [this message]
     [not found]               ` <mailman.1372.1263428412.18930.info-gnus-english@gnu.org>
2010-01-14 14:22                 ` Ted Zlatanov
2010-01-14 15:36                   ` Richard Riley
     [not found]                   ` <mailman.1413.1263483604.18930.info-gnus-english@gnu.org>
2010-01-15 18:37                     ` Ted Zlatanov
2009-11-29 18:35 Richard Riley

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='hilnuq$s1e$1@ger.gmane.org' \
    --to=rileyrgdev@gmail.com \
    --cc=info-gnus-english@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.
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).