Tag Configuration object draft

[Thomas Jarosch]

On Thursday, 27. February 2014 13:19:19 Jeroen van Meeuwen wrote:
> However, should message $x (already received) be tagged, and a copy of
> message $x be forwarded to the same recipient, and with the same
> Message-ID [1], becoming message $y, the duplicate appearing as having
> been tagged is not a completely insurmountable side-effect, and
> otherwise barely relevant unless your boss forwards you a message that
> you had tagged as "IGNORE".

LOL

> That said, the way that duplicate delivery suppression has resolved the
> issue is by matching more headers than just the one Message-ID. Perhaps
> it is not unreasonable to at least allow the storage format used to
> include such additional headers as well, solely in an attempt to
> uniquely identify the message.

may be some unorthodox request and it came up earlier:
Can't the tagging be stored in the headers of the individual message?

Then it's really unique to that specific message. It also won't have
any problems if you copy the message to another folder and
untag the copy only.

Some kind of "X-Kolab-Message-Tag" header. An "external" message tag needs 
always to be synchronized to the current mail folder content and I think
its annoying for the user if the tag gets lost somehow.

Cheers,
Thomas