Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@pdc.kth.se>
Cc: ding@gnus.org
Subject: Re: .authinfo and mail sources
Date: 04 Mar 2000 20:13:41 +0100	[thread overview]
Message-ID: <iluog8uwntm.fsf@badis.pdc.kth.se> (raw)
In-Reply-To: John Prevost's message of "03 Mar 2000 13:13:38 -0500"

John Prevost <prevost@maya.com> writes:

> Hmm.  Well, nnimap already uses the authinfo file just fine.

Yes, but that's not a very nice thing of nnimap. .authinfo is nntp.

> The thing that confuses me is that the mail-source code for imap
> doesn't even try to use the password in this file.

Lars?

> 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.

I don't think so, no, then you couldn't have multiple IMAP services on
one single IP (which I know some people have, hence the extra cludge
for supporting that in nnimap). What's wrong with 'port'?

If mail-sources had a name, the cludge nnimap uses (put the virtual
server name as the `machine' field in .authinfo) would work, but they
don't so `port' or something similar is probably necessery. Or
preferably, using another standardized file format altogheter.



  reply	other threads:[~2000-03-04 19: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
2000-03-04 19:13     ` Simon Josefsson [this message]
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=iluog8uwntm.fsf@badis.pdc.kth.se \
    --to=jas@pdc.kth.se \
    --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).