Message Flags: Difference between revisions
(New page: '''Zimbra Message Flags''' Zimbra Messages have a "flags" attribute that describes the state of the message. This flags attribute is of type String and has a one character code which repr...) |
No edit summary |
||
| Line 5: | Line 5: | ||
u -> unread | u -> unread | ||
f -> flagged | f -> flagged | ||
a -> has attachment | a -> has attachment | ||
s -> sent by me | s -> sent by me | ||
r -> replied | r -> replied | ||
w -> forwarded | w -> forwarded | ||
d -> draft | d -> draft | ||
x -> deleted | x -> deleted | ||
n -> notification sent | n -> notification sent | ||
by default a message priority is "normal" otherwise: | by default a message priority is "normal" otherwise: | ||
! -> priority high | ! -> priority high | ||
? -> priority low | ? -> priority low | ||
| Line 23: | Line 34: | ||
flags attribute should be of type uint and store bitwise flags. They are easier and faster to parse. | flags attribute should be of type uint and store bitwise flags. They are easier and faster to parse. | ||
--[[User:Fernandoflorez|Fernandoflorez]] 07:43, 23 February 2009 (UTC) | |||
Revision as of 07:43, 23 February 2009
Zimbra Message Flags
Zimbra Messages have a "flags" attribute that describes the state of the message. This flags attribute is of type String and has a one character code which represents a state:
u -> unread
f -> flagged
a -> has attachment
s -> sent by me
r -> replied
w -> forwarded
d -> draft
x -> deleted
n -> notification sent
by default a message priority is "normal" otherwise:
! -> priority high
? -> priority low
Improvement
flags attribute should be of type uint and store bitwise flags. They are easier and faster to parse.
--Fernandoflorez 07:43, 23 February 2009 (UTC)
