From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Various nnimap problems
Date: Wed, 22 Sep 2010 20:45:21 +0200 [thread overview]
Message-ID: <m38w2t4ny6.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87ocbpn019.fsf@maru.md5i.com>
Michael Welsh Duggan <md5i@md5i.com> writes:
> Yes. As part of a SELECT, the response should include an OK
> [PERMANENTFLAGS (<list-of-flags>)] clause. (Section 6.3.1 of RFC 3501
> mandates this response.)
>
> OK [PERMANENTFLAGS (<list of flags>)]
> A list of message flags that the client can change
> permanently. If this is missing, the client should
> assume that all flags can be changed permanently.
I've started implementing this, but then I discovered that EXAMINE
always returns
* OK [PERMANENTFLAGS ()]
on all the mail boxes.
*sigh*
So to inhibit the copying of marks from the server to Gnus on read-only
groups, nnimap has to maintain a cache so that it knows which groups not
do fiddle with.
Geez.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-09-22 18:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 15:40 Michael Welsh Duggan
2010-09-22 15:57 ` Michael Welsh Duggan
2010-09-22 16:39 ` Julien Danjou
2010-09-22 17:09 ` Julien Danjou
2010-09-22 17:16 ` Lars Magne Ingebrigtsen
2010-09-22 17:23 ` Lars Magne Ingebrigtsen
2010-09-22 17:13 ` Lars Magne Ingebrigtsen
2010-09-22 17:46 ` Michael Welsh Duggan
2010-09-22 18:45 ` Lars Magne Ingebrigtsen [this message]
2010-09-22 18:31 ` Michael Welsh Duggan
2010-09-22 18:36 ` Lars Magne Ingebrigtsen
2010-09-22 21:06 ` Michael Welsh Duggan
2010-09-22 21:33 ` Lars Magne Ingebrigtsen
2010-09-22 22:49 ` Michael Welsh Duggan
2010-09-22 22:53 ` Michael Welsh Duggan
2010-09-26 18:25 ` Michael Welsh Duggan
2010-09-26 18:57 ` Lars Magne Ingebrigtsen
2010-09-22 17:58 ` Lars Magne Ingebrigtsen
2010-09-24 15:06 ` Michael Welsh Duggan
2010-09-24 16:04 ` 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=m38w2t4ny6.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).