From: John Prevost <prevost@maya.com>
Cc: ding@gnus.org
Subject: Re: .authinfo and mail sources
Date: 03 Mar 2000 13:13:38 -0500 [thread overview]
Message-ID: <87itz3c46l.fsf@isil.localdomain> (raw)
In-Reply-To: Simon Josefsson's message of "03 Mar 2000 14:27:45 +0100"
Simon Josefsson <jas@pdc.kth.se> writes:
> John Prevost <prevost@maya.com> writes:
>
> > Is there any reason mail sources don't seem to use .authinfo, or is
> > this just an oversight?
>
> The .netrc format only support one protocol, the original being ftp
> and it's nntp in .authinfo. So if the same machine ran nntp/pop/imap
> services, there is no obvious way of specifying different passwords.
>
> Perhaps we could further enhance the syntax of netrc files in
> .authinfo, perhaps add a keyword `port' to specify which port we're
> talking about? As one couldn't run multiple services on a single
> port, that might work.
>
> Are there any other standardized password credential file formats
> around?
Hmm. Well, nnimap already uses the authinfo file just fine. (In
fact, the password is the same all around on that machine.) The thing
that confuses me is that the mail-source code for imap doesn't even
try to use the password in this file.
I think we should probably extend .authinfo. Maybe not port, but
protocol (which could allow for "imap" working for either normal or
SSL imap, or imap on a weird port, or ... Or something like that.
That might not be quite right either. Hmm.
John.
next prev parent reply other threads:[~2000-03-03 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-03 8:36 John Prevost
2000-03-03 13:27 ` Simon Josefsson
2000-03-03 18:13 ` John Prevost [this message]
2000-03-04 19:13 ` Simon Josefsson
2000-03-06 15:14 ` David S. Goldberg
2000-04-20 20:24 ` Lars Magne Ingebrigtsen
2000-04-21 5:48 ` Katsumi Yamaoka
2000-03-03 18:32 ` Alan Shutko
2000-03-04 16:35 ` Kai Großjohann
2000-03-06 18:49 ` Toby Speight
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=87itz3c46l.fsf@isil.localdomain \
--to=prevost@maya.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).