Hello there,
I'm trying to run Cassandane on my laptop, because I'm interested in
writing tests and automating the execution thereof.
Having followed the instructions in doc/setting_up.txt -liberally, I
must admit-, I notice that;
- While Cyrus IMAP is installed with a proverbial './configure; make;
make install DESTDIR=/var/tmp/cyrus-imapd-2.4/', and the binaries
therefore end up in /var/tmp/cyrus-imapd-2.4/usr/cyrus/bin/, the
configuration that Cassandane writes out refers to binaries in
/var/tmp/cyrus-imapd-2.4/bin/, a directory that does not exist.
Please find that:
$ cat /var/tmp/cass/cassandane/conf/cyrus.conf
START {
# integrity check and setup of databases
recover cmd="ctl_cyrusdb -C /var/tmp/cass/cassandane/conf/imapd.conf
-r"
}
SERVICES {
imap listen=127.0.0.1:9100 cmd="/var/tmp/cyrus-imapd-2.4//bin/imapd
-C /var/tmp/cass/cassandane/conf/imapd.conf"
}
and;
$ cat cassandane.ini | grep -v ^#
[cassandane]
rootdir = /var/tmp/cass
[cyrus default]
prefix = /var/tmp/cyrus-imapd-2.4/usr/cyrus
[gdb]
[config]
cyrus_prefix = /usr/cyrus
prefix = /var/tmp/cyrus-imapd-2.4
- When /var/tmp/cyrus-imapd-2.4/bin/ is created a symbolic link for, to
/var/tmp/cyrus-imapd-2.4/usr/cyrus/bin/, Cyrus IMAP / Cassandane
ultimately fails authenticating. I recon this is a Cyrus SASL thing, but
I was wondering whether Cassandane requires the system to have a valid
SASL configuration with an 'admin' user, whether any additional users
would be required, and whether it could be made so that no such
system-wide configuration is required (by starting an SASL auth daemon
with a different user database then the system database?).
Kind regards,
Jeroen van Meeuwen
--
Systems Architect, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com
pgp: 9342 BF08
