[cmenke]

Thanks for your reply! I like the idea of the trick to create a new Account based on the old zimbraID, as the mysql db still provides the account entry!

Unfortunately I get following return when running zmprov to create the new account:

> zmprov ca x.y@z.tld password zimbraID 6aae8f57-f067-4d24-b949-20835271de8d
ERROR: service.INVALID_REQUEST (invalid request: zimbraId is immutable)

Is it possible that I have to set a flag somewhere to make it 'mutable' or is there any other way to circumvent this?

Edit: -v provides a lot more information, as far as i can tell unrelated to missing attributes though:

> zmprov ca testaccount@domain.tld password zimbraID 6aae8f57-f067-4d24-b949-20835271de8d
ERROR: service.INVALID_REQUEST (invalid request: zimbraId is immutable)
com.zimbra.common.soap.SoapFaultException: invalid request: zimbraId is immutable
ExceptionId:btpool0-13:1257984111589:34e6f1b24ca89e7b
Code:service.INVALID_REQUEST
at com.zimbra.common.soap.Soap12Protocol.soapFault(So ap12Protocol.java:88)
at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:263)
at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:224)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:261)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:216)
at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:315)
at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:279)
at com.zimbra.cs.account.soap.SoapProvisioning.invoke (SoapProvisioning.java:191)
at com.zimbra.cs.account.soap.SoapProvisioning.create Account(SoapProvisioning.java:325)
at com.zimbra.cs.account.ProvUtil.execute(ProvUtil.ja va:460)
at com.zimbra.cs.account.ProvUtil.main(ProvUtil.java: 2141)

is this of any help?