Cyrus imapd 2.5 on ARM

hede kolab983 at der-he.de
Fri Oct 10 17:09:37 CEST 2014


Hi list, 

I'm using Kolab 3.x for some time now (3.0->3.1->3.2).
Because for me it seems broken on arm I'm not using cyrus-imapd-2.5 from 
kolabsys.com, even I'm using Kolab 3.2. 
But I would like to switch to Kolab 3.3 and cyrus imapd 2.5.

The last days I gave it another try, I've compiled 
cyrus-imapd_2.5~dev2014082101-0~kolab1_armhf.deb
from the kolab sources (http://obs.kolabsys.com:82/Kolab:/...).

(((
dpkg-source -x cyrus-imapd_2.5~dev2014082101-0~kolab1.dsc
cd cyrus-imapd-2.5~dev2014082101
dpkg-buildpackage -us -uc
... results in the deb abobe
)))

I did so with the whole kolab sources. And installed it.
But it doesn't do it's job. Many problems... many...

Then I've created a fresh Debian 7 lxc vm, installed only cyrus-imapd 
with it's dependencies plus sasl2-bin to have a working environment. 

Using cyradm to create a mailbox results in a clear behaviour:

###################

root at kolab33test:/var/lib/imap# cyradm -u cyrus localhost
verify error:num=18:self signed certificate
IMAP Password: 
              localhost> 
localhost> lm
localhost> cm mbox1
localhost> cm mbox2
localhost> lm 
localhost> cm mbox1
createmailbox: System I/O error
localhost> cm mbox2
createmailbox: System I/O error
localhost> lm
localhost> quit
root at kolab33test:/var/lib/imap# 

###################

It seems all files got created:

###################
root at kolab33test:/var/lib/imap# find /var/spool/imap/
[...]
/var/spool/imap/m
/var/spool/imap/m/mbox2
/var/spool/imap/m/mbox2/cyrus.header
/var/spool/imap/m/mbox2/cyrus.cache
/var/spool/imap/m/mbox2/cyrus.index
/var/spool/imap/m/mbox1
/var/spool/imap/m/mbox1/cyrus.header
/var/spool/imap/m/mbox1/cyrus.cache
/var/spool/imap/m/mbox1/cyrus.index
/var/spool/imap/.viminfo
/var/spool/imap/j
/var/spool/imap/d
root at kolab33test:/var/lib/imap# 
###################

But even after reconstructing the hole /var/lib/imap directory (deleting and 
recreating a mailbox.db with mbox1 and mbox2 in it) "lm" results in nothing 
and "cm" results in an I/O error and not complaining about an existing mailbox.

I don't know how to solve this problem.

Anybody else using cyrus imapd 2.5 on arm or any other non-Intel environment?

regards
hede



More information about the users mailing list