Clear text makes more sense — using a json structure and allows other clients to read it easier (and make rules better)
For example it is better to have a rule
if x-MailTags header contains aProjectName
Than
if x-MailTags header contains f8ul43isa==sdfese (encoding of aProjectName)

:)

As for Zimbra syncing — unfortunately it is not a two way street — and a bit of a kludge.

Clear text makes more sense — using a json structure and allows other clients to read it easier (and make rules better)
For example it is better to have a rule
if x-MailTags header contains aProjectName
Than
if x-MailTags header contains f8ul43isa==sdfese (encoding of aProjectName)

:)

As for Zimbra syncing — unfortunately it is not a two way street — an a bit of a kludge.

Although my emails still contain an X-MailTags header with info like this in it:

X-Mailtags: { “mailTagsProject” : ["Hawk Wings"]}

I wonder how that happened. Perhaps you should post over in Scott’s forums — http://forums.indev.ca/

X-Keywords: todo

(todo is one of my predefined keywords). I use a rule in Zimbra that says that if the header named ‘x-keywords’ contains ‘todo’ then the message should be tagged with a Zimbra tag. But this never happens.