Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: mail-source.el patch to use netrc-parse
Date: Sat, 16 Feb 2008 23:21:25 +0100	[thread overview]
Message-ID: <v93arsk0ey.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <86ejbrrvg3.fsf@lifelogs.com>

On Tue, Feb 05 2008, Ted Zlatanov wrote:

> The attached patch

Please use unified (or context) diffs.

> modifies mail-source.el to use a netrc (~/.authinfo) file for IMAP
> fetching.  It will be triggered when mail-source-authinfo-file is
> not nil.  It will override the :user and
> :password parameters set in mail-sources unconditionally.

Is it good to override it?  Wouldn't it be more natural if
`mail-source-authinfo-file' is used if no user/password is given in
`mail-sources'?

> This allows users to store their passwords for an IMAP mail source
> in the authinfo file, encrypted if necessary.  

I think this is useful.

> I use this for my IMAP fetching and it worked fine; please test
> (also if you don't use the feature, make sure your IMAP fetching
> works OK).  I won't commit until I get confirmations it works, since
> mail fetching is a sensitive area for improvements.
>
> I plan to add this to POP and webmail fetching as well, possibly through
> mail-source-bind instead of in each individual fetching function.
> Please let me know what you think.

I'm not sure if I understand what you have in mind.

> Also, I think instead of the current variables
>
> (setq
>  nnimap-authinfo-file "~/.authinfo.enc"
>  nntp-authinfo-file "~/.authinfo.enc"
>  mail-source-authinfo-file "~/.authinfo.enc"
>  smtpmail-auth-credentials "~/.authinfo.enc")
>
> Gnus should have a single specification:

`smtpmail.el', (pop3.el) and `mail-source.el' are not Gnus specific.
So it should be a general Emacs facility.  So please include
emacs-devel in further discussions.  As all ~/.authinfo parsing is
done via `netrc.el', it might make sense to define it therein?

> (setq
>  authinfo-files '(('nnimap "~/.imap-authinfo.enc")
>                   (t "~/.authinfo.enc")))

Maybe a simple value "~/.authinfo" should be equivalent
to '((t "~/.authinfo")).

> Then we can derive each of those variables at runtime, if they are not
> set:
>
> (setq nnimap-authinfo-file
>  (or nnimap-authinfo-file (gnus-get-authinfo-file 'nnimap)))
>
> WDYT?

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2008-02-16 22:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 20:37 Ted Zlatanov
2008-02-16 22:21 ` Reiner Steib [this message]
2008-02-28 15:38   ` Ted Zlatanov
2008-04-25 18:52     ` Ted Zlatanov
2008-02-28 15:38   ` global authinfo mechanism in Emacs, Gnus, Tramp (was: mail-source.el patch to use netrc-parse) Ted Zlatanov
2008-02-28 16:12     ` global authinfo mechanism in Emacs, Gnus, Tramp Tom Tromey
2008-02-28 18:03       ` Ted Zlatanov
2008-02-28 17:48         ` Tom Tromey
2008-03-06 22:36     ` Ted Zlatanov

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=v93arsk0ey.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).