From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Dovecot and capabilities
Date: Tue, 29 Mar 2011 22:27:03 +0200 [thread overview]
Message-ID: <m3bp0twu3s.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <tntmxkd8ymy.fsf@waterbuck.yellow.cert.org>
Michael Welsh Duggan <mwd@cert.org> writes:
> 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.
If there are other servers out there that don't return the changed
capabilities after LOGIN, then I'm sure somebody will notice and send a
bug report.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2011-03-29 20:27 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
2011-03-29 20:27 ` Lars Magne Ingebrigtsen [this message]
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=m3bp0twu3s.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).