saslauth problem / imap login does not work

[Michael Schmitt]

Hi list!

I did install the new kolab2 beta3 (formerly beta2 with the same
"success") and can't login via imap but on the webadminpage I am able to
log in with an user account I created. The same problem (at least I
think it is more or less related) does "UK Linux" aka "Charles Johnson"
have.
I got the packages from:
http://max.kde.org:8080/mirrors/ftp.kolab.org/server/beta/kolab-server-2.0-beta-3/ix86-debian3.0

My setup:
A local network with a local domain which is served by a local bind9
nameserver. There is an MX record which points to a local mailserver.
The host for Kolab is Debian Woody. The install and bootstrap (according
to README.1st) completed without errors or complaints.

Some specs for the local network:
domain = tcw.local
DNS = europa.tcw.local
MX = mail.tcw.local
Kolab = kolab.tcw.local
No firewall inside the network!

Some commands with output to proof the DNS is working:
mschmitt at amalthea:~$ host -t MX tcw.local
tcw.local               MX      80 mail.tcw.local
---
mschmitt at amalthea:~$ host kolab
kolab.tcw.local         A       192.168.0.121
---
mschmitt at kolab:~$ /sbin/ifconfig eth0 |grep "inet addr"
          inet addr:192.168.0.121  Bcast:192.168.0.255
Mask:255.255.255.0

A glimpse in the logs:
Here are some samples which I think may be relevant.
First /kolab/var/sasl/log/saslauth.log:
Mar 12 01:07:06 kolab.tcw.local <info> saslauthd[25642]:
detach_tty      : master pid is: 25642
Mar 12 01:07:06 kolab.tcw.local <info> saslauthd[25642]:
ipc_init        : listening on socket: /kolab/var/sasl/saslauthd/mux
Mar 12 01:08:02 kolab.tcw.local <debug> saslauthd[25642]: Domain/Realm
not available.
[...]
Mar 12 01:10:08 kolab.tcw.local <debug> saslauthd[25642]: Domain/Realm
not available.
Mar 12 01:10:08 kolab.tcw.local <error> saslauthd[25642]: user
ldap_search_st() failed: Can't contact LDAP server
Mar 12 01:10:08 kolab.tcw.local <info> saslauthd[25642]: Retrying
authentication
[...]
Mar 12 01:20:08 kolab.tcw.local <debug> saslauthd[25642]: Domain/Realm
not available.
[...]
Mar 12 01:40:05 kolab.tcw.local <debug> saslauthd[25657]:
ldap_simple_bind() failed -1 (Can't contact LDAP server).
[...]

Next /kolab/var/imapd/log/master.log:
Mar 12 01:07:35 kolab.tcw.local <error> master[26619]: setrlimit: Unable
to set file descriptors limit to -1: (1) Operation not 
permitted
Mar 12 01:07:35 kolab.tcw.local <error> master[26619]: retrying with
1024 (current max)
Mar 12 01:07:35 kolab.tcw.local <notice> master[26619]: process started
Mar 12 01:07:35 kolab.tcw.local <debug> master[26656]: about to
exec /kolab/bin/ctl_cyrusdb
Mar 12 01:07:38 kolab.tcw.local <notice> master[26619]: ready for work
Mar 12 01:07:38 kolab.tcw.local <debug> master[26722]: about to
exec /kolab/bin/tls_prune
Mar 12 01:07:38 kolab.tcw.local <debug> master[26723]: about to
exec /kolab/bin/ctl_deliver
Mar 12 01:07:38 kolab.tcw.local <debug> master[26724]: about to
exec /kolab/bin/ctl_cyrusdb
Mar 12 01:07:39 kolab.tcw.local <debug> master[26619]: process 26724
exited, status 0
Mar 12 01:07:46 kolab.tcw.local <debug> master[26619]: process 26722
exited, status 0
Mar 12 01:07:46 kolab.tcw.local <debug> master[26619]: process 26723
exited, status 0
Mar 12 01:07:57 kolab.tcw.local <debug> master[26945]: about to
exec /kolab/bin/imapd

Then /kolab/var/imapd/log/misc.log:
Mar 12 01:07:37 kolab.tcw.local <notice> ctl_cyrusdb[26656]: recovering
cyrus databases
Mar 12 01:07:37 kolab.tcw.local <notice> ctl_cyrusdb[26656]: done
recovering cyrus databases
Mar 12 01:07:38 kolab.tcw.local <notice> ctl_cyrusdb[26724]:
checkpointing cyrus databases
Mar 12 01:07:38 kolab.tcw.local <debug> ctl_cyrusdb[26724]: archiving
database file: /kolab/var/imapd/annotations.db
Mar 12 01:07:39 kolab.tcw.local <debug> ctl_cyrusdb[26724]: archiving
log file: /kolab/var/imapd/db/log.0000000001
Mar 12 01:07:39 kolab.tcw.local <debug> ctl_cyrusdb[26724]: archiving
database file: /kolab/var/imapd/mailboxes.db
Mar 12 01:07:39 kolab.tcw.local <debug> ctl_cyrusdb[26724]: archiving
log file: /kolab/var/imapd/db/log.0000000001
Mar 12 01:07:39 kolab.tcw.local <notice> ctl_cyrusdb[26724]: done
checkpointing cyrus databases
Mar 12 01:07:45 kolab.tcw.local <notice> tls_prune[26722]: tls_prune:
purged 0 out of 0 entries
Mar 12 01:07:45 kolab.tcw.local <notice> cyr_expire[26723]:
duplicate_prune: pruning back 3 days
Mar 12 01:07:45 kolab.tcw.local <notice> cyr_expire[26723]:
duplicate_prune: purged 0 out of 0 entries
Mar 12 01:07:45 kolab.tcw.local <notice> cyr_expire[26723]: expunged 0
out of 0 messages from 0 mailboxes
Mar 12 01:08:00 kolab.tcw.local <debug> imap[26945]: executed
Mar 12 01:08:01 kolab.tcw.local <debug> imap[26945]: accepted connection
Mar 12 01:08:02 kolab.tcw.local <notice> imap[26945]: login: kolab
[127.0.0.1] manager plaintext User logged in
Mar 12 01:08:30 kolab.tcw.local <debug> imap[26945]: accepted connection

Some final words:
I did reinstall several times (purging /kolab, removing the user kolab,
purging /etc/rc?.d/*kolab and the refering initscript in /etc/init.d,
then a complete reinstall) and tried to tweak the dns system (to that
what it looks like now) because someone familiar with kolab said it is
most likely a dns issue. Furthermore I did read and search the
kolab-user mailinglist to no avail... I think I found one or two people
having the same problem but there it was said the broken dns would be
most likely the culprit.

Sorry if this mail got somehow a bit big ;) but I tried to give as much
infomation as possible and to avoid some basic re-questions. Any help is
greatly appreciated!

regards
Michael Schmitt

P.S.: Sorry for the possible duplicate mail. I used the wrong
from-address the first time :)