Archive for the ‘Zimbra’ Category
When I opened my Zimbra Desktop today I got a notification that the new version 7.1.4 is available. Of course I’ve updated directly.
Here’re the new features / enhancements:
- Users can move folders to “local folders” in Zimbra Desktop by dragging and dropping the folder to the desired location in “local folders”. The folder move might take some time before the move completes, in particular if the folder contains many messages, but also because the process of moving folders happens in the background. The move process copies the messages to the destination, and then deletes the messages from the source. (Bug 42542)
- Only Zimlets that are supported by ZCS are installed by Zimbra Desktop.
These are considered default Zimlets:
Attach Contacts • Phone• Date Highlights • Search• Drag-n-Drop Attachments • Social• Email Attacher • URL Links• Email Contact • WebEx• LinkedIn
- If upgrading from previous installations of Zimbra Desktop, already installed Zimlets remain. (Bug 61927)
- The Socialcast account can now be added and configured using the Social Zimlet. (Bug 60813)
- Zimbra Desktop prompts for a password when it cannot authenticate against the mail server. (Bug 54058)
For the full release notes please visit this link.
Two weeks ago I’ve decided to update my Zimbra Desktop Client 2.0 to the new beta version 7. All went well so far and I could see the new look and feel. Really nice changes to the UI. After a few days I had to change my domain password which is also my Zimbra password because the server is connected to the Active Directory. So good so far but I couldn’t open my Zimbra Desktop Beta 7 Client anymore. I always got the error message: service.FAILURE: system failure: Unable to unmarshal response for AuthResponse. I could find a thread in the Zimbra forums which helped me a bit and also a colleague was facing the issue and he could fix it. I’ve tried to fix the issue with his instruction but it didn’t worked.
He gave me the following hint:
Delete your email signature and reset the language to English via the Zimbra web interface.
In the forums I found some information which said:
If your signature or any of your other account settings in ZWC contain UTF-8 characters you will get this error. You can get around the problem for now by removing those characters from your signature.
I’ve tried that workaround and deleted the signature and set the language to English but still no chance to login via Zimbra Desktop.
After a few thought I came up with another idea! Checking the zdesktop.log file might be a good way to get more information on the issue. On Mac OS X you can find the file in the path /Users/christoph/Library/Zimbra Desktop/log. Of course it helped me. I found out that there where more UTF-8 characters in the AuthResponse. Both the signature and the Out-of-Office notification contained the UTF-8 characters. After deleting also the OOO-message I could login again. That’s a first workaround but I think this will be fixed in the next beta version of the Zimbra Desktop client. I hope this helps.
This week my companies email account has changed from Exchange to Zimbra Collaboration Server due to my participation in an internal pilot program. This is great because I’m already using the Zimbra server and also the desktop client privately for a while and I’m really happy with it. What I’ve never thought about before is the backup procedure of my local stored folders which are not synchronized with the cloud. In my private environment that was never an issue for me because my email account has no restricted size. With the companies account I got a limit of 2 GB which is a lot, but not enough when storing all PDF and PPT files as well as the archived mails. Because I’m a Mac user and usually using Time Machine for my backup I was wondering if there is another way to do a backup of the Zimbra Desktop data including my local stored folders. Some googleing gave me the final hint!
For quite a while now I’ve tried to get Zimbra Desktop working with my Zimbra Collaboration Server (ZCS) but I couldn’t get it running. I’ve always received an error message saying: account.INVALID_ATTR_VALUE: zimbraPrefForwardIncludeOriginalText must be one of: …” for me just something like: $&%°!%!" so I left it for a while. But again I thought there must be a way to get it running and I investigated the issue.
Due to some limitations with the Zimbra ZCS Open Source edition, especially the missing ActiveSync protocol feature I’ve decided to update my mail server to Zimbra Collaboration Suite Network Edition. The upgrade was easy going, just start the ./install.sh script and let it go. The installer asks you for holding the configuration data and after 10-15 minutes my server was running the commercial version with a much better feature set. ActiveSync and mobile devices support are not the only features which I wanted. Also the integrated backup and software updating function was a good enhancement as I see today. I love the software update check which can be configured on a daily, hourly or minutely basis. It will inform you directly when a new release of the collaboration server is available. Great for me because I’m always forgetting to update my services to the newest release.
The good thing is that the update feature is not automatically upgrading your server when a new version is available. You can just configure ZCS to send you an email if a new update is available at the Zimbra website.
Also the backup is great. In the Open Source edition I had to write a script and run a Cron job to backup my server but now, with the Network Edition this is implemented in the admin console. Just selecting the Backup link offers me the option to do a full or an incremental backup of my server.
It’s also possible to do an easy restore for all accounts or just the accounts which have maybe a corrupt database or the users having deleted their data by mistake.
I think Zimbra ZCS Network Edition is a great competition for other collaboration solutions. It’s great that Zimbra can run in either the private or public cloud. If you haven’t seen Zimbra yet, you should definitely check it out at www.zimbra.com.
I’m using the Zimbra Collaboration Suite for some days now and I have to say that I’m really happy with it. The user web interface is just awesome, easy to use and I love the Ajax stuff. I’m also using it on my iPhone and it runs perfectly. There was just one thing which made me feel a bit uncomfortable with. After the installation the Webmail component was just accessible via HTTP which is not encrypted. During the last years I got some bad experience with other applications which needed to be changed from HTTP to HTTPS and this time I had a uneasy feeling but it was without any reason.
Running out of memory will prevent the Linux system from running ZCS because it can’t create the needed Java virtual machine and also start essential processes like the MTA. During the installation I came to several situations where I ran out of memory but in the end I could install the software but not start all services. I needed some optimization here. After some searching on the web I found tips which helped me.
Before I go on with the tuning tips for the Vserver I want to give you an overview of the most important command line parameters and log files. For the log files I’ve found a great resource in the Zimbra Wiki. During installation and configuration I’ve needed the zimbra.log which can be found at /var/log/zimbra.log. In this file you’ll find information for MTA, the system status and 3rd party software as Postfix, Amavisd and more. Also interesting is the Tomcat web server log which helped me finding installation errors with the web interface. The information is written in two files: /opt/zimbra/log/mailbox.log and /opt/zimbra/tomcat/logs/catalina.out.
The first command I needed on the server was zmcontrol. With zmcontrol which is located in /opt/zimbra/bin/zmcontrol, you can start and stop services and also get an status.
During this week I spent every night at my laptop, to get the the server running. Not because the installation is so hard, no because I don’t want to RTFM. So I had to run the setup several times. It’s important that you have a valid A-Record and MX-Record for your Zimbra Collaboration Server. During the setup those two DNS parameters will be checked. It seems that you can install the software even when you have not configured it but I read in some forums that you can get errors. You’ll also need to edit the /etc/hosts file in order to get a successful installation.
127.0.0.1 localhost.localdomain localhost
xxx.xxx.xxx.xxx mail.thatsmyview.net mail
As with every fresh installed Ubuntu system you should also run apt-get upgrade to get the latest fixes. If you start the ZCS installation now it will stop due to missing dependencies. I had to install some additional packages.
apt-get install libpcre3 libgmp3c2 libstdc++5
Possibly you’ll have to install more or less packages depending on your core installation and the selected options. The Zimbra installation can begin. First untar/gunzip the archive file and then start the installation through the installation script.
The installer will ask you which components should be installed. As I’ve to less RAM for all of them I’ve decided to leave the proxy, logger and the memcached option. After that you can configure loads of parameters but the only one which is really needed is the admin password. Press menu 4, then 3 to set the password. Then press a to apply the options and save the configuration in a file as suggested. The setup will try to start the services after the installation but here I got in trouble. The RAM was already full and the Java virtual machine couldn’t be started. Bad for me and I first thought of getting more RAM for my Vserver but in the end I found some more helpful stuff on the web to go on without expanding memory and spending more money. In case you have a Vserver or physical box with just 1 GB of memory, wait for an upcoming article which will give you the needed parameters to successfully run ZCS.