From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Subject: Re: nnimap blindly assumes that imap server can store arbitrary flags
Date: Sun, 01 May 2011 14:38:00 -0400 [thread overview]
Message-ID: <m3liyqgtb3.fsf@jhcloos.com> (raw)
In-Reply-To: <m3zkn69sur.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 01 May 2011 20:30:04 +0200")
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
LMI> Hm... it's not supposed to overwrite those flags unless the IMAP server
LMI> is announcing that it's storing \* flags. Is it announcing that?
Permanent flags are: %Seen %Answered %Deleted %Flagged %Draft
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2011-05-01 18:38 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
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 [this message]
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=m3liyqgtb3.fsf@jhcloos.com \
--to=cloos@jhcloos.com \
--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).