Re: IMAP Flags clarification.

[Joseph Brennan]

\Seen is an IMAP flag. Unseen means "Messages that do not have the \Seen 
flag set."

I don't know what "high priority" means in this context. If you mean 
headers like "Priority: Urgent" or "X-Priority: 1", those are not IMAP 
flags. And for that reason I don't know what Michael Slusarz means by the 
order in which the server returns the flags.

Evidently Horde IMP can show only one of the two things, but whether it 
prefers an IMAP state to the content of a header sure seems to me like an 
IMP client-side decision.

I am probably missing something here.

Joseph Brennan
Columbia University Information Technology



--On August 27, 2013 13:51:35 +0530 Anant Athavale 
 wrote:

> It's entirely dependent on the order the IMAP server returns the IMAP
> flags.
>
> The problem is that both 'unseen' and 'high priority' have the same CSS
> importance.  CSS only allows a binary determination of what is
> "important".  Thus, 2 or more rules with labeled important necessarily
> need to overwrite each other in either a FIFO or LIFO manner.
>
> Writing code to get around this would be prohibitively expensive and not
> worth it - especially since "priority" is not even a real, recognized
> flag.






Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

IMAP Flags clarification.

[Anant Athavale]

Dear List,

I have been using cyrus rpms provided by invoca.ch.  The version being used
is;

cyrus-imapd-debuginfo-2.4.17-6.el6.x86_64
cyrus-imapd-devel-2.4.17-6.el6.x86_64
cyrus-imapd-utils-2.4.17-6.el6.x86_64
cyrus-imapd-2.4.17-6.el6.x86_64

I am using Horde groupware webmail edition and I am facing issues with
mails composed with High Priority.

Please look at the thread

http://lists.horde.org/archives/imp/Week-of-Mon-20130819/055306.html

As per the developer of Horde:

*It's entirely dependent on the order the IMAP server returns the IMAP
flags.

The problem is that both 'unseen' and 'high priority' have the same CSS
importance.  CSS only allows a binary determination of what is "important".
 Thus, 2 or more rules with labeled important necessarily need to overwrite
each other in either a FIFO or LIFO manner.

Writing code to get around this would be prohibitively expensive and not
worth it - especially since "priority" is not even a real, recognized flag.

michael*

Can anybody clarify on this  from Cyrus IMAPd server view?

-- 
anant athavale.
bangalore

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus