From: Simon Josefsson <simon@josefsson.org>
To: ding@gnus.org
Subject: Re: nnimap blindly assumes that imap server can store arbitrary flags
Date: Sun, 01 May 2011 17:50:26 +0200 [thread overview]
Message-ID: <87fwoyzagt.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3vcxuii8x.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 01 May 2011 16:54:22 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> James Cloos <cloos@jhcloos.com> writes:
>
>> I see this kind of error, lately, when I ?-tick an article:
>>
>> ,----
>> | 238728 UID STORE 4467 +FLAGS.SILENT (gnus-dormant)
>> | 238728 BAD invalid flag list to STORE command
>> `----
>>
>> Gnus needs to store its own flags in .newsrc.eld.
>
> It does store these flags in .newsrc.eld. But I guess sending flags
> that the server don't understand to the server is kinda rude? But does
> it matter?
Gnus should only send it to the server if either gnus-dormant is
mentioned as a PERMANENTFLAGS, or more likely, \* is part of the
server-provided PERMANENTFLAGS. See its documentation:
PERMANENTFLAGS
Followed by a parenthesized list of flags, indicates which of
the known flags the client can change permanently. Any flags
that are in the FLAGS untagged response, but not the
PERMANENTFLAGS list, can not be set permanently. If the client
attempts to STORE a flag that is not in the PERMANENTFLAGS
list, the server will either ignore the change or store the
state change for the remainder of the current session only.
The PERMANENTFLAGS list can also include the special flag \*,
which indicates that it is possible to create new keywords by
attempting to store those flags in the mailbox.
/Simon
next prev parent reply other threads:[~2011-05-01 15:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 19:47 James Cloos
2011-05-01 14:54 ` Lars Magne Ingebrigtsen
2011-05-01 15:50 ` Simon Josefsson [this message]
2011-05-01 15:56 ` Lars Magne Ingebrigtsen
2011-05-01 18:24 ` James Cloos
2011-05-01 18:30 ` Lars Magne Ingebrigtsen
2011-05-01 18:38 ` James Cloos
2011-05-30 21:11 ` Lars Magne Ingebrigtsen
2011-05-01 18:35 ` James Cloos
2011-05-30 21:02 ` Lars Magne Ingebrigtsen
2011-05-31 4:52 ` James Cloos
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=87fwoyzagt.fsf@latte.josefsson.org \
--to=simon@josefsson.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).