[SOLVED] user can't log in because of tag bug...?

[stuartg.orion]

Bug 23488 - Orange Tag not supported

We are currently hitting this bug in version 5.0.2. Can anyone please how I could remove a tag so the user affected can log in?

Our error message is:

HTTP ERROR: 500

invalid color: 80, valid values: [defaultColor, blue, cyan, green, purple, red, yellow, pink, gray, orange]

RequestURI=/zimbra/h/search
Caused by:

com.zimbra.cs.zclient.ZClientException: invalid color: 80, valid values: [defaultColor, blue, cyan, green, purple, red, yellow, pink, gray, orange]
Code:zclient.CLIENT_ERROR
at com.zimbra.cs.zclient.ZClientException.CLIENT_ERRO R(ZClientException.java:51)
at com.zimbra.cs.zclient.ZTag$Color.fromString(ZTag.j ava:61)
at com.zimbra.cs.zclient.ZTag.(ZTag.java:69)
at com.zimbra.cs.zclient.ZMailbox.handleRefresh(ZMail box.java:555)

[mmorse]

Can you login to the advanced (AJAX) web-client & change the tag color?
You could also do a SOAP TagActionRequest to change it.

[stuartg.orion]

No he can't log into his account using any web client (and neither can I using the admin interface view mail button).

Also I get pretty much the same error when I try and use zmmailbox on his account:

[zimbra@akl-zm2 conf]$ zmmailbox -z -m useraccount gat -v
ERROR: zclient.CLIENT_ERROR (invalid color: 80, valid values: [defaultColor, blue, cyan, green, purple, red, yellow, pink, gray, orange]) (cause: java.lang.IllegalArgumentException No enum const class com.zimbra.cs.zclient.ZTag$Color.80)


How would I create the Soap Request?

[mmorse]

I've attached some soap information (you can also append ?dev=1 on a working account and you'll see the full structure). Might also need to do some debugging (zmprov aal user@domain.com zimbra.soap debug or logger.com.zimbra.soap=DEBUG).
Using the below syntax you should be able to reset them-
By ID:

zmmailbox -z -m user@domain.com mtc id green

Or by name:

zmmailbox -z -m user@domain.com mtc test green

SOAP tidbits:

<TagActionRequest>
<action op="read|rename|color|delete|update" id="..." [name="..."] [color="..."]/>
</TagActionRequest>
- if op="update", the caller can specify "name" and/or "color"

ZTag.Color
public enum Color {
orange(0),
blue(1),
cyan(2),
green(3),
purple(4),
red(5),
yellow(6),
orange(9);

[mmorse]

That bug corrected it so that tags with 0 & 9 were rendered as orange.
You can technically set it between 0-127, so you weren't hitting that particular bug with a value of 80 which the client can't display. I might open a bug on how that's handled, as it should react the same as setting it to pink(7) & gray(8) does (still allows the client to function fine).

To try and nail down how this happened:
Is there a thick-client somewhere in the picture?
Is there a tag with an ID of 80? (ie: Did we accidentally cross the tag ID with color somewhere?)

[stuartg.orion]

Hi Mike,

I've logged a support call about this now. Nothing's worked yet though.

Most of the zmmailbox commands I've tried give a similar error to the one the user gets in the browser. Eg:

[zimbra@akl-zm2 ~]$ zmmailbox -z -m user@domain gat
ERROR: zclient.CLIENT_ERROR (invalid color: 80, valid values: [defaultColor, blue, cyan, green, purple, red, yellow, pink, gray, orange]) (cause: java.lang.IllegalArgumentException No enum const class com.zimbra.cs.zclient.ZTag$Color.80)
[zimbra@akl-zm2 ~]$

Unfortunately the user says he has lots of tags and can't remember what they're called.

He is using thunderbird to get at his mail now. In the past he has used Outlook

[mmorse]

Ok, anything useful out of:

zmmailbox -z -m user@domain.com -d | grep tag

[mmorse]

By the way (don't know if you saw my edit above):

zmprov aal user@domain.com zimbra.soap debug

('ral' turns it off, 'gal' lists currently enabled on the account, 'gaal server' spits them all out, & other logging levels are listed here)

[stuartg.orion]

Ok getting somewhere, thanks Mike!
So from "zmmailbox -z -m user@domain.com -d | grep tag" I got:
<tags>
<tag id="79" color="80" name="Conference Call"/>
<tag id="76" color="3" name="Sales"/>
<tag id="75" color="88" name="Travel Required"/>
<tag id="64" color="0" name="SugarCRM"/>
</tags>

And then the error. So the culprit is tag 79 (and possibly 75 as well), I then tried the dt call on that id but that didn't work - it triggers the error first, I'll have a look at the logging levels.

Thanks once again

[mjp]

hi,

Same here, customer does use outlook07 but the bug occured after doing something (tag related) in ZWC. at least the user thinks.

And in my case it is another tag color: invalid color: 87

zmmailbox -z -m user@domain -d | grep tag
<tags>
<tag id="65" color="3" name="tag_a"/>
<tag id="77" color="6" name="tag_b"/>
<tag id="69" color="5" name="tag_c"/>
<tag id="86" color="87" name="tag_d"/>
<tag id="79" color="1" name="tag_e"/>
<tag id="88" color="88" name="tag_f"/>
<tag id="90" color="3" name="tag_g"/>
<tag id="91" color="83" name="tag_h"/>
<tag id="92" color="88" name="tag_i"/>
<tag id="93" color="85" name="tag_j"/>
<tag id="82" color="4" name="tag_k"/>
<tag id="74" color="3" name="tag_l"/>
<tag id="68" color="76" name="tag_m"/>
</tags>
ERROR: zclient.CLIENT_ERROR (invalid color: 87, valid values: [defaultColor, blue, cyan, green, purple, red, yellow, pink, gray, orange]) (cause: java.lang.IllegalArgumentException No enum const class com.zimbra.cs.zclient.ZTag$Color.87)

mtc did not help, haven't tried dt because it did not work above. zimbra.soap debug on the account let me see the whole soap request, but that does not really help...

any news?
thanks!