Kolab on Debian Etch

[Saim Kim]

Hello Alex,

I used both binary and source files on a clean install of Etch (no VM). 
I didn't find any errors in the kolab-install.log Just this note after 
imapd is prepared:

+----------------------------------Notice-------------------------------------+
| To complete the Cyrus IMAP installation 
do:                                 |
| 1. start SASL and Cyrus IMAP 
with:                                          |
|    /kolab/bin/openpkg rc sasl 
start                                         |
|    /kolab/bin/openpkg rc imapd 
start                                        |
| 2. hook Cyrus IMAP into your particular MTA 
manually                        |
|    (usually configure mail delivery via 
LMTP)                               |
| 3. create mailboxes for each of your 
users:                                 |
|    $ /kolab/bin/cyradm --user=root 
localhost                                |
|    cyradm> createmailbox 
user.<user>                                        |
|    cyradm> setaclmailbox user.<user> <user> 
lrswipcd                        |
|    cyradm> mboxconfig user.<user> comment 
"<name>"                          |
|    cyradm> setquota user.<user> STORAGE 
500000                              |
+-----------------------------------------------------------------------------+

After the install runs through I start with /kolab/ect/kolab/bootstrap -b
Bootstrapping also runs through without an error message. All ports are 
available. The webadmin page also works, I can create new users and
the synchronization with Outlook over the Toltec connector. But everything
that interacts or uses Horde doesn't work (fbview, Horde webclient, etc.)

How did you get it to work? Did it work "out-of-the-box"? Any hints on 
solving this problem? I would really appreciate your help :-) What 
Debian Etch Version do you use?

Saim



Alex Chejlyk schrieb:
> Hello Saim,
>
> Kolab 2.2rc2 works on Etch. I currently have it installed on three 
> systems (1 bare metal, 2 as VMware Server 1.04 clients) and all is 
> well, including Horde.
>
> Did you build using the binaries or did you build from source?
> Was this a clean install of Etch? Is it a virtual machine or running 
> on bare metal?
>
> Are there any error in the kolab-build.log?
>
> Cheers,
>
> Alex C.
>
> Saim Kim wrote:
>> Hello,
>>
>> since I couldn't get Kolab 2.2 rc 2 with Horde not to work  on my 
>> Etch system I tried to step down to Kolab 2.1 release version. 
>> Strange thing is, that I have to reenter a password for every newly 
>> compiled package. This takes a long time. I used the "# sh obmtool 
>> kolab 2>&1 | tee kolab-build.log" command as described in the readme 
>> of the sources.
>>
>> Now, I'm quite unsure if I should rather spend my time to check if 
>> the Kolab 2.1 release version works or better spend some time to get 
>> the Kolab 2.2 rc with Horde to run on the Etch system? It would be 
>> really great if the Etch users out there could help me out here :-)
>>
>> Greets,
>> Saim
>>
>
>


-- 
--------------------------------------------------------------------------
Dipl.-Ing. Saim Kim
Lehrstuhl fuer Medizinische Informationstechnik
Helmholtz-Institut fuer Biomedizinische Technik
RWTH Aachen
Pauwelsstr. 20, D-52074 Aachen
---
Web:   http://www.medit.hia.rwth-aachen.de/
Tel:   +49-(0)241-80 23218
Fax:   +49-(0)241-80 82442
email: s.kim at hia.rwth-aachen.de
--------------------------------------------------------------------------