Calendar Express in Communications Express Problem

Question

It seems intermittently, maybe after using commadmin to perform some task (e.g., add user to a e-mail dist. group), a user cannot access his calendar within communications express. I don't have the exact error - but it's something like calendar is not available.
Removing the <@domain.com> from the following 3 attributes,
Default Calendar: [email protected]$User One
Owned Calendar: [email protected]$User One
Subscribed Calendar: [email protected]$User One
seems to remedy this.
so they become:
Default Calendar: user1$User One
Owned Calendar: user1$User One
Subscribed Calendar: user1$User One
But recently, I wasn't able to fix this by editing these attributes in the DA, I got a 'could not save error.' and nothing in the ldap logs. I was however able to remove these as cn=Directory Manager in the LDAP console?
they had become multiples, e.g. for Default Calendar: there would be two values (one correct, and another incorrect):
Default Calendar:
user1$User One
[email protected]$User One
Any idea what this is about? I believe I have read it has something to do with the legacy vs. hosted specification when creating a user, these users are all created as legacy.
Thanks,
S7

Answer 1

The question really is, why do I have to keep correcting these 3 attributes. What's causing the @domain.com to be appended to them, or added as an entirely new value? e.g. an attributre seems to be able to have multiple values, as mentioned above.