From: Simon Josefsson <jas@extundo.com>
Subject: Re: imaps, and .authinfo port name/number?
Date: Fri, 13 Aug 2004 08:35:15 +0200 [thread overview]
Message-ID: <iluekmb1r6k.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87u0v8jg38.fsf@dod.no>
Steinar Bang <sb@dod.no> writes:
> What port name, or number should I use in the .authinfo file, for an
> imaps server?
>
> I have the following in gnus-secondary-select-methods:
> (nnimap "somemachine"
> (nnimap-address "somemachine.somecompany.com")
> (nnimap-stream ssl))
>
> I have tried
> machine somemachine.somecompany.com login sb password secret port 993
> and I have tried
> machine somemachine.somecompany.com login sb password secret port imaps
"port imap"?
next prev parent reply other threads:[~2004-08-13 6:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 19:45 Steinar Bang
2004-08-13 6:35 ` Simon Josefsson [this message]
2004-08-13 16:33 ` Steinar Bang
2004-08-13 21:09 ` Simon Josefsson
2004-08-14 20:12 ` Steinar Bang
2004-08-14 22:39 ` Simon Josefsson
2004-08-16 17:43 ` Ted Zlatanov
2004-08-16 21:36 ` Simon Josefsson
2004-08-17 14:05 ` 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=iluekmb1r6k.fsf@latte.josefsson.org \
--to=jas@extundo.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).