From: "Bjørn Mork" <bjorn@mork.no>
To: ding@gnus.org
Subject: Re: A few basic nnimap problems
Date: Fri, 01 Oct 2010 13:17:24 +0200 [thread overview]
Message-ID: <87wrq2yxff.fsf@nemi.mork.no> (raw)
In-Reply-To: <m3ocbf3q5l.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> openssl s_client is "-starttls imap" (or whatever other protocol you're
> using) -- and THEN IT EATS THE GREETING.
You mean the problem that you end up with just the final
". OK CAPABILITY completed"
and not the actual capability list?
Doesn't matter much, does it? Send a cabability command if you cannot
parse IMAP4rev1 out of the OK CAPABILITY. In fact reading the RFC
3501, sending the CAPABILITY as part of the preauth OK is optional:
<quote rfc3501 7.2.1. CAPABILITY Response>
A server MAY send capabilities automatically, by using the
CAPABILITY response code in the initial PREAUTH or OK responses,
and by sending an updated CAPABILITY response code in the tagged
OK response as part of a successful authentication. It is
unnecessary for a client to send a separate CAPABILITY command if
it recognizes these automatic capabilities.
</quote>
although I haven't yet seen an IMAP4rev1 server not sending it
automatically... But you should handle such servers, and that will also
handle the case where openssl ate your automatic capability.
One question I can't find the RFC answer to right now: Is it possible
for the capabilities to change depending on the logged in user? Maybe
some users are allowed to use server resource intensive commands like
sorting and threading while others are not? The quoted text above
certainly indicates that this may happen. If this is possible, then
you should probable issue another capability command right after
authenticating as well.
Bjørn
next prev parent reply other threads:[~2010-10-01 11:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 17:03 Bjørn Mork
2010-09-30 17:09 ` Lars Magne Ingebrigtsen
2010-09-30 18:04 ` Bjørn Mork
2010-09-30 18:53 ` Lars Magne Ingebrigtsen
2010-09-30 20:08 ` Steinar Bang
2010-09-30 20:57 ` Lars Magne Ingebrigtsen
2010-10-01 11:17 ` Bjørn Mork [this message]
2010-10-01 12:36 ` Daniel Pittman
2010-10-01 17:10 ` Lars Magne Ingebrigtsen
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=87wrq2yxff.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--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).