From: Ted Stern <stern+gnus@cray.com>
Subject: semi-undocumented "feature" of nnimap-authinfo-file
Date: Mon, 25 Aug 2003 14:15:27 -0700 [thread overview]
Message-ID: <yccsmnpcuc0.fsf@orff.wc.cray.com> (raw)
I use nnimap via gnus-secondary-select-methods. For one particular server, I
specify nnimap-stream to be ssl, but otherwise I use the nnimap defaults.
I find that the only way my entries in the ~/.authinfo file containing the
login and password are seen during imap login is if I enter the machine name
this way:
machine some.place.net login mylogin password mypassword port imap
^^^^^^^^^
non-obvious!!!!
This took a lot of delving around and experimenting with the low-level
functions that read the authinfo file. And I don't know what would have
happened if I had specified a non-standard ssl port.
Knowing after the fact what I was supposed to look for, I find that the NNTP
info entry for `nntp-authinfo-function' does mention the extra "port" token
(with zero examples):
`port' is used to indicate what port on the server the credentials
apply to and `force' is explained below.
But the IMAP node documentation for `nnimap-authinfo-file' that refers to the
NNTP page doesn't mention what the port token should be set to. Seems pretty
vague to me, especially when ~/.authinfo could be used by more than one
protocol.
Maybe somebody could amend the docs a little bit to help other clueless imap
users such as myself? ;-)
Ted
--
Ted Stern Applications Group
Cray Inc. office: 206-701-2182
411 First Avenue South, Suite 600 cell: 206-383-1049
Seattle, WA 98104-2860 FAX: 206-701-2500
Frango ut patefaciam -- I break that I may reveal
(The Paleontological Society motto, equally apropos for debugging)
next reply other threads:[~2003-08-25 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 21:15 Ted Stern [this message]
2003-08-27 18:02 ` Ted Stern
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=yccsmnpcuc0.fsf@orff.wc.cray.com \
--to=stern+gnus@cray.com \
/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).