From: Michael Welsh Duggan <mwd@cert.org>
To: ding@gnus.org
Subject: Re: Dovecot and capabilities
Date: Tue, 29 Mar 2011 16:23:01 -0400 [thread overview]
Message-ID: <tntmxkd8ymy.fsf@waterbuck.yellow.cert.org> (raw)
In-Reply-To: <m3ipv14woy.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 29 Mar 2011 20:18:37 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Michael Welsh Duggan <md5i@md5i.com> writes:
>
>> Upon login on Dovecot, an updated set of capabilities may be
>> advertised. I was able to account for that using the included patch.
>
> Thanks; applied.
>
>> A perhaps-better method might be to re-run CAPABILITY after logging
>> in.
>
> I don't see why -- if the LOGIN responds with a CAPABILITY list, then we
> should use it. If not, then the capabilities probably haven't changed.
>
> Not issuing another CAPABILITY saves one round trip. :-)
Only because I don't see any way to guarantee that a server will return
a capability list in response to LOGIN, whereas we know it will return
one in response to CAPABILITY. My solution will work in Dovecot 2, but
I don't know if it will work anywhere else. Now, we could certainly use
the capability response if it is there, and re-request capabilities if
it is not.
Either way, my problem is solved with this patch, so it is up to you.
--
Michael Welsh Duggan
(mwd@cert.org)
next prev parent reply other threads:[~2011-03-29 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 1:15 Michael Welsh Duggan
2011-03-24 15:14 ` Ted Zlatanov
2011-03-29 18:18 ` Lars Magne Ingebrigtsen
2011-03-29 20:23 ` Michael Welsh Duggan [this message]
2011-03-29 20:27 ` 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=tntmxkd8ymy.fsf@waterbuck.yellow.cert.org \
--to=mwd@cert.org \
--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).