[Tickets #8306] Re: Marking as unread missing
bugs at horde.org
bugs at horde.org
Thu May 28 15:22:24 UTC 2009
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/8306
------------------------------------------------------------------------------
Ticket | 8306
Updated By | Michael Slusarz <slusarz at horde.org>
Summary | Marking as unread missing
Queue | IMP
Version | Git master
Type | Bug
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners | Michael Slusarz
------------------------------------------------------------------------------
Michael Slusarz <slusarz at horde.org> (2009-05-28 11:22) wrote:
> Turns out that this was due to the msgflags_hidesys preference being
> turned on by default and no way to turn it off for the user. I
> changed both, but I wonder why we need this setting at all. I doesn't
> make much sense to me.
Turns out that the main issue is that the seen flag should have been
of type 'imapu', not 'imap'.
Agreed that a separate msgflags_hidesys pref is not needed - this can
be handled entirely via the 'imap' vs. 'imapu' type field in the
msgflags pref. I've made this change. However, the theory behind the
pref is still sound - not all system flags should be user-settable (by
default). For example, the forwarded, draft, and answered flag should
really never be set by the user. These flags indicate specific things
at the IMAP level and messing with them is arguably breaking RFCs.
Thus the need to not show these flags in the Mark Messages dropdown.
Theoretically, the deleted flag should be on this list also since it
should be set exclusively via Delete/Undelete actions. However, since
we allow switching between Trash and non-Trash mode, it is sometimes
necessary to remove unwanted deleted flags. And even though unseen
also should not be theoretically settable, it is the single most
important flag in terms of message highlighting that it is ok to allow
being set.
More information about the bugs
mailing list