It seems simple enough, both servers support imap but the devil’s in the details: cyrus puts all mail under INBOX, Zimbra does not by default and cyrus uses ‘.’ as a separator while Zimbra uses ‘/.’ Add –delete2 if you’ve been testing for a few days on an active server and the target server has mail that is getting stale:

$ imapsync --sep1 \. --prefix1 INBOX\. \
    --authmech1 PLAIN --ssl1 --host1 sourcehost.domain.org \
        --user1 morgan --password1 pass \
    --authmech2 PLAIN --ssl2 --host2 targethost.domain.org \
        --user2 morgan --password2 pass \
    --useheader Message-ID --useheader From --useheader To \
        --skipsize  --delete2

I have a client who has long used Zimbra’s archiving feature: we set it up several versions ago and regularly use it to retrieve messages sent/received on a per-user basis for various purposes.

We recently had a need to search across multiple accounts. We’ve long known that Zimbra offered a tool to do this searching but never got around to looking into it.

http://wiki.zimbra.com/wiki/Ajcody-Notes-Archive-Discovery-Mailstore-Setup

So click Tools->Search Mail in the admin interface. Simple, yes? In both their development and production environments we get a pop-up error like this:

Message: unknown document: GetXMbxSearchesListRequest Error code: service.UNKNOWN_DOCUMENT Method: GetXMboxSearchListRequest Details:soap:Sender

A quick look at the mailbox.log shows the archive store (mail06) is proxying to the Logger store (mail01).

2010-12-21 12:50:56,480 INFO [btpool0-7://mail06.domain.org:7071/service/admin/soap/GetXMbxSearchesListRequest] [name=admin@domain.org;mid=33900;ip=10.0.0.123;ua=ZimbraWebClient - FF3.0 (Mac);] soap – GetXMbxSearchesListRequest (Proxying to ProxyTarget(url=https://mail01.domain.org:7071/service/admin/soap/GetXMbxSearchesListRequest))

I’m reasonably sure it’s a coincidence that it is looking to the Logger store but it is consistent in both of their environments. Incidentally: changing zimbraLogHostname doesn’t fix the problem.

The only fix I’ve found is to re-run the installer and add a zimbra-archiving to the Logger host (mail01.domain.org in this example).

There has to be a setting that configures this.

A seemingly innocuous DNS configuration change caused all of the RBL checks in a client’s Zimbra Spamassassin to trigger mail that would have only had an X-Spam-Score of 2 or 3 to register 7+. This of course lead to legitimate mail to end up in users’ Junk folders.

Our Junk boxes age out in 2 or so weeks and our user base is not in the habit of checking regularly since most SPAM is caught at the gateway and not delivered to Junk. It was decided that the best solution for us was to just move mail delivered to Junk in the last 5 days back into users’ inboxes.

It turns out imapsync can be easily configured to move mail intra-server and intra-account by supplying the same host and user, limiting to –folder Junk and changing –prefix1 and –prefix2. If you have tens of thousands of accounts you may want to parallelize this but for the sake of brevity here’s a short shell script that moves all mail from the last 5 days from Junk to INBOX in a Zimbra environment:

#!/bin/sh
#
p=pass
au=user
h=imap.domain.org

echo starting at `date`
for u in `sudo su - zimbra -c "zmprov -l gaa"|grep -v archive|cut -d @ -f 1`; do
    echo; echo ${u}:
    c="imapsync ${1} --folder Junk --maxage 5 \
        --prefix1 Junk  --ssl1 --host1 ${h} --authuser1 ${au} --user1 ${u} --password1 ${p}\
        --prefix2 INBOX --ssl2 --host2 ${h} --authuser2 ${au} --user2 ${u} --password2 ${p}"
    echo $c
    $c
done
echo finished at `date`

This is Zimbra 6.0.8 but it should work in any version at least up to that:

“user” must be set up as a zimbra admin. I imagine the Zimbra admin user would work.

This script does disclose the password on the command line so it will show up in a ps(1) output. imapsync does include –passfile options to correct this.

If you’re thinking this looks handy but are overwhelmed by the idea of installing imapsync (it has a ton of dependencies) and use CentOS or Redhat I can vouch for epel’s (http://fedoraproject.org/wiki/EPEL) distribution of imapsync. Install the epel repository and imapsync is just a “yum install imapsync” away.