Zimbra Forums

For anyone else that has this issue, it turned out there was a conflict with aliases. The account that wouldn't work had postmaster as an alias. The conflict occured because the new install had postmaster as an alias for admin.

I'm trying to move to a new zimbra server by using the backup/restore function. I'm running 8.0.3 NE on both servers. When I try to restore an accout I get the following message: zmrestore -a test@example.com -t /path/to/backup Error occurred: invalid attr value: invalid attr value - unable to modif...

Thanks for the response. That's good to know. However, I was particularly curious about whether the new Z10 worked with Activesync. It isn't really feasible for us to buy BES so it only makes sense to get a blackberry if it will be compatible with zimbra using active sync. Has anyone tried yet?

We are thinking of buying some blackberry z10s, but I would like to know for sure if push email will work using zimbra activesync. Does anyone have experience with this?
I apoligize in advance if this question has already been asked. I didn't see anything on google or in the forums.

For anyone else who has this problem, the resolution is in this thread

Thank you very much for the reply! I stopped zimbra, moved flush_enforcer.frm to /tmp, and restarted zimbra and now the database check doesn't find any errors and my backup is actually running! Thanks again for the help.

I already posted this problem in a different thread because I think it is causing my backups to fail, but I think it is a separate topic so I'm starting a new thread about it. When I run the db integrity check I get zimbra@mail:~$ libexec/zmdbintegrityreport -v Database errors found. /opt/zimbra/mys...

Thanks for your reply. I have 257 GB free where I store the backups, and in the past when the backups worked a full backup would only need about 5 GB of space. In my case I'm wondering if the problem has to do with the redo log in some way. Going back in my admin emails I found that on Sept 12 the b...

[quote user="jerryboi"][SOLVED] Resolution: You have to make sure that no fields have a trailing space in their name should you add custom tables to the zimbra database. The backup script chokes on field names with trailing spaces.[/QUOTE] I'm having this same problem where the backups are...

[quote user="bdial"]check your zimbraAuthTokenLifetime config for the cos. i found that having this set too high (mine was at 30d) caused this. setting it down to 5 fixed it[/QUOTE]
Thanks! That solved it.