Hi all,
I think it could be a bug, or just a usecase that screws with zimbra.
I reproduced the exact same thing by following these steps
1, Created an account called test.test@domain
2 Added alias test@domain (don't know if this is needed)
3, logged in as test.test sent and received one email (again don't know if this is needed)
4, edited test.test in administrator, changed to text.example - *didn't save*, flipped to the alias tab and clicked add and added alias test.test@
5, clicked save
Error in administrator
Failed to add Aliases. Message: invalid request: LDAP schema violation: [LDAP: error code 65 - attribute 'zimbraMailAlias' not allowed] Error code: service.INVALID_REQUEST Method: AddAccountAliasRequest Details:soap:Sender
6, clicked close
7, clicked don't save to the close dialog
8, you see the account still in the accounts list, but if you navigate away and come back test.test is _gone_
9, click on Aliases tab and you get this error (if you flip to the page where the test.test alias would be.)
Server error encountered Message: system failure: target d4b71341-b485-41fe-a60f-1c16f5abf731 of alias
test.test@domain.com not found (zimbraId=d4b71341-b485-41fe-a60f-1c16f5abf731) Error code: service.FAILURE Method: SearchDirectoryRequest Details:soap:Receiver
So I can reproduce a nasty error every time by effectively trying to create an alias which is an exact match of the current account name (account: test.test@ alias test.test@domain). If I save the new account name before adding the alias everything works fine.
Hope this helps, it's is a bit late for me but if you know a way of retrieving the account now in purgatory then I would be interested in finding out.
It might also be worth reporting this so it can be fixed or managed in a future release?