The clients are broken imho - the untagged fetch response should be the overriding feature.
However, your server is ALSO broken according to the spec. Flag modifications MUST occur when requested. The server doesn't have to commit the changes to disk (that's what permenantflags is for), but the server is REQUIRED to respect flag changes by the client (I don't have the reference, but it's there (it bit us in the Exchange server when we used clients against read-only mailboxes)). Larry Osterman -----Original Message----- From: Rick Block [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 7:06 PM To: [EMAIL PROTECTED] Subject: speaking of storing flags I'm working on a server that cannot make a message unseen once it's been marked seen. I've tried returning untagged fetch responses to store attempts to clear the seen flag, like so (assuming message 1 is already seen): c: xyzzy store 1 -flags (\seen) s: * 1 fetch (flags (\seen)) s: xyzzy OK but the clients I've tried (Outlook Express 5 and a fairly old version of Netscape Communicator) seem to completely ignore the untagged response (the message starts out looking seen in the client, after marking the message unseen via their user interface even with the untagged fetch response the message is displayed as unseen). I've tried a NO response; this is treated as a protocol error by these clients. Anyone have any ideas how to better handle this situation? Would you consider these clients broken? Thanks, Rick Block Avaya Inc. -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html ----------------------------------------------------------------- -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html -----------------------------------------------------------------
