I believe I was misinterpreting the intent of the PERMANENTFLAGS response.
After receiving Larry's replies I now feel this response is largely
irrelevant to our wireless client because of its mode of operation (i.e.
SnapperMail queries message flags from the server at the start of each
session).
Stuart,
The SELECT response that you quote strikes me as unusual, perhaps even a
bit anomalous, but not unreasonable. The user might, for example, have
permissions that, in principle, give him write access to the mailbox but
have specific prohibitions for storing each message flag. (That's a
This is one of the most subtle parts of IMAP IMHO. READ-ONLY deals with
the messages in the folder, not necessarily the flags on those messages.
The flags on a messages can always be modified, but they might not be
persisted.
I'm not sure I understand what "honoring" permanentflags means. The
s
Nicely put and I see your point. I'm dealing with a wireless client that
isn't using the normal IMAP 'connected' model. Our sessions typically last
less than 5 minutes which has obviously influenced our design. However I
would expect folders that can't be modified to have the READ-ONLY property
sur
That behavior (empty permanentflags but flags) is explicitly allowed.
And if you read the spec VERY carefully you'll find it's REQUIRED if the
user can't modify the folder. The server maintains flags, but they
aren't persisted.
Think of it this way: FLAGS is the set of flags supported by the serv
Greetings, my first post here so an brief intro: I'm the developer building
IMAP client support for SnapperFish. We're responsible for 'SnapperMail'
(www.snappermail.com) a wireless email client for PalmOS based devices.
Question: How well honoured are FLAGS vs PERMANENTFLAGS in the IMAP
community
Hello,
I'm in the process of testing a little embedded IMAP server which is
part of a P2P messaging system and... I was wandering if there is an
"official conformance test suite" anywhere which could assist me with
uncovering any protocol related glitches in a more or less systematic
way?
RFC
