From yugm6161 at yahoo.com  Tue Jul  1 05:43:37 2008
From: yugm6161 at yahoo.com (Paul Franklin)
Date: Mon, 30 Jun 2008 20:43:37 -0700 (PDT)
Subject: Fw: Zero emails again
Message-ID: <349415.4583.qm@web59316.mail.re1.yahoo.com>

Alain,Thanks again for your tutorial. ?I have now had opportunity to put it into practice. ?I did not get very far in the process, however, before I discovered a sign of what is wrong. ?I just don't know what to do with the sign.This morning mail delivery stopped at around 10:30. ?The postfix log shows messages such asJun 30 20:23:26 exchange <info> postfix/pipe[20064]: 52F63384220: to=<yugm6161 at yahoo.com>, relay=kolabfilter, delay=0, status=sent (exchange.yugm.org)
Jun 30 20:23:26 exchange <info> postfix/qmgr[3142]: 5B0DC384230: to=<yugm6161 at yahoo.com>, relay=none, delay=0, status=deferred (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]: Connection refused)

I grepped for "temporarily" and discovered that when the mail first stopped, a typical log entry was?
Jun 30
 10:31:22 exchange <info> postfix/qmgr[3142]: 64EBF457B7C: to=<archive at yugm.org>, relay=none, delay=703, status=deferred (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]: read timeout)

I'm going to reboot my kolab box since that is what seemed to do the job last time. ?I would like, however, to figure out what is causing this occasional problem. ?Given this information, where would you look next?
--Paul


      


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20080630/714df1fa/attachment.html

From yugm6161 at yahoo.com  Tue Jul  1 06:17:55 2008
From: yugm6161 at yahoo.com (Paul Franklin)
Date: Mon, 30 Jun 2008 21:17:55 -0700 (PDT)
Subject: Zero emails again
In-Reply-To: <349415.4583.qm@web59316.mail.re1.yahoo.com>
Message-ID: <776549.50543.qm@web59305.mail.re1.yahoo.com>

I have rebooted the box, and things look to be happening again ?The log is not showing any temporary suspensions since the reboot.I have an inkling of the proximate cause, but I don't think a properly-set-up ?install should do this. ?This morning, somewhere around the time the mail stopped being delivered, I issued the command/kolab/bin/openpkg rc all restartwhen what I intended to issue was/kolab/bin/openpkg rc amavisd restart.And I recently--within the past two months--added a backup which includes an rc all stop and an rc all start. ?This backup routine runs nightly. ?I looked back in the log and found that it experienced some read timeouts during the night about the time it would have done the backup.Having the backup is important, but if it is causing occasional outages, I need to change something.--Paul

--- On Mon, 6/30/08, Paul Franklin <yugm6161 at yahoo.com> wrote:
Alain,Thanks again for your tutorial. ?I have now had opportunity to put it into practice. ?I did not get very far in the process, however, before I discovered a sign of what is wrong. ?I just don't know what to do with the sign.This morning mail delivery stopped at around 10:30. ?The postfix log shows messages such asJun 30 20:23:26 exchange <info> postfix/pipe[20064]: 52F63384220: to=<yugm6161 at yahoo.com>, relay=kolabfilter, delay=0, status=sent (exchange.yugm.org)
Jun 30 20:23:26 exchange <info> postfix/qmgr[3142]: 5B0DC384230: to=<yugm6161 at yahoo.com>, relay=none, delay=0, status=deferred (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]: Connection refused)

I grepped
 for "temporarily" and discovered that when the mail first stopped, a typical log entry was?
Jun 30
 10:31:22 exchange <info> postfix/qmgr[3142]: 64EBF457B7C: to=<archive at yugm.org>, relay=none, delay=703, status=deferred (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]: read timeout)

I'm going to reboot my kolab box since that is what seemed to do the job last time. ?I would like, however, to figure out what is causing this occasional problem. ?Given this information, where would you look next?
--Paul


      




      _______________________________________________
Kolab-users mailing list
Kolab-users at kolab.org
https://kolab.org/mailman/listinfo/kolab-users


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20080630/996f625f/attachment.html

From wrobel at pardus.de  Tue Jul  1 16:30:10 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Tue, 01 Jul 2008 16:30:10 +0200
Subject: Fw: Zero emails again
In-Reply-To: <349415.4583.qm@web59316.mail.re1.yahoo.com> (Paul Franklin's
	message of "Mon, 30 Jun 2008 20:43:37 -0700 (PDT)")
References: <349415.4583.qm@web59316.mail.re1.yahoo.com>
Message-ID: <87tzf9pthp.fsf@home.pardus.de>

Paul Franklin <yugm6161 at yahoo.com> writes:

> Alain,                                                                                                                                                                           
> Thanks again for your tutorial. ?I have now had opportunity to put it into practice. ?I did not get very far in the process, however, before I discovered a sign of what is      
> wrong. ?I just don't know what to do with the sign.                                                                                                                              
>                                                                                                                                                                                  
> This morning mail delivery stopped at around 10:30. ?The postfix log shows messages such as                                                                                      
>                                                                                                                                                                                  
> Jun 30 20:23:26 exchange <info> postfix/pipe[20064]: 52F63384220: to=<yugm6161 at yahoo.com>, relay=kolabfilter, delay=0, status=sent (exchange.yugm.org)                           
> Jun 30 20:23:26 exchange <info> postfix/qmgr[3142]: 5B0DC384230: to=<yugm6161 at yahoo.com>, relay=none, delay=0, status=deferred (delivery temporarily suspended: connect to       
> 127.0.0.1[127.0.0.1]: Connection refused)                                                                                                                                        
>                                                                                                                                                                                  
> I grepped for "temporarily" and discovered that when the mail first stopped, a typical log entry was?                                                                            
>                                                                                                                                                                                  
> Jun 30 10:31:22 exchange <info> postfix/qmgr[3142]: 64EBF457B7C: to=<archive at yugm.org>, relay=none, delay=703, status=deferred (delivery temporarily suspended: connect to       
> 127.0.0.1[127.0.0.1]: read timeout)                                                                                                                                              
>                                                                                                                                                                                  
> I'm going to reboot my kolab box since that is what seemed to do the
> job last time. ?I would like, however, to figure out what is causing
> this occasional problem. ?Given this information, where would you
> look next?

Looks like your amavisd-new process is failing here. You should be
able to restart it with

/kolab/bin/openpkg rc amavisd

On the other hand it should not be failing in the first place. Do you
see anything in the amavisd logs?

Cheers,

Gunnar

>                                                                                                                                                                                  
> --Paul                                                                                                                                                                           
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From wrobel at pardus.de  Tue Jul  1 16:31:36 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Tue, 01 Jul 2008 16:31:36 +0200
Subject: Fehler bei der Erstellung von Benutzerkonten
In-Reply-To: <002101c8dab9$cbfb0610$270119ac@cargopack.local> (Martin Mach's
	message of "Mon, 30 Jun 2008 16:01:09 +0200")
References: <002101c8dab9$cbfb0610$270119ac@cargopack.local>
Message-ID: <87prpxptfb.fsf@home.pardus.de>

Hallo Martin,

"Martin Mach" <martin.mach at cargopack.de> writes:

> Hallo,
>
> ich habe hier folgendes Problem: Neulich waren Elektriker im Haus. Die haben
> dem Mailserver kurz den Netzstrom abgestellt (E-Check!). Der Server ging
> also aus und fuhr anschlie?end selbstst?ndig wieder hoch. Seitdem passiert
> aber folgendes: Ich lege einen neuen Benutzer an, dieser erscheint auch
> unter "Benutzer", ein Verzeichnis unter
> /kolab/var/imapd/spool/domain/cargopack.local/user/ wird aber nicht
> angelegt, weder POP noch IMAP kennen den neuen User. Alle anderen k?nnen
> ohne Problem auf ihre POP-Mailbox und die IMAP-Ordner (via Toltec+Outlook)
> zugreifen.
> Was funktioniert hier nicht?

Vermutlich l?uft der kolabd-Prozess nicht.

Neu starten mit

/kolab/bin/openpkg rc kolabd stop
/kolab/bin/openpkg rc kolabd start

Falls das nicht hilft (die Prozesstabelle sollte nach dem Start zwei
laufende kolabd Prozesse zeigen) im syslog nach Fehlern suchen.

Gru?,

Gunnar

>
> Server ist Kolab 2.1 auf Suse 9.1
>
> Martin
>
> -- 
>
> Martin Mach
> Str UV CI
> Koerschtalstrasse 100
> 73770 Denkendorf
>
> Phone +49(0)711 954610 18
> Fax +49(0)711 954610 23
> Mobile +49(0)173 4462358
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From mike at rochestervball.com  Tue Jul  1 16:56:01 2008
From: mike at rochestervball.com (Michael Harnden)
Date: Tue, 01 Jul 2008 10:56:01 -0400
Subject: Problems installing on openSuse 11.0
Message-ID: <486A4581.6060601@rochestervball.com>

Try to install the latest release version on openSuse 11.0.

My openpkg install fails due to perl failing to install. I found this - 
http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_Compiling#Perl_fails_to_build:_.2Fkolab.2Fbin.2Fperl:_bad_interpreter:_no_such_file_or_directory 
- but it doesn't seem to apply.

The install log at point of failure is:
SysV.xs.7:25: error asm/page.h: No such file or directory
make[1]: *** [SysV.o] Error 1
make : *** [lib/auto/IPC/SysV/SysV.so] Error 2
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.18960 (%build)

RPM build errors:
     Bad exit status from /kolab/RPM/TMP/rpm-tmp.18960 (%build)
]0;basement-server:/tmp/obmtool.21292
obmtool:WARNING: install failure, Missing 
/kolab/RPM/PKG/perl-5.8.7-2.5.1.ix86-suse11.0-kolab.rpm

Then after that numerous things fail due to a lack of perl.

Any suggestions?
Thanks,
Mike


From wrobel at pardus.de  Tue Jul  1 17:08:45 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Tue, 01 Jul 2008 17:08:45 +0200
Subject: Problems installing on openSuse 11.0
In-Reply-To: <486A4581.6060601@rochestervball.com> (Michael Harnden's message
	of "Tue, 01 Jul 2008 10:56:01 -0400")
References: <486A4581.6060601@rochestervball.com>
Message-ID: <87ej6dmyki.fsf@home.pardus.de>

Hi Micheal,

Michael Harnden <mike at rochestervball.com> writes:

> Try to install the latest release version on openSuse 11.0.

You mean the 2.1 release?

>
> My openpkg install fails due to perl failing to install. I found this - 
> http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_Compiling#Perl_fails_to_build:_.2Fkolab.2Fbin.2Fperl:_bad_interpreter:_no_such_file_or_directory 
> - but it doesn't seem to apply.
>
> The install log at point of failure is:
> SysV.xs.7:25: error asm/page.h: No such file or directory

I think this file has been removed on newer systems. I remeber seeing
that once on Gentoo but I don't remeber exactly if there was something
I was able to do about it. You'll find many comments if you google for
that error.

You might wish to try the newer Kolab server release candidates unless
somebody comes up with a better solution :)

Cheers,

Gunnar

> make[1]: *** [SysV.o] Error 1
> make : *** [lib/auto/IPC/SysV/SysV.so] Error 2
> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.18960 (%build)
>
> RPM build errors:
>      Bad exit status from /kolab/RPM/TMP/rpm-tmp.18960 (%build)
> ]0;basement-server:/tmp/obmtool.21292
> obmtool:WARNING: install failure, Missing 
> /kolab/RPM/PKG/perl-5.8.7-2.5.1.ix86-suse11.0-kolab.rpm
>
> Then after that numerous things fail due to a lack of perl.
>
> Any suggestions?
> Thanks,
> Mike
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From martin.mach at cargopack.de  Tue Jul  1 17:10:22 2008
From: martin.mach at cargopack.de (Martin Mach)
Date: Tue, 1 Jul 2008 17:10:22 +0200
Subject: Fehler bei der Erstellung von Benutzerkonten
In-Reply-To: <87prpxptfb.fsf@home.pardus.de>
Message-ID: <004c01c8db8c$a1887c40$270119ac@cargopack.local>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tats?chlich. Offenbar ein Fehler beim Start aller Dienste.

besten Dank.

- -- 

Martin Mach
Str UV CI
Koerschtalstrasse 100
73770 Denkendorf

Phone +49(0)711 954610 18
Fax +49(0)711 954610 23
Mobile +49(0)173 4462358 

> -----Original Message-----
> From: kolab-users-bounces at kolab.org 
> [mailto:kolab-users-bounces at kolab.org] On Behalf Of Gunnar Wrobel
> Sent: Tuesday, July 01, 2008 4:32 PM
> To: martin.mach at cargopack.de
> Cc: Kolab-users at kolab.org
> Subject: Re: Fehler bei der Erstellung von Benutzerkonten
> 
> Hallo Martin,
> 
> "Martin Mach" <martin.mach at cargopack.de> writes:
> 
> > Hallo,
> >
> > ich habe hier folgendes Problem: Neulich waren Elektriker 
> im Haus. Die 
> > haben dem Mailserver kurz den Netzstrom abgestellt (E-Check!). Der 
> > Server ging also aus und fuhr anschlie?end selbstst?ndig 
> wieder hoch. 
> > Seitdem passiert aber folgendes: Ich lege einen neuen Benutzer an, 
> > dieser erscheint auch unter "Benutzer", ein Verzeichnis unter 
> > /kolab/var/imapd/spool/domain/cargopack.local/user/ wird aber nicht 
> > angelegt, weder POP noch IMAP kennen den neuen User. Alle anderen 
> > k?nnen ohne Problem auf ihre POP-Mailbox und die IMAP-Ordner (via 
> > Toltec+Outlook) zugreifen.
> > Was funktioniert hier nicht?
> 
> Vermutlich l?uft der kolabd-Prozess nicht.
> 
> Neu starten mit
> 
> /kolab/bin/openpkg rc kolabd stop
> /kolab/bin/openpkg rc kolabd start
> 
> Falls das nicht hilft (die Prozesstabelle sollte nach dem 
> Start zwei laufende kolabd Prozesse zeigen) im syslog nach 
> Fehlern suchen.
> 
> Gru?,
> 
> Gunnar
> 
> >
> > Server ist Kolab 2.1 auf Suse 9.1
> >
> > Martin
> >
> > --
> >
> > Martin Mach
> > Str UV CI
> > Koerschtalstrasse 100
> > 73770 Denkendorf
> >
> > Phone +49(0)711 954610 18
> > Fax +49(0)711 954610 23
> > Mobile +49(0)173 4462358
> >
> > _______________________________________________
> > Kolab-users mailing list
> > Kolab-users at kolab.org
> > https://kolab.org/mailman/listinfo/kolab-users
> 
> --
> ______ http://kdab.com _______________ http://kolab-konsortium.com _
> 
> p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
> 
> ____ http://www.pardus.de _________________ http://gunnarwrobel.de _
> E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
> Tel.   : +49 700 6245 0000                          Bundesstrasse 29
> Fax    : +49 721 1513 52322                          D-20146 Hamburg
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>    >> Mail at ease - Rent a kolab groupware server at p at rdus 
> <<                 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)

iQEVAwUBSGpI3bO82i/nlpjDAQIZZQgAzhQM5wOpZN/UzZfdLoWjIIo6Xa5p2hsI
Uo//NRo8ZBEIxegfsfNfl32MYyNYExaKFxrzmiMwU85SubaCMd5d83BH49ABAmlN
5A28GN8ohcIp36v/CC5ucuvskLqJQ0x98qVCeDaS86AjgTip9pLzCscF0R/AokFY
Md99COAgIDyQS1Z4WQz9vRQw1VxRF+kmOy8cepA9yurb29WCs4L6QAX1G6WLSV1D
l9O/E5XcB8F5hMTQHY0/xQSa/J/WqLGQCL+Yh75HR2eoYc2mT/GmdOBAvisZlrIr
XIdZhbBbLYHEmk0ixWQqJLBnpyyBiFOpDOUCp3jeWjRPGRTlgCxoTg==
=2wX9
-----END PGP SIGNATURE-----


From pdf at yugm.org  Tue Jul  1 19:42:18 2008
From: pdf at yugm.org (Paul Douglas Franklin)
Date: Tue, 01 Jul 2008 10:42:18 -0700
Subject: Fw: Zero emails again
In-Reply-To: <87tzf9pthp.fsf@home.pardus.de>
References: <349415.4583.qm@web59316.mail.re1.yahoo.com>
	<87tzf9pthp.fsf@home.pardus.de>
Message-ID: <486A6C7A.1020800@yugm.org>

Gunnar Wrobel wrote:
> Paul Franklin <yugm6161 at yahoo.com> writes:
>
>   
>> Alain,                                                                                                                                                                           
>> Thanks again for your tutorial.  I have now had opportunity to put it into practice.  I did not get very far in the process, however, before I discovered a sign of what is      
>> wrong.  I just don't know what to do with the sign.                                                                                                                              
>>                                                                                                                                                                                  
>> This morning mail delivery stopped at around 10:30.  The postfix log shows messages such as                                                                                      
>>                                                                                                                                                                                  
>> Jun 30 20:23:26 exchange <info> postfix/pipe[20064]: 52F63384220: to=<yugm6161 at yahoo.com>, relay=kolabfilter, delay=0, status=sent (exchange.yugm.org)                           
>> Jun 30 20:23:26 exchange <info> postfix/qmgr[3142]: 5B0DC384230: to=<yugm6161 at yahoo.com>, relay=none, delay=0, status=deferred (delivery temporarily suspended: connect to       
>> 127.0.0.1[127.0.0.1]: Connection refused)                                                                                                                                        
>>                                                                                                                                                                                  
>> I grepped for "temporarily" and discovered that when the mail first stopped, a typical log entry was                                                                             
>>                                                                                                                                                                                  
>> Jun 30 10:31:22 exchange <info> postfix/qmgr[3142]: 64EBF457B7C: to=<archive at yugm.org>, relay=none, delay=703, status=deferred (delivery temporarily suspended: connect to       
>> 127.0.0.1[127.0.0.1]: read timeout)                                                                                                                                              
>>                                                                                                                                                                                  
>> I'm going to reboot my kolab box since that is what seemed to do the
>> job last time.  I would like, however, to figure out what is causing
>> this occasional problem.  Given this information, where would you
>> look next?
>>     
>
> Looks like your amavisd-new process is failing here. You should be
> able to restart it with
>
> /kolab/bin/openpkg rc amavisd
>
> On the other hand it should not be failing in the first place. Do you
> see anything in the amavisd logs?
>
>   
I see some things.
At 10:10:07 I issued the /kolab/bin/openpkg rc all restart command.  It 
went thru quite a process, finishing at 10:10:44.  (More about that 
later.)  Then, at 10:11:52, I issued the /kolab/bin/openpkg rc amavisd 
restart command (just to get it moved into my recent history--I knew 
amavisd was included in all).  It was at this point that problems 
happened, but without any indication of why.  There are exactly two 
lines in the log here:

Jun 30 10:11:52 exchange.yugm.org /kolab/sbin/amavisd[4330]: starting.  /kolab/sbin/amavisd at exchange.yugm.org amavisd-new-2.3.3 (20050822), Unicode aware, LANG=en_US.UTF-8
Jun 30 10:11:52 exchange.yugm.org /kolab/sbin/amavisd[4330]: Perl version               5.008007

The next entry wasn't until I rebooted at 20:52.  So it does appear that 
amavisd didn't load, but it doesn't say why.

There is another thing that I see that causes me concern.  Toward the 
end of the restart, it appears that clam fails.

Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .rar  tried: rar, unrar
Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .arj  tried: arj, unarj
Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .arc  tried: nomarch, arc
Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .zoo  tried: zoo
Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .lha  tried: lha
Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .doc 
Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .cab 
Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .tnef
Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: Internal decoder for .tnef
Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .exe  tried: rar, unrar; lha; arj, unarj
Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: Using internal av scanner code for (primary) Clam Antivirus-clamd
Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: Found secondary av scanner Clam Antivirus - /kolab/bin/clamscan at /kolab/bin/clamscan
Jun 30 20:52:16 exchange.yugm.org /kolab/sbin/amavisd[5359]: (05359-01) Clam Antivirus-clamd: Can't connect to UNIX socket /kolab/var/clamav/clamd.sock: No such file or directory, retrying (2)
Jun 30 20:52:16 exchange.yugm.org /kolab/sbin/amavisd[5360]: (05360-01) Clam Antivirus-clamd: Can't connect to UNIX socket /kolab/var/clamav/clamd.sock: No such file or directory, retrying (2)
Jun 30 20:52:22 exchange.yugm.org /kolab/sbin/amavisd[5359]: (05359-01) Clam Antivirus-clamd av-scanner FAILED: Too many retries to talk to /kolab/var/clamav/clamd.sock (Can't connect to UNIX socket /kolab/var/clamav/clamd.sock: No such file or directory) at (eval 55) line 266.
Jun 30 20:52:22 exchange.yugm.org /kolab/sbin/amavisd[5359]: (05359-01) WARN: all primary virus scanners failed, considering backups
Jun 30 20:52:22 exchange.yugm.org /kolab/sbin/amavisd[5360]: (05360-01) Clam Antivirus-clamd av-scanner FAILED: Too many retries to talk to /kolab/var/clamav/clamd.sock (Can't connect to UNIX socket /kolab/var/clamav/clamd.sock: No such file or directory) at (eval 55) line 266.
Jun 30 20:52:22 exchange.yugm.org /kolab/sbin/amavisd[5360]: (05360-01) WARN: all primary virus scanners failed, considering backups

Looking at the clamav log, I see that it started at 20:52:09.
Is this indeed saying that I have no antivirus protection?
--Paul

> Cheers,
>
> Gunnar
>   
>
-- 
Paul Douglas Franklin
Computer Manager, Union Gospel Mission of Yakima, Washington
Husband of Danette
Father of Laurene, Miriam, Tycko, Timothy, Sarabeth, Marie, Dawnita, Anna Leah, Alexander, and Caleb


From mike at rochestervball.com  Wed Jul  2 03:03:30 2008
From: mike at rochestervball.com (Michael Harnden)
Date: Tue, 01 Jul 2008 21:03:30 -0400
Subject: Problems installing on openSuse 11.0
In-Reply-To: <87ej6dmyki.fsf@home.pardus.de>
References: <486A4581.6060601@rochestervball.com>
	<87ej6dmyki.fsf@home.pardus.de>
Message-ID: <486AD3E2.2030802@rochestervball.com>

Gunnar Wrobel wrote:
> Hi Micheal,
>
> Michael Harnden <mike at rochestervball.com> writes:
>
>   
>> Try to install the latest release version on openSuse 11.0.
>>     
>
> You mean the 2.1 release?
>   
Yes, I forgot that detail, 2.1 release.

>> My openpkg install fails due to perl failing to install. I found this - 
>> http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_Compiling#Perl_fails_to_build:_.2Fkolab.2Fbin.2Fperl:_bad_interpreter:_no_such_file_or_directory 
>> - but it doesn't seem to apply.
>>
>> The install log at point of failure is:
>> SysV.xs.7:25: error asm/page.h: No such file or directory
>>     
>
> I think this file has been removed on newer systems. I remeber seeing
> that once on Gentoo but I don't remeber exactly if there was something
> I was able to do about it. You'll find many comments if you google for
> that error.
>   
You are correct on that one. I searched my system and couldn't find it. 
I had to install my kernel sources then linked 
/usr/src/linux/include/asm-generic/page.h to /usr/include/asm/. The 
installation is running as I type, but it has made it past the previous 
error, so I think I am good.

Thank you for the assistance,
Mike


From eberlein at vw.htw-aalen.de  Wed Jul  2 13:53:39 2008
From: eberlein at vw.htw-aalen.de (Till Eberlein)
Date: Wed, 02 Jul 2008 13:53:39 +0200
Subject: Swapfile
Message-ID: <486B6C43.2090903@vw.htw-aalen.de>

Hallo Zusammen

Vielleicht hat jemand eine Idee oder sogar eine L?sung f?r folgendes 
Problem:

Kolab 2.2 rc2, Opensuse 10.2, 2GB Arbeitsspeicher (wenig, aber es geht 
nicht mehr), 4GB Swap.

Nach sp?testens drei bis vier Tagen normalem Betrieb laufen die 
Swap-Files voll, es bringt auch nichts den Swap zu vergr?ssern, der 
l?uft dann nach kurzer Zeit auch voll. Ein Neustart des Apache l?st das 
Problem (der Swap wird wieder freigegeben), aber nach einigen Tagen habe 
ich wieder das gleiche Szenario. Es liegt nachvollziehbar am Apache, 
obwohl dieser kaum genutzt wird. Maximal zur Administration und hin und 
wieder einmal ein Zugriff per Horde.
Freebusy wird zwar genutzt, aber maximal von 5 Usern.

Im Voraus schon mal Danke

-- 

Mit freundlichen Gr?ssen


Till Eberlein


From christian.tardif at servinfo.ca  Thu Jul  3 05:25:36 2008
From: christian.tardif at servinfo.ca (Christian Tardif)
Date: Wed, 02 Jul 2008 23:25:36 -0400
Subject: Kolab and SpamAssassin
Message-ID: <20080702232536.697940pxqo9s1cqo@ambrosia.servinfo.ca>

I have latest Kolab installed and working. But it seems (no...  it IS)  
very less accurate in filtering spam than my previous  
postfix/cyrus-imap/amavisd setup, and the config seems very similar. I  
get many messages that have no testing done at all.

Where do I start looking at?

-- 
Christian Tardif


From wrobel at pardus.de  Thu Jul  3 06:58:47 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 03 Jul 2008 06:58:47 +0200
Subject: Fw: Zero emails again
In-Reply-To: <486A6C7A.1020800@yugm.org> (Paul Douglas Franklin's message of
	"Tue, 01 Jul 2008 10:42:18 -0700")
References: <349415.4583.qm@web59316.mail.re1.yahoo.com>
	<87tzf9pthp.fsf@home.pardus.de> <486A6C7A.1020800@yugm.org>
Message-ID: <87od5fk1h4.fsf@home.pardus.de>

Paul Douglas Franklin <pdf at yugm.org> writes:

> Gunnar Wrobel wrote:
>> Paul Franklin <yugm6161 at yahoo.com> writes:
>>
>>   
>>> Alain,                                                                                                                                                                           
>>> Thanks again for your tutorial.  I have now had opportunity to put it into practice.  I did not get very far in the process, however, before I discovered a sign of what is      
>>> wrong.  I just don't know what to do with the sign.                                                                                                                              
>>>                                                                                                                                                                                  
>>> This morning mail delivery stopped at around 10:30.  The postfix log shows messages such as                                                                                      
>>>                                                                                                                                                                                  
>>> Jun 30 20:23:26 exchange <info> postfix/pipe[20064]: 52F63384220: to=<yugm6161 at yahoo.com>, relay=kolabfilter, delay=0, status=sent (exchange.yugm.org)                           
>>> Jun 30 20:23:26 exchange <info> postfix/qmgr[3142]: 5B0DC384230: to=<yugm6161 at yahoo.com>, relay=none, delay=0, status=deferred (delivery temporarily suspended: connect to       
>>> 127.0.0.1[127.0.0.1]: Connection refused)                                                                                                                                        
>>>                                                                                                                                                                                  
>>> I grepped for "temporarily" and discovered that when the mail first stopped, a typical log entry was                                                                             
>>>                                                                                                                                                                                  
>>> Jun 30 10:31:22 exchange <info> postfix/qmgr[3142]: 64EBF457B7C: to=<archive at yugm.org>, relay=none, delay=703, status=deferred (delivery temporarily suspended: connect to       
>>> 127.0.0.1[127.0.0.1]: read timeout)                                                                                                                                              
>>>                                                                                                                                                                                  
>>> I'm going to reboot my kolab box since that is what seemed to do the
>>> job last time.  I would like, however, to figure out what is causing
>>> this occasional problem.  Given this information, where would you
>>> look next?
>>>     
>>
>> Looks like your amavisd-new process is failing here. You should be
>> able to restart it with
>>
>> /kolab/bin/openpkg rc amavisd
>>
>> On the other hand it should not be failing in the first place. Do you
>> see anything in the amavisd logs?
>>
>>   
> I see some things.
> At 10:10:07 I issued the /kolab/bin/openpkg rc all restart command.  It 
> went thru quite a process, finishing at 10:10:44.  (More about that 
> later.)  Then, at 10:11:52, I issued the /kolab/bin/openpkg rc amavisd 
> restart command (just to get it moved into my recent history--I knew 
> amavisd was included in all).  It was at this point that problems 
> happened, but without any indication of why.  There are exactly two 
> lines in the log here:
>
> Jun 30 10:11:52 exchange.yugm.org /kolab/sbin/amavisd[4330]: starting.  /kolab/sbin/amavisd at exchange.yugm.org amavisd-new-2.3.3 (20050822), Unicode aware, LANG=en_US.UTF-8
> Jun 30 10:11:52 exchange.yugm.org /kolab/sbin/amavisd[4330]: Perl version               5.008007
>
> The next entry wasn't until I rebooted at 20:52.  So it does appear that 
> amavisd didn't load, but it doesn't say why.
>
> There is another thing that I see that causes me concern.  Toward the 
> end of the restart, it appears that clam fails.
>
> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .rar  tried: rar, unrar
> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .arj  tried: arj, unarj
> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .arc  tried: nomarch, arc
> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .zoo  tried: zoo
> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .lha  tried: lha
> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .doc 
> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .cab 
> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .tnef
> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: Internal decoder for .tnef
> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .exe  tried: rar, unrar; lha; arj, unarj
> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: Using internal av scanner code for (primary) Clam Antivirus-clamd
> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: Found secondary av scanner Clam Antivirus - /kolab/bin/clamscan at /kolab/bin/clamscan
> Jun 30 20:52:16 exchange.yugm.org /kolab/sbin/amavisd[5359]: (05359-01) Clam Antivirus-clamd: Can't connect to UNIX socket /kolab/var/clamav/clamd.sock: No such file or directory, retrying (2)
> Jun 30 20:52:16 exchange.yugm.org /kolab/sbin/amavisd[5360]: (05360-01) Clam Antivirus-clamd: Can't connect to UNIX socket /kolab/var/clamav/clamd.sock: No such file or directory, retrying (2)
> Jun 30 20:52:22 exchange.yugm.org /kolab/sbin/amavisd[5359]: (05359-01) Clam Antivirus-clamd av-scanner FAILED: Too many retries to talk to /kolab/var/clamav/clamd.sock (Can't connect to UNIX socket /kolab/var/clamav/clamd.sock: No such file or directory) at (eval 55) line 266.
> Jun 30 20:52:22 exchange.yugm.org /kolab/sbin/amavisd[5359]: (05359-01) WARN: all primary virus scanners failed, considering backups
> Jun 30 20:52:22 exchange.yugm.org /kolab/sbin/amavisd[5360]: (05360-01) Clam Antivirus-clamd av-scanner FAILED: Too many retries to talk to /kolab/var/clamav/clamd.sock (Can't connect to UNIX socket /kolab/var/clamav/clamd.sock: No such file or directory) at (eval 55) line 266.
> Jun 30 20:52:22 exchange.yugm.org /kolab/sbin/amavisd[5360]: (05360-01) WARN: all primary virus scanners failed, considering backups
>
> Looking at the clamav log, I see that it started at 20:52:09.
> Is this indeed saying that I have no antivirus protection?

Yes it appears so. The socket file should indicate that clamd is
running. You can also check the process table for the "clamd" process.

You can also try to run clamd manually from the command line using:

/kolab/sbin/clamd --config-file=/kolab/etc/clamav/clamd.conf

The clamd command has a few additional options that might help to
debug the process.

Cheers,

Gunnar

> --Paul
>
>> Cheers,
>>
>> Gunnar
>>   
>>
> -- 
> Paul Douglas Franklin
> Computer Manager, Union Gospel Mission of Yakima, Washington
> Husband of Danette
> Father of Laurene, Miriam, Tycko, Timothy, Sarabeth, Marie, Dawnita, Anna Leah, Alexander, and Caleb
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From wrobel at pardus.de  Thu Jul  3 07:07:58 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 03 Jul 2008 07:07:58 +0200
Subject: Swapfile
In-Reply-To: <486B6C43.2090903@vw.htw-aalen.de> (Till Eberlein's message of
	"Wed, 02 Jul 2008 13:53:39 +0200")
References: <486B6C43.2090903@vw.htw-aalen.de>
Message-ID: <87k5g3k11t.fsf@home.pardus.de>

Till Eberlein <eberlein at vw.htw-aalen.de> writes:

> Hallo Zusammen
>
> Vielleicht hat jemand eine Idee oder sogar eine L?sung f?r folgendes 
> Problem:
>
> Kolab 2.2 rc2, Opensuse 10.2, 2GB Arbeitsspeicher (wenig, aber es geht 
> nicht mehr), 4GB Swap.
>
> Nach sp?testens drei bis vier Tagen normalem Betrieb laufen die 
> Swap-Files voll, es bringt auch nichts den Swap zu vergr?ssern, der 
> l?uft dann nach kurzer Zeit auch voll. Ein Neustart des Apache l?st das 
> Problem (der Swap wird wieder freigegeben), aber nach einigen Tagen habe 
> ich wieder das gleiche Szenario. Es liegt nachvollziehbar am Apache, 
> obwohl dieser kaum genutzt wird. Maximal zur Administration und hin und 
> wieder einmal ein Zugriff per Horde.
> Freebusy wird zwar genutzt, aber maximal von 5 Usern.
>
> Im Voraus schon mal Danke

In der Apache-2.2.9-Version wurde zumindest ein memory leak
korrigiert, das relevant sein k?nnte:

https://issues.apache.org/bugzilla/show_bug.cgi?id=44975

Dort ist ein Test beschrieben, den man vielleicht durchf?hren k?nnte.

Von Deiner Beschreibung her vermute ich auf jeden Fall eher ein
generelles Apache-Problem.

L?sst sich ?berpr?fen, welche Seitenaufrufe den Speicherbedarf des
Apache erh?hen? Also z.B. durch mehrfaches Aufrufen nur einer der
installierten Web-Applikationen?

Gru?,

Gunnar

>
> -- 
>
> Mit freundlichen Gr?ssen
>
>
> Till Eberlein
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From wrobel at pardus.de  Thu Jul  3 07:09:42 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 03 Jul 2008 07:09:42 +0200
Subject: Kolab and SpamAssassin
In-Reply-To: <20080702232536.697940pxqo9s1cqo@ambrosia.servinfo.ca> (Christian
	Tardif's message of "Wed, 02 Jul 2008 23:25:36 -0400")
References: <20080702232536.697940pxqo9s1cqo@ambrosia.servinfo.ca>
Message-ID: <87fxqrk0yx.fsf@home.pardus.de>

Christian Tardif <christian.tardif at servinfo.ca> writes:

> I have latest Kolab installed and working. But it seems (no...  it IS)  
> very less accurate in filtering spam than my previous  
> postfix/cyrus-imap/amavisd setup, and the config seems very similar. I  
> get many messages that have no testing done at all.

Similar probably does not mean the same. And even small changes could
change a great deal. The Kolab server does not activate non-local
tests by default. You could check if activating them changes anything.

Cheers,

Gunnar

>
> Where do I start looking at?
>
> -- 
> Christian Tardif
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From jens at codes-concepts.com  Thu Jul  3 12:57:00 2008
From: jens at codes-concepts.com (Jens Kleikamp)
Date: Thu, 03 Jul 2008 12:57:00 +0200
Subject: Kolab and SpamAssassin
In-Reply-To: <20080702232536.697940pxqo9s1cqo@ambrosia.servinfo.ca>
References: <20080702232536.697940pxqo9s1cqo@ambrosia.servinfo.ca>
Message-ID: <486CB07C.3030004@codes-concepts.com>

Christian Tardif schrieb:
> I have latest Kolab installed and working. But it seems (no...  it IS)  
> very less accurate in filtering spam than my previous  
> postfix/cyrus-imap/amavisd setup, and the config seems very similar. I  
> get many messages that have no testing done at all.
> 
> Where do I start looking at?
> 
Another point is that after a fresh install your bayes db does not
contain enough messages to do its job. It requires a mininum of 200 spam
and ham messages.

You could also install Pyzor, Razor and DCC to improve SA. (see the wiki
for more information)

I additionally use some advanced rulesets and update them regulary using
sa-update. Here is my channel file:

------
updates.spamassassin.org
saupdates.openprotect.com
sought.rules.yerp.org
70_sare_stocks.cf.sare.sa-update.dostech.net
70_sare_adult.cf.sare.sa-update.dostech.net
70_sare_spoof.cf.sare.sa-update.dostech.net
70_sare_bayes_poison_nxm.cf.sare.sa-update.dostech.net
70_sare_genlsubj_x30.cf.sare.sa-update.dostech.net
70_sare_oem.cf.sare.sa-update.dostech.net
70_sare_random.cf.sare.sa-update.dostech.net
70_sare_specific.cf.sare.sa-update.dostech.net
70_zmi_german.cf.zmi.sa-update.dostech.net
88_FVGT_Bayes_Poison.cf.sare.sa-update.dostech.net
88_FVGT_Tripwire.cf.sare.sa-update.dostech.net
88_FVGT_rawbody.cf.sare.sa-update.dostech.net
88_FVGT_subject.cf.sare.sa-update.dostech.net
chickenpox.cf.sare.sa-update.dostech.net
-------


The SPF plugin is also not that bad, at least with appropriate score values.



From eberlein at vw.htw-aalen.de  Thu Jul  3 14:51:38 2008
From: eberlein at vw.htw-aalen.de (Till Eberlein)
Date: Thu, 03 Jul 2008 14:51:38 +0200
Subject: Swapfile
In-Reply-To: <87k5g3k11t.fsf@home.pardus.de>
References: <486B6C43.2090903@vw.htw-aalen.de> <87k5g3k11t.fsf@home.pardus.de>
Message-ID: <486CCB5A.7040208@vw.htw-aalen.de>

Nochmal Hallo

Ist das bekannte Apache-Problem in der RC3 noch von Bestand, oder ist 
dort  schon eine entsprechend korrigierte Version enthalten? Denn dann 
macht es ja eher Sinn die RC3 zu installieren als Apache zu patchen.

Was ist denn eher zu empfehlen bei einem Upgrade (ich habe bis jetzt nur 
  einige Neuinstallationen hinter mir): Neuer kolabtemp-Ordner und dort 
die ...since...Dateien herunterladen und dann kolab-install ausf?hren 
oder die ....since.... Dateien direkt ins RC2-kolabtemp-Verzeichnis 
laden und dann die aktuelle kolab-install ausf?hren?

Hat schon jemand hoffentlich gute oder eventuell auch schlechte 
Erfahrungen bei einem Upgrade von RC2 auf RC3?


Mit freundlichen Gr?ssen


Till Eberlein



Gunnar Wrobel schrieb:
> Till Eberlein <eberlein at vw.htw-aalen.de> writes:
> 
>> Hallo Zusammen
>>
>> Vielleicht hat jemand eine Idee oder sogar eine L?sung f?r folgendes 
>> Problem:
>>
>> Kolab 2.2 rc2, Opensuse 10.2, 2GB Arbeitsspeicher (wenig, aber es geht 
>> nicht mehr), 4GB Swap.
>>
>> Nach sp?testens drei bis vier Tagen normalem Betrieb laufen die 
>> Swap-Files voll, es bringt auch nichts den Swap zu vergr?ssern, der 
>> l?uft dann nach kurzer Zeit auch voll. Ein Neustart des Apache l?st das 
>> Problem (der Swap wird wieder freigegeben), aber nach einigen Tagen habe 
>> ich wieder das gleiche Szenario. Es liegt nachvollziehbar am Apache, 
>> obwohl dieser kaum genutzt wird. Maximal zur Administration und hin und 
>> wieder einmal ein Zugriff per Horde.
>> Freebusy wird zwar genutzt, aber maximal von 5 Usern.
>>
>> Im Voraus schon mal Danke
> 
> In der Apache-2.2.9-Version wurde zumindest ein memory leak
> korrigiert, das relevant sein k?nnte:
> 
> https://issues.apache.org/bugzilla/show_bug.cgi?id=44975
> 
> Dort ist ein Test beschrieben, den man vielleicht durchf?hren k?nnte.
> 
> Von Deiner Beschreibung her vermute ich auf jeden Fall eher ein
> generelles Apache-Problem.
> 
> L?sst sich ?berpr?fen, welche Seitenaufrufe den Speicherbedarf des
> Apache erh?hen? Also z.B. durch mehrfaches Aufrufen nur einer der
> installierten Web-Applikationen?
> 
> Gru?,
> 
> Gunnar
> 
>> -- 
>>
>> Mit freundlichen Gr?ssen
>>
>>
>> Till Eberlein
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
> 


From jens at codes-concepts.com  Thu Jul  3 14:58:14 2008
From: jens at codes-concepts.com (Jens Kleikamp)
Date: Thu, 03 Jul 2008 14:58:14 +0200
Subject: Swapfile
In-Reply-To: <486CCB5A.7040208@vw.htw-aalen.de>
References: <486B6C43.2090903@vw.htw-aalen.de> <87k5g3k11t.fsf@home.pardus.de>
	<486CCB5A.7040208@vw.htw-aalen.de>
Message-ID: <486CCCE6.4010902@codes-concepts.com>

Till Eberlein schrieb:
> Nochmal Hallo
> 
> ...
> 
> Hat schon jemand hoffentlich gute oder eventuell auch schlechte 
> Erfahrungen bei einem Upgrade von RC2 auf RC3?
> 

Bei mir hat es astrein geklappt.
Hatte aber keine Probleme mit dem Apache in rc2.

Gru?
Jens


From jens at codes-concepts.com  Thu Jul  3 16:21:27 2008
From: jens at codes-concepts.com (Jens Kleikamp)
Date: Thu, 03 Jul 2008 16:21:27 +0200
Subject: Kolab and SpamAssassin
In-Reply-To: <20080702232536.697940pxqo9s1cqo@ambrosia.servinfo.ca>
References: <20080702232536.697940pxqo9s1cqo@ambrosia.servinfo.ca>
Message-ID: <g4in8d$34j$1@ger.gmane.org>

Christian Tardif schrieb:
> I have latest Kolab installed and working. But it seems (no...  it IS)  
> very less accurate in filtering spam than my previous  
> postfix/cyrus-imap/amavisd setup, and the config seems very similar. I  
> get many messages that have no testing done at all.
> 
> Where do I start looking at?
> 

You should also improve clamav with additional phishing&scam databases:
http://www.sanesecurity.com/clamav/usage.htm


Another good way to improve the spam protection of kolab is to enhance
the default postfix configuration. I like the following document:
http://jimsun.linxnet.com/misc/postfix-anti-UCE.txt


From pdf at yugm.org  Thu Jul  3 19:32:39 2008
From: pdf at yugm.org (Paul Douglas Franklin)
Date: Thu, 03 Jul 2008 10:32:39 -0700
Subject: Fw: Zero emails again
In-Reply-To: <87od5fk1h4.fsf@home.pardus.de>
References: <349415.4583.qm@web59316.mail.re1.yahoo.com>	<87tzf9pthp.fsf@home.pardus.de>
	<486A6C7A.1020800@yugm.org> <87od5fk1h4.fsf@home.pardus.de>
Message-ID: <486D0D37.9060306@yugm.org>

Gunnar Wrobel wrote:
> Paul Douglas Franklin <pdf at yugm.org> writes:
>
>   
>> Gunnar Wrobel wrote:
>>     
>>> Paul Franklin <yugm6161 at yahoo.com> writes:
>>>
>>>   
>>>       
>>>> Alain,                                                                                                                                                                           
>>>> Thanks again for your tutorial.  I have now had opportunity to put it into practice.  I did not get very far in the process, however, before I discovered a sign of what is      
>>>> wrong.  I just don't know what to do with the sign.                                                                                                                              
>>>>                                                                                                                                                                                  
>>>> This morning mail delivery stopped at around 10:30.  The postfix log shows messages such as                                                                                      
>>>>                                                                                                                                                                                  
>>>> Jun 30 20:23:26 exchange <info> postfix/pipe[20064]: 52F63384220: to=<yugm6161 at yahoo.com>, relay=kolabfilter, delay=0, status=sent (exchange.yugm.org)                           
>>>> Jun 30 20:23:26 exchange <info> postfix/qmgr[3142]: 5B0DC384230: to=<yugm6161 at yahoo.com>, relay=none, delay=0, status=deferred (delivery temporarily suspended: connect to       
>>>> 127.0.0.1[127.0.0.1]: Connection refused)                                                                                                                                        
>>>>                                                                                                                                                                                  
>>>> I grepped for "temporarily" and discovered that when the mail first stopped, a typical log entry was                                                                             
>>>>                                                                                                                                                                                  
>>>> Jun 30 10:31:22 exchange <info> postfix/qmgr[3142]: 64EBF457B7C: to=<archive at yugm.org>, relay=none, delay=703, status=deferred (delivery temporarily suspended: connect to       
>>>> 127.0.0.1[127.0.0.1]: read timeout)                                                                                                                                              
>>>>                                                                                                                                                                                  
>>>> I'm going to reboot my kolab box since that is what seemed to do the
>>>> job last time.  I would like, however, to figure out what is causing
>>>> this occasional problem.  Given this information, where would you
>>>> look next?
>>>>     
>>>>         
>>> Looks like your amavisd-new process is failing here. You should be
>>> able to restart it with
>>>
>>> /kolab/bin/openpkg rc amavisd
>>>
>>> On the other hand it should not be failing in the first place. Do you
>>> see anything in the amavisd logs?
>>>
>>>   
>>>       
>> I see some things.
>> At 10:10:07 I issued the /kolab/bin/openpkg rc all restart command.  It 
>> went thru quite a process, finishing at 10:10:44.  (More about that 
>> later.)  Then, at 10:11:52, I issued the /kolab/bin/openpkg rc amavisd 
>> restart command (just to get it moved into my recent history--I knew 
>> amavisd was included in all).  It was at this point that problems 
>> happened, but without any indication of why.  There are exactly two 
>> lines in the log here:
>>
>> Jun 30 10:11:52 exchange.yugm.org /kolab/sbin/amavisd[4330]: starting.  /kolab/sbin/amavisd at exchange.yugm.org amavisd-new-2.3.3 (20050822), Unicode aware, LANG=en_US.UTF-8
>> Jun 30 10:11:52 exchange.yugm.org /kolab/sbin/amavisd[4330]: Perl version               5.008007
>>
>> The next entry wasn't until I rebooted at 20:52.  So it does appear that 
>> amavisd didn't load, but it doesn't say why.
>>
>> There is another thing that I see that causes me concern.  Toward the 
>> end of the restart, it appears that clam fails.
>>
>> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .rar  tried: rar, unrar
>> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .arj  tried: arj, unarj
>> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .arc  tried: nomarch, arc
>> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .zoo  tried: zoo
>> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .lha  tried: lha
>> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .doc 
>> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .cab 
>> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .tnef
>> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: Internal decoder for .tnef
>> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: No decoder for       .exe  tried: rar, unrar; lha; arj, unarj
>> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: Using internal av scanner code for (primary) Clam Antivirus-clamd
>> Jun 30 20:52:07 exchange.yugm.org /kolab/sbin/amavisd[5274]: Found secondary av scanner Clam Antivirus - /kolab/bin/clamscan at /kolab/bin/clamscan
>> Jun 30 20:52:16 exchange.yugm.org /kolab/sbin/amavisd[5359]: (05359-01) Clam Antivirus-clamd: Can't connect to UNIX socket /kolab/var/clamav/clamd.sock: No such file or directory, retrying (2)
>> Jun 30 20:52:16 exchange.yugm.org /kolab/sbin/amavisd[5360]: (05360-01) Clam Antivirus-clamd: Can't connect to UNIX socket /kolab/var/clamav/clamd.sock: No such file or directory, retrying (2)
>> Jun 30 20:52:22 exchange.yugm.org /kolab/sbin/amavisd[5359]: (05359-01) Clam Antivirus-clamd av-scanner FAILED: Too many retries to talk to /kolab/var/clamav/clamd.sock (Can't connect to UNIX socket /kolab/var/clamav/clamd.sock: No such file or directory) at (eval 55) line 266.
>> Jun 30 20:52:22 exchange.yugm.org /kolab/sbin/amavisd[5359]: (05359-01) WARN: all primary virus scanners failed, considering backups
>> Jun 30 20:52:22 exchange.yugm.org /kolab/sbin/amavisd[5360]: (05360-01) Clam Antivirus-clamd av-scanner FAILED: Too many retries to talk to /kolab/var/clamav/clamd.sock (Can't connect to UNIX socket /kolab/var/clamav/clamd.sock: No such file or directory) at (eval 55) line 266.
>> Jun 30 20:52:22 exchange.yugm.org /kolab/sbin/amavisd[5360]: (05360-01) WARN: all primary virus scanners failed, considering backups
>>
>> Looking at the clamav log, I see that it started at 20:52:09.
>> Is this indeed saying that I have no antivirus protection?
>>     
>
> Yes it appears so. The socket file should indicate that clamd is
> running. You can also check the process table for the "clamd" process.
>
> You can also try to run clamd manually from the command line using:
>
> /kolab/sbin/clamd --config-file=/kolab/etc/clamav/clamd.conf
>
> The clamd command has a few additional options that might help to
> debug the process.
>
> Cheers,
>
> Gunnar
>
>   
Thanks, Gunnar.  I have made no changes, but clam seems to be fine now.  
I issued ps-ax | grep clam and found a running process.  Then I 
restarted amavisd just to see.  Its log says that it is using clam.
--Paul
>> --Paul
>>
>>     
>>> Cheers,
>>>
>>> Gunnar
>>>   
>>>
>>>       
>> -- 
>> Paul Douglas Franklin
>> Computer Manager, Union Gospel Mission of Yakima, Washington
>> Husband of Danette
>> Father of Laurene, Miriam, Tycko, Timothy, Sarabeth, Marie, Dawnita, Anna Leah, Alexander, and Caleb
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>     
>
>   

-- 
Paul Douglas Franklin
Computer Manager, Union Gospel Mission of Yakima, Washington
Husband of Danette
Father of Laurene, Miriam, Tycko, Timothy, Sarabeth, Marie, Dawnita, Anna Leah, Alexander, and Caleb


From troy at carpenter.cx  Fri Jul  4 16:26:23 2008
From: troy at carpenter.cx (Troy Carpenter)
Date: Fri, 04 Jul 2008 10:26:23 -0400
Subject: Kolab/Horde contact phone numbers
Message-ID: <486E330F.3010109@carpenter.cx>

We have a large number of contacts in a shared folder on the Kolab 
server.  Nearly all the contacts have phone numbers attached, and in 
Kontact I can see all the data associated with a contact.

However, in Horde, I only see phone numbers for a few contacts.  When I 
added a phone number to one of those contacts via Horde, the contact 
appears in Kontact with two phone entries, both labeled "home", while 
Horde only shows the one I entered via Horde.

It would appear to me that Horde is not always recognizing the home 
phone field.  I cannot say how old the records are compared to the ones 
that are showing phone numbers. 

Obviously, I would like to have Horde show all the information without 
re-entering all the (already existing) phone numbers.

Thanks,
Troy Carpenter


From devgioiatech at gmail.com  Wed Jul  9 16:16:41 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Wed, 9 Jul 2008 16:16:41 +0200
Subject: problem with horde login
Message-ID: <d53357b70807090716n2dddc316ybab6a976c292a3@mail.gmail.com>

Hi all,
i've a problem when i try to connect to horde webmail.
the saslauthd.log contains  "user ldap_search_st() failed: Can't contact
LDAP server" but openldap is running and the same users can log in correctly
in admin interface.

the horde configuration file contain the fallowing lines

$conf['kolab']['ldap']['server'] = 'localhost';
$conf['kolab']['ldap']['port'] = 389;
$conf['kolab']['ldap']['basedn'] = 'dc=example,dc=com';
$conf['kolab']['ldap']['phpdn'] = 'cn=nobody,cn=internal,dc=example,dc=com';
$conf['kolab']['ldap']['phppw'] = 'dummy';
$conf['kolab']['imap']['server'] = 'localhost';
$conf['kolab']['imap']['port'] = 143;
$conf['kolab']['imap']['sieveport'] = 2000;
$conf['kolab']['imap']['maildomain'] = 'example.com';

i try to change this line with correct parameter of domain and maildomain,
but nothing changes...

any idea?

thanks.
-------------- parte successiva --------------
Un allegato HTML ? stato rimosso...
URL: http://kolab.org/pipermail/kolab-users/attachments/20080709/42204c27/attachment.html

From troy at carpenter.cx  Wed Jul  9 17:13:25 2008
From: troy at carpenter.cx (Troy Carpenter)
Date: Wed, 09 Jul 2008 11:13:25 -0400
Subject: Kolab/Horde contact phone numbers
In-Reply-To: <486E330F.3010109@carpenter.cx>
References: <486E330F.3010109@carpenter.cx>
Message-ID: <4874D595.3000806@carpenter.cx>

Troy Carpenter wrote:
> We have a large number of contacts in a shared folder on the Kolab 
> server.  Nearly all the contacts have phone numbers attached, and in 
> Kontact I can see all the data associated with a contact.
>
> However, in Horde, I only see phone numbers for a few contacts.  When I 
> added a phone number to one of those contacts via Horde, the contact 
> appears in Kontact with two phone entries, both labeled "home", while 
> Horde only shows the one I entered via Horde.
>
> It would appear to me that Horde is not always recognizing the home 
> phone field.  I cannot say how old the records are compared to the ones 
> that are showing phone numbers. 
>
> Obviously, I would like to have Horde show all the information without 
> re-entering all the (already existing) phone numbers.
>
> Thanks,
> Troy Carpenter
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>   
I have discovered the following in the contact.xml records stored on the 
IMAP server (as seen by opening the attachment in an email program):

- <#> <phone>
    <type>home2</type>
    <number>123-456-6332</number>
</phone>

All the ones that don't show the home phone number in Horde are marked 
"home2", while the ones Horde shows (or subsequently creates), are 
marked "home1".

Now I just need a quick way to rename all the "home2" entries to "home1".

Troy


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
Url : http://kolab.org/pipermail/kolab-users/attachments/20080709/3d73ba8f/signature.bin

From aspineux at gmail.com  Wed Jul  9 19:57:52 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Wed, 9 Jul 2008 19:57:52 +0200
Subject: problem with horde login
In-Reply-To: <d53357b70807090716n2dddc316ybab6a976c292a3@mail.gmail.com>
References: <d53357b70807090716n2dddc316ybab6a976c292a3@mail.gmail.com>
Message-ID: <71fe4e760807091057q61226b76w90cd58cc56138474@mail.gmail.com>

On Wed, Jul 9, 2008 at 4:16 PM, Antonio Straziota
<devgioiatech at gmail.com> wrote:
> Hi all,
> i've a problem when i try to connect to horde webmail.
> the saslauthd.log contains  "user ldap_search_st() failed: Can't contact
> LDAP server" but openldap is running and the same users can log in correctly
> in admin interface.

Dit you search the archive, someone with the same problem make a post
some time ago.

I remember someone trying to login withe a password with unusual characters.
Can you try with a simple password ?


>
> the horde configuration file contain the fallowing lines
>
> $conf['kolab']['ldap']['server'] = 'localhost';
> $conf['kolab']['ldap']['port'] = 389;
> $conf['kolab']['ldap']['basedn'] = 'dc=example,dc=com';
> $conf['kolab']['ldap']['phpdn'] = 'cn=nobody,cn=internal,dc=example,dc=com';
> $conf['kolab']['ldap']['phppw'] = 'dummy';
> $conf['kolab']['imap']['server'] = 'localhost';
> $conf['kolab']['imap']['port'] = 143;
> $conf['kolab']['imap']['sieveport'] = 2000;
> $conf['kolab']['imap']['maildomain'] = 'example.com';
>
> i try to change this line with correct parameter of domain and maildomain,
> but nothing changes...
>
> any idea?
>
> thanks.
>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From devgioiatech at gmail.com  Thu Jul 10 00:13:27 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Thu, 10 Jul 2008 00:13:27 +0200
Subject: problem with horde login
In-Reply-To: <71fe4e760807091057q61226b76w90cd58cc56138474@mail.gmail.com>
References: <d53357b70807090716n2dddc316ybab6a976c292a3@mail.gmail.com>
	<71fe4e760807091057q61226b76w90cd58cc56138474@mail.gmail.com>
Message-ID: <d53357b70807091513k6ecf5e29sa16249ba2e1d5d0f@mail.gmail.com>

My password is "test"...i reset it more time with no success.
I've search in wiki in the troubleshooting section:

http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_Mail_accounts
http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_SASL

All suggested checks goes fine.

I had a look at archive since to 2008-January and i've found only this
similar (not the same) problem

http://www.kolab.org/pipermail/kolab-users/2008-February/007382.html

The strange issue is that only webmail not authenticate users, all users,
with the LDAP error.
the webmin and sasl test works fine.


2008/7/9 Alain Spineux <aspineux at gmail.com>:

> On Wed, Jul 9, 2008 at 4:16 PM, Antonio Straziota
> <devgioiatech at gmail.com> wrote:
> > Hi all,
> > i've a problem when i try to connect to horde webmail.
> > the saslauthd.log contains  "user ldap_search_st() failed: Can't contact
> > LDAP server" but openldap is running and the same users can log in
> correctly
> > in admin interface.
>
> Dit you search the archive, someone with the same problem make a post
> some time ago.
>
> I remember someone trying to login withe a password with unusual
> characters.
> Can you try with a simple password ?
>
>
> >
> > the horde configuration file contain the fallowing lines
> >
> > $conf['kolab']['ldap']['server'] = 'localhost';
> > $conf['kolab']['ldap']['port'] = 389;
> > $conf['kolab']['ldap']['basedn'] = 'dc=example,dc=com';
> > $conf['kolab']['ldap']['phpdn'] =
> 'cn=nobody,cn=internal,dc=example,dc=com';
> > $conf['kolab']['ldap']['phppw'] = 'dummy';
> > $conf['kolab']['imap']['server'] = 'localhost';
> > $conf['kolab']['imap']['port'] = 143;
> > $conf['kolab']['imap']['sieveport'] = 2000;
> > $conf['kolab']['imap']['maildomain'] = 'example.com';
> >
> > i try to change this line with correct parameter of domain and
> maildomain,
> > but nothing changes...
> >
> > any idea?
> >
> > thanks.
> >
> >
> > _______________________________________________
> > Kolab-users mailing list
> > Kolab-users at kolab.org
> > https://kolab.org/mailman/listinfo/kolab-users
> >
> >
>
>
>
> --
> Alain Spineux
> aspineux gmail com
> May the sources be with you
>
-------------- parte successiva --------------
Un allegato HTML ? stato rimosso...
URL: http://kolab.org/pipermail/kolab-users/attachments/20080710/321968a5/attachment.html

From devgioiatech at gmail.com  Thu Jul 10 12:00:57 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Thu, 10 Jul 2008 12:00:57 +0200
Subject: problem with horde login
In-Reply-To: <d53357b70807091513k6ecf5e29sa16249ba2e1d5d0f@mail.gmail.com>
References: <d53357b70807090716n2dddc316ybab6a976c292a3@mail.gmail.com>
	<71fe4e760807091057q61226b76w90cd58cc56138474@mail.gmail.com>
	<d53357b70807091513k6ecf5e29sa16249ba2e1d5d0f@mail.gmail.com>
Message-ID: <d53357b70807100300v1dc03d11q5dfecb5b95433575@mail.gmail.com>

Hi all...
The problem is resolved...

It was a name resolution problem.

I add the FQDN of the server in the /etc/hosts file and now i can
authenticate on webmail.

Bye...


2008/7/10 Antonio Straziota <devgioiatech at gmail.com>:

> My password is "test"...i reset it more time with no success.
> I've search in wiki in the troubleshooting section:
>
>
> http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_Mail_accounts
> http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_SASL
>
> All suggested checks goes fine.
>
> I had a look at archive since to 2008-January and i've found only this
> similar (not the same) problem
>
> http://www.kolab.org/pipermail/kolab-users/2008-February/007382.html
>
> The strange issue is that only webmail not authenticate users, all users,
> with the LDAP error.
> the webmin and sasl test works fine.
>
>
> 2008/7/9 Alain Spineux <aspineux at gmail.com>:
>
> On Wed, Jul 9, 2008 at 4:16 PM, Antonio Straziota
>> <devgioiatech at gmail.com> wrote:
>> > Hi all,
>> > i've a problem when i try to connect to horde webmail.
>> > the saslauthd.log contains  "user ldap_search_st() failed: Can't contact
>> > LDAP server" but openldap is running and the same users can log in
>> correctly
>> > in admin interface.
>>
>> Dit you search the archive, someone with the same problem make a post
>> some time ago.
>>
>> I remember someone trying to login withe a password with unusual
>> characters.
>> Can you try with a simple password ?
>>
>>
>> >
>> > the horde configuration file contain the fallowing lines
>> >
>> > $conf['kolab']['ldap']['server'] = 'localhost';
>> > $conf['kolab']['ldap']['port'] = 389;
>> > $conf['kolab']['ldap']['basedn'] = 'dc=example,dc=com';
>> > $conf['kolab']['ldap']['phpdn'] =
>> 'cn=nobody,cn=internal,dc=example,dc=com';
>> > $conf['kolab']['ldap']['phppw'] = 'dummy';
>> > $conf['kolab']['imap']['server'] = 'localhost';
>> > $conf['kolab']['imap']['port'] = 143;
>> > $conf['kolab']['imap']['sieveport'] = 2000;
>> > $conf['kolab']['imap']['maildomain'] = 'example.com';
>> >
>> > i try to change this line with correct parameter of domain and
>> maildomain,
>> > but nothing changes...
>> >
>> > any idea?
>> >
>> > thanks.
>> >
>> >
>> > _______________________________________________
>> > Kolab-users mailing list
>> > Kolab-users at kolab.org
>> > https://kolab.org/mailman/listinfo/kolab-users
>> >
>> >
>>
>>
>>
>> --
>> Alain Spineux
>> aspineux gmail com
>> May the sources be with you
>>
>
>
-------------- parte successiva --------------
Un allegato HTML ? stato rimosso...
URL: http://kolab.org/pipermail/kolab-users/attachments/20080710/3bffd892/attachment.html

From wrobel at pardus.de  Thu Jul 10 12:10:33 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 10 Jul 2008 12:10:33 +0200
Subject: Swapfile
In-Reply-To: <486CCB5A.7040208@vw.htw-aalen.de> (Till Eberlein's message of
	"Thu, 03 Jul 2008 14:51:38 +0200")
References: <486B6C43.2090903@vw.htw-aalen.de> <87k5g3k11t.fsf@home.pardus.de>
	<486CCB5A.7040208@vw.htw-aalen.de>
Message-ID: <87abgq82xy.fsf@home.pardus.de>

Hallo Till,

Till Eberlein <eberlein at vw.htw-aalen.de> writes:

> Nochmal Hallo
>
> Ist das bekannte Apache-Problem in der RC3 noch von Bestand, oder ist 
> dort  schon eine entsprechend korrigierte Version enthalten? Denn dann 
> macht es ja eher Sinn die RC3 zu installieren als Apache zu patchen.

Es wird auch im Kolab-Server-2.2-Release der Apache-2.2.8
verwendet. Bisher ist das von Dir berichtete Problem ein
Einzelfall. Von daher bin ich auch selber noch nicht sicher, dass ein
Upgrade auf Apache-2.2.9 das Problem in Deinem Fall ?berhaupt l?sen
w?rde.

Das k?nntest Du allerdings auch manuell vornehmen. Wenn das die
Probleme auf Deiner Seite beseitigt, haben wir einen Hinweis, dass es
sinnvoll ist auf 2.2.9 zu wechseln.

>
> Was ist denn eher zu empfehlen bei einem Upgrade (ich habe bis jetzt nur 
>   einige Neuinstallationen hinter mir): Neuer kolabtemp-Ordner und dort 
> die ...since...Dateien herunterladen und dann kolab-install ausf?hren 
> oder die ....since.... Dateien direkt ins RC2-kolabtemp-Verzeichnis 
> laden und dann die aktuelle kolab-install ausf?hren?
>
> Hat schon jemand hoffentlich gute oder eventuell auch schlechte 
> Erfahrungen bei einem Upgrade von RC2 auf RC3?

Ich w?rde in Deinem Fall nur den Apache auf 2.2.9 aktualisieren, wenn
das entsprechende Paket von OpenPKG verf?gbar ist. Ein paar technische
Hinweise dazu gibt es hier:

http://wiki.kolab.org/index.php/Kolab_Server_erweitern

Gru?,

Gunnar

>
>
> Mit freundlichen Gr?ssen
>
>
> Till Eberlein
>
>
>
> Gunnar Wrobel schrieb:
>> Till Eberlein <eberlein at vw.htw-aalen.de> writes:
>> 
>>> Hallo Zusammen
>>>
>>> Vielleicht hat jemand eine Idee oder sogar eine L?sung f?r folgendes 
>>> Problem:
>>>
>>> Kolab 2.2 rc2, Opensuse 10.2, 2GB Arbeitsspeicher (wenig, aber es geht 
>>> nicht mehr), 4GB Swap.
>>>
>>> Nach sp?testens drei bis vier Tagen normalem Betrieb laufen die 
>>> Swap-Files voll, es bringt auch nichts den Swap zu vergr?ssern, der 
>>> l?uft dann nach kurzer Zeit auch voll. Ein Neustart des Apache l?st das 
>>> Problem (der Swap wird wieder freigegeben), aber nach einigen Tagen habe 
>>> ich wieder das gleiche Szenario. Es liegt nachvollziehbar am Apache, 
>>> obwohl dieser kaum genutzt wird. Maximal zur Administration und hin und 
>>> wieder einmal ein Zugriff per Horde.
>>> Freebusy wird zwar genutzt, aber maximal von 5 Usern.
>>>
>>> Im Voraus schon mal Danke
>> 
>> In der Apache-2.2.9-Version wurde zumindest ein memory leak
>> korrigiert, das relevant sein k?nnte:
>> 
>> https://issues.apache.org/bugzilla/show_bug.cgi?id=44975
>> 
>> Dort ist ein Test beschrieben, den man vielleicht durchf?hren k?nnte.
>> 
>> Von Deiner Beschreibung her vermute ich auf jeden Fall eher ein
>> generelles Apache-Problem.
>> 
>> L?sst sich ?berpr?fen, welche Seitenaufrufe den Speicherbedarf des
>> Apache erh?hen? Also z.B. durch mehrfaches Aufrufen nur einer der
>> installierten Web-Applikationen?
>> 
>> Gru?,
>> 
>> Gunnar
>> 
>>> -- 
>>>
>>> Mit freundlichen Gr?ssen
>>>
>>>
>>> Till Eberlein
>>>
>>> _______________________________________________
>>> Kolab-users mailing list
>>> Kolab-users at kolab.org
>>> https://kolab.org/mailman/listinfo/kolab-users
>> 
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From wrobel at pardus.de  Thu Jul 10 12:21:07 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 10 Jul 2008 12:21:07 +0200
Subject: Kolab/Horde contact phone numbers
In-Reply-To: <4874D595.3000806@carpenter.cx> (Troy Carpenter's message of "Wed,
	09 Jul 2008 11:13:25 -0400")
References: <486E330F.3010109@carpenter.cx> <4874D595.3000806@carpenter.cx>
Message-ID: <87zloq6nvw.fsf@home.pardus.de>

Troy Carpenter <troy at carpenter.cx> writes:

> Troy Carpenter wrote:
>> We have a large number of contacts in a shared folder on the Kolab
>> server.  Nearly all the contacts have phone numbers attached, and in
>> Kontact I can see all the data associated with a contact.
>>
>> However, in Horde, I only see phone numbers for a few contacts.
>> When I added a phone number to one of those contacts via Horde, the
>> contact appears in Kontact with two phone entries, both labeled
>> "home", while Horde only shows the one I entered via Horde.
>>
>> It would appear to me that Horde is not always recognizing the home
>> phone field.  I cannot say how old the records are compared to the
>> ones that are showing phone numbers. 
>>
>> Obviously, I would like to have Horde show all the information
>> without re-entering all the (already existing) phone numbers.
>>
>> Thanks,
>> Troy Carpenter
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>   
> I have discovered the following in the contact.xml records stored on
> the IMAP server (as seen by opening the attachment in an email
> program):
>
> - <#> <phone>
>    <type>home2</type>
>    <number>123-456-6332</number>
> </phone>
>
> All the ones that don't show the home phone number in Horde are marked
> "home2", while the ones Horde shows (or subsequently creates), are
> marked "home1".
>
> Now I just need a quick way to rename all the "home2" entries to "home1".

Better not :)

While I guess this would work I think it is safer to edit the Horde
configuration to allow for a second home entry. Horde is actually
pretty flexible there.

What you'd need to do is the following:

Add a block like

 $attributes['homePhone2'] = array(
 'label' => _("Home Phone 2"),
 'type' => 'phone',
 'required' => false
 );

to /kolab/var/kolab/www/horde/turba/config/attributes.php

and add the line

'homePhone2' => 'phone-home2',

in the 'map' entry of the $cfgSources['kolab'] array in 
/kolab/var/kolab/www/horde/turba/config/sources.php.

If people require this to work by default you should add a bug in the
Kolab bug tracker. I can easily add this to Horde and I think I just
didn't do it because there are a large number of possible phone types.

Cheers,

Gunnar

>
> Troy
>
>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From wrobel at pardus.de  Thu Jul 10 12:25:40 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 10 Jul 2008 12:25:40 +0200
Subject: problem with horde login
In-Reply-To: <d53357b70807090716n2dddc316ybab6a976c292a3@mail.gmail.com>
	(Antonio Straziota's message of "Wed, 9 Jul 2008 16:16:41 +0200")
References: <d53357b70807090716n2dddc316ybab6a976c292a3@mail.gmail.com>
Message-ID: <87tzey6nob.fsf@home.pardus.de>

"Antonio Straziota" <devgioiatech at gmail.com> writes:

> Hi all,
> i've a problem when i try to connect to horde webmail.
> the saslauthd.log contains  "user ldap_search_st() failed: Can't contact LDAP server" but openldap is running and the same users can log in correctly in admin interface.
>
> the horde configuration file contain the fallowing lines
>
> $conf['kolab']['ldap']['server'] = 'localhost';
> $conf['kolab']['ldap']['port'] = 389;
> $conf['kolab']['ldap']['basedn'] = 'dc=example,dc=com';
> $conf['kolab']['ldap']['phpdn'] = 'cn=nobody,cn=internal,dc=example,dc=com';
> $conf['kolab']['ldap']['phppw'] = 'dummy';
> $conf['kolab']['imap']['server'] = 'localhost';
> $conf['kolab']['imap']['port'] = 143;
> $conf['kolab']['imap']['sieveport'] = 2000;
> $conf['kolab']['imap']['maildomain'] = 'example.com';
>
> i try to change this line with correct parameter of domain and maildomain, but nothing changes...
>
> any idea?

Can you provide additional details about your system? I assume you are
using a standard Kolab2.2-RC3 system?

Editing the configuration displayed above won't help as the correct
information for you server should be present in the kolab.php file
rather than the conf.php file.

kolabconf is responsible for correctly generating the kolab.php
configuration file.

Cheers,
Gunnar

>
> thanks.
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From wrobel at pardus.de  Thu Jul 10 13:33:33 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 10 Jul 2008 13:33:33 +0200
Subject: A (currently theoretical) question concerning a book about the Kolab
	Server
Message-ID: <87ej626kj6.fsf@home.pardus.de>

Hi!

As some of you may know I recently wrote a book about the Linux
distribution Gentoo
(https://www.opensourcepress.de/index.php?26&tt_products=144).

While I like Gentoo my main area of activity is the Kolab groupware
and I'd be really interested in writing a handbook for administrators
of the Kolab server.

Ideally that book would be available in print but free in its
electronic version as PDF. This is a model currently not supported by
my publisher OpenSourcePress. They rely of course on the income made
with the books in whatever format.

So I could choose to tackle that project on my own. But that would
have significant drawbacks. I'd probably only invest time when I have
it which would mean it would be a project that takes ages. And I'd
loose the very valuable influx of knowledge from the publisher. 

I know very well from the experience with the Gentoo book that their
input has a very high value. What I was capable of writing and
submitting into their subversion system miraculously turned into
readable text with the next revision I checked out. And I think I'm
not yet lost deep enough in code that I would underestimate the value
a well readable technical documentation has.

I do see parallels with the free software provided by the Kolab
Konsortium. It is actually a quite amazing success that the consortium
manages to publish a free groupware server that is commercially
viable. Companies are willing to pay for feature enhancements such as
the port of Kontact to Windows or the start of the SyncML support to
name some recent ones. In my eyes it is a fantastic achievement by the
companies driving the Kolab project that such things are automatically
contributed back to the community.

So I'm wondering if there'd actually be enough financial interest in a
book about Kolab. This is still a completely hypothetical question as
I didn't consider the important parameters of such a project yet. I'd
expect the costs to be somewhere in the range of twenty to thirty
thousand Euros for convinving the publisher to agree to the model with
a non-free print version and a free PDF.

So right now I'm just looking for some comments to start getting some
ideas and a better grasp of the potential problems that one would need
to solve.

Thanks!

Gunnar

-- 
____ http://www.pardus.de _________________ http://gunnarwrobel.de _

E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                         Bundesstrasse 29
Fax    : +49 721 1513 52322                        D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From roland.kaeser at intersoft-networks.ch  Thu Jul 10 14:16:20 2008
From: roland.kaeser at intersoft-networks.ch (Roland Kaeser)
Date: Thu, 10 Jul 2008 14:16:20 +0200
Subject: Upgrade from 2.2-Beta3 to Current Version
Message-ID: <200807101416.20611.roland.kaeser@intersoft-networks.ch>

Hello

I'm currently working with a 2.2-Beta 3 and would like to upgrade it to the 
current release candidate. After reading the available docs I'm already not 
sure how this should exactly go. Can I just download the new files and run a 
compile and install or is there an additional procedure to make (backup files 
etc.)?

Roland


-- 
Roland K?ser, Systems Engineer
Fulachstr. 197, CH-8200 Schaffhausen
Tel.: ++41 76 481 37 85, www.intersoft-networks.ch
mailto:roland.kaeser at intersoft-networks.ch
----------------------------------------------------------------------------------------------------------------------------------
Diejenigen, die ihre Freiheit zugunsten der Sicherheit aufgeben, 
werden am Ende keines von beiden haben - und verdienen es auch nicht. 
(Benjamin Franklin)
----------------------------------------------------------------------------------------------------------------------------------


From wrobel at pardus.de  Thu Jul 10 14:25:49 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 10 Jul 2008 14:25:49 +0200
Subject: Upgrade from 2.2-Beta3 to Current Version
In-Reply-To: <200807101416.20611.roland.kaeser@intersoft-networks.ch> (Roland
	Kaeser's message of "Thu, 10 Jul 2008 14:16:20 +0200")
References: <200807101416.20611.roland.kaeser@intersoft-networks.ch>
Message-ID: <87abgq6i42.fsf@home.pardus.de>

Roland Kaeser <roland.kaeser at intersoft-networks.ch> writes:

> Hello
>
> I'm currently working with a 2.2-Beta 3 and would like to upgrade it to the 
> current release candidate. After reading the available docs I'm already not 
> sure how this should exactly go. Can I just download the new files and run a 
> compile and install or is there an additional procedure to make (backup files 
> etc.)?

If you are running a productive server you hopefully have a regular
backup. If not you should follow this description:

http://wiki.kolab.org/index.php/Backups_for_kolab2

The same type of backup should be done before an upgrade.

Other than that you should follow the general upgrade instructions
plus the release specific ones in

http://kolab.linjection.org/server/beta/kolab-server-2.2-rc-3/sources/1st.README

But right now you should also just wait a few days for the final
release :) That saves you another upgrade.

Cheers,

Gunnar

>
> Roland
>
>
> -- 
> Roland K?ser, Systems Engineer
> Fulachstr. 197, CH-8200 Schaffhausen
> Tel.: ++41 76 481 37 85, www.intersoft-networks.ch
> mailto:roland.kaeser at intersoft-networks.ch
> ----------------------------------------------------------------------------------------------------------------------------------
> Diejenigen, die ihre Freiheit zugunsten der Sicherheit aufgeben, 
> werden am Ende keines von beiden haben - und verdienen es auch nicht. 
> (Benjamin Franklin)
> ----------------------------------------------------------------------------------------------------------------------------------
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From roland.kaeser at intersoft-networks.ch  Thu Jul 10 14:49:08 2008
From: roland.kaeser at intersoft-networks.ch (Roland Kaeser)
Date: Thu, 10 Jul 2008 14:49:08 +0200
Subject: Upgrade from 2.2-Beta3 to Current Version
In-Reply-To: <87abgq6i42.fsf@home.pardus.de>
References: <200807101416.20611.roland.kaeser@intersoft-networks.ch>
	<87abgq6i42.fsf@home.pardus.de>
Message-ID: <200807101449.08507.roland.kaeser@intersoft-networks.ch>

Hello

Thanks, surely we have a regular backup. But I couldn't find a upgrade path 
for the Beta3 to RC3. Are there special upgrade steps required?

Roland

Am Donnerstag, 10. Juli 2008 14:25:49 schrieb Gunnar Wrobel:
> Roland Kaeser <roland.kaeser at intersoft-networks.ch> writes:
> > Hello
> >
> > I'm currently working with a 2.2-Beta 3 and would like to upgrade it to
> > the current release candidate. After reading the available docs I'm
> > already not sure how this should exactly go. Can I just download the new
> > files and run a compile and install or is there an additional procedure
> > to make (backup files etc.)?
>
> If you are running a productive server you hopefully have a regular
> backup. If not you should follow this description:
>
> http://wiki.kolab.org/index.php/Backups_for_kolab2
>
> The same type of backup should be done before an upgrade.
>
> Other than that you should follow the general upgrade instructions
> plus the release specific ones in
>
> http://kolab.linjection.org/server/beta/kolab-server-2.2-rc-3/sources/1st.R
>EADME
>
> But right now you should also just wait a few days for the final
> release :) That saves you another upgrade.
>
> Cheers,
>
> Gunnar
>
> > Roland
> >
> >
> > --
> > Roland K?ser, Systems Engineer
> > Fulachstr. 197, CH-8200 Schaffhausen
> > Tel.: ++41 76 481 37 85, www.intersoft-networks.ch
> > mailto:roland.kaeser at intersoft-networks.ch
> > -------------------------------------------------------------------------
> >--------------------------------------------------------- Diejenigen, die
> > ihre Freiheit zugunsten der Sicherheit aufgeben, werden am Ende keines
> > von beiden haben - und verdienen es auch nicht. (Benjamin Franklin)
> > -------------------------------------------------------------------------
> >---------------------------------------------------------
> >
> > _______________________________________________
> > Kolab-users mailing list
> > Kolab-users at kolab.org
> > https://kolab.org/mailman/listinfo/kolab-users




-- 
Roland K?ser, Systems Engineer
Fulachstr. 197, CH-8200 Schaffhausen
Tel.: ++41 76 481 37 85, www.intersoft-networks.ch
mailto:roland.kaeser at intersoft-networks.ch
----------------------------------------------------------------------------------------------------------------------------------
Diejenigen, die ihre Freiheit zugunsten der Sicherheit aufgeben, 
werden am Ende keines von beiden haben - und verdienen es auch nicht. 
(Benjamin Franklin)
----------------------------------------------------------------------------------------------------------------------------------


From jkomar at jbox.ca  Thu Jul 10 15:14:23 2008
From: jkomar at jbox.ca (Jason Komar)
Date: Thu, 10 Jul 2008 07:14:23 -0600
Subject: A (currently theoretical) question concerning a book about the
	Kolab Server
In-Reply-To: <87ej626kj6.fsf@home.pardus.de>
References: <87ej626kj6.fsf@home.pardus.de>
Message-ID: <200807100714.25320.jkomar@jbox.ca>

On July 10, 2008 05:33:33 am Gunnar Wrobel wrote:
> Hi!
>
> As some of you may know I recently wrote a book about the Linux
> distribution Gentoo
> (https://www.opensourcepress.de/index.php?26&tt_products=144).
>
> While I like Gentoo my main area of activity is the Kolab groupware
> and I'd be really interested in writing a handbook for administrators
> of the Kolab server.
>
> Ideally that book would be available in print but free in its
> electronic version as PDF. This is a model currently not supported by
> my publisher OpenSourcePress. They rely of course on the income made
> with the books in whatever format.
>
> So I could choose to tackle that project on my own. But that would
> have significant drawbacks. I'd probably only invest time when I have
> it which would mean it would be a project that takes ages. And I'd
> loose the very valuable influx of knowledge from the publisher.
>
> I know very well from the experience with the Gentoo book that their
> input has a very high value. What I was capable of writing and
> submitting into their subversion system miraculously turned into
> readable text with the next revision I checked out. And I think I'm
> not yet lost deep enough in code that I would underestimate the value
> a well readable technical documentation has.
>
> I do see parallels with the free software provided by the Kolab
> Konsortium. It is actually a quite amazing success that the consortium
> manages to publish a free groupware server that is commercially
> viable. Companies are willing to pay for feature enhancements such as
> the port of Kontact to Windows or the start of the SyncML support to
> name some recent ones. In my eyes it is a fantastic achievement by the
> companies driving the Kolab project that such things are automatically
> contributed back to the community.
>
> So I'm wondering if there'd actually be enough financial interest in a
> book about Kolab. This is still a completely hypothetical question as
> I didn't consider the important parameters of such a project yet. I'd
> expect the costs to be somewhere in the range of twenty to thirty
> thousand Euros for convinving the publisher to agree to the model with
> a non-free print version and a free PDF.
>
> So right now I'm just looking for some comments to start getting some
> ideas and a better grasp of the potential problems that one would need
> to solve.
>
> Thanks!
>
> Gunnar

I don't have a lot of funds available, but would be willing to contribute what 
I can. A book like this would make the use of the kolab server more 
attractive to business which in turn could help drive development in the 
future. The existence of a manual such as this would be a real asset to the 
kolab community.

-- 
Jason Komar
806706 Alberta Ltd.
O/A Stormfront Ventures
Email: jkomar at jbox.ca


From wrobel at pardus.de  Thu Jul 10 15:14:48 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 10 Jul 2008 15:14:48 +0200
Subject: Upgrade from 2.2-Beta3 to Current Version
In-Reply-To: <200807101449.08507.roland.kaeser@intersoft-networks.ch> (Roland
	Kaeser's message of "Thu, 10 Jul 2008 14:49:08 +0200")
References: <200807101416.20611.roland.kaeser@intersoft-networks.ch>
	<87abgq6i42.fsf@home.pardus.de>
	<200807101449.08507.roland.kaeser@intersoft-networks.ch>
Message-ID: <8763rd7uev.fsf@home.pardus.de>

Roland Kaeser <roland.kaeser at intersoft-networks.ch> writes:

> Hello
>
> Thanks, surely we have a regular backup. But I couldn't find a upgrade path 
> for the Beta3 to RC3. Are there special upgrade steps required?
>
> Roland
>
> Am Donnerstag, 10. Juli 2008 14:25:49 schrieb Gunnar Wrobel:
>> Roland Kaeser <roland.kaeser at intersoft-networks.ch> writes:
>> > Hello
>> >
>> > I'm currently working with a 2.2-Beta 3 and would like to upgrade it to
>> > the current release candidate. After reading the available docs I'm
>> > already not sure how this should exactly go. Can I just download the new
>> > files and run a compile and install or is there an additional procedure
>> > to make (backup files etc.)?
>>
>> If you are running a productive server you hopefully have a regular
>> backup. If not you should follow this description:
>>
>> http://wiki.kolab.org/index.php/Backups_for_kolab2
>>
>> The same type of backup should be done before an upgrade.
>>
>> Other than that you should follow the general upgrade instructions
>> plus the release specific ones in
>>
>> http://kolab.linjection.org/server/beta/kolab-server-2.2-rc-3/sources/1st.README

The file linked above ^ holds three sections named:

Upgrade from 2.2-rc2 to 2.2-rc3
Upgrade from 2.2-rc1 to 2.2-rc2
Upgrade from 2.2-beta3 to 2.2-rc1

Cheers,

Gunnar

>>
>> But right now you should also just wait a few days for the final
>> release :) That saves you another upgrade.
>>
>> Cheers,
>>
>> Gunnar
>>
>> > Roland
>> >
>> >
>> > --
>> > Roland K?ser, Systems Engineer
>> > Fulachstr. 197, CH-8200 Schaffhausen
>> > Tel.: ++41 76 481 37 85, www.intersoft-networks.ch
>> > mailto:roland.kaeser at intersoft-networks.ch
>> > -------------------------------------------------------------------------
>> >--------------------------------------------------------- Diejenigen, die
>> > ihre Freiheit zugunsten der Sicherheit aufgeben, werden am Ende keines
>> > von beiden haben - und verdienen es auch nicht. (Benjamin Franklin)
>> > -------------------------------------------------------------------------
>> >---------------------------------------------------------
>> >
>> > _______________________________________________
>> > Kolab-users mailing list
>> > Kolab-users at kolab.org
>> > https://kolab.org/mailman/listinfo/kolab-users
>
>
>
>
> -- 
> Roland K?ser, Systems Engineer
> Fulachstr. 197, CH-8200 Schaffhausen
> Tel.: ++41 76 481 37 85, www.intersoft-networks.ch
> mailto:roland.kaeser at intersoft-networks.ch
> ----------------------------------------------------------------------------------------------------------------------------------
> Diejenigen, die ihre Freiheit zugunsten der Sicherheit aufgeben, 
> werden am Ende keines von beiden haben - und verdienen es auch nicht. 
> (Benjamin Franklin)
> ----------------------------------------------------------------------------------------------------------------------------------
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From bernhard at intevation.de  Thu Jul 10 16:21:22 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 10 Jul 2008 16:21:22 +0200
Subject: A (currently theoretical) question concerning a book about the
	Kolab Server
In-Reply-To: <87ej626kj6.fsf@home.pardus.de>
References: <87ej626kj6.fsf@home.pardus.de>
Message-ID: <200807101621.22388.bernhard@intevation.de>

Am Donnerstag, 10. Juli 2008 13:33:33 schrieb Gunnar Wrobel:
> So I'm wondering if there'd actually be enough financial interest in a
> book about Kolab. This is still a completely hypothetical question as
> I didn't consider the important parameters of such a project yet. I'd
> expect the costs to be somewhere in the range of twenty to thirty
> thousand Euros for convinving the publisher to agree to the model with
> a non-free print version and a free PDF.

There is some interested in documentation,
as you can see from the operating system manual in German available from 
http://kolab.org/documentation.html which a customer of the Kolab-Konsortium
contracted.

(One of the next steps probably would be to translate this nice manual.)
 
> So right now I'm just looking for some comments to start getting some
> ideas and a better grasp of the potential problems that one would need
> to solve.

There are two problems that I see:
a) people just expect the documentation to be there, so it probably will need 
to be cross financed from other Kolab business. While it is commericially 
viable for KK to run a large portions of the Kolab community efforts, the 
level could be better for maintenance and documentation. It will largely 
depend on how good KK will manage to get business and how fair users are 
inclined to pay for good service which includes running infrastructure and 
documentation.

b) Technically a good manual must be changed in the moment the software is 
changed, so it must be part of the software development process. For this the 
documentation must be part of public infrastructure of the kolab.org 
community.

Best,
Bernhard


-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From bernhard at intevation.de  Thu Jul 10 16:33:20 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 10 Jul 2008 16:33:20 +0200
Subject: Swapfile
In-Reply-To: <87abgq82xy.fsf@home.pardus.de>
References: <486B6C43.2090903@vw.htw-aalen.de>
	<486CCB5A.7040208@vw.htw-aalen.de> <87abgq82xy.fsf@home.pardus.de>
Message-ID: <200807101633.23328.bernhard@intevation.de>

Hallo, nur nebenbei:
Es ist zwar in Ordnung auf kolab-users@ in anderen Sprachen zu fragen,
f?r Deutsch haben wir aber seid Kurzem eine eigene Liste: kolab-users-de@ . :)

Rough translation: While it is okay to send questions in other languages to 
kolab-users@ we do have a special mailinglist for German: kolab-users-de at .

Bernhard

Am Donnerstag, 10. Juli 2008 12:10:33 schrieb Gunnar Wrobel:
>  Von daher bin ich auch selber noch nicht sicher, dass ein
> Upgrade auf Apache-2.2.9 das Problem in Deinem Fall ?berhaupt l?sen
> w?rde.
>
> Das k?nntest Du allerdings auch manuell vornehmen. Wenn das die
> Probleme auf Deiner Seite beseitigt, haben wir einen Hinweis, dass es
> sinnvoll ist auf 2.2.9 zu wechseln.


-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2620 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20080710/e08a19e9/smime.bin

From wrobel at pardus.de  Thu Jul 10 16:43:50 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 10 Jul 2008 16:43:50 +0200
Subject: Swapfile
In-Reply-To: <200807101633.23328.bernhard@intevation.de> (Bernhard Reiter's
	message of "Thu, 10 Jul 2008 16:33:20 +0200")
References: <486B6C43.2090903@vw.htw-aalen.de>
	<486CCB5A.7040208@vw.htw-aalen.de> <87abgq82xy.fsf@home.pardus.de>
	<200807101633.23328.bernhard@intevation.de>
Message-ID: <87wsjt6bq1.fsf@home.pardus.de>

Bernhard Reiter <bernhard at intevation.de> writes:

> Hallo, nur nebenbei:
> Es ist zwar in Ordnung auf kolab-users@ in anderen Sprachen zu fragen,
> f?r Deutsch haben wir aber seid Kurzem eine eigene Liste: kolab-users-de@ . :)
>
> Rough translation: While it is okay to send questions in other languages to 
> kolab-users@ we do have a special mailinglist for German: kolab-users-de at .

ups, I completely missed that. I should probably sort the two into two
different folders ;)

>
> Bernhard
>
> Am Donnerstag, 10. Juli 2008 12:10:33 schrieb Gunnar Wrobel:
>>  Von daher bin ich auch selber noch nicht sicher, dass ein
>> Upgrade auf Apache-2.2.9 das Problem in Deinem Fall ?berhaupt l?sen
>> w?rde.
>>
>> Das k?nntest Du allerdings auch manuell vornehmen. Wenn das die
>> Probleme auf Deiner Seite beseitigt, haben wir einen Hinweis, dass es
>> sinnvoll ist auf 2.2.9 zu wechseln.
>
>
> -- 
> Managing Director - Owner: www.intevation.net       (Free Software Company)
> Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
> Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
> Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From pdf at yugm.org  Thu Jul 10 18:40:45 2008
From: pdf at yugm.org (Paul Douglas Franklin)
Date: Thu, 10 Jul 2008 09:40:45 -0700
Subject: A (currently theoretical) question concerning a book about the
	Kolab	Server
In-Reply-To: <87ej626kj6.fsf@home.pardus.de>
References: <87ej626kj6.fsf@home.pardus.de>
Message-ID: <48763B8D.2000104@yugm.org>

Gunnar Wrobel wrote:
> I'd be really interested in writing a handbook for administrators
> of the Kolab server.
>
> Ideally that book would be available in print but free in its
> electronic version as PDF. This is a model currently not supported by
> my publisher OpenSourcePress. They rely of course on the income made
> with the books in whatever format.
>
> So I could choose to tackle that project on my own. But that would
> have significant drawbacks. I'd probably only invest time when I have
> it which would mean it would be a project that takes ages. And I'd
> loose the very valuable influx of knowledge from the publisher. 
>
> I know very well from the experience with the Gentoo book that their
> input has a very high value. What I was capable of writing and
> submitting into their subversion system miraculously turned into
> readable text with the next revision I checked out. And I think I'm
> not yet lost deep enough in code that I would underestimate the value
> a well readable technical documentation has.
>
> I do see parallels with the free software provided by the Kolab
> Konsortium. It is actually a quite amazing success that the consortium
> manages to publish a free groupware server that is commercially
> viable. Companies are willing to pay for feature enhancements such as
> the port of Kontact to Windows or the start of the SyncML support to
> name some recent ones. In my eyes it is a fantastic achievement by the
> companies driving the Kolab project that such things are automatically
> contributed back to the community.
>
> So I'm wondering if there'd actually be enough financial interest in a
> book about Kolab. This is still a completely hypothetical question as
> I didn't consider the important parameters of such a project yet. I'd
> expect the costs to be somewhere in the range of twenty to thirty
> thousand Euros for convinving the publisher to agree to the model with
> a non-free print version and a free PDF.
>
> So right now I'm just looking for some comments to start getting some
> ideas and a better grasp of the potential problems that one would need
> to solve.
>
> Thanks!
>
> Gunnar
>
>   
That model seems to work for O'Reilly.
I for one would be interested in such a book.  One difficulty that I run 
across is an assumption that those who will install and maintain Kolab 
are already familiar with concepts that I am not familiar with.  I 
suspect that these concepts are known by people who have worked with an 
Exchange server, but I'm not sure.  Setting up a Kolab server is a snap, 
but I'm not using it to its full potential.
--Paul

-- 
Paul Douglas Franklin
Computer Manager, Union Gospel Mission of Yakima, Washington
Husband of Danette
Father of Laurene, Miriam, Tycko, Timothy, Sarabeth, Marie, Dawnita, Anna Leah, Alexander, and Caleb


From aspineux at gmail.com  Thu Jul 10 20:43:10 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Thu, 10 Jul 2008 20:43:10 +0200
Subject: A (currently theoretical) question concerning a book about the
	Kolab Server
In-Reply-To: <48763B8D.2000104@yugm.org>
References: <87ej626kj6.fsf@home.pardus.de> <48763B8D.2000104@yugm.org>
Message-ID: <71fe4e760807101143o36a42c6cqb08adc11c7db3182@mail.gmail.com>

> Gunnar Wrobel wrote:
>> I'd be really interested in writing a handbook for administrators
>> of the Kolab server.

Any idea of how many kolab servers are running (in production).
And how many mailbox are hosted on such server ?


-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From s.trenz at 43gmbh.de  Fri Jul 11 11:51:33 2008
From: s.trenz at 43gmbh.de (s.trenz@43gmbh.de)
Date: Fri, 11 Jul 2008 11:51:33 +0200
Subject: ldap backup
Message-ID: <20080711115133.imra2ta7oco0sogw@webmail.43gmbh.de>

hi, i try to move the kolab Server to another Hardware.
I want to do a Backup wich is already listet on wiki.kolab.org, but i  
get an Error Message if i try to backup the Ldad with the following  
command
/kolab/sbin/slapcat -l /backup/kolab_ldap_db.ldif
and i get this message
/kolab/etc/openldap/slapd.conf: line 64: new attribute <member>


the Config File looks like
#### Using overlays to improve data consistency
# Ensure that we never get dangling member attributes
# Checked on rename and delete
overlay refint
refint_attributes member # this is line 64

# The mail and the uid attribute must be unique.
overlay unique
unique_attributes mail uid

index   objectClass     pres,eq
index   uid             approx,sub,pres,eq
index   mail            approx,sub,pres,eq


From thomas at intevation.de  Fri Jul 11 19:38:59 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 11 Jul 2008 19:38:59 +0200
Subject: Kolab Server 2.2.0 Final Release
Message-ID: <20080711173859.GC4107.thomas@intevation.de>

Hi!

I just uploaded the final release of Kolab Server 2.2.0, which
includes some important fixes to the last release candidates.

Again mmany thanks to all the people who helped with this!

Documentation and OpenPKG source packages will soon be available in
the directory server/release/kolab-server-2.2.0/ of the mirrors
listed on http://kolab.org/mirrors.html
for example:
http://ftp.gwdg.de/pub/linux/kolab/server/release/kolab-server-2.2.0/
 ftp://ftp.gwdg.de/pub/linux/kolab/server/release/kolab-server-2.2.0/

rsync://rsync.kolab.org/kolab/RSYNC.txt explains how to get (or
mirror) the files via rsync.

All files updated since 2.2-rc3 are available in the directory
server/development-2.2/20080711-since-20080523/

You can check the integrity of the downloaded files with:

$ gpg --keyserver hkp://subkeys.pgp.net --recv-key 5816791A
  or import the key from https://www.intevation.de/~thomas/gpg_pub_key.asc
  (the same key that I used to sign this email)
$ gpg --verify MD5SUMS.sig
$ md5sum -c MD5SUMS

Binary packages for Debian GNU/Linux (etch/stable) on x86 platforms
can be found in the ix86-debian4.0 directory next to the sources.

Please look at 1st.README and release-notes.txt (attached for your
convenience) for install instructions and more information about
this release. The install and upgrade instructions have been
extended since version 2.2-rc3.

Please report any problems you encounter in our issue tracker:
https://issues.kolab.org/

Regards,
Thomas Arendsen Hein

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
Kolab2 Server Install and Upgrade Information
=============================================

See http://kolab.org/ for general information about Kolab,
or look at http://wiki.kolab.org/ for specific topics.

It is recommended to subscribe to the announcement mailing list at
http://kolab.org/mailman/listinfo/kolab-announce
to receive security advisories and release announcements.


Quick install instructions
--------------------------

Kolab server with Horde needs about 1GB of disk space for the initial
install. By default the directory /kolab will be used, which should be
an empty directory or a symbolic link to an empty directory. If this
directory does not yet exist, it will be automatically created.

For production use it is recommended to create a separate partition for
/kolab (2GB to have some spare) and partitions for /kolab/var (at least
2GB for log files, virus filtering and caches) and /kolab/var/imapd/spool
(with enough space for your users' mails). For evaluation you could
start with the 2GB partition for /kolab (or 2GB free space on / if you
only have one big partition for your test system) and create the other
partitions when needed. Do _not_ use an NFS mounted drive!

Make sure that the following names are not in /etc/passwd or /etc/groups,
as OpenPKG will want to create them: "kolab" "kolab-r" "kolab-n"

To install the Kolab server, you need to download the files from the
directory containing this file (1st.README) to some local directory.

You can check the integrity of the downloaded files with:

$ gpg --keyserver hkp://subkeys.pgp.net --recv-key 5816791A
  or import the key from https://www.intevation.de/~thomas/gpg_pub_key.asc
$ gpg --verify MD5SUMS.sig
$ md5sum -c MD5SUMS

Then as root, cd into that local directory and run

# sh install-kolab.sh 2>&1 | tee /root/kolab-install.log

to build and install packages in /kolab. The command output will
be logged to install-kolab.log so that you have a reference in case
an errors occurs during installation.

The install script needs to store some files and creates a subdirectory
below /tmp (or $TMPDIR if set) for this purpose.

Horde might create much load on your server if there are many concurrent
users, so you can choose to not install it by adding the option
"-x horde-kolab-client" to the call to install-kolab.sh.
Installing Horde on a separate host is possible, but not discussed here.

If you do not want to install the free/busy view tool, add the option
"-x fbview-kronolith".

The binary packages distributed via kolab.org are compiled with Horde
and the free/busy view tool. Currently you need to compile from the
source packages to install without these features, see kolab/issue2440
for details.

By default, the Kolab server will now be started at boottime, so you
have to bootstrap the server configuration now to prevent unconfigured
components from being started, see kolab/issue1745 for details.

Please run:

# /kolab/etc/kolab/kolab_bootstrap -b

and follow the instructions.

Check http://www.openpkg.org/documentation/ for additional documentation
about the OpenPKG packaging system.


General update instructions
---------------------------

Usually an update of the Kolab server works as described here.  In
some cases you will need to deviate from these instructions a bit.  All
such cases are documented below, so read the release specific update
instructions for all releases newer than the one you already have before
you start the update.

In any case you should completely read *all* relevant update
instruction *before* starting the upgrade procedure.  Always make
sure you have a recent backup of your /kolab directory before you
attempt to upgrade Kolab.

The installation of the new packages works just as for the initial
installation.  Download the files as described above and run

# sh install-kolab.sh 2>&1 | tee /root/kolab-update.log

If you installed without Horde or F/B-View you need to drop the
corresponding flags again.

install-kolab.sh will usually automatically determine which packages
need to be built.  If you have made changes to configuration files or
an updated package includes configuration files which are usually
regenerated from files in /kolab/etc/kolab/templates/ the old
configuration file will be saved with the extension .rpmsave.  For
files generated from templates you just have to remove the rpmsave
file, because services will refuse to start if there still is an
rpmsave file, e.g.:

# rm /kolab/etc/clamav/*.conf.rpmsave

For other changed files (e.g. the template files themselves) you may
want to transfer your changes from the .rpmsave backup to the new files.

Then regenerate the configuration and restart Kolab with:

# /kolab/sbin/kolabconf
# /kolab/bin/openpkg rc all restart

Or alternatively if the Kolab server was stopped before the upgrade:

# /kolab/bin/openpkg rc openldap start
# /kolab/sbin/kolabconf
# /kolab/bin/openpkg rc all start


Generating your own 00INDEX.rdf for installations or upgrades
-------------------------------------------------------------

The source and binary downloads contain the 00INDEX.rdf file needed by
the "openpkg build" command used by install-kolab.sh to install or upgrade
a Kolab server.

If you already have your own set of binary packages from a previous build,
you can use these to create a full binary installer (e.g. to install the
packages on a second machine) or or a partial binary installer (for upgrades
where you only want to compile the new .src.rpm files instead of everything).

To generate this file, you always need all .src.rpm files, so link or copy
them in a new directory (needs to be writable by the kolab user of your
installation). After this you can link/copy the install-kolab.sh file and
your binary rpm files (e.g. from /kolab/RPM/PKG/) into this directory and
run the following command as user kolab or root to create the new
00INDEX.rdf file::

$ sh install-kolab.sh -X

If you want a pure binary installer, you can remove the .src.rpm files
now. To be able to use this directory for fresh installations (i.e. not
only for upgrades), you need to put the OpenPKG bootstrap file
(openpkg-*.src.sh or openpkg-<ARCH>-<OS>-kolab.rpm) into this directory,
too.


Upgrade from 2.2-rc3 to 2.2.0
-----------------------------

Nothing special has to be done for this upgrade.


Upgrade from 2.2-rc2 to 2.2-rc3
-------------------------------

You should regenerated the free/busy cache again, as described in the
upgrading instructions from 2.2-rc1 to 2.2-rc2.

The IMAP annotation /vendor/kolab/xfb-readable (introduced in 2.2-beta3)
was renamed to /vendor/kolab/pxfb-readable-for to reflect the actual meaning.
After the upgrade the old annotations are still readable, but unused by the
server. If you still need to write this annotation for some reason, you have
to add it to imapd.annotation_definitions.template and run kolabconf.


Upgrade from 2.2-rc1 to 2.2-rc2
-------------------------------

You have to regenerated the free/busy cache, which now can be done
automatically. First (optional, but recommended) step is to remove the
current cache below /kolab/var/kolab-freebusy/cache:

# su - kolab-n
$ rm -r /kolab/var/kolab-freebusy/cache/*

Now you can use the following command (still as user kolab-n):

$ PHP_AUTH_USER=manager PHP_AUTH_PW='managerpassword' /kolab/bin/php \
  -c /kolab/etc/apache/php.ini /kolab/var/kolab/www/freebusy/generatefb.php

As this will show the manager's password on the command line, you can
alternatively open https://yourserver.example.com/freebusy/generatefb.php
in a web browser and login as "manager". This needs "Allow unauthenticated
downloading of Free/Busy information" to be disabled, which is the default.


Upgrade from 2.2-beta3 to 2.2-rc1
---------------------------------

Updating the free/busy cache has to be triggered for all calendar
folders of all accounts:
- Users need to create or update an appointment in their folders.
- Resources can be invited to a new appointment or send them an update
  to an existing appointment.


Upgrade from 2.2-beta2 to 2.2-beta3
-----------------------------------

After upgrading, you should remove the package "kolab-horde-framework",
which is no longer needed:

# /kolab/bin/openpkg rpm -e kolab-horde-framework


Upgrade from 2.2-beta1 to 2.2-beta2
-----------------------------------

Before running install-kolab.sh, you should stop the running Kolab server and
remove some packages which got renamed or will no longer be needed by running
this command:

# /kolab/bin/openpkg rc all stop
# /kolab/bin/openpkg rpm -e --nodeps apache2 apache2-php getopt proftpd \
    pth sharutils kolab-horde-fbview kolab-resource-handlers

Ignore errors about pth or sharutils not being installed, these
were included in the beta1 release but not installed by default.


Upgrade from Kolab server 2.1 or before
---------------------------------------

Instructions for upgrading from Kolab server 2.0 will be added in a
future version of this document.  These instructions are for upgrading
from Kolab server 2.1.0 to 2.2.0:

0.  Make a backup of your installation and data stored inside /kolab

1.  Before upgrading the Kolab server must be stoped:

    # /kolab/bin/openpkg rc all stop

2.  Save the current ldap:

    Copy the contents of the openldap database, use a different output
    filename if you want. You should make sure that no other users can
    read the sensitive data contained in the ldif file, e.g. with umask:

    # umask 077
    # /kolab/sbin/slapcat > ~/kolab-2.1.ldif

3.  Some of the old Kolab packages must be removed to avoid conflicts
    during the upgrade process:

    # /kolab/bin/openpkg rpm -e --nodeps \
        kolabd kolab-webadmin kolab-horde-fbview kolab-horde-framework \
        kolab-resource-handlers getopt patch proftpd sharutils

4.  New versions of openpkg and openpkg-tools are needed for the upgrade, so
    you have to install them manually beforehand.

    As root, cd into the directory of kolab server 2.2 binary packages and run:

    # /kolab/bin/openpkg rpm -Uvh \
        ./openpkg-20071227-20071227.<ARCH>-<OS>-kolab.rpm
    # /kolab/bin/openpkg rpm -Uvh \
        ./openpkg-tools-1.4.6-20071231.<ARCH>-<OS>-kolab.rpm

    If you do not have binary packages for you platform, you have to build
    them from source first. As root, cd into the Kolab server 2.2 source
    directory and run:

    # /kolab/bin/openpkg rpm --rebuild ./openpkg-20071227-20071227.src.rpm
    # /kolab/bin/openpkg rpm -Uvh \
        /kolab/RPM/PKG/openpkg-20071227-20071227.<ARCH>-<OS>-kolab.rpm
    # /kolab/bin/openpkg rpm --rebuild ./openpkg-tools-1.4.6-20071231.src.rpm
    # /kolab/bin/openpkg rpm -Uvh \
        /kolab/RPM/PKG/openpkg-tools-1.4.6-20071231.<ARCH>-<OS>-kolab.rpm

    (<ARCH> and <OS> must be replaced by the correct values for your system).

5.  Start the standard upgrade (as described above):

    # sh install-kolab.sh 2>&1 | tee /root/kolab-update.log

6.  Before starting the LDAP server the database must be restored from
    the ldif:

    # rm /kolab/var/openldap/openldap-data/*
    # /kolab/sbin/slapadd -l ~/kolab-2.1.ldif

7.  The format of the TLS session cache changed, therefore you have truncated
    it to zero length:

    # > /kolab/var/imapd/tls_sessions.db

8   Check /kolab/etc/kolab/kolab.conf and merge new entries from
    kolab.conf.rpmnew manually!

9.  Remove all *.conf.rpmsave files in the subdirectories of
    /kolab/etc/ as described above.

10. Start the OpenLDAP, generate the configuration files and start the
    Kolab server:

    # /kolab/bin/openpkg rc openldap start
    # /kolab/sbin/kolabconf
    # /kolab/bin/openpkg rc all start

11. After the successful upgrade some cleanup can be done, by
    removing obsolete files/directories:

    # rm -r /kolab/etc/resmgr
    # rm -r /kolab/etc/proftpd
    # rm -r /kolab/var/kolab/www/freebusy/cache/*

12. The free/busy cache has to be regenerated for all calendar folders
    of all accounts, see "Upgrade from 2.2-rc1 to 2.2-rc2" in this file.

Additional hints may be available in the Kolab wiki:
http://wiki.kolab.org/index.php/Kolab2_Upgrading

Direct upgrade from Kolab1 is not supported. We suggest that you back
up your IMAP store, install Kolab2 and manually recreate user accounts
and then restore the IMAP data from the backup.


Known problems and workarounds
------------------------------

    - Your system (C library) has to support all languages you want to have
      available in the web admin interface and fbview. For most languages you
      have to use the non-UTF-8 and non-euro locales, i.e. de_DE, fr_FR,
      it_IT, nl_NL instead of e.g. de_DE at euro. For fbview some languages need
      a UTF-8 locale, e.g. ja_JP.UTF-8 for Japanese.
      See kolab/issue2732 (Horde and Web Admin Interface Language Selection
      depends on OS locale support) for details.

    - If login on https://yourserver.example.com/fbview and triggering
      free/busy regeneration does not work, try as user kolab:

        /kolab/bin/php -r 'imap_open("{localhost:143/notls}", "" ,"");'

      If it yields "Segmentation fault (core dumped)", then there probably is
      a conflict between a dynamically loaded libdb3 from your system and a
      statically linked libdb4 from the OpenpPKG php package. If it yields a
      "PHP Warning: ...", this part of the system works correctly.

      One reason for such a conflict could be the mere presence of
      /lib/libnss_db.so.*, which is installed on some distributions by
      default. On Debian systems it is contained in the package "libnss-db".
      If you really need this library, you could work around the loading of
      libdb3 by placing a symbolic link with the correct name in /kolab/lib,
      e.g.:

        ldd /lib/libnss_db.so.2
                libnss_files.so.2 => /lib/tls/libnss_files.so.2 (0xb7f16000)
           ---> libdb3.so.3 => /usr/lib/libdb3.so.3 (0xb7e6b000)
                libc.so.6 => /lib/tls/libc.so.6 (0xb7d36000)
                /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
        ln -s /dev/null /kolab/lib/libdb3.so.3

      See kolab/issue1607 (need to replace gdbm for pfbcache, because of
      license clash gdbm vs php) for details.

    - /kolab/etc/kolab/kolab_bootstrap -b fails to start the temporary
      slapd on Linux 2.4 kernels if binaries compiled on Linux 2.6 (as
      provided on kolab.org) are used. See kolab/issue1795 for details.

    - Under some circumstance the Kolab server may not create or delete
      users or update the configuration after changes have been made in
      the web interface.  This happens most often immediately after the
      bootstrap.  In that case restart the kolabd:

        /kolab/bin/openpkg rc kolabd restart

      If user accounts are still not created or deleted, you can try removing
      the file /kolab/var/kolab/mailbox-uidcache.db and restarting kolabd.

      See kolab/issue1068 (Mailboxes are not created until kolabd restart)
      and kolab/issue1098 (Changes in the service tab are not accepted after
      bootstrap) for details.

    - If modifying or deleting of address book entries doesn't work,
      restarting openldap can help, see kolab/issue854 for details.

    - There is a report that the manager can only see users in the primary
      domain, see kolab/issue1485. We can't reproduce this problem, please
      tell us if you can.

    - Calendar folders for group/resource accounts can't be created for
      domains which were added after bootstrap, i.e. via the web admin
      interface. See kolab/issue1313 for details.

    - When deleting domains via the web admin interface, the corresponding
      LDAP data and IMAP spool stay on the server and have to be deleted
      manually. See kolab/issue1571 and kolab/issue1576 for details.

    - A domain maintainer can not always edit the email aliases for a user,
      even if the user and the alias is in domains the domain maintainer has
      access to. See kolab/issue2825 for details.


$Id: README.1st,v 1.90 2008/07/10 12:41:32 thomas Exp $
-------------- next part --------------
Kolab Server 2.2 Release Notes
==============================
(Version 20080711, Kolab Server 2.2.0)

For upgrading and installation instructions, please refer to
the 1st.README file in the package directory.
Upgrading from Kolab server 2.1 is not yet documented.


Differences between Kolab 2.1 and 2.2:

    - Upgrade of central Kolab server components

	The Apache server shipped with the Kolab server has been
	upgraded to Apache-2.2.*. At the same time the system was
	switched to PHP5.

	Postfix got upgraded to 2.4.* which removes the need for
	special Kolab patches which were integrated upstream.

	The Cyrus IMAP server was updated to 2.3.* also removing the
	need for some, though not all, Kolab specific patches.

    - Inclusion of the web based Horde Groupware client

	The Kolab server now provides a web client that supports all
	the groupware features known from Outlook and Kontact. Thus
	users are less dependent on their local client and can access
	their groupware data from anywhere in the world provided they
	have a standard browser available.

    - Structural improvements

	Several components of the Kolab server got restructured so
	that porting the Kolab server to distributions other than
	OpenPKG got easier. This also improves the development model
	in general.

    - Improvements, bugfixes and upgraded software components

	The 2.2 release received many improvements and bugfixes for
	issues found in earlier versions. Additionally all software
	components have been upgraded to new upstream versions.
	The specifics are described below.


Changes between 2.2-rc-3 and 2.2.0

    - clamav-0.93.3-20080708

	New upstream version, fixes denial of service.

    - fbview-horde-3.2_rc3-20080605

	Allow login if public imap service is disabled.

    - fbview-kronolith-2.2_rc2-20080710

	kolab/issue2872 (Building horde packages fails if different version
	                 already installed)

    - horde-imp-kolab-4.2_rc3-20080710

	kolab/issue2872 (Building horde packages fails if different version
	                 already installed)

    - horde-ingo-kolab-1.2_rc2-20080710

	kolab/issue2872 (Building horde packages fails if different version
	                 already installed)

    - horde-kolab-3.2_rc3-20080707

	Allow login if public imap service is disabled.

	kolab/issue2831 (SECURITY: <horde-3.2.1 affected by XSS issue)

    - horde-kronolith-kolab-2.2_rc2-20080710

	kolab/issue2872 (Building horde packages fails if different version
	                 already installed)

    - horde-mnemo-kolab-2.2_rc2-20080710

	kolab/issue2872 (Building horde packages fails if different version
	                 already installed)

    - horde-nag-kolab-2.2_rc2-20080710

	kolab/issue2872 (Building horde packages fails if different version
	                 already installed)

    - horde-passwd-kolab-3.0.1-20080710

	kolab/issue2872 (Building horde packages fails if different version
	                 already installed)

    - horde-turba-kolab-2.2_rc3-20080710

	kolab/issue2832 (SECURITY: <turba-2.2.1 affected by XSS issue)
	kolab/issue2872 (Building horde packages fails if different version
	                 already installed)

    - install-kolab.sh

	Adjusted version number.

	Install fbview-kronolith and horde-kolab-client by default, unless
	excluded with "-x fbview-kronolith" or "-x horde-kolab-client".

	Removed obsolete options -F/-H/-i.

	kolab/issue2727 (install-kolab.sh: tar uses -O which is not
	                 implemented in Solaris' tar)
	kolab/issue2747 (Installation of ix86 binaries fails on amd64 system)

    - kolabconf-2.2.0-20080709

	Adjusted version number.

    - kolabd-2.2.0-20080709

	Adjusted version number (and fixed typo).

	Removed unused fbview.conf.template file.

	kolab_bootstrap: Use Net::Domain to determine fqdn more reliably
	and make sure suggested domain name contains a dot.

	kolab.conf, quotawarning and templates are owned by kolab instead of
	kolab-n to improve security, and kolab.conf is marked as (noreplace)
	so it does not overwrite the existing config file during upgrades.

	Updated check of free ports during kolab_bootstrap.

	kolab/issue1895 (switch from virtual_maps to virtual_alias_maps)
	kolab/issue2855 (Can create folder while logging in as user without
	                 domain name)

    - kolab-filter-2.2.0-20080709

	Adjusted version number.

    - kolab-freebusy-2.2.0-20080709

	Adjusted version number.

    - kolab-webadmin-2.2.0-20080709

	Adjusted version number.

	Fix deleting of domains and kolab hosts.

	kolab/issue2739 (Some characters are not allowed in users
	                 fax-/phonenumbers despite the description
	                 in the error)

    - perl-kolab-2.2.0-20080709

	Adjusted version number.

	kolab/issue2517 (group accounts lead to more rights than necessary for
	                 the "calendar" user)
	kolab/issue2760 (Deleting shared folders does not work)
	kolab/issue2827 (Deleting users does not work reliably)

    - php-kolab-2.2.0-20080711

	Adjusted version number.

	kolab/issue2660 (Invitation for event series not accept automatically)
	kolab/issue2734 (Automatic ressources decline changed overlapping event
	                 time)


    Packages in the OpenPKG based Kolab server release:

    - Kolab packages:

      Updated:

	fbview-horde-3.2_rc3-20080605
	fbview-kronolith-2.2_rc2-20080710
	horde-imp-kolab-4.2_rc3-20080710
	horde-ingo-kolab-1.2_rc2-20080710
	horde-kolab-3.2_rc3-20080707
	horde-kronolith-kolab-2.2_rc2-20080710
	horde-mnemo-kolab-2.2_rc2-20080710
	horde-nag-kolab-2.2_rc2-20080710
	horde-passwd-kolab-3.0.1-20080710
	horde-turba-kolab-2.2_rc3-20080710
	kolab-filter-2.2.0-20080709
	kolab-freebusy-2.2.0-20080709
	kolab-webadmin-2.2.0-20080709
	kolabconf-2.2.0-20080709
	kolabd-2.2.0-20080709
	perl-kolab-2.2.0-20080709
	php-kolab-2.2.0-20080711

      Unchanged:

	PEAR-Auth_SASL-1.0.2-1
	PEAR-Date-1.4.7-1
	PEAR-HTTP_Request-1.4.1-1
	PEAR-Log-1.9.9-1
	PEAR-Mail-1.1.14-1
	PEAR-Mail_Mime-1.3.1-1
	PEAR-Net_IMAP-1.1.0beta1-1
	PEAR-Net_LMTP-1.0.1-1
	PEAR-Net_SMTP-1.2.10-1
	PEAR-Net_Sieve-1.1.5-1
	PEAR-Net_Socket-1.0.6-1
	PEAR-Net_URL-1.0.15-1
	horde-framework-kolab-3.2_rc3-20080405
	horde-kolab-client-0.99-20080405
	openldap-2.3.41-20080424
	php-channel-horde-1.0-1
	php-smarty-2.6.18-20070607

    - OpenPKG packages:

      Updated:

	clamav-0.93.3-20080708

      Unchanged:

	amavisd-2.5.3-20080101
	apache-2.2.8-20080118
	apache-php-5.2.6-20080514_kolab
	apr-1.2.12-20080101
	autoconf-2.61-20080101
	automake-1.10-20080101
	bc-1.06-20080101
	binutils-2.18-20080101
	bison-2.3-20080101
	bzip2-1.0.4-20080101
	config-20060923-20080101
	curl-7.17.1-20080101
	db-4.5.20.2-20070628
	diffutils-2.8.7-20080101
	expat-2.0.1-20080101
	file-4.23-20080101
	flex-2.5.34-20080101
	freetype-2.3.5-20080101
	fsl-1.7.0-20080101
	gcc-4.2.2-20080101
	gd-2.0.35-20080101
	gettext-0.17-20080101
	gmp-4.2.2-20080101
	grep-2.5.3-20080101
	groff-1.19.2-20080101
	gzip-1.3.12-20080101
	imap-2006k-20080101
	imapd-2.3.11-20080101_kolab4
	jpeg-6b-20080101
	libiconv-1.12-20080101
	libmcrypt-2.5.8-20080101
	libxml-2.6.31-20080111
	libxslt-1.1.22-20080101
	lzo-2.02-20080101
	m4-1.4.9-20080101
	make-3.81-20080101
	mhash-0.9.9-20080101
	mm-1.4.2-20080101
	ncurses-5.6.20080112-20080113
	openpkg-20071227-20071227
	openpkg-tools-1.4.6-20071231
	openssl-0.9.8g-20080101
	pcre-7.5-20080110
	perl-5.10.0-20080103
	perl-comp-5.10.0-20080110
	perl-conv-5.10.0-20080101
	perl-crypto-5.10.0-20080101
	perl-db-5.10.0-20080118
	perl-dns-5.10.0-20080101
	perl-ds-5.10.0-20080104
	perl-ldap-5.10.0-20080101
	perl-locale-5.10.0-20080112
	perl-mail-5.10.0-20080117
	perl-module-5.10.0-20080101
	perl-net-5.10.0-20080101
	perl-openpkg-5.10.0-20080109
	perl-parse-5.10.0-20080117
	perl-ssl-5.10.0-20080101
	perl-stats-5.10.0-20080101
	perl-sys-5.10.0-20080101
	perl-term-5.10.0-20080116
	perl-text-5.10.0-20080101
	perl-time-5.10.0-20080101
	perl-util-5.10.0-20080116
	perl-www-5.10.0-20080103
	perl-xml-5.10.0-20080101
	php-5.2.6-20080514_kolab
	pkgconfig-0.23-20080117
	png-1.2.24-20080101
	postfix-2.4.6-20080101_kolab
	procmail-3.22-20080101
	readline-5.2.12-20080101
	sasl-2.1.22-20080101
	sed-4.1.5-20080101
	spamassassin-3.2.4-20080107
	texinfo-4.11-20080101
	zlib-1.2.3-20080101


Changes between 2.2-rc-2 and 2.2-rc-3

    - apache-php-5.2.6-20080514_kolab

	New upstream version, fixes various security issues.

	kolab/issue2519 (Add functionality PHP : GetMYRIGHT)

    - clamav-0.93-20080414

	New upstream version, fixes various security issues.

    - fbview-horde-3.2_rc3-20080523

	Removed manager password from fbview config file.

	kolab/issue2134 ([Horde]Unable to send message with attachments)

    - fbview-kronolith-2.2_rc2-20080523

	New upstream package with adjusted patches.

    - install-kolab.sh

	kolab/issue2371 (install-kolab.sh script incompatible with /bin/sh of
	                 e.g. Solaris 10)
	kolab/issue2591 (NTLM support in Cyrus SASL)
	kolab/issue2686 (unquoted wildcards in install-kolab.sh)

    - horde-framework-kolab-3.2_rc3-20080405

	Rename .xpfb to .pxfb.

	kolab/issue2587 (ifb retrieval does not work for aliases anymore)
	kolab/issue2588 (whole day event with show-time-as free gets into the
	                 pfb)

    - horde-kolab-3.2_rc3-20080405

	kolab/issue2134 ([Horde]Unable to send message with attachments)

    - imapd-2.3.11-20080101_kolab4

	kolab/issue1824 (cyrus-imapd segfaults on x86_64)
	kolab/issue2443 (kontact aborts sieve when imapd sends capabilities
	                 after starttls)

    - kolabd-2.1.99-20080521

	Rename .xpfb to .pxfb and xfb-readable to pxfb-readable-for

	kolab/issue2244 (SpamAssassin uses DNS blacklists)
	kolab/issue2436 (delprune setting in cyrus.conf)
	kolab/issue2586 (SPAM filtering: HELO_LOCALHOST score default too high)

    - kolab-filter-2.2.rc3-20080521

	Rename .xpfb to .pxfb.

    - kolab-freebusy-2.2.rc3-20080521

	kolab/issue2536 (generatefb.php doesn't work with folders containing
	                 umlauts)

    - kolab-webadmin-2.1.99-20080521

	Fixes for XHTML strict

	kolab/issue2505 (update of the french translation for kolab-server)
	kolab/issue2538 (Make the location of the Smarty compile directory
	                 configurable)
	kolab/issue2569 (rename of services to settings makes welcome screen
	                 fail)
	kolab/issue2575 (Make background of favicon transparent)

    - openldap-2.3.41-20080424

	New upstream version, fixes various security issues.

    - perl-kolab-2.2.rc3-20080521

	Added Fedora-DS backend (inactive by default)

	kolab/issue2466 (How should Kolab Filter handle mails from privileged
	                 networks?)

    - php-5.2.6-20080514_kolab

	New upstream version, fixes various security issues.

	kolab/issue2519 (Add functionality PHP : GetMYRIGHT)

    - php-kolab-2.2.rc3-20080521

	Rename .xpfb to .pxfb.

	kolab/issue2549 (Resource manager creates events in wrong account)

    - postfix-2.4.6-20080101_kolab

	kolab/issue2346 (Compilation of postfix fails on CentOS 5.1 64Bit)


    Packages in the OpenPKG based Kolab server release:

    - Kolab packages:

      Updated:

	fbview-horde-3.2_rc3-20080523
	fbview-kronolith-2.2_rc2-20080523
	horde-framework-kolab-3.2_rc3-20080405
	horde-imp-kolab-4.2_rc3-20080405
	horde-ingo-kolab-1.2_rc2-20080405
	horde-kolab-3.2_rc3-20080405
	horde-kolab-client-0.99-20080405
	horde-kronolith-kolab-2.2_rc2-20080405
	horde-mnemo-kolab-2.2_rc2-20080405
	horde-nag-kolab-2.2_rc2-20080405
	horde-passwd-kolab-3.0.1-20080405
	horde-turba-kolab-2.2_rc3-20080405
	kolab-filter-2.2.rc3-20080521
	kolab-freebusy-2.2.rc3-20080521
	kolab-webadmin-2.1.99-20080521
	kolabconf-2.2.rc3-20080521
	kolabd-2.1.99-20080521
	openldap-2.3.41-20080424
	perl-kolab-2.2.rc3-20080521
	php-kolab-2.2.rc3-20080521

      Unchanged:

	PEAR-Auth_SASL-1.0.2-1
	PEAR-Date-1.4.7-1
	PEAR-HTTP_Request-1.4.1-1
	PEAR-Log-1.9.9-1
	PEAR-Mail-1.1.14-1
	PEAR-Mail_Mime-1.3.1-1
	PEAR-Net_IMAP-1.1.0beta1-1
	PEAR-Net_LMTP-1.0.1-1
	PEAR-Net_SMTP-1.2.10-1
	PEAR-Net_Sieve-1.1.5-1
	PEAR-Net_Socket-1.0.6-1
	PEAR-Net_URL-1.0.15-1
	php-channel-horde-1.0-1
	php-smarty-2.6.18-20070607

    - OpenPKG packages:

      Updated:

	apache-php-5.2.6-20080514_kolab
	clamav-0.93-20080414
	imapd-2.3.11-20080101_kolab4
	php-5.2.6-20080514_kolab
	postfix-2.4.6-20080101_kolab

      Unchanged:

	amavisd-2.5.3-20080101
	apache-2.2.8-20080118
	apr-1.2.12-20080101
	autoconf-2.61-20080101
	automake-1.10-20080101
	bc-1.06-20080101
	binutils-2.18-20080101
	bison-2.3-20080101
	bzip2-1.0.4-20080101
	config-20060923-20080101
	curl-7.17.1-20080101
	db-4.5.20.2-20070628
	diffutils-2.8.7-20080101
	expat-2.0.1-20080101
	file-4.23-20080101
	flex-2.5.34-20080101
	freetype-2.3.5-20080101
	fsl-1.7.0-20080101
	gcc-4.2.2-20080101
	gd-2.0.35-20080101
	gettext-0.17-20080101
	gmp-4.2.2-20080101
	grep-2.5.3-20080101
	groff-1.19.2-20080101
	gzip-1.3.12-20080101
	imap-2006k-20080101
	jpeg-6b-20080101
	libiconv-1.12-20080101
	libmcrypt-2.5.8-20080101
	libxml-2.6.31-20080111
	libxslt-1.1.22-20080101
	lzo-2.02-20080101
	m4-1.4.9-20080101
	make-3.81-20080101
	mhash-0.9.9-20080101
	mm-1.4.2-20080101
	ncurses-5.6.20080112-20080113
	openpkg-20071227-20071227
	openpkg-tools-1.4.6-20071231
	openssl-0.9.8g-20080101
	pcre-7.5-20080110
	perl-5.10.0-20080103
	perl-comp-5.10.0-20080110
	perl-conv-5.10.0-20080101
	perl-crypto-5.10.0-20080101
	perl-db-5.10.0-20080118
	perl-dns-5.10.0-20080101
	perl-ds-5.10.0-20080104
	perl-ldap-5.10.0-20080101
	perl-locale-5.10.0-20080112
	perl-mail-5.10.0-20080117
	perl-module-5.10.0-20080101
	perl-net-5.10.0-20080101
	perl-openpkg-5.10.0-20080109
	perl-parse-5.10.0-20080117
	perl-ssl-5.10.0-20080101
	perl-stats-5.10.0-20080101
	perl-sys-5.10.0-20080101
	perl-term-5.10.0-20080116
	perl-text-5.10.0-20080101
	perl-time-5.10.0-20080101
	perl-util-5.10.0-20080116
	perl-www-5.10.0-20080103
	perl-xml-5.10.0-20080101
	pkgconfig-0.23-20080117
	png-1.2.24-20080101
	procmail-3.22-20080101
	readline-5.2.12-20080101
	sasl-2.1.22-20080101
	sed-4.1.5-20080101
	spamassassin-3.2.4-20080107
	texinfo-4.11-20080101
	zlib-1.2.3-20080101


Changes between 2.2-rc-1 and 2.2-rc-2

    - clamav-0.92.1-20080213

	New upstream version, fixes various security issues.

    - horde-framework-kolab-3.2_rc1-20080311

	kolab/issue2521 (an event breaking lib/Horde/Kolab/Freebusy.php)

    - imapd-2.3.11-20080101_kolab2

	kolab/issue2535 (group:distributionlist at example.com doesn't work for
	                 Cyrus IMAP ACLs)
	kolab/issue2541 (openpkg rpm -e imapd removes annotations.db and
	                 mailboxes.db)

    - kolabconf-2.2.rc2-20080314

	kolab/issue1550 (Masquerade problem)
	kolab/issue2446 (Make the used syslog facility configureable)

    - kolabd-2.1.99-20080314

	kolabdcachetool: Fix location of graveyard caches.

	Enforce SSL for horde and fbview and corrected Location entries.

	Use https for freebusy look-ups by the resmgr (resmgr didn't work
	when "FreeBusy Service via HTTP" was disabled).

	kolab/issue1693 (Automatically trigger f/b cache regeneration)
	kolab/issue2350 (Email from buggy Lotus notes client not accepted by
	                 Cyrus)
	kolab/issue2358 (mismatch between cyrus-admins and cyrus-admin)
	kolab/issue2446 (Make the used syslog facility configureable)
	kolab/issue2466 (How should Kolab Filter handle mails from privileged
	                 networks?)
	kolab/issue2507 (move session_vars.php to sysconfig directory)

    - kolab-freebusy-2.2.rc2-20080314

	kolab/issue1693 (Automatically trigger f/b cache regeneration)

    - kolab-webadmin-2.1.99-20080314

	Corrections in the Dutch translation.

	Better LDAP filter when listing admins and maintainers.

	kolab/issue2203 (About Kolab does not list new server components)
	kolab/issue2329 (Domain Maintainer cannot create users)
	kolab/issue2437 (Change name of service tab to settings)
	kolab/issue2505 (update of the french translation for kolab-server)
	kolab/issue2507 (move session_vars.php to sysconfig directory)

    - perl-kolab-2.2.rc2-20080314

	kolab/issue2358 (mismatch between cyrus-admins and cyrus-admin)
	kolab/issue2478 (kolabd memory leak)

    - php-kolab-2.2.rc2-20080314

	Fixed determination of calendar folder owner.  Resmgr wasn't
	able to trigger freebusy list generation.

	kolab/issue1272 (From: header in vacation messages is marked as
	                 "Untrusted")
	kolab/issue1693 (Automatically trigger f/b cache regeneration)
	kolab/issue2466 (How should Kolab Filter handle mails from privileged
	                 networks?)
	kolab/issue2467 (Kolab Filter ignores configuration in 2.2 RC1)
	kolab/issue2487 (Incorrect variable name $fbfilename within
	                 Freebusy/Cache.php)
	kolab/issue2495 (The reply to an invitation with umlauts of a group
	                 account doesn't display the umlauts.)


    Packages in the OpenPKG based Kolab server release:

    - Kolab packages:

      Updated:

	horde-framework-kolab-3.2_rc1-20080311
	kolab-filter-2.2.rc2-20080314
	kolab-freebusy-2.2.rc2-20080314
	kolab-webadmin-2.1.99-20080314
	kolabconf-2.2.rc2-20080314
	kolabd-2.1.99-20080314
	perl-kolab-2.2.rc2-20080314
	php-kolab-2.2.rc2-20080314

      Unchanged:

	PEAR-Auth_SASL-1.0.2-1
	PEAR-Date-1.4.7-1
	PEAR-HTTP_Request-1.4.1-1
	PEAR-Log-1.9.9-1
	PEAR-Mail-1.1.14-1
	PEAR-Mail_Mime-1.3.1-1
	PEAR-Net_IMAP-1.1.0beta1-1
	PEAR-Net_LMTP-1.0.1-1
	PEAR-Net_SMTP-1.2.10-1
	PEAR-Net_Sieve-1.1.5-1
	PEAR-Net_Socket-1.0.6-1
	PEAR-Net_URL-1.0.15-1
	fbview-horde-3.2_rc1-20071201
	fbview-kronolith-2.2_rc1-20071129
	horde-imp-kolab-4.2_rc1-20071128
	horde-ingo-kolab-1.2_rc1-20071128
	horde-kolab-3.2_rc1-20071201
	horde-kolab-client-0.99-20071002
	horde-kronolith-kolab-2.2_rc1-20071129
	horde-mnemo-kolab-2.2_rc1-20071128
	horde-nag-kolab-2.2_rc1-20071128
	horde-passwd-kolab-3.0.1-20071001
	horde-turba-kolab-2.2_rc1-20071128
	php-channel-horde-1.0-1
	php-smarty-2.6.18-20070607

    - OpenPKG packages:

      Updated:

	clamav-0.92.1-20080213
	imapd-2.3.11-20080101_kolab2

      Unchanged:

	amavisd-2.5.3-20080101
	apache-2.2.8-20080118
	apache-php-5.2.5-20080114
	apr-1.2.12-20080101
	autoconf-2.61-20080101
	automake-1.10-20080101
	bc-1.06-20080101
	binutils-2.18-20080101
	bison-2.3-20080101
	bzip2-1.0.4-20080101
	config-20060923-20080101
	curl-7.17.1-20080101
	db-4.5.20.2-20070628
	diffutils-2.8.7-20080101
	expat-2.0.1-20080101
	file-4.23-20080101
	flex-2.5.34-20080101
	freetype-2.3.5-20080101
	fsl-1.7.0-20080101
	gcc-4.2.2-20080101
	gd-2.0.35-20080101
	gettext-0.17-20080101
	gmp-4.2.2-20080101
	grep-2.5.3-20080101
	groff-1.19.2-20080101
	gzip-1.3.12-20080101
	imap-2006k-20080101
	jpeg-6b-20080101
	libiconv-1.12-20080101
	libmcrypt-2.5.8-20080101
	libxml-2.6.31-20080111
	libxslt-1.1.22-20080101
	lzo-2.02-20080101
	m4-1.4.9-20080101
	make-3.81-20080101
	mhash-0.9.9-20080101
	mm-1.4.2-20080101
	ncurses-5.6.20080112-20080113
	openldap-2.3.39-20071130
	openpkg-20071227-20071227
	openpkg-tools-1.4.6-20071231
	openssl-0.9.8g-20080101
	pcre-7.5-20080110
	perl-5.10.0-20080103
	perl-comp-5.10.0-20080110
	perl-conv-5.10.0-20080101
	perl-crypto-5.10.0-20080101
	perl-db-5.10.0-20080118
	perl-dns-5.10.0-20080101
	perl-ds-5.10.0-20080104
	perl-ldap-5.10.0-20080101
	perl-locale-5.10.0-20080112
	perl-mail-5.10.0-20080117
	perl-module-5.10.0-20080101
	perl-net-5.10.0-20080101
	perl-openpkg-5.10.0-20080109
	perl-parse-5.10.0-20080117
	perl-ssl-5.10.0-20080101
	perl-stats-5.10.0-20080101
	perl-sys-5.10.0-20080101
	perl-term-5.10.0-20080116
	perl-text-5.10.0-20080101
	perl-time-5.10.0-20080101
	perl-util-5.10.0-20080116
	perl-www-5.10.0-20080103
	perl-xml-5.10.0-20080101
	php-5.2.5-20080114
	pkgconfig-0.23-20080117
	png-1.2.24-20080101
	postfix-2.4.6-20080101
	procmail-3.22-20080101
	readline-5.2.12-20080101
	sasl-2.1.22-20080101
	sed-4.1.5-20080101
	spamassassin-3.2.4-20080107
	texinfo-4.11-20080101
	zlib-1.2.3-20080101


Changes between 2.2-beta-3 and 2.2-rc-1

    All packages except for openldap and db were upgraded to OpenPKG-CURRENT
    (as of 20080118). The new imapd package was modified to behave like in
    previous server releases, i.e. to not send capabilities after STARTTLS,
    see kolab/issue2443 for details.

    - kolabconf-2.2.rc1-20080204

	Added missing newlines in kolabconf -h

    - kolabd-2.1.99-20080204

	deluser: add missing @ to bindir variable

	Updates for SUSE (support for <= 10.1 is completely dropped)

	kolab/issue26   (Allow to bind to specific IPs)

    - kolab-filter-2.2.rc1-20080204

	kolab/issue2425 (Undefined variable: reject_forged_from_header
	                 reported in fatal.log)

    - kolab-webadmin-2.1.99-20080204

	Fixed some variable initialisations.

	Correction in the Dutch translation.

	Link to favicon.ico so it is still used when running the web interface
	with a different path prefix.

	kolab/issue2439 (Explanation in the section Mail Filter Settings on
	                 the services tab not clear)

    - perl-kolab-2.2.rc1-20080204

	kolab/issue2411 (perl error in LDAP.pm)


    Packages in the OpenPKG based Kolab server release:

    - Kolab packages:

      Updated:

	imapd-2.3.11-20080101_kolab
	kolab-filter-2.2.rc1-20080204
	kolab-freebusy-2.2.rc1-20080204
	kolab-webadmin-2.1.99-20080204
	kolabconf-2.2.rc1-20080204
	kolabd-2.1.99-20080204
	openldap-2.3.39-20071130
	perl-kolab-2.2.rc1-20080204
	php-kolab-2.2.rc1-20080204

      Unchanged:

	PEAR-Auth_SASL-1.0.2-1
	PEAR-Date-1.4.7-1
	PEAR-HTTP_Request-1.4.1-1
	PEAR-Log-1.9.9-1
	PEAR-Mail-1.1.14-1
	PEAR-Mail_Mime-1.3.1-1
	PEAR-Net_IMAP-1.1.0beta1-1
	PEAR-Net_LMTP-1.0.1-1
	PEAR-Net_SMTP-1.2.10-1
	PEAR-Net_Sieve-1.1.5-1
	PEAR-Net_Socket-1.0.6-1
	PEAR-Net_URL-1.0.15-1
	fbview-horde-3.2_rc1-20071201
	fbview-kronolith-2.2_rc1-20071129
	horde-framework-kolab-3.2_rc1-20071129
	horde-imp-kolab-4.2_rc1-20071128
	horde-ingo-kolab-1.2_rc1-20071128
	horde-kolab-3.2_rc1-20071201
	horde-kolab-client-0.99-20071002
	horde-kronolith-kolab-2.2_rc1-20071129
	horde-mnemo-kolab-2.2_rc1-20071128
	horde-nag-kolab-2.2_rc1-20071128
	horde-passwd-kolab-3.0.1-20071001
	horde-turba-kolab-2.2_rc1-20071128
	php-channel-horde-1.0-1
	php-smarty-2.6.18-20070607

    - OpenPKG packages:

      Added:

	perl-locale-5.10.0-20080112
	perl-text-5.10.0-20080101

      Updated:

	amavisd-2.5.3-20080101
	apache-2.2.8-20080118
	apache-php-5.2.5-20080114
	apr-1.2.12-20080101
	autoconf-2.61-20080101
	automake-1.10-20080101
	bc-1.06-20080101
	binutils-2.18-20080101
	bison-2.3-20080101
	bzip2-1.0.4-20080101
	clamav-0.92-20080101
	config-20060923-20080101
	curl-7.17.1-20080101
	diffutils-2.8.7-20080101
	expat-2.0.1-20080101
	file-4.23-20080101
	flex-2.5.34-20080101
	freetype-2.3.5-20080101
	fsl-1.7.0-20080101
	gcc-4.2.2-20080101
	gd-2.0.35-20080101
	gettext-0.17-20080101
	gmp-4.2.2-20080101
	grep-2.5.3-20080101
	groff-1.19.2-20080101
	gzip-1.3.12-20080101
	imap-2006k-20080101
	jpeg-6b-20080101
	libiconv-1.12-20080101
	libmcrypt-2.5.8-20080101
	libxml-2.6.31-20080111
	libxslt-1.1.22-20080101
	lzo-2.02-20080101
	m4-1.4.9-20080101
	make-3.81-20080101
	mhash-0.9.9-20080101
	mm-1.4.2-20080101
	ncurses-5.6.20080112-20080113
	openpkg-20071227-20071227
	openpkg-tools-1.4.6-20071231
	openssl-0.9.8g-20080101
	pcre-7.5-20080110
	perl-5.10.0-20080103
	perl-comp-5.10.0-20080110
	perl-conv-5.10.0-20080101
	perl-crypto-5.10.0-20080101
	perl-db-5.10.0-20080118
	perl-dns-5.10.0-20080101
	perl-ds-5.10.0-20080104
	perl-ldap-5.10.0-20080101
	perl-mail-5.10.0-20080117
	perl-module-5.10.0-20080101
	perl-net-5.10.0-20080101
	perl-openpkg-5.10.0-20080109
	perl-parse-5.10.0-20080117
	perl-ssl-5.10.0-20080101
	perl-stats-5.10.0-20080101
	perl-sys-5.10.0-20080101
	perl-term-5.10.0-20080116
	perl-time-5.10.0-20080101
	perl-util-5.10.0-20080116
	perl-www-5.10.0-20080103
	perl-xml-5.10.0-20080101
	php-5.2.5-20080114
	pkgconfig-0.23-20080117
	png-1.2.24-20080101
	postfix-2.4.6-20080101
	procmail-3.22-20080101
	readline-5.2.12-20080101
	sasl-2.1.22-20080101
	sed-4.1.5-20080101
	spamassassin-3.2.4-20080107
	texinfo-4.11-20080101
	zlib-1.2.3-20080101

      Unchanged:

	db-4.5.20.2-20070628


Changes between 2.2-beta-2 and 2.2-beta-3:

    All packages except for openldap and db were upgraded to OpenPKG-CURRENT
    (as of 20071206). The package openldap-2.3.39-20071130 was created to
    fix security issues (CVE-2007-5707 and CVE-2007-5708) without upgrading
    to OpenLDAP 2.4.

    - kolabconf-2.2.beta3-20071207

	Fix the install location for kolabconf for the newest MakeMaker.

    - kolabd-2.1.99-20071203

	freebusy_logfile is now freebusy_logdir.

	Updated the template for the restructured kolab-freebusy package.

	Allow postfix smtp and smtps to bind to a specific IP, too.

	Support for the extended free/busy concept.

	Removed resource password handling which is unused since server 2.1.

	kolab/issue2134 ([Horde] Unable to send message with attachments)
	kolab/issue2206 (Multiple deliveries to distribution lists)
	kolab/issue2225 (notifyd logging going into fsl.log)
	kolab/issue2236 (Apache UID access broken)

    - kolab-filter-2.2.beta3-20071203

	Adapted to the restructured php-kolab/Kolab_Filter package.

	Removed resource password handling which is unused since server 2.1.

	kolab/issue2174 (Automatic Invitation Policy not working with invites
	                 as attachment)
	kolab/issue2177 (Better logging in kolabfilter and kolabmailboxfilter)

    - kolab-freebusy-2.2.beta3-20071130

	A fully restructured free/busy with the most recent free/busy
	concept implemented.

	kolab/issue799 (pfb php script cannot handle umlaut and dots in
	                foldernames correctly)
	kolab/issue898 (pfbs from several servers, are not combined into .ifb)

    - kolab-webadmin-2.1.99-20071203

	Improved some message strings.

	Updated German translations.

	Removed resource password handling which is unused since server 2.1.

	Removed obsolete explanation about enabling legacy services.

	kolab/issue1711 (extra space after first name when editing users or
	                 admins)
	kolab/issue1912 (some field descriptions missing in web admin
	                 interface)

    - perl-kolab-2.2.beta3-20071130

	Show component and log level when sending debug log to stdout.

	kolab/issue1313 (resmngr cannot create calendar folder in multidomain
	                 setup)

    - php-kolab-2.2.beta3-20071207

	A fully restructured free/busy with the most recent free/busy
	concept implemented.

	Restructured Kolab_Filter package with the focus on error
	handling and unit testing.

	Fix removal of the empty line between header and body. Added a
	unit test for that.

	kolab/issue1313 (resmngr cannot create calendar folder in multidomain
	                 setup)

    - horde-framework-kolab-3.2_rc1-20071129

	New functionality required for kolab-freebusy.

	Support for the extended free/busy concept.

	kolab/issue2128 (Building horde-framework-kolab without http access
	                 fails)
	kolab/issue2134 ([Horde] Unable to send message with attachments)
	kolab/issue2135 ([horde/turba] Turba should support some more contact
	                 attributes)
	kolab/issue2138 (Horde creates events in main inbox)
	kolab/issue2144 (Calendar items of shared calendar not appearing)

    - horde-kolab-3.2_rc1-20071201

	kolab/issue2101 ([horde] can't delete categories)

    - horde-kronolith-kolab-2.2_rc1-20071129

	kolab/issue2138 (Horde creates events in main inbox)

    - horde-turba-kolab-2.2_rc1-20071128

	kolab/issue2040 (Horde: resouces are not displayed in address book)
	kolab/issue2135 ([horde/turba] Turba should support some more contact
	                 attributes)

    - fbview-kronolith-2.2_rc1-20071129

	Support for the extended free/busy concept.


    Packages in the OpenPKG based Kolab server release:

    - Kolab packages:

      Removed:

	kolab-horde-framework (now horde-framework-kolab)

      Added:

	php-channel-horde-1.0-1

      Updated:

	fbview-horde-3.2_rc1-20071201
	fbview-kronolith-2.2_rc1-20071129
	horde-framework-kolab-3.2_rc1-20071129
	horde-imp-kolab-4.2_rc1-20071128
	horde-ingo-kolab-1.2_rc1-20071128
	horde-kolab-3.2_rc1-20071201
	horde-kronolith-kolab-2.2_rc1-20071129
	horde-mnemo-kolab-2.2_rc1-20071128
	horde-nag-kolab-2.2_rc1-20071128
	horde-turba-kolab-2.2_rc1-20071128
	kolab-filter-2.2.beta3-20071203
	kolab-freebusy-2.2.beta3-20071130
	kolab-webadmin-2.1.99-20071203
	kolabconf-2.2.beta3-20071207
	kolabd-2.1.99-20071203
	openldap-2.3.39-20071130
	perl-kolab-2.2.beta3-20071130
	php-kolab-2.2.beta3-20071207

      Unchanged:

	PEAR-Auth_SASL-1.0.2-1
	PEAR-Date-1.4.7-1
	PEAR-HTTP_Request-1.4.1-1
	PEAR-Log-1.9.9-1
	PEAR-Mail-1.1.14-1
	PEAR-Mail_Mime-1.3.1-1
	PEAR-Net_IMAP-1.1.0beta1-1
	PEAR-Net_LMTP-1.0.1-1
	PEAR-Net_SMTP-1.2.10-1
	PEAR-Net_Sieve-1.1.5-1
	PEAR-Net_Socket-1.0.6-1
	PEAR-Net_URL-1.0.15-1
	horde-kolab-client-0.99-20071002
	horde-passwd-kolab-3.0.1-20071001
	php-smarty-2.6.18-20070607

    - OpenPKG packages:

      Updated:

	apache-2.2.6-20071121
	apache-php-5.2.5-20071206
	apr-1.2.12-20071126
	binutils-2.18-20071111
	curl-7.17.1-20071030
	flex-2.5.33-20071104
	fsl-1.7.0-20071027
	gcc-4.2.2-20071031
	gettext-0.17-20071107
	gmp-4.2.2-20071107
	imap-2006j2-20071028
	imapd-2.3.10-20071206
	libiconv-1.12-20071112
	libxml-2.6.30-20071205
	ncurses-5.6.20071201-20071202
	openpkg-20071030-20071030
	openssl-0.9.8g-20071104
	pcre-7.4-20071101
	perl-5.8.8-20071108
	perl-comp-5.8.8-20071201
	perl-crypto-5.8.8-20071110
	perl-db-5.8.8-20071029
	perl-ds-5.8.8-20071114
	perl-mail-5.8.8-20071206
	perl-module-5.8.8-20071206
	perl-net-5.8.8-20071203
	perl-parse-5.8.8-20071129
	perl-ssl-5.8.8-20071026
	perl-stats-5.8.8-20071204
	perl-sys-5.8.8-20071124
	perl-time-5.8.8-20071204
	perl-util-5.8.8-20071203
	perl-www-5.8.8-20071201
	perl-xml-5.8.8-20071121
	php-5.2.5-20071206
	png-1.2.23-20071109
	postfix-2.4.6-20071027
	procmail-3.22-20071027
	sasl-2.1.22-20071206
	spamassassin-3.2.3-20071027

      Unchanged:

	amavisd-2.5.2-20070907
	autoconf-2.61-20070711
	automake-1.10-20061111
	bc-1.06-20061013
	bison-2.3-20070312
	bzip2-1.0.4-20070507
	clamav-0.91.2-20070907
	config-20060923-20061013
	db-4.5.20.2-20070628
	diffutils-2.8.7-20071005
	expat-2.0.1-20070629
	file-4.21-20070829
	freetype-2.3.5-20070720
	gd-2.0.35-20071011
	grep-2.5.3-20070829
	groff-1.19.2-20070113
	gzip-1.3.12-20070623
	jpeg-6b-20070507
	libmcrypt-2.5.8-20070720
	libxslt-1.1.22-20070824
	lzo-2.02-20061013
	m4-1.4.9-20070818
	make-3.81-20061013
	mhash-0.9.9-20070807
	mm-1.4.2-20061013
	openpkg-tools-1.4.5-20070624
	perl-conv-5.8.8-20070526
	perl-dns-5.8.8-20070920
	perl-ldap-5.8.8-20070916
	perl-openpkg-5.8.8-20061013
	perl-term-5.8.8-20070924
	pkgconfig-0.22-20070720
	readline-5.2.7-20070927
	sed-4.1.5-20061013
	texinfo-4.11-20070911
	zlib-1.2.3-20070507


Changes between 2.2-beta-1 and 2.2-beta-2:

    - perl-kolab-2.2.beta2-20071018

	Removed the Kolab-Mailer module.

	Removed "dirserv"-support.

	Replaced path reference to the kolabconf script by a
	configuration variable.

	Replaced statedir path with function argument.

	Replaced several variables originally rewritten during the
	make cycle with values in a central configuration file.

	Converted the package into a standard perl library package.

	kolab/issue26   (Allow to bind to specific IPs)
	kolab/issue934  (Remove FTP FreeBusy Service (proftpd))
	kolab/issue1862 (dist_conf/kolab: Use settings from OpenPKG
	                 installation)

    - php-kolab-2.2.beta2-20071018

	kolab/issue26   (Allow to bind to specific IPs)
	kolab/issue1637 (Recurrency issues)
	kolab/issue1862 (dist_conf/kolab: Use settings from OpenPKG
	                 installation)

    - kolabconf-2.2.beta2-20071018

	New package that holds the kolabconf script.

	Added mechanism to allow config variable replacement in the META
	section.

	kolab/issue26   (Allow to bind to specific IPs)
	kolab/issue934  (Remove FTP FreeBusy Service (proftpd))
	kolab/issue1879 (kolabconf poor error message in buildCyrusConfig)
	kolab/issue1862 (dist_conf/kolab: Use settings from OpenPKG
	                 installation)

    - kolabd-2.1.99-20071018

	Added "discard" service to the postfix master.cf configuration.

	Removed "dirserv"-support.

	Replaced path reference to the kolabconf script by a
	configuration variable.

	Replaced statedir path with function argument in Kolab::LDAP::startup.

	Replaced several variables originally rewritten during the
	make cycle with values in a central configuration file.

	Moved kolabconf into its own package.

	Fixed the apache configuration for the new fbview packages

	Switched from displaying php errors to logging them
	(recommended for production servers).

	Disabled spamd, hourly instead of daily clamav updates.

	Added "with_horde" support.

	Added LDAP attributes 'kolabAllowSMTPRecipient' and
	'kolabPolicyDaemon' in preparation for kolab/issue1340.

	The emailserver_socket is stored in $(libexecdir) and not in
	$(libdir). This fixes an x86_64 issue.

	kolab/issue26   (Allow to bind to specific IPs)
	kolab/issue934  (Remove FTP FreeBusy Service (proftpd))
	kolab/issue1025 (loading policy bank "MYUSERS": unknown field
	                 "mynetworks")
	kolab/issue1686 (Remove WebDAV Support)
	kolab/issue1796 (httpd.conf : MISSING Include
	                 "/kolab/etc/apache/apache.d/*.conf")
	kolab/issue1804 (Several files apparently missing in kolabd package)
	kolab/issue1805 (Uncleaned files in kolabd source package)
	kolab/issue1811 (Spurious files in CVS, kolabd directory)
	kolab/issue1861 (imapd.conf.template: primary domain listed twice in
	                 loginrealms)
	kolab/issue1862 (dist_conf/kolab: Use settings from OpenPKG
	                 installation)
	kolab/issue1895 (switch from virtual_maps to virtual_alias_maps)
	kolab/issue2038 (additional sieve extensions)

    - kolab-filter-2.2.beta2-20071018

	kolab/issue26   (Allow to bind to specific IPs)
	kolab/issue1606 (Allow to run kolab-resource-handlers with PHP cgi)
	kolab/issue1862 (dist_conf/kolab: Use settings from OpenPKG
	                 installation)

    - kolab-webadmin-2.1.99-20071018

	Clarify web admin description for HTTP FreeBusy switch
	(with updated German translation)

	kolab/issue932  (Illegal values in webadmin cause LDAP errors)
	kolab/issue934  (Remove FTP FreeBusy Service (proftpd))
	kolab/issue1162 (Misplaced title field in webinterface)
	kolab/issue1246 (Permission handling in the webadmin frontend)
	kolab/issue1611 ([webadmin] page.tpl use no valid XHTML)
	kolab/issue1694 (Unable to modify the folder type of an already
	                 created shared folder)
	kolab/issue1781 (Spanish PO File Translation)
	kolab/issue1797 (kolab-webadmin source package missing PO files)
	kolab/issue1800 (kolab-webadmin debian dist_conf smarty location)
	kolab/issue1845 (incorrect check mailForDn for ldap results)
	kolab/issue1862 (dist_conf/kolab: Use settings from OpenPKG
	                 installation)


    Packages in the OpenPKG based Kolab server release:

    - Kolab packages:

      Removed:

	kolab-horde-fbview (now fbview-horde, fbview-kronolith)
	kolab-resource-handlers (now kolab-filter, kolab-freebusy, php-kolab)

      Added:

	PEAR-Auth_SASL-1.0.2-1
	PEAR-Date-1.4.7-1
	PEAR-HTTP_Request-1.4.1-1
	PEAR-Log-1.9.9-1
	PEAR-Mail-1.1.14-1
	PEAR-Mail_Mime-1.3.1-1
	PEAR-Mail_Mime-1.3.1-1
	PEAR-Net_IMAP-1.1.0beta1-1
	PEAR-Net_LMTP-1.0.1-1
	PEAR-Net_SMTP-1.2.10-1
	PEAR-Net_Sieve-1.1.5-1
	PEAR-Net_Socket-1.0.6-1
	PEAR-Net_URL-1.0.15-1
	fbview-horde-3.2_alpha-20071013
	fbview-kronolith-2.2_alpha-20071001
	horde-framework-kolab-3.2_ALPHA-20071004
	horde-imp-kolab-4.2_alpha-20071004
	horde-ingo-kolab-1.2_alpha-20071004
	horde-kolab-3.2_alpha-20071013
	horde-kolab-client-0.99-20071002
	horde-kolab-client-0.99-20071002
	horde-kronolith-kolab-2.2_alpha-20071004
	horde-mnemo-kolab-2.2_alpha-20071001
	horde-nag-kolab-2.2_alpha-20071004
	horde-passwd-kolab-3.0.1-20071001
	horde-turba-kolab-2.2_alpha-20071002
	kolab-filter-2.2.beta2-20071018
	kolab-freebusy-2.2.beta2-20071018
	kolabconf-2.2.beta2-20071018
	php-kolab-2.2.beta2-20071018

      Updated:

	kolab-webadmin-2.1.99-20071018
	kolabd-2.1.99-20071018
	perl-kolab-2.2.beta2-20071018

      Unchanged:

	kolab-horde-framework-2.1.99-20070607
	php-smarty-2.6.18-20070607

    - OpenPKG packages:

      Removed:

	apache2 (renamed to apache)
	apache2-php (renamed to apache-php)
	getopt (was needed by proftpd)
	proftpd (obsolete)
	pth (openldap is now built without pth)
	sharutils (no package requires this)

      Added:

	apache-2.2.6-20070910
	apache-php-5.2.4-20071015
	apr-1.2.11-20070907
	freetype-2.3.5-20070720
	gd-2.0.35-20071011
	jpeg-6b-20070507
	libmcrypt-2.5.8-20070720
	mhash-0.9.9-20070807
	png-1.2.22-20071014

      Updated:

	amavisd-2.5.2-20070907
	autoconf-2.61-20070711
	binutils-2.18-20070829
	clamav-0.91.2-20070907
	curl-7.17.0-20071009
	db-4.5.20.2-20070628
	diffutils-2.8.7-20071005
	expat-2.0.1-20070629
	file-4.21-20070829
	gcc-4.2.2-20071016
	gettext-0.16.1-20070930
	grep-2.5.3-20070829
	gzip-1.3.12-20070623
	imap-2006j2-20071012
	imapd-2.3.9-20071015
	libxml-2.6.30-20070824
	libxslt-1.1.22-20070824
	m4-1.4.9-20070818
	ncurses-5.6.20071013-20071014
	openldap-2.3.38-20071012
	openpkg-20071018-20071018
	openpkg-tools-1.4.5-20070624
	openssl-0.9.8f-20071017
	pcre-7.4-20070921
	perl-5.8.8-20071011
	perl-comp-5.8.8-20071005
	perl-crypto-5.8.8-20070929
	perl-db-5.8.8-20070711
	perl-dns-5.8.8-20070920
	perl-ds-5.8.8-20071008
	perl-ldap-5.8.8-20070916
	perl-mail-5.8.8-20070928
	perl-module-5.8.8-20070928
	perl-net-5.8.8-20070829
	perl-parse-5.8.8-20071018
	perl-ssl-5.8.8-20071017
	perl-stats-5.8.8-20070708
	perl-sys-5.8.8-20071018
	perl-term-5.8.8-20070924
	perl-time-5.8.8-20071006
	perl-util-5.8.8-20071015
	perl-www-5.8.8-20071010
	perl-xml-5.8.8-20070929
	php-5.2.4-20071012
	pkgconfig-0.22-20070720
	postfix-2.4.5-20070908
	procmail-3.22-20070720
	readline-5.2.7-20070927
	sasl-2.1.22-20071009
	spamassassin-3.2.3-20070810
	texinfo-4.11-20070911

      Unchanged:

	automake-1.10-20061111
	bc-1.06-20061013
	bison-2.3-20070312
	bzip2-1.0.4-20070507
	config-20060923-20061013
	flex-2.5.33-20070507
	fsl-1.7.0-20070316
	gmp-4.2.1-20061222
	groff-1.19.2-20070113
	libiconv-1.11-20061013
	lzo-2.02-20061013
	make-3.81-20061013
	mm-1.4.2-20061013
	perl-conv-5.8.8-20070526
	perl-openpkg-5.8.8-20061013
	sed-4.1.5-20061013
	zlib-1.2.3-20070507


Changes between 2.1.0 and 2.2-beta1:

    All components except for OpenLDAP were upgraded to
    OpenPKG-CURRENT (as of 20070608), most noteworthy:

	amavisd 2.5.1
	apache 2.2.4
	imapd 2.3.8
	php 5.2.3
	postfix 2.4.3
	spamassassin 3.2.0

    - perl-kolab-5.8.8-20070608

	kolab/issue1679 (Update template META mechanism to support service
	                 restarts)

    - kolabd-2.1.99-20070612

	kolab/issue919  (kolab server has problems with some characters in
	                 passwords)
	kolab/issue1126 (ldap_simple_bind() failed and Domain/Realm not
	                 available) - partial fix
	kolab/issue1679 (Update template META mechanism to support service
	                 restarts)
	kolab/issue1693 (Automatically trigger f/b cache regeneration)

    - kolab-resource-handlers-2.1.99-20070612

	added location to xpfb events

	kolab/issue1693 (Automatically trigger f/b cache regeneration)

    - kolab-webadmin-2.1.99-20070607

	kolab/issue1610 (Use <label> for forms in webadmin)
	kolab/issue1615 (Use <label> also for login page)
	kolab/issue1618 (Add missing headings)
	kolab/issue1619 (Add CSS file for printing)
	kolab/issue1620 (fix invalid XHTML in form.class.php)
	kolab/issue1742 (Do not modify the objectclasses of an existing object)
	kolab/issue1744 (No "User Deleted, awaiting cleanup" for admins and
	                 domain maintainers)


-------------------------------------------------------------------------------

Differences between Kolab 2.0 and 2.1:

    - Simple multi-domain support

	The Kolab server can now accept mail for multiple email domains.
	There is also a new class of maintainers which are only allowed
	to manage settings for a subset of the mail domains of the kolab
	server.

    - Hashed IMAP spool

	The default imapd configuration has been changed to enable the
	hashimapspool option, which allows the Cyrus IMAP server to run
	more efficiently especially when you have many mailboxes.

    - Improvements, bugfixes and upgraded software components

	The 2.1 release received many improvements and bugfixes for issues
	found in the 2.0 versions and during the long beta and rc phase.
	Additionally many software components have been upgraded to new
	upstream versions.


Changes between 2.1-rc-2 and 2.1.0:

    - Documentation

	Documented workaround for libdb3 conflict in README.1st

	Added instructions for automatically upgrading the free/busy cache.

    - amavisd-2.3.3-2.5.0_kolab

	kolab/issue1447 (Virus Scanning: Inserted note when partially scanned
	                 ugly)

    - kolabd-2.1.0-20070510

	kolab/issue974  (Localize the text for rewritten From: headers)
	kolab/issue1560 (postfix modifies message/rfc822 MIME parts)
	kolab/issue1608 (A patch for kolabd to include the horde LDAP schema)

    - kolab-resource-handlers-2.1.0-20070510

	Generate a single To: header listing all recipients when forwarding
	encapsulated iCal messages.

	kolab/issue974  (Localize the text for rewritten From: headers)
	kolab/issue1422 (Dummy freebusy info)

    - kolab-webadmin-2.1.0-20070510

	kolab/issue1616 (Use different cursor for <label> tags)
	kolab/issue1617 (fix small inconsistency in german translation)


Changes between 2.1-rc-1 and 2.1-rc-2:

    - apache-1.3.33-2.5.6_kolab2

	kolab/issue1607 (need to replace gdbm for pfbcache, because of license
	                 clash gdbm vs php)

    - clamav-0.90.2-20070413_kolab

	New upstream version, fixes various security issues.

    - file-4.15-2.5.0_kolab2

	Fix for security issue described in CVE-2007-1536:
	buffer overflow, remotely exploitable due to the usage of file in
	amavisd-new

    - fsl-1.7.0-20070303

	New upstream version.

	kolab/issue1172 (Cyrus Imapd dies when logfile exceeds 2 GiB)

    - php-4.4.0-2.5.2_kolab2

	kolab/issue1607 (need to replace gdbm for pfbcache, because of license
	                 clash gdbm vs php)

    - spamassassin-3.1.0-2.5.1_kolab

	Fix for security issue described in CVE-2007-0451:
	possible DoS due to incredibly long URIs found in the message content

	Disabled external DNS and URI blacklists, because some of these
	services require payment if used for many mailboxes.

	Ignore headers inserted on the receiving side for bayes filtering.

    - perl-kolab-5.8.7-20070420

	Added debug option for verbose logging to stderr.

    - kolabd-2.1.0-20070420

	Fix the path to the freebusy directory for non-OpenPKG installations.

	Fix usage of tar and modification of rc.conf during slave setup for
	non-OpenPKG installations.

	Don't pass notifications and quarantined mails through amavisd-new.

	Updated configuration templates for ClamAV 0.90

	Updated openldap monitor configuration.

	Updated cyrus imapd configuration to use cyr_expire.

	kolab/issue954  (kolab server rejects mails that should be marked
	                 untrusted)
	kolab/issue1538 (outlook invitation forwarding broken in Kolab server
	                 2.1)
	kolab/issue1607 (need to replace gdbm for pfbcache, because of license
	                 clash gdbm vs php)
	kolab/issue1609 ("kolab --help" tries to execute *all* commands)
	kolab/issue1638 (kolabconf generates broken resmgr.conf)
	kolab/issue1680 (/kolab/bin/kolab fix)

    - kolab-horde-fbview-2.1.0-20070420

	Updated version number, no other changes since 2.1rc1

    - kolab-resource-handlers-2.1.0-20070420

	Improved logging for opening pfbcache.db

	kolab/issue954  (kolab server rejects mails that should be marked
	                 untrusted)
	kolab/issue1538 (outlook invitation forwarding broken in Kolab server
	                 2.1)
	kolab/issue1607 (need to replace gdbm for pfbcache, because of license
	                 clash gdbm vs php)
	kolab/issue1659 (Freebusy assumes that all day events last exactly one
	                 day)

    - kolab-webadmin-2.1.0-20070420

	Updated Dutch and German translations.

	kolab/issue1457 (updated French translation)
	kolab/issue1612 (modify user ignores account type)
	kolab/issue1614 (ldap_add() - Constraint violation on change user
	                 account type)
	kolab/issue1630 (Domain maintainer can see distribution lists from
	                 other domains)
	kolab/issue1652 (Import users from ldif and LDAP Constraint violation)
	kolab/issue1654 (New LDAP overlay prevents modification of
	                 distribution lists)
	kolab/issue1663 (It is possible to create domain maintainers without
	                 domains)
	kolab/issue1670 (Renaming a domain maintainer twice within the same
	                 form fails)


Changes between 2.1-beta-4 and 2.1-rc-1:

    - kolabd-2.0.99-20070205

	kolab/issue1335 (pfbcache.db locking problems)
	kolab/issue1507 (Public viewable phpinfo() and more in Server default
	                 installation)
	kolab/issue1550 (Masquerade problem, corrected template)
	kolab/issue1563 (freebusy.conf template doesn't match freebusy.conf
	                 from package)
	kolab/issue1575 (Openldap enhanced data integrity)

    - kolab-webadmin-2.0.99-20070205

	Disabled Spanish language selection from web admin interface, because
	of missing translation.

	kolab/issue1479 ("Type" of shared folder can only be modified in 2nd
	                 try)
	kolab/issue1486 ("About Kolab" in Webinterface needs work over)
	kolab/issue1539 (extension to the opening text, when the manager logs
	                 in for the 1st time)
	kolab/issue1559 (Domain Maintainer cannot delete "his" users)
	kolab/issue1586 ("Required field" not translated to German in web
	                 admin)
	kolab/issue1592 (LANGUAGE variable overrides web admin language
	                 selection)


Changes between 2.1-beta-3 and 2.1-beta-4:

    - clamav-0.88.7-20061211

	bypass virus detection (CVE-2006-6406),
	denial of service, remotely exploitable (CVE-2006-6481)
	(http://kolab.org/security/kolab-vendor-notice-14.txt)

    - kolabd-2.0.99-20070117

	Updated proftpd.conf template: LDAPHomedirOnDemand(Prefix) is
	now named LDAPGenerateHomedir(Prefix).

	Set imapidlepoll to 5 seconds in imapd.conf.template.in.

	kolab/issue1433 (Some files in /kolab/etc/postfix have wrong ownership)
	kolab/issue1484 (Warnings using openldap = 2.3.27-2.20061018_kolab)
	kolab/issue1487 (amavisd.conf mynetworks incomplete)
	kolab/issue1531 (amavisd.conf local_domains only contains primary
	                 domain)
	kolab/issue1532 (Set "duplicatesuppression: 0" in imapd.conf.template?)

    - kolab-horde-fbview-2.0.99-20070112

	Improvements to the week view (part of kolab/issue666)

	Removed dangerous php scripts (part of kolab/issue1507)

    - kolab-resource-handlers-2.0.99-20070117

	kolab/issue1490 (freebusy cache written to /kolab/kolab/...)
	kolab/issue1512 (No FB information for resource accounts)
	kolab/issue1558 (kolab-webadmin and php 5.2.0)

    - kolab-webadmin-2.0.99-20070117

	kolab/issue1013 (user passwords sha1 encoded without salt)
	kolab/issue1262 (Setting quota to 4096+ MB breaks message delivery)
	kolab/issue1418 (fields visible even when attribute_access is "hidden"
	                 in session_vars.php)
	kolab/issue1540 (Typo on kolab/admin/service page)
	kolab/issue1555 (Login screen shows error msg for no good reason)

    - openldap-2.3.29-2.20061110_kolab

	New upstream version, fixes CVE-2006-5779 (Bugtraq ID 20939)

    - perl-kolab-5.8.7-20070117

	Only print warning about missing configuration variable if relevant.

	kolab/issue1550 (Masquerade problem)


Changes between 2.1-beta-2 and 2.1-beta-3:

    - openpkg-2.5.4-2.5.4

	New upstream version.

    - apache-1.3.33-2.5.6

	denial of service and possibly arbitrary code execution via crafted
	URLs that are not properly handled using certain rewrite rules.
	http://www.openpkg.org/security/advisories/OpenPKG-SA-2006.015-apache.html

    - gzip-1.3.5-2.5.1

	denial of service, arbitrary code execution
	http://www.openpkg.org/security/advisories/OpenPKG-SA-2006.020-gzip.html

    - curl-7.15.0-2.5.2

	buffer overflow
	http://www.openpkg.org/security/advisories/OpenPKG-SA-2006.012-curl.html

    - openssl-0.9.8a-2.5.4

	denial of service, may allow execution of arbitrary code
	(http://kolab.org/security/kolab-vendor-notice-12.txt)

    - clamav-0.88.5-2.20061018

	buffer overflow, remotely exploitable (CVE-2006-4018)
	(http://kolab.org/security/kolab-vendor-notice-10.txt)

	heap overflow, remotely exploitable (CVE-2006-4182),
	denial of service, remotely exploitable (CVE-2006-5295)
	(http://kolab.org/security/kolab-vendor-notice-13.txt)

    - file-4.15-2.5.0_kolab

	kolab/issue1458 (Password protected .sxw files can be banned by
	                 amavisd, as a result of the file command)

    - openldap-2.3.27-2.20061018_kolab

	New upstream version, fixes CVE-2006-4600 (Bugtraq ID 19832)
	and other problems.

	kolab/issue1229 (Master openldap's slurpd fails to start after
	                 adding slave)
	kolab/issue1431 (Slave cannot access master ldap server via SSL)

    - imapd-2.2.12-2.5.0_kolab2

	Fix folder structure for foldernames with non-alphanumeric characters,
	when using skiplist as the database backend for mailboxes.db.

    - perl-kolab-5.8.7-20061110

	kolab/issue1194 (serious performance problem on high number of users)

    - kolabd-2.0.99-20061110

	Added missing relay service for postfix.

	Changed main.cf masquerading defaults so email to
	user at machine.example.org is actually delivered.

	Use mailbox_transport instead of local_transport for
	kolabmailboxfilter to work around issue825.

	Removed doubled attribute cyrus-autocreatequota.

	Added indexes for delegate and delete.

	Updated freebusy.conf template for freebusy IMAP caching.

	Changed imapd.conf template to use berkeley db instead of
	skiplist for annotations.db and mailboxes.db as a workaround
	for kolab/issue840 (Annotations needs to be more robust).

	kolab/issue824  (kolabmailboxfilter run once for each recipient)
	kolab/issue1264 (Add support for sieve based notifications)
	kolab/issue1273 (Sending as delegate broken in Kolab server 2.1)
	kolab/issue1428 (Fixed locking issue)
	kolab/issue1433 (Some files in /kolab/etc/postfix have wrong ownership)

    - kolab-webadmin-2.0.99-20061110

	Fixes for setting folder type of shared folders.

	Guard against large number of users.

	kolab/issue1457 (updated French translation)

    - kolab-resource-handlers-2.0.99-20061110

	Improvements and fixes for freebusy IMAP caching.

	kolab/issue815  (invitation replies vanish in resmgr)
	kolab/issue957  (All-day events from Outlook don't show up in freebusy)
	kolab/issue974  (Localize the text for rewritten From: headers)
	kolab/issue1042 (empty lines at the end of mails delivered via LMTP)
	kolab/issue1352 (resmgr can create wrong range dates)
	kolab/issue1387 (resmgr replies to replies creating mail loop)
	kolab/issue1422 (Dummy freebusy info)


Changes between 2.1-beta-1 and 2.1-beta-2:

    OpenPKG updates:

      openpkg-2.5.2-2.5.2
      openpkg-registry-0.2.7-20060223
      libxslt-1.1.15-2.5.1
      php-smarty-2.6.10-20051003
      clamav-0.88.2-20060524

      binutils-2.16.1-2.5.1
	http://www.openpkg.org/security/advisories/OpenPKG-SA-2006.009-binutils.html

      openldap-2.3.11-2.5.1
	http://www.openpkg.org/security/advisories/OpenPKG-SA-2006.008-openldap.html


    Kolab updates:

      More distconf changes by Richard Bos and Markus Huewe.

      - perl-kolab-5.8.7-20060619

	kolab/issue1194 (kolabd quota performance)
	kolab/issue1220 (postfix permissions)
	kolab/issue1237 (Handling of @@@var@@@ in Conf.pm (Gunnar Wrobel))

      - kolabd-2.0.99-20060619

	* The default imapd configuration has been changed to enable the
	  hashimapspool option.  This affects the upgrade procedure.
	  See 1st.README for upgrade instructions.

	* amavis now logs to /kolab/var/amavisd/amavisd.log.  This is
	  part of the fix for Issue1015

	kolab/issue1015 (fixing logging and logrotate for amavisd)
	kolab/issue1089 (enable hashimapspool for imapd to cope with many users)
	kolab/issue1101 (allowapop: no; disable apop access to imapd by default)
	kolab/issue1105 (fix compilation of kolabd on FreeBSD)
	kolab/issue1257 (wrong attribute name for imap quota)

      - kolab-webadmin-2.0.99-20060619

	* patch from Tobias Koenig in order to support setting of
	  foldertype for public folders

	kolab/issue848 (Modifying address book entry may break distribution list)
	kolab/issue1106 (email validation in webgui)
	kolab/issue1214 (number of days for vacation messages on webinterface)
	kolab/issue1263 (Bug in the shared folders folder-type code) [Wrobel]

      - kolab-resource-handlers-2.0.99-20060619

	* create empty pfbcache.db if missing

	kolab/issue973 (quoting and rewriting From header)
	kolab/issue966 (Wrong CN for resource accounts)
	kolab/issue1042 (server modifies email content)
	kolab/issue1195 (error message in bounce)
	kolab/issue1243 (rewriting fails when "From:" contains quoted printable)
	kolab/issue1245 (rewriting problems on folded Header "From:"-line)


$Id: release-notes.txt,v 1.295 2008/07/11 16:25:38 thomas Exp $
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20080711/e8563eea/attachment-0001.bin

From aspineux at gmail.com  Sat Jul 12 01:23:08 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sat, 12 Jul 2008 01:23:08 +0200
Subject: ldap backup
In-Reply-To: <20080711115133.imra2ta7oco0sogw@webmail.43gmbh.de>
References: <20080711115133.imra2ta7oco0sogw@webmail.43gmbh.de>
Message-ID: <71fe4e760807111623y16929f31ybb432fcc39f705b@mail.gmail.com>

On Fri, Jul 11, 2008 at 11:51 AM,  <s.trenz at 43gmbh.de> wrote:
> hi, i try to move the kolab Server to another Hardware.
> I want to do a Backup wich is already listet on wiki.kolab.org, but i
> get an Error Message if i try to backup the Ldad with the following
> command
> /kolab/sbin/slapcat -l /backup/kolab_ldap_db.ldif
> and i get this message
> /kolab/etc/openldap/slapd.conf: line 64: new attribute <member>

Did you mix openldap files from different version ?
Then try to recover to the original file version !


>
>
> the Config File looks like
> #### Using overlays to improve data consistency
> # Ensure that we never get dangling member attributes
> # Checked on rename and delete
> overlay refint
> refint_attributes member # this is line 64
>
> # The mail and the uid attribute must be unique.
> overlay unique
> unique_attributes mail uid
>
> index   objectClass     pres,eq
> index   uid             approx,sub,pres,eq
> index   mail            approx,sub,pres,eq
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From thorsten.schnebeck at gmx.net  Sun Jul 13 20:25:09 2008
From: thorsten.schnebeck at gmx.net (Thorsten Schnebeck)
Date: Sun, 13 Jul 2008 20:25:09 +0200
Subject: kolab 2.2.0 migration success + horde mobile access problem
Message-ID: <200807132025.10108.thorsten.schnebeck@gmx.net>

Hi,

congratulation to the Kolab team for the new release.

I used the weekend to migrate from 2.1 to 2.2. I did not follow the standard 
upgrade procedure as that leads to longer server downtime during compilation.
So I used a new installation root /kolab-2.2 and did a backup restore 
procedure.
Everything went smooth. Of course due to slabcat/slabadd I still have merged 
proftpd-stuff in my LDAP.

While I prefer using Gentoo on my servers I really like the Openpkg system and 
did not used Gunnars Gentoo packages (*sorry* :-) and do proxying between 
Kolabs apache and Gentoos apache.

So after one year successfully running 2.1 now the 2.2 area starts and I hope 
I can start migrating the real "beasts" :-)

One of the new stuff I want to use is the new Horde webmail system from a 
mobile phone. But after the login I get "/horde/mimp was not fond on this 
server" and this is correct. For now I just made a symlink from mimp -> imp 
and this works great with opera mini.

Bye and thank you all!

  Thorsten 

 


From troy at carpenter.cx  Mon Jul 14 02:41:13 2008
From: troy at carpenter.cx (Troy Carpenter)
Date: Sun, 13 Jul 2008 20:41:13 -0400
Subject: Lost mailbox ACLs
Message-ID: <200807132041.13770.troy@carpenter.cx>

Something strange happened on my system overnight, and I don't know if my 
recovery actions may have caused this, but some of the mailboxes in users 
accounts.  Some inboxes were simply missing the ACL for the user, but I'm 
talking about ones that don't have any ACLs at all, so the cyrus admin user 
can't even add the user back in because that account isn't in the ACL either.

The lm command lists the mailboxes, and they exist in the mailbox tree, but 
they don't show up in any clients, and like I said, the lam command comes 
back blank.

Any ideas?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20080713/654e9f59/attachment.bin

From troy at carpenter.cx  Mon Jul 14 03:09:42 2008
From: troy at carpenter.cx (troy@carpenter.cx)
Date: Sun, 13 Jul 2008 21:09:42 -0400
Subject: Lost mailbox ACLs (rewrite)
In-Reply-To: <200807132041.13770.troy@carpenter.cx>
References: <200807132041.13770.troy@carpenter.cx>
Message-ID: <20080713210942.70571trmw5do7p7a@mail.carpenter.cx>

I seemed to have foo-bar'ed one of the important sentences...here's a rewrite.

Quoting Troy Carpenter <troy at carpenter.cx>:

Something strange happened on my system overnight, and I don't know if my
recovery actions may have caused this, but some of the mailboxes in users
accounts are completely missing ACLs.  Some inboxes were simply  
missing the ACL for the user, but I'm talking about ones that don't  
have any ACLs at all, so the cyrus admin user can't even add the user  
back in because that account isn't in the ACL either.

The lm command lists the mailboxes, and they exist in the mailbox tree, but
they don't show up in any clients, and like I said, the lam command comes
back blank.

If I try to reconstruct the mailboxes, I get the following:

kolab-r at sol$ cyrreconstruct user/troy/Sent at carpenter.cx
carpenter.cx!user.troy.Sent: Unknown/invalid partition


Any ideas?



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 1332 bytes
Desc: PGP Public Key
Url : http://kolab.org/pipermail/kolab-users/attachments/20080713/3362c0a1/attachment.bin

From troy at carpenter.cx  Mon Jul 14 04:39:54 2008
From: troy at carpenter.cx (Troy Carpenter)
Date: Sun, 13 Jul 2008 22:39:54 -0400
Subject: Lost mailbox ACLs (rewrite)
In-Reply-To: <20080713210942.70571trmw5do7p7a@mail.carpenter.cx>
References: <200807132041.13770.troy@carpenter.cx>
	<20080713210942.70571trmw5do7p7a@mail.carpenter.cx>
Message-ID: <200807132239.54862.troy@carpenter.cx>

On Sunday 13 July 2008 09:09:42 pm troy at carpenter.cx wrote:
> I seemed to have foo-bar'ed one of the important sentences...here's a
> rewrite.
>
> Quoting Troy Carpenter <troy at carpenter.cx>:
>
> Something strange happened on my system overnight, and I don't know if my
> recovery actions may have caused this, but some of the mailboxes in users
> accounts are completely missing ACLs.  Some inboxes were simply
> missing the ACL for the user, but I'm talking about ones that don't
> have any ACLs at all, so the cyrus admin user can't even add the user
> back in because that account isn't in the ACL either.
>
> The lm command lists the mailboxes, and they exist in the mailbox tree, but
> they don't show up in any clients, and like I said, the lam command comes
> back blank.
>
> If I try to reconstruct the mailboxes, I get the following:
>
> kolab-r at sol$ cyrreconstruct user/troy/Sent at carpenter.cx
> carpenter.cx!user.troy.Sent: Unknown/invalid partition
>
>
> Any ideas?

Ok, here's how I fixed it.  I was still able to get the mailbox database via 
the command "/kolab/bin/ctl_mboxlist -d > mailboxlist.txt".  Then I edited 
the file to correct the ACLs as necessary, then reloaded the file with the 
opposite command "/kolab/bin/ctl_mboxlist -u < mailboxlist.txt".  I basically 
used the wiki page 
http://wiki.kolab.org/index.php/Backups_for_kolab2#IMAP_store_recovery_.28cyrus.29 
as a guide.

Troy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20080713/3125eb9c/attachment.bin

From s.kim at hia.rwth-aachen.de  Mon Jul 14 10:02:05 2008
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Mon, 14 Jul 2008 10:02:05 +0200
Subject: Freebusy regeneration
In-Reply-To: <mailman.10.1215856804.15405.kolab-users@kolab.org>
References: <mailman.10.1215856804.15405.kolab-users@kolab.org>
Message-ID: <487B07FD.2070707@hia.rwth-aachen.de>

Hello,

I just read through the readme.txt of the 2.2 release version and found 
the command to regenerate the freebusy cache information (I'm still 
working with 2.2 rc 2):

https://yourserver.example.com/freebusy/generatefb.php

Unfortunatly, this doesn't work for me (of course I changed the yoursever.example.com accordingly :-) 
I get the following error message: "Failed to authenticate! Please authenticate!" I didn't get a login screen where I could
have authenticated myself as manager.

Any hints?

Thanks,
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
-------------------------------------------------------------------------- 


From liutauras.adomaitis at gmail.com  Wed Jul 16 08:53:56 2008
From: liutauras.adomaitis at gmail.com (Liutauras Adomaitis)
Date: Wed, 16 Jul 2008 09:53:56 +0300
Subject: Kolab vs Scalix
Message-ID: <c1ec9ac0807152353o22d3da98i6a09920b8a5774e6@mail.gmail.com>

Hello everybody,

does anybody knows anything about Kolab and Scalix comparison. We are
choosing
solution for groupware server for 40 users network. All users are with
Windows workstations. We didn't decided, but as a client we plan to use
either MS Outlook (2003/2007) or Mozilla Thunderbird. Outlook is more
mature,
but Thunderbird is closer to our "Open Source Spirit".
We have tested Kolab2 and several connectors to Outlook did not seem to work

very well (some are not MAPI, the others work very slow). SyncKolab also did

not act the way we expected. I understand that there maybe our problems, but

still it is problems for us.
We did not tested Scalix yet, but got some recommendations about it.

So what does Kolab users think about Kolab and Scalix.
- Server installation, maintenance and backup
- Commercial support (this is a big issue for us)
- Outlook support
- Thunderbird support
- Webmail (Horde vs Scalix Java webmail)
- Any links on the web about this comparison

Price is not a big issue for us as long as it is cheaper than Exchange.

Liutauras
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20080716/07f639e7/attachment.html

From liutauras at mandriva.lt  Tue Jul 15 17:55:04 2008
From: liutauras at mandriva.lt (Liutauras Adomaitis)
Date: Tue, 15 Jul 2008 18:55:04 +0300
Subject: kolab vs scalix
In-Reply-To: <487B07FD.2070707@hia.rwth-aachen.de>
References: <mailman.10.1215856804.15405.kolab-users@kolab.org>
	<487B07FD.2070707@hia.rwth-aachen.de>
Message-ID: <200807151855.05296.liutauras@mandriva.lt>

Hello everybody,

does anybody knows anything about Kolab and Scalix comparison. We are choosing 
solution for groupware server for 40 users network. All users are with 
Windows workstations. We didn't decided, but as a client we plan to use 
either MS Outlook (2003/2007) or Mozilla Thunderbird. Outlook is more mature, 
but Thunderbird is closer to our "Open Source Spirit".
We have tested Kolab2 and several connectors to Outlook did not seem to work 
very well (some are not MAPI, the others work very slow). SyncKolab also did 
not act the way we expected. I understand that there maybe our problems, but 
still it is problems for us.
We did not tested Scalix yet, but got some recommendations about it.

So what does Kolab users think about Kolab and Scalix.
- Server installation, maintenance and backup
- Commercial support (this is a big issue for us)
- Outlook support
- Thunderbird support
- Webmail (Horde vs Scalix Java webmail)
- Any links on the web about this comparison

Price is not a big issue for us as long as it is cheaper than Exchange.

Liutauras


From michael at pasdziernik.net  Wed Jul 16 10:23:25 2008
From: michael at pasdziernik.net (Michael Pasdziernik)
Date: Wed, 16 Jul 2008 10:23:25 +0200
Subject: Kolab vs Scalix
In-Reply-To: <c1ec9ac0807152353o22d3da98i6a09920b8a5774e6@mail.gmail.com>
References: <c1ec9ac0807152353o22d3da98i6a09920b8a5774e6@mail.gmail.com>
Message-ID: <200807161023.25757.michael@pasdziernik.net>

Hello Liutauras,

we used scalix some time before we migrated to kolab. Scalix is very useful 
and the outlook connector works good. The base of scalix is HP OpenMail
which is a really stable and mature platform. As a long time linux 
administrator I prefer kolab because of its well know server components, 
scalix always was a bit like a black box to me. 

Our main reason for the migration was that the webclient is very buggy and 
slow. It is based on java/tomcat and has serious performance issues, even 
with five concurrent users on a dedicated server (2,8 GHz P4, 2 GB RAM). They 
worked on the problem but never managed to solve our issues (we only used 
forum support).
The user experience regarding scalix webmail was very bad. It has to much 
Ajax.The user sees something that looks like a desktop client but acts slow 
like a webclient. So webclient did never receive any acceptance by our users.
Horde is much better in that way.
Another annoyance was that the regular updates do not only fix bugs and 
security issues but also introduced new features with new bugs.
I think their QA for the community version is not so good, I do not know if
paid versions are more stable.

The only problem with kolab in my opinion is the missing windows client for
power users, that means users with thousands of messages and several
GBytes mailbox size.
Konsec does not allow more then 3GB of mailbox-size, Toltec
has some issus with synchronisation on big mailboxes.
Currently I am evaluating the new bynari insight connector and this looks very 
promising.

What I like about kolab is the growing choice of clients. If kontact for Win 
an synckolab are stable you can choose between kontact, outlook, thunderbird, 
horde and syncml-clients.

Regards
Michael






On Wednesday, 16. July 2008 08:53:56 Liutauras Adomaitis wrote:
> Hello everybody,
>
> does anybody knows anything about Kolab and Scalix comparison. We are
> choosing
> solution for groupware server for 40 users network. All users are with
> Windows workstations. We didn't decided, but as a client we plan to use
> either MS Outlook (2003/2007) or Mozilla Thunderbird. Outlook is more
> mature,
> but Thunderbird is closer to our "Open Source Spirit".
> We have tested Kolab2 and several connectors to Outlook did not seem to
> work
>
> very well (some are not MAPI, the others work very slow). SyncKolab also
> did
>
> not act the way we expected. I understand that there maybe our problems,
> but
>
> still it is problems for us.
> We did not tested Scalix yet, but got some recommendations about it.
>
> So what does Kolab users think about Kolab and Scalix.
> - Server installation, maintenance and backup
> - Commercial support (this is a big issue for us)
> - Outlook support
> - Thunderbird support
> - Webmail (Horde vs Scalix Java webmail)
> - Any links on the web about this comparison
>
> Price is not a big issue for us as long as it is cheaper than Exchange.
>
> Liutauras



From wrobel at pardus.de  Wed Jul 16 15:22:17 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 16 Jul 2008 15:22:17 +0200
Subject: A (currently theoretical) question concerning a book about the
	Kolab Server
In-Reply-To: <200807101621.22388.bernhard@intevation.de> (Bernhard Reiter's
	message of "Thu, 10 Jul 2008 16:21:22 +0200")
References: <87ej626kj6.fsf@home.pardus.de>
	<200807101621.22388.bernhard@intevation.de>
Message-ID: <87d4lem0ae.fsf@home.pardus.de>

Bernhard Reiter <bernhard at intevation.de> writes:

> Am Donnerstag, 10. Juli 2008 13:33:33 schrieb Gunnar Wrobel:
>> So I'm wondering if there'd actually be enough financial interest in a
>> book about Kolab. This is still a completely hypothetical question as
>> I didn't consider the important parameters of such a project yet. I'd
>> expect the costs to be somewhere in the range of twenty to thirty
>> thousand Euros for convinving the publisher to agree to the model with
>> a non-free print version and a free PDF.
>
> There is some interested in documentation,
> as you can see from the operating system manual in German available from 
> http://kolab.org/documentation.html which a customer of the Kolab-Konsortium
> contracted.
>
> (One of the next steps probably would be to translate this nice manual.)
>  
>> So right now I'm just looking for some comments to start getting some
>> ideas and a better grasp of the potential problems that one would need
>> to solve.
>
> There are two problems that I see:
> a) people just expect the documentation to be there, so it probably will need 
> to be cross financed from other Kolab business.

Yes, for commercial software that is certainly the case. Kolab is kind
of on a middle ground here. Most of the admins in a Linux environment
probably know a good deal of software packages that don't provide
decent documentation so the expectations are probably less high.

> While it is commericially viable for KK to run a large portions of
> the Kolab community efforts, the level could be better for
> maintenance and documentation. It will largely depend on how good KK
> will manage to get business and how fair users are inclined to pay
> for good service which includes running infrastructure and
> documentation.

For most other software projects I wouldn't even have dared to mention
the idea. The fact that KK is successfully running a commercial free
software product and actively paying for community work is not common
at all. I think in most cases the only choice is writing stuff and
give your copyright to the publisher. Which is kind of weird when the
software you write is free.

I agree that some of this probably has to be cross-financed but I hope
there might be some companies or people willing to also contribute
just for the sake of having better documentation.

>
> b) Technically a good manual must be changed in the moment the software is 
> changed, so it must be part of the software development process. For this the 
> documentation must be part of public infrastructure of the kolab.org 
> community.

I don't see that as a problem but as a requirement. The content
definitely would need to be available via the wiki, too. And work on
any texts would take place in a version controlled repository in any
case.

Cheers,

Gunnar

>
> Best,
> Bernhard
>
>
> -- 
> Managing Director - Owner: www.intevation.net       (Free Software Company)
> Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
> Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
> Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From wrobel at pardus.de  Wed Jul 16 15:24:23 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 16 Jul 2008 15:24:23 +0200
Subject: A (currently theoretical) question concerning a book about the
	Kolab Server
In-Reply-To: <71fe4e760807101143o36a42c6cqb08adc11c7db3182@mail.gmail.com>
	(Alain Spineux's message of "Thu, 10 Jul 2008 20:43:10 +0200")
References: <87ej626kj6.fsf@home.pardus.de> <48763B8D.2000104@yugm.org>
	<71fe4e760807101143o36a42c6cqb08adc11c7db3182@mail.gmail.com>
Message-ID: <8763r6m06w.fsf@home.pardus.de>

"Alain Spineux" <aspineux at gmail.com> writes:

>> Gunnar Wrobel wrote:
>>> I'd be really interested in writing a handbook for administrators
>>> of the Kolab server.
>
> Any idea of how many kolab servers are running (in production).
> And how many mailbox are hosted on such server ?

No, we don't watch the users to that extend :) We are often suprised
when there are support requests from new locations that we didn't know
about.

Cheers,

Gunnar

>
>
> -- 
> Alain Spineux
> aspineux gmail com
> May the sources be with you
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From wrobel at pardus.de  Wed Jul 16 15:28:53 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 16 Jul 2008 15:28:53 +0200
Subject: kolab 2.2.0 migration success + horde mobile access problem
In-Reply-To: <200807132025.10108.thorsten.schnebeck@gmx.net> (Thorsten
	Schnebeck's message of "Sun, 13 Jul 2008 20:25:09 +0200")
References: <200807132025.10108.thorsten.schnebeck@gmx.net>
Message-ID: <871w1ulzze.fsf@home.pardus.de>

Thorsten Schnebeck <thorsten.schnebeck at gmx.net> writes:

> Hi,
>
> congratulation to the Kolab team for the new release.
>
> I used the weekend to migrate from 2.1 to 2.2. I did not follow the standard 
> upgrade procedure as that leads to longer server downtime during compilation.
> So I used a new installation root /kolab-2.2 and did a backup restore 
> procedure.
> Everything went smooth. Of course due to slabcat/slabadd I still have merged 
> proftpd-stuff in my LDAP.
>
> While I prefer using Gentoo on my servers I really like the Openpkg system and 
> did not used Gunnars Gentoo packages (*sorry* :-) and do proxying between 
> Kolabs apache and Gentoos apache.
>
> So after one year successfully running 2.1 now the 2.2 area starts and I hope 
> I can start migrating the real "beasts" :-)
>
> One of the new stuff I want to use is the new Horde webmail system from a 
> mobile phone. But after the login I get "/horde/mimp was not fond on this 
> server" and this is correct. For now I just made a symlink from mimp -> imp 
> and this works great with opera mini.

I guess you might also be able to just install mimp from one of the
horde release pacakges by unpacking it into
/kolab/var/kolab/www/horde.

It will probably be included in Kolab-Server-2.2.1. The current Horde
version was a frist trial version and we weren't able to extend this
to all the stuff Horde offers (e.g. dimp, mimp and SyncML). But 2.2.1
should see some upgrades and enhancements in that sector. Horde is
currently advancing a lot in the Kolab sector.

Cheers,

Gunnar

>
> Bye and thank you all!
>
>   Thorsten 
>
>  
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From wrobel at pardus.de  Wed Jul 16 15:32:02 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 16 Jul 2008 15:32:02 +0200
Subject: Freebusy regeneration
In-Reply-To: <487B07FD.2070707@hia.rwth-aachen.de> (Saim Kim's message of "Mon,
	14 Jul 2008 10:02:05 +0200")
References: <mailman.10.1215856804.15405.kolab-users@kolab.org>
	<487B07FD.2070707@hia.rwth-aachen.de>
Message-ID: <87wsjmkl9p.fsf@home.pardus.de>

Saim Kim <s.kim at hia.rwth-aachen.de> writes:

> Hello,
>
> I just read through the readme.txt of the 2.2 release version and found 
> the command to regenerate the freebusy cache information (I'm still 
> working with 2.2 rc 2):
>
> https://yourserver.example.com/freebusy/generatefb.php
>
> Unfortunatly, this doesn't work for me (of course I changed the yoursever.example.com accordingly :-) 
> I get the following error message: "Failed to authenticate! Please authenticate!" I didn't get a login screen where I could
> have authenticated myself as manager.
>
> Any hints?

Does the command line equivalent work?

Calling https://yourserver.example.com/freebusy/generatefb.php should
ask you for HTTP-Authentication (so your browser should open a special
authentication window). This did not happen?

Cheers,

Gunnar

>
> Thanks,
> 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
> -------------------------------------------------------------------------- 
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From wrobel at pardus.de  Wed Jul 16 16:06:03 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 16 Jul 2008 16:06:03 +0200
Subject: Kolab vs Scalix
In-Reply-To: <c1ec9ac0807152353o22d3da98i6a09920b8a5774e6@mail.gmail.com>
	(Liutauras Adomaitis's message of "Wed,
	16 Jul 2008 09:53:56 +0300")
References: <c1ec9ac0807152353o22d3da98i6a09920b8a5774e6@mail.gmail.com>
Message-ID: <87mykhly9g.fsf@home.pardus.de>

"Liutauras Adomaitis" <liutauras.adomaitis at gmail.com> writes:

> Hello everybody,
>
> does anybody knows anything about Kolab and Scalix comparison. We are choosing
> solution for groupware server for 40 users network. All users are with
> Windows workstations. We didn't decided, but as a client we plan to use
> either MS Outlook (2003/2007) or Mozilla Thunderbird. Outlook is more mature,
> but Thunderbird is closer to our "Open Source Spirit".
> We have tested Kolab2 and several connectors to Outlook did not seem to work
> very well (some are not MAPI, the others work very slow). SyncKolab also did
> not act the way we expected. I understand that there maybe our problems, but
> still it is problems for us.
> We did not tested Scalix yet, but got some recommendations about it.
>
> So what does Kolab users think about Kolab and Scalix.
> - Server installation, maintenance and backup
> - Commercial support (this is a big issue for us)

There are several companies offering Kolab support. The
Kolab-Konsortium being the main support partner. So you definitely
have several options there without being glued to a single partner.

> - Outlook support

I always had the impression that the Outlook connectors for the Kolab
Server are pretty good. Maybe you can provide some more details where
they troubled you?

> - Thunderbird support

Thunderbird suppport isn't good in my eyes. I do really like the
SyncKolab-extension for Thunderbird, but this still lacks too many
features that are critical for a fast and reliable Kolab support. I
wouldn't use this in production at the moment.

> - Webmail (Horde vs Scalix Java webmail)

Well, I like Horde :) - I'm Horde developer so I have to love it. But
from the developers perspective I can assure you that Horde has a very
clean code base. I wouldn't say that Horde is very flashy and it might
not impress that much on first sight. But it has a very sound basis
that has been build over years. And this basis is now being used to
add the more flashy parts in areas where it actually makes sense.

Cheers,

Gunnar

> - Any links on the web about this comparison
>
> Price is not a big issue for us as long as it is cheaper than Exchange.
>
> Liutauras
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From s.kim at hia.rwth-aachen.de  Thu Jul 17 11:42:45 2008
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Thu, 17 Jul 2008 11:42:45 +0200
Subject: Freebusy regeneration: solved
In-Reply-To: <87wsjmkl9p.fsf@home.pardus.de>
References: <mailman.10.1215856804.15405.kolab-users@kolab.org>
	<487B07FD.2070707@hia.rwth-aachen.de> <87wsjmkl9p.fsf@home.pardus.de>
Message-ID: <487F1415.8080100@hia.rwth-aachen.de>

Hello Gunnar,

I solved the problem: I didn't RTFM :-( I didn't turn off the "allow 
unauthenticated download of freebusy information" option. Now an 
authentication window opens and it starts the regeneration problem.

Unfortunatly though, it stops after an error with the following error 
message: "Regenerating calendar "user/test1/Gel&APY-schte 
Objekte/Kalender at myserver.com"! Failed regenerating cache for calendar 
"user/test1/Gel&APY-schte Objekte/Kalender at myserver.com"! Folder 
user/test1/Gel&-APY-schte Objekte/Kalender at myserver.com does not exist!" 
It would be great if such an error doesn't stop the whole process.

Best regards,
Saim



Gunnar Wrobel schrieb:
> Saim Kim <s.kim at hia.rwth-aachen.de> writes:
>
>   
>> Hello,
>>
>> I just read through the readme.txt of the 2.2 release version and found 
>> the command to regenerate the freebusy cache information (I'm still 
>> working with 2.2 rc 2):
>>
>> https://yourserver.example.com/freebusy/generatefb.php
>>
>> Unfortunatly, this doesn't work for me (of course I changed the yoursever.example.com accordingly :-) 
>> I get the following error message: "Failed to authenticate! Please authenticate!" I didn't get a login screen where I could
>> have authenticated myself as manager.
>>
>> Any hints?
>>     
>
> Does the command line equivalent work?
>
> Calling https://yourserver.example.com/freebusy/generatefb.php should
> ask you for HTTP-Authentication (so your browser should open a special
> authentication window). This did not happen?
>
> Cheers,
>
> Gunnar
>
>   
>> Thanks,
>> 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
>> -------------------------------------------------------------------------- 
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>     
>
>   


-- 
--------------------------------------------------------------------------
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
-------------------------------------------------------------------------- 


From wrobel at pardus.de  Thu Jul 17 13:08:40 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 17 Jul 2008 13:08:40 +0200
Subject: A (currently theoretical) question concerning a book about the
	Kolab Server
In-Reply-To: <200807171219.22133.richard@radoeka.nl> (Richard Bos's message of
	"Thu, 17 Jul 2008 12:19:21 +0200")
References: <87ej626kj6.fsf@home.pardus.de>
	<200807171219.22133.richard@radoeka.nl>
Message-ID: <87ej5sbwef.fsf@home.pardus.de>

Hi Richard,

I'm responding to the first part of your private e-mail in
public. Hope that is okay ;)

Richard Bos <richard at radoeka.nl> writes:

> Hello Gunnar,
>
> Op donderdag 10 juli 2008 13:33, schreef Gunnar Wrobel:
>> While I like Gentoo my main area of activity is the Kolab groupware
>> and I'd be really interested in writing a handbook for administrators
>> of the Kolab server.
>
> if you have time: can you give an explanation what the big difference is 
> between kolab and other solutions like: scalix, open-exchange, zimfra (I 
> think it is called).
>
> From my perspective, kolab is fully open source, each and every component is 
> open source.  That's one thing.

This difference is also what makes it easier to do the native
ports. Not that native ports are easy but when I chose Kolab three
years ago it was obvious that neither scalix, open-exchange, nor
zimbra would be open enough to get easily ported to Gentoo.

> The other thing is that kolab is fully based on a directory (ldap)
> and imap storage instead of a database.  But what is the big
> advantage of using a directory and imap storage instead of database?
> With IP everywhere a database is also very reachable from each
> location, even from remote locations and databases can be replicated
> as well.

You only look at the administrators point of view here. Of course the
server admin can access a database. But what about the user? This is
the most crucial point about Kolab for me. Of course Kolab offers a
lot more than IMAP based storage of data. But to me this is the core
element. And it is not a technical reason why I'm excited about this
but a plain social one.

Storing data in IMAP means the user has full control of his
data. Assuming there are several Kolab providers you could simply move
all your data from one provider to the next. It would not even be
necessary that these are Kolab providers. Just IMAP providers would be
enough (see my latest message on Kolab on Gmail).

Putting the user in control of his own data is crucial to me if I look
at the current growth of web 2.0 applications. We happily store all
our data in the databases of a large number of different companies. We
don't remain in control of that data and we usually can only access it
via an API provided by the company.

I'm not overly paranaiod about this but conceptionally I believe "full
control of your data" will be a very important concept in the
future. And relying on IMAP for data storage gives you exactly
that. User are already now in full control of their e-mail. If they
change the provider they have the possibility to migrate their data
with them. So with Kolab nothing changes for them.

On top of that it would actually be easy to encrypt the Kolab data
stored in IMAP. So your IMAP provider wouldn't even have access to the
private data you store on the servers.


From marko at mechtron.com.au  Thu Jul 17 13:26:49 2008
From: marko at mechtron.com.au (Mark Berndt)
Date: Thu, 17 Jul 2008 21:26:49 +1000
Subject: A (currently theoretical) question concerning a book about the
	Kolab Server
In-Reply-To: <87d4lem0ae.fsf@home.pardus.de>
References: <87ej626kj6.fsf@home.pardus.de>
	<200807101621.22388.bernhard@intevation.de>
	<87d4lem0ae.fsf@home.pardus.de>
Message-ID: <200807172126.49921.marko@mechtron.com.au>

On Wednesday 16 July 2008 23:22:17 you wrote:
> Bernhard Reiter <bernhard at intevation.de> writes:
> > Am Donnerstag, 10. Juli 2008 13:33:33 schrieb Gunnar Wrobel:
> >> So I'm wondering if there'd actually be enough financial interest in a
> >> book about Kolab. This is still a completely hypothetical question as
> >> I didn't consider the important parameters of such a project yet. I'd
> >> expect the costs to be somewhere in the range of twenty to thirty
> >> thousand Euros for convinving the publisher to agree to the model with
> >> a non-free print version and a free PDF.
> >
> > There is some interested in documentation,
> > as you can see from the operating system manual in German available from
> > http://kolab.org/documentation.html which a customer of the
> > Kolab-Konsortium contracted.
> >
> > (One of the next steps probably would be to translate this nice manual.)
> >
> >> So right now I'm just looking for some comments to start getting some
> >> ideas and a better grasp of the potential problems that one would need
> >> to solve.
> >
> > There are two problems that I see:
> > a) people just expect the documentation to be there, so it probably will
> > need to be cross financed from other Kolab business.
>
> Yes, for commercial software that is certainly the case. Kolab is kind
> of on a middle ground here. Most of the admins in a Linux environment
> probably know a good deal of software packages that don't provide
> decent documentation so the expectations are probably less high.


You need to provide installation documentation for free.  You might also 
provide some operating instructions also for free.  

I would be happy to pay for a book:

(1) that provides information on how to apply the software (kolab) to business 
situations.
(2) that provides technical information on how the server components work.
(3) how to tune and tweak the server components
(4) how to configure the client software

$50 or $100 is a small price to pay when the software is free.  If you can't 
afford it, or your company can't afford it, you need to find a new job!!! 

>
> > While it is commericially viable for KK to run a large portions of
> > the Kolab community efforts, the level could be better for
> > maintenance and documentation. It will largely depend on how good KK
> > will manage to get business and how fair users are inclined to pay
> > for good service which includes running infrastructure and
> > documentation.
>
> For most other software projects I wouldn't even have dared to mention
> the idea. The fact that KK is successfully running a commercial free
> software product and actively paying for community work is not common
> at all. I think in most cases the only choice is writing stuff and
> give your copyright to the publisher. Which is kind of weird when the
> software you write is free.
>
> I agree that some of this probably has to be cross-financed but I hope
> there might be some companies or people willing to also contribute
> just for the sake of having better documentation.
>
> > b) Technically a good manual must be changed in the moment the software
> > is changed, so it must be part of the software development process. For
> > this the documentation must be part of public infrastructure of the
> > kolab.org community.
>
> I don't see that as a problem but as a requirement. The content
> definitely would need to be available via the wiki, too. And work on
> any texts would take place in a version controlled repository in any
> case.

Extension of a book by a website or wiki would be fine.  I'd expect a new 
release of the book with each major version 2, 3 etc.  and I'd pay for it 
each time.

rgds,

Marko


>
> Cheers,
>
> Gunnar
>
> > Best,
> > Bernhard
> >
> >
> > --
> > Managing Director - Owner: www.intevation.net       (Free Software
> > Company) Germany Coordinator: fsfeurope.org. Coordinator:
> > www.Kolab-Konsortium.com. Intevation GmbH, Osnabr?ck, DE; Amtsgericht
> > Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr.
> > Jan-Oliver Wagner
> >
> > _______________________________________________
> > Kolab-users mailing list
> > Kolab-users at kolab.org
> > https://kolab.org/mailman/listinfo/kolab-users



From ml at radoeka.nl  Thu Jul 17 14:59:06 2008
From: ml at radoeka.nl (Richard Bos)
Date: Thu, 17 Jul 2008 14:59:06 +0200
Subject: A (currently theoretical) question concerning a book about the
	Kolab Server
In-Reply-To: <87ej5sbwef.fsf@home.pardus.de>
References: <87ej626kj6.fsf@home.pardus.de>
	<200807171219.22133.richard@radoeka.nl>
	<87ej5sbwef.fsf@home.pardus.de>
Message-ID: <200807171459.06347.ml@radoeka.nl>

Op Thursday 17 July 2008 13:08:40 schreef Gunnar Wrobel:
> > The other thing is that kolab is fully based on a directory (ldap)
> > and imap storage instead of a database. ?But what is the big
> > advantage of using a directory and imap storage instead of database?
> > With IP everywhere a database is also very reachable from each
> > location, even from remote locations and databases can be replicated
> > as well.
>
> You only look at the administrators point of view here. Of course the
> server admin can access a database. But what about the user? This is
> the most crucial point about Kolab for me. Of course Kolab offers a
> lot more than IMAP based storage of data. But to me this is the core
> element. And it is not a technical reason why I'm excited about this
> but a plain social one.

I did not think about this aspect actually, but it is a very nice one indeed.  

However, if one is to use kolab in a company environment this fact (user in 
control of data) is of no importance as the user should not move his email :)
In that case why is the directory / imap storage better than other solutions?  
Probably because it is scalably.  But isn't the same valid for groupware 
solutions based on a database (I wonder)?  Perhaps Bernard or Martin can 
elaborate on this?

-- 
Richard Bos
Without a home the journey is endless


From s.kim at hia.rwth-aachen.de  Thu Jul 17 15:45:19 2008
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Thu, 17 Jul 2008 15:45:19 +0200
Subject: Can't receive mail after upgrading from 2.2rc2 to 2.2 release
In-Reply-To: <mailman.2732.1216287689.2108.kolab-users@kolab.org>
References: <mailman.2732.1216287689.2108.kolab-users@kolab.org>
Message-ID: <487F4CEF.3030001@hia.rwth-aachen.de>

Hello,

I upgraded to the kolab 2.2 release version from rc2. I followed the 
instruction and upgraded to rc3 and then to the release version. After 
doing the kolab.conf regeneration I started the kolab services -and 
since then I cannot receive mails :-( The only thing I have changed is 
that I unchecked the virus checking in the admin interface. But I turned 
it back on and also ran the  kolab.conf regeneration several times after 
that.

I checked all kinds of mail to check if there are any changes after the 
upgrade. Here is a list of things I found:

1. No problems sending mails using the Toltec connector and Outlook, and 
Horde
2. All services are checked positive with the "check mail configuration" 
from outlook
3. No email are received (tested with different user accounts)
4. kolab-filter log looks fine (no errors or warning and the email are 
correctly identified as kolab events etc.)
5. kolab-filter fatal.log is empty
6. postfix.log shows multiple errors caused by failed virus checking 
(clamav not detected, was turned off, see on top). Is it possible that 
the emails are discarded or not forwarded if the virus scanner is turned 
off? Even though I turned it back on, I still cannot receive emails
7. imapd notify.log doesn't show "executed" messages any more after 
upgrading

Any hints on how to get the server back into working state?

Thanks for your help,
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
-------------------------------------------------------------------------- 


From thomas at intevation.de  Thu Jul 17 15:55:04 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Thu, 17 Jul 2008 15:55:04 +0200
Subject: Specify Kolab IP address
In-Reply-To: <38061.84.12.101.132.1208196195.squirrel@kolab.mail.anderson.eu.com>
References: <38061.84.12.101.132.1208196195.squirrel@kolab.mail.anderson.eu.com>
Message-ID: <20080717135504.GD27184.thomas@intevation.de>

* Stuart McCulloch Anderson <stuart-kolabusers at stuartanderson.org> [20080414 20:03]:
> Afternoon guys, I need a little advice for configuring Kolab.
> It has recently come up that our network operator requires Kolab to only
> listen for pop3(s) and imap(s) connection on one of our four IP addresses.
> I cant seem to find a way to set it up.
> 
> Can anyone please offer me any guidance or support?

Kolab Server 2.2.0 offers this out of the box, just add the lines

bind_any : FALSE
bind_addr : 1.2.3.4

to your /kolab/etc/kolab/kolab.conf and run /kolab/sbin/kolabconf

After this you have to stop and start the server and this massive
change does not propagate automatically.

With Kolab Server 2.1 you would need to build your own packages from
CVS as it was added after 2.1.0 and there won't be a 2.1.1 release.

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From thomas at intevation.de  Thu Jul 17 16:34:58 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Thu, 17 Jul 2008 16:34:58 +0200
Subject: Deleting user does not delete mailaccount
In-Reply-To: <E180434E4C1EB54894D8C670FB6739230170DE0C@LYEXCHESV1.bvra.fr>
References: <E180434E4C1EB54894D8C670FB6739230170DE0C@LYEXCHESV1.bvra.fr>
Message-ID: <20080717143458.GE27184.thomas@intevation.de>

* Maury Sandra <sandra.maury at enssib.fr> [20080609 15:26]:
> When i delete a user in Kolab web-interface Admin, files on server in
> /kolab/var/imapd/spool/domain/p/mondomain.fr/m/user/ are not deleted.
> Can you explain me why ?

Which Kolab server version do you use?

There was a bug regarding this introduced in 2.2-rc2 and solved in
2.2.0

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From thomas at intevation.de  Thu Jul 17 16:54:34 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Thu, 17 Jul 2008 16:54:34 +0200
Subject: Freebusy regeneration: solved
In-Reply-To: <487F1415.8080100@hia.rwth-aachen.de>
References: <mailman.10.1215856804.15405.kolab-users@kolab.org>
	<487B07FD.2070707@hia.rwth-aachen.de>
	<87wsjmkl9p.fsf@home.pardus.de>
	<487F1415.8080100@hia.rwth-aachen.de>
Message-ID: <20080717145433.GG27184.thomas@intevation.de>

* Saim Kim <s.kim at hia.rwth-aachen.de> [20080717 11:41]:
> Unfortunatly though, it stops after an error with the following error 
> message: "Regenerating calendar "user/test1/Gel&APY-schte 
> Objekte/Kalender at myserver.com"! Failed regenerating cache for calendar 
> "user/test1/Gel&APY-schte Objekte/Kalender at myserver.com"! Folder 
> user/test1/Gel&-APY-schte Objekte/Kalender at myserver.com does not exist!" 
> It would be great if such an error doesn't stop the whole process.

Yes, that should be better.

I opened an issue for this:
kolab/issue2905 (generatefb.php should skip invalid folders instead of aborting)

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From s.kim at hia.rwth-aachen.de  Thu Jul 17 17:41:05 2008
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Thu, 17 Jul 2008 17:41:05 +0200
Subject: Can't receive mail after upgrading from 2.2rc2 to 2.2 release: More
	Information
In-Reply-To: <mailman.2758.1216306477.2108.kolab-users@kolab.org>
References: <mailman.2758.1216306477.2108.kolab-users@kolab.org>
Message-ID: <487F6811.7090808@hia.rwth-aachen.de>

>
> ------------------------------------------------------------------------
>
> Betreff:
> Can't receive mail after upgrading from 2.2rc2 to 2.2 release
> Von:
> Saim Kim <s.kim at hia.rwth-aachen.de>
> Datum:
> Thu, 17 Jul 2008 15:45:19 +0200
> An:
> kolab-users at kolab.org
>
> An:
> kolab-users at kolab.org
>
>
> Hello,
>
> I upgraded to the kolab 2.2 release version from rc2. I followed the 
> instruction and upgraded to rc3 and then to the release version. After 
> doing the kolab.conf regeneration I started the kolab services -and 
> since then I cannot receive mails :-( The only thing I have changed is 
> that I unchecked the virus checking in the admin interface. But I 
> turned it back on and also ran the  kolab.conf regeneration several 
> times after that.
>
> I checked all kinds of mail to check if there are any changes after 
> the upgrade. Here is a list of things I found:
>
> 1. No problems sending mails using the Toltec connector and Outlook, 
> and Horde
> 2. All services are checked positive with the "check mail 
> configuration" from outlook
> 3. No email are received (tested with different user accounts)
> 4. kolab-filter log looks fine (no errors or warning and the email are 
> correctly identified as kolab events etc.)
> 5. kolab-filter fatal.log is empty
> 6. postfix.log shows multiple errors caused by failed virus checking 
> (clamav not detected, was turned off, see on top). Is it possible that 
> the emails are discarded or not forwarded if the virus scanner is 
> turned off? Even though I turned it back on, I still cannot receive 
> emails
> 7. imapd notify.log doesn't show "executed" messages any more after 
> upgrading

Here is an excerpt from my imapd notify.log. I started the update at 
11.40. After that there is no message indicading "do_notify using method 
'mailto' anymore. Just a plain executed statement. Does this give 
anybody a hint for a solution?

Jul 17 04:01:19 stud14 <debug> notifyd[16738]: do_notify using method 
'mailto'
Jul 17 10:37:26 stud14 <debug> notifyd[16738]: do_notify using method 
'mailto'
Jul 17 11:16:04 stud14 <debug> notifyd[16738]: do_notify using method 
'mailto'
Jul 17 11:17:27 stud14 <debug> notifyd[16738]: do_notify using method 
'mailto'
Jul 17 11:19:32 stud14 <debug> notifyd[16738]: do_notify using method 
'mailto'
Jul 17 11:19:35 stud14 <debug> notifyd[16738]: do_notify using method 
'mailto'
Jul 17 12:34:49 stud14 <debug> notifyd[28387]: executed
Jul 17 12:49:48 stud14 <debug> notifyd[1960]: executed
Jul 17 13:27:34 stud14 <debug> notifyd[13312]: executed
Jul 17 13:38:24 stud14 <debug> notifyd[18889]: executed
Jul 17 14:51:07 stud14 <debug> notifyd[24799]: executed
Jul 17 17:31:33 stud14 <debug> notifyd[981]: executed

Best regards,
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
-------------------------------------------------------------------------- 


From s.kim at hia.rwth-aachen.de  Thu Jul 17 17:55:42 2008
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Thu, 17 Jul 2008 17:55:42 +0200
Subject: Can't receive mail after upgrading from 2.2rc2 to 2.2 release Even
	more information
Message-ID: <487F6B7E.1070605@hia.rwth-aachen.de>

Here is an error message from the postfix.log:

Jul 17 17:41:34 stud14 <info> postfix/qmgr[1102]: F0E31496884: 
from=<s.kim at medit.intern>, size=967, nrcpt=1 (queue active)
Jul 17 17:41:41 stud14 <info> postfix/smtp[1370]: F0E31496884: 
to=<test1 at medit.intern>, relay=127.0.0.1[127.0.0.1]:10024, delay=546, 
delays=539/0/0/7.1, dsn=4
.5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error 
in processing, id=00581-04, virus_scan FAILED: virus_scan: ALL VIRUS 
SCANNERS FAILED: C
lam Antivirus-clamd av-scanner FAILED: CODE(0x89039e0) Too many retries 
to talk to /kolab/var/clamav/clamd.sock (Can't connect to UNIX socket 
/kolab/var/clama
v/clamd.sock: 2) at (eval 99) line 310. at (eval 99) line 511.; Clam 
Antivirus - /kolab/bin/clamscan av-scanner FAILED: /kolab/bin/clamscan 
DIED on signal 4 (
0004) at (eval 99) line 511. (in reply to end of DATA command))

So, even though in the admin webinterface Amavis is checked it still 
seems not to work, right? Can that be the cause of my mail delivery 
problem? How can I solve this problem?

Best regards,
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
--------------------------------------------------------------------------


From s.kim at hia.rwth-aachen.de  Thu Jul 17 18:19:27 2008
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Thu, 17 Jul 2008 18:19:27 +0200
Subject: Can't receive mail after upgrading from 2.2rc2 to 2.2 release: Even
	more information
In-Reply-To: <mailman.2758.1216306477.2108.kolab-users@kolab.org>
References: <mailman.2758.1216306477.2108.kolab-users@kolab.org>
Message-ID: <487F710F.8070406@hia.rwth-aachen.de>

>
> ------------------------------------------------------------------------
>

Ok,

so after some more checking I'm quite sure that clamav is the reason for 
the mail error. Even it is started with the /kolab/bin/openpkg rc all 
start, if I check the status it is still not active:


mykolab:/kolab/var/clamav# /kolab/bin/openpkg rc clamav start

OpenPKG: start: clamav.

mykolab:/kolab/var/clamav# /kolab/bin/openpkg rc clamav status

OpenPKG: status: clamav.
clamav_enable="yes"
clamav_usable="unknown"
clamav_active="no"

So, how can I make clamav start?

Also both update logs don't show any error messages (rc2->rc3, rc3 -> 
release)

Best regards,
Saim

P.s.: Sorry for writing so many mails today...


> Betreff:
> Can't receive mail after upgrading from 2.2rc2 to 2.2 release
> Von:
> Saim Kim <s.kim at hia.rwth-aachen.de>
> Datum:
> Thu, 17 Jul 2008 15:45:19 +0200
> An:
> kolab-users at kolab.org
>
> An:
> kolab-users at kolab.org
>
>
> Hello,
>
> I upgraded to the kolab 2.2 release version from rc2. I followed the 
> instruction and upgraded to rc3 and then to the release version. After 
> doing the kolab.conf regeneration I started the kolab services -and 
> since then I cannot receive mails :-( The only thing I have changed is 
> that I unchecked the virus checking in the admin interface. But I 
> turned it back on and also ran the  kolab.conf regeneration several 
> times after that.
>
> I checked all kinds of mail to check if there are any changes after 
> the upgrade. Here is a list of things I found:
>
> 1. No problems sending mails using the Toltec connector and Outlook, 
> and Horde
> 2. All services are checked positive with the "check mail 
> configuration" from outlook
> 3. No email are received (tested with different user accounts)
> 4. kolab-filter log looks fine (no errors or warning and the email are 
> correctly identified as kolab events etc.)
> 5. kolab-filter fatal.log is empty
> 6. postfix.log shows multiple errors caused by failed virus checking 
> (clamav not detected, was turned off, see on top). Is it possible that 
> the emails are discarded or not forwarded if the virus scanner is 
> turned off? Even though I turned it back on, I still cannot receive 
> emails
> 7. imapd notify.log doesn't show "executed" messages any more after 
> upgrading
>
> Any hints on how to get the server back into working state?
>
> Thanks for your help,
> Saim
>
 


From richard at radoeka.nl  Thu Jul 17 14:37:33 2008
From: richard at radoeka.nl (Richard Bos)
Date: Thu, 17 Jul 2008 14:37:33 +0200
Subject: A (currently theoretical) question concerning a book about the
	Kolab Server
In-Reply-To: <87ej5sbwef.fsf@home.pardus.de>
References: <87ej626kj6.fsf@home.pardus.de>
	<200807171219.22133.richard@radoeka.nl>
	<87ej5sbwef.fsf@home.pardus.de>
Message-ID: <200807171437.34235.richard@radoeka.nl>

Op Thursday 17 July 2008 13:08:40 schreef Gunnar Wrobel:
> > The other thing is that kolab is fully based on a directory (ldap)
> > and imap storage instead of a database. ?But what is the big
> > advantage of using a directory and imap storage instead of database?
> > With IP everywhere a database is also very reachable from each
> > location, even from remote locations and databases can be replicated
> > as well.
>
> You only look at the administrators point of view here. Of course the
> server admin can access a database. But what about the user? This is
> the most crucial point about Kolab for me. Of course Kolab offers a
> lot more than IMAP based storage of data. But to me this is the core
> element. And it is not a technical reason why I'm excited about this
> but a plain social one.

I did not think about this aspect actually, but it is a very nice one indeed.  

However, if one is to use kolab in a company environment this fact (user in 
control of data) is of no importance as the user should not move his email :)
In that case why is the directory / imap storage better than other solutions?  
Probably because it is scalably.  But isn't the same valid for groupware 
solutions based on a database (I wonder)?  Perhaps Bernard or Martin can 
elaborate on this?

-- 
Richard Bos
Without a home the journey is endless


From s.kim at hia.rwth-aachen.de  Fri Jul 18 01:47:27 2008
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Fri, 18 Jul 2008 01:47:27 +0200
Subject: IMAP recovery
Message-ID: <002001c8e867$789279c0$6400a8c0@ldssfoi>

Hello,

I tried to do a complete IMAP recovery as described in the backups how-to in the wiki. But so far I have not been able to access the mails e.g. calendar events. I ran the cyrreconstruct command like this (as kolab-r):
/kolab/bin/cyrreconstruct -rf user/user/folder/subfolder at mydomain.com

When I log into Horde I have an empty calendar eventhough the directory (imapd/spool/...) is full with events? Any hints?

Best regards,
Saim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20080718/a53cebb3/attachment.html

From thomas at intevation.de  Fri Jul 18 09:05:20 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 18 Jul 2008 09:05:20 +0200
Subject: IMAP recovery
In-Reply-To: <002001c8e867$789279c0$6400a8c0@ldssfoi>
References: <002001c8e867$789279c0$6400a8c0@ldssfoi>
Message-ID: <20080718070520.GA10397.thomas@intevation.de>

* Saim Kim <s.kim at hia.rwth-aachen.de> [20080718 01:47]:
> I tried to do a complete IMAP recovery as described in the backups how-to in the wiki. But so far I have not been able to access the mails e.g. calendar events. I ran the cyrreconstruct command like this (as kolab-r):
> /kolab/bin/cyrreconstruct -rf user/user/folder/subfolder at mydomain.com
> 
> When I log into Horde I have an empty calendar eventhough the directory (imapd/spool/...) is full with events? Any hints?

cyrreconstruct can't reconstruct (or rather invent) ACLs (not
related to your problem) and annotations (the folder meta
information where e.g. the type of a folder is stored).

See http://kolab.org/pipermail/kolab-users/2007-October/006934.html

Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From thomas at intevation.de  Fri Jul 18 09:14:40 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 18 Jul 2008 09:14:40 +0200
Subject: Can't receive mail after upgrading from 2.2rc2 to 2.2 release
	Even more information
In-Reply-To: <487F6B7E.1070605@hia.rwth-aachen.de>
References: <487F6B7E.1070605@hia.rwth-aachen.de>
Message-ID: <20080718071440.GB10397.thomas@intevation.de>

* Saim Kim <s.kim at hia.rwth-aachen.de> [20080717 17:54]:
> Here is an error message from the postfix.log:
>
> Jul 17 17:41:34 stud14 <info> postfix/qmgr[1102]: F0E31496884:
> from=<s.kim at medit.intern>, size=967, nrcpt=1 (queue active)
> Jul 17 17:41:41 stud14 <info> postfix/smtp[1370]: F0E31496884:
> to=<test1 at medit.intern>, relay=127.0.0.1[127.0.0.1]:10024, delay=546,
> delays=539/0/0/7.1, dsn=4
> .5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error
> in processing, id=00581-04, virus_scan FAILED: virus_scan: ALL VIRUS
> SCANNERS FAILED: C
> lam Antivirus-clamd av-scanner FAILED: CODE(0x89039e0) Too many retries
> to talk to /kolab/var/clamav/clamd.sock (Can't connect to UNIX socket
> /kolab/var/clama
> v/clamd.sock: 2) at (eval 99) line 310. at (eval 99) line 511.; Clam
> Antivirus - /kolab/bin/clamscan av-scanner FAILED: /kolab/bin/clamscan
> DIED on signal 4 (
> 0004) at (eval 99) line 511. (in reply to end of DATA command))
>
> So, even though in the admin webinterface Amavis is checked it still
> seems not to work, right? Can that be the cause of my mail delivery
> problem? How can I solve this problem?

The web interface just looks at LDAP, not at the reality. It tries
to change the reality to match LDAP, but for this it relies on the
system behaving correctly.

In this case "kolabd" should translate the file
/kolab/etc/kolab/templates/master.cf.template
containing
@@@if postfix-enable-virus-scan@@@
    -o content_filter=smtp-amavis:[@@@local_addr@@@]:10024
@@@else@@@
    -o content_filter=
@@@endif@@@

into /kolab/etc/postfix/master.cf
containing either the content_filter=smtp-amavis line or the other.

Check the later file. If it is not correct, try running
/kolab/sbin/kolabconf

If this does not solve the problem add the line "debug : 1" to
/kolab/etc/kolab/kolab.conf and run kolabconf again to see where it
aborts.

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From thomas at intevation.de  Fri Jul 18 09:27:58 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 18 Jul 2008 09:27:58 +0200
Subject: Can't receive mail after upgrading from 2.2rc2 to 2.2 release:
	Even more information
In-Reply-To: <487F710F.8070406@hia.rwth-aachen.de>
References: <mailman.2758.1216306477.2108.kolab-users@kolab.org>
	<487F710F.8070406@hia.rwth-aachen.de>
Message-ID: <20080718072758.GC10397.thomas@intevation.de>

* Saim Kim <s.kim at hia.rwth-aachen.de> [20080717 18:18]:
> so after some more checking I'm quite sure that clamav is the reason for
> the mail error. Even it is started with the /kolab/bin/openpkg rc all
> start, if I check the status it is still not active:
>
> mykolab:/kolab/var/clamav# /kolab/bin/openpkg rc clamav start
>
> OpenPKG: start: clamav.
>
> mykolab:/kolab/var/clamav# /kolab/bin/openpkg rc clamav status
>
> OpenPKG: status: clamav.
> clamav_enable="yes"
> clamav_usable="unknown"
> clamav_active="no"
>
> So, how can I make clamav start?

Or rather: why does your correct way of starting clamav fail?

There is /kolab/var/clamav/clamd.log or your could try manually
executing /kolab/bin/clamscan

You might want to try manually updating the virus database:
# su - kolab-r
$ freshclam

> P.s.: Sorry for writing so many mails today...

With this and my other two mails you might be able to get a working
system again, but there is something wrong on your machine or
installation which causes all this.

If this should be used for production I strongly recommend to get
professional support from the Kolab Konsortium (which Intevation is
part of) or at least help from another person or company with some
experience in troubleshooting mail server installations.

See http://www.kolab-konsortium.de/

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From s.kim at hia.rwth-aachen.de  Fri Jul 18 09:33:02 2008
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Fri, 18 Jul 2008 09:33:02 +0200
Subject: IMAP recovery
In-Reply-To: <20080718070520.GA10397.thomas@intevation.de>
References: <002001c8e867$789279c0$6400a8c0@ldssfoi>
	<20080718070520.GA10397.thomas@intevation.de>
Message-ID: <4880472E.4090509@hia.rwth-aachen.de>

Thomas Arendsen Hein schrieb:
> * Saim Kim <s.kim at hia.rwth-aachen.de> [20080718 01:47]:
>   
>> I tried to do a complete IMAP recovery as described in the backups how-to in the wiki. But so far I have not been able to access the mails e.g. calendar events. I ran the cyrreconstruct command like this (as kolab-r):
>> /kolab/bin/cyrreconstruct -rf user/user/folder/subfolder at mydomain.com
>>
>> When I log into Horde I have an empty calendar eventhough the directory (imapd/spool/...) is full with events? Any hints?
>>     
>
> cyrreconstruct can't reconstruct (or rather invent) ACLs (not
> related to your problem) and annotations (the folder meta
> information where e.g. the type of a folder is stored).
>
> See http://kolab.org/pipermail/kolab-users/2007-October/006934.html
>
> Thomas
>
>   
Hello Thomas,

the Wikki was quite clear about the ACL's. So, of course I did save the 
ACL's with the mailboxlist and read it back before the cyrreconstruct. I 
checked in cyradm and all mailboxes are shown with the correct ACL's. 
Interestingly, also a broken mailbox which prevent the automatic 
freebusy regeneration before suddenly didn't bother the process anymore.

The problem is, that I don't see any email e.g. calendar events in my 
recovered system even though the email is in the spool directory and the 
mailbox is shown correctly in the cyradm interface.

Best regards,
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
-------------------------------------------------------------------------- 


From s.kim at hia.rwth-aachen.de  Fri Jul 18 10:06:17 2008
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Fri, 18 Jul 2008 10:06:17 +0200
Subject: Can't receive mail after upgrading from 2.2rc2 to 2.2 release
	Even more information
In-Reply-To: <20080718071440.GB10397.thomas@intevation.de>
References: <487F6B7E.1070605@hia.rwth-aachen.de>
	<20080718071440.GB10397.thomas@intevation.de>
Message-ID: <48804EF9.1070401@hia.rwth-aachen.de>

Thomas Arendsen Hein schrieb:
> * Saim Kim <s.kim at hia.rwth-aachen.de> [20080717 17:54]:
>   
>> Here is an error message from the postfix.log:
>>
>> Jul 17 17:41:34 stud14 <info> postfix/qmgr[1102]: F0E31496884:
>> from=<s.kim at medit.intern>, size=967, nrcpt=1 (queue active)
>> Jul 17 17:41:41 stud14 <info> postfix/smtp[1370]: F0E31496884:
>> to=<test1 at medit.intern>, relay=127.0.0.1[127.0.0.1]:10024, delay=546,
>> delays=539/0/0/7.1, dsn=4
>> .5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error
>> in processing, id=00581-04, virus_scan FAILED: virus_scan: ALL VIRUS
>> SCANNERS FAILED: C
>> lam Antivirus-clamd av-scanner FAILED: CODE(0x89039e0) Too many retries
>> to talk to /kolab/var/clamav/clamd.sock (Can't connect to UNIX socket
>> /kolab/var/clama
>> v/clamd.sock: 2) at (eval 99) line 310. at (eval 99) line 511.; Clam
>> Antivirus - /kolab/bin/clamscan av-scanner FAILED: /kolab/bin/clamscan
>> DIED on signal 4 (
>> 0004) at (eval 99) line 511. (in reply to end of DATA command))
>>
>> So, even though in the admin webinterface Amavis is checked it still
>> seems not to work, right? Can that be the cause of my mail delivery
>> problem? How can I solve this problem?
>>     
>
> The web interface just looks at LDAP, not at the reality. It tries
> to change the reality to match LDAP, but for this it relies on the
> system behaving correctly.
>
> In this case "kolabd" should translate the file
> /kolab/etc/kolab/templates/master.cf.template
> containing
> @@@if postfix-enable-virus-scan@@@
>     -o content_filter=smtp-amavis:[@@@local_addr@@@]:10024
> @@@else@@@
>     -o content_filter=
> @@@endif@@@
>
> into /kolab/etc/postfix/master.cf
> containing either the content_filter=smtp-amavis line or the other.
>
> Check the later file. If it is not correct, try running
> /kolab/sbin/kolabconf
>
> If this does not solve the problem add the line "debug : 1" to
> /kolab/etc/kolab/kolab.conf and run kolabconf again to see where it
> aborts.
>
> Regards,
> Thomas
>
>   
Hello Thomas,

I checked the /kolab/etc/kolab/templates/master.cf.template 
and/kolab/etc/postfix/master.cf. Both look fine and have the 
content_filter=smtp-amavis line.
Also, I did the /kolab/sbin/kolab.conf with the debug line added. There 
were also no error messages. The only thing was these lines here:

T Debug: `/kolab/etc/clamav/clamd.conf' change detected: Dateien 
/kolab/etc/clamav/clamd.conf und /kolab/etc/clamav/clamd.conf.old sind 
verschieden.
T Debug: Finished creating configuration file `/kolab/etc/clamav/clamd.conf'

T Debug: `/kolab/etc/clamav/freshclam.conf' change detected: Dateien 
/kolab/etc/clamav/freshclam.conf und 
/kolab/etc/clamav/freshclam.conf.old sind verschieden.
T Debug: Finished creating configuration file 
`/kolab/etc/clamav/freshclam.conf'

KC: Reloading kolab components
K: Restarting clamav...
OpenPKG: restart: clamav.
K: Reload finished
KC: Finished

So, it looks to me, that kolab.conf runs fine, right? Nevertheless, 
clamav is not "active" when I call /kolab/bin/openpkg rc all start and 
check the status. Interestingly, I get the same error on a fresh install.

Best regards,
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
-------------------------------------------------------------------------- 


From thomas at intevation.de  Fri Jul 18 12:02:08 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 18 Jul 2008 12:02:08 +0200
Subject: IMAP recovery
In-Reply-To: <4880472E.4090509@hia.rwth-aachen.de>
References: <002001c8e867$789279c0$6400a8c0@ldssfoi>
	<20080718070520.GA10397.thomas@intevation.de>
	<4880472E.4090509@hia.rwth-aachen.de>
Message-ID: <20080718100208.GB21080.thomas@intevation.de>

* Saim Kim <s.kim at hia.rwth-aachen.de> [20080718 09:31]:
> Thomas Arendsen Hein schrieb:
> > * Saim Kim <s.kim at hia.rwth-aachen.de> [20080718 01:47]:
> >   
> >> I tried to do a complete IMAP recovery as described in the backups how-to in the wiki. But so far I have not been able to access the mails e.g. calendar events. I ran the cyrreconstruct command like this (as kolab-r):
> >> /kolab/bin/cyrreconstruct -rf user/user/folder/subfolder at mydomain.com
> >>
> >> When I log into Horde I have an empty calendar eventhough the directory (imapd/spool/...) is full with events? Any hints?
> >>     
> >
> > cyrreconstruct can't reconstruct (or rather invent) ACLs (not
> > related to your problem) and annotations (the folder meta
> > information where e.g. the type of a folder is stored).
> >
> > See http://kolab.org/pipermail/kolab-users/2007-October/006934.html
> 
> the Wikki was quite clear about the ACL's. So, of course I did save the 
> ACL's with the mailboxlist and read it back before the cyrreconstruct. I 
> checked in cyradm and all mailboxes are shown with the correct ACL's. 
> Interestingly, also a broken mailbox which prevent the automatic 
> freebusy regeneration before suddenly didn't bother the process anymore.
> 
> The problem is, that I don't see any email e.g. calendar events in my 
> recovered system even though the email is in the spool directory and the 
> mailbox is shown correctly in the cyradm interface.

Please re-read my mail: Lost annotations cause your problems.

Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From thomas at intevation.de  Fri Jul 18 12:05:51 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 18 Jul 2008 12:05:51 +0200
Subject: Can't receive mail after upgrading from 2.2rc2 to 2.2 release
	Even more information
In-Reply-To: <48804EF9.1070401@hia.rwth-aachen.de>
References: <487F6B7E.1070605@hia.rwth-aachen.de>
	<20080718071440.GB10397.thomas@intevation.de>
	<48804EF9.1070401@hia.rwth-aachen.de>
Message-ID: <20080718100551.GC21080.thomas@intevation.de>

* Saim Kim <s.kim at hia.rwth-aachen.de> [20080718 10:05]:
> Thomas Arendsen Hein schrieb:
> > * Saim Kim <s.kim at hia.rwth-aachen.de> [20080717 17:54]:
> >   
> >> Here is an error message from the postfix.log:
> >>
> >> Jul 17 17:41:34 stud14 <info> postfix/qmgr[1102]: F0E31496884:
> >> from=<s.kim at medit.intern>, size=967, nrcpt=1 (queue active)
> >> Jul 17 17:41:41 stud14 <info> postfix/smtp[1370]: F0E31496884:
> >> to=<test1 at medit.intern>, relay=127.0.0.1[127.0.0.1]:10024, delay=546,
> >> delays=539/0/0/7.1, dsn=4
> >> .5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error
> >> in processing, id=00581-04, virus_scan FAILED: virus_scan: ALL VIRUS
> >> SCANNERS FAILED: C
> >> lam Antivirus-clamd av-scanner FAILED: CODE(0x89039e0) Too many retries
> >> to talk to /kolab/var/clamav/clamd.sock (Can't connect to UNIX socket
> >> /kolab/var/clama
> >> v/clamd.sock: 2) at (eval 99) line 310. at (eval 99) line 511.; Clam
> >> Antivirus - /kolab/bin/clamscan av-scanner FAILED: /kolab/bin/clamscan
> >> DIED on signal 4 (
> >> 0004) at (eval 99) line 511. (in reply to end of DATA command))
> >>
> >> So, even though in the admin webinterface Amavis is checked it still
> >> seems not to work, right? Can that be the cause of my mail delivery
> >> problem? How can I solve this problem?
> >
> > The web interface just looks at LDAP, not at the reality. It tries
> > to change the reality to match LDAP, but for this it relies on the
> > system behaving correctly.
> >
> > In this case "kolabd" should translate the file
> > /kolab/etc/kolab/templates/master.cf.template
> > containing
> > @@@if postfix-enable-virus-scan@@@
> >     -o content_filter=smtp-amavis:[@@@local_addr@@@]:10024
> > @@@else@@@
> >     -o content_filter=
> > @@@endif@@@
> >
> > into /kolab/etc/postfix/master.cf
> > containing either the content_filter=smtp-amavis line or the other.
> >
> > Check the later file. If it is not correct, try running
> > /kolab/sbin/kolabconf
> >
> > If this does not solve the problem add the line "debug : 1" to
> > /kolab/etc/kolab/kolab.conf and run kolabconf again to see where it
> > aborts.
>
> I checked the /kolab/etc/kolab/templates/master.cf.template 
> and/kolab/etc/postfix/master.cf. Both look fine and have the 
> content_filter=smtp-amavis line.

I thought you said you disabled it, so it should not be there in
master.cf

Now disable it to see if mail (without spam/virus checking) works
for you.

> Also, I did the /kolab/sbin/kolab.conf with the debug line added. There 
> were also no error messages. The only thing was these lines here:
> 
> T Debug: `/kolab/etc/clamav/clamd.conf' change detected: Dateien 
> /kolab/etc/clamav/clamd.conf und /kolab/etc/clamav/clamd.conf.old sind 
> verschieden.
> T Debug: Finished creating configuration file `/kolab/etc/clamav/clamd.conf'
> 
> T Debug: `/kolab/etc/clamav/freshclam.conf' change detected: Dateien 
> /kolab/etc/clamav/freshclam.conf und 
> /kolab/etc/clamav/freshclam.conf.old sind verschieden.
> T Debug: Finished creating configuration file 
> `/kolab/etc/clamav/freshclam.conf'
> 
> KC: Reloading kolab components
> K: Restarting clamav...
> OpenPKG: restart: clamav.
> K: Reload finished
> KC: Finished
> 
> So, it looks to me, that kolab.conf runs fine, right?

Right.

> Nevertheless, 
> clamav is not "active" when I call /kolab/bin/openpkg rc all start and 
> check the status. Interestingly, I get the same error on a fresh install.

Yes, you have to solve the clamav problem, otherwise of course it
won't work. One of my other mails contained instructions where to
look.

Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From s.kim at hia.rwth-aachen.de  Fri Jul 18 13:32:28 2008
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Fri, 18 Jul 2008 13:32:28 +0200
Subject: Kolab-users Digest, Vol 53, Issue 18
In-Reply-To: <mailman.8.1216375204.9094.kolab-users@kolab.org>
References: <mailman.8.1216375204.9094.kolab-users@kolab.org>
Message-ID: <48807F4C.7030907@hia.rwth-aachen.de>

>
> etreff:
> Re: Can't receive mail after upgrading from 2.2rc2 to 2.2 release: 
> Even more information
> Von:
> Thomas Arendsen Hein <thomas at intevation.de>
> Datum:
> Fri, 18 Jul 2008 09:27:58 +0200
> An:
> kolab-users at kolab.org
>
> An:
> kolab-users at kolab.org
>
>
> * Saim Kim <s.kim at hia.rwth-aachen.de> [20080717 18:18]:
>   
>> so after some more checking I'm quite sure that clamav is the reason for
>> the mail error. Even it is started with the /kolab/bin/openpkg rc all
>> start, if I check the status it is still not active:
>>
>> mykolab:/kolab/var/clamav# /kolab/bin/openpkg rc clamav start
>>
>> OpenPKG: start: clamav.
>>
>> mykolab:/kolab/var/clamav# /kolab/bin/openpkg rc clamav status
>>
>> OpenPKG: status: clamav.
>> clamav_enable="yes"
>> clamav_usable="unknown"
>> clamav_active="no"
>>
>> So, how can I make clamav start?
>>     
>
> Or rather: why does your correct way of starting clamav fail?
>
> There is /kolab/var/clamav/clamd.log or your could try manually
> executing /kolab/bin/clamscan
>
> You might want to try manually updating the virus database:
> # su - kolab-r
> $ freshclam
>
>   
Ok,

I did the things you suggested and clamav still won't start. 
Interestingly, when I try to execute /kolab/bin/clamscan I get an error 
message stating that it is an invalid machine command (ung?ltiger 
Maschinenbefehl). The libraries are linked right (checked with ldd) So, 
can it be that the clamav package has a compilation error? I tested it 
on a clean debian etch server from scratch so my installation should be 
error free. I'll try to recompile  the clamav package from source and 
give feedback as soon as available.

Best regards,
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
-------------------------------------------------------------------------- 


From thomas at intevation.de  Fri Jul 18 15:30:09 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 18 Jul 2008 15:30:09 +0200
Subject: Kolab-users Digest, Vol 53, Issue 18
In-Reply-To: <48807F4C.7030907@hia.rwth-aachen.de>
References: <mailman.8.1216375204.9094.kolab-users@kolab.org>
	<48807F4C.7030907@hia.rwth-aachen.de>
Message-ID: <20080718133009.GD32121.thomas@intevation.de>

* Saim Kim <s.kim at hia.rwth-aachen.de> [20080718 13:31]:
> >> So, how can I make clamav start?
> >
> > Or rather: why does your correct way of starting clamav fail?
> >
> > There is /kolab/var/clamav/clamd.log or your could try manually
> > executing /kolab/bin/clamscan
>
> Ok,
> 
> I did the things you suggested and clamav still won't start. 

My intention was to find the problem, not to make it work.

> Interestingly, when I try to execute /kolab/bin/clamscan I get an error 
> message stating that it is an invalid machine command (ung?ltiger 
> Maschinenbefehl). The libraries are linked right (checked with ldd) So, 
> can it be that the clamav package has a compilation error? I tested it 
> on a clean debian etch server from scratch so my installation should be 
> error free. I'll try to recompile  the clamav package from source and 
> give feedback as soon as available.

Known problem, you'll have to recompile gmp and clamav, see
http://lists.wald.intevation.org/pipermail/kolab-users-de/2008-July/000052.html
(in German, but I suspect you'll understand it :))

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From s.kim at hia.rwth-aachen.de  Fri Jul 18 17:47:45 2008
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Fri, 18 Jul 2008 17:47:45 +0200
Subject: Can't receive mail after upgrading from 2.2rc2 to 2.2 release:
	Even more information
In-Reply-To: <20080718072758.GC10397.thomas@intevation.de>
References: <mailman.2758.1216306477.2108.kolab-users@kolab.org>
	<487F710F.8070406@hia.rwth-aachen.de>
	<20080718072758.GC10397.thomas@intevation.de>
Message-ID: <4880BB21.1080502@hia.rwth-aachen.de>

Thomas Arendsen Hein schrieb:
> * Saim Kim <s.kim at hia.rwth-aachen.de> [20080717 18:18]:
>   
>> so after some more checking I'm quite sure that clamav is the reason for
>> the mail error. Even it is started with the /kolab/bin/openpkg rc all
>> start, if I check the status it is still not active:
>>
>> mykolab:/kolab/var/clamav# /kolab/bin/openpkg rc clamav start
>>
>> OpenPKG: start: clamav.
>>
>> mykolab:/kolab/var/clamav# /kolab/bin/openpkg rc clamav status
>>
>> OpenPKG: status: clamav.
>> clamav_enable="yes"
>> clamav_usable="unknown"
>> clamav_active="no"
>>
>> So, how can I make clamav start?
>>     
>
> Or rather: why does your correct way of starting clamav fail?
>
> There is /kolab/var/clamav/clamd.log or your could try manually
> executing /kolab/bin/clamscan
>
> You might want to try manually updating the virus database:
> # su - kolab-r
> $ freshclam
>
>   
>> P.s.: Sorry for writing so many mails today...
>>     
>
> With this and my other two mails you might be able to get a working
> system again, but there is something wrong on your machine or
> installation which causes all this.
>
> If this should be used for production I strongly recommend to get
> professional support from the Kolab Konsortium (which Intevation is
> part of) or at least help from another person or company with some
> experience in troubleshooting mail server installations.
>
> See http://www.kolab-konsortium.de/
>
> Regards,
> Thomas
>
>   
Ok,

even more research closed it pretty much in to clamav failing to launch 
as described earlier. I have several assumptions: At the first download 
of the files from one of the mirrors (I don't remember which one) the 
MD5Check failed for a couple of package. Of course, I can't remember 
them BUT I'm quite sure one of them was clamav. So, I downloaded them 
from another mirror checked it and it passed the MD5Check. After, 
recompiling the clamav rpm package from source on my machine it still 
doesn't work after a complete fresh kolab installation. Is it by any 
means possible that a couple of corrupted rpm packages made it onto the 
mirrors? Even kolab server 2.2 rc3 has the same error.

And it seems that I'm not the only one: there is an issue on the kolab 
bug tracker from jurgen: kolab/issue2898. He has the exact problem. 
Also, in an old issue a similiar effect is dicussed: 
https://www.intevation.de/roundup/kolab/issue943 In our case the 
secondary scanner fails as well. Thus, the mail is passed in to 
quaratine and blocks all mail delivery.

In conclusion, does anybody have a stable running kolab server 2.2 
release version? Just wondering because it wouldn't even start on a 
sparkling fresh debian etch installation -unlike the rc2 version.

Best regards,
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
-------------------------------------------------------------------------- 


From thorsten.schnebeck at gmx.net  Fri Jul 18 18:05:53 2008
From: thorsten.schnebeck at gmx.net (Thorsten Schnebeck)
Date: Fri, 18 Jul 2008 18:05:53 +0200
Subject: Can't receive mail after upgrading from 2.2rc2 to 2.2 release:
	Even more information
In-Reply-To: <4880BB21.1080502@hia.rwth-aachen.de>
References: <mailman.2758.1216306477.2108.kolab-users@kolab.org>
	<20080718072758.GC10397.thomas@intevation.de>
	<4880BB21.1080502@hia.rwth-aachen.de>
Message-ID: <200807181805.54483.thorsten.schnebeck@gmx.net>

Am Freitag 18 Juli 2008 schrieb Saim Kim:
> In conclusion, does anybody have a stable running kolab server 2.2
> release version? Just wondering because it wouldn't even start on a
> sparkling fresh debian etch installation -unlike the rc2 version.

tail  /kolab/var/clamav/freshclam.log
daily.cld updated (version: 7747, sigs: 47422, f-level: 33, builder: arnaud)
Database updated (359726 signatures) from database.clamav.net (IP: 
62.26.160.3)
Clamd successfully notified about the update.
--------------------------------------
ClamAV update process started at Fri Jul 18 17:00:13 2008
main.cvd is up to date (version: 47, sigs: 312304, f-level: 31, builder: sven)
Downloading daily-7748.cdiff [100%]
daily.cld updated (version: 7748, sigs: 47439, f-level: 33, builder: arnaud)
Database updated (359743 signatures) from database.clamav.net (IP: 
85.10.242.82)
Clamd successfully notified about the update.

tail  -n 200  /kolab/var/clamav/clamd.log
Thu Jul 17 11:46:19 2008 -> SelfCheck: Database status OK.
Thu Jul 17 12:17:22 2008 -> SelfCheck: Database status OK.
Thu Jul 17 12:53:19 2008 -> SelfCheck: Database status OK.
Thu Jul 17 13:27:18 2008 -> SelfCheck: Database status OK.
Thu Jul 17 14:00:07 2008 -> SelfCheck: Database modification detected. Forcing 
reload.
Thu Jul 17 14:00:08 2008 -> Reading databases from /kolab-2.2/share/clamav
Thu Jul 17 14:00:14 2008 -> Database correctly reloaded (355094 signatures)
Thu Jul 17 14:43:37 2008 -> SelfCheck: Database status OK.
Thu Jul 17 15:24:05 2008 -> SelfCheck: Database status OK.
Thu Jul 17 15:54:42 2008 -> SelfCheck: Database status OK.
Thu Jul 17 16:00:23 2008 -> Reading databases from /kolab-2.2/share/clamav
Thu Jul 17 16:00:36 2008 -> Database correctly reloaded (355117 signatures)
Thu Jul 17 16:25:51 2008 -> SelfCheck: Database status OK.
Thu Jul 17 17:07:45 2008 -> SelfCheck: Database status OK.
Thu Jul 17 17:40:12 2008 -> SelfCheck: Database status OK.
Thu Jul 17 18:13:42 2008 -> SelfCheck: Database status OK.

md5sum /opt/kolab_build/clamav-0.93.3-20080708.src.rpm
cf9c9edba28087f748ccdd4eaa7daecd  /opt/kolab_build/clamav-0.93.3-20080708.src.rpm

No problems on master and slave server.

Bye

  Thorsten


From fiona-lists at traum-welten.com  Fri Jul 18 18:34:06 2008
From: fiona-lists at traum-welten.com (=?ISO-8859-1?Q?Fiona_D=FCrst?=)
Date: Fri, 18 Jul 2008 18:34:06 +0200
Subject: Opensuse integrated version 
Message-ID: <A427B87B-724A-40FE-8518-6D3C18DAFE89@traum-welten.com>

Hi everyone

First of all, i want to say thanks to for the integrated version of  
Kolab. Makes a few things easier for me and my administrators. :)

I just wanted to ask if there will be an integrated version of Kolab  
2.2 and when will it become avaible?

Best regards

Fiona D?rst

From issanyr at gmail.com  Fri Jul 18 20:08:30 2008
From: issanyr at gmail.com (Reza Issany)
Date: Fri, 18 Jul 2008 20:08:30 +0200
Subject: need some helps with kolab 2.2
Message-ID: <4880DC1E.7000904@gmail.com>

Hello,

Sorry for my bad english. I'm a french people.

I've just made a fresh installation of kolab 2.2 on a debian server and 
I could not
send or receive any email messages.

The error log is :
Jul 18 19:50:54 xxxxxx <info> postfix/smtp[5326]: E0CF29276: 
to=<reza at xxx.info>, relay=127.0.0.1[127.0.0.1]:10024, delay=7.3, 
delays=0.07/0.01/0.01/7.2, dsn=4.5.0, status=deferred (host 
127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=04193-03, 
virus_scan FAILED: virus_scan: ALL VIRUS SCANNERS FAILED: Clam 
Antivirus-clamd av-scanner FAILED: CODE(0x89079b0) Too many retries to 
talk to /kolab/var/clamav/clamd.sock (Can't connect to UNIX socket 
/kolab/var/clamav/clamd.sock: 2) at (eval 99) line 310. at (eval 99) 
line 511.; Clam Antivirus - /kolab/bin/clamscan av-scanner FAILED: 
/kolab/bin/clamscan DIED on signal 4 (0004) at (eval 99) line 511. (in 
reply to end of DATA command))

I've already tried to lauch it manually using  /kolab/sbin/clamd 
--config-file=/kolab/etc/clamav/clamd.conf
but it can't start : Illegal Instruction

Any idea to resolve the problem ?

Thanks for your helps.

reza.


From thorsten.schnebeck at gmx.net  Fri Jul 18 22:38:19 2008
From: thorsten.schnebeck at gmx.net (Thorsten Schnebeck)
Date: Fri, 18 Jul 2008 22:38:19 +0200
Subject: master/slave setup via VPN?
Message-ID: <200807182238.20202.thorsten.schnebeck@gmx.net>

Hi,

I'm trying to use a Kolab-2.2 master/slave multi-domain setup with one special 
detail: The smtp communication is only via vpn available.

Lets create an example:

master.domain1.com: IP 1.2.3.4 + VPN 10.10.10.1
slave.domain2.com: IP 4.3.2.1 + VPN 10.10.10.2

on master I have users of the mail-domains maildomain1.com, maildomain2.com
on slave I have users of the mail-domains maildomain2.com(!), maildomain3.com

master collects all mails of all 3 maildomains.
If the users has its mailbox on slave if see something like this in the master 
postfix log:

connect to slave.domain2.com[4.3.2.1]: Connection timed out (port 25)
Jul 18 21:48:39 master <info> postfix/smtp[5227]: 72668274971: 
to=<test at maildomain3.com>, relay=none, delay=3350, delays=3320/0.06/30/0, 
dsn=4.4.1, status=deferred (connect to slave.domain2.com[4.3.2.1]: Connection 
timed out)

So, I need a config that transfers the Std-IP of slave to its VPN-IP but only 
for postfix. IMHO I can not use transport.db cause I have users of 
maildomain2.com on master _and_ slave.(?)

Suggestions?

Bye

  Thorsten 


From aspineux at gmail.com  Sat Jul 19 00:46:57 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sat, 19 Jul 2008 00:46:57 +0200
Subject: master/slave setup via VPN?
In-Reply-To: <200807182238.20202.thorsten.schnebeck@gmx.net>
References: <200807182238.20202.thorsten.schnebeck@gmx.net>
Message-ID: <71fe4e760807181546v704106d1p13d34051bcdba055@mail.gmail.com>

On Fri, Jul 18, 2008 at 10:38 PM, Thorsten Schnebeck
<thorsten.schnebeck at gmx.net> wrote:
> Hi,
>
> I'm trying to use a Kolab-2.2 master/slave multi-domain setup with one special
> detail: The smtp communication is only via vpn available.
>
> Lets create an example:
>
> master.domain1.com: IP 1.2.3.4 + VPN 10.10.10.1
> slave.domain2.com: IP 4.3.2.1 + VPN 10.10.10.2
>
> on master I have users of the mail-domains maildomain1.com, maildomain2.com
> on slave I have users of the mail-domains maildomain2.com(!), maildomain3.com
>
> master collects all mails of all 3 maildomains.
> If the users has its mailbox on slave if see something like this in the master
> postfix log:
>
> connect to slave.domain2.com[4.3.2.1]: Connection timed out (port 25)
> Jul 18 21:48:39 master <info> postfix/smtp[5227]: 72668274971:
> to=<test at maildomain3.com>, relay=none, delay=3350, delays=3320/0.06/30/0,
> dsn=4.4.1, status=deferred (connect to slave.domain2.com[4.3.2.1]: Connection
> timed out)
>

You can add this entry in /etc/hosts

10.10.10.2               slave.domain2.com

> So, I need a config that transfers the Std-IP of slave to its VPN-IP but only
> for postfix. IMHO I can not use transport.db cause I have users of
> maildomain2.com on master _and_ slave.(?)
>
> Suggestions?
>
> Bye
>
>  Thorsten
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From aspineux at gmail.com  Sat Jul 19 00:54:38 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sat, 19 Jul 2008 00:54:38 +0200
Subject: need some helps with kolab 2.2
In-Reply-To: <4880DC1E.7000904@gmail.com>
References: <4880DC1E.7000904@gmail.com>
Message-ID: <71fe4e760807181554v2c001f62p340c143e0a8202fd@mail.gmail.com>

On Fri, Jul 18, 2008 at 8:08 PM, Reza Issany <issanyr at gmail.com> wrote:
> Hello,
>
> Sorry for my bad english. I'm a french people.
>
> I've just made a fresh installation of kolab 2.2 on a debian server and
> I could not
> send or receive any email messages.
>
> The error log is :
> Jul 18 19:50:54 xxxxxx <info> postfix/smtp[5326]: E0CF29276:
> to=<reza at xxx.info>, relay=127.0.0.1[127.0.0.1]:10024, delay=7.3,
> delays=0.07/0.01/0.01/7.2, dsn=4.5.0, status=deferred (host
> 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=04193-03,
> virus_scan FAILED: virus_scan: ALL VIRUS SCANNERS FAILED: Clam
> Antivirus-clamd av-scanner FAILED: CODE(0x89079b0) Too many retries to
> talk to /kolab/var/clamav/clamd.sock (Can't connect to UNIX socket
> /kolab/var/clamav/clamd.sock: 2) at (eval 99) line 310. at (eval 99)
> line 511.; Clam Antivirus - /kolab/bin/clamscan av-scanner FAILED:
> /kolab/bin/clamscan DIED on signal 4 (0004) at (eval 99) line 511. (in
> reply to end of DATA command))
>
> I've already tried to lauch it manually using  /kolab/sbin/clamd
> --config-file=/kolab/etc/clamav/clamd.conf
> but it can't start : Illegal Instruction
>
> Any idea to resolve the problem ?

If you have time constraint, you can disable amavis from inside the webadmin,
to get a running kolab.
Then look in the kolabwiki for freshclam , and how to update the AV signatures.
Then try to start the AV.
check if it is running.
reset the configuration of the mail filtering inside the web admin

Is-it working


>
> Thanks for your helps.
>
> reza.
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From aspineux at gmail.com  Sat Jul 19 01:00:03 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sat, 19 Jul 2008 01:00:03 +0200
Subject: Can't receive mail after upgrading from 2.2rc2 to 2.2
	release: Even more information
In-Reply-To: <4880BB21.1080502@hia.rwth-aachen.de>
References: <mailman.2758.1216306477.2108.kolab-users@kolab.org>
	<487F710F.8070406@hia.rwth-aachen.de>
	<20080718072758.GC10397.thomas@intevation.de>
	<4880BB21.1080502@hia.rwth-aachen.de>
Message-ID: <71fe4e760807181600w322af32ew17459851e220ec55@mail.gmail.com>

On Fri, Jul 18, 2008 at 5:47 PM, Saim Kim <s.kim at hia.rwth-aachen.de> wrote:
> Thomas Arendsen Hein schrieb:
>> * Saim Kim <s.kim at hia.rwth-aachen.de> [20080717 18:18]:
>>
>>> so after some more checking I'm quite sure that clamav is the reason for
>>> the mail error. Even it is started with the /kolab/bin/openpkg rc all
>>> start, if I check the status it is still not active:
>>>
>>> mykolab:/kolab/var/clamav# /kolab/bin/openpkg rc clamav start
>>>
>>> OpenPKG: start: clamav.
>>>
>>> mykolab:/kolab/var/clamav# /kolab/bin/openpkg rc clamav status
>>>
>>> OpenPKG: status: clamav.
>>> clamav_enable="yes"
>>> clamav_usable="unknown"
>>> clamav_active="no"
>>>
>>> So, how can I make clamav start?
>>>
>>
>> Or rather: why does your correct way of starting clamav fail?
>>
>> There is /kolab/var/clamav/clamd.log or your could try manually
>> executing /kolab/bin/clamscan
>>
>> You might want to try manually updating the virus database:
>> # su - kolab-r
>> $ freshclam
>>
>>
>>> P.s.: Sorry for writing so many mails today...
>>>
>>
>> With this and my other two mails you might be able to get a working
>> system again, but there is something wrong on your machine or
>> installation which causes all this.
>>
>> If this should be used for production I strongly recommend to get
>> professional support from the Kolab Konsortium (which Intevation is
>> part of) or at least help from another person or company with some
>> experience in troubleshooting mail server installations.
>>
>> See http://www.kolab-konsortium.de/
>>
>> Regards,
>> Thomas
>>
>>
> Ok,
>
> even more research closed it pretty much in to clamav failing to launch
> as described earlier. I have several assumptions: At the first download
> of the files from one of the mirrors (I don't remember which one) the
> MD5Check failed for a couple of package. Of course, I can't remember
> them BUT I'm quite sure one of them was clamav. So, I downloaded them
> from another mirror checked it and it passed the MD5Check. After,
> recompiling the clamav rpm package from source on my machine it still
> doesn't work after a complete fresh kolab installation. Is it by any

Check for integrity of mm package first,
recompile mm if needed, and cmald once more time.

> means possible that a couple of corrupted rpm packages made it onto the
> mirrors? Even kolab server 2.2 rc3 has the same error.
>
> And it seems that I'm not the only one: there is an issue on the kolab
> bug tracker from jurgen: kolab/issue2898. He has the exact problem.
> Also, in an old issue a similiar effect is dicussed:
> https://www.intevation.de/roundup/kolab/issue943 In our case the
> secondary scanner fails as well. Thus, the mail is passed in to
> quaratine and blocks all mail delivery.
>
> In conclusion, does anybody have a stable running kolab server 2.2
> release version? Just wondering because it wouldn't even start on a
> sparkling fresh debian etch installation -unlike the rc2 version.
>
> Best regards,
> 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
> --------------------------------------------------------------------------
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From uga at domestic.de  Sat Jul 19 02:08:26 2008
From: uga at domestic.de (Uwe Galle)
Date: Sat, 19 Jul 2008 02:08:26 +0200
Subject: kolab_bootstrap -b of kolab 2.2.0-1.1 does not work on openSUSE 10.3
Message-ID: <4881307A.6090800@domestic.de>

Hi,

as I tried to install kolab 2.2.0-1.1 on my openSUSE 10.3 system today kolab_bootstrap -b reported at first:

Detected running slurpd processes

But there was no slurpd process. I saw that in the script the usual line

      if( `ps -elf|grep slurpd|grep -v grep` ) {

was replaced by the line

      if( `ps -elf|grep s[l]urpd` ) {

This line didn't filter the string "slurpd" of the grep command out and always
finds a running slurpd process.

I changed the line back and at next got the error

chown: Zugriff auf ?/var/lib/ldap/*? nicht m?glich: Datei oder Verzeichnis nicht
gefunden

I saw that the script deletes the whole /var/lib/ldap/ but doesn't create any
new database here so that slapd cannot start. Because the owner of
/var/lib/ldap/ is ldap and other owners have no other rights I assigned the read
and write right for other users to /var/lib/ldap/ in order to be sure that there will be no
permission problems here. Furthermore I run kolab_bootstrap -b as root.

The problem is as far as I can see that no database is created in
/var/lib/ldap/. This is no permission problem. I used all default settings.

There was already a similar problem on the kolab list (http://www.kolab.org/pipermail/kolab-users/2008-April/007779.html)
but in that case the script continued. In my case the script exits with the message

Could not start temporary slapd:  at /usr/share/kolab/scripts/kolab_bootstrap line 469.

It was not possible to install kolab. Please help.


From thomas at intevation.de  Sat Jul 19 09:09:26 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Sat, 19 Jul 2008 09:09:26 +0200
Subject: need some helps with kolab 2.2
In-Reply-To: <4880DC1E.7000904@gmail.com>
References: <4880DC1E.7000904@gmail.com>
Message-ID: <20080719070926.GA12469.thomas@intevation.de>

* Reza Issany <issanyr at gmail.com> [20080718 20:08]:
> I've already tried to lauch it manually using  /kolab/sbin/clamd 
> --config-file=/kolab/etc/clamav/clamd.conf
> but it can't start : Illegal Instruction
> 
> Any idea to resolve the problem ?

You need to compile the packages "gmp" and "clamav" yourself to
match your processor.

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From thomas at intevation.de  Sat Jul 19 09:15:55 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Sat, 19 Jul 2008 09:15:55 +0200
Subject: kolab_bootstrap -b of kolab 2.2.0-1.1 does not work on openSUSE
	10.3
In-Reply-To: <4881307A.6090800@domestic.de>
References: <4881307A.6090800@domestic.de>
Message-ID: <20080719071555.GB12469.thomas@intevation.de>

* Uwe Galle <uga at domestic.de> [20080719 02:08]:
> But there was no slurpd process. I saw that in the script the usual line
>
>       if( `ps -elf|grep slurpd|grep -v grep` ) {
>
> was replaced by the line
>
>       if( `ps -elf|grep s[l]urpd` ) {
>
> This line didn't filter the string "slurpd" of the grep command out and always
> finds a running slurpd process.

$ echo s[l]urpd
s[l]urpd
$ touch slurpd
$ echo s[l]urpd
slurpd

Maybe you have a file or directory named 'slurpd' in the same
directory where you run kolab_bootstrap?
Anyway, I'll add some quoting now to circumvent this problem in the
future.

> I saw that the script deletes the whole /var/lib/ldap/ but doesn't create any
> new database here so that slapd cannot start. Because the owner of
> /var/lib/ldap/ is ldap and other owners have no other rights I assigned the read
> and write right for other users to /var/lib/ldap/ in order to be sure that there will be no
> permission problems here. Furthermore I run kolab_bootstrap -b as root.

This is a problem specific to OpenSUSE, so I can't help here.

> It was not possible to install kolab. Please help.

The OpenPKG packages might be an alternative for you.

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From aspineux at gmail.com  Sat Jul 19 09:52:19 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sat, 19 Jul 2008 09:52:19 +0200
Subject: Can't receive mail after upgrading from 2.2rc2 to 2.2
	release: Even more information
In-Reply-To: <71fe4e760807181600w322af32ew17459851e220ec55@mail.gmail.com>
References: <mailman.2758.1216306477.2108.kolab-users@kolab.org>
	<487F710F.8070406@hia.rwth-aachen.de>
	<20080718072758.GC10397.thomas@intevation.de>
	<4880BB21.1080502@hia.rwth-aachen.de>
	<71fe4e760807181600w322af32ew17459851e220ec55@mail.gmail.com>
Message-ID: <71fe4e760807190052y7299aae6r3e798b1b7a530438@mail.gmail.com>

On Sat, Jul 19, 2008 at 1:00 AM, Alain Spineux <aspineux at gmail.com> wrote:
> On Fri, Jul 18, 2008 at 5:47 PM, Saim Kim <s.kim at hia.rwth-aachen.de> wrote:
>> Thomas Arendsen Hein schrieb:
>>> * Saim Kim <s.kim at hia.rwth-aachen.de> [20080717 18:18]:
>>>
>>>> so after some more checking I'm quite sure that clamav is the reason for
>>>> the mail error. Even it is started with the /kolab/bin/openpkg rc all
>>>> start, if I check the status it is still not active:
>>>>
>>>> mykolab:/kolab/var/clamav# /kolab/bin/openpkg rc clamav start
>>>>
>>>> OpenPKG: start: clamav.
>>>>
>>>> mykolab:/kolab/var/clamav# /kolab/bin/openpkg rc clamav status
>>>>
>>>> OpenPKG: status: clamav.
>>>> clamav_enable="yes"
>>>> clamav_usable="unknown"
>>>> clamav_active="no"
>>>>
>>>> So, how can I make clamav start?
>>>>
>>>
>>> Or rather: why does your correct way of starting clamav fail?
>>>
>>> There is /kolab/var/clamav/clamd.log or your could try manually
>>> executing /kolab/bin/clamscan
>>>
>>> You might want to try manually updating the virus database:
>>> # su - kolab-r
>>> $ freshclam
>>>
>>>
>>>> P.s.: Sorry for writing so many mails today...
>>>>
>>>
>>> With this and my other two mails you might be able to get a working
>>> system again, but there is something wrong on your machine or
>>> installation which causes all this.
>>>
>>> If this should be used for production I strongly recommend to get
>>> professional support from the Kolab Konsortium (which Intevation is
>>> part of) or at least help from another person or company with some
>>> experience in troubleshooting mail server installations.
>>>
>>> See http://www.kolab-konsortium.de/
>>>
>>> Regards,
>>> Thomas
>>>
>>>
>> Ok,
>>
>> even more research closed it pretty much in to clamav failing to launch
>> as described earlier. I have several assumptions: At the first download
>> of the files from one of the mirrors (I don't remember which one) the
>> MD5Check failed for a couple of package. Of course, I can't remember
>> them BUT I'm quite sure one of them was clamav. So, I downloaded them
>> from another mirror checked it and it passed the MD5Check. After,
>> recompiling the clamav rpm package from source on my machine it still
>> doesn't work after a complete fresh kolab installation. Is it by any
>
> Check for integrity of mm package first,
> recompile mm if needed, and cmald once more time.

ops the gmp module, not mm

>
>> means possible that a couple of corrupted rpm packages made it onto the
>> mirrors? Even kolab server 2.2 rc3 has the same error.
>>
>> And it seems that I'm not the only one: there is an issue on the kolab
>> bug tracker from jurgen: kolab/issue2898. He has the exact problem.
>> Also, in an old issue a similiar effect is dicussed:
>> https://www.intevation.de/roundup/kolab/issue943 In our case the
>> secondary scanner fails as well. Thus, the mail is passed in to
>> quaratine and blocks all mail delivery.
>>
>> In conclusion, does anybody have a stable running kolab server 2.2
>> release version? Just wondering because it wouldn't even start on a
>> sparkling fresh debian etch installation -unlike the rc2 version.
>>
>> Best regards,
>> 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
>> --------------------------------------------------------------------------
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>
>
>
>
> --
> Alain Spineux
> aspineux gmail com
> May the sources be with you
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From aspineux at gmail.com  Sat Jul 19 09:59:16 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sat, 19 Jul 2008 09:59:16 +0200
Subject: kolab_bootstrap -b of kolab 2.2.0-1.1 does not work on openSUSE
	10.3
In-Reply-To: <4881307A.6090800@domestic.de>
References: <4881307A.6090800@domestic.de>
Message-ID: <71fe4e760807190059x23b04dbbod11b8c57b3d08aa0@mail.gmail.com>

On Sat, Jul 19, 2008 at 2:08 AM, Uwe Galle <uga at domestic.de> wrote:
> Hi,
>
> as I tried to install kolab 2.2.0-1.1 on my openSUSE 10.3 system today kolab_bootstrap -b reported at first:
>
> Detected running slurpd processes
>
> But there was no slurpd process. I saw that in the script the usual line
>
>      if( `ps -elf|grep slurpd|grep -v grep` ) {
>
> was replaced by the line
>
>      if( `ps -elf|grep s[l]urpd` ) {
>
> This line didn't filter the string "slurpd" of the grep command out and always
> finds a running slurpd process.
>
> I changed the line back and at next got the error
>
> chown: Zugriff auf „/var/lib/ldap/*" nicht möglich: Datei oder Verzeichnis nicht
> gefunden
>
> I saw that the script deletes the whole /var/lib/ldap/ but doesn't create any
> new database here so that slapd cannot start. Because the owner of
> /var/lib/ldap/ is ldap and other owners have no other rights I assigned the read
> and write right for other users to /var/lib/ldap/ in order to be sure that there will be no
> permission problems here. Furthermore I run kolab_bootstrap -b as root.
>
> The problem is as far as I can see that no database is created in
> /var/lib/ldap/. This is no permission problem. I used all default settings.
>
> There was already a similar problem on the kolab list (http://www.kolab.org/pipermail/kolab-users/2008-April/007779.html)
> but in that case the script continued. In my case the script exits with the message
>
> Could not start temporary slapd:  at /usr/share/kolab/scripts/kolab_bootstrap line 469.

start slapd manualy, and look for the errors on the console

# where_is_your_slapd_on_suse/slapd -d 255

>
> It was not possible to install kolab. Please help.
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From aspineux at gmail.com  Sat Jul 19 10:02:42 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sat, 19 Jul 2008 10:02:42 +0200
Subject: need some helps with kolab 2.2
In-Reply-To: <20080719070926.GA12469.thomas@intevation.de>
References: <4880DC1E.7000904@gmail.com>
	<20080719070926.GA12469.thomas@intevation.de>
Message-ID: <71fe4e760807190102v1b200805kc5b17ce17c456857@mail.gmail.com>

On Sat, Jul 19, 2008 at 9:09 AM, Thomas Arendsen Hein
<thomas at intevation.de> wrote:
> * Reza Issany <issanyr at gmail.com> [20080718 20:08]:
>> I've already tried to lauch it manually using  /kolab/sbin/clamd
>> --config-file=/kolab/etc/clamav/clamd.conf
>> but it can't start : Illegal Instruction
>>
>> Any idea to resolve the problem ?
>
> You need to compile the packages "gmp" and "clamav" yourself to
> match your processor.
>

This is the case if you have reused binary packages compiled on another box.

> Regards,
> Thomas
>
> --
> thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
> Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
> Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From aspineux at gmail.com  Sat Jul 19 10:15:48 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sat, 19 Jul 2008 10:15:48 +0200
Subject: IMAP recovery
In-Reply-To: <4880472E.4090509@hia.rwth-aachen.de>
References: <002001c8e867$789279c0$6400a8c0@ldssfoi>
	<20080718070520.GA10397.thomas@intevation.de>
	<4880472E.4090509@hia.rwth-aachen.de>
Message-ID: <71fe4e760807190115i24ad815ag18487ac290cf7dd3@mail.gmail.com>

On Fri, Jul 18, 2008 at 9:33 AM, Saim Kim <s.kim at hia.rwth-aachen.de> wrote:
> Thomas Arendsen Hein schrieb:
>> * Saim Kim <s.kim at hia.rwth-aachen.de> [20080718 01:47]:
>>
>>> I tried to do a complete IMAP recovery as described in the backups how-to in the wiki. But so far I have not been able to access the mails e.g. calendar events. I ran the cyrreconstruct command like this (as kolab-r):
>>> /kolab/bin/cyrreconstruct -rf user/user/folder/subfolder at mydomain.com
>>>
>>> When I log into Horde I have an empty calendar eventhough the directory (imapd/spool/...) is full with events? Any hints?
>>>
>>
>> cyrreconstruct can't reconstruct (or rather invent) ACLs (not
>> related to your problem) and annotations (the folder meta
>> information where e.g. the type of a folder is stored).
>>
>> See http://kolab.org/pipermail/kolab-users/2007-October/006934.html
>>
>> Thomas
>>
>>
> Hello Thomas,
>
> the Wikki was quite clear about the ACL's. So, of course I did save the
> ACL's with the mailboxlist and read it back before the cyrreconstruct. I
> checked in cyradm and all mailboxes are shown with the correct ACL's.
> Interestingly, also a broken mailbox which prevent the automatic
> freebusy regeneration before suddenly didn't bother the process anymore.
>
> The problem is, that I don't see any email e.g. calendar events in my

Not clear ! You can see normal email but not calendar events ?
If so update your annotation as Thomas told you

> recovered system even though the email is in the spool directory and the
> mailbox is shown correctly in the cyradm interface.
>
> Best regards,
> 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
> --------------------------------------------------------------------------
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From issanyr at gmail.com  Sat Jul 19 10:24:49 2008
From: issanyr at gmail.com (Reza Issany)
Date: Sat, 19 Jul 2008 10:24:49 +0200
Subject: need some helps with kolab 2.2
In-Reply-To: <71fe4e760807190102v1b200805kc5b17ce17c456857@mail.gmail.com>
References: <4880DC1E.7000904@gmail.com>	<20080719070926.GA12469.thomas@intevation.de>
	<71fe4e760807190102v1b200805kc5b17ce17c456857@mail.gmail.com>
Message-ID: <4881A4D1.60805@gmail.com>

I have reinstall kolab from source on a vmware machine and all works fine.

I'm trying to get working Thunderbird, but I'm looking for a tutorial to 
share
calendars, address books, and tasks.

Ldap is correctly configured and working.

Where could I find manuals to configure calendars on thunderbird ?

Alain Spineux a ?crit :
> On Sat, Jul 19, 2008 at 9:09 AM, Thomas Arendsen Hein
> <thomas at intevation.de> wrote:
>   
>> * Reza Issany <issanyr at gmail.com> [20080718 20:08]:
>>     
>>> I've already tried to lauch it manually using  /kolab/sbin/clamd
>>> --config-file=/kolab/etc/clamav/clamd.conf
>>> but it can't start : Illegal Instruction
>>>
>>> Any idea to resolve the problem ?
>>>       
>> You need to compile the packages "gmp" and "clamav" yourself to
>> match your processor.
>>
>>     
>
> This is the case if you have reused binary packages compiled on another box.
>
>   
>> Regards,
>> Thomas
>>
>> --
>> thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
>> Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
>> Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>
>>     
>
>
>
>   


From aspineux at gmail.com  Sat Jul 19 10:52:53 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sat, 19 Jul 2008 10:52:53 +0200
Subject: need some helps with kolab 2.2
In-Reply-To: <4881A4D1.60805@gmail.com>
References: <4880DC1E.7000904@gmail.com>
	<20080719070926.GA12469.thomas@intevation.de>
	<71fe4e760807190102v1b200805kc5b17ce17c456857@mail.gmail.com>
	<4881A4D1.60805@gmail.com>
Message-ID: <71fe4e760807190152m584614f0m72f1dd9ece4543be@mail.gmail.com>

On Sat, Jul 19, 2008 at 10:24 AM, Reza Issany <issanyr at gmail.com> wrote:
> I have reinstall kolab from source on a vmware machine and all works fine.
>
> I'm trying to get working Thunderbird, but I'm looking for a tutorial to
> share
> calendars, address books, and tasks.
>
> Ldap is correctly configured and working.
>
> Where could I find manuals to configure calendars on thunderbird ?

Sunbird is a standalone calendar client.
lightning is the "sunbird" extension for thunderbird.
search the internet for more info

>
> Alain Spineux a ?crit :
>>
>> On Sat, Jul 19, 2008 at 9:09 AM, Thomas Arendsen Hein
>> <thomas at intevation.de> wrote:
>>
>>>
>>> * Reza Issany <issanyr at gmail.com> [20080718 20:08]:
>>>
>>>>
>>>> I've already tried to lauch it manually using  /kolab/sbin/clamd
>>>> --config-file=/kolab/etc/clamav/clamd.conf
>>>> but it can't start : Illegal Instruction
>>>>
>>>> Any idea to resolve the problem ?
>>>>
>>>
>>> You need to compile the packages "gmp" and "clamav" yourself to
>>> match your processor.
>>>
>>>
>>
>> This is the case if you have reused binary packages compiled on another
>> box.
>>
>>
>>>
>>> Regards,
>>> Thomas
>>>
>>> --
>>> thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key:
>>> 0x5816791A
>>> Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B
>>> 18998
>>> Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
>>>
>>> _______________________________________________
>>> Kolab-users mailing list
>>> Kolab-users at kolab.org
>>> https://kolab.org/mailman/listinfo/kolab-users
>>>
>>>
>>
>>
>>
>>
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From thorsten.schnebeck at gmx.net  Sun Jul 20 13:32:57 2008
From: thorsten.schnebeck at gmx.net (Thorsten Schnebeck)
Date: Sun, 20 Jul 2008 13:32:57 +0200
Subject: master/slave setup via VPN?
In-Reply-To: <71fe4e760807181546v704106d1p13d34051bcdba055@mail.gmail.com>
References: <200807182238.20202.thorsten.schnebeck@gmx.net>
	<71fe4e760807181546v704106d1p13d34051bcdba055@mail.gmail.com>
Message-ID: <200807201332.57983.thorsten.schnebeck@gmx.net>

Am Samstag 19 Juli 2008 schrieb Alain Spineux:
> On Fri, Jul 18, 2008 at 10:38 PM, Thorsten Schnebeck
>
> <thorsten.schnebeck at gmx.net> wrote:
> > Hi,
> >
> > I'm trying to use a Kolab-2.2 master/slave multi-domain setup with one
> > special detail: The smtp communication is only via vpn available.
> >
> > Lets create an example:
> >
> > master.domain1.com: IP 1.2.3.4 + VPN 10.10.10.1
> > slave.domain2.com: IP 4.3.2.1 + VPN 10.10.10.2
> >
> > on master I have users of the mail-domains maildomain1.com,
> > maildomain2.com on slave I have users of the mail-domains
> > maildomain2.com(!), maildomain3.com
> >
> > master collects all mails of all 3 maildomains.
> > If the users has its mailbox on slave if see something like this in the
> > master postfix log:
> >
> > connect to slave.domain2.com[4.3.2.1]: Connection timed out (port 25)
> > Jul 18 21:48:39 master <info> postfix/smtp[5227]: 72668274971:
> > to=<test at maildomain3.com>, relay=none, delay=3350, delays=3320/0.06/30/0,
> > dsn=4.4.1, status=deferred (connect to slave.domain2.com[4.3.2.1]:
> > Connection timed out)
>
> You can add this entry in /etc/hosts
>
> 10.10.10.2               slave.domain2.com

Hmm, does not work :-(
When I ping to slave.domain2.com now it pings to 10.10.10.2
but postfix still want to deliver to the real IP. I also insert

smtp_host_lookup = native,dns

into  /kolab/etc/postfix/main.cf but this somehow does not change anything.
Using transport does also not work. Maybe a conflict with Kolabs homeserver 
ldap settings? 

Any ideas?

Bye

  Thorsten


From alex at swiftnetcomputers.biz  Sun Jul 20 19:17:56 2008
From: alex at swiftnetcomputers.biz (Alex Chejlyk)
Date: Sun, 20 Jul 2008 13:17:56 -0400
Subject: need some helps with kolab 2.2
In-Reply-To: <71fe4e760807190152m584614f0m72f1dd9ece4543be@mail.gmail.com>
References: <4880DC1E.7000904@gmail.com>	<20080719070926.GA12469.thomas@intevation.de>	<71fe4e760807190102v1b200805kc5b17ce17c456857@mail.gmail.com>	<4881A4D1.60805@gmail.com>
	<71fe4e760807190152m584614f0m72f1dd9ece4543be@mail.gmail.com>
Message-ID: <48837344.5030306@swiftnetcomputers.biz>

>> I'm trying to get working Thunderbird, but I'm looking for a tutorial to
>> share
>> calendars, address books, and tasks.


Synckolab is the extension that will allow sharing of addressbooks and 
calendar data. I prefer using ical for my calendering, the kolab wiki 
has an older write of how to setup webdav (for ical).


If you configure an ldap addressbook, the contacts sidebar extension 
will list the entries.

SyncKolab
http://www.gargan.org/extensions/synckolab.html

Contacts Sidebar:
http://jpeters.no-ip.com/extensions/index.php?page=tb_cs

Kolab Wiki, sunbird/lightning:
http://wiki.kolab.org/index.php/Setup_Mozilla_Sunbird_for_Kolab_2

Cheers,

Alex C.


From issanyr at gmail.com  Sun Jul 20 19:47:17 2008
From: issanyr at gmail.com (Reza Issany)
Date: Sun, 20 Jul 2008 19:47:17 +0200
Subject: need some helps with kolab 2.2
In-Reply-To: <48837344.5030306@swiftnetcomputers.biz>
References: <4880DC1E.7000904@gmail.com>	<20080719070926.GA12469.thomas@intevation.de>	<71fe4e760807190102v1b200805kc5b17ce17c456857@mail.gmail.com>	<4881A4D1.60805@gmail.com>	<71fe4e760807190152m584614f0m72f1dd9ece4543be@mail.gmail.com>
	<48837344.5030306@swiftnetcomputers.biz>
Message-ID: <48837A25.9000105@gmail.com>

Thanks for your helps. I'm going to test the contacts sidebar.

Alex Chejlyk a ?crit :
>>> I'm trying to get working Thunderbird, but I'm looking for a tutorial to
>>> share
>>> calendars, address books, and tasks.
>>>       
>
>
> Synckolab is the extension that will allow sharing of addressbooks and 
> calendar data. I prefer using ical for my calendering, the kolab wiki 
> has an older write of how to setup webdav (for ical).
>
>
> If you configure an ldap addressbook, the contacts sidebar extension 
> will list the entries.
>
> SyncKolab
> http://www.gargan.org/extensions/synckolab.html
>
> Contacts Sidebar:
> http://jpeters.no-ip.com/extensions/index.php?page=tb_cs
>
> Kolab Wiki, sunbird/lightning:
> http://wiki.kolab.org/index.php/Setup_Mozilla_Sunbird_for_Kolab_2
>
> Cheers,
>
> Alex C.
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
>   


From thorsten.schnebeck at gmx.net  Sun Jul 20 20:57:32 2008
From: thorsten.schnebeck at gmx.net (Thorsten Schnebeck)
Date: Sun, 20 Jul 2008 20:57:32 +0200
Subject: master/slave setup via VPN?
In-Reply-To: <200807201332.57983.thorsten.schnebeck@gmx.net>
References: <200807182238.20202.thorsten.schnebeck@gmx.net>
	<71fe4e760807181546v704106d1p13d34051bcdba055@mail.gmail.com>
	<200807201332.57983.thorsten.schnebeck@gmx.net>
Message-ID: <200807202057.32983.thorsten.schnebeck@gmx.net>

Am Sonntag 20 Juli 2008 schrieb Thorsten Schnebeck:
> Am Samstag 19 Juli 2008 schrieb Alain Spineux:
> > On Fri, Jul 18, 2008 at 10:38 PM, Thorsten Schnebeck

> > You can add this entry in /etc/hosts
> >
> > 10.10.10.2               slave.domain2.com
>
> Hmm, does not work :-(
> When I ping to slave.domain2.com now it pings to 10.10.10.2
> but postfix still want to deliver to the real IP. I also insert
>
> smtp_host_lookup = native,dns
>
> into  /kolab/etc/postfix/main.cf but this somehow does not change anything.
> Using transport does also not work. Maybe a conflict with Kolabs homeserver
> ldap settings?
>
> Any ideas?
Ok, seems to work now, but only after one timeout.
I use
smtp      unix  -       -       n       -       -       smtp -o 
fallback_relay=10.10.10.2

in master.cf

now I get
> connect to slave.domain2.com[4.3.2.1]: Connection timed out (port 25)
> to=<info at maildomain3.com>, relay=10.10.10.2[10.10.10.2]:25, delay=30,
> delays=0.03/0.01/30/0.06, dsn=2.0.0, status=sent (250 2.0.0 Ok: 
> queued as 1430A19F97C)  

and for some unknown reasons I get on the _slave_ for one of the mail domain 
names a

> : to=<info at maildomain3.com>, relay=none, delay=0.01, delays=0.01/0/0/0,
> dsn=5.4.6, status=bounced (mail for 10.10.10.2 loops back to myself) 

I have no problems with delivering mails to maildomain2.com on the slave. 
Maybe because maildomain2.com==domainname of the slave. But this could be 
solved in using the master as smarthost of the slave.

While now everything seems to work stable, this was a little bit of 
voodoo. :-/ weekend!! :-)

Tips & hints for a better or cleaner solution or a better understanding of 
this stuff are welcome!

Bye

  Thorsten


From aspineux at gmail.com  Mon Jul 21 11:45:39 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 21 Jul 2008 11:45:39 +0200
Subject: master/slave setup via VPN?
In-Reply-To: <200807201332.57983.thorsten.schnebeck@gmx.net>
References: <200807182238.20202.thorsten.schnebeck@gmx.net>
	<71fe4e760807181546v704106d1p13d34051bcdba055@mail.gmail.com>
	<200807201332.57983.thorsten.schnebeck@gmx.net>
Message-ID: <71fe4e760807210245x12e193bdl4aa4ab9c13788d21@mail.gmail.com>

On Sun, Jul 20, 2008 at 1:32 PM, Thorsten Schnebeck
<thorsten.schnebeck at gmx.net> wrote:
> Am Samstag 19 Juli 2008 schrieb Alain Spineux:
>> On Fri, Jul 18, 2008 at 10:38 PM, Thorsten Schnebeck
>>
>> <thorsten.schnebeck at gmx.net> wrote:
>> > Hi,
>> >
>> > I'm trying to use a Kolab-2.2 master/slave multi-domain setup with one
>> > special detail: The smtp communication is only via vpn available.
>> >
>> > Lets create an example:
>> >
>> > master.domain1.com: IP 1.2.3.4 + VPN 10.10.10.1
>> > slave.domain2.com: IP 4.3.2.1 + VPN 10.10.10.2
>> >
>> > on master I have users of the mail-domains maildomain1.com,
>> > maildomain2.com on slave I have users of the mail-domains
>> > maildomain2.com(!), maildomain3.com
>> >
>> > master collects all mails of all 3 maildomains.
>> > If the users has its mailbox on slave if see something like this in the
>> > master postfix log:
>> >
>> > connect to slave.domain2.com[4.3.2.1]: Connection timed out (port 25)
>> > Jul 18 21:48:39 master <info> postfix/smtp[5227]: 72668274971:
>> > to=<test at maildomain3.com>, relay=none, delay=3350, delays=3320/0.06/30/0,
>> > dsn=4.4.1, status=deferred (connect to slave.domain2.com[4.3.2.1]:
>> > Connection timed out)
>>
>> You can add this entry in /etc/hosts
>>
>> 10.10.10.2               slave.domain2.com
>
> Hmm, does not work :-(
> When I ping to slave.domain2.com now it pings to 10.10.10.2
> but postfix still want to deliver to the real IP. I also insert
>
> smtp_host_lookup = native,dns

Hmm, yes maybe, I didn't know about that
but "disable_dns_lookups" looks more appropriate.
I was thinking "disable_dns_lookups" was the default, happy
to learn something new

>
> into  /kolab/etc/postfix/main.cf but this somehow does not change anything.

Postfix store the "transport" information is has calculated and the
error message it got.
I dont know if it reuse this info for next try.

> Using transport does also not work. Maybe a conflict with Kolabs homeserver
> ldap settings?

Or maybe you have a bad use of transport.



>
> Any ideas?
>
> Bye
>
>  Thorsten
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From aspineux at gmail.com  Mon Jul 21 11:54:57 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 21 Jul 2008 11:54:57 +0200
Subject: master/slave setup via VPN?
In-Reply-To: <200807202057.32983.thorsten.schnebeck@gmx.net>
References: <200807182238.20202.thorsten.schnebeck@gmx.net>
	<71fe4e760807181546v704106d1p13d34051bcdba055@mail.gmail.com>
	<200807201332.57983.thorsten.schnebeck@gmx.net>
	<200807202057.32983.thorsten.schnebeck@gmx.net>
Message-ID: <71fe4e760807210254s524ca390k13254032f767e611@mail.gmail.com>

On Sun, Jul 20, 2008 at 8:57 PM, Thorsten Schnebeck
<thorsten.schnebeck at gmx.net> wrote:
> Am Sonntag 20 Juli 2008 schrieb Thorsten Schnebeck:
>> Am Samstag 19 Juli 2008 schrieb Alain Spineux:
>> > On Fri, Jul 18, 2008 at 10:38 PM, Thorsten Schnebeck
>
>> > You can add this entry in /etc/hosts
>> >
>> > 10.10.10.2               slave.domain2.com
>>
>> Hmm, does not work :-(
>> When I ping to slave.domain2.com now it pings to 10.10.10.2
>> but postfix still want to deliver to the real IP. I also insert
>>
>> smtp_host_lookup = native,dns
>>
>> into  /kolab/etc/postfix/main.cf but this somehow does not change anything.
>> Using transport does also not work. Maybe a conflict with Kolabs homeserver
>> ldap settings?
>>
>> Any ideas?
> Ok, seems to work now, but only after one timeout.
> I use
> smtp      unix  -       -       n       -       -       smtp -o
> fallback_relay=10.10.10.2

This is a mistake !!!!
If your server is sending an "autging" mail
and the recipient server is unavailable, your server
will try 10.10.10.2 that should reject the email
and your sender will got a NDR.

>
> in master.cf
>
> now I get
>> connect to slave.domain2.com[4.3.2.1]: Connection timed out (port 25)
>> to=<info at maildomain3.com>, relay=10.10.10.2[10.10.10.2]:25, delay=30,
>> delays=0.03/0.01/30/0.06, dsn=2.0.0, status=sent (250 2.0.0 Ok:
>> queued as 1430A19F97C)
>
> and for some unknown reasons I get on the _slave_ for one of the mail domain
> names a
>
>> : to=<info at maildomain3.com>, relay=none, delay=0.01, delays=0.01/0/0/0,
>> dsn=5.4.6, status=bounced (mail for 10.10.10.2 loops back to myself)
>

Did you set a transport for domain3 ?
If slave share the same ldap data as the master,
maybe it will not understand why you setup a transport to itself.
You should define a transport per mailbox, not for all domain3
or customize your master.cf templates accordingly

> I have no problems with delivering mails to maildomain2.com on the slave.
> Maybe because maildomain2.com==domainname of the slave. But this could be
> solved in using the master as smarthost of the slave.
>
> While now everything seems to work stable, this was a little bit of
> voodoo. :-/ weekend!! :-)
>
> Tips & hints for a better or cleaner solution or a better understanding of
> this stuff are welcome!
>
> Bye
>
>  Thorsten
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From thorsten.schnebeck at gmx.net  Mon Jul 21 12:35:37 2008
From: thorsten.schnebeck at gmx.net (Thorsten Schnebeck)
Date: Mon, 21 Jul 2008 12:35:37 +0200
Subject: master/slave setup via VPN?
In-Reply-To: <71fe4e760807210245x12e193bdl4aa4ab9c13788d21@mail.gmail.com>
References: <200807182238.20202.thorsten.schnebeck@gmx.net>
	<200807201332.57983.thorsten.schnebeck@gmx.net>
	<71fe4e760807210245x12e193bdl4aa4ab9c13788d21@mail.gmail.com>
Message-ID: <200807211235.37892.thorsten.schnebeck@gmx.net>

On Monday 21 July 2008 11:45:39 Alain Spineux wrote:
> On Sun, Jul 20, 2008 at 1:32 PM, Thorsten Schnebeck
> <thorsten.schnebeck at gmx.net> wrote:
> > Am Samstag 19 Juli 2008 schrieb Alain Spineux:
> >> On Fri, Jul 18, 2008 at 10:38 PM, Thorsten Schnebeck
> > When I ping to slave.domain2.com now it pings to 10.10.10.2
> > but postfix still want to deliver to the real IP. I also insert
> >
> > smtp_host_lookup = native,dns
>
> Hmm, yes maybe, I didn't know about that
> but "disable_dns_lookups" looks more appropriate.
> I was thinking "disable_dns_lookups" was the default, happy
> to learn something new

/kolab/sbin/postconf -d | grep _dns_
disable_dns_lookups = no

I changed it to "yes" and now this works without timeout and forced 
relaying :-)

Speaking about default config:
I would also vote for a config of
delay_warning_time = 3h
in main.cf.template. Some users wonder when the get a "could not deliver" 
message after 5 days. So an early warning that there is a problem is here 
necessary.

now to the slave bouncing problem...

Thanks

  Thorsten


From thorsten.schnebeck at gmx.net  Mon Jul 21 13:19:39 2008
From: thorsten.schnebeck at gmx.net (Thorsten Schnebeck)
Date: Mon, 21 Jul 2008 13:19:39 +0200
Subject: master/slave setup via VPN?
In-Reply-To: <200807211235.37892.thorsten.schnebeck@gmx.net>
References: <200807182238.20202.thorsten.schnebeck@gmx.net>
	<71fe4e760807210245x12e193bdl4aa4ab9c13788d21@mail.gmail.com>
	<200807211235.37892.thorsten.schnebeck@gmx.net>
Message-ID: <200807211319.39220.thorsten.schnebeck@gmx.net>

Am Monday 21 July 2008 um 12:35:37 schrieb Thorsten Schnebeck:
> On Monday 21 July 2008 11:45:39 Alain Spineux wrote:
> > On Sun, Jul 20, 2008 at 1:32 PM, Thorsten Schnebeck
> >
> > <thorsten.schnebeck at gmx.net> wrote:
> > > Am Samstag 19 Juli 2008 schrieb Alain Spineux:
> > >> On Fri, Jul 18, 2008 at 10:38 PM, Thorsten Schnebeck
> > >
> > > When I ping to slave.domain2.com now it pings to 10.10.10.2
> > > but postfix still want to deliver to the real IP. I also insert
> > >
> > > smtp_host_lookup = native,dns
> >
> > Hmm, yes maybe, I didn't know about that
> > but "disable_dns_lookups" looks more appropriate.
> > I was thinking "disable_dns_lookups" was the default, happy
> > to learn something new
>
> /kolab/sbin/postconf -d | grep _dns_
> disable_dns_lookups = no
>
> I changed it to "yes" and now this works without timeout and forced
> relaying :-)

BUT...
now some mail servers do not like my server anymore:
status=deferred (connect to gmx.net[213.165.65.50]: Connection timed out)

If I change this back to "no" everything is fine
relay=mx0.gmx.de[213.165.64.100]:25, delay=1087, delays=1087/0.05/0.13/0.17, 
dsn=2.6.0, status=sent (250 2.6.0 Message accepted {mx007})

So, while this option helps for my local vpn setup, is a showstopper for my 
global system.

Bye

  Thorsten


From thorsten.schnebeck at gmx.net  Mon Jul 21 17:14:15 2008
From: thorsten.schnebeck at gmx.net (Thorsten Schnebeck)
Date: Mon, 21 Jul 2008 17:14:15 +0200
Subject: master/slave setup via VPN?
In-Reply-To: <200807211319.39220.thorsten.schnebeck@gmx.net>
References: <200807182238.20202.thorsten.schnebeck@gmx.net>
	<200807211235.37892.thorsten.schnebeck@gmx.net>
	<200807211319.39220.thorsten.schnebeck@gmx.net>
Message-ID: <200807211714.15159.thorsten.schnebeck@gmx.net>

Am Monday 21 July 2008 um 13:19:39 schrieb Thorsten Schnebeck:
> Am Monday 21 July 2008 um 12:35:37 schrieb Thorsten Schnebeck:
> BUT...
> now some mail servers do not like my server anymore:
> status=deferred (connect to gmx.net[213.165.65.50]: Connection timed out)
>
> If I change this back to "no" everything is fine
> relay=mx0.gmx.de[213.165.64.100]:25, delay=1087,
> delays=1087/0.05/0.13/0.17, dsn=2.6.0, status=sent (250 2.6.0 Message
> accepted {mx007})

> So, while this option helps for my local vpn setup, is a showstopper for my
> global system.

master to slave transport is explicit controlled by
/kolab/etc/postfix/ldaptransport.cf
This generates an smtp:[slave-domainname] transport for every multi domain 
user with home server != master server. 

But when I know this is a master-slave connection nobody forbids me to disable 
DNS lookups in master.cf as special service:

ms_smtp    unix  -       -    n    -    -   smtp -o disable_dns_lookups=yes

and in ldaptransport.cf
--  result_filter = smtp:[%s]
++  result_filter = ms_smtp:[%s]

Looks like this works. Objections from anyone?

Bye

  Thorsten



From aspineux at gmail.com  Mon Jul 21 23:35:55 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 21 Jul 2008 23:35:55 +0200
Subject: master/slave setup via VPN?
In-Reply-To: <200807211319.39220.thorsten.schnebeck@gmx.net>
References: <200807182238.20202.thorsten.schnebeck@gmx.net>
	<71fe4e760807210245x12e193bdl4aa4ab9c13788d21@mail.gmail.com>
	<200807211235.37892.thorsten.schnebeck@gmx.net>
	<200807211319.39220.thorsten.schnebeck@gmx.net>
Message-ID: <71fe4e760807211435h5469a8e2u4481bdfe43383141@mail.gmail.com>

On Mon, Jul 21, 2008 at 1:19 PM, Thorsten Schnebeck
<thorsten.schnebeck at gmx.net> wrote:
> Am Monday 21 July 2008 um 12:35:37 schrieb Thorsten Schnebeck:
>> On Monday 21 July 2008 11:45:39 Alain Spineux wrote:
>> > On Sun, Jul 20, 2008 at 1:32 PM, Thorsten Schnebeck
>> >
>> > <thorsten.schnebeck at gmx.net> wrote:
>> > > Am Samstag 19 Juli 2008 schrieb Alain Spineux:
>> > >> On Fri, Jul 18, 2008 at 10:38 PM, Thorsten Schnebeck
>> > >
>> > > When I ping to slave.domain2.com now it pings to 10.10.10.2
>> > > but postfix still want to deliver to the real IP. I also insert
>> > >
>> > > smtp_host_lookup = native,dns
>> >
>> > Hmm, yes maybe, I didn't know about that
>> > but "disable_dns_lookups" looks more appropriate.
>> > I was thinking "disable_dns_lookups" was the default, happy
>> > to learn something new
>>
>> /kolab/sbin/postconf -d | grep _dns_
>> disable_dns_lookups = no
>>
>> I changed it to "yes" and now this works without timeout and forced
>> relaying :-)
>
> BUT...
> now some mail servers do not like my server anymore:
> status=deferred (connect to gmx.net[213.165.65.50]: Connection timed out)

from http://www.postfix.org/faq.html

. When you disable DNS lookups, you must specify the relayhost  as
either a numeric IP address, or as a hostname that resolves to one .
or more IP addresses (with DNS lookup disabled, Postfix does no MX
lookup).

we are on the wrong way, you need MX lookup, IP lookup only is not enough
Then remove the disable_dns_lookups !

The entry in /etc/hosts alone should be enough !

>
> If I change this back to "no" everything is fine
> relay=mx0.gmx.de[213.165.64.100]:25, delay=1087, delays=1087/0.05/0.13/0.17,
> dsn=2.6.0, status=sent (250 2.6.0 Message accepted {mx007})
>
> So, while this option helps for my local vpn setup, is a showstopper for my
> global system.
>
> Bye
>
>  Thorsten
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From marko at mechtron.com.au  Tue Jul 22 02:28:01 2008
From: marko at mechtron.com.au (Mark Berndt)
Date: Tue, 22 Jul 2008 10:28:01 +1000
Subject: Tar won't build on debian lenny
Message-ID: <200807221028.02101.marko@mechtron.com.au>

I'm install kolab 2.2
Running install-kolab.sh on debian lenny x86 fails during the tar build 
process.  

Its a fresh basic install of debian lenny with no desktop and exim removed, 
Locale is en_AU, bison, flex, gcc, make, libtool, automake, autoconf is 
installed.

MD5's are correct.

2.2rc3 also fails in the same way.  

2.2 installs ok on my laptop running debian etch with gnome installed.

Any idea what packages I'm missing?

Thanks,

Marko  

The output is: 


        then mv -f ".deps/utf8.Tpo" ".deps/utf8.Po"; else 
rm -f ".deps/utf8.Tpo"; exit 1; fi
utf8.c:26:1: warning: "iconv_t" redefined
In file included from ../lib/system.h:21,
                 from utf8.c:19:
../config.h:1084:1: warning: this is the location of the previous definition
/usr/bin/gcc -std=gnu99  -g -O2   -o tar  buffer.o compare.o create.o delete.o 
extract.o xheader.o incremen.o list.o mis
c.o names.o sparse.o system.o tar.o transform.o update.o 
utf8.o ../lib/libtar.a   -lrt 
../lib/libtar.a(argp-fmtstream.o): In function `argp_fmtstream_putc':
/tmp/openpkg-20071227/tar-1.19/lib/argp-fmtstream.h:233: multiple definition 
of `argp_fmtstream_putc'
tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp-fmtstream.h:233: first 
defined here
../lib/libtar.a(argp-fmtstream.o): In function `argp_fmtstream_point':
/tmp/openpkg-20071227/tar-1.19/lib/argp-fmtstream.h:279: multiple definition 
of `argp_fmtstream_point'
tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp-fmtstream.h:279: first 
defined here
../lib/libtar.a(argp-fmtstream.o): In function `argp_fmtstream_set_wmargin':
/tmp/openpkg-20071227/tar-1.19/lib/argp-fmtstream.h:267: multiple definition 
of `argp_fmtstream_set_wmargin'
tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp-fmtstream.h:267: first 
defined here

(snip)

tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp.h:606: first defined here
../lib/libtar.a(argp-eexst.o): In function `_option_is_short':
/tmp/openpkg-20071227/tar-1.19/lib/argp.h:594: multiple definition of 
`_option_is_short'
tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp.h:594: first defined here
../lib/libtar.a(argp-eexst.o): In function `argp_usage':
/tmp/openpkg-20071227/tar-1.19/lib/argp.h:588: multiple definition of 
`argp_usage'
tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp.h:588: first defined here
collect2: ld returned 1 exit status
make[2]: *** [tar] Error 1
make[2]: Leaving directory `/tmp/openpkg-20071227/tar-1.19/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/openpkg-20071227/tar-1.19'
make: *** [all] Error 2
+ exit 2
+ exit 2
./openpkg.boot:ERROR: script returned non-null value


From thorsten.schnebeck at gmx.net  Tue Jul 22 08:34:00 2008
From: thorsten.schnebeck at gmx.net (Thorsten Schnebeck)
Date: Tue, 22 Jul 2008 08:34:00 +0200
Subject: master/slave setup via VPN?
In-Reply-To: <71fe4e760807211435h5469a8e2u4481bdfe43383141@mail.gmail.com>
References: <200807182238.20202.thorsten.schnebeck@gmx.net>
	<200807211319.39220.thorsten.schnebeck@gmx.net>
	<71fe4e760807211435h5469a8e2u4481bdfe43383141@mail.gmail.com>
Message-ID: <200807220834.00311.thorsten.schnebeck@gmx.net>

On Monday 21 July 2008 23:35:55 Alain Spineux wrote:
> . When you disable DNS lookups, you must specify the relayhost  as
> either a numeric IP address, or as a hostname that resolves to one .
> or more IP addresses (with DNS lookup disabled, Postfix does no MX
> lookup).
>
> we are on the wrong way, you need MX lookup, IP lookup only is not enough
> Then remove the disable_dns_lookups !
>
> The entry in /etc/hosts alone should be enough !

Have you notice the other mail in this thread about using a separate 
master-slave smtp-send-service to solve this issue? What do you think about 
this?

Thanks for your support!

  Thorsten


From johannes_graumann at web.de  Tue Jul 22 09:07:42 2008
From: johannes_graumann at web.de (Johannes Graumann)
Date: Tue, 22 Jul 2008 09:07:42 +0200
Subject: Tar won't build on debian lenny
References: <200807221028.02101.marko@mechtron.com.au>
Message-ID: <g640vs$qb2$1@ger.gmane.org>

I had the same issue a while ago ... you have to downgrade the gcc ...

Joh

Mark Berndt wrote:

> I'm install kolab 2.2
> Running install-kolab.sh on debian lenny x86 fails during the tar build
> process.
> 
> Its a fresh basic install of debian lenny with no desktop and exim
> removed, Locale is en_AU, bison, flex, gcc, make, libtool, automake,
> autoconf is installed.
> 
> MD5's are correct.
> 
> 2.2rc3 also fails in the same way.
> 
> 2.2 installs ok on my laptop running debian etch with gnome installed.
> 
> Any idea what packages I'm missing?
> 
> Thanks,
> 
> Marko
> 
> The output is:
> 
> 
>         then mv -f ".deps/utf8.Tpo" ".deps/utf8.Po"; else
> rm -f ".deps/utf8.Tpo"; exit 1; fi
> utf8.c:26:1: warning: "iconv_t" redefined
> In file included from ../lib/system.h:21,
>                  from utf8.c:19:
> ../config.h:1084:1: warning: this is the location of the previous
> definition
> /usr/bin/gcc -std=gnu99  -g -O2   -o tar  buffer.o compare.o create.o
> delete.o extract.o xheader.o incremen.o list.o mis
> c.o names.o sparse.o system.o tar.o transform.o update.o
> utf8.o ../lib/libtar.a   -lrt
> ../lib/libtar.a(argp-fmtstream.o): In function `argp_fmtstream_putc':
> /tmp/openpkg-20071227/tar-1.19/lib/argp-fmtstream.h:233: multiple
> definition of `argp_fmtstream_putc'
> tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp-fmtstream.h:233:
> first defined here
> ../lib/libtar.a(argp-fmtstream.o): In function `argp_fmtstream_point':
> /tmp/openpkg-20071227/tar-1.19/lib/argp-fmtstream.h:279: multiple
> definition of `argp_fmtstream_point'
> tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp-fmtstream.h:279:
> first defined here
> ../lib/libtar.a(argp-fmtstream.o): In function
> `argp_fmtstream_set_wmargin':
> /tmp/openpkg-20071227/tar-1.19/lib/argp-fmtstream.h:267: multiple
> definition of `argp_fmtstream_set_wmargin'
> tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp-fmtstream.h:267:
> first defined here
> 
> (snip)
> 
> tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp.h:606: first defined
> here ../lib/libtar.a(argp-eexst.o): In function `_option_is_short':
> /tmp/openpkg-20071227/tar-1.19/lib/argp.h:594: multiple definition of
> `_option_is_short'
> tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp.h:594: first defined
> here ../lib/libtar.a(argp-eexst.o): In function `argp_usage':
> /tmp/openpkg-20071227/tar-1.19/lib/argp.h:588: multiple definition of
> `argp_usage'
> tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp.h:588: first defined
> here collect2: ld returned 1 exit status
> make[2]: *** [tar] Error 1
> make[2]: Leaving directory `/tmp/openpkg-20071227/tar-1.19/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/tmp/openpkg-20071227/tar-1.19'
> make: *** [all] Error 2
> + exit 2
> + exit 2
> ./openpkg.boot:ERROR: script returned non-null value



From thorsten.schnebeck at gmx.net  Tue Jul 22 09:11:18 2008
From: thorsten.schnebeck at gmx.net (Thorsten Schnebeck)
Date: Tue, 22 Jul 2008 09:11:18 +0200
Subject: master/slave setup via VPN?
In-Reply-To: <71fe4e760807210254s524ca390k13254032f767e611@mail.gmail.com>
References: <200807182238.20202.thorsten.schnebeck@gmx.net>
	<200807202057.32983.thorsten.schnebeck@gmx.net>
	<71fe4e760807210254s524ca390k13254032f767e611@mail.gmail.com>
Message-ID: <200807220911.18949.thorsten.schnebeck@gmx.net>

Hi,

(ok, just to remember in this part of the thread we are looking at the 
slave :-)

On Monday 21 July 2008 11:54:57 Alain Spineux wrote:
> On Sun, Jul 20, 2008 at 8:57 PM, Thorsten Schnebeck
> > and for some unknown reasons I get on the _slave_ for one of the mail
> > domain names a
> >
> >> : to=<info at maildomain3.com>, relay=none, delay=0.01, delays=0.01/0/0/0,
> >> dsn=5.4.6, status=bounced (mail for 10.10.10.2 loops back to myself)
>
> Did you set a transport for domain3 ?
> If slave share the same ldap data as the master,
> maybe it will not understand why you setup a transport to itself.
Yes, this is standard kolab 2.2 master/slave setup and the ldap of the slave 
is a replica of the master. 

> You should define a transport per mailbox, not for all domain3
> or customize your master.cf templates accordingly
if I use
/kolab/sbin/postmap -q "info at domain3.com" 
ldap:/kolab/etc/postfix/ldaptransport.cf
I get an empty string as "info at domain3.com" has its homeserver on the slave.
This should be ok (?) 

I do not understand what happens in this case when I use master as relaishost 
of the slave and if this setup is "bad". I know that it works as every 
incoming mail gets delivered into the right mailbox but what happens when 
there is an error in the delivering chain. Can this result in a bounce/loop?

I mean " (mail for 10.10.10.2 loops back to myself)" sounds again as this has 
something to do with my special VPN setup and a standard kolab master/slave 
setup working in "real" networks does not have this problem.

Bye

  Thorsten


From liutauras.adomaitis at gmail.com  Tue Jul 22 11:43:21 2008
From: liutauras.adomaitis at gmail.com (Liutauras Adomaitis)
Date: Tue, 22 Jul 2008 12:43:21 +0300
Subject: Kolab vs Scalix
In-Reply-To: <87mykhly9g.fsf@home.pardus.de>
References: <c1ec9ac0807152353o22d3da98i6a09920b8a5774e6@mail.gmail.com>
	<87mykhly9g.fsf@home.pardus.de>
Message-ID: <c1ec9ac0807220243p40d33d7r16740d726f8fdc91@mail.gmail.com>

Thanks a lot for your oponions. We probably stick to Kolab, because we tried
bynari insight connector now and it worked quite well.

Liutauras
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20080722/4cbc3df1/attachment.html

From luca at furna.com  Tue Jul 22 12:03:22 2008
From: luca at furna.com (Luca Fornasari)
Date: Tue, 22 Jul 2008 18:03:22 +0800
Subject: Kolab 2.2.0 Debian packages for etch and mailing list
Message-ID: <4885B06A.30105@furna.com>

I searched the kolab-user mailing list archive at marc.info for "Deb 
packages" and "Debian packages"; I found out that Ubuntu 8.04 has 
packages of Kolab 2.1.0 and that Mathieu Parent made some packages that 
are not available anymore at 
http://mathieu.parent.free.fr/debian/kolab/2.2~rc1+20080204
Daryl Caudill also mention a separate mailing list for Debian packages ...

Anyone has any information about that mailing list or a new URL for .deb 
packages of Kolab 2.2.0 for etch or lenny?

Thanks in adavance

-- 
Luca Fornasari
FURNA.COM


From marko at mechtron.com.au  Tue Jul 22 13:36:43 2008
From: marko at mechtron.com.au (Mark Berndt)
Date: Tue, 22 Jul 2008 21:36:43 +1000
Subject: Tar won't build on debian lenny
In-Reply-To: <g640vs$qb2$1@ger.gmane.org>
References: <200807221028.02101.marko@mechtron.com.au>
	<g640vs$qb2$1@ger.gmane.org>
Message-ID: <200807222136.43928.marko@mechtron.com.au>

Downgraded to gcc 4.2 and it works fine.

Thanks!


On Tue, 22 Jul 2008 05:07:42 pm you wrote:
> I had the same issue a while ago ... you have to downgrade the gcc ...
>
> Joh
>
> Mark Berndt wrote:
> > I'm install kolab 2.2
> > Running install-kolab.sh on debian lenny x86 fails during the tar build
> > process.
> >
> > Its a fresh basic install of debian lenny with no desktop and exim
> > removed, Locale is en_AU, bison, flex, gcc, make, libtool, automake,
> > autoconf is installed.
> >
> > MD5's are correct.
> >
> > 2.2rc3 also fails in the same way.
> >
> > 2.2 installs ok on my laptop running debian etch with gnome installed.
> >
> > Any idea what packages I'm missing?
> >
> > Thanks,
> >
> > Marko
> >
> > The output is:
> >
> >
> >         then mv -f ".deps/utf8.Tpo" ".deps/utf8.Po"; else
> > rm -f ".deps/utf8.Tpo"; exit 1; fi
> > utf8.c:26:1: warning: "iconv_t" redefined
> > In file included from ../lib/system.h:21,
> >                  from utf8.c:19:
> > ../config.h:1084:1: warning: this is the location of the previous
> > definition
> > /usr/bin/gcc -std=gnu99  -g -O2   -o tar  buffer.o compare.o create.o
> > delete.o extract.o xheader.o incremen.o list.o mis
> > c.o names.o sparse.o system.o tar.o transform.o update.o
> > utf8.o ../lib/libtar.a   -lrt
> > ../lib/libtar.a(argp-fmtstream.o): In function `argp_fmtstream_putc':
> > /tmp/openpkg-20071227/tar-1.19/lib/argp-fmtstream.h:233: multiple
> > definition of `argp_fmtstream_putc'
> > tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp-fmtstream.h:233:
> > first defined here
> > ../lib/libtar.a(argp-fmtstream.o): In function `argp_fmtstream_point':
> > /tmp/openpkg-20071227/tar-1.19/lib/argp-fmtstream.h:279: multiple
> > definition of `argp_fmtstream_point'
> > tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp-fmtstream.h:279:
> > first defined here
> > ../lib/libtar.a(argp-fmtstream.o): In function
> > `argp_fmtstream_set_wmargin':
> > /tmp/openpkg-20071227/tar-1.19/lib/argp-fmtstream.h:267: multiple
> > definition of `argp_fmtstream_set_wmargin'
> > tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp-fmtstream.h:267:
> > first defined here
> >
> > (snip)
> >
> > tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp.h:606: first defined
> > here ../lib/libtar.a(argp-eexst.o): In function `_option_is_short':
> > /tmp/openpkg-20071227/tar-1.19/lib/argp.h:594: multiple definition of
> > `_option_is_short'
> > tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp.h:594: first defined
> > here ../lib/libtar.a(argp-eexst.o): In function `argp_usage':
> > /tmp/openpkg-20071227/tar-1.19/lib/argp.h:588: multiple definition of
> > `argp_usage'
> > tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp.h:588: first defined
> > here collect2: ld returned 1 exit status
> > make[2]: *** [tar] Error 1
> > make[2]: Leaving directory `/tmp/openpkg-20071227/tar-1.19/src'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/tmp/openpkg-20071227/tar-1.19'
> > make: *** [all] Error 2
> > + exit 2
> > + exit 2
> > ./openpkg.boot:ERROR: script returned non-null value



From vincent at acheson.uk.com  Tue Jul 22 15:21:54 2008
From: vincent at acheson.uk.com (vincent@acheson.uk.com)
Date: Tue, 22 Jul 2008 14:21:54 +0100
Subject: Kolab 2.2 fails to build on debian etch - file permissions problem?
In-Reply-To: <200807222136.43928.marko@mechtron.com.au>
Message-ID: <001501c8ebfd$e9a977f0$1600a8c0@horgabost.pri>

Hi

Am trying to build kolab 2.2 on debian etch with no success. Problem may be
my own ignorance, but I would be very grateful for guidance.

I have followed advice on the wiki - esp:
http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_Compiling

I'm using a minimal install on VMWare, and debian packages from one of the
kolab mirrors

build-essential is installed, as are Bison, and Flex,
I did apt-get install gcc, make, libtool, automake and autoconf just in case
some of those wer not part of build-essential.

Did mkdir kolab, then chmod 777 /kolab (tho the install script changes
ownership back to kolab when it runs)

When I run sh install-kolab.sh  2>&1 | tee /root/kolab-install.log

I get the following output:
Changing to temporary working directory
/tmp/install-kolab.12798.18854.18988.5010 ...

Kolab installation tag (TAG):       kolab
Kolab installation prefix (PREFIX): /kolab
Kolab version (KOLAB_VERSION):      2.2.0
Kolab user name (USER):             root
Kolab user base UID (KID):          19414
Kolab restricted UID (KID):         19415
Kolab non-priviledged UID (KID):    19416
Exclude following Kolab packages:

Received no instructions. Trying to determine required action...
Found a binary OpenPKG package. This will be installed now.
OpenPKG CURRENT Binary Bootstrap Package, version 20071227
Built for prefix /kolab on target platform ix86-debian4.0
++ hooking OpenPKG instance into system environment
++ fixating OpenPKG instance root directory "/kolab"
++ extracting OpenPKG binary distribution
++ installing OpenPKG binary distribution
./openpkg-20071227-20071227.ix86-debian4.0-kolab.sh: line 903:
./openpkg.bzip2: No such file or directory
++ fixating OpenPKG instance filesystem hierarchy
./openpkg-20071227-20071227.ix86-debian4.0-kolab.sh: line 915:
/kolab/bin/openpkg: No such file or directory
++ post-processing OpenPKG bootstrap installation
./openpkg-20071227-20071227.ix86-debian4.0-kolab.sh: line 954:
/kolab/lib/openpkg/rpmdb: No such file or directory
cat: /kolab/etc/openpkg/platform: No such file or directory
./openpkg-20071227-20071227.ix86-debian4.0-kolab.sh: line 1051:
/kolab/bin/openpkg: No such file or directory
./openpkg-20071227-20071227.ix86-debian4.0-kolab.sh: line 1052:
/kolab/lib/openpkg/rpmtool: No such file or directory
./openpkg-20071227-20071227.ix86-debian4.0-kolab.sh: line 1096:
/kolab/lib/openpkg/rpmtool: No such file or directory
install-kolab.sh: line 294: /kolab/bin/openpkg: No such file or directory
----------- SETUP COMPLETED -----------

 Now running:

   /kolab/bin/openpkg build -kKBuZ -r
"/tmp/install-kolab.12798.18854.18988.5010" -p "-kolab" -D
openldap::with_pth=no -D sasl::with_ldap -D sasl::with_login -D
sasl::with_ntlm -D postfix::with_sasl -D postfix::with_ssl -D
postfix::with_ldap -D imapd::with_kolab_nocaps
            -Dkolabd::kolab_version=2.2.0
            -Dkolab-webadmin::kolab_version=2.2.0
          openpkg-tools openldap postfix kolabd kolab-filter kolab-freebusy
kolab-webadmin fbview-kronolith horde-kolab-client | sh

---------------------------------------
install-kolab.sh: line 312: /kolab/bin/openpkg: No such file or directory


Thanks

Vincent


From grenzlaeufer at gmx.net  Wed Jul 23 11:15:04 2008
From: grenzlaeufer at gmx.net (Volker Stoppe)
Date: Wed, 23 Jul 2008 11:15:04 +0200
Subject: Shared Folders in Kolab 2.2
Message-ID: <200807231115.05346.grenzlaeufer@gmx.net>

Hallo folks!

Big thanks for the new release 2.2 of the Kolab-server! Actually I am setting 
up a Demo system an trying to sync between Horde, Outlook and Thunderbird.

I noticed a strange problem when creating a shared folder. 
? Creating shared-folder in admin-interface seems ok.
? shared-folder doesn't appear in filesystem.
? mailbox isn't created, I checked it in cyradm with "lm"

Theoretical question:
Situation: I grant in horde access for the user_a calender for user_b.
Should user_b see the imap-folder in Thunderbird?
I thought yes, but I don?t see other folders.

The ACLs are these:
localhost> lam user/usera/Kontakte at domain.com
usera at domain.com lrswikxtecda
userb at domain.com lrswikxtecd

Maybe someone has the same problems and can help.

Greetinx

Volker


From thomas at intevation.de  Wed Jul 23 14:10:36 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Wed, 23 Jul 2008 14:10:36 +0200
Subject: Shared Folders in Kolab 2.2
In-Reply-To: <200807231115.05346.grenzlaeufer@gmx.net>
References: <200807231115.05346.grenzlaeufer@gmx.net>
Message-ID: <20080723121036.GB9252.thomas@intevation.de>

* Volker Stoppe <grenzlaeufer at gmx.net> [20080723 11:15]:
> Big thanks for the new release 2.2 of the Kolab-server! Actually I am setting 
> up a Demo system an trying to sync between Horde, Outlook and Thunderbird.
> 
> I noticed a strange problem when creating a shared folder. 
> ? Creating shared-folder in admin-interface seems ok.
> ? shared-folder doesn't appear in filesystem.
> ? mailbox isn't created, I checked it in cyradm with "lm"

Try stopping and starting kolabd:
/kolab/bin/openpkg rc kolabd stop
/kolab/bin/openpkg rc kolabd start

If this does not help, try stopping kolabd again, add "debug : 1" to
/kolab/etc/kolab/kolab.conf and manually run /kolab/sbin/kolabd and
watch the messages when creating a shared folder.

> Theoretical question:
> Situation: I grant in horde access for the user_a calender for user_b.
> Should user_b see the imap-folder in Thunderbird?
> I thought yes, but I don??t see other folders.

I think this is a Thunderbird problem. Can you see it with Outlook
and one of the Kolab connectors?

Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From vincent at acheson.uk.com  Wed Jul 23 19:53:50 2008
From: vincent at acheson.uk.com (vincent@acheson.uk.com)
Date: Wed, 23 Jul 2008 18:53:50 +0100
Subject: Kolab 2.2 fails to build on debian etch - file permissions
	problem? - SOLVED
In-Reply-To: <001501c8ebfd$e9a977f0$1600a8c0@horgabost.pri>
Message-ID: <001001c8eced$182150e0$1600a8c0@horgabost.pri>

Sorted - MD5 problem - openpkg*.sh failed md5 if downloaded onto windows
using Free Downoald Manager and then copied to debian machine using WinSCP.
If downloaded direct using wget, all fine.

-----Original Message-----
From: kolab-users-bounces at kolab.org
[mailto:kolab-users-bounces at kolab.org]On Behalf Of
vincent at acheson.uk.com
Sent: 22 July 2008 14:22
To: kolab-users at kolab.org
Subject: Kolab 2.2 fails to build on debian etch - file permissions
problem?


Hi

Am trying to build kolab 2.2 on debian etch with no success. Problem may be
my own ignorance, but I would be very grateful for guidance.

I have followed advice on the wiki - esp:
http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_Compiling

I'm using a minimal install on VMWare, and debian packages from one of the
kolab mirrors

build-essential is installed, as are Bison, and Flex,
I did apt-get install gcc, make, libtool, automake and autoconf just in case
some of those wer not part of build-essential.

Did mkdir kolab, then chmod 777 /kolab (tho the install script changes
ownership back to kolab when it runs)

When I run sh install-kolab.sh  2>&1 | tee /root/kolab-install.log

I get the following output:
Changing to temporary working directory
/tmp/install-kolab.12798.18854.18988.5010 ...

Kolab installation tag (TAG):       kolab
Kolab installation prefix (PREFIX): /kolab
Kolab version (KOLAB_VERSION):      2.2.0
Kolab user name (USER):             root
Kolab user base UID (KID):          19414
Kolab restricted UID (KID):         19415
Kolab non-priviledged UID (KID):    19416
Exclude following Kolab packages:

Received no instructions. Trying to determine required action...
Found a binary OpenPKG package. This will be installed now.
OpenPKG CURRENT Binary Bootstrap Package, version 20071227
Built for prefix /kolab on target platform ix86-debian4.0
++ hooking OpenPKG instance into system environment
++ fixating OpenPKG instance root directory "/kolab"
++ extracting OpenPKG binary distribution
++ installing OpenPKG binary distribution
./openpkg-20071227-20071227.ix86-debian4.0-kolab.sh: line 903:
./openpkg.bzip2: No such file or directory
++ fixating OpenPKG instance filesystem hierarchy
./openpkg-20071227-20071227.ix86-debian4.0-kolab.sh: line 915:
/kolab/bin/openpkg: No such file or directory
++ post-processing OpenPKG bootstrap installation
./openpkg-20071227-20071227.ix86-debian4.0-kolab.sh: line 954:
/kolab/lib/openpkg/rpmdb: No such file or directory
cat: /kolab/etc/openpkg/platform: No such file or directory
./openpkg-20071227-20071227.ix86-debian4.0-kolab.sh: line 1051:
/kolab/bin/openpkg: No such file or directory
./openpkg-20071227-20071227.ix86-debian4.0-kolab.sh: line 1052:
/kolab/lib/openpkg/rpmtool: No such file or directory
./openpkg-20071227-20071227.ix86-debian4.0-kolab.sh: line 1096:
/kolab/lib/openpkg/rpmtool: No such file or directory
install-kolab.sh: line 294: /kolab/bin/openpkg: No such file or directory
----------- SETUP COMPLETED -----------

 Now running:

   /kolab/bin/openpkg build -kKBuZ -r
"/tmp/install-kolab.12798.18854.18988.5010" -p "-kolab" -D
openldap::with_pth=no -D sasl::with_ldap -D sasl::with_login -D
sasl::with_ntlm -D postfix::with_sasl -D postfix::with_ssl -D
postfix::with_ldap -D imapd::with_kolab_nocaps
            -Dkolabd::kolab_version=2.2.0
            -Dkolab-webadmin::kolab_version=2.2.0
          openpkg-tools openldap postfix kolabd kolab-filter kolab-freebusy
kolab-webadmin fbview-kronolith horde-kolab-client | sh

---------------------------------------
install-kolab.sh: line 312: /kolab/bin/openpkg: No such file or directory


Thanks

Vincent

_______________________________________________
Kolab-users mailing list
Kolab-users at kolab.org
https://kolab.org/mailman/listinfo/kolab-users


From diegows at xtech.com.ar  Wed Jul 23 23:43:21 2008
From: diegows at xtech.com.ar (Diego Woitasen)
Date: Wed, 23 Jul 2008 18:43:21 -0300 (ART)
Subject: I don't see my folders
Message-ID: <36777.200.80.227.103.1216849401.squirrel@webmail.xtech.com.ar>

Hi,
 I have a fresh Kolab 2.2 installation. I'm trying with a user and when I
create folder, it's created ok but I don't see on Horde or via IMAP.

Example:

kolab:/kolab# /kolab/bin/cyradm -u diegows at domain.com.ar localhost
Password:
localhost> lm
INBOX (\HasNoChildren)
localhost> cm INBOX/testing1
localhost> lm
INBOX (\HasNoChildren)
localhost>

The folder exists on filesystem and I see it with "ctl_mboxlist -d".

Any ideas?



-- 
Diego Woitasen
XTECH - Soluciones Linux para empresas
(54) 011 5219-0678


From diegows at xtech.com.ar  Thu Jul 24 02:38:46 2008
From: diegows at xtech.com.ar (Diego Woitasen)
Date: Wed, 23 Jul 2008 21:38:46 -0300 (ART)
Subject: I don't see my folders
In-Reply-To: <36777.200.80.227.103.1216849401.squirrel@webmail.xtech.com.ar>
References: <36777.200.80.227.103.1216849401.squirrel@webmail.xtech.com.ar>
Message-ID: <38375.190.190.22.29.1216859926.squirrel@webmail.xtech.com.ar>


On Wed, July 23, 2008 6:43 pm, Diego Woitasen wrote:
> Hi,
>  I have a fresh Kolab 2.2 installation. I'm trying with a user and when I
> create folder, it's created ok but I don't see on Horde or via IMAP.
>
> Example:
>
> kolab:/kolab# /kolab/bin/cyradm -u diegows at domain.com.ar localhost
> Password:
> localhost> lm
> INBOX (\HasNoChildren)
> localhost> cm INBOX/testing1
> localhost> lm
> INBOX (\HasNoChildren)
> localhost>
>
> The folder exists on filesystem and I see it with "ctl_mboxlist -d".
>
> Any ideas?
>
>
>
> --
> Diego Woitasen
> XTECH - Soluciones Linux para empresas
> (54) 011 5219-0678
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>

I found something... The lookup permissions doesn't exists on new folder.
If a set it manually the folder appears...

Anybody with the same problem?

-- 
Diego Woitasen
XTECH - Soluciones Linux para empresas
(54) 011 5219-0678


From marko at mechtron.com.au  Thu Jul 24 16:00:34 2008
From: marko at mechtron.com.au (Mark Berndt)
Date: Fri, 25 Jul 2008 00:00:34 +1000
Subject: Kontact - note & calendar duplication
Message-ID: <200807250000.34221.marko@mechtron.com.au>

Kontact is showing multiple copies of the same note, however horde shows only 
one note.  Creating a note in horde or Kontact shows multiple notes in the 
Kontact display.

When I try to add a contact, the resource selection dialog shows 3 copies of 
kolab resources.  

email, journal and calendar all work fine.

When I delete the kolab accounts and recreate them with the kde groupware 
wizard, I get another copy of the notes and another entry in the resource 
selection dialog.

How can I get rid of these "left over" kolab resources?

I've had a good look through .kde/share/config, but can't find anything 
obviously wrong.

This is kolab server 2.2 and Kontact 1.29 on ubuntu 8.04

Thanks,

Marko


-- 
High performance computer, software and automation systems for demanding 
applications
 
Mechtron Systems
ABN: 52 149 788 293
329 Old Canobolas Road NASHDALE NSW 2800
mob 04-2860-1801 ph 02-6365-3568 fx 02-6365-3578 


From bernhard at intevation.de  Thu Jul 24 17:38:59 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 24 Jul 2008 17:38:59 +0200
Subject: A (currently theoretical) question concerning a book about the
	Kolab Server
In-Reply-To: <200807171437.34235.richard@radoeka.nl>
References: <87ej626kj6.fsf@home.pardus.de> <87ej5sbwef.fsf@home.pardus.de>
	<200807171437.34235.richard@radoeka.nl>
Message-ID: <200807241739.03861.bernhard@intevation.de>

On Thursday 17 July 2008 14:37, Richard Bos wrote:
> Op Thursday 17 July 2008 13:08:40 schreef Gunnar Wrobel:
> > > The other thing is that kolab is fully based on a directory (ldap)
> > > and imap storage instead of a database. ?But what is the big
> > > advantage of using a directory and imap storage instead of database?

More scalability.
Many Imap servers use specialisted storage that is more easy to backup
and thus actually is a specialist "database" with all advantages
over a general database management system.

> > > With IP everywhere a database is also very reachable from each
> > > location, even from remote locations and databases can be replicated
> > > as well.

Replication with databases is much more difficult, the idea of Kolab
is to avoid lock situations which make database replication very difficult.
Also there is better separations between data stores if a less complicated 
piece of software coverns it.

> > You only look at the administrators point of view here. Of course the
> > server admin can access a database. But what about the user? This is
> > the most crucial point about Kolab for me. Of course Kolab offers a
> > lot more than IMAP based storage of data. But to me this is the core
> > element. And it is not a technical reason why I'm excited about this
> > but a plain social one.
>
> I did not think about this aspect actually, but it is a very nice one
> indeed.

Yes, and it does not come from the IMAP usage, but from the idea of doing
the main groupware work on the client. A good client can have several 
storages, remote and local.

> However, if one is to use kolab in a company environment this fact (user in
> control of data) is of no importance as the user should not move his email
> :)

Even a company world, people have private appointments and might be a member 
of an non-profit association. My vision with Kontact and Kolab is that one 
day you have your personal client which saves your appointments on the three 
Kolab Servers: Company, Home, Association. Only the client has access to all 
three sources of information.
Corporations and large organisations will still like this as a happy employee
with their private life being nice is a much better employee.

> In that case why is the directory / imap storage better than other 
> solutions? Probably because it is scalably.  But isn't the same valid for
> groupware solutions based on a database (I wonder)?  Perhaps Bernard or
> Martin can elaborate on this?

(Martin does not read this list, AFAIK.)
A bit is on the old http://kroupware.kolab.org/faq/faq.html#Kolab%20Server0
Other things I would need to write down in a good way - a bit is in the design 
documents of course, but might be burried somewhere.

Bernhard

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20080724/3c198bb9/attachment.bin

From bernhard at intevation.de  Thu Jul 24 17:41:12 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 24 Jul 2008 17:41:12 +0200
Subject: kolab 2.2.0 migration success + horde mobile access problem
In-Reply-To: <871w1ulzze.fsf@home.pardus.de>
References: <200807132025.10108.thorsten.schnebeck@gmx.net>
	<871w1ulzze.fsf@home.pardus.de>
Message-ID: <200807241741.13168.bernhard@intevation.de>

On Wednesday 16 July 2008 15:28, Gunnar Wrobel wrote:
> I guess you might also be able to just install mimp from one of the
> horde release pacakges by unpacking it into
> /kolab/var/kolab/www/horde.
>
> It will probably be included in Kolab-Server-2.2.1. 

We should open an issue about this.

> The current Horde 
> version was a frist trial version and we weren't able to extend this
> to all the stuff Horde offers (e.g. dimp, mimp and SyncML). But 2.2.1
> should see some upgrades and enhancements in that sector. Horde is
> currently advancing a lot in the Kolab sector.

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20080724/bad37712/attachment.bin

From bernhard at intevation.de  Thu Jul 24 17:43:20 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 24 Jul 2008 17:43:20 +0200
Subject: Lost mailbox ACLs (rewrite)
In-Reply-To: <200807132239.54862.troy@carpenter.cx>
References: <200807132041.13770.troy@carpenter.cx>
	<20080713210942.70571trmw5do7p7a@mail.carpenter.cx>
	<200807132239.54862.troy@carpenter.cx>
Message-ID: <200807241743.21586.bernhard@intevation.de>

Troy,

the version of your Kolab Server would be very important to know.
There had been problems with skiplist databases before,
they should not happend with berkleydb or very new Server versions.
Also the kernel of your host operating system can be important.

Best,
Bernhard

On Monday 14 July 2008 04:39, Troy Carpenter wrote:
> > Any ideas?
>
> Ok, here's how I fixed it. ?I was still able to get the mailbox database
> via the command "/kolab/bin/ctl_mboxlist -d > mailboxlist.txt". ?Then I
> edited the file to correct the ACLs as necessary, then reloaded the file
> with the opposite command "/kolab/bin/ctl_mboxlist -u < mailboxlist.txt".
> ?I basically used the wiki page
> http://wiki.kolab.org/index.php/Backups_for_kolab2#IMAP_store_recovery_.28c
>yrus.29 as a guide.

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20080724/ce2e75dc/attachment.bin

From bernhard at intevation.de  Thu Jul 24 17:49:23 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 24 Jul 2008 17:49:23 +0200
Subject: Kolab vs Scalix
In-Reply-To: <200807161023.25757.michael@pasdziernik.net>
References: <c1ec9ac0807152353o22d3da98i6a09920b8a5774e6@mail.gmail.com>
	<200807161023.25757.michael@pasdziernik.net>
Message-ID: <200807241749.25353.bernhard@intevation.de>

On Wednesday 16 July 2008 10:23, Michael Pasdziernik wrote:
> The only problem with kolab in my opinion is the missing windows client for
> power users, that means users with thousands of messages and several
> GBytes mailbox size.
> Konsec does not allow more then 3GB of mailbox-size, 

Are you sure about the 3GB? If so, might it be 2GB because of the .pst limit?

> Toltec has some issus with synchronisation on big mailboxes.

Can you be more precise here, this would help Toltec to improve the product.
What kind of issues did you have?
Were they reproducable?

> Currently I am evaluating the new bynari insight connector and this looks
> very promising.

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From bernhard at intevation.de  Thu Jul 24 18:01:28 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 24 Jul 2008 18:01:28 +0200
Subject: Shared Folders in Kolab 2.2
In-Reply-To: <20080723121036.GB9252.thomas@intevation.de>
References: <200807231115.05346.grenzlaeufer@gmx.net>
	<20080723121036.GB9252.thomas@intevation.de>
Message-ID: <200807241801.34261.bernhard@intevation.de>

On Wednesday 23 July 2008 14:10, Thomas Arendsen Hein wrote:
> > Theoretical question:
> > Situation: I grant in horde access for the user_a calender for user_b.
> > Should user_b see the imap-folder in Thunderbird?
> > I thought yes, but I don??t see other folders.
>
> I think this is a Thunderbird problem.

I've heard there are settings that Thunderbird shows all folders not just the 
subscribed ones. So I would check deep into Thunderbird options, with the 
keywords subscription and namespace.

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20080724/cde8e4c9/attachment.bin

From troy at carpenter.cx  Thu Jul 24 18:06:34 2008
From: troy at carpenter.cx (Troy Carpenter)
Date: Thu, 24 Jul 2008 12:06:34 -0400
Subject: Lost mailbox ACLs (rewrite)
In-Reply-To: <200807241743.21586.bernhard@intevation.de>
References: <200807132041.13770.troy@carpenter.cx>
	<200807132239.54862.troy@carpenter.cx>
	<200807241743.21586.bernhard@intevation.de>
Message-ID: <200807241206.34977.troy@carpenter.cx>

On Thursday 24 July 2008 11:43:20 am Bernhard Reiter wrote:
> Troy,
>
> the version of your Kolab Server would be very important to know.
> There had been problems with skiplist databases before,
> they should not happend with berkleydb or very new Server versions.
> Also the kernel of your host operating system can be important.

No problem.  At the time, I was using 2.2-RC3 with some config differences 
from the distribution for Postfix and Horde.  My server is Ubuntu Hardy 64bit:

root at sol:~# uname -a
Linux sol 2.6.24-18-server #1 SMP Wed May 28 20:21:05 UTC 2008 x86_64

I can only give you the nebulous "something happened" which caused me to 
rebuild the mailbox files using  /kolab/bin/cyrreconstruct.  After that, I 
noticed that some mailboxes were not accessible by the end users. Using 
"/kolab/bin/cyradm -U manager localhost", I was able to change the ACLs on 
most of the mailboxes by adding the owner back to the list.  But on a handful 
of mailboxes, there were no ACLs listed at all.  For those even the manager 
account couldn't do anything.

So using "/kolab/bin/ctl_mboxlist -d > mailboxlist.txt", I edited the 
mailboxlist.txt file so that it had the right ACLs for the mailboxes missing 
them.  I reloaded the list and presto, everything was back to normal.

Hope that helps.

Troy

>On Monday 14 July 2008 04:39, Troy Carpenter wrote:
>> > Any ideas?
>>
>> Ok, here's how I fixed it.  I was still able to get the mailbox database
>> via the command "/kolab/bin/ctl_mboxlist -d > mailboxlist.txt".  Then I
>> edited the file to correct the ACLs as necessary, then reloaded the file
>> with the opposite command "/kolab/bin/ctl_mboxlist -u < mailboxlist.txt".
>>  I basically used the wiki page
>> http://wiki.kolab.org/index.php/Backups_for_kolab2#IMAP_store_recovery_.28c
>>yrus.29 as a guide.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20080724/8c0d319f/attachment.bin

From bernhard at intevation.de  Thu Jul 24 18:17:36 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 24 Jul 2008 18:17:36 +0200
Subject: I don't see my folders
In-Reply-To: <38375.190.190.22.29.1216859926.squirrel@webmail.xtech.com.ar>
References: <36777.200.80.227.103.1216849401.squirrel@webmail.xtech.com.ar>
	<38375.190.190.22.29.1216859926.squirrel@webmail.xtech.com.ar>
Message-ID: <200807241817.40975.bernhard@intevation.de>

Diego,

On Thursday 24 July 2008 02:38, Diego Woitasen wrote:
> On Wed, July 23, 2008 6:43 pm, Diego Woitasen wrote:
> >  I have a fresh Kolab 2.2 installation. I'm trying with a user and when I
> > create folder, it's created ok but I don't see on Horde or via IMAP.

are you sure you did not make any typos in the name of the server 
for the account? (On Slave servers, the permissions for INBOX are created 
differently.)

> > Example:
> >
> > kolab:/kolab# /kolab/bin/cyradm -u diegows at domain.com.ar localhost
> > Password:
> > localhost> lm
> > INBOX (\HasNoChildren)
> > localhost> cm INBOX/testing1
> > localhost> lm
> > INBOX (\HasNoChildren)
> > localhost>
> >
> > The folder exists on filesystem and I see it with "ctl_mboxlist -d".
> >
> > Any ideas?

The new folder might inherit the ACL from INBOX.
Check "lam *".

> I found something... The lookup permissions doesn't exists on new folder.
> If a set it manually the folder appears...
>
> Anybody with the same problem?

I've tried and "cm" gives me good folders.
Bernhard


-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20080724/40b2319e/attachment-0001.bin

From francesco at trimarchi.it  Thu Jul 24 21:08:17 2008
From: francesco at trimarchi.it (francesco@trimarchi.it)
Date: Thu, 24 Jul 2008 21:08:17 +0200
Subject: error compiling on centos 5.2
Message-ID: <98b19a63642745869f5685c0958fc395@plesk1.auroranetwork.it>

hello to everybody.

i'm trying to compile kolab on a centos 5.2 but I own the following error:

everybody can help me?

Francesco

........

++ cleaning up environment
+ /kolab/bin/perl-openpkg -d /kolab/RPM/SRC/perl-www/WWW-Mechanize-1.34.tar.gz -A --nolive configure build install
++ OpenPKG perl-openpkg 2.0.1 (03-Dec-2004)
++ determined RPM  program: /kolab/libexec/openpkg/rpm (4.2.1)
++ determined Perl program: /kolab/bin/perl (5.10.0)
++ step 2: configure
++ configuring module via ExtUtils::MakeMaker environment
Can't load '/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Crypt/SSLeay/SSLeay.so' for module Crypt::SSLeay: /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Crypt/SSLeay/SSLeay.so: cannot restore segment prot after reloc: Permission denied at /kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 203.
 at /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/Net/SSL.pm line 19
Compilation failed in require at /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/Net/SSL.pm line 19.
Compilation failed in require at /kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/Net/HTTPS.pm line 18.
Can't load '/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Net/SSLeay/SSLeay.so' for module Net::SSLeay: /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Net/SSLeay/SSLeay.so: cannot restore segment prot after reloc: Permission denied at /kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 203.
 at /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18
Compilation failed in require at /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18.
BEGIN failed--compilation aborted at /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18.
Compilation failed in require at /kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/Net/HTTPS.pm line 22.
Compilation failed in require at /kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/LWP/Protocol/https.pm line 46.
Compilation failed in require at (eval 11) line 3.

++ step 3: build
perl-openpkg:ERROR: neither "Build" nor "Makefile" found in working directory (No such file or directory)
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.31809 (%install)


RPM build errors:
    Bad exit status from /kolab/RPM/TMP/rpm-tmp.31809 (%install)




From martin.konold at erfrakon.de  Thu Jul 24 21:09:15 2008
From: martin.konold at erfrakon.de (Martin Konold)
Date: Thu, 24 Jul 2008 21:09:15 +0200
Subject: Kolab vs Scalix
In-Reply-To: <200807241749.25353.bernhard@intevation.de>
References: <c1ec9ac0807152353o22d3da98i6a09920b8a5774e6@mail.gmail.com>
	<200807161023.25757.michael@pasdziernik.net>
	<200807241749.25353.bernhard@intevation.de>
Message-ID: <200807242109.31411.martin.konold@erfrakon.de>

Am Thursday 24 July 2008 schrieb Bernhard Reiter:

Hi,

> On Wednesday 16 July 2008 10:23, Michael Pasdziernik wrote:
> > The only problem with kolab in my opinion is the missing windows client
> > for power users, that means users with thousands of messages and several
> > GBytes mailbox size.
> > Konsec does not allow more then 3GB of mailbox-size,
>
> Are you sure about the 3GB? If so, might it be 2GB because of the .pst
> limit?

The limit for the currently released stable KONSEC Konnector is indeed 2 GB 
per mailbox which is inherited from from an old Outlook limitation.

If you wan I can give you access to an alpha release of the upcoming KONSEC 
Konnector 2.0 (for OL2K3 and OL2K7) which will noch have this limitation. In 
addition 2.0 is tuned for more speed.

Regards,
-- martin konold

-- 
e r f r a k o n
Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
Sitz: Adolfstra?e 23, 70469 Stuttgart, Partnerschaftsregister Stuttgart PR 126
http://www.erfrakon.com/


From michael at pasdziernik.net  Fri Jul 25 11:17:14 2008
From: michael at pasdziernik.net (Michael Pasdziernik)
Date: Fri, 25 Jul 2008 11:17:14 +0200
Subject: Kolab vs Scalix
In-Reply-To: <200807241749.25353.bernhard@intevation.de>
References: <c1ec9ac0807152353o22d3da98i6a09920b8a5774e6@mail.gmail.com>
	<200807161023.25757.michael@pasdziernik.net>
	<200807241749.25353.bernhard@intevation.de>
Message-ID: <200807251117.14695.michael@pasdziernik.net>

On Thursday, 24. July 2008 17:49:23 Bernhard Reiter wrote:
> On Wednesday 16 July 2008 10:23, Michael Pasdziernik wrote:
> > The only problem with kolab in my opinion is the missing windows client
> > for power users, that means users with thousands of messages and several
> > GBytes mailbox size.
> > Konsec does not allow more then 3GB of mailbox-size,
>
> Are you sure about the 3GB? If so, might it be 2GB because of the .pst
> limit?

Yes. The limit is 2 GB. Sorry for the mistake.

> > Toltec has some issus with synchronisation on big mailboxes.
>
> Can you be more precise here, this would help Toltec to improve the
> product. What kind of issues did you have?
> Were they reproducable?

The issue we have is about mail duplicates. Currently I have not found a way 
to reproduce them. They occur on one very big mailbox that is used by a 
single user with a single workstation and on a mailbox with only about 1000 
messages but used by three users on different workstations and notebooks, 
sometimes concurrently and sometimes remote via vpn. 
I had to remove the duplicates several times with the duplicates plugin for
thunderbird. Last week I updated to the last toltec version and it seems that 
they are gone now. We have to wait some time to be sure.

> > Currently I am evaluating the new bynari insight connector and this looks
> > very promising.



From devgioiatech at gmail.com  Fri Jul 25 12:56:10 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Fri, 25 Jul 2008 12:56:10 +0200
Subject: error compiling on centos 5.2
In-Reply-To: <98b19a63642745869f5685c0958fc395@plesk1.auroranetwork.it>
References: <98b19a63642745869f5685c0958fc395@plesk1.auroranetwork.it>
Message-ID: <d53357b70807250356x233d2db0r8d01365250a43202@mail.gmail.com>

Did you check integrity of the downloaded files?
i kept similar error when a file was corrupted... check with md5sum -c
MD5SUMS

bye

2008/7/24 francesco at trimarchi.it <francesco at trimarchi.it>:

> hello to everybody.
>
> i'm trying to compile kolab on a centos 5.2 but I own the following error:
>
> everybody can help me?
>
> Francesco
>
> ........
>
> ++ cleaning up environment
> + /kolab/bin/perl-openpkg -d
> /kolab/RPM/SRC/perl-www/WWW-Mechanize-1.34.tar.gz -A --nolive configure
> build install
> ++ OpenPKG perl-openpkg 2.0.1 (03-Dec-2004)
> ++ determined RPM  program: /kolab/libexec/openpkg/rpm (4.2.1)
> ++ determined Perl program: /kolab/bin/perl (5.10.0)
> ++ step 2: configure
> ++ configuring module via ExtUtils::MakeMaker environment
> Can't load
> '/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Crypt/SSLeay/SSLeay.so'
> for module Crypt::SSLeay:
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Crypt/SSLeay/SSLeay.so:
> cannot restore segment prot after reloc: Permission denied at
> /kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 203.
>  at /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/Net/SSL.pm line 19
> Compilation failed in require at
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/Net/SSL.pm line 19.
> Compilation failed in require at
> /kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/Net/HTTPS.pm
> line 18.
> Can't load
> '/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Net/SSLeay/SSLeay.so'
> for module Net::SSLeay:
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Net/SSLeay/SSLeay.so:
> cannot restore segment prot after reloc: Permission denied at
> /kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 203.
>  at /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18
> Compilation failed in require at
> /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18.
> BEGIN failed--compilation aborted at
> /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18.
> Compilation failed in require at
> /kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/Net/HTTPS.pm
> line 22.
> Compilation failed in require at
> /kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/LWP/Protocol/
> https.pm line 46.
> Compilation failed in require at (eval 11) line 3.
>
> ++ step 3: build
> perl-openpkg:ERROR: neither "Build" nor "Makefile" found in working
> directory (No such file or directory)
> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.31809 (%install)
>
>
> RPM build errors:
>    Bad exit status from /kolab/RPM/TMP/rpm-tmp.31809 (%install)
>
>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
-------------- parte successiva --------------
Un allegato HTML ? stato rimosso...
URL: http://kolab.org/pipermail/kolab-users/attachments/20080725/c4445cdb/attachment.html

From bernhard at intevation.de  Fri Jul 25 14:18:15 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 25 Jul 2008 14:18:15 +0200
Subject: Kontact - note & calendar duplication
In-Reply-To: <200807250000.34221.marko@mechtron.com.au>
References: <200807250000.34221.marko@mechtron.com.au>
Message-ID: <200807251418.19420.bernhard@intevation.de>

On Thursday 24 July 2008 16:00, Mark Berndt wrote:
> Kontact is showing multiple copies of the same note, however horde shows
> only one note. ?Creating a note in horde or Kontact shows multiple notes in
> the Kontact display.
>
> When I try to add a contact, the resource selection dialog shows 3 copies
> of kolab resources.

Three copies of the folder under one top resource or several resources
which have the same contact folders?

> email, journal and calendar all work fine.
>
> When I delete the kolab accounts and recreate them with the kde groupware
> wizard, I get another copy of the notes and another entry in the resource
> selection dialog.

The wizard will not delete old accounts.
If you want to start over, try with a fresh .kde.
(Make sure KDE is down when you move or delete that directory.)

> How can I get rid of these "left over" kolab resources?

Try checking the resources for notes with "kcontrol".

> I've had a good look through .kde/share/config, but can't find anything
> obviously wrong.
>
> This is kolab server 2.2 and Kontact 1.29 on ubuntu 8.04

Which Kontact package precisely?
The best versions are those that say "enterprise35".

Bernhard


-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20080725/0e0ae51a/attachment.bin

From lbf at dragonrising.com  Sat Jul 26 11:40:21 2008
From: lbf at dragonrising.com (Alex)
Date: Sat, 26 Jul 2008 10:40:21 +0100
Subject: Feature request: reply-to setting for distribution lists
Message-ID: <488AF105.1040707@dragonrising.com>

Hello,

Firstly, to the developers - a big well done for the good work on Kolab
Server 2.2. I found this release a million times easier to install than
my efforts on 2.0 + horde, which I never got working properly.

Now for the request...

I use distribution lists as a way for my colleagues to chat amongst each
other, so it would be really useful if the reply-to field of the email
header could point my users reply back at the distribution list.

At the moment, I can get round this by manually setting the reply-to
field in Thunderbird mail client - but it's not convenient and many of
my users forget to do this, causing their reply to just go back to the
user that sent the mail.

If that makes sense.

Thanks again,

Alex

ps: SyncKolab - also excellent!


From marko at mechtron.com.au  Sun Jul 27 10:17:06 2008
From: marko at mechtron.com.au (Mark Berndt)
Date: Sun, 27 Jul 2008 18:17:06 +1000
Subject: Kontact - note & calendar duplication
In-Reply-To: <200807251418.19420.bernhard@intevation.de>
References: <200807250000.34221.marko@mechtron.com.au>
	<200807251418.19420.bernhard@intevation.de>
Message-ID: <200807271817.06926.marko@mechtron.com.au>

On Fri, 25 Jul 2008 10:18:15 pm you wrote:
> On Thursday 24 July 2008 16:00, Mark Berndt wrote:
> > Kontact is showing multiple copies of the same note, however horde shows
> > only one note. ?Creating a note in horde or Kontact shows multiple notes
> > in the Kontact display.
> >
> > When I try to add a contact, the resource selection dialog shows 3 copies
> > of kolab resources.
>
> Three copies of the folder under one top resource or several resources
> which have the same contact folders?



>
> > email, journal and calendar all work fine.
> >
> > When I delete the kolab accounts and recreate them with the kde groupware
> > wizard, I get another copy of the notes and another entry in the resource
> > selection dialog.
>
> The wizard will not delete old accounts.
> If you want to start over, try with a fresh .kde.
> (Make sure KDE is down when you move or delete that directory.)
>
> > How can I get rid of these "left over" kolab resources?
>
> Try checking the resources for notes with "kcontrol".

Thanks Bernard - the additional resources are listed in the kcontrol program.

Deleting the additional resources removes the duplicate copies.

It seems that removing the kolab imap connection from the email accounts setup 
does not remove the imap resource connections for notes and calendar.  


>
> > I've had a good look through .kde/share/config, but can't find anything
> > obviously wrong.
> >
> > This is kolab server 2.2 and Kontact 1.29 on ubuntu 8.04

Ubuntu is using 4:3.5.9-0ubuntu3(hardy)

>
> Which Kontact package precisely?
> The best versions are those that say "enterprise35".
>
> Bernhard



-- 
High performance computer, software and automation systems for demanding 
applications
 
Mechtron Systems
ABN: 52 149 788 293
329 Old Canobolas Road NASHDALE NSW 2800
mob 04-2860-1801 ph 02-6365-3568 fx 02-6365-3578 


From francesco at trimarchi.it  Sun Jul 27 11:51:53 2008
From: francesco at trimarchi.it (Francesco Trimarchi)
Date: Sun, 27 Jul 2008 11:51:53 +0200
Subject: R: error compiling on centos 5.2
In-Reply-To: <d53357b70807250356x233d2db0r8d01365250a43202@mail.gmail.com>
References: <98b19a63642745869f5685c0958fc395@plesk1.auroranetwork.it>
	<d53357b70807250356x233d2db0r8d01365250a43202@mail.gmail.com>
Message-ID: <654B48A95BF24EE8A61F6FA7CF4EE2B5@trim01>

I already tested the file integrity an I disabled selinux but I own the same
compilation error 

The system is a VMWARE 1.06 virtual machine with virtual tools installed.

 
Francesco
________________________________________
Da: Antonio Straziota [mailto:devgioiatech at gmail.com] 
Inviato: venerd? 25 luglio 2008 12.56
A: francesco at trimarchi.it
Cc: kolab-users at kolab.org
Oggetto: Re: error compiling on centos 5.2

Did you check integrity of the downloaded files?
i kept similar error when a file was corrupted... check with md5sum -c
MD5SUMS

bye
2008/7/24 francesco at trimarchi.it <francesco at trimarchi.it>:
hello to everybody.

i'm trying to compile kolab on a centos 5.2 but I own the following error:

everybody can help me?

Francesco

...............

++ cleaning up environment
+ /kolab/bin/perl-openpkg -d
/kolab/RPM/SRC/perl-www/WWW-Mechanize-1.34.tar.gz -A --nolive configure
build install
++ OpenPKG perl-openpkg 2.0.1 (03-Dec-2004)
++ determined RPM ?program: /kolab/libexec/openpkg/rpm (4.2.1)
++ determined Perl program: /kolab/bin/perl (5.10.0)
++ step 2: configure
++ configuring module via ExtUtils::MakeMaker environment
Can't load
'/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Crypt/SSLeay/SSLeay.so'
for module Crypt::SSLeay:
/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Crypt/SSLeay/SSLeay.so:
cannot restore segment prot after reloc: Permission denied at
/kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 203.
?at /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/Net/SSL.pm line 19
Compilation failed in require at
/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/Net/SSL.pm line 19.
Compilation failed in require at
/kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/Net/HT
TPS.pm line 18.
Can't load
'/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Net/SSLeay/SSLeay.so'
for module Net::SSLeay:
/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Net/SSLeay/SSLeay.so:
cannot restore segment prot after reloc: Permission denied at
/kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 203.
?at /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18
Compilation failed in require at
/kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18.
BEGIN failed--compilation aborted at
/kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18.
Compilation failed in require at
/kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/Net/HT
TPS.pm line 22.
Compilation failed in require at
/kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/LWP/Pr
otocol/https.pm line 46.
Compilation failed in require at (eval 11) line 3.

++ step 3: build
perl-openpkg:ERROR: neither "Build" nor "Makefile" found in working
directory (No such file or directory)
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.31809 (%install)


RPM build errors:
? ?Bad exit status from /kolab/RPM/TMP/rpm-tmp.31809 (%install)



_______________________________________________
Kolab-users mailing list
Kolab-users at kolab.org
https://kolab.org/mailman/listinfo/kolab-users



From aspineux at gmail.com  Mon Jul 28 00:42:30 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 28 Jul 2008 00:42:30 +0200
Subject: R: error compiling on centos 5.2
In-Reply-To: <654B48A95BF24EE8A61F6FA7CF4EE2B5@trim01>
References: <98b19a63642745869f5685c0958fc395@plesk1.auroranetwork.it>
	<d53357b70807250356x233d2db0r8d01365250a43202@mail.gmail.com>
	<654B48A95BF24EE8A61F6FA7CF4EE2B5@trim01>
Message-ID: <71fe4e760807271542n54f132a5s7a8dd444e5f83537@mail.gmail.com>

On Sun, Jul 27, 2008 at 11:51 AM, Francesco Trimarchi
<francesco at trimarchi.it> wrote:
> I already tested the file integrity an I disabled selinux but I own the same
> compilation error

Some idea:

Did you reboot after disabling SELinux ?
Are you trying to compile colab without hord ?
>
> The system is a VMWARE 1.06 virtual machine with virtual tools installed.
>
>
> Francesco
> ________________________________________
> Da: Antonio Straziota [mailto:devgioiatech at gmail.com]
> Inviato: venerd? 25 luglio 2008 12.56
> A: francesco at trimarchi.it
> Cc: kolab-users at kolab.org
> Oggetto: Re: error compiling on centos 5.2
>
> Did you check integrity of the downloaded files?
> i kept similar error when a file was corrupted... check with md5sum -c
> MD5SUMS
>
> bye
> 2008/7/24 francesco at trimarchi.it <francesco at trimarchi.it>:
> hello to everybody.
>
> i'm trying to compile kolab on a centos 5.2 but I own the following error:
>
> everybody can help me?
>
> Francesco
>
> ...............
>
> ++ cleaning up environment
> + /kolab/bin/perl-openpkg -d
> /kolab/RPM/SRC/perl-www/WWW-Mechanize-1.34.tar.gz -A --nolive configure
> build install
> ++ OpenPKG perl-openpkg 2.0.1 (03-Dec-2004)
> ++ determined RPM  program: /kolab/libexec/openpkg/rpm (4.2.1)
> ++ determined Perl program: /kolab/bin/perl (5.10.0)
> ++ step 2: configure
> ++ configuring module via ExtUtils::MakeMaker environment
> Can't load
> '/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Crypt/SSLeay/SSLeay.so'
> for module Crypt::SSLeay:
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Crypt/SSLeay/SSLeay.so:
> cannot restore segment prot after reloc: Permission denied at
> /kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 203.
>  at /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/Net/SSL.pm line 19
> Compilation failed in require at
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/Net/SSL.pm line 19.
> Compilation failed in require at
> /kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/Net/HT
> TPS.pm line 18.
> Can't load
> '/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Net/SSLeay/SSLeay.so'
> for module Net::SSLeay:
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Net/SSLeay/SSLeay.so:
> cannot restore segment prot after reloc: Permission denied at
> /kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 203.
>  at /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18
> Compilation failed in require at
> /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18.
> BEGIN failed--compilation aborted at
> /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18.
> Compilation failed in require at
> /kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/Net/HT
> TPS.pm line 22.
> Compilation failed in require at
> /kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/LWP/Pr
> otocol/https.pm line 46.
> Compilation failed in require at (eval 11) line 3.
>
> ++ step 3: build
> perl-openpkg:ERROR: neither "Build" nor "Makefile" found in working
> directory (No such file or directory)
> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.31809 (%install)
>
>
> RPM build errors:
>    Bad exit status from /kolab/RPM/TMP/rpm-tmp.31809 (%install)
>
>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From aspineux at gmail.com  Mon Jul 28 00:49:46 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 28 Jul 2008 00:49:46 +0200
Subject: Feature request: reply-to setting for distribution lists
In-Reply-To: <488AF105.1040707@dragonrising.com>
References: <488AF105.1040707@dragonrising.com>
Message-ID: <71fe4e760807271549k58813770yc860684bae65c47@mail.gmail.com>

On Sat, Jul 26, 2008 at 11:40 AM, Alex <lbf at dragonrising.com> wrote:
> Hello,
>
> Firstly, to the developers - a big well done for the good work on Kolab
> Server 2.2. I found this release a million times easier to install than
> my efforts on 2.0 + horde, which I never got working properly.
>
> Now for the request...
>
> I use distribution lists as a way for my colleagues to chat amongst each
> other, so it would be really useful if the reply-to field of the email
> header could point my users reply back at the distribution list.
>
> At the moment, I can get round this by manually setting the reply-to
> field in Thunderbird mail client - but it's not convenient and many of
> my users forget to do this, causing their reply to just go back to the
> user that sent the mail.
>
> If that makes sense.

I think mailman do the trick :-)
Then the question is:  why, if mailman does that already add this
feature to kolab :-)
And you are lucky, the kolab's wiki has a section about how to
integrate mailman into kolab.

Regards.

>
> Thanks again,
>
> Alex
>
> ps: SyncKolab - also excellent!
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From francesco at trimarchi.it  Mon Jul 28 08:03:42 2008
From: francesco at trimarchi.it (Francesco Trimarchi)
Date: Mon, 28 Jul 2008 08:03:42 +0200
Subject: R: R: error compiling on centos 5.2
In-Reply-To: <71fe4e760807271542n54f132a5s7a8dd444e5f83537@mail.gmail.com>
References: <98b19a63642745869f5685c0958fc395@plesk1.auroranetwork.it>
	<d53357b70807250356x233d2db0r8d01365250a43202@mail.gmail.com>
	<654B48A95BF24EE8A61F6FA7CF4EE2B5@trim01>
	<71fe4e760807271542n54f132a5s7a8dd444e5f83537@mail.gmail.com>
Message-ID: <C76E9096C682466A989FDA4B394DFCD0@trim01>

I successfully compiled kolab with the same files on a VM based on ubuntu
server 8.04.

On Centos: yes, I rebooted before compile.
I will try to compile without horde (but I need horde to access to mail
system from remote!).

Someone in mailing list had successfully compiled on Centos 5.2?

Best regards

francesco

  

-----Messaggio originale-----
Da: Alain Spineux [mailto:aspineux at gmail.com] 
Inviato: luned? 28 luglio 2008 0.43
A: Francesco Trimarchi
Cc: Antonio Straziota; kolab-users at kolab.org
Oggetto: Re: R: error compiling on centos 5.2

On Sun, Jul 27, 2008 at 11:51 AM, Francesco Trimarchi
<francesco at trimarchi.it> wrote:
> I already tested the file integrity an I disabled selinux but I own the
same
> compilation error

Some idea:

Did you reboot after disabling SELinux ?
Are you trying to compile colab without hord ?
>
> The system is a VMWARE 1.06 virtual machine with virtual tools installed.
>
>
> Francesco
> ________________________________________
> Da: Antonio Straziota [mailto:devgioiatech at gmail.com]
> Inviato: venerd? 25 luglio 2008 12.56
> A: francesco at trimarchi.it
> Cc: kolab-users at kolab.org
> Oggetto: Re: error compiling on centos 5.2
>
> Did you check integrity of the downloaded files?
> i kept similar error when a file was corrupted... check with md5sum -c
> MD5SUMS
>
> bye
> 2008/7/24 francesco at trimarchi.it <francesco at trimarchi.it>:
> hello to everybody.
>
> i'm trying to compile kolab on a centos 5.2 but I own the following error:
>
> everybody can help me?
>
> Francesco
>
> ...............
>
> ++ cleaning up environment
> + /kolab/bin/perl-openpkg -d
> /kolab/RPM/SRC/perl-www/WWW-Mechanize-1.34.tar.gz -A --nolive configure
> build install
> ++ OpenPKG perl-openpkg 2.0.1 (03-Dec-2004)
> ++ determined RPM  program: /kolab/libexec/openpkg/rpm (4.2.1)
> ++ determined Perl program: /kolab/bin/perl (5.10.0)
> ++ step 2: configure
> ++ configuring module via ExtUtils::MakeMaker environment
> Can't load
>
'/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Crypt/SSLeay/SSLeay.so'
> for module Crypt::SSLeay:
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Crypt/SSLeay/SSLeay.so:
> cannot restore segment prot after reloc: Permission denied at
> /kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 203.
>  at /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/Net/SSL.pm line 19
> Compilation failed in require at
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/Net/SSL.pm line 19.
> Compilation failed in require at
>
/kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/Net/HT
> TPS.pm line 18.
> Can't load
> '/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Net/SSLeay/SSLeay.so'
> for module Net::SSLeay:
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Net/SSLeay/SSLeay.so:
> cannot restore segment prot after reloc: Permission denied at
> /kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 203.
>  at /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18
> Compilation failed in require at
> /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18.
> BEGIN failed--compilation aborted at
> /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18.
> Compilation failed in require at
>
/kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/Net/HT
> TPS.pm line 22.
> Compilation failed in require at
>
/kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/LWP/Pr
> otocol/https.pm line 46.
> Compilation failed in require at (eval 11) line 3.
>
> ++ step 3: build
> perl-openpkg:ERROR: neither "Build" nor "Makefile" found in working
> directory (No such file or directory)
> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.31809 (%install)
>
>
> RPM build errors:
>    Bad exit status from /kolab/RPM/TMP/rpm-tmp.31809 (%install)
>
>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From marko at mechtron.com.au  Mon Jul 28 13:51:01 2008
From: marko at mechtron.com.au (Mark Berndt)
Date: Mon, 28 Jul 2008 21:51:01 +1000
Subject: Mailman integration (was Re: Feature request: reply-to setting for
	distribution lists)
Message-ID: <200807282151.01748.marko@mechtron.com.au>

> On Sat, Jul 26, 2008 at 11:40 AM, Alex <lbf at dragonrising.com> wrote:
> > Hello,
> >
> > Firstly, to the developers - a big well done for the good work on Kolab
> > Server 2.2. I found this release a million times easier to install than
> > my efforts on 2.0 + horde, which I never got working properly.
> >
> > Now for the request...
> >
> > I use distribution lists as a way for my colleagues to chat amongst each
> > other, so it would be really useful if the reply-to field of the email
> > header could point my users reply back at the distribution list.
> >
> > At the moment, I can get round this by manually setting the reply-to
> > field in Thunderbird mail client - but it's not convenient and many of
> > my users forget to do this, causing their reply to just go back to the
> > user that sent the mail.
> >
> > If that makes sense.
>
> I think mailman do the trick :-)
> Then the question is:  why, if mailman does that already add this
> feature to kolab :-)
> And you are lucky, the kolab's wiki has a section about how to
> integrate mailman into kolab.

Mailman won't directly integrate with kolab, but can be made to work.

There are two choices - integrate mailman with your base operating system or 
use the openpkg mailman package.

I was able to make it work using the openpkg system.  I gave up trying to make 
it work with debian packages.

I couldn't get the wiki method working and went with using 
postfix_to_mailman.py script as there was less configuration file setup 
needed when adding new lists.  

Either way, I had to rebuild the mailman executable to ensure it has the 
correct uid/gid for the system. 

You need to modify the postfix configuration file, including removing the 
masqurade_domains section and add the new relay_domains and mydestination 
entries.  You also must use local_transport, not mailbox_transport since only 
local_transport will process transport_maps (see below).

I went with using mailman_to_postfix.py as it was easier to setup in the 
postfix master.cf config file.   I used lists.somedomain.com to separate the 
mail from normal kolabuser at somedomain.com and a transport_map file to call 
the mailman_to_postfix on receiving mail for somelist at lists.somedomain.com.

Unfortunately I could not find a way to make the kolab template write the 
required lists.somedomain.com and somedomain.com entries in the mydestination 
section without causing kolabconf to go into an endless loop.  This means 
that everytime the kolab admin web interface is called (eg adding a user), it 
will trash your postfix main.cf file and you need to copy a backup over it 
manually.  All the other changes can be made in the templates.

I don't think it would be too hard to integrate mailman into kolab, it would 
just need an entry for the list subdomain prefix in the admin interface and 
some minor changes to config files.  This would certainly be something that 
would be used by many kolab sites.

I'll be doing another kolab/mailman install soon and hopefully will create 
some better documentation for the kolab wiki.

kind regards,

Marko
 

>
> Regards.
>
> > Thanks again,
> >
> > Alex
> >
> > ps: SyncKolab - also excellent!
> >
> > _______________________________________________
> > Kolab-users mailing list
> > Kolab-users at kolab.org
> > https://kolab.org/mailman/listinfo/kolab-users



-- 
High performance computer, software and automation systems for demanding 
applications
 
Mechtron Systems
ABN: 52 149 788 293
329 Old Canobolas Road NASHDALE NSW 2800
mob 04-2860-1801 ph 02-6365-3568 fx 02-6365-3578


From thomas at intevation.de  Mon Jul 28 15:47:41 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Mon, 28 Jul 2008 15:47:41 +0200
Subject: Feature request: reply-to setting for distribution lists
In-Reply-To: <71fe4e760807271549k58813770yc860684bae65c47@mail.gmail.com>
References: <488AF105.1040707@dragonrising.com>
	<71fe4e760807271549k58813770yc860684bae65c47@mail.gmail.com>
Message-ID: <20080728134741.GF26708.thomas@intevation.de>

* Alain Spineux <aspineux at gmail.com> [20080728 00:49]:
> On Sat, Jul 26, 2008 at 11:40 AM, Alex <lbf at dragonrising.com> wrote:
> > I use distribution lists as a way for my colleagues to chat amongst each
> > other, so it would be really useful if the reply-to field of the email
> > header could point my users reply back at the distribution list.
> >
> > At the moment, I can get round this by manually setting the reply-to
> > field in Thunderbird mail client - but it's not convenient and many of
> > my users forget to do this, causing their reply to just go back to the
> > user that sent the mail.
> >
> > If that makes sense.
> 
> I think mailman do the trick :-)
> Then the question is:  why, if mailman does that already add this
> feature to kolab :-)
> And you are lucky, the kolab's wiki has a section about how to
> integrate mailman into kolab.

Yes, mailman (or other mailing list software) is the way to go here.

Distribution lists try to avoid touching mail headers and if you
want to go into this direction, there already is a very good
solution for this.

Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From wrobel at pardus.de  Tue Jul 29 08:04:35 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Tue, 29 Jul 2008 08:04:35 +0200
Subject: Kolab 2.2.0 Debian packages for etch and mailing list
In-Reply-To: <4885B06A.30105@furna.com> (Luca Fornasari's message of "Tue,
	22 Jul 2008 18:03:22 +0800")
References: <4885B06A.30105@furna.com>
Message-ID: <87proxrzt8.fsf@home.pardus.de>

Luca Fornasari <luca at furna.com> writes:

> I searched the kolab-user mailing list archive at marc.info for "Deb 
> packages" and "Debian packages"; I found out that Ubuntu 8.04 has 
> packages of Kolab 2.1.0 and that Mathieu Parent made some packages that 
> are not available anymore at 
> http://mathieu.parent.free.fr/debian/kolab/2.2~rc1+20080204
> Daryl Caudill also mention a separate mailing list for Debian packages ...
>
> Anyone has any information about that mailing list or a new URL for .deb 
> packages of Kolab 2.2.0 for etch or lenny?

You can try to ask on their mailing list:

http://lists.alioth.debian.org/pipermail/pkg-kolab-devel/

Cheers,

Gunnar

>
> Thanks in adavance
>
> -- 
> Luca Fornasari
> FURNA.COM
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From wrobel at pardus.de  Tue Jul 29 08:21:58 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Tue, 29 Jul 2008 08:21:58 +0200
Subject: A (currently theoretical) question concerning a book about the
	Kolab Server
In-Reply-To: <200807241739.03861.bernhard@intevation.de> (Bernhard Reiter's
	message of "Thu, 24 Jul 2008 17:38:59 +0200")
References: <87ej626kj6.fsf@home.pardus.de> <87ej5sbwef.fsf@home.pardus.de>
	<200807171437.34235.richard@radoeka.nl>
	<200807241739.03861.bernhard@intevation.de>
Message-ID: <87iquprz09.fsf@home.pardus.de>

Bernhard Reiter <bernhard at intevation.de> writes:

> On Thursday 17 July 2008 14:37, Richard Bos wrote:
>> Op Thursday 17 July 2008 13:08:40 schreef Gunnar Wrobel:
>> > > The other thing is that kolab is fully based on a directory (ldap)
>> > > and imap storage instead of a database. ?But what is the big
>> > > advantage of using a directory and imap storage instead of database?
>
> More scalability.
> Many Imap servers use specialisted storage that is more easy to backup
> and thus actually is a specialist "database" with all advantages
> over a general database management system.

As Bernhard mentions: with IMAP you will only have one storage
system. Most groupware servers come with IMAP for mail storage and a
database for data storage. Combining this in one system makes both
replication and backup easier for the admin.

>
>> > > With IP everywhere a database is also very reachable from each
>> > > location, even from remote locations and databases can be replicated
>> > > as well.
>
> Replication with databases is much more difficult, the idea of Kolab
> is to avoid lock situations which make database replication very difficult.
> Also there is better separations between data stores if a less complicated 
> piece of software coverns it.
>
>> > You only look at the administrators point of view here. Of course the
>> > server admin can access a database. But what about the user? This is
>> > the most crucial point about Kolab for me. Of course Kolab offers a
>> > lot more than IMAP based storage of data. But to me this is the core
>> > element. And it is not a technical reason why I'm excited about this
>> > but a plain social one.
>>
>> I did not think about this aspect actually, but it is a very nice one
>> indeed.
>
> Yes, and it does not come from the IMAP usage, but from the idea of doing
> the main groupware work on the client. A good client can have several 
> storages, remote and local.

But do you envision to use any other kind of storage type than IMAP
for the future? I didn't see the client aspect of the solution yet but
it makes sense.

The question of other storage types would have some relevance for the
release of the Kolab_Storage package from Horde. It is currently still
married to IMAP though I could probably make that more flexible if
required.

Cheers,

Gunnar

>
>> However, if one is to use kolab in a company environment this fact (user in
>> control of data) is of no importance as the user should not move his email
>> :)
>
> Even a company world, people have private appointments and might be a member 
> of an non-profit association. My vision with Kontact and Kolab is that one 
> day you have your personal client which saves your appointments on the three 
> Kolab Servers: Company, Home, Association. Only the client has access to all 
> three sources of information.
> Corporations and large organisations will still like this as a happy employee
> with their private life being nice is a much better employee.
>
>> In that case why is the directory / imap storage better than other 
>> solutions? Probably because it is scalably.  But isn't the same valid for
>> groupware solutions based on a database (I wonder)?  Perhaps Bernard or
>> Martin can elaborate on this?
>
> (Martin does not read this list, AFAIK.)
> A bit is on the old http://kroupware.kolab.org/faq/faq.html#Kolab%20Server0
> Other things I would need to write down in a good way - a bit is in the design 
> documents of course, but might be burried somewhere.
>
> Bernhard
>
> -- 
> Managing Director - Owner: www.intevation.net       (Free Software Company)
> Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
> Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
> Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From wrobel at pardus.de  Tue Jul 29 08:31:06 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Tue, 29 Jul 2008 08:31:06 +0200
Subject: kolab 2.2.0 migration success + horde mobile access problem
In-Reply-To: <200807241741.13168.bernhard@intevation.de> (Bernhard Reiter's
	message of "Thu, 24 Jul 2008 17:41:12 +0200")
References: <200807132025.10108.thorsten.schnebeck@gmx.net>
	<871w1ulzze.fsf@home.pardus.de>
	<200807241741.13168.bernhard@intevation.de>
Message-ID: <87ej5dryl1.fsf@home.pardus.de>

Bernhard Reiter <bernhard at intevation.de> writes:

> On Wednesday 16 July 2008 15:28, Gunnar Wrobel wrote:
>> I guess you might also be able to just install mimp from one of the
>> horde release pacakges by unpacking it into
>> /kolab/var/kolab/www/horde.
>>
>> It will probably be included in Kolab-Server-2.2.1. 
>
> We should open an issue about this.

https://www.intevation.de/roundup/kolab/issue2943

>
>> The current Horde 
>> version was a frist trial version and we weren't able to extend this
>> to all the stuff Horde offers (e.g. dimp, mimp and SyncML). But 2.2.1
>> should see some upgrades and enhancements in that sector. Horde is
>> currently advancing a lot in the Kolab sector.
>
> -- 
> Managing Director - Owner: www.intevation.net       (Free Software Company)
> Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
> Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
> Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


From bernhard at intevation.de  Tue Jul 29 09:41:17 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 29 Jul 2008 09:41:17 +0200
Subject: A (currently theoretical) question concerning a book about the
	Kolab Server
In-Reply-To: <87iquprz09.fsf@home.pardus.de>
References: <87ej626kj6.fsf@home.pardus.de>
	<200807241739.03861.bernhard@intevation.de>
	<87iquprz09.fsf@home.pardus.de>
Message-ID: <200807290941.18651.bernhard@intevation.de>

On Tuesday 29 July 2008 08:21, Gunnar Wrobel wrote:
> As Bernhard mentions: with IMAP you will only have one storage
> system. Most groupware servers come with IMAP for mail storage and a
> database for data storage. Combining this in one system makes both
> replication and backup easier for the admin.

The other aspect is that many databases and groupware concepts
makes it hard to to an incremental backup online and keeping a consistant 
state. Often the result is that you need to backup a full large binary object 
with the complete dump of a consistant state.

> > Yes, and it does not come from the IMAP usage, but from the idea of doing
> > the main groupware work on the client. A good client can have several
> > storages, remote and local.
>
> But do you envision to use any other kind of storage type than IMAP
> for the future? I

No, but several IMAP stores, which can be distributed over several servers
(e.g. private, company, and spare time club).

> didn't see the client aspect of the solution yet but 
> it makes sense.

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20080729/544910aa/attachment-0001.bin

From troy at carpenter.cx  Tue Jul 29 13:36:41 2008
From: troy at carpenter.cx (Troy Carpenter)
Date: Tue, 29 Jul 2008 07:36:41 -0400
Subject: Don't make this mistake with Kontact
Message-ID: <200807290736.41825.troy@carpenter.cx>

Greetings all.

Last night I made a fatal mistake with Kontact and my Inbox.  I am using KMail 
1.10.0 from KDE 4.1 RC1.  I am sure this is a KMail problem and not anything 
in Kolab, but since many people use Kontact/KMail as their client, here's a 
warning:

On one account, I right-clicked on my Inbox, and from the drop down menu 
selected "Copy Folder To -> Troy Carpenter -> Copy to This Folder".  Kmail 
then erased all the email in my Inbox, recreated all the cyrus.* files, and 
showed two Inbox folders for my account, both mirroring the other (that is, 
they were both the same view into the same folder, not distinct folders).

I was trying to copy the Inbox folder into a subfolder of itself (which was 
blocked by KMail when I tried it later with the empty Inbox), but chose the 
wrong level.

Just beware in case users try to do this on their own...

Troy Carpenter

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20080729/3d4f70a6/attachment.bin

From aspineux at gmail.com  Tue Jul 29 18:04:49 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Tue, 29 Jul 2008 18:04:49 +0200
Subject: R: R: error compiling on centos 5.2
In-Reply-To: <C76E9096C682466A989FDA4B394DFCD0@trim01>
References: <98b19a63642745869f5685c0958fc395@plesk1.auroranetwork.it>
	<d53357b70807250356x233d2db0r8d01365250a43202@mail.gmail.com>
	<654B48A95BF24EE8A61F6FA7CF4EE2B5@trim01>
	<71fe4e760807271542n54f132a5s7a8dd444e5f83537@mail.gmail.com>
	<C76E9096C682466A989FDA4B394DFCD0@trim01>
Message-ID: <71fe4e760807290904g585f9a6bsc40539b782800714@mail.gmail.com>

On Mon, Jul 28, 2008 at 8:03 AM, Francesco Trimarchi
<francesco at trimarchi.it> wrote:
> I successfully compiled kolab with the same files on a VM based on ubuntu
> server 8.04.
>
> On Centos: yes, I rebooted before compile.
> I will try to compile without horde (but I need horde to access to mail
> system from remote!).

Noooooooooooo , because in one of the RC, compiling without Horde was failing !

>
> Someone in mailing list had successfully compiled on Centos 5.2?

Yes me a ( updated 5.1 )

>
> Best regards
>
> francesco
>
>
>
> -----Messaggio originale-----
> Da: Alain Spineux [mailto:aspineux at gmail.com]
> Inviato: luned? 28 luglio 2008 0.43
> A: Francesco Trimarchi
> Cc: Antonio Straziota; kolab-users at kolab.org
> Oggetto: Re: R: error compiling on centos 5.2
>
> On Sun, Jul 27, 2008 at 11:51 AM, Francesco Trimarchi
> <francesco at trimarchi.it> wrote:
>> I already tested the file integrity an I disabled selinux but I own the
> same
>> compilation error
>
> Some idea:
>
> Did you reboot after disabling SELinux ?
> Are you trying to compile colab without hord ?
>>
>> The system is a VMWARE 1.06 virtual machine with virtual tools installed.
>>
>>
>> Francesco
>> ________________________________________
>> Da: Antonio Straziota [mailto:devgioiatech at gmail.com]
>> Inviato: venerd? 25 luglio 2008 12.56
>> A: francesco at trimarchi.it
>> Cc: kolab-users at kolab.org
>> Oggetto: Re: error compiling on centos 5.2
>>
>> Did you check integrity of the downloaded files?
>> i kept similar error when a file was corrupted... check with md5sum -c
>> MD5SUMS
>>
>> bye
>> 2008/7/24 francesco at trimarchi.it <francesco at trimarchi.it>:
>> hello to everybody.
>>
>> i'm trying to compile kolab on a centos 5.2 but I own the following error:
>>
>> everybody can help me?
>>
>> Francesco
>>
>> ...............
>>
>> ++ cleaning up environment
>> + /kolab/bin/perl-openpkg -d
>> /kolab/RPM/SRC/perl-www/WWW-Mechanize-1.34.tar.gz -A --nolive configure
>> build install
>> ++ OpenPKG perl-openpkg 2.0.1 (03-Dec-2004)
>> ++ determined RPM  program: /kolab/libexec/openpkg/rpm (4.2.1)
>> ++ determined Perl program: /kolab/bin/perl (5.10.0)
>> ++ step 2: configure
>> ++ configuring module via ExtUtils::MakeMaker environment
>> Can't load
>>
> '/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Crypt/SSLeay/SSLeay.so'
>> for module Crypt::SSLeay:
>> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Crypt/SSLeay/SSLeay.so:
>> cannot restore segment prot after reloc: Permission denied at
>> /kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 203.
>>  at /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/Net/SSL.pm line 19
>> Compilation failed in require at
>> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/Net/SSL.pm line 19.
>> Compilation failed in require at
>>
> /kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/Net/HT
>> TPS.pm line 18.
>> Can't load
>> '/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Net/SSLeay/SSLeay.so'
>> for module Net::SSLeay:
>> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/auto/Net/SSLeay/SSLeay.so:
>> cannot restore segment prot after reloc: Permission denied at
>> /kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 203.
>>  at /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18
>> Compilation failed in require at
>> /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18.
>> BEGIN failed--compilation aborted at
>> /kolab/lib/perl/vendor_perl/5.10.0/IO/Socket/SSL.pm line 18.
>> Compilation failed in require at
>>
> /kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/Net/HT
>> TPS.pm line 22.
>> Compilation failed in require at
>>
> /kolab/RPM/TMP/perl-www-5.10.0-root/kolab/lib/perl/vendor_perl/5.10.0/LWP/Pr
>> otocol/https.pm line 46.
>> Compilation failed in require at (eval 11) line 3.
>>
>> ++ step 3: build
>> perl-openpkg:ERROR: neither "Build" nor "Makefile" found in working
>> directory (No such file or directory)
>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.31809 (%install)
>>
>>
>> RPM build errors:
>>    Bad exit status from /kolab/RPM/TMP/rpm-tmp.31809 (%install)
>>
>>
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>
>
>
>
> --
> Alain Spineux
> aspineux gmail com
> May the sources be with you
>
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you


From albrecht.dress at lios-tech.com  Thu Jul 31 10:35:05 2008
From: albrecht.dress at lios-tech.com (=?UTF-8?B?QWxicmVjaHQgRHJlw58=?=)
Date: Thu, 31 Jul 2008 10:35:05 +0200
Subject: Distributed setup
Message-ID: <48917939.5040508@lios-tech.com>

Hi all,

I'm new to this list, so please excuse me if my questions are really dumb...

I would like to install Kolab 2.2 on /two/ Ubuntu Hardy machines in a "distributed" way:  box #1 shall have the Cyrus, Postfix and Apache related stuff installed, and box #2 shall get all the rest.  Apart for a more equally distributed load, the services on #1 shall be visible to the outside world.  Obviously, this box must be treated with more care.  Are there any descriptions how to install such a scenario?

Related to this, it would be great if I could use the pre-built Apache/Horde, Postfix and Cyrus packages on #1.  The advantage is that (1) I can rely on the Ubuntu package management for security updates and (2) it will probably be easier to write proper SELinux policies (or do policies already exist?).  Any opinion about this?

Connected to the distributed install question above, maybe I can do a "full" install on #2, install the "stock" Ubuntu packages on #1, and then just copy the configs and tweak a few connection settings?  Or is this a too simplified approach?

Thanks in advance,
Albrecht.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: albrecht_dress.vcf
Type: text/x-vcard
Size: 547 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20080731/af6007bf/albrecht_dress.bin

From symedeot at yahoo.fr  Thu Jul 31 15:53:38 2008
From: symedeot at yahoo.fr (Sylvain MEDEOT)
Date: Thu, 31 Jul 2008 15:53:38 +0200
Subject: Problem migrating from kolab 2.1 to kolab 2.2
Message-ID: <4891C3E2.3060101@yahoo.fr>

Hi,

I have currently running kolab 2.1 in production without problem.

I tried today to move it to kolab 2.2 (virtual guest).
The full upgrade process gives no error.

But I am suffering several problems.

There is a change in the structure of the imap/spool folders :

Structure with Kolab 2.1
========================

|-- spool
|   |-- domain
|   |   `-- ville-pontoise.fr
|   |       `-- user
|   |           |-- auser1
|   |           |   |-- 11.
|   `-- stage.


Structure with Kolab 2.2
========================

|-- spool
|   |-- domain
|   |   `-- v
|   |       `-- ville-pontoise.fr
|   |           |-- a
|   |           |   `-- user
|   |           |       |-- auser1
|   |           |       |   |-- 11.
|   |           |       |-- auser2
|   |           |       |   |-- 11.

I had to rework reorganize through a batch process the data. Then, all 
seems to work normally.
I noticed nothing about that in the upgrade procedure...

The second issue is linked to horde. When I access horde 
(https://fqdn/horde), I am not asked for authentification and I am 
logged as an administrator : many features are not configured...

I tried to install kolab 2.2 without upgrading my previous installation 
and then it works fine : I can access horde in a normal way and all 
seems to work fine.

Can anybody points me to what I've missed ?

Kind regards,

Sylvain


From thomas at intevation.de  Thu Jul 31 16:11:39 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Thu, 31 Jul 2008 16:11:39 +0200
Subject: Problem migrating from kolab 2.1 to kolab 2.2
In-Reply-To: <4891C3E2.3060101@yahoo.fr>
References: <4891C3E2.3060101@yahoo.fr>
Message-ID: <20080731141139.GE19320.thomas@intevation.de>

* Sylvain MEDEOT <symedeot at yahoo.fr> [20080731 15:54]:
> There is a change in the structure of the imap/spool folders :
> 
> Structure with Kolab 2.1
> ========================
> 
> |-- spool
> |   |-- domain
> |   |   `-- ville-pontoise.fr
> |   |       `-- user
> |   |           |-- auser1
> |   |           |   |-- 11.
> |   `-- stage.
> 
> 
> Structure with Kolab 2.2
> ========================
> 
> |-- spool
> |   |-- domain
> |   |   `-- v
> |   |       `-- ville-pontoise.fr
> |   |           |-- a
> |   |           |   `-- user
> |   |           |       |-- auser1
> |   |           |       |   |-- 11.
> |   |           |       |-- auser2
> |   |           |       |   |-- 11.
> 
> I had to rework reorganize through a batch process the data. Then, all 
> seems to work normally.
> I noticed nothing about that in the upgrade procedure...

This probably is a server that got upgraded from 2.0 to 2.1, the
upgrade instructions for that include the following text:

| The default imapd configuration has been changed to enable the
| hashimapspool option.  This means that in 2.1 the default directory
| layout of the imapd spool (/kolab/var/imapd/spool/) is different from
| the one in 2.0.  When you upgrade from 2.0 it's best to keep using the
| old structure, so remove or comment out the line "hashimapspool: yes"
| in /kolab/etc/kolab/templates/imapd.conf.template *before* running
| kolabconf.
|
| For new installations the new default setting is recommended because
| it's more efficient especially when you have many mailboxes.
|
| For some background information about this see the dicussion at
| https://intevation.de/roundup/kolab/issue1089

A python script to convert the old layout to the new one is on the CVS server:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/*checkout*/utils/admin/hash-imap-spool

> The second issue is linked to horde. When I access horde 
> (https://fqdn/horde), I am not asked for authentification and I am 
> logged as an administrator : many features are not configured...
> 
> I tried to install kolab 2.2 without upgrading my previous installation 
> and then it works fine : I can access horde in a normal way and all 
> seems to work fine.

I can't reproduce this, even on an upgraded system.
You may want to remove cookies you have for the old server.

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From thomas at intevation.de  Thu Jul 31 16:18:45 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Thu, 31 Jul 2008 16:18:45 +0200
Subject: R: R: error compiling on centos 5.2
In-Reply-To: <71fe4e760807290904g585f9a6bsc40539b782800714@mail.gmail.com>
References: <98b19a63642745869f5685c0958fc395@plesk1.auroranetwork.it>
	<d53357b70807250356x233d2db0r8d01365250a43202@mail.gmail.com>
	<654B48A95BF24EE8A61F6FA7CF4EE2B5@trim01>
	<71fe4e760807271542n54f132a5s7a8dd444e5f83537@mail.gmail.com>
	<C76E9096C682466A989FDA4B394DFCD0@trim01>
	<71fe4e760807290904g585f9a6bsc40539b782800714@mail.gmail.com>
Message-ID: <20080731141845.GF19320.thomas@intevation.de>

* Alain Spineux <aspineux at gmail.com> [20080729 18:05]:
> On Mon, Jul 28, 2008 at 8:03 AM, Francesco Trimarchi
> <francesco at trimarchi.it> wrote:
> > I successfully compiled kolab with the same files on a VM based on ubuntu
> > server 8.04.
> >
> > On Centos: yes, I rebooted before compile.
> > I will try to compile without horde (but I need horde to access to mail
> > system from remote!).
> 
> Noooooooooooo , because in one of the RC, compiling without Horde was failing !

Installing without Horde from binary packages compiled with horde
failed. And it still fails, but we install Horde now by default.

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From devgioiatech at gmail.com  Thu Jul 31 16:48:36 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Thu, 31 Jul 2008 16:48:36 +0200
Subject: R: R: error compiling on centos 5.2
In-Reply-To: <20080731141845.GF19320.thomas@intevation.de>
References: <98b19a63642745869f5685c0958fc395@plesk1.auroranetwork.it>
	<d53357b70807250356x233d2db0r8d01365250a43202@mail.gmail.com>
	<654B48A95BF24EE8A61F6FA7CF4EE2B5@trim01>
	<71fe4e760807271542n54f132a5s7a8dd444e5f83537@mail.gmail.com>
	<C76E9096C682466A989FDA4B394DFCD0@trim01>
	<71fe4e760807290904g585f9a6bsc40539b782800714@mail.gmail.com>
	<20080731141845.GF19320.thomas@intevation.de>
Message-ID: <d53357b70807310748vc5a164es8e8441493f5826d4@mail.gmail.com>

Did you install libtool automake autoconf ?

2008/7/31 Thomas Arendsen Hein <thomas at intevation.de>

> * Alain Spineux <aspineux at gmail.com> [20080729 18:05]:
> > On Mon, Jul 28, 2008 at 8:03 AM, Francesco Trimarchi
> > <francesco at trimarchi.it> wrote:
> > > I successfully compiled kolab with the same files on a VM based on
> ubuntu
> > > server 8.04.
> > >
> > > On Centos: yes, I rebooted before compile.
> > > I will try to compile without horde (but I need horde to access to mail
> > > system from remote!).
> >
> > Noooooooooooo , because in one of the RC, compiling without Horde was
> failing !
>
> Installing without Horde from binary packages compiled with horde
> failed. And it still fails, but we install Horde now by default.
>
> Regards,
> Thomas
>
> --
> thomas at intevation.de - http://intevation.de/~thomas/<http://intevation.de/%7Ethomas/>- OpenPGP key: 0x5816791A
> Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
> Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
-------------- parte successiva --------------
Un allegato HTML ? stato rimosso...
URL: http://kolab.org/pipermail/kolab-users/attachments/20080731/7e7b8cad/attachment.html

From symedeot at yahoo.fr  Thu Jul 31 19:34:25 2008
From: symedeot at yahoo.fr (Sylvain MEDEOT)
Date: Thu, 31 Jul 2008 19:34:25 +0200
Subject: Problem migrating from kolab 2.1 to kolab 2.2
In-Reply-To: <20080731141139.GE19320.thomas@intevation.de>
References: <4891C3E2.3060101@yahoo.fr>
	<20080731141139.GE19320.thomas@intevation.de>
Message-ID: <4891F7A1.20105@yahoo.fr>

> A python script to convert the old layout to the new one is on the CVS server:
> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/*checkout*/utils/admin/hash-imap-spool
> 
>> The second issue is linked to horde. When I access horde 
>> (https://fqdn/horde), I am not asked for authentification and I am 
>> logged as an administrator : many features are not configured...
>>
>> I tried to install kolab 2.2 without upgrading my previous installation 
>> and then it works fine : I can access horde in a normal way and all 
>> seems to work fine.
> 
> I can't reproduce this, even on an upgraded system.
> You may want to remove cookies you have for the old server.
> 
> Regards,
> Thomas
> 

Hi Thomas,

Many thanks for your help. I delete all the cookies from my browser, no change.

Can you tell me where the configuration of horde is stored ?

I was using with kolab 2.1 an old version of horde and delete all the related informations 
stored in the ldap tree to see if that was the trouble but it makes no change.

Any advise welcome,

Kind regards,

Sylvain


From bogus@does.not.exist.com  Wed Jul 30 18:44:19 2008
From: bogus@does.not.exist.com ()
Date: Wed, 30 Jul 2008 16:44:19 -0000
Subject: No subject
Message-ID: <mailman.0.1218189518.2162.kolab-users@kolab.org>

20080416 (clamav)

The package can be installed on your Kolab Server with

# /kolab/bin/openpkg rpm --rebuild clamav-0.93-20080414_kolab.src.rpm
# /kolab/bin/openpkg rpm \
 -Uvh /kolab/RPM/PKG/clamav-0.93-20080414_kolab.<ARCH>-<OS>-kolab.rpm
# rm /kolab/etc/clamav/*.rpmsave
# /kolab/bin/openpkg rc clamav stop
# /kolab/bin/openpkg rc clamav start
# su - kolab-r
$ freshclam
$ rm -r /kolab/share/clamav/*.inc

Hope this help

>
> I'll try to build the complete kolab sources locally and check again and let
> you know if it worked.
>
> Best regards,
> Saim
>>
>>
>>>
>>> Best regards,
>>> 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
>>>
>>> --------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Kolab-users mailing list
>>> Kolab-users at kolab.org
>>> https://kolab.org/mailman/listinfo/kolab-users
>>>
>>>
>>
>>
>>
>>
>
>
> --
> --------------------------------------------------------------------------
> 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
> --------------------------------------------------------------------------
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you