From oszwald at web.de  Mon Dec  1 08:52:14 2008
From: oszwald at web.de (Florian Oszwald)
Date: Mon, 1 Dec 2008 08:52:14 +0100
Subject: Kolab-users Digest, Vol 57, Issue 37
In-Reply-To: <mailman.3401.1227996238.2135.kolab-users@kolab.org>
References: <mailman.3401.1227996238.2135.kolab-users@kolab.org>
Message-ID: <200812010852.14496.oszwald@web.de>

Am Samstag 29 November 2008 23:03:58 schrieb kolab-users-request at kolab.org:
> Quoting Florian Oszwald <oszwald at web.de>:
> > Hi all,
> >
> > I now have horde installed working together with kolab on opensuse 10.2.
> >
> > The problem is, that i get the message DB Error: not found everytime I
> > log in on a new day or making a new entry in the calendar or in notes.
> >
> > In /var/log/horde/horde.log I do not get any useful information about
> > this problem. On the internet I found, that it might be related to the
> > SQL, but I am using it together with Kolab, so there is no need for sql,
> > is there?
>
> Correct. In general there is no need for a database. If Horde gives ?
> you this error the configuration provided by the package maintainers ?
> is broken and you should submit a bug concerning the package.
>
> For newer Horde/Kolab installations you need a database if you want to ?
> use SyncML. But it should be sufficient if this is based on sqlite and ?
> I see it as a package maintainers task to provide a correctly ?
> preconfigured database in that case.
>
> Cheers,
>
> Gunnar

Hi Gunnar,
thank you very much for your email.
Would it be possible to somehow narrow it a little bit more down, so I can 
file the bug more exactly and help the package maintainer more precisely?

Installing Kolab/horde with openpgk will not work for me due to limited 
bandwith and traffic.

Maybe you can point me to something where to look at, and I will try it out.

Regards,
Florian



From carsten at cburghardt.com  Mon Dec  1 09:37:57 2008
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Mon, 01 Dec 2008 09:37:57 +0100
Subject: Mail not rejected
In-Reply-To: <200811251455.44954.itsef-admin@brightsight.com>
References: <200811132129.05713.carsten@cburghardt.com>
	<71fe4e760811140841o5f5e633eh17205a93479e0f36@mail.gmail.com>
	<20081114205655.12501znrhyasbfnk@www.inovox.de>
	<200811251455.44954.itsef-admin@brightsight.com>
Message-ID: <20081201093757.12701v1mmh5ts9y8@www.inovox.de>

Quoting "ITSEF Admin" <itsef-admin at brightsight.com>:

> On Friday 14 November 2008 20:56:55 Carsten Burghardt wrote:
>> I tested some usernames and noticed an (for me) inconsistent
>> behaviour. A mail to mail at mydomain is accepted whereas
>> nonsense at mydomain is rejected. I have not created an alias entry for
>> "mail" that is for sure.
>
> Is "mail at domain" the only "strange" address that works? "mail at domain" *seems*
> to be a standard address that always work. I have not been able to track down
> where this is defined or where Kolab enables this, but it sure
> worked "out-of-the-box" on our Kolab server as well (2.0.x and 2.1).

Thanks for the information as that seems to be the case. Unfortunately  
a lot of the spam senders also know this.


Carsten



From loic.elineau at benefacere.fr  Mon Dec  1 09:59:30 2008
From: loic.elineau at benefacere.fr (=?iso-8859-15?q?Lo=EFc_Elineau?=)
Date: Mon, 1 Dec 2008 09:59:30 +0100
Subject: Add logging info for untrusted sender
In-Reply-To: <20081129225406.977471nqljgy4p44@webmail.pardus.de>
References: <200811271136.10514.loic.elineau@benefacere.fr>
	<200811271557.25756.loic.elineau@benefacere.fr>
	<20081129225406.977471nqljgy4p44@webmail.pardus.de>
Message-ID: <200812010959.30755.loic.elineau@benefacere.fr>

Hy,
> > I don't want kolab to add "UNTRUSTED", I'd like it to respond with 550
> > error.
>
> Should be possible by switching to "Reject forged from header" in the
> Kolab web admin "Service" tab.
>
Isn't it supposed to implie problems with mailing lists subscribtions such as 
this one?
I'll try it

Cheers

-- 
Lo?c Elineau
http://www.benefacere.fr/



From loic.elineau at benefacere.fr  Mon Dec  1 10:06:20 2008
From: loic.elineau at benefacere.fr (=?iso-8859-1?q?Lo=EFc_Elineau?=)
Date: Mon, 1 Dec 2008 10:06:20 +0100
Subject: Add logging info for untrusted sender
In-Reply-To: <71fe4e760811292146p59d6f60aqb4c9f486a388c454@mail.gmail.com>
References: <200811271136.10514.loic.elineau@benefacere.fr>
	<200811271557.25756.loic.elineau@benefacere.fr>
	<71fe4e760811292146p59d6f60aqb4c9f486a388c454@mail.gmail.com>
Message-ID: <200812011006.20934.loic.elineau@benefacere.fr>

Hello
>
> Sorry I didn(t know about the "UNTRUSTED" label added by kolab, I was
> thinking about
> something else.
> Do you want to deny any unauthenticated connection ?
>
Yes, but it isn't possible if I want kolab to deliver mails from external. The 
problems deal with "reject forged from header" as write by Gunnar. But if I 
check this option, I am afraid I won't receive kolab-users messages any more, 
as the "to" field doesn't equals to me. I try it....

best regards,


-- 
Lo?c Elineau
http://www.benefacere.fr/



From loic.elineau at benefacere.fr  Mon Dec  1 10:11:51 2008
From: loic.elineau at benefacere.fr (=?iso-8859-15?q?Lo=EFc_Elineau?=)
Date: Mon, 1 Dec 2008 10:11:51 +0100
Subject: Add logging info for untrusted sender
In-Reply-To: <20081129225406.977471nqljgy4p44@webmail.pardus.de>
References: <200811271136.10514.loic.elineau@benefacere.fr>
	<200811271557.25756.loic.elineau@benefacere.fr>
	<20081129225406.977471nqljgy4p44@webmail.pardus.de>
Message-ID: <200812011011.51285.loic.elineau@benefacere.fr>

>
> Should be possible by switching to "Reject forged from header" in the
> Kolab web admin "Service" tab.
>
it seems it's working without I lost mail from mailing lists. There must be 
anything wrong in the assertion:
"Always reject the message. Note that enabling this setting will make the 
server reject any mail with non-matching sender and From header if the sender 
is an account on this server. This is known to cause trouble for example with 
mailinglists. "

I'll wait a few days to validate that I don't receive any more spams from 
"UNSTRUSTED me" :D

Cheers

-- 
Lo?c Elineau
http://www.benefacere.fr/



From albrecht.dress at lios-tech.com  Tue Dec  2 10:37:40 2008
From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=)
Date: Tue, 02 Dec 2008 10:37:40 +0100
Subject: Log Rotation Question
In-Reply-To: <20081129223500.13926z1ud9jqcq88@webmail.pardus.de> (from
	wrobel@pardus.de on Sat Nov 29 22:35:00 2008)
References: <1227090006l.24345l.0l@pc-adr2.lios-koeln.de>
	<20081123184512.48472gaw2c9egj3c@portal.lios-koeln.de>
	<20081129223500.13926z1ud9jqcq88@webmail.pardus.de>
Message-ID: <1228210660l.3344l.1l@pc-adr2.lios-koeln.de>

Am 29.11.2008 22:35:00 schrieb(en) Gunnar Wrobel:
> The notices can in fact be ignored. Though I hope they are gone with  
> Kolab Server 2.2.1.
[snipped descriptions]

Thanks for the clarification - the important message is that there is  
nothing I really have to worry about...

Best, Albrecht.


Dr. Albrecht Dre?
LIOS Technology GmbH
R & D - Software Design
Schanzenstrasse 39 / Building D9-D13
D-51063 Cologne / Germany
Phone +49 221 99887 401
Fax   +49 221 99887 150
Managing Director: Thomas Oldemeyer
Registration Court Amtsgericht Cologne, Reg.-No. HRB 33482



From albrecht.dress at lios-tech.com  Tue Dec  2 10:59:38 2008
From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=)
Date: Tue, 02 Dec 2008 10:59:38 +0100
Subject: Duplication of appointments in shared calendar
Message-ID: <1228211978l.3344l.2l@pc-adr2.lios-koeln.de>

Hi,

I have a *really* nasty problem with the duplication of appointments in  
a shared calendar.  I run a self-compiled Kolab 2.2.0 on Ubuntu  
8.04/64.  My users (~35) use Outlook 2002/2003/2007 through the latest  
Toltec connector.

The problem occurs on a shared calendar for which all users have write  
access.  Periodically, *all* appointments in this calendar get  
mysteriously duplicated, and in some cases they occur even more times  
(I saw up to 8 copies of the same one).  Sometimes the attributes of  
the copies are slightly different (e.g. the background colour displayed  
in Outlook is changed).

I tried to follow (in imapd.log) who adds the "spam" to the calendar,  
and temporarily de-activated write access for those users, but  
apparently many of them seem to trigger this problem.

Is this a known problem?  In Toltec or in Kolab?  Any idea how I can  
solve this bug?  It is somewhat annoying to manually erase the  
duplicates manually every day...

Thanks,
Albrecht.



From g.adamczyk at netkult.eu  Tue Dec  2 12:30:14 2008
From: g.adamczyk at netkult.eu (Gregor Adamczyk)
Date: Tue, 02 Dec 2008 12:30:14 +0100
Subject: How-To activate RBL (Spamhaus), the SpamAssassin way
Message-ID: <49351C46.20007@netkult.eu>

Halo, I have some trouble with activating SPAMHAUS RBL and another in
Kolab 2.2.

I don't really understand the working mechanism from amavisd-new.

I read already some FAQ but this don't help me to understand the situation.

In the FAQ: http://www.ijs.si/software/amavisd/#faq-spam

I read this:
Does SpamAssassin observe settings in its configuration file local.cf?
SA does observe all settings in its configuration file, but not all of
them have effect...

I know that it is possible to activate RBL on two ways.
With SpamAssassin or directly in Postfix.

I think SpamAssassin is the better way, so I test this:

change in:
/kolab/etc/kolab/templates/local.cf.template
score RCVD_IN_SBL 10
score RCVD_IN_XBL 10
score RCVD_IN_PBL 10

change in:
/kolab/etc/kolab/templates/amavisd.conf.template
$sa_local_tests_only = 0;   # (default: false)

then run:
/kolab/sbin/kolabconf

after request a SPAM test mail (nelson-sbl-test at crynwr.com) from spamhaus:

read instruction here:
http://www.spamhaus.org/sbl/howtouse.html

I received the black listed mail without any higher score.

I don't understand why, please help me to understand this...

Thank You



From joon at radleys.co.za  Tue Dec  2 16:03:18 2008
From: joon at radleys.co.za (Joon Radley)
Date: Tue, 2 Dec 2008 17:03:18 +0200
Subject: Duplication of appointments in shared calendar
In-Reply-To: <1228211978l.3344l.2l@pc-adr2.lios-koeln.de>
References: <1228211978l.3344l.2l@pc-adr2.lios-koeln.de>
Message-ID: <004101c9548f$1eb82190$5c2864b0$@co.za>

Hi Albrecht,

Can you please direct your Toltec related support questions to
support at toltec.co.za. This is the Kolab support mailing list and it is not
vendor specific.

Regards

Joon Radley
Radley Network Technologies CC
Cell: +27 (0)83 368 8557
Fax: +27 (0)12 998 4346
E-mail: joon at radleys.co.za
Web: www.toltec.co.za

> -----Original Message-----
> From: kolab-users-bounces at kolab.org [mailto:kolab-users-
> bounces at kolab.org] On Behalf Of Albrecht Dre?
> Sent: Tuesday, December 02, 2008 12:00 PM
> To: Kolab Users List
> Cc: support at toltec.co.za
> Subject: Duplication of appointments in shared calendar
> 
> Hi,
> 
> I have a *really* nasty problem with the duplication of appointments in
> a shared calendar.  I run a self-compiled Kolab 2.2.0 on Ubuntu
> 8.04/64.  My users (~35) use Outlook 2002/2003/2007 through the latest
> Toltec connector.
> 
> The problem occurs on a shared calendar for which all users have write
> access.  Periodically, *all* appointments in this calendar get
> mysteriously duplicated, and in some cases they occur even more times
> (I saw up to 8 copies of the same one).  Sometimes the attributes of
> the copies are slightly different (e.g. the background colour displayed
> in Outlook is changed).
> 
> I tried to follow (in imapd.log) who adds the "spam" to the calendar,
> and temporarily de-activated write access for those users, but
> apparently many of them seem to trigger this problem.
> 
> Is this a known problem?  In Toltec or in Kolab?  Any idea how I can
> solve this bug?  It is somewhat annoying to manually erase the
> duplicates manually every day...
> 
> Thanks,
> Albrecht.
> 
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users



From thomas at intevation.de  Tue Dec  2 18:27:01 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Tue, 2 Dec 2008 18:27:01 +0100
Subject: Kolab Security Issue 23 20081202 (clamav)
Message-ID: <20081202172701.GE20734.thomas@intevation.de>

Kolab Security Issue 23 20081202
================================

Package:              Kolab Server, ClamAV
Vulnerability:        various
Kolab Specific:       no
Dependent Packages:   none


Summary
~~~~~~~

Moritz Jodeit reports that ClamAV up to version 0.94 contains an
off-by-one heap overflow vulnerability in the code responsible for
parsing VBA project files. Successful exploitation could allow an
attacker to execute arbitrary code with the privileges of the `clamd'
process by sending an email with a prepared attachment.

Ilja Van Sprundel reported a denial-of-service vulnerability and an
unconfirmed possibility to run arbitrary code in ClamAV up to version
0.94.1 by sending malformed JPEG files.


Affected Versions
~~~~~~~~~~~~~~~~~

This affects versions of ClamAV up to version 0.94.1
Kolab Server 2.2.0 and previous prereleases are affected.
Kolab Server 2.1.0 and previous releases of the 2.1 branch are affected.
Kolab Server 2.0.4 and previous releases of the 2.0 branch are affected.


Fix
~~~

Upgrade to ClamAV 0.94.2.

The ClamAV source RPM for Kolab Server 2.2, 2.1 and 2.0
is available from the Kolab download mirrors as:
security-updates/20081202/clamav-0.94.2-20081202.src.rpm

A binary RPM for Kolab Server 2.1.0 (ix86 Debian GNU/Linux Sarge) is available:
security-updates/20081202/clamav-0.94.2-20081202.ix86-debian3.1-kolab.rpm

A binary RPM for Kolab Server 2.2.0 (ix86 Debian GNU/Linux Etch)
is available from:
security-updates/20081202/clamav-0.94.2-20081202_kolab.ix86-debian4.0-kolab.rpm

All other server versions: Please build from the src.rpm.


The mirrors are listed on http://kolab.org/mirrors.html
While the mirrors are catching up, you can also get the package via rsync:
# rsync -tvP rsync://rsync.kolab.org/kolab/server/security-updates/20081202/clamav-0.94.2-20081202.src.rpm .
# rsync -tvP rsync://rsync.kolab.org/kolab/server/security-updates/20081202/clamav-0.94.2-20081202.ix86-debian3.1-kolab.rpm .
# rsync -tvP rsync://rsync.kolab.org/kolab/server/security-updates/20081202/clamav-0.94.2-20081202.ix86-debian4.0-kolab.rpm .

MD5 sums:
bd4aaba0b5dc0c4c7349fd3418326534  clamav-0.94.2-20081202.src.rpm
4e1efcb88af5ab6538560be9ee618ca0  clamav-0.94.2-20081202.ix86-debian3.1-kolab.rpm
0fe61493cfc48dda972844e455867f8e  clamav-0.94.2-20081202.ix86-debian4.0-kolab.rpm


The package can be installed on your Kolab Server with

# /kolab/bin/openpkg rpm --rebuild clamav-0.94.2-20081202.src.rpm
# /kolab/bin/openpkg rpm \
  -Uvh /kolab/RPM/PKG/clamav-0.94.2-20081202.<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

For Kolab Server 2.0.4 you have to copy the new /kolab/etc/clamav/clamd.conf
to /kolab/etc/kolab/templates/clamd.conf.template so it will not be
overwritten by kolabconf. Do NOT copy this file with Kolab Server 2.1 or 2.2!


Details
~~~~~~~

http://sourceforge.net/project/shownotes.php?release_id=637952&group_id=86638
	ClamAV 0.94.1 release notes

http://lists.grok.org.uk/pipermail/full-disclosure/2008-November/065530.html
	Vulnerability description: ClamAV get_unicode_name() off-by-one buffer overflow

https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1239
	ClamAV bug tracker entry for above vulnerability (not yet publicly available)

http://sourceforge.net/project/shownotes.php?release_id=643134&group_id=86638
	ClamAV 0.94.2 release notes

http://www.securityfocus.com/bid/32555
https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1266
	ClamAV 'cli_check_jpeg_exploit' Function Malformed JPEG File Remote Denial Of Service Vulnerability


Timeline
~~~~~~~~
    20081016 Moritz Jodeit reports vulnerability to ClamAV vendor.
    20081103 ClamAV release 0.94.1.
    20081109 Moritz Jodeit publishes vulnerability fixed in 0.94.1.
    20081126 ClamAV release 0.94.2.
    20081201 Bugtraq ID 32555 published for problem fixed in 0.94.2.
    20081202 Kolab Server security advisory published.

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 206 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20081202/bb264847/attachment.bin

From aspineux at gmail.com  Wed Dec  3 05:52:53 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Wed, 3 Dec 2008 05:52:53 +0100
Subject: Why the use of SPF pointer is becoming more important
Message-ID: <71fe4e760812022052q1436049fgb015e9717f4f766f@mail.gmail.com>

Hi

I was thinking about the hard live of SPAMMER, becoming harder and harder ....

Because SPF is used more and more, SPAMMER will become forced to choose
unprotected SPF domain as sender of their spam!

Then the need of a kolab SPF aware will become more and more urgent !

Isn't it ?

Regards


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



From wrobel at pardus.de  Wed Dec  3 09:50:55 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 03 Dec 2008 09:50:55 +0100
Subject: Kolab-users Digest, Vol 57, Issue 37
In-Reply-To: <200812010852.14496.oszwald@web.de>
References: <mailman.3401.1227996238.2135.kolab-users@kolab.org>
	<200812010852.14496.oszwald@web.de>
Message-ID: <20081203095055.163613cm0hj85jzk@webmail.pardus.de>

Quoting Florian Oszwald <oszwald at web.de>:

> Am Samstag 29 November 2008 23:03:58 schrieb kolab-users-request at kolab.org:
>> Quoting Florian Oszwald <oszwald at web.de>:
>> > Hi all,
>> >
>> > I now have horde installed working together with kolab on opensuse 10.2.
>> >
>> > The problem is, that i get the message DB Error: not found everytime I
>> > log in on a new day or making a new entry in the calendar or in notes.
>> >
>> > In /var/log/horde/horde.log I do not get any useful information about
>> > this problem. On the internet I found, that it might be related to the
>> > SQL, but I am using it together with Kolab, so there is no need for sql,
>> > is there?
>>
>> Correct. In general there is no need for a database. If Horde gives  
>>  you this error the configuration provided by the package  
>> maintainers  is broken and you should submit a bug concerning the  
>> package.
>>
>> For newer Horde/Kolab installations you need a database if you want  
>> to  use SyncML. But it should be sufficient if this is based on  
>> sqlite and  I see it as a package maintainers task to provide a  
>> correctly  preconfigured database in that case.
>>
>> Cheers,
>>
>> Gunnar
>
> Hi Gunnar,
> thank you very much for your email.
> Would it be possible to somehow narrow it a little bit more down, so I can
> file the bug more exactly and help the package maintainer more precisely?

No, not really. From your report it is not clear to me which subsystem  
was configured to require a database and fails. It might be the alarms  
module but thats a guess.

As I do not have access to the native Kolab Server port you are using  
I'd suggest opening the bug in the unspecific form you reported it  
here and work with the port maintainer to get it more specific. The  
maintainer will know how Horde was configured and should be able to  
get more details in the discussion with you. Either the port  
maintainer is able to already fix the bug that way or he contacts  
Kolab or Horde upstream. That is the best way of handling these types  
of bugs in my eyes.

>
> Installing Kolab/horde with openpgk will not work for me due to limited
> bandwith and traffic.

Hm, I'd still guess that it is cheaper to invest into bandwith rather  
than investing days and weeks into bug fixing. I have been working for  
more than three years on a native Gentoo port and it is not nearly as  
good as the Kolab2/OpenPKG server ;)

Cheers,

Gunnar

>
> Maybe you can point me to something where to look at, and I will try it out.
>
> Regards,
> Florian
>
> _______________________________________________
> 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 <<
--------------------------------------------------------------------


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-users/attachments/20081203/90265e94/attachment.bin

From wrobel at pardus.de  Wed Dec  3 09:59:03 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 03 Dec 2008 09:59:03 +0100
Subject: Duplication of appointments in shared calendar
In-Reply-To: <1228211978l.3344l.2l@pc-adr2.lios-koeln.de>
References: <1228211978l.3344l.2l@pc-adr2.lios-koeln.de>
Message-ID: <20081203095903.17115b7id9jg7gcg@webmail.pardus.de>

Quoting Albrecht Dre? <albrecht.dress at lios-tech.com>:

> Hi,
>
> I have a *really* nasty problem with the duplication of appointments in
> a shared calendar.  I run a self-compiled Kolab 2.2.0 on Ubuntu
> 8.04/64.  My users (~35) use Outlook 2002/2003/2007 through the latest
> Toltec connector.
>
> The problem occurs on a shared calendar for which all users have write
> access.  Periodically, *all* appointments in this calendar get
> mysteriously duplicated, and in some cases they occur even more times
> (I saw up to 8 copies of the same one).  Sometimes the attributes of
> the copies are slightly different (e.g. the background colour displayed
> in Outlook is changed).
>
> I tried to follow (in imapd.log) who adds the "spam" to the calendar,
> and temporarily de-activated write access for those users, but
> apparently many of them seem to trigger this problem.
>
> Is this a known problem?  In Toltec or in Kolab?  Any idea how I can
> solve this bug?  It is somewhat annoying to manually erase the
> duplicates manually every day...

Kolab itself has no feature that would do automatic writes in a shared  
calendar. If Toltec is the *only* client accessing the shared folder  
I'd guess it is causing the problem.

Cheers,

Gunnar

>
> Thanks,
> Albrecht.
>
> _______________________________________________
> 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 <<
--------------------------------------------------------------------


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-users/attachments/20081203/68915672/attachment.bin

From wrobel at pardus.de  Wed Dec  3 10:04:05 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 03 Dec 2008 10:04:05 +0100
Subject: How-To activate RBL (Spamhaus), the SpamAssassin way
In-Reply-To: <49351C46.20007@netkult.eu>
References: <49351C46.20007@netkult.eu>
Message-ID: <20081203100405.69796lxmbl3r7u88@webmail.pardus.de>

Quoting Gregor Adamczyk <g.adamczyk at netkult.eu>:

> Halo, I have some trouble with activating SPAMHAUS RBL and another in
> Kolab 2.2.
>
> I don't really understand the working mechanism from amavisd-new.
>
> I read already some FAQ but this don't help me to understand the situation.
>
> In the FAQ: http://www.ijs.si/software/amavisd/#faq-spam
>
> I read this:
> Does SpamAssassin observe settings in its configuration file local.cf?
> SA does observe all settings in its configuration file, but not all of
> them have effect...
>
> I know that it is possible to activate RBL on two ways.
> With SpamAssassin or directly in Postfix.
>
> I think SpamAssassin is the better way, so I test this:
>
> change in:
> /kolab/etc/kolab/templates/local.cf.template
> score RCVD_IN_SBL 10
> score RCVD_IN_XBL 10
> score RCVD_IN_PBL 10
>
> change in:
> /kolab/etc/kolab/templates/amavisd.conf.template
> $sa_local_tests_only = 0;   # (default: false)
>
> then run:
> /kolab/sbin/kolabconf
>
> after request a SPAM test mail (nelson-sbl-test at crynwr.com) from spamhaus:
>
> read instruction here:
> http://www.spamhaus.org/sbl/howtouse.html
>
> I received the black listed mail without any higher score.
>
> I don't understand why, please help me to understand this...

If I remember correctly a spamassassin used with amavisd-new does  
ignore the local.cf and gets all its config from amavis. There might  
be exception or ways around this but I'd have to read up on the topic  
again to give a definite answer. I think there should be pointers if  
you google for the amavisd-new/spamassassin integration.

Cheers,

Gunnar

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


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-users/attachments/20081203/d201bb1a/attachment.bin

From kcaesar at hotmail.com  Wed Dec  3 10:54:46 2008
From: kcaesar at hotmail.com (kiser Caesar)
Date: Wed, 3 Dec 2008 10:54:46 +0100
Subject: connect calendar of other users with thunderbird
Message-ID: <BLU122-W507217E41CC9A940FCA83FA3030@phx.gbl>


Hello,


I want to know how can connect calendar of others users ? The only is to share it and syncing withsynckolab ?
Or there are an another way ?

Thank :)
_________________________________________________________________
T?l?phonez gratuitement ? tous vos proches avec Windows Live Messenger? !? T?l?chargez-le maintenant !
http://www.windowslive.fr/messenger/1.asp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081203/f03dce8f/attachment.html

From LHendricks at austinent.com  Wed Dec  3 19:24:50 2008
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Wed, 3 Dec 2008 12:24:50 -0600 
Subject: connect calendar of other users with thunderbird
Message-ID: <7907AE10BB50DD4F840E76527D27EF1902104FF5@entmail.domain.austinent.com>

As of Kolab 2.2-rc3 I believe you could use the Horde interface to subscribe
to it as an icalendar.  You will probably need to logon to horde and set the
permissions there, and then under manage calendars there is a subscription
URL.  There is also a lightbulb next to calendars that shows a subscription
url for icalendar style.  I'm not positive if the version of horde used in
2.2 is 2-way yet but I believe as of 2.2.1 it will be.  Or if it is not
2-way there may be something in the horde-wiki that can help make it so.  

 

Example icalendar subscription url: 

https://kolabserver.mycompany.com/horde/rpc.php/kronolith/username at kolabserv
er.mycompany.com.ics
<https://kolabserver.mycompany.com/horde/rpc.php/kronolith/username at kolabser
ver.mycompany.com.ics> 

 

Lucas

 

  _____  

From: kiser Caesar [mailto:kcaesar at hotmail.com] 
Sent: Wednesday, December 03, 2008 3:55 AM
To: kolab-users at kolab.org
Subject: connect calendar of other users with thunderbird

 

Hello,


I want to know how can connect calendar of others users ? The only is to
share it and syncing withsynckolab ?
Or there are an another way ?

Thank :)

  _____  

Votre correspondant a choisi Hotmail et profite d'un stockage quasiment
illimit?. Cr?ez un <http://www.windowslive.fr/hotmail/default.asp>  compte
Hotmail gratuitement !

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081203/f46e7d16/attachment.html

From LHendricks at austinent.com  Wed Dec  3 19:29:14 2008
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Wed, 3 Dec 2008 12:29:14 -0600 
Subject: cannot delete shared calendar with spaces in the name
Message-ID: <7907AE10BB50DD4F840E76527D27EF1902104FF6@entmail.domain.austinent.com>

Hello,

 

I have created some shared calendars in the horde admin interface that
included spaces in the name and they seem buggy.  I could not subscribe to
them via url and they will not let me delete them either through admin or
horde.  When I set them to delete in the admin interface they say "Folder
deleted, awaiting cleanup..." but then never delete and after cleanup runs
they're still there.

 

I'm only on a beta install and I will most likely do a clean install when
2.2.1 comes out so it's not an issue that needs much thought wasted on it (I
will just not use spaces in folder names in the future).   I just wanted to
check here to see if someone knows how to fix this off the top of their
heads or if it should be considered a feature. 

 

Lucas Hendricks

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081203/18595817/attachment.html

From ml at radoeka.nl  Wed Dec  3 20:29:25 2008
From: ml at radoeka.nl (Richard Bos)
Date: Wed, 3 Dec 2008 20:29:25 +0100
Subject: cannot delete shared calendar with spaces in the name
In-Reply-To: <7907AE10BB50DD4F840E76527D27EF1902104FF6@entmail.domain.austinent.com>
References: <7907AE10BB50DD4F840E76527D27EF1902104FF6@entmail.domain.austinent.com>
Message-ID: <200812032029.25636.ml@radoeka.nl>

Op Wednesday 03 December 2008 19:29:14 schreef Lucas Hendricks:
> I have created some shared calendars in the horde admin interface that
> included spaces in the name and they seem buggy. ?I could not subscribe to
> them via url and they will not let me delete them either through admin or
> horde. ?When I set them to delete in the admin interface they say "Folder
> deleted, awaiting cleanup..." but then never delete and after cleanup runs
> they're still there.
>
> ?
>
> I'm only on a beta install and I will most likely do a clean install when
> 2.2.1 comes out so it's not an issue that needs much thought wasted on it
> (I will just not use spaces in folder names in the future). ? I just wanted
> to check here to see if someone knows how to fix this off the top of their
> heads or if it should be considered a feature.


Does it help if you replace the space in the url with %20?

-- 
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.



From itsef-admin at brightsight.com  Thu Dec  4 11:11:56 2008
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Thu, 4 Dec 2008 11:11:56 +0100
Subject: Cannot get freebusy to work in Kontact
In-Reply-To: <200810081024.43359.itsef-admin@brightsight.com>
References: <200810081024.43359.itsef-admin@brightsight.com>
Message-ID: <200812041111.56971.itsef-admin@brightsight.com>

On Wednesday 8 October 2008 10:24:43 ITSEF Admin wrote:
> I'm trying to get freebusy to work in my own Kontact (enterprise35) - so
> far without luck.

No ideas, anyone? I still can't use freebusy. I *think* it might have 
something to do with the interaction Kontact<->kwallet, but that's just a 
hunch. My Kontact simply does not send out the username/password needed to 
retrieve the freebusy information - and it does not ask for one, either, no 
matter what I do... I'll include the original description below for 
completeness.

Regards,

Thomas


> Here's what I see so far:
>  > - We have several users for whom freebusy just works (same Kontact 
version 
> and no significant differences in korganizerrc, as far as I can see)
> - For those users, the reqests I can see on the server (apache log) include
> a login name
> - If I use a browser to get the freebusy information "manually", I get
> asked for a username and password. Once I supply them, I get the text.
> Hence, freebusy does indeed work correctly on the server.
> - In Settings -> Calendar -> Free/Busy -> Retrieve, I have set username and
> password - however, none of those seems to get used by my client. The
> username can be seen in korganizerrc, but it can never be seen in the
> serverlogs.
> - Restarting Kontact did not help
>
> Basically, it looks like "my" Kontact refuses to send the username/password
> I have entered when trying to retrieve the freebusy information.
> Unfortunately, I have absolutely no idea why, especially, as it seems to
> work for other users with the same Kontact version.
>
> I have seen the Wiki article on the topic, but that does not seem to have
> any clues. BTW: The Wiki article states that the URL for freebusy is
> supposed to be "https://my-domain.de/freebusy/%EMAIL%.ifb". Is this still
> correct for enterprise35? I'm asking 'cause all our users with working
> freebusy have "https://my-domain.de/freebusy/" in there - which is the way
> kolabwizard sets it.


-- 
==============================================================================
           Thomas Ribbrock, Team Leader IT-Team |   brightsight
           itsef-admin at brightsight.com          |   Delftechpark 1
           +31-15-2692529                       |   NL-2628XJ Delft



From wrobel at pardus.de  Fri Dec  5 09:35:54 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Fri, 05 Dec 2008 09:35:54 +0100
Subject: cannot delete shared calendar with spaces in the name
In-Reply-To: <7907AE10BB50DD4F840E76527D27EF1902104FF6@entmail.domain.austinent.com>
References: <7907AE10BB50DD4F840E76527D27EF1902104FF6@entmail.domain.austinent.com>
Message-ID: <20081205093554.63852r35wadl61wk@webmail.pardus.de>

Hi Lucas,

Quoting Lucas Hendricks <LHendricks at austinent.com>:

>   font-family: Arial;\">Hello,  font-family: Arial;\">    
> font-family: Arial;\">I have created some shared calendars in the
> horde admin interface that included spaces in the name and they
seem
> buggy.

In the horde admin interface? I guess you rather mean the web-admin, right?

> I could not subscribe to them via url and they will not let
> me delete them either through admin or horde.

How exactly do you try to delete it in horde? Did you give admin  
rights to the user trying to delete the shared folder?

> When I set them to
> delete in the admin interface they say "Folder deleted,
> awaiting cleanup..." but then never delete and after cleanup
> runs they're still there.

What kind of a cleanup run? Does your kolabd run? kolabd should be  
responsible for removing the folders.

>
>  font-family: Arial;\">   font-family: Arial;\">I'm only on a beta  
> install and I will most
> likely do a clean install when 2.2.1 comes out so it's not an issue
> that needs much thought wasted on it (I will just not use spaces in
> folder names in the future).   I just wanted to check here to see
if
> someone knows how to fix this off the top of their heads or if it
> should be considered a feature.

Deleting such folders works fine for me (albeit on a 2.2.1  
installation). I don't think we had some changes in that area though  
and I would expect it to also work on 2.2.0. I could check 2.2.0 also  
if required.

Cheers,

Gunnar

>
>  font-family: Arial;\">   style=\"font-size: 10pt; font-family:  
> Arial; color: blue;\">Lucas
> Hendricks

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

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-users/attachments/20081205/b6b531db/attachment.bin

From LHendricks at austinent.com  Fri Dec  5 20:40:11 2008
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Fri, 5 Dec 2008 13:40:11 -0600 
Subject: cannot delete shared calendar with spaces in the name
Message-ID: <7907AE10BB50DD4F840E76527D27EF1902105002@entmail.domain.austinent.com>

I was able to delete one shared folder with a space, and now I only have 1
left which seems to be a phantom shared folder which indicates as far as
deleting the folder: an isolated problem not related to the space in the
name.  

Retrieving an ics file via the subscription link does not work for shared
folders with a space in the name for me, though.  Using IE as a
troubleshooting tool to connect to the Debian 4.0 binary install of 2.2:

Shared folder name: mycal  
type: events
https://kolab.mydomain.com/horde/rpc.php/kronolith/shared.mycal.ics 
This works fine and prompts me to download the ics file through IE

Shared folder name: my calendar     
type: events
https://kolab.mydomain.com/horde/rpc.php/kronolith/shared.my%20calendar.ics
This gives a blank response with no file download prompt

I think I might have made the phantom folder during 2.2-rc3 and done an
upgrade from that to 2.2 which I could easily have done incorrectly to
prevent the issue (I might have marked it to delete then done the upgrade
before it ran the cleanup or something).  Since that is isolated to the one
phantom folder and I plan on doing a clean wipe and fresh install with 2.2.1
it probably doesn't need any more attention.  

Info for if you are just interested, though: folder appears in horde as:
[anonymous]shared.doc surgery

I cannot delete it while logged on to the horde as my only user account nor
as the manager logon, and it does not appear in shared folders in the
web-admin interface logged on as the default manager account.  I created a
maintainer account and administrator account, neither of which even has the
calendar show up as visible either in horde or the web-admin interface for
kolab.

Lucas

-----Original Message-----
From: Gunnar Wrobel [mailto:wrobel at pardus.de] 
Sent: Friday, December 05, 2008 2:36 AM
To: kolab-users at kolab.org
Subject: Re: cannot delete shared calendar with spaces in the name

Hi Lucas,

Quoting Lucas Hendricks <LHendricks at austinent.com>:

>   font-family: Arial;\">Hello,  font-family: Arial;\">    
> font-family: Arial;\">I have created some shared calendars in the
> horde admin interface that included spaces in the name and they
seem
> buggy.

In the horde admin interface? I guess you rather mean the web-admin, right?

> I could not subscribe to them via url and they will not let
> me delete them either through admin or horde.

How exactly do you try to delete it in horde? Did you give admin  
rights to the user trying to delete the shared folder?

> When I set them to
> delete in the admin interface they say "Folder deleted,
> awaiting cleanup..." but then never delete and after cleanup
> runs they're still there.

What kind of a cleanup run? Does your kolabd run? kolabd should be  
responsible for removing the folders.

>
>  font-family: Arial;\">   font-family: Arial;\">I'm only on a beta  
> install and I will most
> likely do a clean install when 2.2.1 comes out so it's not an issue
> that needs much thought wasted on it (I will just not use spaces in
> folder names in the future).   I just wanted to check here to see
if
> someone knows how to fix this off the top of their heads or if it
> should be considered a feature.

Deleting such folders works fine for me (albeit on a 2.2.1  
installation). I don't think we had some changes in that area though  
and I would expect it to also work on 2.2.0. I could check 2.2.0 also  
if required.

Cheers,

Gunnar

>
>  font-family: Arial;\">   style=\"font-size: 10pt; font-family:  
> Arial; color: blue;\">Lucas
> Hendricks

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

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
Kolab-users mailing list
Kolab-users at kolab.org
https://kolab.org/mailman/listinfo/kolab-users



From lists at oak-wood.co.uk  Sat Dec  6 11:59:34 2008
From: lists at oak-wood.co.uk (Chris Hastie)
Date: Sat, 06 Dec 2008 10:59:34 +0000
Subject: Installation problems on Ubuntu intrepid
Message-ID: <493A5B16.5050903@oak-wood.co.uk>

I'm having problems installing on ubuntu intrepid and would appreciate
any pointers.

First issue is that openpkg wouldn't compile with gcc 4.3. I've
installed gcc-4.2 and linked /usr/bin/gcc to the 4.2 binary and am now
able to get a lot further.

However, openldap fails to compile, with this:

getpeereid.c: In function 'getpeereid':
getpeereid.c:52: error: storage size of 'peercred' isn't known
make[2]: *** [getpeereid.o] Error 1

A bit of googling throws up this one line patch:

http://bugs.gentoo.org/attachment.cgi?id=156475&action=diff

I've applied this to the openldap source left lying around when the
install bombed out, run 'make' and and got past the error, so it looks
like the patch works.

But how do I apply a patch to the rpm before starting the install from
scratch again?

-- 
Chris



From oliv at gensys-net.eu  Mon Dec  8 16:04:55 2008
From: oliv at gensys-net.eu (Olivier)
Date: Mon, 08 Dec 2008 15:04:55 +0000
Subject: Kolab Live CD /USB
Message-ID: <493D3797.5020404@gensys-net.eu>

Hi,

I am pleased to introduce you the Cooperation-iws project.

Cooperation-iws is an Intranet Nomad Web Server. Intranet to decide when 
you want to be connected. Nomad to carry it in your pocket on USB key / 
hard drive.

Cooperation-iws have just been released in 0.7.0 version and now include 
a Kolab Live CD /USB release in the Intranet System flavors.


Cooperation-iws web is here : http://www.cooperation-iws.eu

Cooperation-iws short introduction is here: 
http://www.cooperation-iws.eu/CMS/wp-content/plugins/download-monitor/download.php?id=22

Cooperation-iws extended presentation is here: 
http://www.cooperation-iws.eu/CMS/wp-content/plugins/download-monitor/download.php?id=39


Mit freundlichen Gr?ssen,

Olivier



From support at toltec.co.za  Tue Dec  2 16:00:31 2008
From: support at toltec.co.za (Toltec Support)
Date: Tue, 2 Dec 2008 17:00:31 +0200
Subject: Duplication of appointments in shared calendar
In-Reply-To: <1228211978l.3344l.2l@pc-adr2.lios-koeln.de>
References: <1228211978l.3344l.2l@pc-adr2.lios-koeln.de>
Message-ID: <004001c9548e$bba790e0$32f6b2a0$@co.za>

Hi,

If all appointments duplicate in a folder it is one of two issues.

First possibility is that the main users PST is corrupted. Please run a
SCANPST.EXE on the PST file.

Second possibility is that the UID Validity of the mailbox on the IMAP4
server keeps changing. This can happen for a number of different reasons,
please have a look at your Cyrus log files.

Best regards

Support @ Toltec
Mobile: +27 (0)83 368 8557
Fax: +27 (0)12 998 4346
E-mail: support at toltec.co.za
Web: www.toltec.co.za


> -----Original Message-----
> From: Albrecht Dre? [mailto:albrecht.dress at lios-tech.com]
> Sent: Tuesday, December 02, 2008 12:00 PM
> To: Kolab Users List
> Cc: support at toltec.co.za
> Subject: Duplication of appointments in shared calendar
> 
> Hi,
> 
> I have a *really* nasty problem with the duplication of appointments in
> a shared calendar.  I run a self-compiled Kolab 2.2.0 on Ubuntu
> 8.04/64.  My users (~35) use Outlook 2002/2003/2007 through the latest
> Toltec connector.
> 
> The problem occurs on a shared calendar for which all users have write
> access.  Periodically, *all* appointments in this calendar get
> mysteriously duplicated, and in some cases they occur even more times
> (I saw up to 8 copies of the same one).  Sometimes the attributes of
> the copies are slightly different (e.g. the background colour displayed
> in Outlook is changed).
> 
> I tried to follow (in imapd.log) who adds the "spam" to the calendar,
> and temporarily de-activated write access for those users, but
> apparently many of them seem to trigger this problem.
> 
> Is this a known problem?  In Toltec or in Kolab?  Any idea how I can
> solve this bug?  It is somewhat annoying to manually erase the
> duplicates manually every day...
> 
> Thanks,
> Albrecht.



From toni.sunnari at comdate.se  Tue Dec  2 09:57:16 2008
From: toni.sunnari at comdate.se (Toni Sunnari)
Date: Tue, 2 Dec 2008 09:57:16 +0100
Subject: prerequisites kolab-server-2.2.0 on Fedora 10
Message-ID: <5586FE094C64FF4E96155847880E36F72A98@tanzania.sunnari.com>

Hi,
 
As the subject says: I would like to know the prerequisites for a kolab-server-2.2.0 installation on a fresh fedora 10 OS. I seem to get random gcc errors and I have tried several version of gcc. Do I need to install apache before attempting to install kolab? Do I need to install openpkg etc?
 
Best regards,
 
Toni
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081202/fcb50e28/attachment.html

From aspineux at gmail.com  Wed Dec 10 07:17:57 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Wed, 10 Dec 2008 07:17:57 +0100
Subject: prerequisites kolab-server-2.2.0 on Fedora 10
In-Reply-To: <5586FE094C64FF4E96155847880E36F72A98@tanzania.sunnari.com>
References: <5586FE094C64FF4E96155847880E36F72A98@tanzania.sunnari.com>
Message-ID: <71fe4e760812092217u43b4901fq7ffab98b751d3f4a@mail.gmail.com>

On Tue, Dec 2, 2008 at 9:57 AM, Toni Sunnari <toni.sunnari at comdate.se> wrote:
> Hi,
>
> As the subject says: I would like to know the prerequisites for a
> kolab-server-2.2.0 installation on a fresh fedora 10 OS. I seem to get
> random gcc errors and I have tried several version of gcc. Do I need to
> install apache before attempting to install kolab? Do I need to install
> openpkg etc?

No you don't need to install anything, except gcc.
I will make a try this weekend and make some report.

Regards.

>
> Best regards,
>
> Toni
>
>
> _______________________________________________
> 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 delonly at gmail.com  Wed Dec 10 16:31:12 2008
From: delonly at gmail.com (Del)
Date: Wed, 10 Dec 2008 16:31:12 +0100
Subject: Any news on version 2.2.1?
Message-ID: <1228923072.24317.3.camel@merom>

An update would be great Gunnar :)

Cheers,
Del



From itsef-admin at brightsight.com  Wed Dec 10 17:14:31 2008
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Wed, 10 Dec 2008 17:14:31 +0100
Subject: Cannot get freebusy to work in Kontact
In-Reply-To: <200812041111.56971.itsef-admin@brightsight.com>
References: <200810081024.43359.itsef-admin@brightsight.com>
	<200812041111.56971.itsef-admin@brightsight.com>
Message-ID: <200812101714.32022.itsef-admin@brightsight.com>

On Thursday 4 December 2008 11:11:56 ITSEF Admin wrote:
> No ideas, anyone? I still can't use freebusy. I *think* it might have
> something to do with the interaction Kontact<->kwallet, but that's just a
> hunch. My Kontact simply does not send out the username/password needed to
> retrieve the freebusy information - and it does not ask for one, either, no
> matter what I do... I'll include the original description below for
> completeness.

Still not working. I just tried the following:

- close kontact
- remove kwalletrc
- remove apps/kwallet
- change the freebusy section in korganizerrc to match that of an account 
where freebusy is working
- start kontact

No change. "My" kontact still does not send any username in its HTTP request, 
while the same kontact (i.e. on the same PC) in another (Linux-)account 
(hence with slightly different settings *somewhere*) does send the user name.

Does that ring a bell with someone? I'm really out of ideas...

Cheerio,

Thomas



From itsef-admin at brightsight.com  Wed Dec 10 17:46:10 2008
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Wed, 10 Dec 2008 17:46:10 +0100
Subject: Cannot get freebusy to work in Kontact
In-Reply-To: <200812101714.32022.itsef-admin@brightsight.com>
References: <200810081024.43359.itsef-admin@brightsight.com>
	<200812041111.56971.itsef-admin@brightsight.com>
	<200812101714.32022.itsef-admin@brightsight.com>
Message-ID: <200812101746.10487.itsef-admin@brightsight.com>

On Wednesday 10 December 2008 17:14:31 ITSEF Admin wrote:
[...]
> No change. "My" kontact still does not send any username in its HTTP
> request, while the same kontact (i.e. on the same PC) in another
> (Linux-)account (hence with slightly different settings *somewhere*) does
> send the user name.

Ok, it's definitely some problem in the interaction with KWallet. If I enter 
username *and* password in the freebusy config dialog (Settings-.Configure 
Calendar->Freebusy->Retrieve), it works. I know for certain that I used to 
get a KWallet dialog the first time I tried, upon which I could add the 
password to KWallet and be happy. However, for some odd reasons, Kontact 
seems to ignore KWallet completely right now - no idea why.

Cheerio,

Thomas
-- 
==============================================================================
           Thomas Ribbrock, Team Leader IT-Team |   brightsight
           itsef-admin at brightsight.com          |   Delftechpark 1
           +31-15-2692529                       |   NL-2628XJ Delft



From aspineux at gmail.com  Thu Dec 11 07:38:58 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Thu, 11 Dec 2008 07:38:58 +0100
Subject: Any news on version 2.2.1?
In-Reply-To: <1228923072.24317.3.camel@merom>
References: <1228923072.24317.3.camel@merom>
Message-ID: <71fe4e760812102238o24749110we78dc62b83c3fa8a@mail.gmail.com>

On Wed, Dec 10, 2008 at 4:31 PM, Del <delonly at gmail.com> wrote:
> An update would be great Gunnar :)

Yes give us some gifts, Santa :-)

>
> Cheers,
> Del
>
> _______________________________________________
> 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 Dec 11 21:28:50 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Thu, 11 Dec 2008 21:28:50 +0100
Subject: kolab user for samba access
Message-ID: <d53357b70812111228v494cff2aua40f7d3420e0677d@mail.gmail.com>

Hi all,
i need to make kolab user capable to access samba shares.
I'm trying to authenticate samba user against kolab openldap following
some tutorial found on the web, but any attempt fails.

somebody has a suggestion?

thanks in advance.



From aniedermeier at mac.com  Fri Dec 12 04:11:18 2008
From: aniedermeier at mac.com (Alexander Niedermeier)
Date: Fri, 12 Dec 2008 04:11:18 +0100
Subject: Issue with installing Kolab on Debian
Message-ID: <48941C7A-6FC1-4AC0-B35D-60138B4045E6@mac.com>

Hi,

when I try to install Kolab on a Debian system, I get the following  
errors:

server:/home/aniederm/ix86-debian3.1# sh obmtool kolab
---- boot/build server %kolab ----
obmtool:NOTICE: did not find openpkg/rpm executable. Checking/fetching  
binary sh.
OpenPKG 2.5-RELEASE Binary Bootstrap Package, version 2.5.4
Built for prefix /kolab on target platform ix86-debian3.1
++ hooking OpenPKG instance into system environment
++ fixating OpenPKG instance root directory "/kolab"
++ extracting OpenPKG binary distribution
++ installing OpenPKG binary distribution
./openpkg.bzip2: /lib/libc.so.6: version `GLIBC_2.3' not found  
(required by ./openpkg.bzip2)
./openpkg.bzip2: /lib/libc.so.6: version `GLIBC_2.1' not found  
(required by ./openpkg.bzip2)
./openpkg.bzip2: /lib/libc.so.6: version `GLIBC_2.0' not found  
(required by ./openpkg.bzip2)
++ fixating OpenPKG instance filesystem hierarchy
/kolab/RPM/PKG/openpkg-2.5.4-2.5.4.ix86-debian3.1-kolab.sh: line  
1009: /kolab/bin/openpkg: No such file or directory
++ post-processing OpenPKG bootstrap installation
/kolab/RPM/PKG/openpkg-2.5.4-2.5.4.ix86-debian3.1-kolab.sh: line  
1048: /kolab/lib/openpkg/rpmdb: No such file or directory
cat: /kolab/etc/openpkg/platform: No such file or directory
/kolab/RPM/PKG/openpkg-2.5.4-2.5.4.ix86-debian3.1-kolab.sh: line  
1138: /kolab/lib/openpkg/rpmtool: No such file or directory
obmtool:ERROR: bootstrapping failed

I tried with Kolab 2.1 on Sarge and 2.2 on Etch. Same issue.

What am I missing ?

Thanks,

Alex



From albrecht.dress at lios-tech.com  Fri Dec 12 08:46:41 2008
From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=)
Date: Fri, 12 Dec 2008 08:46:41 +0100
Subject: kolab user for samba access
In-Reply-To: <d53357b70812111228v494cff2aua40f7d3420e0677d@mail.gmail.com>
	(from devgioiatech@gmail.com on Thu Dec 11 21:28:50 2008)
References: <d53357b70812111228v494cff2aua40f7d3420e0677d@mail.gmail.com>
Message-ID: <1229068001l.6902l.0l@pc-adr2.lios-koeln.de>

Am 11.12.2008 21:28:50 schrieb(en) Antonio Straziota:
> i need to make kolab user capable to access samba shares. I'm trying  
> to authenticate samba user against kolab openldap following some  
> tutorial found on the web, but any attempt fails.

Did you try  
<http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy>?   
Works nicely for me...

Hth,
Albrecht.



From thomas at intevation.de  Fri Dec 12 10:42:20 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 12 Dec 2008 10:42:20 +0100
Subject: Any news on version 2.2.1?
In-Reply-To: <71fe4e760812102238o24749110we78dc62b83c3fa8a@mail.gmail.com>
References: <1228923072.24317.3.camel@merom>
	<71fe4e760812102238o24749110we78dc62b83c3fa8a@mail.gmail.com>
Message-ID: <20081212094220.GA9353.thomas@intevation.de>

* Alain Spineux <aspineux at gmail.com> [20081211 07:39]:
> On Wed, Dec 10, 2008 at 4:31 PM, Del <delonly at gmail.com> wrote:
> > An update would be great Gunnar :)
> 
> Yes give us some gifts, Santa :-)

I hope to get 2.2.1-beta1 out of the door today.

Regards,
Thomas Arendsen Hein

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



From t.nintemann at medial-networks.de  Fri Dec 12 14:28:00 2008
From: t.nintemann at medial-networks.de (Thomas Nintemann)
Date: Fri, 12 Dec 2008 14:28:00 +0100
Subject: find out user deleted
Message-ID: <200812121428.00379.t.nintemann@medial-networks.de>

Hi all,

Small question...

Is there a way to find out what user deleted a specific folder on the kolab 
server?

Thanks
Thomas



From thomas at intevation.de  Fri Dec 12 20:18:15 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 12 Dec 2008 20:18:15 +0100
Subject: Kolab Server 2.2.1 Beta 1
Message-ID: <20081212191815.GA21528.thomas@intevation.de>

Hi!

I just uploaded Kolab Server 2.2.1-beta1 which contains a new
version of the web client (Horde), restructured packages and many
important fixes to the last release. Please make sure to follow
the upgrade instructions in 1st.README, because there have been
some changes in the LDAP schema.

|  This is a beta release and therefore not yet recommended
|  to be used in production environments!

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

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

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

All files updated since 2.2.0 are available in the directory
server/development-2.2/20081212-since-20080711/

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.

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 --------------
Kolab Server 2.2 Install and Upgrade Information
================================================
(Version 20081212, Kolab Server 2.2.1-beta1)

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 kolab-webclient" 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 kolab-fbview".

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/sbin/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.0 to 2.2.1-beta1
---------------------------------

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

1. The Kolab server must be stopped:

    # /kolab/bin/openpkg rc all stop

2. Save the current LDAP data:

   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.2.0.ldif

3. Start the standard upgrade:
   (as described in the General update instructions)

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

4. /kolab/etc/kolab/kolab.conf will be saved as kolab.conf.rpmsave,
   please move it back to the original name:

   # cd /kolab/etc/kolab && mv kolab.conf.rpmsave kolab.conf

5. Look at *.conf.rpmsave files in the subdirectories of /kolab/etc/,
   transfer your changes and remove these files.
   (as described in the General update instructions)

6. Before starting the LDAP server the database must be restored from
   the ldif (with Horde preferences filtered out, since these are now
   stored in files):

   # rm /kolab/var/openldap/openldap-data/*
   # /kolab/bin/awk '!/^ / {ok=1;}
      /^objectClass: horde(Person|Group)$/ {ok=0;}
      /^([a-z]*Prefs|turba(Contact|Members|PGPPublicKey|Type)):/ {ok=0;}
      {if(ok) print;}' kolab-2.2.0.ldif | /kolab/sbin/slapadd

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


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/regenerate.php

As this will show the manager's password on the command line, you can
alternatively open https://yourserver.example.com/freebusy/regenerate.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 stopped:

    # /kolab/bin/openpkg rc all stop

2.  Save the current LDAP data:

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

    - Compiling openpkg-20071227-20071227 does not work with gcc 4.3, e.g.
      on Debian/lenny. As a workaround you can install the gcc-4.2 package,
      but you have to make sure that "gcc" calls this version. If your system
      uses a symbolic link /usr/bin/gcc -> gcc-4.3 you can execute:

        ln -sf gcc-4.2 /usr/bin/gcc

      "gcc --version" should report 4.2.x now. See kolab/issue2871
      (openpkg-20071227-20071227 does not compile with gcc 4.3) for details.

    - 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/sbin/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.97 2008/12/12 18:00:35 thomas Exp $
-------------- next part --------------
Kolab Server 2.2 Release Notes
==============================
(Version 20081212, Kolab Server 2.2.1-beta1)

For upgrading and installation instructions, please refer to
the 1st.README file in the package directory.


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.0 and 2.2.1-beta-1

    - apache-2.2.10-20081111

	New upstream version, fixes various security issues.

    - apache-php-5.2.8-20081209_kolab

	New upstream version, fixes various security issues.

	Added sqlite2 support for SyncML support in kolab-webclient.

    - bzip2-1.0.5-20080318

	New upstream version, fixes CVE-2008-1372 (denial of service)

    - clamav-0.94.2-20081212

	New upstream version, fixes various security issues.

	kolab/issue765  (openpkg "junk" warnings)

    - gawk-3.1.6-20080101

	New package, build (not runtime) dependency of sqlite.

    - gmp-4.2.2-20080101_kolab

	kolab/issue2928 (gmp-4.2.2-20080101 does not compile on Debian
	                 lenny/amd64)

    - Horde_iCalendar-0.1.0-20081209

	kolab/issue3284 (Webclient or resmgr might send invitations that Outlook
	                 2003 does not understand (unquoted CN with Umlauts))

    - Kolab_Filter-0.1.3-20081212

	A new package replacing kolab-filter
	(from http://pear.horde.org/index.php?package=Kolab_Filter)

	Added LDA (dovecot) backend.

	kolab/issue839  (problem when kolabHomeServer is missing)
	kolab/issue3074 (Freebusy trigger fails for other users's calenders.)
	kolab/issue3208 (Free/Busy list is always empty)
	kolab/issue3256 (resmgr responses should reflect server revision in
	                 PRODID)
	kolab/issue3260 (kolabfilter does not allow empty sender (and
	                 therefore MAILER-DAEMON))
	kolab/issue3289 (resmgr dies when it should accept, but has
	                 not Calender folder access) - only partial fix

    - Kolab_Format-1.0.0-20081212

	New package
	(from http://pear.horde.org/index.php?package=Kolab_Format)

    - Kolab_FreeBusy-0.1.2-20081212

	A new package replacing kolab-freebusy
	(from http://pear.horde.org/index.php?package=Kolab_FreeBusy)

	Fixed handling of extended free/busy information.

	Fixed identification of the corresponding free/busy server.

	kolab/issue3208 (Free/Busy list is always empty)
	kolab/issue3256 (resmgr responses should reflect server revision in
	                 PRODID)

    - Kolab_Server-0.2.0.20081114-20081114

	New package
	(from http://pear.horde.org/index.php?package=Kolab_Server)

    - Kolab_Storage-0.3.0-20081205

	New package
	(from http://pear.horde.org/index.php?package=Kolab_Storage)

    - kolabd-2.2.1-20081212

	Added configuration option in resmgr.conf for local delivery
	backend.  (Makes it possible to activate the new LDA backend)

	Activated sqlite support in PHP.

	Updated the configuration for the newer Kolab_Filter package.

	kolab/issue765  (openpkg "junk" warnings)
	kolab/issue936  (kolabquotawarn: system cron used, and firing when
	                 server stopped)
	kolab/issue1310 (kolabquotawarn runs via cron before server was
	                 bootstrapped)
	kolab/issue1755 (syncrepl support (for OpenLDAP >=2.4.6))
	kolab/issue2351 (horde doesn't present attachment stuff while compose
	                 a message)
	kolab/issue2440 (Installing binary packages of 2.2 fails without Horde)
	kolab/issue2446 (Make the used syslog facility configureable (kolabd,
	                 kolabconf))
	kolab/issue2550 (kolabconf should make some others postfix maps)
	kolab/issue2910 (obsolete definition of schemacheck in slapd.conf)
	kolab/issue2911 (Change comments around the idletimeout definiton
	                 in the file templates/slapd.conf.template.in)
	kolab/issue2961 (added smtpd_sasl_authenticated_header = yes for
	                 simpler authorization)
	kolab/issue2994 (Duplicated kolab.conf files in cvs, one should
	                 be removed)
	kolab/issue3005 (Remove specific TLSCertificate code by using new
	                 bootstrap_config conditional in slapd.conf.template)
	kolab/issue3006 (Surround the horde schema include in
	                 slapd.conf.template with @@@ conditionals)
	                 Remark: this actually added only the code that allows
	                 to use @@@if exists(<file)@@@ inside a config file
	kolab/issue3031 (Make kolab.globals readonly)
	kolab/issue3224 (perl-kolab has been restructured)
	kolab/issue3262 (web admin: versions page needs to be updated for CVS
	                 HEAD)
	kolab/issue3298 (kolab2.schema uses wrong enterprise number in some
	                 attributes)

    - kolab-fbview-1.2.0-20081212

	A new package replacing the older horde-* packages.

	kolab/issue765  (openpkg "junk" warnings)

    - kolab-webadmin-2.2.1-20081212

	Added acknowledgments for OpenSSL and PHP.

	kolab/issue765  (openpkg "junk" warnings)
	kolab/issue2596 (Kolab's login page title is not bookmark friendly)
	kolab/issue3230 (opportunity to delete freebusy value)
	kolab/issue3262 (web admin: versions page needs to be updated for CVS
	                 HEAD)

    - kolab-webclient-1.2.0-20081212

	A new package replacing the older horde-* packages.

	kolab/issue765  (openpkg "junk" warnings)
	kolab/issue614  (Events from deleted/renamed calendar folder
	                 still show up in free/busy list)
	kolab/issue2249 ([horde/kronolith] Kronolith is unable to
	                 trigger a free/busy update on a folder rename)
	kolab/issue3037 (Free/Busy List interaction for Horde broken)
	kolab/issue3205 (FB in horde while creating events)
	kolab/issue3241 (Horde: Can't accept invitation)
	kolab/issue3243 (Store web client user preferences in files, not in
	                 LDAP)
	kolab/issue3284 (Webclient or resmgr might send invitations that Outlook
	                 2003 does not understand (unquoted CN with Umlauts))
	kolab/issue3292 (Sharing Default Groupware Resources does not work in
	                 Webclient)

    - openldap-2.3.43-20081212

	kolab/issue765  (openpkg "junk" warnings)
	kolab/issue2902 (OpenLDAP/slapd: CVE-2008-2952 remote denial of
	                 service)
	kolab/issue3302 (Kolab fails to build on Ubuntu 8.10 (Intrepid Ibex))

    - perl-kolab-2.2.1-20081212

	kolab_bootstrap: Quote s[l]urpd to prevent shell expansion.

	template META: RUNONCHANGE is now triggered when creating a file
	and is now also catching special config files (postfix, slapd, ...)

	template META: warning for incorrect keys

	template META: support to define the comment character

	kolab/issue765  (openpkg "junk" warnings)
	kolab/issue1671 (Improving the warning about kolab templates within
	                 configuration files)
	kolab/issue1755 (syncrepl support (for OpenLDAP >=2.4.6))
	kolab/issue2981 (kolab_bootstrap: re-use kolabconf code to read the
	                 config file)
	kolab/issue3006 (Surround the horde schema include in
	                 slapd.conf.template with @@@ conditionals)
	                 Remark: this actually added only the code that allows
	                 to use @@@if exists(<file)@@@ inside a config file
	kolab/issue3152 (keep syncrepl cookie on disk between sessions)
	kolab/issue3224 (perl-kolab has been restructured)

    - php-5.2.8-20081209_kolab

	New upstream version, fixes various security issues.

	Added full sqlite support.

    - php-smarty-2.6.20-20081212

	New upstream version.

	kolab/issue765  (openpkg "junk" warnings)
	kolab/issue2559 (CVE-2008-1066: php-smarty needs to be upgraded)

    - sqlite-3.6.4-20081212

	New package, required by the kolab-webclient.
	(includes sqlite 3.6.4 and sqlite 2.8.17)

	kolab/issue765  (openpkg "junk" warnings)


    Packages in the OpenPKG based Kolab server release:

    - Kolab packages:

      Removed:

	PEAR-Mail_Mime-1.3.1-1
	PEAR-Net_IMAP-1.1.0beta1-1
	PEAR-Net_Sieve-1.1.5-1
	fbview-horde-3.2_rc3-20080605
	fbview-kronolith-2.2_rc2-20080710
	horde-framework-kolab-3.2_rc3-20080405
	horde-imp-kolab-4.2_rc3-20080710
	horde-ingo-kolab-1.2_rc2-20080710
	horde-kolab-3.2_rc3-20080707
	horde-kolab-client-0.99-20080405
	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
	kolabconf-2.2.0-20080709
	php-channel-horde-1.0-1
	php-kolab-2.2.0-20080711

      Added:

	Horde_Argv-0.1.0-20081209
	Horde_Auth-0.1.1-20081209
	Horde_Browser-0.0.2-20081209
	Horde_CLI-0.0.2-20081209
	Horde_Cache-0.0.2-20081209
	Horde_Cipher-0.0.2-20081209
	Horde_DOM-0.1.0-20081209
	Horde_DataTree-0.0.3-20081209
	Horde_Date-0.1.0-20081209
	Horde_Framework-0.0.2-20081209
	Horde_Group-0.1.0-20081209
	Horde_History-0.0.2-20081209
	Horde_LDAP-0.0.2-20081209
	Horde_MIME-0.0.2-20081209
	Horde_NLS-0.0.2-20081209
	Horde_Perms-0.1.0-20081209
	Horde_Secret-0.0.2-20081209
	Horde_Serialize-0.0.2-20081209
	Horde_SessionObjects-0.0.2-20081209
	Horde_Util-0.1.0-20081209
	Horde_iCalendar-0.1.0-20081209
	Kolab_Filter-0.1.3-20081212
	Kolab_Format-1.0.0-20081212
	Kolab_FreeBusy-0.1.2-20081212
	Kolab_Server-0.2.0.20081114-20081114
	Kolab_Storage-0.3.0-20081205
	PEAR-Horde-Channel-1.0-20081210
	PEAR-Mail_mimeDecode-1.5.0-20081209
	PEAR-PHPUnit-Channel-1.0-20081012
	PHPUnit-3.3.3-1
	kolab-fbview-1.2.0-20081212
	kolab-webclient-1.2.0-20081212
	sqlite-3.6.4-20081212

      Updated:

	PEAR-HTTP_Request-1.4.3-1
	PEAR-Log-1.11.2-1
	PEAR-Net_SMTP-1.3.1-1
	PEAR-Net_Socket-1.0.9-1
	clamav-0.94.2-20081212
	kolab-webadmin-2.2.1-20081212
	kolabd-2.2.1-20081212
	openldap-2.3.43-20081212
	perl-kolab-2.2.1-20081212
	php-smarty-2.6.20-20081212

      Unchanged:

	PEAR-Auth_SASL-1.0.2-1
	PEAR-Date-1.4.7-1
	PEAR-Mail-1.1.14-1
	PEAR-Net_LMTP-1.0.1-1
	PEAR-Net_URL-1.0.15-1

    - OpenPKG packages:

      Added:

	gawk-3.1.6-20080101

      Updated:

	apache-2.2.10-20081111
	apache-php-5.2.8-20081209_kolab
	bzip2-1.0.5-20080318
	gmp-4.2.2-20080101_kolab
	php-5.2.8-20081209_kolab

      Unchanged:

	amavisd-2.5.3-20080101
	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
	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
	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
	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-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.348 2008/12/12 18:05:34 thomas Exp $
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 206 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20081212/7d077f3f/attachment.bin

From wrobel at pardus.de  Sat Dec 13 21:51:25 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sat, 13 Dec 2008 21:51:25 +0100
Subject: Installation problems on Ubuntu intrepid
In-Reply-To: <493A5B16.5050903@oak-wood.co.uk>
References: <493A5B16.5050903@oak-wood.co.uk>
Message-ID: <20081213215125.35776m9qoap4a204@webmail.pardus.de>

Quoting Chris Hastie <lists at oak-wood.co.uk>:

> I'm having problems installing on ubuntu intrepid and would appreciate
> any pointers.
>
> First issue is that openpkg wouldn't compile with gcc 4.3. I've
> installed gcc-4.2 and linked /usr/bin/gcc to the 4.2 binary and am now
> able to get a lot further.
>
> However, openldap fails to compile, with this:
>
> getpeereid.c: In function 'getpeereid':
> getpeereid.c:52: error: storage size of 'peercred' isn't known
> make[2]: *** [getpeereid.o] Error 1
>
> A bit of googling throws up this one line patch:
>
> http://bugs.gentoo.org/attachment.cgi?id=156475&action=diff
>
> I've applied this to the openldap source left lying around when the
> install bombed out, run 'make' and and got past the error, so it looks
> like the patch works.
>
> But how do I apply a patch to the rpm before starting the install from
> scratch again?

You would need to modify the spec file of the rpm. You can find it in  
the Kolab CVS tree. But in general this is a complex procedure as you  
will need to know how to generate the new package on OpenPKG.

You could also try to use the OpenLDAP package from the newer Kolab  
Server 2.2.1 beta1. This is OpenLDAP-2.4.43 and it might already have  
the fix you referred to.

Cheers,

Gunnar

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



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


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.



From wrobel at pardus.de  Sat Dec 13 22:33:15 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sat, 13 Dec 2008 22:33:15 +0100
Subject: find out user deleted
In-Reply-To: <200812121428.00379.t.nintemann@medial-networks.de>
References: <200812121428.00379.t.nintemann@medial-networks.de>
Message-ID: <20081213223315.21094gvi6jal67sw@webmail.pardus.de>

Quoting Thomas Nintemann <t.nintemann at medial-networks.de>:

> Hi all,
>
> Small question...
>
> Is there a way to find out what user deleted a specific folder on the kolab
> server?

You should have the deletion event in the log. And I believe it should  
be possible to connect the process number of the imapd listed in that  
line with the most recent login on that process number. Just a guess.  
I never tried myself.

Cheers,

Gunnar

>
> Thanks
> Thomas
>
> _______________________________________________
> 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 <<
--------------------------------------------------------------------


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-users/attachments/20081213/2281d072/attachment.bin

From thomas at intevation.de  Sun Dec 14 12:46:46 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Sun, 14 Dec 2008 12:46:46 +0100
Subject: Installation problems on Ubuntu intrepid
In-Reply-To: <20081213215125.35776m9qoap4a204@webmail.pardus.de>
References: <493A5B16.5050903@oak-wood.co.uk>
	<20081213215125.35776m9qoap4a204@webmail.pardus.de>
Message-ID: <20081214114646.GB3408.thomas@intevation.de>

* Gunnar Wrobel <wrobel at pardus.de> [20081213 21:51]:
> You could also try to use the OpenLDAP package from the newer Kolab  
> Server 2.2.1 beta1. This is OpenLDAP-2.4.43 and it might already have  
> the fix you referred to.

It has, see https://www.intevation.de/roundup/kolab/issue3302
(or the 2.2.1-beta1 release notes)

Regards,
Thomas Arendsen Hein

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



From thomas at intevation.de  Sun Dec 14 12:48:46 2008
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Sun, 14 Dec 2008 12:48:46 +0100
Subject: find out user deleted
In-Reply-To: <20081213223315.21094gvi6jal67sw@webmail.pardus.de>
References: <200812121428.00379.t.nintemann@medial-networks.de>
	<20081213223315.21094gvi6jal67sw@webmail.pardus.de>
Message-ID: <20081214114846.GC3408.thomas@intevation.de>

* Gunnar Wrobel <wrobel at pardus.de> [20081213 22:33]:
> Quoting Thomas Nintemann <t.nintemann at medial-networks.de>:
> >Is there a way to find out what user deleted a specific folder on the kolab
> >server?
> 
> You should have the deletion event in the log. And I believe it should be possible to connect the 
> process number of the imapd listed in that line with the most recent login on that process number. 
> Just a guess. I never tried myself.

Correct guess, I often did it exactly the way you described.
(You'll find many deletion events, one for each mail contained in
the folder)

Regards,
Thomas Arendsen Hein

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 206 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20081214/3859ba02/attachment.bin

From albrecht.dress at lios-tech.com  Sun Dec 14 16:04:46 2008
From: albrecht.dress at lios-tech.com (Albrecht =?iso-8859-1?b?RHJl3w==?=)
Date: Sun, 14 Dec 2008 16:04:46 +0100
Subject: Kolab Server 2.2.1 Beta 1
In-Reply-To: <20081212191815.GA21528.thomas@intevation.de> (from
	thomas@intevation.de on Fri Dec 12 20:18:15 2008)
Message-ID: <1229267086.5137.0@antares>

Am 12.12.08 20:18 schrieb(en) Thomas Arendsen Hein:
> I just uploaded Kolab Server 2.2.1-beta1 which contains a new
> version of the web client (Horde), restructured packages and many
> important fixes to the last release.

Cool - I look forward to try it (and hopefully it resolves all the  
issues I have with 2.2.0 ;-)

------quoted attachment "1st.README"-----
[snip]
> 6. Before starting the LDAP server the database must be restored from  
> the ldif (with Horde preferences filtered out, since these are now  
> stored in files):

Is there a tool to migrate the Horde prefs from LDAP to the files?  I  
really dislike the idea to do that manually for ~35 users (in  
particular I convinced them to use Horde to manage their mail filters,  
and they are probably going to *kill* me if I tell them they have to do  
the same work again).  Is there any documentation around about the file  
structure of the new prefs, and where/how they are stored?  I would be  
willing to contribute such a tool if it doesn't exist yet.

This is also related to extension I reported in issue #3035, btw, which  
seems not to be part of this release.  Do you think it will be part of  
2.2.1 final?  Otherwise, I will of course try to upgrade the patch  
myself.

------quoted attachment "release-notes.txt"------
If I may "nag" about a missing patch in the release notes - Horde's  
#3050 (and the apparently related #3236) are still open, and they are  
*blockers* for me, though easy to fix IMHO...

Thanks a lot to everyone involved for providing this nice software  
package!

Cheers, Albrecht.



From wrobel at pardus.de  Sun Dec 14 16:53:06 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sun, 14 Dec 2008 16:53:06 +0100
Subject: Kolab Server 2.2.1 Beta 1
In-Reply-To: <1229267086.5137.0@antares>
References: <1229267086.5137.0@antares>
Message-ID: <20081214165306.20982s3c7yods000@webmail.pardus.de>

Quoting Albrecht Dre? <albrecht.dress at lios-tech.com>:

> Am 12.12.08 20:18 schrieb(en) Thomas Arendsen Hein:
>> I just uploaded Kolab Server 2.2.1-beta1 which contains a new
>> version of the web client (Horde), restructured packages and many
>> important fixes to the last release.
>
Hi Albrecht,

> Cool - I look forward to try it (and hopefully it resolves all the
> issues I have with 2.2.0 ;-)
>
> ------quoted attachment "1st.README"-----
> [snip]
>> 6. Before starting the LDAP server the database must be restored from
>> the ldif (with Horde preferences filtered out, since these are now
>> stored in files):
>
> Is there a tool to migrate the Horde prefs from LDAP to the files?  I
> really dislike the idea to do that manually for ~35 users (in
> particular I convinced them to use Horde to manage their mail filters,
> and they are probably going to *kill* me if I tell them they have to do
> the same work again).  Is there any documentation around about the file
> structure of the new prefs, and where/how they are stored?  I would be
> willing to contribute such a tool if it doesn't exist yet.

Would be great!

It should actually not be too hard to write a tool if you use the  
standard "Prefs" module from Horde  
(http://cvs.horde.org/framework/Prefs/). You will need to initiate it  
once with the standard "kolab" driver backend, read and serialize the  
prefernces of each user and pipe them back into the preferences  
system, this time using the "file" driver.

>
> This is also related to extension I reported in issue #3035, btw, which
> seems not to be part of this release.  Do you think it will be part of
> 2.2.1 final?  Otherwise, I will of course try to upgrade the patch
> myself.

As I mentioned in that issue I cannot use the patch as you provided it  
at the moment. It is a good idea in general but for structural reasons  
such a functionality belongs into the Kolab_Server package.  
Specifically into  
http://cvs.horde.org/framework/Kolab_Server/lib/Horde/Kolab/Session.php.

Your initHorde() function should be added in the initial session setup  
(function Horde_Kolab_Session()). And it needs to use the standard  
preferences setup in order to inject the configurations into the  
preferences system. You hardcoded the injection into LDAP. If you  
place it into the Session manager and just use the general Preferences  
interface you will be able to initiate the Preference whatever backend  
driver is being used ("ldap", "file", or "kolab_imap").

I'm writing this so that if you invest the effort in updating it it  
could be really added directly.

>
> ------quoted attachment "release-notes.txt"------
> If I may "nag" about a missing patch in the release notes - Horde's
> #3050 (and the apparently related #3236) are still open, and they are
> *blockers* for me, though easy to fix IMHO...

Both should be fixed in the newer release. I probably should have  
marked them as such in the release-notes.txt when I set both issues to  
"testing". I missed that because I did not need to do anything for  
them. They have been fixed in the upstream release anyway so all they  
need are some testing. I'm pretty certain Thomas will add them to the  
release-notes.txt ones they have been checked and move to state  
"resolved".

Cheers,

Gunnar

>
> Thanks a lot to everyone involved for providing this nice software
> package!
>
> Cheers, Albrecht.
>
> _______________________________________________
> 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 <<
--------------------------------------------------------------------


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-users/attachments/20081214/0d79ef67/attachment.bin

From wrobel at pardus.de  Sun Dec 14 19:35:08 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sun, 14 Dec 2008 19:35:08 +0100
Subject: Beta-1 available on EC2 (was: Re: Kolab Server 2.2.1 Beta 1)
In-Reply-To: <20081212191815.GA21528.thomas@intevation.de>
References: <20081212191815.GA21528.thomas@intevation.de>
Message-ID: <20081214193508.913233igfa2v9ps0@webmail.pardus.de>

Quoting Thomas Arendsen Hein <thomas at intevation.de>:

> Hi!
>
> I just uploaded Kolab Server 2.2.1-beta1 which contains a new
> version of the web client (Horde), restructured packages and many
> important fixes to the last release. Please make sure to follow
> the upgrade instructions in 1st.README, because there have been
> some changes in the LDAP schema.
>
> |  This is a beta release and therefore not yet recommended
> |  to be used in production environments!

Anyone who wants to do a quick test of the new beta without doing any  
harm to existing systems can simply run a test machine on Amazons EC2  
cloud:

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

The image (AMI) is called "ami-4748ac2e".

The only difference to the older versions: You need to run a "chmod  
777 /tmp" after bootstrapping the server to get the Kolab web client  
to work. I know why this changed but I still need to check if I can  
fix it.

Cheers,

Gunnar

>
> Again many thanks to all the people who helped with this!
>
> Documentation and OpenPKG source packages will soon be available in
> the directory server/beta/kolab-server-2.2.1-beta-1/ of the mirrors
> listed on http://kolab.org/mirrors.html
> for example:
> http://ftp.gwdg.de/pub/linux/kolab/server/beta/kolab-server-2.2.1-beta-1/
>  ftp://ftp.gwdg.de/pub/linux/kolab/server/beta/kolab-server-2.2.1-beta-1/
>
> rsync://rsync.kolab.org/kolab/RSYNC.txt explains how to get (or
> mirror) the files via rsync.
>
> All files updated since 2.2.0 are available in the directory
> server/development-2.2/20081212-since-20080711/
>
> 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.
>
> 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
>



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


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-users/attachments/20081214/552e4008/attachment.bin

From albrecht.dress at lios-tech.com  Sun Dec 14 19:44:23 2008
From: albrecht.dress at lios-tech.com (Albrecht =?iso-8859-1?b?RHJl3w==?=)
Date: Sun, 14 Dec 2008 19:44:23 +0100
Subject: Kolab Server 2.2.1 Beta 1
In-Reply-To: <20081214165306.20982s3c7yods000@webmail.pardus.de> (from
	wrobel@pardus.de on Sun Dec 14 16:53:06 2008)
Message-ID: <1229280263.5288.0@antares>

Hi Gunnar:

Am 14.12.08 16:53 schrieb(en) Gunnar Wrobel:
> It should actually not be too hard to write a tool if you use the  
> standard "Prefs" module from Horde  
> (http://cvs.horde.org/framework/Prefs/). You will need to initiate it  
> once with the standard "kolab" driver backend, read and serialize the  
> prefernces of each user and pipe them back into the preferences  
> system, this time using the "file" driver.

Thanks for that hint - I have *no* experience with php, but a few extra  
days of vacation over xmas, so I should be able to have something at  
the beginning of January at the latest, so stay tuned.  Is it ok to  
open an issue for that once I have something?

> As I mentioned in that issue I cannot use the patch as you provided  
> it at the moment. It is a good idea in general but for structural  
> reasons such a functionality belongs into the Kolab_Server package.  
> Specifically into  
> http://cvs.horde.org/framework/Kolab_Server/lib/Horde/Kolab/Session.php.
> 
> Your initHorde() function should be added in the initial session  
> setup (function Horde_Kolab_Session()). And it needs to use the  
> standard preferences setup in order to inject the configurations into  
> the preferences system. You hardcoded the injection into LDAP. If you  
> place it into the Session manager and just use the general  
> Preferences interface you will be able to initiate the Preference  
> whatever backend driver is being used ("ldap", "file", or  
> "kolab_imap").
> 
> I'm writing this so that if you invest the effort in updating it it  
> could be really added directly.

Yes, I will do that - my approach was somewhat naive, and the only  
thing I can mention in favour of it is that it works nicely in /my/  
2.2.0 environment...  But of course you're right that it should go into  
the standard prefs system.  I actually hacked a lot more meanwhile  
which is specific for my company.  Maybe a template-like init file  
would be nice, at least for small organisations like ours (not suitable  
for bigger ones like the BSI, though!).  Again, don't expect anything  
too fast, but I'll definitively will work on that!

Oh, and, btw, I will of course also update my samba patches (#2997 &  
the Wiki page), which I need in my setup...

> Both should be fixed in the newer release.

Cool, thanks, I just was a little worried that it got lost... ;-)

Again, I am *really* curious about the new release, and it's great to  
have it quickly after 2.2.0, in particular as I had *much* trouble with  
it.  Now the main thing which I'm concerned about is #2982, which is  
clearly an OpenLDAP (or Berkely DB, or 64-bit?) related one; maybe the  
upgrade is an improvement...

Cheers, Albrecht.



From schmerold1 at gmail.com  Sun Dec 14 21:02:04 2008
From: schmerold1 at gmail.com (schmerold1@gmail.com)
Date: Sun, 14 Dec 2008 14:02:04 -0600
Subject: kolab user for samba access
In-Reply-To: <1229068001l.6902l.0l@pc-adr2.lios-koeln.de>
References: <d53357b70812111228v494cff2aua40f7d3420e0677d@mail.gmail.com>
	<1229068001l.6902l.0l@pc-adr2.lios-koeln.de>
Message-ID: <4945663C.40501@gmail.com>

Any feedback regarding following the Ubuntu directions on a Centos 5.2 
box are appreciated.

Ubuntu directions: 
http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy


Albrecht Dre? wrote:
> Am 11.12.2008 21:28:50 schrieb(en) Antonio Straziota:
>   
>> i need to make kolab user capable to access samba shares. I'm trying  
>> to authenticate samba user against kolab openldap following some  
>> tutorial found on the web, but any attempt fails.
>>     
>
> Did you try  
> <http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy>?   
> Works nicely for me...
>
> Hth,
> Albrecht.
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>   



From devgioiatech at gmail.com  Mon Dec 15 08:54:35 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Mon, 15 Dec 2008 08:54:35 +0100
Subject: kolab user for samba access
In-Reply-To: <4945663C.40501@gmail.com>
References: <d53357b70812111228v494cff2aua40f7d3420e0677d@mail.gmail.com>
	<1229068001l.6902l.0l@pc-adr2.lios-koeln.de>
	<4945663C.40501@gmail.com>
Message-ID: <d53357b70812142354y62dafb05yfa4839fcca8a6f27@mail.gmail.com>

I'm going to try it... ;)

thanks to all for the link... i was searching for samba-openldap and i
haven't found this tutorial.
I'll give you a feedback asap.

bye.


2008/12/14 schmerold1 at gmail.com <schmerold1 at gmail.com>:
> Any feedback regarding following the Ubuntu directions on a Centos 5.2
> box are appreciated.
>
> Ubuntu directions:
> http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy
>
>
> Albrecht Dre? wrote:
>> Am 11.12.2008 21:28:50 schrieb(en) Antonio Straziota:
>>
>>> i need to make kolab user capable to access samba shares. I'm trying
>>> to authenticate samba user against kolab openldap following some
>>> tutorial found on the web, but any attempt fails.
>>>
>>
>> Did you try
>> <http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy>?
>> Works nicely for me...
>>
>> Hth,
>> Albrecht.
>>
>> _______________________________________________
>> 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
>



From christian.tardif at servinfo.ca  Wed Dec 17 18:06:59 2008
From: christian.tardif at servinfo.ca (Christian Tardif)
Date: Wed, 17 Dec 2008 12:06:59 -0500
Subject: Kolab Server 2.2.1 Beta 1
In-Reply-To: <20081212191815.GA21528.thomas@intevation.de>
References: <20081212191815.GA21528.thomas@intevation.de>
Message-ID: <494931B3.70506@servinfo.ca>

Le 12/12/08 ? 02:18 PM, Thomas Arendsen Hein ?crivait:
> I just uploaded Kolab Server 2.2.1-beta1 which contains a new
> version of the web client (Horde), restructured packages and many
> important fixes to the last release. Please make sure to follow
> the upgrade instructions in 1st.README, because there have been
>
> some changes in the LDAP schema.
I just tried to update mu 2.2.0 installation with what is in 2.2.1b1 
(from development-2.2/20081212-since-20080711/sources). I followed the 
instructions  from 1st.README for updating. But it did not succeed. In 
some point in the update process, I got:

Package "/kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz" is not valid
Attached  is the gzipped logfile of my last attempt, in case it helps. 
But, in short, here is what I got:

Executing(%install): env -i /kolab/lib/openpkg/bash --norc --noprofile 
--posix -e /kolab/RPM/TMP/rpm-tmp.14620
+ cd /kolab/RPM/TMP
+ cd PHPUnit-3.3.3
+ env 'PHP_PEAR_PHP_BIN=/kolab/bin/php -d safe_mode=off -d 
memory_limit=40M' PHP_PEAR_CACHE_DIR=/tmp/pear/cache /kolab/bin/pear 
install --offlin
Parsing of package.xml from file 
"/kolab/RPM/TMP/pear/download/package.xml" failed
Cannot download non-local package "/kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz"
Package "/kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz" is not valid
install failed
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.14620 (%install)


RPM build errors:
    Bad exit status from /kolab/RPM/TMP/rpm-tmp.14620 (%install)

Anyone knows how to fix that?  In the meantime, I went back to 2.2.0 
(viva backups!!!)
-- 
*Christian Tardif*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081217/74a0b24e/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kolab-update.log.gz
Type: application/x-gzip
Size: 8263 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20081217/74a0b24e/kolab-update.log.bin

From ml at radoeka.nl  Wed Dec 17 19:23:06 2008
From: ml at radoeka.nl (Richard Bos)
Date: Wed, 17 Dec 2008 19:23:06 +0100
Subject: Kolab Server 2.2.1 Beta 1
In-Reply-To: <494931B3.70506@servinfo.ca>
References: <20081212191815.GA21528.thomas@intevation.de>
	<494931B3.70506@servinfo.ca>
Message-ID: <200812171923.06680.ml@radoeka.nl>

Op Wednesday 17 December 2008 18:06:59 schreef Christian Tardif:
> + env 'PHP_PEAR_PHP_BIN=/kolab/bin/php -d safe_mode=off -d
> memory_limit=40M' PHP_PEAR_CACHE_DIR=/tmp/pear/cache /kolab/bin/pear
> install --offlin

Is this copy and pasted or written by you?  The --offlin should be --offline.  
Perhaps that rpm spec file is not correct?


-- 
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.



From christian.tardif at servinfo.ca  Wed Dec 17 20:11:38 2008
From: christian.tardif at servinfo.ca (Christian Tardif)
Date: Wed, 17 Dec 2008 14:11:38 -0500
Subject: Kolab Server 2.2.1 Beta 1
In-Reply-To: <200812171923.06680.ml@radoeka.nl>
References: <20081212191815.GA21528.thomas@intevation.de>	<494931B3.70506@servinfo.ca>
	<200812171923.06680.ml@radoeka.nl>
Message-ID: <49494EEA.3010501@servinfo.ca>

Le 17/12/08 ? 01:23 PM, Richard Bos ?crivait:
> Op Wednesday 17 December 2008 18:06:59 schreef Christian Tardif:
>   
>> > + env 'PHP_PEAR_PHP_BIN=/kolab/bin/php -d safe_mode=off -d
>> > memory_limit=40M' PHP_PEAR_CACHE_DIR=/tmp/pear/cache /kolab/bin/pear
>> > install --offlin
>>     
>
> Is this copy and pasted or written by you?  The --offlin should be --offline.  
>
> Perhaps that rpm spec file is not correct?
Oops. I did not sent it to the list in my reply. So here it is....

No, no. I copy/pasted, and did not pay attention to the rest of the 
line. It should read:

+ env 'PHP_PEAR_PHP_BIN=/kolab/bin/php -d safe_mode=off -d memory_limit=40M' PHP_PEAR_CACHE_DIR=/tmp/pear/cache /kolab/bin/pear install --offline --force --nodeps -P /kolab/RPM/TMP/PHPUnit-3.3.3-root /kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz


-- 
*Christian Tardif*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081217/f5c6cb8e/attachment.html

From kcaesar at hotmail.com  Wed Dec 17 20:41:02 2008
From: kcaesar at hotmail.com (kiser Caesar)
Date: Wed, 17 Dec 2008 20:41:02 +0100
Subject: How I can connect calendars ?
Message-ID: <BLU122-W3634A44898E89BADC1C35AA3F20@phx.gbl>


Hello,

I have certainly a stupid question, but I want to know if it's possible to connect directly to calendars with ICS or Webdav under thunderbird + lightning mod ?

Thank :)

_________________________________________________________________
In?dit ! Des Emotic?nes D?jant?es! Installez les dans votre Messenger ! 
http://www.ilovemessenger.fr/Emoticones/EmoticonesDejantees.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081217/3b61e326/attachment.html

From christian.tardif at servinfo.ca  Thu Dec 18 06:45:11 2008
From: christian.tardif at servinfo.ca (Christian Tardif)
Date: Thu, 18 Dec 2008 00:45:11 -0500
Subject: Kolab (openpkg) and gcc
Message-ID: <4949E367.9050709@servinfo.ca>

I tried the new Kolab beta tonight on a brand new Mandriva server 
2009.0. Does not compile. I tried latest kolab release. Does not 
compile.  But I found out. Mandriva 2009.0 comes with gcc 4.3.2..... 
openpkg does not compile with gcc 4.3.....  :-(

I installed, along with gcc 4.3, gcc 4.2, and soft linked gcc to gcc 
4.2. It works (well...  it's still compiling. At least, it does not hang 
any more). But is there a way to "point" to the right compiler instead 
of having to change the gcc soft link?
-- 

*Christian Tardif*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081218/54e992cc/attachment.html

From vladislav.tchernev at broadsign.com  Thu Dec 18 16:12:58 2008
From: vladislav.tchernev at broadsign.com (Vladislav Tchernev)
Date: Thu, 18 Dec 2008 10:12:58 -0500
Subject: Creating/deleting folders stopped working
Message-ID: <200812181012.58864.vladislav.tchernev@broadsign.com>

Hi all,
Since recently, I am having a weird problem. When I create a new user via the 
web GIU, kolab reports that the operation is successfull but it doesn't 
create a mailbox for the new user. When I try to delete the newly created 
user the the process hags showing "User Deleted, awaiting cleanup..." in the 
web interface. If I try to create an imap folder manually via cyradm it's 
working. Trying to delete the same folder via the kolab GUI still fails. So 
for some reason kolab is not able to perform any disk related operations. The  
permitions for /kolab/var/imapd/spool/domain/****/user/ looks right. 
Any ideas?

Regrads
Vlad



From christian.tardif at servinfo.ca  Thu Dec 18 17:35:49 2008
From: christian.tardif at servinfo.ca (Christian Tardif)
Date: Thu, 18 Dec 2008 11:35:49 -0500
Subject: SyncML
Message-ID: <494A7BE5.7050100@servinfo.ca>

Hi,

Is SyncML known to work under 2.2.1b1?  If so, what are the needed infos 
to make it work?

Thanks,
-- 

  *Christian Tardif*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081218/1b207cda/attachment.html

From wrobel at pardus.de  Thu Dec 18 22:13:20 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 18 Dec 2008 22:13:20 +0100
Subject: cannot delete shared calendar with spaces in the name
In-Reply-To: <7907AE10BB50DD4F840E76527D27EF1902105002@entmail.domain.austinent.com>
References: <7907AE10BB50DD4F840E76527D27EF1902105002@entmail.domain.austinent.com>
Message-ID: <20081218221320.5296332ste5w2by8@webmail.pardus.de>

Quoting Lucas Hendricks <LHendricks at austinent.com>:

> I was able to delete one shared folder with a space, and now I only have 1
> left which seems to be a phantom shared folder which indicates as far as
> deleting the folder: an isolated problem not related to the space in the
> name.
>
> Retrieving an ics file via the subscription link does not work for shared
> folders with a space in the name for me, though.  Using IE as a
> troubleshooting tool to connect to the Debian 4.0 binary install of 2.2:
>

Created https://www.intevation.de/roundup/kolab/issue3330

Cheers,

Gunnar

> Shared folder name: mycal
> type: events
> https://kolab.mydomain.com/horde/rpc.php/kronolith/shared.mycal.ics
> This works fine and prompts me to download the ics file through IE
>
> Shared folder name: my calendar
> type: events
> https://kolab.mydomain.com/horde/rpc.php/kronolith/shared.my%20calendar.ics
> This gives a blank response with no file download prompt
>
> I think I might have made the phantom folder during 2.2-rc3 and done an
> upgrade from that to 2.2 which I could easily have done incorrectly to
> prevent the issue (I might have marked it to delete then done the upgrade
> before it ran the cleanup or something).  Since that is isolated to the one
> phantom folder and I plan on doing a clean wipe and fresh install with 2.2.1
> it probably doesn't need any more attention.
>
> Info for if you are just interested, though: folder appears in horde as:
> [anonymous]shared.doc surgery
>
> I cannot delete it while logged on to the horde as my only user account nor
> as the manager logon, and it does not appear in shared folders in the
> web-admin interface logged on as the default manager account.  I created a
> maintainer account and administrator account, neither of which even has the
> calendar show up as visible either in horde or the web-admin interface for
> kolab.
>
> Lucas
>
> -----Original Message-----
> From: Gunnar Wrobel [mailto:wrobel at pardus.de]
> Sent: Friday, December 05, 2008 2:36 AM
> To: kolab-users at kolab.org
> Subject: Re: cannot delete shared calendar with spaces in the name
>
> Hi Lucas,
>
> Quoting Lucas Hendricks <LHendricks at austinent.com>:
>
>>   font-family: Arial;">Hello,  font-family: Arial;">
>> font-family: Arial;">I have created some shared calendars in the
>> horde admin interface that included spaces in the name and they
> seem
>> buggy.
>
> In the horde admin interface? I guess you rather mean the web-admin, right?
>
>> I could not subscribe to them via url and they will not let
>> me delete them either through admin or horde.
>
> How exactly do you try to delete it in horde? Did you give admin
> rights to the user trying to delete the shared folder?
>
>> When I set them to
>> delete in the admin interface they say "Folder deleted,
>> awaiting cleanup..." but then never delete and after cleanup
>> runs they're still there.
>
> What kind of a cleanup run? Does your kolabd run? kolabd should be
> responsible for removing the folders.
>
>>
>>  font-family: Arial;">   font-family: Arial;">I'm only on a beta
>> install and I will most
>> likely do a clean install when 2.2.1 comes out so it's not an issue
>> that needs much thought wasted on it (I will just not use spaces in
>> folder names in the future).   I just wanted to check here to see
> if
>> someone knows how to fix this off the top of their heads or if it
>> should be considered a feature.
>
> Deleting such folders works fine for me (albeit on a 2.2.1
> installation). I don't think we had some changes in that area though
> and I would expect it to also work on 2.2.0. I could check 2.2.0 also
> if required.
>
> Cheers,
>
> Gunnar
>
>>
>>  font-family: Arial;">   style="font-size: 10pt; font-family:
>> Arial; color: blue;">Lucas
>> Hendricks
>
> --
> ____ 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 <<
> --------------------------------------------------------------------
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
> _______________________________________________
> 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://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 <<
--------------------------------------------------------------------


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-users/attachments/20081218/c0a3bcbe/attachment.bin

From wrobel at pardus.de  Thu Dec 18 23:55:08 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 18 Dec 2008 23:55:08 +0100
Subject: How I can connect calendars ?
In-Reply-To: <BLU122-W3634A44898E89BADC1C35AA3F20@phx.gbl>
References: <BLU122-W3634A44898E89BADC1C35AA3F20@phx.gbl>
Message-ID: <20081218235508.857155ijpn5m79c0@webmail.pardus.de>


Quoting kiser Caesar <kcaesar at hotmail.com>:

> Hello,
>
> I have certainly a stupid question, but I want to know if it's
> possible to connect directly to calendars with ICS or Webdav under
> thunderbird + lightning mod ?

You can do this via the Kolab web client. The URLs look like this:

https://example.com/client/rpc.php/kronolith/wrobel at example.com/wrobel at example.com.ics

for a default Calendar and like this

https://example.com/client/rpc.php/kronolith/wrobel at example.com/Kalender.ics

for other calendars.

Cheers,

Gunnar
>
> Thank :)
>
>
> -------------------------
> T?l?phonez gratuitement ? tous vos proches avec Windows Live
> Messenger  !
href=\"http://www.windowslive.fr/messenger/1.asp\">T?l?chargez-le
> maintenant !

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

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-users/attachments/20081218/d22eb3bc/attachment.bin

From wrobel at pardus.de  Fri Dec 19 00:03:16 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Fri, 19 Dec 2008 00:03:16 +0100
Subject: SyncML
In-Reply-To: <494A7BE5.7050100@servinfo.ca>
References: <494A7BE5.7050100@servinfo.ca>
Message-ID: <20081219000316.11584o9f0cf76c8w@webmail.pardus.de>


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

> Hi,
>  Is SyncML known to work under 2.2.1b1?  If so, what are the needed
> infos to make it work?

It works, yes. Probably not with each and every possible device but  
that is a problem of SyncML itself not so much of the implementation.

For infos see:

http://wiki.horde.org/SyncHowTo

Cheers,

Gunnar

>  Thanks,
> -- 
>   CHRISTIAN TARDIF
>

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

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-users/attachments/20081219/886d7c50/attachment.bin

From wrobel at pardus.de  Fri Dec 19 00:04:28 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Fri, 19 Dec 2008 00:04:28 +0100
Subject: Creating/deleting folders stopped working
In-Reply-To: <200812181012.58864.vladislav.tchernev@broadsign.com>
References: <200812181012.58864.vladislav.tchernev@broadsign.com>
Message-ID: <20081219000428.12166gz5weg3tyko@webmail.pardus.de>

Quoting Vladislav Tchernev <vladislav.tchernev at broadsign.com>:

> Hi all,
> Since recently, I am having a weird problem. When I create a new user via the
> web GIU, kolab reports that the operation is successfull but it doesn't
> create a mailbox for the new user. When I try to delete the newly created
> user the the process hags showing "User Deleted, awaiting cleanup..." in the
> web interface. If I try to create an imap folder manually via cyradm it's
> working. Trying to delete the same folder via the kolab GUI still fails. So
> for some reason kolab is not able to perform any disk related operations. The
> permitions for /kolab/var/imapd/spool/domain/****/user/ looks right.
> Any ideas?

Sounds like the kolabd process broke down. Try to restart it with:

/kolab/bin/openpkg rc kolabd restart

>
> Regrads
> Vlad
>
> _______________________________________________
> 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 <<
--------------------------------------------------------------------


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-users/attachments/20081219/44941f2f/attachment.bin

From bernhard at intevation.de  Fri Dec 19 10:33:48 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 19 Dec 2008 10:33:48 +0100
Subject: Issue with installing Kolab on Debian
In-Reply-To: <48941C7A-6FC1-4AC0-B35D-60138B4045E6@mac.com>
References: <48941C7A-6FC1-4AC0-B35D-60138B4045E6@mac.com>
Message-ID: <200812191033.48499.bernhard@intevation.de>

Am Freitag, 12. Dezember 2008 04:11:18 schrieb Alexander Niedermeier:
> ++ installing OpenPKG binary distribution
> ./openpkg.bzip2: /lib/libc.so.6: version `GLIBC_2.3' not found ?
> (required by ./openpkg.bzip2)
> ./openpkg.bzip2: /lib/libc.so.6: version `GLIBC_2.1' not found ?
> (required by ./openpkg.bzip2)
> ./openpkg.bzip2: /lib/libc.so.6: version `GLIBC_2.0' not found ?
> (required by ./openpkg.bzip2)
> ++ fixating OpenPKG instance filesystem hierarchy
> /kolab/RPM/PKG/openpkg-2.5.4-2.5.4.ix86-debian3.1-kolab.sh: line ?
> 1009: /kolab/bin/openpkg: No such file or directory
> ++ post-processing OpenPKG bootstrap installation
> /kolab/RPM/PKG/openpkg-2.5.4-2.5.4.ix86-debian3.1-kolab.sh: line ?
> 1048: /kolab/lib/openpkg/rpmdb: No such file or directory
> cat: /kolab/etc/openpkg/platform: No such file or directory
> /kolab/RPM/PKG/openpkg-2.5.4-2.5.4.ix86-debian3.1-kolab.sh: line ?
> 1138: /kolab/lib/openpkg/rpmtool: No such file or directory
> obmtool:ERROR: bootstrapping failed
>
> I tried with Kolab 2.1 on Sarge and 2.2 on Etch. Same issue.
>
> What am I missing ?

Did you try from source? If not, you should.
If you get the same problem then, send the output of the command:
 /lib/libc.so.6

-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20081219/180d2d1c/attachment.bin

From bernhard at intevation.de  Fri Dec 19 10:37:49 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 19 Dec 2008 10:37:49 +0100
Subject: Kolab Live CD /USB
In-Reply-To: <493D3797.5020404@gensys-net.eu>
References: <493D3797.5020404@gensys-net.eu>
Message-ID: <200812191037.49616.bernhard@intevation.de>

Olivier,

Am Montag, 8. Dezember 2008 16:04:55 schrieb Olivier:
> I am pleased to introduce you the Cooperation-iws project.
>
> Cooperation-iws is an Intranet Nomad Web Server. Intranet to decide when
> you want to be connected. Nomad to carry it in your pocket on USB key /
> hard drive.
>
> Cooperation-iws have just been released in 0.7.0 version and now include
> a Kolab Live CD /USB release in the Intranet System flavors.

thanks for letting us know!
We hope Kolab Server works nicely for you!

Bernhard


> Cooperation-iws web is here : http://www.cooperation-iws.eu
>
> Cooperation-iws short introduction is here:
> http://www.cooperation-iws.eu/CMS/wp-content/plugins/download-monitor/downl
>oad.php?id=22
>
> Cooperation-iws extended presentation is here:
> http://www.cooperation-iws.eu/CMS/wp-content/plugins/download-monitor/downl
>oad.php?id=39


-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20081219/b05f0b83/attachment.bin

From vladislav.tchernev at broadsign.com  Fri Dec 19 14:33:11 2008
From: vladislav.tchernev at broadsign.com (Vladislav Tchernev)
Date: Fri, 19 Dec 2008 08:33:11 -0500
Subject: Creating/deleting folders stopped working
In-Reply-To: <20081219000428.12166gz5weg3tyko@webmail.pardus.de>
References: <200812181012.58864.vladislav.tchernev@broadsign.com>
	<20081219000428.12166gz5weg3tyko@webmail.pardus.de>
Message-ID: <200812190833.11636.vladislav.tchernev@broadsign.com>

Did it already couple of times .. no change .. the problem still persists.
How could I  debug this .. any place to look for usefull errors/messages .. 
system-wide or Kolab related logs (I have tried most of them already withot 
success)?

Thanks
Vlad


On Thursday 18 December 2008 18:04:28 Gunnar Wrobel wrote:
> Quoting Vladislav Tchernev <vladislav.tchernev at broadsign.com>:
> > Hi all,
> > Since recently, I am having a weird problem. When I create a new user via
> > the web GIU, kolab reports that the operation is successfull but it
> > doesn't create a mailbox for the new user. When I try to delete the newly
> > created user the the process hags showing "User Deleted, awaiting
> > cleanup..." in the web interface. If I try to create an imap folder
> > manually via cyradm it's working. Trying to delete the same folder via
> > the kolab GUI still fails. So for some reason kolab is not able to
> > perform any disk related operations. The permitions for
> > /kolab/var/imapd/spool/domain/****/user/ looks right. Any ideas?
>
> Sounds like the kolabd process broke down. Try to restart it with:
>
> /kolab/bin/openpkg rc kolabd restart
>
> > Regrads
> > Vlad
> >
> > _______________________________________________
> > Kolab-users mailing list
> > Kolab-users at kolab.org
> > https://kolab.org/mailman/listinfo/kolab-users




From harkin.as at gmail.com  Fri Dec 19 18:19:30 2008
From: harkin.as at gmail.com (Harkin Banks)
Date: Fri, 19 Dec 2008 12:19:30 -0500
Subject: Help with getting email working: kolab-server-2.2.1-beta-1
In-Reply-To: <54EC12E8D9B4476596228C52EF134C6F@mdmbxp>
References: <54EC12E8D9B4476596228C52EF134C6F@mdmbxp>
Message-ID: <8634029a0812190919q3d8510fbofc1d702d24a6484c@mail.gmail.com>

This is a followup as I have been looking through the logs and trying to
diagnose what's going on.  Below is the tail of
/kolab/var/postfix/log/postfix.log that I get when it try to email myself (
harkin at example.com to harkin at example.com).  Again, I get the same behavior
in Horde:  the email is in the Sent box, but does not appear in the Inbox.
It appears that the message appears to bounce on the basis of 'Command died
with status 255: "/kolab/bin/php"' (the full log associated with an email
attempt is below; this is just one line that looks particularly important to
my untrained eye):

Dec 19 16:55:39 smtp.example.com <info> postfix/pipe[17699]: 8A0A45883DA:
to=<harkin at example.com>, relay
=kolabmailboxfilter, delay=0.51, delays=0.1/0.08/0/0.34, dsn=5.3.0,
status=bounced (Command died with status 2
55: "/kolab/bin/php")


The issue with LDAP that I mentioned in the previous email seems to have
been resolved by restarting all the kolab services. Still, it's a little
scary since I don't what happened or why.


I have found another issue in searching the logs (I don't know if there
might be some relationship with the above bounce/command died issue).
Here's a line from /var/log/maillog:
Dec 19 14:45:02 vps kolabquotawarn[17454]: fatal: Can't read configuration,
please make sure that kolabquotawarn runs with sufficient privileges


/kolab/var/postfix/log/postfix.log:
Dec 19 16:52:20 smtp.example.com <warning> postfix/smtpd[11717]: warning:
database /kolab/etc/postfix/canon
ical.db is older than source file /kolab/etc/postfix/canonical
Dec 19 16:52:20 smtp.example.com <warning> postfix/smtpd[11718]: warning:
database /kolab/etc/postfix/canon
ical.db is older than source file /kolab/etc/postfix/canonical
Dec 19 16:52:21 smtp.example.com <info> postfix/smtpd[11718]: connect from
118-165-88-73.dynamic.hinet.net[
118.165.88.73]
Dec 19 16:52:21 smtp.example.com <info> postfix/smtpd[11718]: lost
connection after CONNECT from 118-165-88
-73.dynamic.hinet.net[118.165.88.73]
Dec 19 16:52:21 smtp.example.com <info> postfix/smtpd[11718]: disconnect
from 118-165-88-73.dynamic.hinet.n
et[118.165.88.73]
Dec 19 16:52:21 smtp.example.com <info> postfix/smtpd[11717]: connect from
118-165-88-73.dynamic.hinet.net[
118.165.88.73]
Dec 19 16:52:21 smtp.example.com <info> postfix/smtpd[11717]: lost
connection after CONNECT from 118-165-88
-73.dynamic.hinet.net[118.165.88.73]
Dec 19 16:52:21 smtp.example.com <info> postfix/smtpd[11717]: disconnect
from 118-165-88-73.dynamic.hinet.n
et[118.165.88.73]
Dec 19 16:55:34 smtp.example.com <warning> postfix/smtpd[17625]: warning:
database /kolab/etc/postfix/canon
ical.db is older than source file /kolab/etc/postfix/canonical
Dec 19 16:55:34 smtp.example.com <info> postfix/smtpd[17625]: connect from
localhost.localdomain[127.0.0.1]
Dec 19 16:55:35 smtp.example.com <info> postfix/smtpd[17625]: setting up TLS
connection from localhost.loca
ldomain[127.0.0.1]
Dec 19 16:55:35 smtp.example.com <info> postfix/smtpd[17625]: TLS connection
established from localhost.loc
aldomain[127.0.0.1]: TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)
Dec 19 16:55:35 smtp.example.com <warning> postfix/trivial-rewrite[17648]:
warning: database /kolab/etc/pos
tfix/relocated.db is older than source file /kolab/etc/postfix/relocated
Dec 19 16:55:35 smtp.example.com <warning> postfix/cleanup[17653]: warning:
database /kolab/etc/postfix/can
onical.db is older than source file /kolab/etc/postfix/canonical
Dec 19 16:55:35 smtp.example.com <info> postfix/smtpd[17625]: 78B865883DA:
client=localhost.localdomain[127
.0.0.1], sasl_method=LOGIN, sasl_username=harkin at example.com
Dec 19 16:55:35 smtp.example.com <info> postfix/cleanup[17653]: 78B865883DA:
message-id=<20081219165533.170
07aqp55a1mvk8 at example.com>
Dec 19 16:55:35 smtp.example.com <info> postfix/qmgr[30201]: 78B865883DA:
from=<harkin at example.com>, siz
e=1029, nrcpt=1 (queue active)
Dec 19 16:55:35 smtp.example.com <info> postfix/smtpd[17625]: disconnect
from localhost.localdomain[127.0.0
.1]
Dec 19 16:55:37 smtp.example.com <warning> postfix/smtpd[17680]: warning:
database /kolab/etc/postfix/canon
ical.db is older than source file /kolab/etc/postfix/canonical
Dec 19 16:55:37 smtp.example.com <info> postfix/smtpd[17680]: connect from
localhost.localdomain[127.0.0.1]
Dec 19 16:55:37 smtp.example.com <warning> postfix/cleanup[17682]: warning:
database /kolab/etc/postfix/can
onical.db is older than source file /kolab/etc/postfix/canonical
Dec 19 16:55:37 smtp.example.com <info> postfix/smtpd[17680]: 13DCB5883DC:
client=localhost.localdomain[127
.0.0.1]
Dec 19 16:55:37 smtp.example.com <info> postfix/cleanup[17682]: 13DCB5883DC:
message-id=<20081219165533.170
07aqp55a1mvk8 at example.com>
Dec 19 16:55:37 smtp.example.com <info> postfix/qmgr[30201]: 13DCB5883DC:
from=<harkin at example.com>, siz
e=1224, nrcpt=1 (queue active)
Dec 19 16:55:37 smtp.example.com <info> postfix/smtpd[17680]: disconnect
from localhost.localdomain[127.0.0
.1]
Dec 19 16:55:37 smtp.example.com <info> postfix/pipe[17660]: 78B865883DA:
to=<harkin at example.com>, relay
=kolabfilter, delay=2.2, delays=0.53/0.25/0/1.4, dsn=2.0.0, status=sent
(delivered via kolabfilter service)
Dec 19 16:55:37 smtp.example.com <info> postfix/qmgr[30201]: 78B865883DA:
removed
Dec 19 16:55:38 smtp.example.com <warning> postfix/smtpd[17696]: warning:
database /kolab/etc/postfix/canon
ical.db is older than source file /kolab/etc/postfix/canonical
Dec 19 16:55:38 smtp.example.com <info> postfix/smtpd[17696]: connect from
localhost.localdomain[127.0.0.1]
Dec 19 16:55:38 smtp.example.com <info> postfix/smtpd[17696]: 8A0A45883DA:
client=localhost.localdomain[127
.0.0.1]
Dec 19 16:55:38 smtp.example.com <info> postfix/cleanup[17682]: 8A0A45883DA:
message-id=<20081219165533.170
07aqp55a1mvk8 at example.com>
Dec 19 16:55:38 smtp.example.com <info> postfix/qmgr[30201]: 8A0A45883DA:
from=<harkin at example.com>, siz
e=1699, nrcpt=1 (queue active)
Dec 19 16:55:38 smtp.example.com <info> postfix/smtpd[17696]: disconnect
from localhost.localdomain[127.0.0
.1]
Dec 19 16:55:38 smtp.example.com <info> postfix/smtp[17684]: 13DCB5883DC:
to=<harkin at example.com>, relay
=127.0.0.1[127.0.0.1]:10024, delay=1.6, delays=0.17/0.38/0.01/1, dsn=2.0.0,
status=sent (250 2.0.0 Ok: queued
as 8A0A45883DA)
Dec 19 16:55:38 smtp.example.com <info> postfix/qmgr[30201]: 13DCB5883DC:
removed
Dec 19 16:55:39 smtp.example.com <info> postfix/pipe[17699]: 8A0A45883DA:
to=<harkin at example.com>, relay
=kolabmailboxfilter, delay=0.51, delays=0.1/0.08/0/0.34, dsn=5.3.0,
status=bounced (Command died with status 2
55: "/kolab/bin/php")
Dec 19 16:55:39 smtp.example.com <info> postfix/cleanup[17653]: 141605883DE:
message-id=<20081219165539.141
605883DE at mail101.example.com>
Dec 19 16:55:39 smtp.example.com <info> postfix/qmgr[30201]: 141605883DE:
from=<>, size=3599, nrcpt=1 (queu
e active)
Dec 19 16:55:39 smtp.example.com <info> postfix/bounce[17707]: 8A0A45883DA:
sender non-delivery notificatio
n: 141605883DE
Dec 19 16:55:39 smtp.example.com <info> postfix/qmgr[30201]: 8A0A45883DA:
removed
Dec 19 16:55:40 smtp.example.com <info> postfix/pipe[17699]: 141605883DE:
to=<harkin at example.com>, relay
=kolabmailboxfilter, delay=1.1, delays=0.18/0/0/0.91, dsn=5.3.0,
status=bounced (Command died with status 255:
 "/kolab/bin/php")
Dec 19 16:55:40 smtp.example.com <info> postfix/qmgr[30201]: 141605883DE:
removed
Dec 19 16:55:41 smtp.example.com <info> postfix/anvil[11774]: statistics:
max connection rate 2/60s for (0.
0.0.0:smtp:118.165.88.73) at Dec 19 16:52:21
Dec 19 16:55:41 smtp.example.com <info> postfix/anvil[11774]: statistics:
max connection count 1 for (0.0.0
.0:smtp:118.165.88.73) at Dec 19 16:52:21
Dec 19 16:55:41 smtp.example.com <info> postfix/anvil[11774]: statistics:
max cache size 1 at Dec 19 16:52:
21
#



On Thu, Dec 18, 2008 at 8:53 PM, Harkin Banks <harkin.as at gmail.com> wrote:

>  I just installed Kolab on a server with a fresh install of CentOS 5.2.  I
> got the source rpm's from
> http://ftp.belnet.be/packages/kolab/server/beta/kolab-server-2.2.1-beta-1/
>
> .  I did the install according to
> http://wiki.kolab.org/index.php/Kolab2_Installation_-_Source
> Everything looks great, except that email is not quite working correctly.
> I created two users on the local domain (user1 at domain.com,
> user2 at domain.com) and sent each an email from the other via Horde.  In
> each case the email showed up in the senders Sent box, but did not appear in
> the Inbox of the recipient.
>
> Subsequent to this, after working with the system for an hour or so, I am
> getting the following when I try to log in (with any of the three accounts
> I've created (one admin, two users)):
> Failed identifying the UID of the Kolab user harkin at domain.com. Error was:
> Unable to bind to the LDAP server as cn=nobody,cn=internal,dc=domain,dc=com!
>
> I hope by mentioning the second issue (with LDAP) I'm not creating
> additional confusion, but I thought they might be related.
>
> Any suggestions are appreciated.  Thank you.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081219/3d823ea4/attachment.html

From bernhard at intevation.de  Fri Dec 19 22:19:43 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 19 Dec 2008 22:19:43 +0100
Subject: Creating/deleting folders stopped working
In-Reply-To: <200812190833.11636.vladislav.tchernev@broadsign.com>
References: <200812181012.58864.vladislav.tchernev@broadsign.com>
	<20081219000428.12166gz5weg3tyko@webmail.pardus.de>
	<200812190833.11636.vladislav.tchernev@broadsign.com>
Message-ID: <200812192219.44204.bernhard@intevation.de>

On Freitag, 19. Dezember 2008, Vladislav Tchernev wrote:
> Did it already couple of times .. no change .. the problem still persists.
> How could I  debug this .. any place to look for usefull errors/messages ..
> system-wide or Kolab related logs (I have tried most of them already withot
> success)?

From page 16, 
http://www.kolab.org/doc/Allgemeine-Betriebsdokumentation-KolabServer22_20080103_1.0.pdf

Change values /kolab/etc/kolab/kolab.conf to
     log_level : 4
     debug : 1
Restart kolabd.
Check /var/log/syslog



>
> Thanks
> Vlad
>
> On Thursday 18 December 2008 18:04:28 Gunnar Wrobel wrote:
> > Quoting Vladislav Tchernev <vladislav.tchernev at broadsign.com>:
> > > Hi all,
> > > Since recently, I am having a weird problem. When I create a new user
> > > via the web GIU, kolab reports that the operation is successfull but it
> > > doesn't create a mailbox for the new user. When I try to delete the
> > > newly created user the the process hags showing "User Deleted, awaiting
> > > cleanup..." in the web interface. If I try to create an imap folder
> > > manually via cyradm it's working. Trying to delete the same folder via
> > > the kolab GUI still fails. So for some reason kolab is not able to
> > > perform any disk related operations. The permitions for
> > > /kolab/var/imapd/spool/domain/****/user/ looks right. Any ideas?
> >
> > Sounds like the kolabd process broke down. Try to restart it with:
> >
> > /kolab/bin/openpkg rc kolabd restart
> >
> > > Regrads
> > > Vlad
> > >
> > > _______________________________________________
> > > 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



-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20081219/2bd9baa2/attachment.bin

From bernhard at intevation.de  Fri Dec 19 22:21:53 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 19 Dec 2008 22:21:53 +0100
Subject: Help with getting email working: kolab-server-2.2.1-beta-1
In-Reply-To: <8634029a0812190919q3d8510fbofc1d702d24a6484c@mail.gmail.com>
References: <54EC12E8D9B4476596228C52EF134C6F@mdmbxp>
	<8634029a0812190919q3d8510fbofc1d702d24a6484c@mail.gmail.com>
Message-ID: <200812192221.53369.bernhard@intevation.de>

On Freitag, 19. Dezember 2008, Harkin Banks wrote:
> Dec 19 16:55:39 smtp.example.com <info> postfix/pipe[17699]: 8A0A45883DA:
> to=<harkin at example.com>, relay
> =kolabmailboxfilter, delay=0.51, delays=0.1/0.08/0/0.34, dsn=5.3.0,
> status=bounced (Command died with status 2
> 55: "/kolab/bin/php")

Hmm that looks bad, 
can you check with cyradm that you actually have an account INBOX for the user 
it wants to deliver? (Maybe misstyped the kolab homeserver?)
Also check the logs for kolabmailboxfiler.


-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20081219/9b6be9f4/attachment.bin

From harkin.as at gmail.com  Fri Dec 19 02:53:32 2008
From: harkin.as at gmail.com (Harkin Banks)
Date: Thu, 18 Dec 2008 20:53:32 -0500
Subject: Help with getting email working:  kolab-server-2.2.1-beta-1
Message-ID: <54EC12E8D9B4476596228C52EF134C6F@mdmbxp>

I just installed Kolab on a server with a fresh install of CentOS 5.2.  I got the source rpm's from 
http://ftp.belnet.be/packages/kolab/server/beta/kolab-server-2.2.1-beta-1/

.  I did the install according to 
http://wiki.kolab.org/index.php/Kolab2_Installation_-_Source

Everything looks great, except that email is not quite working correctly.  I created two users on the local domain (user1 at domain.com, user2 at domain.com) and sent each an email from the other via Horde.  In each case the email showed up in the senders Sent box, but did not appear in the Inbox of the recipient.  

Subsequent to this, after working with the system for an hour or so, I am getting the following when I try to log in (with any of the three accounts I've created (one admin, two users)):  
Failed identifying the UID of the Kolab user harkin at domain.com. Error was: Unable to bind to the LDAP server as cn=nobody,cn=internal,dc=domain,dc=com!

I hope by mentioning the second issue (with LDAP) I'm not creating additional confusion, but I thought they might be related.  

Any suggestions are appreciated.  Thank you.  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081218/7c82a324/attachment.html

From wrobel at pardus.de  Sat Dec 20 19:34:53 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sat, 20 Dec 2008 19:34:53 +0100
Subject: Help with getting email working: kolab-server-2.2.1-beta-1
In-Reply-To: <8634029a0812190919q3d8510fbofc1d702d24a6484c@mail.gmail.com>
References: <54EC12E8D9B4476596228C52EF134C6F@mdmbxp>
	<8634029a0812190919q3d8510fbofc1d702d24a6484c@mail.gmail.com>
Message-ID: <20081220193453.62192mxnz0gvejsw@webmail.pardus.de>


Quoting Harkin Banks <harkin.as at gmail.com>:

> This is a followup as I have been looking through the logs and
> trying to diagnose what's going on.  Below is the tail of
> /kolab/var/postfix/log/postfix.log that I get when it try to email
> myself (harkin at example.com[1] to harkin at example.com[2]).  Again, I
> get the same behavior in Horde:  the email is in the Sent box, but
> does not appear in the Inbox.  It appears that the message appears
> to bounce on the basis of 'Command died with status 255:
> "/kolab/bin/php"' (the full log associated with an email
> attempt is below; this is just one line that looks particularly
> important to my untrained eye):

This is a dumb configuration error we had in the configuration files.  
I discovered and fixed this yesterday:

https://www.intevation.de/roundup/kolab/issue3331

This should not have happened.

Cheers,

Gunnar

>  Dec 19 16:55:39 smtp.example.com[3] <info>
> postfix/pipe[17699]: 8A0A45883DA: to=<harkin at example.com[4]>,
> relay
> =kolabmailboxfilter, delay=0.51, delays=0.1/0.08/0/0.34, dsn=5.3.0,
> status=bounced (Command died with status 2
> 55: "/kolab/bin/php")
>
>
> The issue with LDAP that I mentioned in the previous email seems to
> have been resolved by restarting all the kolab services. Still,
it's
> a little scary since I don't what happened or why.   I have found  
> another issue in searching the logs (I don't know if
> there might be some relationship with the above bounce/command died
> issue).  Here's a line from /var/log/maillog:
> Dec 19 14:45:02 vps kolabquotawarn[17454]: fatal: Can't read
> configuration, please make sure that kolabquotawarn runs with
> sufficient privileges
>  /kolab/var/postfix/log/postfix.log:
> Dec 19 16:52:20 smtp.example.com[5] <warning>
> postfix/smtpd[11717]: warning: database /kolab/etc/postfix/canon
> ical.db is older than source file /kolab/etc/postfix/canonical
> Dec 19 16:52:20 smtp.example.com[6] <warning>
> postfix/smtpd[11718]: warning: database /kolab/etc/postfix/canon
> ical.db is older than source file /kolab/etc/postfix/canonical
> Dec 19 16:52:21 smtp.example.com[7] <info>
> postfix/smtpd[11718]: connect from
> 118-165-88-73.dynamic.hinet.net[8][
> 118.165.88.73]
> Dec 19 16:52:21 smtp.example.com[9] <info>
> postfix/smtpd[11718]: lost connection after CONNECT from 118-165-88
> -73.dynamic.hinet.net[10][118.165.88.73]
> Dec 19 16:52:21 smtp.example.com[11] <info>
> postfix/smtpd[11718]: disconnect from 118-165-88-73.dynamic.hinet.n
> et[118.165.88.73]
> Dec 19 16:52:21 smtp.example.com[12] <info>
> postfix/smtpd[11717]: connect from
> 118-165-88-73.dynamic.hinet.net[13][
> 118.165.88.73]
> Dec 19 16:52:21 smtp.example.com[14] <info>
> postfix/smtpd[11717]: lost connection after CONNECT from 118-165-88
> -73.dynamic.hinet.net[15][118.165.88.73]
> Dec 19 16:52:21 smtp.example.com[16] <info>
> postfix/smtpd[11717]: disconnect from 118-165-88-73.dynamic.hinet.n
> et[118.165.88.73]
> Dec 19 16:55:34 smtp.example.com[17] <warning>
> postfix/smtpd[17625]: warning: database /kolab/etc/postfix/canon
> ical.db is older than source file /kolab/etc/postfix/canonical
> Dec 19 16:55:34 smtp.example.com[18] <info>
> postfix/smtpd[17625]: connect from localhost.localdomain[127.0.0.1]
> Dec 19 16:55:35 smtp.example.com[19] <info>
> postfix/smtpd[17625]: setting up TLS connection from localhost.loca
> ldomain[127.0.0.1]
> Dec 19 16:55:35 smtp.example.com[20] <info>
> postfix/smtpd[17625]: TLS connection established from localhost.loc
> aldomain[127.0.0.1]: TLSv1 with cipher DHE-RSA-AES256-SHA (256/256
> bits)
> Dec 19 16:55:35 smtp.example.com[21] <warning>
> postfix/trivial-rewrite[17648]: warning: database /kolab/etc/pos
> tfix/relocated.db is older than source file
> /kolab/etc/postfix/relocated
> Dec 19 16:55:35 smtp.example.com[22] <warning>
> postfix/cleanup[17653]: warning: database /kolab/etc/postfix/can
> onical.db is older than source file /kolab/etc/postfix/canonical
> Dec 19 16:55:35 smtp.example.com[23] <info>
> postfix/smtpd[17625]: 78B865883DA: client=localhost.localdomain[127
> .0.0.1], sasl_method=LOGIN, sasl_username=harkin at example.com[24]
> Dec 19 16:55:35 smtp.example.com[25] <info>
> postfix/cleanup[17653]: 78B865883DA:
> message-id=<20081219165533.170
>  07aqp55a1mvk8 at example.com[26]>
> Dec 19 16:55:35 smtp.example.com[27] <info>
> postfix/qmgr[30201]: 78B865883DA:
> from=<harkin at example.com[28]>, siz
> e=1029, nrcpt=1 (queue active)
> Dec 19 16:55:35 smtp.example.com[29] <info>
> postfix/smtpd[17625]: disconnect from localhost.localdomain[127.0.0
> .1]
> Dec 19 16:55:37 smtp.example.com[30] <warning>
> postfix/smtpd[17680]: warning: database /kolab/etc/postfix/canon
> ical.db is older than source file /kolab/etc/postfix/canonical
> Dec 19 16:55:37 smtp.example.com[31] <info>
> postfix/smtpd[17680]: connect from localhost.localdomain[127.0.0.1]
> Dec 19 16:55:37 smtp.example.com[32] <warning>
> postfix/cleanup[17682]: warning: database /kolab/etc/postfix/can
> onical.db is older than source file /kolab/etc/postfix/canonical
> Dec 19 16:55:37 smtp.example.com[33] <info>
> postfix/smtpd[17680]: 13DCB5883DC: client=localhost.localdomain[127
> .0.0.1]
> Dec 19 16:55:37 smtp.example.com[34] <info>
> postfix/cleanup[17682]: 13DCB5883DC:
> message-id=<20081219165533.170
>  07aqp55a1mvk8 at example.com[35]>
> Dec 19 16:55:37 smtp.example.com[36] <info>
> postfix/qmgr[30201]: 13DCB5883DC:
> from=<harkin at example.com[37]>, siz
> e=1224, nrcpt=1 (queue active)
> Dec 19 16:55:37 smtp.example.com[38] <info>
> postfix/smtpd[17680]: disconnect from localhost.localdomain[127.0.0
> .1]
> Dec 19 16:55:37 smtp.example.com[39] <info>
> postfix/pipe[17660]: 78B865883DA: to=<harkin at example.com[40]>,
> relay
> =kolabfilter, delay=2.2, delays=0.53/0.25/0/1.4, dsn=2.0.0,
> status=sent (delivered via kolabfilter service)
> Dec 19 16:55:37 smtp.example.com[41] <info>
> postfix/qmgr[30201]: 78B865883DA: removed
> Dec 19 16:55:38 smtp.example.com[42] <warning>
> postfix/smtpd[17696]: warning: database /kolab/etc/postfix/canon
> ical.db is older than source file /kolab/etc/postfix/canonical
> Dec 19 16:55:38 smtp.example.com[43] <info>
> postfix/smtpd[17696]: connect from localhost.localdomain[127.0.0.1]
> Dec 19 16:55:38 smtp.example.com[44] <info>
> postfix/smtpd[17696]: 8A0A45883DA: client=localhost.localdomain[127
> .0.0.1]
> Dec 19 16:55:38 smtp.example.com[45] <info>
> postfix/cleanup[17682]: 8A0A45883DA:
> message-id=<20081219165533.170
> 07aqp55a1mvk8 at example.com[46]>
> Dec 19 16:55:38 smtp.example.com[47] <info>
> postfix/qmgr[30201]: 8A0A45883DA:
> from=<harkin at example.com[48]>, siz
> e=1699, nrcpt=1 (queue active)
> Dec 19 16:55:38 smtp.example.com[49] <info>
> postfix/smtpd[17696]: disconnect from localhost.localdomain[127.0.0
> .1]
> Dec 19 16:55:38 smtp.example.com[50] <info>
> postfix/smtp[17684]: 13DCB5883DC: to=<harkin at example.com[51]>,
> relay
> =127.0.0.1[127.0.0.1]:10024, delay=1.6, delays=0.17/0.38/0.01/1,
> dsn=2.0.0, status=sent (250 2.0.0 Ok: queued
> as 8A0A45883DA)
> Dec 19 16:55:38 smtp.example.com[52] <info>
> postfix/qmgr[30201]: 13DCB5883DC: removed
> Dec 19 16:55:39 smtp.example.com[53] <info>
> postfix/pipe[17699]: 8A0A45883DA: to=<harkin at example.com[54]>,
> relay
> =kolabmailboxfilter, delay=0.51, delays=0.1/0.08/0/0.34, dsn=5.3.0,
> status=bounced (Command died with status 2
> 55: "/kolab/bin/php")
> Dec 19 16:55:39 smtp.example.com[55] <info>
> postfix/cleanup[17653]: 141605883DE:
> message-id=<20081219165539.141
> 605883DE at mail101.example.com[56]>
> Dec 19 16:55:39 smtp.example.com[57] <info>
> postfix/qmgr[30201]: 141605883DE: from=<>, size=3599, nrcpt=1
> (queu
> e active)
> Dec 19 16:55:39 smtp.example.com[58] <info>
> postfix/bounce[17707]: 8A0A45883DA: sender non-delivery notificatio
> n: 141605883DE
> Dec 19 16:55:39 smtp.example.com[59] <info>
> postfix/qmgr[30201]: 8A0A45883DA: removed
> Dec 19 16:55:40 smtp.example.com[60] <info>
> postfix/pipe[17699]: 141605883DE: to=<harkin at example.com[61]>,
> relay
> =kolabmailboxfilter, delay=1.1, delays=0.18/0/0/0.91, dsn=5.3.0,
> status=bounced (Command died with status 255:
>  "/kolab/bin/php")
> Dec 19 16:55:40 smtp.example.com[62] <info>
> postfix/qmgr[30201]: 141605883DE: removed
> Dec 19 16:55:41 smtp.example.com[63] <info>
> postfix/anvil[11774]: statistics: max connection rate 2/60s for (0.
> 0.0.0:smtp:118.165.88.73) at Dec 19 16:52:21
> Dec 19 16:55:41 smtp.example.com[64] <info>
> postfix/anvil[11774]: statistics: max connection count 1 for (0.0.0
> .0:smtp:118.165.88.73) at Dec 19 16:52:21
> Dec 19 16:55:41 smtp.example.com[65] <info>
> postfix/anvil[11774]: statistics: max cache size 1 at Dec 19 16:52:
> 21
> #
>
> On Thu, Dec 18, 2008 at 8:53 PM, Harkin
> Banks <harkin.as[66]@gmail.com[67]>
> wrote:
>  0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
bgcolor="#ffffff"> I just
> installed Kolab on a server with a fresh install of CentOS 5.2.  I
> got the source rpm's from   face="Arial">
href="http://ftp.belnet.be/packages/kolab/server/beta/kolab-server-2.2.1-beta-1/">http://ftp.belnet.be/packages/kolab/server/beta/kolab-server-2.2.1-beta-1/
>    size="2" face="Arial">.  I did the install according to
>   target="_blank"
>
href="http://wiki.kolab.org/index.php/Kolab2_Installation_-_Source">http://wiki.kolab.org/index.php/Kolab2_Installation_-_Source
>  Everything looks
> great, except that email is not quite working correctly.  I created
> two users on the local domain (
href="mailto:user1 at domain.com">user1 at domain.com,  target="_blank"
> href="mailto:user2 at domain.com">user2 at domain.com) and sent each
> an email from the other via Horde.  In each case the email showed
up
> in the senders Sent box, but did not appear in the Inbox of the
> recipient.    face="Arial">   face="Arial">Subsequent to this,
after working with the system for
> an hour or so, I am getting the following when I try to log in
(with
> any of the three accounts I've created (one admin, two users)):    
> face="Times New Roman">Failed identifying the UID of the Kolab
> user  href="mailto:harkin at domain.com">harkin at domain.com. Error
was:
> Unable to bind to the LDAP server as
> cn=nobody,cn=internal,dc=domain,dc=com!
>  New Roman">   face="Arial">I hope by
> mentioning the second issue (with LDAP) I'm not creating additional
> confusion, but I thought they might be related.   size="3"  
> face="Times New Roman">   size="2" face="Arial">
Roman">Any suggestions are appreciated.  Thank you.
>   size="3" face="Times New Roman">

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

Links:
------
[1] mailto:harkin at example.com
[2] mailto:harkin at example.com
[3] http://smtp.example.com
[4] mailto:harkin at example.com
[5] http://smtp.example.com
[6] http://smtp.example.com
[7] http://smtp.example.com
[8] http://118-165-88-73.dynamic.hinet.net
[9] http://smtp.example.com
[10] http://73.dynamic.hinet.net
[11] http://smtp.example.com
[12] http://smtp.example.com
[13] http://118-165-88-73.dynamic.hinet.net
[14] http://smtp.example.com
[15] http://73.dynamic.hinet.net
[16] http://smtp.example.com
[17] http://smtp.example.com
[18] http://smtp.example.com
[19] http://smtp.example.com
[20] http://smtp.example.com
[21] http://smtp.example.com
[22] http://smtp.example.com
[23] http://smtp.example.com
[24] mailto:harkin at example.com
[25] http://smtp.example.com
[26] mailto:07aqp55a1mvk8 at example.com
[27] http://smtp.example.com
[28] mailto:harkin at example.com
[29] http://smtp.example.com
[30] http://smtp.example.com
[31] http://smtp.example.com
[32] http://smtp.example.com
[33] http://smtp.example.com
[34] http://smtp.example.com
[35] mailto:07aqp55a1mvk8 at example.com
[36] http://smtp.example.com
[37] mailto:harkin at example.com
[38] http://smtp.example.com
[39] http://smtp.example.com
[40] mailto:harkin at example.com
[41] http://smtp.example.com
[42] http://smtp.example.com
[43] http://smtp.example.com
[44] http://smtp.example.com
[45] http://smtp.example.com
[46] mailto:07aqp55a1mvk8 at example.com
[47] http://smtp.example.com
[48] mailto:harkin at example.com
[49] http://smtp.example.com
[50] http://smtp.example.com
[51] mailto:harkin at example.com
[52] http://smtp.example.com
[53] http://smtp.example.com
[54] mailto:harkin at example.com
[55] http://smtp.example.com
[56] mailto:605883DE at mail101.example.com
[57] http://smtp.example.com
[58] http://smtp.example.com
[59] http://smtp.example.com
[60] http://smtp.example.com
[61] mailto:harkin at example.com
[62] http://smtp.example.com
[63] http://smtp.example.com
[64] http://smtp.example.com
[65] http://smtp.example.com
[66] http://harkin.as
[67] http://gmail.com


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-users/attachments/20081220/01792eaf/attachment.bin

From aspineux at gmail.com  Sat Dec 20 22:22:20 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sat, 20 Dec 2008 22:22:20 +0100
Subject: Kolab Server 2.2.1 Beta 1
In-Reply-To: <494931B3.70506@servinfo.ca>
References: <20081212191815.GA21528.thomas@intevation.de>
	<494931B3.70506@servinfo.ca>
Message-ID: <71fe4e760812201322r31078531y572fb0edf4524ffe@mail.gmail.com>

On Wed, Dec 17, 2008 at 6:06 PM, Christian Tardif
<christian.tardif at servinfo.ca> wrote:
> Le 12/12/08 ? 02:18 PM, Thomas Arendsen Hein ?crivait:
>
> I just uploaded Kolab Server 2.2.1-beta1 which contains a new
> version of the web client (Horde), restructured packages and many
> important fixes to the last release. Please make sure to follow
> the upgrade instructions in 1st.README, because there have been
>
> some changes in the LDAP schema.
>
> I just tried to update mu 2.2.0 installation with what is in 2.2.1b1 (from
> development-2.2/20081212-since-20080711/sources). I followed the
> instructions  from 1st.README for updating. But it did not succeed. In some
> point in the update process, I got:
>
> Package "/kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz" is not valid
> Attached  is the gzipped logfile of my last attempt, in case it helps. But,
> in short, here is what I got:
>
> Executing(%install): env -i /kolab/lib/openpkg/bash --norc --noprofile
> --posix -e /kolab/RPM/TMP/rpm-tmp.14620
> + cd /kolab/RPM/TMP
> + cd PHPUnit-3.3.3
> + env 'PHP_PEAR_PHP_BIN=/kolab/bin/php -d safe_mode=off -d memory_limit=40M'
> PHP_PEAR_CACHE_DIR=/tmp/pear/cache /kolab/bin/pear install --offlin
> Parsing of package.xml from file "/kolab/RPM/TMP/pear/download/package.xml"
> failed
> Cannot download non-local package "/kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz"
> Package "/kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz" is not valid
> install failed

Can you check the checksum of your RPM package ?
If it match, can you extract the tgz above (just use a "openpkg rpm -i
???.src.rpm") the try a
"tar tvzf /kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz" and look the last
lines for an error or not


> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.14620 (%install)
>
>
> RPM build errors:
>     Bad exit status from /kolab/RPM/TMP/rpm-tmp.14620 (%install)
>
> Anyone knows how to fix that?  In the meantime, I went back to 2.2.0 (viva
> backups!!!)
> --
> Christian Tardif
>
> _______________________________________________
> 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 wrobel at pardus.de  Sun Dec 21 23:00:20 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sun, 21 Dec 2008 23:00:20 +0100
Subject: Kolab Server 2.2.1 Beta 1
In-Reply-To: <494931B3.70506@servinfo.ca>
References: <20081212191815.GA21528.thomas@intevation.de>
	<494931B3.70506@servinfo.ca>
Message-ID: <20081221230020.79162evflp078a68@webmail.pardus.de>


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

> Le 12/12/08 ? 02:18 PM, Thomas Arendsen Hein ?crivait:
>  I just uploaded Kolab Server 2.2.1-beta1 which contains a new
> version of the web client (Horde), restructured packages and many
> important fixes to the last release. Please make sure to follow the
> upgrade instructions in 1st.README, because there have beensome
> changes in the LDAP schema.

> I just tried to update mu 2.2.0 installation with what is in 2.2.1b1
> (from development-2.2/20081212-since-20080711/sources). I followed the
> instructions  from 1st.README for updating. But it did not succeed. In
> some point in the update process, I got:
>
> Package "/kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz" is not valid
> Attached  is the gzipped logfile of my last attempt, in case it
> helps. But, in short, here is what I got:
>
> Executing(%install): env -i /kolab/lib/openpkg/bash --norc
> --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.14620
> + cd /kolab/RPM/TMP
> + cd PHPUnit-3.3.3
> + env 'PHP_PEAR_PHP_BIN=/kolab/bin/php -d safe_mode=off -d
> memory_limit=40M' PHP_PEAR_CACHE_DIR=/tmp/pear/cache /kolab/bin/pear
> install --offlin
> Parsing of package.xml from file
> "/kolab/RPM/TMP/pear/download/package.xml" failed
> Cannot download non-local package
> "/kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz"
> Package "/kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz" is not valid
> install failed
> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.14620 (%install)

Hm, the upgrade procedure runs fine for me. Is the server you upgrade  
from a plain 2.2.0 server or has it been upgraded from an earlier  
version? What is the version of PEAR on that machine?

Cheers,

Gunnar

-- 
____ http://www.pardus.de[1] _________________
http://gunnarwrobel.de[2] _

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

Links:
------
[1] http://www.pardus.de
[2] http://gunnarwrobel.de


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-users/attachments/20081221/f77b145f/attachment.bin

From admin at jmay.org  Mon Dec 22 10:16:08 2008
From: admin at jmay.org (Jochen May)
Date: Mon, 22 Dec 2008 10:16:08 +0100
Subject: Log-In Problems
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAJ7BXRqPWfdNkLKYTJ3u6xjCgAAAEAAAABpx1mXMku5Jgf0VXzrUvmcBAAAAAA==@jmay.org>


Hi!

I have a problem with the login at horde. The system is a fresh kolab 2.2.0 installation on a debian 4 system. Via imap-client (e.g.
Thunderbird) the login is possible.

When i try to login, i get the message "username and/or password are incorrect" at the horde webclient. At the horde.log i get the
message:

Nov 30 17:12:09 HORDE [error] [horde] FAILED LOGIN for foo at foo.bar [192.168.1.211] to Horde [pid 3373 on line 157 of
"/kolab/var/kolab/www/horde/login.php"]

At the same time in the php-errors.log:
[30-Nov-2008 17:12:09] PHP Notice:  Unknown: Connection failed to kolab.taj-mahal.lan,143: Die Wartezeit f?r die Verbindung ist
abgelaufen (errflg=2) in Unknown on line 0
Translation: The waiting time for the connection is over

During the installtion i get no errors or warning. Anybody a hint or idea? 
Or is this a horde problem and not related to kolab?

Greetings
Jochen

--
Contact Information:

Jochen May
Im Laufer 9
97892 Kreuzwertheim
Tel:+49-(0)9342/919692
Fax:+49-(0)9342/919693
Key-ID: 0x3A7D7FFC



From dvadell at linuxclusters.com.ar  Mon Dec 22 10:57:40 2008
From: dvadell at linuxclusters.com.ar (Diego M. Vadell)
Date: Mon, 22 Dec 2008 07:57:40 -0200
Subject: Log-In Problems
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAAJ7BXRqPWfdNkLKYTJ3u6xjCgAAAEAAAABpx1mXMku5Jgf0VXzrUvmcBAAAAAA==@jmay.org>
References: <!&!AAAAAAAAAAAYAAAAAAAAAJ7BXRqPWfdNkLKYTJ3u6xjCgAAAEAAAABpx1mXMku5Jgf0VXzrUvmcBAAAAAA==@jmay.org>
Message-ID: <200812220757.40958.dvadell@linuxclusters.com.ar>

Hi,

   Are you sure that the kolab server knows that it is kolab.taj-mahal.lan? 
i.e. do you have an entry for kolab.taj-mahal.lan in /etc/hosts ?

 -- Diego

On Monday 22 December 2008 07:16:08 Jochen May wrote:
> Hi!
>
> I have a problem with the login at horde. The system is a fresh kolab 2.2.0
> installation on a debian 4 system. Via imap-client (e.g. Thunderbird) the
> login is possible.
>
> When i try to login, i get the message "username and/or password are
> incorrect" at the horde webclient. At the horde.log i get the message:
>
> Nov 30 17:12:09 HORDE [error] [horde] FAILED LOGIN for foo at foo.bar
> [192.168.1.211] to Horde [pid 3373 on line 157 of
> "/kolab/var/kolab/www/horde/login.php"]
>
> At the same time in the php-errors.log:
> [30-Nov-2008 17:12:09] PHP Notice:  Unknown: Connection failed to
> kolab.taj-mahal.lan,143: Die Wartezeit f?r die Verbindung ist abgelaufen
> (errflg=2) in Unknown on line 0
> Translation: The waiting time for the connection is over
>
> During the installtion i get no errors or warning. Anybody a hint or idea?
> Or is this a horde problem and not related to kolab?
>
> Greetings
> Jochen
>
> --
> Contact Information:
>
> Jochen May
> Im Laufer 9
> 97892 Kreuzwertheim
> Tel:+49-(0)9342/919692
> Fax:+49-(0)9342/919693
> Key-ID: 0x3A7D7FFC
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users




From harkin.as at gmail.com  Fri Dec 19 23:27:59 2008
From: harkin.as at gmail.com (Harkin Banks)
Date: Fri, 19 Dec 2008 17:27:59 -0500
Subject: Help with getting email working: kolab-server-2.2.1-beta-1
References: <54EC12E8D9B4476596228C52EF134C6F@mdmbxp><8634029a0812190919q3d8510fbofc1d702d24a6484c@mail.gmail.com>
	<200812192221.53369.bernhard@intevation.de>
Message-ID: <935DA27F81A04F408539FC40BEA659D7@mdmbxp>

> can you check with cyradm that you actually have an account INBOX for the 
> user
it wants to deliver? (Maybe misstyped the kolab homeserver?)

Yes, there does appear to be an inbox:
user/harkin at example.com (\HasChildren)

# /kolab/bin/cyradm -user manager localhost
Password:
localhost.localdomain> lm
shared.testsharedfolder at example.com (\HasNoChildren)
user/adminstrator/Calendar at example.com (\HasNoChildren)
user/adminstrator/Contacts at example.com (\HasNoChildren)
user/adminstrator/Notes at example.com (\HasNoChildren)
user/adminstrator/Tasks at example.com (\HasNoChildren)
user/adminstrator at example.com (\HasChildren)
user/harkin/Calendar at example.com (\HasNoChildren)
user/harkin/Contacts at example.com (\HasNoChildren)
user/harkin/Notes at example.com (\HasNoChildren)
user/harkin/Sent at example.com (\HasNoChildren)
user/harkin/Tasks at example.com (\HasNoChildren)
user/harkin at example.com (\HasChildren)
user/user1/Calendar at example.com (\HasNoChildren)
user/user1/Contacts at example.com (\HasNoChildren)
user/user1/Notes at example.com (\HasNoChildren)
user/user1/Sent at example.com (\HasNoChildren)
user/user1/Tasks at example.com (\HasNoChildren)
user/user1 at example.com (\HasChildren)


> Maybe misstyped the kolab homeserver?

I'm not sure what you mean by this?


> Also check the logs for kolabmailboxfiler.

Here are the postfix.log entries (not sure if you have another log in 
mind -- please let me know if you do and I will look there) containing 
"kolabmailboxfilter" that I get when attempting to send an email:
[root at smtp kolab]# tail -n100 /kolab/var/postfix/log/postfix.log | grep 
kolabmailboxfilter
Dec 19 16:55:39 smtp.example.com <info> postfix/pipe[17699]: 8A0A45883DA: 
to=<harkin at example.com>, relay=kolabmailboxfilter, delay=0.51, 
delays=0.1/0.08/0/0.34, dsn=5.3.0, status=bounced (Command died with status 
255: "/kolab/bin/php")
Dec 19 16:55:40 smtp.example.com <info> postfix/pipe[17699]: 141605883DE: 
to=<harkin at example.com>, relay=kolabmailboxfilter, delay=1.1, 
delays=0.18/0/0/0.91, dsn=5.3.0, status=bounced (Command died with status 
255: "/kolab/bin/php")
Dec 19 22:18:36 smtp.example.com <info> postfix/pipe[25895]: A1CFB5883DA: 
to=<harkin at example.com>, relay=kolabmailboxfilter, delay=0.67, 
delays=0.27/0.01/0/0.38, dsn=5.3.0, status=bounced (Command died with status 
255: "/kolab/bin/php")
Dec 19 22:18:36 smtp.example.com <info> postfix/pipe[25895]: 50D7E5883DE: 
to=<harkin at example.com>, relay=kolabmailboxfilter, delay=0.67, 
delays=0.18/0/0/0.49, dsn=5.3.0, status=bounced (Command died with status 
255: "/kolab/bin/php")
[root at smtp kolab]#


Another thing is the the LDAP server appears to be running (in a "ps aux"), 
but there is some problem with it such that Horde and Kolab admin are not 
able to communicate with it.  When I restart the Kolab services, it starts 
to work again.


Thank you.


----- Original Message ----- 
From: "Bernhard Reiter" <bernhard at intevation.de>
To: <kolab-users at kolab.org>
Sent: Friday, December 19, 2008 4:21 PM
Subject: Re: Help with getting email working: kolab-server-2.2.1-beta-1

> Dec 19 16:55:39 smtp.example.com <info> postfix/pipe[17699]: 8A0A45883DA:
> to=<harkin at example.com>, relay
> =kolabmailboxfilter, delay=0.51, delays=0.1/0.08/0/0.34, dsn=5.3.0,
> status=bounced (Command died with status 2
> 55: "/kolab/bin/php")

Hmm that looks bad,
can you check with cyradm that you actually have an account INBOX for the 
user
it wants to deliver? (Maybe misstyped the kolab homeserver?)
Also check the logs for kolabmailboxfiler.


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



From aspineux at gmail.com  Mon Dec 22 15:05:28 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 22 Dec 2008 15:05:28 +0100
Subject: Help with getting email working: kolab-server-2.2.1-beta-1
In-Reply-To: <935DA27F81A04F408539FC40BEA659D7@mdmbxp>
References: <54EC12E8D9B4476596228C52EF134C6F@mdmbxp>
	<8634029a0812190919q3d8510fbofc1d702d24a6484c@mail.gmail.com>
	<200812192221.53369.bernhard@intevation.de>
	<935DA27F81A04F408539FC40BEA659D7@mdmbxp>
Message-ID: <71fe4e760812220605v70e9932asaa07a5e4b1ab2ad7@mail.gmail.com>

On Fri, Dec 19, 2008 at 11:27 PM, Harkin Banks <harkin.as at gmail.com> wrote:
>> can you check with cyradm that you actually have an account INBOX for the
>> user
> it wants to deliver? (Maybe misstyped the kolab homeserver?)
>
> Yes, there does appear to be an inbox:
> user/harkin at example.com (\HasChildren)
>
> # /kolab/bin/cyradm -user manager localhost
> Password:
> localhost.localdomain> lm
> shared.testsharedfolder at example.com (\HasNoChildren)
> user/adminstrator/Calendar at example.com (\HasNoChildren)
> user/adminstrator/Contacts at example.com (\HasNoChildren)
> user/adminstrator/Notes at example.com (\HasNoChildren)
> user/adminstrator/Tasks at example.com (\HasNoChildren)
> user/adminstrator at example.com (\HasChildren)
> user/harkin/Calendar at example.com (\HasNoChildren)
> user/harkin/Contacts at example.com (\HasNoChildren)
> user/harkin/Notes at example.com (\HasNoChildren)
> user/harkin/Sent at example.com (\HasNoChildren)
> user/harkin/Tasks at example.com (\HasNoChildren)
> user/harkin at example.com (\HasChildren)
> user/user1/Calendar at example.com (\HasNoChildren)
> user/user1/Contacts at example.com (\HasNoChildren)
> user/user1/Notes at example.com (\HasNoChildren)
> user/user1/Sent at example.com (\HasNoChildren)
> user/user1/Tasks at example.com (\HasNoChildren)
> user/user1 at example.com (\HasChildren)
>
>
>> Maybe misstyped the kolab homeserver?
>
> I'm not sure what you mean by this?
>
>
>> Also check the logs for kolabmailboxfiler.
>
> Here are the postfix.log entries (not sure if you have another log in
> mind -- please let me know if you do and I will look there) containing
> "kolabmailboxfilter" that I get when attempting to send an email:
> [root at smtp kolab]# tail -n100 /kolab/var/postfix/log/postfix.log | grep
> kolabmailboxfilter
> Dec 19 16:55:39 smtp.example.com <info> postfix/pipe[17699]: 8A0A45883DA:
> to=<harkin at example.com>, relay=kolabmailboxfilter, delay=0.51,
> delays=0.1/0.08/0/0.34, dsn=5.3.0, status=bounced (Command died with status
> 255: "/kolab/bin/php")

Yes, you have to look into the kolabmailboxfilter specific log, aka
/kolab/var/kolab-filter/log/filter.log ( before 2.2 it was
/kolab/var/resmgr/resmgr.log)

> Dec 19 16:55:40 smtp.example.com <info> postfix/pipe[17699]: 141605883DE:
> to=<harkin at example.com>, relay=kolabmailboxfilter, delay=1.1,
> delays=0.18/0/0/0.91, dsn=5.3.0, status=bounced (Command died with status
> 255: "/kolab/bin/php")
> Dec 19 22:18:36 smtp.example.com <info> postfix/pipe[25895]: A1CFB5883DA:
> to=<harkin at example.com>, relay=kolabmailboxfilter, delay=0.67,
> delays=0.27/0.01/0/0.38, dsn=5.3.0, status=bounced (Command died with status
> 255: "/kolab/bin/php")
> Dec 19 22:18:36 smtp.example.com <info> postfix/pipe[25895]: 50D7E5883DE:
> to=<harkin at example.com>, relay=kolabmailboxfilter, delay=0.67,
> delays=0.18/0/0/0.49, dsn=5.3.0, status=bounced (Command died with status
> 255: "/kolab/bin/php")
> [root at smtp kolab]#
>
>
> Another thing is the the LDAP server appears to be running (in a "ps aux"),
> but there is some problem with it such that Horde and Kolab admin are not
> able to communicate with it.  When I restart the Kolab services, it starts
> to work again.

you mean restarting just the kolabd daemon ? Or restarting all the
kolab services ?

>
>
> Thank you.
>
>
> ----- Original Message -----
> From: "Bernhard Reiter" <bernhard at intevation.de>
> To: <kolab-users at kolab.org>
> Sent: Friday, December 19, 2008 4:21 PM
> Subject: Re: Help with getting email working: kolab-server-2.2.1-beta-1
>
>> Dec 19 16:55:39 smtp.example.com <info> postfix/pipe[17699]: 8A0A45883DA:
>> to=<harkin at example.com>, relay
>> =kolabmailboxfilter, delay=0.51, delays=0.1/0.08/0/0.34, dsn=5.3.0,
>> status=bounced (Command died with status 2
>> 55: "/kolab/bin/php")
>
> Hmm that looks bad,
> can you check with cyradm that you actually have an account INBOX for the
> user
> it wants to deliver? (Maybe misstyped the kolab homeserver?)
> Also check the logs for kolabmailboxfiler.
>
>
>> _______________________________________________
>> 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 admin at jmay.org  Mon Dec 22 19:33:31 2008
From: admin at jmay.org (Jochen May)
Date: Mon, 22 Dec 2008 19:33:31 +0100
Subject: Log-In Problems
In-Reply-To: <200812220757.40958.dvadell@linuxclusters.com.ar>
References: <!&!AAAAAAAAAAAYAAAAAAAAAJ7BXRqPWfdNkLKYTJ3u6xjCgAAAEAAAABpx1mXMku5Jgf0VXzrUvmcBAAAAAA==@jmay.org>
	<200812220757.40958.dvadell@linuxclusters.com.ar>
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAJ7BXRqPWfdNkLKYTJ3u6xjCgAAAEAAAAJar4ratbntIs1yvQpcI9tABAAAAAA==@jmay.org>

Hi,
 
>    Are you sure that the kolab server knows that it is 
> kolab.taj-mahal.lan? 
> i.e. do you have an entry for kolab.taj-mahal.lan in /etc/hosts ?
> 
>  -- Diego

Thanks a lot. That was the problem. In the /etc/hosts was a wrong ip-address for the kolab server. 
After i put the right ip-address in, horde worked  without any problem.

Regards,
Jochen



From christian.tardif at servinfo.ca  Tue Dec 23 02:23:16 2008
From: christian.tardif at servinfo.ca (Christian Tardif)
Date: Mon, 22 Dec 2008 20:23:16 -0500
Subject: Kolab Server 2.2.1 Beta 1
In-Reply-To: <71fe4e760812201322r31078531y572fb0edf4524ffe@mail.gmail.com>
References: <20081212191815.GA21528.thomas@intevation.de>	
	<494931B3.70506@servinfo.ca>
	<71fe4e760812201322r31078531y572fb0edf4524ffe@mail.gmail.com>
Message-ID: <49503D84.7050508@servinfo.ca>

Alain Spineux wrote:
> On Wed, Dec 17, 2008 at 6:06 PM, Christian Tardif
> <christian.tardif at servinfo.ca> wrote:
>   
>> Le 12/12/08 ? 02:18 PM, Thomas Arendsen Hein ?crivait:
>>
>> I just uploaded Kolab Server 2.2.1-beta1 which contains a new
>> version of the web client (Horde), restructured packages and many
>> important fixes to the last release. Please make sure to follow
>> the upgrade instructions in 1st.README, because there have been
>>
>> some changes in the LDAP schema.
>>
>> I just tried to update mu 2.2.0 installation with what is in 2.2.1b1 (from
>> development-2.2/20081212-since-20080711/sources). I followed the
>> instructions  from 1st.README for updating. But it did not succeed. In some
>> point in the update process, I got:
>>
>> Package "/kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz" is not valid
>> Attached  is the gzipped logfile of my last attempt, in case it helps. But,
>> in short, here is what I got:
>>
>> Executing(%install): env -i /kolab/lib/openpkg/bash --norc --noprofile
>> --posix -e /kolab/RPM/TMP/rpm-tmp.14620
>> + cd /kolab/RPM/TMP
>> + cd PHPUnit-3.3.3
>> + env 'PHP_PEAR_PHP_BIN=/kolab/bin/php -d safe_mode=off -d memory_limit=40M'
>> PHP_PEAR_CACHE_DIR=/tmp/pear/cache /kolab/bin/pear install --offlin
>> Parsing of package.xml from file "/kolab/RPM/TMP/pear/download/package.xml"
>> failed
>> Cannot download non-local package "/kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz"
>> Package "/kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz" is not valid
>> install failed
>>     
>
> Can you check the checksum of your RPM package ?
> If it match, can you extract the tgz above (just use a "openpkg rpm -i
> ???.src.rpm") the try a
> "tar tvzf /kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz" and look the last
> lines for an error or not

Checksum OK, extraction OK, no error in the tgz file.
-- 

  *Christian Tardif*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081222/a919e1ea/attachment.html

From christian.tardif at servinfo.ca  Tue Dec 23 02:35:55 2008
From: christian.tardif at servinfo.ca (Christian Tardif)
Date: Mon, 22 Dec 2008 20:35:55 -0500
Subject: Kolab Server 2.2.1 Beta 1
In-Reply-To: <20081221230020.79162evflp078a68@webmail.pardus.de>
References: <20081212191815.GA21528.thomas@intevation.de>	<494931B3.70506@servinfo.ca>
	<20081221230020.79162evflp078a68@webmail.pardus.de>
Message-ID: <4950407B.9060205@servinfo.ca>

Gunnar Wrobel wrote:
> Hm, the upgrade procedure runs fine for me. Is the server you upgrade 
> from a plain 2.2.0 server or has it been upgraded from an earlier 
> version? What is the version of PEAR on that machine? 
I think this machine was an upgrade before 2.2.0. Actually, looking at 
my source folder, I have 2.2rc3, and 2.2.0-since-2.2rc3, so....

 From the output of /kolab/bin/pear list:

PEAR   1.7.1   stable

-- 

file:///L:/logo.jpg *Christian Tardif*
Servinfo Inc.
christian.tardif at servinfo.ca
514.237.6332
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081222/eb2b097d/attachment.html

From bernhard at intevation.de  Tue Dec 23 11:18:52 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 23 Dec 2008 11:18:52 +0100
Subject: Kolab Server 2.2.1 Beta 1
In-Reply-To: <49503D84.7050508@servinfo.ca>
References: <20081212191815.GA21528.thomas@intevation.de>
	<71fe4e760812201322r31078531y572fb0edf4524ffe@mail.gmail.com>
	<49503D84.7050508@servinfo.ca>
Message-ID: <200812231118.52901.bernhard@intevation.de>

On Dienstag, 23. Dezember 2008, Christian Tardif wrote:
> >> Cannot download non-local package
> >> "/kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz" Package
> >> "/kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz" is not valid install failed
> >> ? ?
> >
> > Can you check the checksum of your RPM package ?
> > If it match, can you extract the tgz above (just use a "openpkg rpm -i
> > ???.src.rpm") the try a
> > "tar tvzf /kolab/RPM/SRC/PHPUnit/PHPUnit-3.3.3.tgz" and look the last
> > lines for an error or not
>
> Checksum OK, extraction OK, no error in the tgz file.

I take it you have enough disk space, also.
(I know chances are low you'd overlook that, but I thought it might be worth a 
shot.)


-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20081223/33d9c997/attachment.bin

From christian.tardif at servinfo.ca  Tue Dec 23 15:39:31 2008
From: christian.tardif at servinfo.ca (Christian Tardif)
Date: Tue, 23 Dec 2008 09:39:31 -0500
Subject: Kolab Server 2.2.1 Beta 1
In-Reply-To: <200812231118.52901.bernhard@intevation.de>
References: <20081212191815.GA21528.thomas@intevation.de>	<71fe4e760812201322r31078531y572fb0edf4524ffe@mail.gmail.com>	<49503D84.7050508@servinfo.ca>
	<200812231118.52901.bernhard@intevation.de>
Message-ID: <4950F823.4020905@servinfo.ca>

Le 2008-12-23 ? 05:18, Bernhard Reiter ?crivait:
> I take it you have enough disk space, also.
> (I know chances are low you'd overlook that, but I thought it might be worth a 
>
> shot.)
Could have been but no, I'm not missing disk space. I checked, as it 
happened once, in a totally different project. Anything can help. May it 
be the server name!  :-)
-- 

  *Christian Tardif*

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081223/609e3b81/attachment.html

From rdeiriar at lascondes.cl  Tue Dec 23 17:32:41 2008
From: rdeiriar at lascondes.cl (Roberto de Iriarte)
Date: Tue, 23 Dec 2008 13:32:41 -0300
Subject: kolab/issue2349 still present on 2.2.1 beta 1
Message-ID: <495112A9.10804@lascondes.cl>

Hallo,

I am trying to compile kolab 2.2.1 beta 1 on FreeBSD 7-Stable, and have 
just hit issue 2349.

I've modified the imapd.spec file as described on 
https://www.intevation.de/roundup/kolab/msg16342, will see if it helps 
in a couple of minutes, as soon as it finishes compiling (or fails) i 
will report back.

/Froliche Weihnachten/!
Roberto de Iriarte







From rdeiriar at lascondes.cl  Tue Dec 23 20:32:42 2008
From: rdeiriar at lascondes.cl (Roberto de Iriarte)
Date: Tue, 23 Dec 2008 16:32:42 -0300
Subject: kolab/issue2349 still present on 2.2.1 beta 1
In-Reply-To: <495112A9.10804@lascondes.cl>
References: <495112A9.10804@lascondes.cl>
Message-ID: <49513CDA.9040300@lascondes.cl>

Roberto de Iriarte wrote:
> Hallo,
>
> I am trying to compile kolab 2.2.1 beta 1 on FreeBSD 7-Stable, and have 
> just hit issue 2349.
>
> I've modified the imapd.spec file as described on 
> https://www.intevation.de/roundup/kolab/msg16342, will see if it helps 
> in a couple of minutes, as soon as it finishes compiling (or fails) i 
> will report back.
>
> /Froliche Weihnachten/!
> Roberto de Iriarte
>   
I can confirm that the fix described in

https://www.intevation.de/roundup/kolab/msg16342

Allows to compile 2.2.1 beta on FreeBSD 7-Stable

Best regards,
Roberto de Iriarte.




From dvadell at linuxclusters.com.ar  Tue Dec 23 21:07:41 2008
From: dvadell at linuxclusters.com.ar (Diego M. Vadell)
Date: Tue, 23 Dec 2008 18:07:41 -0200
Subject: Multiple Kolab's php eat all the RAM
Message-ID: <200812231807.41967.dvadell@linuxclusters.com.ar>

Hi,

    I have several kolab 2.2. installations. Today one of them started to use 
all the RAM with several php processes. I had to restart it several times and 
then ssh to it as soon as it starts, in order to win a race with all the php 
processess that started to appear!

   The only think I noticed were that in the mailq there were 4 mails, with a 
lot of recipients (all local).

  Question: Does anyone knows what scenario could spawn hundreds of php 
processes?

Before hanging, top looks like this:
-----------------------
top - 14:15:07 up 11 min,  2 users,  load average: 44.85, 26.53, 11.33
Tasks: 165 total,   4 running, 161 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.7%us,  8.6%sy,  0.0%ni,  0.0%id, 71.4%wa, 19.3%hi,  0.0%si,  0.0%st
Mem:    515492k total,   510556k used,     4936k free,      332k buffers
Swap:   524280k total,   489328k used,    34952k free,   386208k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                                                                                                 
 8347 kolab-n   18   0 13400 1300  840 D  1.8  0.3   
0:00.57 /kolab/bin/php -c /kolab/etc/apache/php.ini -f /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php --
 8268 kolab-n   18   0 78940  20m  20m D  1.4  4.1   
0:00.75 /kolab/bin/php -c /kolab/etc/apache/php.ini -f /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php --
 8292 kolab-n   16   0 78940  45m  45m D  1.4  9.1   
0:00.83 /kolab/bin/php -c /kolab/etc/apache/php.ini -f /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php --
 8334 kolab-n   16   0 78940  25m  25m D  1.3  5.1   
0:00.64 /kolab/bin/php -c /kolab/etc/apache/php.ini -f /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php --
 8317 kolab-n   18   0 78940  34m  34m D  0.9  6.8   
0:00.53 /kolab/bin/php -c /kolab/etc/apache/php.ini -f /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php --
 8297 kolab-n   16   0 78940  24m  24m D  0.8  4.8   
0:00.85 /kolab/bin/php -c /kolab/etc/apache/php.ini -f /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php -
-------------------------

Thanks in advance
 - Diego



From dvadell at linuxclusters.com.ar  Tue Dec 23 22:59:32 2008
From: dvadell at linuxclusters.com.ar (Diego M. Vadell)
Date: Tue, 23 Dec 2008 19:59:32 -0200
Subject: Multiple Kolab's php eat all the RAM
In-Reply-To: <200812231807.41967.dvadell@linuxclusters.com.ar>
References: <200812231807.41967.dvadell@linuxclusters.com.ar>
Message-ID: <200812231959.34060.dvadell@linuxclusters.com.ar>

Hi

   I think I found it: when I send an email to 30 people inside the server 
(locals to the server) I get a lot of kolabmailfilter processess. Is it the 
intended way of doing things? 

On Tuesday 23 December 2008 18:07:41 Diego M. Vadell wrote:
> Hi,
>
>     I have several kolab 2.2. installations. Today one of them started to
> use all the RAM with several php processes. I had to restart it several
> times and then ssh to it as soon as it starts, in order to win a race with
> all the php processess that started to appear!
>
>    The only think I noticed were that in the mailq there were 4 mails, with
> a lot of recipients (all local).
>
>   Question: Does anyone knows what scenario could spawn hundreds of php
> processes?
>
> Before hanging, top looks like this:
> -----------------------
> top - 14:15:07 up 11 min,  2 users,  load average: 44.85, 26.53, 11.33
> Tasks: 165 total,   4 running, 161 sleeping,   0 stopped,   0 zombie
> Cpu(s):  0.7%us,  8.6%sy,  0.0%ni,  0.0%id, 71.4%wa, 19.3%hi,  0.0%si, 
> 0.0%st Mem:    515492k total,   510556k used,     4936k free,      332k
> buffers Swap:   524280k total,   489328k used,    34952k free,   386208k
> cached
>
>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
>  8347 kolab-n   18   0 13400 1300  840 D  1.8  0.3
> 0:00.57 /kolab/bin/php -c /kolab/etc/apache/php.ini -f
> /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php -- 8268 kolab-n   18
>   0 78940  20m  20m D  1.4  4.1
> 0:00.75 /kolab/bin/php -c /kolab/etc/apache/php.ini -f
> /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php -- 8292 kolab-n   16
>   0 78940  45m  45m D  1.4  9.1
> 0:00.83 /kolab/bin/php -c /kolab/etc/apache/php.ini -f
> /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php -- 8334 kolab-n   16
>   0 78940  25m  25m D  1.3  5.1
> 0:00.64 /kolab/bin/php -c /kolab/etc/apache/php.ini -f
> /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php -- 8317 kolab-n   18
>   0 78940  34m  34m D  0.9  6.8
> 0:00.53 /kolab/bin/php -c /kolab/etc/apache/php.ini -f
> /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php -- 8297 kolab-n   16
>   0 78940  24m  24m D  0.8  4.8
> 0:00.85 /kolab/bin/php -c /kolab/etc/apache/php.ini -f
> /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php -
> -------------------------
>
> Thanks in advance
>  - Diego




From aspineux at gmail.com  Wed Dec 24 07:55:09 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Wed, 24 Dec 2008 07:55:09 +0100
Subject: [Kolab-devel] Multiple Kolab's php eat all the RAM
In-Reply-To: <200812231959.34060.dvadell@linuxclusters.com.ar>
References: <200812231807.41967.dvadell@linuxclusters.com.ar>
	<200812231959.34060.dvadell@linuxclusters.com.ar>
Message-ID: <71fe4e760812232255h421dbe68j1358196e547f6916@mail.gmail.com>

On Tue, Dec 23, 2008 at 10:59 PM, Diego M. Vadell
<dvadell at linuxclusters.com.ar> wrote:
> Hi
>
>   I think I found it: when I send an email to 30 people inside the server
> (locals to the server) I get a lot of kolabmailfilter processess. Is it the
> intended way of doing things?


Unfortunately yes !
When you send to multiple recipients, one message is "cloned" by recipients !
This could be avoided by some more coding.
This would reduce the CPU load and could reduce the space in the imap
storage regarding
the "singleinstancestore" in imapd.conf if handled
appropriately.(divided by 3 with my own experience)


Regards.


Regards.

>
> On Tuesday 23 December 2008 18:07:41 Diego M. Vadell wrote:
>> Hi,
>>
>>     I have several kolab 2.2. installations. Today one of them started to
>> use all the RAM with several php processes. I had to restart it several
>> times and then ssh to it as soon as it starts, in order to win a race with
>> all the php processess that started to appear!
>>
>>    The only think I noticed were that in the mailq there were 4 mails, with
>> a lot of recipients (all local).
>>
>>   Question: Does anyone knows what scenario could spawn hundreds of php
>> processes?
>>
>> Before hanging, top looks like this:
>> -----------------------
>> top - 14:15:07 up 11 min,  2 users,  load average: 44.85, 26.53, 11.33
>> Tasks: 165 total,   4 running, 161 sleeping,   0 stopped,   0 zombie
>> Cpu(s):  0.7%us,  8.6%sy,  0.0%ni,  0.0%id, 71.4%wa, 19.3%hi,  0.0%si,
>> 0.0%st Mem:    515492k total,   510556k used,     4936k free,      332k
>> buffers Swap:   524280k total,   489328k used,    34952k free,   386208k
>> cached
>>
>>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
>>  8347 kolab-n   18   0 13400 1300  840 D  1.8  0.3
>> 0:00.57 /kolab/bin/php -c /kolab/etc/apache/php.ini -f
>> /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php -- 8268 kolab-n   18
>>   0 78940  20m  20m D  1.4  4.1
>> 0:00.75 /kolab/bin/php -c /kolab/etc/apache/php.ini -f
>> /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php -- 8292 kolab-n   16
>>   0 78940  45m  45m D  1.4  9.1
>> 0:00.83 /kolab/bin/php -c /kolab/etc/apache/php.ini -f
>> /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php -- 8334 kolab-n   16
>>   0 78940  25m  25m D  1.3  5.1
>> 0:00.64 /kolab/bin/php -c /kolab/etc/apache/php.ini -f
>> /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php -- 8317 kolab-n   18
>>   0 78940  34m  34m D  0.9  6.8
>> 0:00.53 /kolab/bin/php -c /kolab/etc/apache/php.ini -f
>> /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php -- 8297 kolab-n   16
>>   0 78940  24m  24m D  0.8  4.8
>> 0:00.85 /kolab/bin/php -c /kolab/etc/apache/php.ini -f
>> /kolab/var/kolab-filter/scripts/kolabmailboxfilter.php -
>> -------------------------
>>
>> Thanks in advance
>>  - Diego
>
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



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



From dvadell at linuxclusters.com.ar  Sat Dec 27 00:13:51 2008
From: dvadell at linuxclusters.com.ar (Diego M. Vadell)
Date: Fri, 26 Dec 2008 21:13:51 -0200
Subject: [Kolab-devel] Multiple Kolab's php eat all the RAM
In-Reply-To: <71fe4e760812232255h421dbe68j1358196e547f6916@mail.gmail.com>
References: <200812231807.41967.dvadell@linuxclusters.com.ar>
	<200812231959.34060.dvadell@linuxclusters.com.ar>
	<71fe4e760812232255h421dbe68j1358196e547f6916@mail.gmail.com>
Message-ID: <200812262113.52165.dvadell@linuxclusters.com.ar>

On Wednesday 24 December 2008 04:55:09 Alain Spineux wrote:
> On Tue, Dec 23, 2008 at 10:59 PM, Diego M. Vadell
>
> <dvadell at linuxclusters.com.ar> wrote:
> > Hi
> >
> >   I think I found it: when I send an email to 30 people inside the server
> > (locals to the server) I get a lot of kolabmailfilter processess. Is it
> > the intended way of doing things?
>
> Unfortunately yes !
> When you send to multiple recipients, one message is "cloned" by recipients
> ! This could be avoided by some more coding.
> This would reduce the CPU load and could reduce the space in the imap
> storage regarding
> the "singleinstancestore" in imapd.conf if handled
> appropriately.(divided by 3 with my own experience)
>
>
> Regards.

Hi,

  I mitigated (or solved?) the issue by editing master.cf.template and 
changing this line:

kolabmailboxfilter     unix  -       n       n       -      -        pipe 
user=kolab-n null_sender= argv=/kolab/bin/php

to:

kolabmailboxfilter     unix  -       n       n       -       2       pipe 
user=kolab-n null_sender= argv=/kolab/bin/php


Given that amavisd gets only 2 emails at a time, I thought 2 was a good place 
to start. 

Thanks,
 -- Diego



From Lucidblue0 at gmail.com  Sat Dec 27 08:54:33 2008
From: Lucidblue0 at gmail.com (Lucidblue0@gmail.com)
Date: Sat, 27 Dec 2008 07:54:33 +0000
Subject: export/import annotations.db
Message-ID: <002215046c8b6a29c0045f028d0a@google.com>

Hi all,

I'm trying to migrate a current install of 2.1 to a 2.2 server.

I first exported the LDAP on the original system. I ran kolab_bootstrap -b  
on the new system and then cleared out the new LDAP, changed the hashes for  
the nobody and manager accounts in the exported ldif file, then had a  
successful import. This finally was the easiest approach, even after trying  
to find all the config files, I guess the hash was still different even  
though it was the same pass...

Next I was able to export and then import the mailboxes.db.

The last vital step (aside from rsync'ing the mail), is to somehow copy the  
annotations.db, I remember when I tried to do this in the past, I just  
copied the file and I was getting DB_ERROR's in the log files.

After much googling, I'm not seeing anything that actually mentions how to  
do this, all the backup docs I've found just skip over it, saying "and you  
might want to backup the annotations.db too".

Should I be able to just copy that file and put it into the new install? I  
have multiple calendar and contact folders on group account and also one or  
more per user account.

Any ideas about this would be great. The migration is going from a SuSE  
10.2 native (Kolab 2.1) to a SuSE 10.3 native (Kolab 2.2).

Thanks,
-Skip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081227/dcfd4969/attachment.html

From aspineux at gmail.com  Sat Dec 27 10:35:10 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sat, 27 Dec 2008 10:35:10 +0100
Subject: export/import annotations.db
In-Reply-To: <002215046c8b6a29c0045f028d0a@google.com>
References: <002215046c8b6a29c0045f028d0a@google.com>
Message-ID: <71fe4e760812270135u28e271edt615d4232f7cf4b29@mail.gmail.com>

On Sat, Dec 27, 2008 at 8:54 AM,  <Lucidblue0 at gmail.com> wrote:
> Hi all,
>
> I'm trying to migrate a current install of 2.1 to a 2.2 server.
>
> I first exported the LDAP on the original system. I ran kolab_bootstrap -b
> on the new system and then cleared out the new LDAP, changed the hashes for
> the nobody and manager accounts in the exported ldif file, then had a
> successful import. This finally was the easiest approach, even after trying
> to find all the config files, I guess the hash was still different even
> though it was the same pass...
>
> Next I was able to export and then import the mailboxes.db.
>
> The last vital step (aside from rsync'ing the mail), is to somehow copy the
> annotations.db, I remember when I tried to do this in the past, I just
> copied the file and I was getting DB_ERROR's in the log files.
>
> After much googling, I'm not seeing anything that actually mentions how to
> do this, all the backup docs I've found just skip over it, saying "and you
> might want to backup the annotations.db too".

Yes, you have to copy the annotation.db too

Happy New Year !

>
> Should I be able to just copy that file and put it into the new install? I
> have multiple calendar and contact folders on group account and also one or
> more per user account.
>
> Any ideas about this would be great. The migration is going from a SuSE 10.2
> native (Kolab 2.1) to a SuSE 10.3 native (Kolab 2.2).

.... hum, it depent the Berkely DB package, run this on both machine and compare

# rpm -qa "bdb*" "db*"

If they is enought different then it could be not compatible.

If so here it part of my backup/restore restore script :

   # backup
   su $eg_cyrus_user -c "/kolab/bin/cvt_cyrusdb $ANNOTATIONS_DB
berkeley $ANNOTATIONS_BAK skiplist"

   # restore
   chown $eg_cyrus_user.$eg_cyrus_user $ANNOTATIONS_BAK
   su $eg_cyrus_user -c "/kolab/bin/cvt_cyrusdb $ANNOTATIONS_BAK
skiplist $ANNOTATIONS_DB berkeley"


>
> Thanks,
> -Skip
> _______________________________________________
> 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 wrobel at pardus.de  Sat Dec 27 18:28:25 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sat, 27 Dec 2008 18:28:25 +0100
Subject: [Kolab-devel] Multiple Kolab's php eat all the RAM
In-Reply-To: <200812262113.52165.dvadell@linuxclusters.com.ar>
References: <200812231807.41967.dvadell@linuxclusters.com.ar>
	<200812231959.34060.dvadell@linuxclusters.com.ar>
	<71fe4e760812232255h421dbe68j1358196e547f6916@mail.gmail.com>
	<200812262113.52165.dvadell@linuxclusters.com.ar>
Message-ID: <20081227182825.16444p7ni4665b40@webmail.pardus.de>

Quoting "Diego M. Vadell" <dvadell at linuxclusters.com.ar>:

> On Wednesday 24 December 2008 04:55:09 Alain Spineux wrote:
>> On Tue, Dec 23, 2008 at 10:59 PM, Diego M. Vadell
>>
>> <dvadell at linuxclusters.com.ar> wrote:
>> > Hi
>> >
>> >   I think I found it: when I send an email to 30 people inside the server
>> > (locals to the server) I get a lot of kolabmailfilter processess. Is it
>> > the intended way of doing things?
>>
>> Unfortunately yes !
>> When you send to multiple recipients, one message is "cloned" by recipients
>> ! This could be avoided by some more coding.
>> This would reduce the CPU load and could reduce the space in the imap
>> storage regarding
>> the "singleinstancestore" in imapd.conf if handled
>> appropriately.(divided by 3 with my own experience)
>>
>>
>> Regards.
>
> Hi,
>
>   I mitigated (or solved?) the issue by editing master.cf.template and
> changing this line:
>
> kolabmailboxfilter     unix  -       n       n       -      -        pipe
> user=kolab-n null_sender= argv=/kolab/bin/php
>
> to:
>
> kolabmailboxfilter     unix  -       n       n       -       2       pipe
> user=kolab-n null_sender= argv=/kolab/bin/php
>
>
> Given that amavisd gets only 2 emails at a time, I thought 2 was a good place
> to start.

I believe that is a sensible safeguard.

@thomas, bernhard: Should we add this as a default?

Cheers,

Gunnar

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


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-users/attachments/20081227/d7bdf934/attachment.bin

From Lucidblue0 at gmail.com  Sat Dec 27 23:25:58 2008
From: Lucidblue0 at gmail.com (Lucidblue0@gmail.com)
Date: Sat, 27 Dec 2008 22:25:58 +0000
Subject: export/import annotations.db
Message-ID: <00221532c8accbe5f6045f0eb9bb@google.com>

Thanks Alain,

this is the output of the >rpm -qa "bdb*" "db*":

Current Server:
dbus-1-mono-0.63-28
dbus-1-1.0.0-7
dbus-1-glib-0.71-26
db-4.4.20-16
dbus-1-x11-1.0.0-7
dbus-1-python-0.71-28
db-utils-4.4.20-16

New Server:

dbus-1-glib-0.74-25
dbus-1-1.0.2-59
db-utils-4.5.20-29


-- I don't know what I'm looking for here, I wouldn't imagine any of the  
dbus packages would have anything to do with it, the db-utils is newer, and  
I'm missing the db-?.?.?? package, must not be used in the new install (I'm  
going non gui because it just wastes space)...

I'll try the script stuff after trying to just copy it manually and see if  
it yells again..

thanks,
-Skip

On Dec 27, 2008 1:35am, Alain Spineux <aspineux at gmail.com> wrote:
> On Sat, Dec 27, 2008 at 8:54 AM, Lucidblue0 at gmail.com> wrote:
>
> > Hi all,
>
> >
>
> > I'm trying to migrate a current install of 2.1 to a 2.2 server.
>
> >
>
> > I first exported the LDAP on the original system. I ran kolab_bootstrap  
-b
>
> > on the new system and then cleared out the new LDAP, changed the hashes  
for
>
> > the nobody and manager accounts in the exported ldif file, then had a
>
> > successful import. This finally was the easiest approach, even after  
trying
>
> > to find all the config files, I guess the hash was still different even
>
> > though it was the same pass...
>
> >
>
> > Next I was able to export and then import the mailboxes.db.
>
> >
>
> > The last vital step (aside from rsync'ing the mail), is to somehow copy  
the
>
> > annotations.db, I remember when I tried to do this in the past, I just
>
> > copied the file and I was getting DB_ERROR's in the log files.
>
> >
>
> > After much googling, I'm not seeing anything that actually mentions how  
to
>
> > do this, all the backup docs I've found just skip over it, saying "and  
you
>
> > might want to backup the annotations.db too".
>
>
>
> Yes, you have to copy the annotation.db too
>
>
>
> Happy New Year !
>
>
>
> >
>
> > Should I be able to just copy that file and put it into the new  
install? I
>
> > have multiple calendar and contact folders on group account and also  
one or
>
> > more per user account.
>
> >
>
> > Any ideas about this would be great. The migration is going from a SuSE  
10.2
>
> > native (Kolab 2.1) to a SuSE 10.3 native (Kolab 2.2).
>
>
>
> .... hum, it depent the Berkely DB package, run this on both machine and  
compare
>
>
>
> # rpm -qa "bdb*" "db*"
>
>
>
> If they is enought different then it could be not compatible.
>
>
>
> If so here it part of my backup/restore restore script :
>
>
>
> # backup
>
> su $eg_cyrus_user -c "/kolab/bin/cvt_cyrusdb $ANNOTATIONS_DB
>
> berkeley $ANNOTATIONS_BAK skiplist"
>
>
>
> # restore
>
> chown $eg_cyrus_user.$eg_cyrus_user $ANNOTATIONS_BAK
>
> su $eg_cyrus_user -c "/kolab/bin/cvt_cyrusdb $ANNOTATIONS_BAK
>
> skiplist $ANNOTATIONS_DB berkeley"
>
>
>
>
>
> >
>
> > Thanks,
>
> > -Skip
>
> > _______________________________________________
>
> > 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
>
>
>
> _______________________________________________
>
> 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/20081227/95649cbc/attachment.html

From aspineux at gmail.com  Sun Dec 28 14:25:06 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sun, 28 Dec 2008 14:25:06 +0100
Subject: export/import annotations.db
In-Reply-To: <002215046c8bb0eedb045f09edff@google.com>
References: <002215046c8bb0eedb045f09edff@google.com>
Message-ID: <71fe4e760812280525v14ed6591wccead6821e77c7c3@mail.gmail.com>

On Sat, Dec 27, 2008 at 5:42 PM,  <Lucidblue0 at gmail.com> wrote:
> Thanks, I'll look into this on monday or sooner if I get the chance. It
> looks as if the backup/restore snippet is converting the annotations.db to
> skiplist and then back again?

Yes that's right. "flat" format could do the trick too (I suppose)

>
> Thanks for the help... Happy New Year! :-)
>
> On Dec 27, 2008 1:35am, Alain Spineux <aspineux at gmail.com> wrote:
>> On Sat, Dec 27, 2008 at 8:54 AM,  Lucidblue0 at gmail.com> wrote:
>>
>> > Hi all,
>>
>> >
>>
>> > I'm trying to migrate a current install of 2.1 to a 2.2 server.
>>
>> >
>>
>> > I first exported the LDAP on the original system. I ran kolab_bootstrap
>> > -b
>>
>> > on the new system and then cleared out the new LDAP, changed the hashes
>> > for
>>
>> > the nobody and manager accounts in the exported ldif file, then had a
>>
>> > successful import. This finally was the easiest approach, even after
>> > trying
>>
>> > to find all the config files, I guess the hash was still different even
>>
>> > though it was the same pass...
>>
>> >
>>
>> > Next I was able to export and then import the mailboxes.db.
>>
>> >
>>
>> > The last vital step (aside from rsync'ing the mail), is to somehow copy
>> > the
>>
>> > annotations.db, I remember when I tried to do this in the past, I just
>>
>> > copied the file and I was getting DB_ERROR's in the log files.
>>
>> >
>>
>> > After much googling, I'm not seeing anything that actually mentions how
>> > to
>>
>> > do this, all the backup docs I've found just skip over it, saying "and
>> > you
>>
>> > might want to backup the annotations.db too".
>>
>>
>>
>> Yes, you have to copy the annotation.db too
>>
>>
>>
>> Happy New Year !
>>
>>
>>
>> >
>>
>> > Should I be able to just copy that file and put it into the new install?
>> > I
>>
>> > have multiple calendar and contact folders on group account and also one
>> > or
>>
>> > more per user account.
>>
>> >
>>
>> > Any ideas about this would be great. The migration is going from a SuSE
>> > 10.2
>>
>> > native (Kolab 2.1) to a SuSE 10.3 native (Kolab 2.2).
>>
>>
>>
>> .... hum, it depent the Berkely DB package, run this on both machine and
>> compare
>>
>>
>>
>> # rpm -qa "bdb*" "db*"
>>
>>
>>
>> If they is enought different then it could be not compatible.
>>
>>
>>
>> If so here it part of my backup/restore restore script :
>>
>>
>>
>>   # backup
>>
>>   su $eg_cyrus_user -c "/kolab/bin/cvt_cyrusdb $ANNOTATIONS_DB
>>
>> berkeley $ANNOTATIONS_BAK skiplist"
>>
>>
>>
>>   # restore
>>
>>   chown $eg_cyrus_user.$eg_cyrus_user $ANNOTATIONS_BAK
>>
>>   su $eg_cyrus_user -c "/kolab/bin/cvt_cyrusdb $ANNOTATIONS_BAK
>>
>> skiplist $ANNOTATIONS_DB berkeley"
>>
>>
>>
>>
>>
>> >
>>
>> > Thanks,
>>
>> > -Skip
>>
>> > _______________________________________________
>>
>> > 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
>>
>>
>>
>> _______________________________________________
>>
>> 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  Sun Dec 28 14:32:44 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sun, 28 Dec 2008 14:32:44 +0100
Subject: export/import annotations.db
In-Reply-To: <00221532c8accbe5f6045f0eb9bb@google.com>
References: <00221532c8accbe5f6045f0eb9bb@google.com>
Message-ID: <71fe4e760812280532i4ed4aacfv31b1c48f7a4f57a0@mail.gmail.com>

On Sat, Dec 27, 2008 at 11:25 PM,  <Lucidblue0 at gmail.com> wrote:
> Thanks Alain,
>
> this is the output of the >rpm -qa "bdb*" "db*":
>
> Current Server:
> dbus-1-mono-0.63-28
> dbus-1-1.0.0-7
> dbus-1-glib-0.71-26
> db-4.4.20-16
> dbus-1-x11-1.0.0-7
> dbus-1-python-0.71-28
> db-utils-4.4.20-16
>
> New Server:
>
> dbus-1-glib-0.74-25
> dbus-1-1.0.2-59
> db-utils-4.5.20-29

I was expecting a db-?? on your new server !
db-utils-4.4 vs db-utils-4.5 means the version has changed between
your two server.

Anyway I dont know how your version of cyrus-imap is linked with the
berkeley db library in the Suse package
and then wich version it's using !

Anyway doing a conversion in between should always solve the problem
in any case (even if the source and the targed
imap server are identical platforms)

OPS: did I say you have to do the export using the cvt_cyrusdb of the
source server and do the import using the one of the target server ?

Regards

>
>
> -- I don't know what I'm looking for here, I wouldn't imagine any of the
> dbus packages would have anything to do with it, the db-utils is newer, and
> I'm missing the db-?.?.?? package, must not be used in the new install (I'm
> going non gui because it just wastes space)...
>
> I'll try the script stuff after trying to just copy it manually and see if
> it yells again..
>
> thanks,
> -Skip
>
> On Dec 27, 2008 1:35am, Alain Spineux <aspineux at gmail.com> wrote:
>> On Sat, Dec 27, 2008 at 8:54 AM,  Lucidblue0 at gmail.com> wrote:
>>
>> > Hi all,
>>
>> >
>>
>> > I'm trying to migrate a current install of 2.1 to a 2.2 server.
>>
>> >
>>
>> > I first exported the LDAP on the original system. I ran kolab_bootstrap
>> > -b
>>
>> > on the new system and then cleared out the new LDAP, changed the hashes
>> > for
>>
>> > the nobody and manager accounts in the exported ldif file, then had a
>>
>> > successful import. This finally was the easiest approach, even after
>> > trying
>>
>> > to find all the config files, I guess the hash was still different even
>>
>> > though it was the same pass...
>>
>> >
>>
>> > Next I was able to export and then import the mailboxes.db.
>>
>> >
>>
>> > The last vital step (aside from rsync'ing the mail), is to somehow copy
>> > the
>>
>> > annotations.db, I remember when I tried to do this in the past, I just
>>
>> > copied the file and I was getting DB_ERROR's in the log files.
>>
>> >
>>
>> > After much googling, I'm not seeing anything that actually mentions how
>> > to
>>
>> > do this, all the backup docs I've found just skip over it, saying "and
>> > you
>>
>> > might want to backup the annotations.db too".
>>
>>
>>
>> Yes, you have to copy the annotation.db too
>>
>>
>>
>> Happy New Year !
>>
>>
>>
>> >
>>
>> > Should I be able to just copy that file and put it into the new install?
>> > I
>>
>> > have multiple calendar and contact folders on group account and also one
>> > or
>>
>> > more per user account.
>>
>> >
>>
>> > Any ideas about this would be great. The migration is going from a SuSE
>> > 10.2
>>
>> > native (Kolab 2.1) to a SuSE 10.3 native (Kolab 2.2).
>>
>>
>>
>> .... hum, it depent the Berkely DB package, run this on both machine and
>> compare
>>
>>
>>
>> # rpm -qa "bdb*" "db*"
>>
>>
>>
>> If they is enought different then it could be not compatible.
>>
>>
>>
>> If so here it part of my backup/restore restore script :
>>
>>
>>
>>   # backup
>>
>>   su $eg_cyrus_user -c "/kolab/bin/cvt_cyrusdb $ANNOTATIONS_DB
>>
>> berkeley $ANNOTATIONS_BAK skiplist"
>>
>>
>>
>>   # restore
>>
>>   chown $eg_cyrus_user.$eg_cyrus_user $ANNOTATIONS_BAK
>>
>>   su $eg_cyrus_user -c "/kolab/bin/cvt_cyrusdb $ANNOTATIONS_BAK
>>
>> skiplist $ANNOTATIONS_DB berkeley"
>>
>>
>>
>>
>>
>> >
>>
>> > Thanks,
>>
>> > -Skip
>>
>> > _______________________________________________
>>
>> > 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
>>
>>
>>
>> _______________________________________________
>>
>> 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  Sun Dec 28 15:01:17 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sun, 28 Dec 2008 15:01:17 +0100
Subject: [Kolab-devel] Multiple Kolab's php eat all the RAM
In-Reply-To: <20081227182825.16444p7ni4665b40@webmail.pardus.de>
References: <200812231807.41967.dvadell@linuxclusters.com.ar>
	<200812231959.34060.dvadell@linuxclusters.com.ar>
	<71fe4e760812232255h421dbe68j1358196e547f6916@mail.gmail.com>
	<200812262113.52165.dvadell@linuxclusters.com.ar>
	<20081227182825.16444p7ni4665b40@webmail.pardus.de>
Message-ID: <71fe4e760812280601y23e155c3jbf8cc27823a2301e@mail.gmail.com>

On Sat, Dec 27, 2008 at 6:28 PM, Gunnar Wrobel <wrobel at pardus.de> wrote:
> Quoting "Diego M. Vadell" <dvadell at linuxclusters.com.ar>:
>
>> On Wednesday 24 December 2008 04:55:09 Alain Spineux wrote:
>>>
>>> On Tue, Dec 23, 2008 at 10:59 PM, Diego M. Vadell
>>>
>>> <dvadell at linuxclusters.com.ar> wrote:
>>> > Hi
>>> >
>>> >   I think I found it: when I send an email to 30 people inside the
>>> > server
>>> > (locals to the server) I get a lot of kolabmailfilter processess. Is it
>>> > the intended way of doing things?
>>>
>>> Unfortunately yes !
>>> When you send to multiple recipients, one message is "cloned" by
>>> recipients
>>> ! This could be avoided by some more coding.
>>> This would reduce the CPU load and could reduce the space in the imap
>>> storage regarding
>>> the "singleinstancestore" in imapd.conf if handled
>>> appropriately.(divided by 3 with my own experience)
>>>
>>>
>>> Regards.
>>
>> Hi,
>>
>>  I mitigated (or solved?) the issue by editing master.cf.template and
>> changing this line:
>>
>> kolabmailboxfilter     unix  -       n       n       -      -        pipe
>> user=kolab-n null_sender= argv=/kolab/bin/php
>>
>> to:
>>
>> kolabmailboxfilter     unix  -       n       n       -       2       pipe
>> user=kolab-n null_sender= argv=/kolab/bin/php
>>
>>
>> Given that amavisd gets only 2 emails at a time, I thought 2 was a good
>> place
>> to start.
>
> I believe that is a sensible safeguard.
>
> @thomas, bernhard: Should we add this as a default?


And  why not change the code to keep all the recipients within the
same email :-)
No need to let the antivirus scan the same email twice (ore more) !


Regards

>
> Cheers,
>
> Gunnar
>
>>
>> Thanks,
>>  -- Diego
>>
>> _______________________________________________
>> 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 <<
> --------------------------------------------------------------------
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
> _______________________________________________
> 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 Lucidblue0 at gmail.com  Sun Dec 28 18:20:36 2008
From: Lucidblue0 at gmail.com (Lucidblue0@gmail.com)
Date: Sun, 28 Dec 2008 17:20:36 +0000
Subject: export/import annotations.db
Message-ID: <000325579e82998217045f1e934b@google.com>

On Dec 28, 2008 5:32am, Alain Spineux <aspineux at gmail.com> wrote:
> On Sat, Dec 27, 2008 at 11:25 PM, Lucidblue0 at gmail.com> wrote:
>
> > Thanks Alain,
>
> >
>
> > this is the output of the >rpm -qa "bdb*" "db*":
>
> >
>
> > Current Server:
>
> > dbus-1-mono-0.63-28
>
> > dbus-1-1.0.0-7
>
> > dbus-1-glib-0.71-26
>
> > db-4.4.20-16
>
> > dbus-1-x11-1.0.0-7
>
> > dbus-1-python-0.71-28
>
> > db-utils-4.4.20-16
>
> >
>
> > New Server:
>
> >
>
> > dbus-1-glib-0.74-25
>
> > dbus-1-1.0.2-59
>
> > db-utils-4.5.20-29
>
>
>
> I was expecting a db-?? on your new server !
>
> db-utils-4.4 vs db-utils-4.5 means the version has changed between
>
> your two server.
>
>
>
> Anyway I dont know how your version of cyrus-imap is linked with the
>
> berkeley db library in the Suse package
>
> and then wich version it's using !
>
>
>
> Anyway doing a conversion in between should always solve the problem
>
> in any case (even if the source and the targed
>
> imap server are identical platforms)
>
>
>
> OPS: did I say you have to do the export using the cvt_cyrusdb of the
>
> source server and do the import using the one of the target server ?
>

Nope, you didn't mention that, but I'd gathered as much. Sounds like this  
should work, I'll do some testing to see if that's the case.

Even after this gets working, I still need to figure out how to sync up the  
toltec connector with the new server, in talking to Joon, it seems that the  
only way might just be to let toltec push all the old messages onto the new  
server. Apparently there's no way to keep the folder UID's from changing, I  
haven't heard back on my latest email, so that may have been in response to  
my questions about using imapsync to do the work. Any thoughts on this are  
good, I would assume it would be similar issues when dealing with Kontact  
as a client as well...

Thanks
>
>
> Regards
>
>
>
> >
>
> >
>
> > -- I don't know what I'm looking for here, I wouldn't imagine any of the
>
> > dbus packages would have anything to do with it, the db-utils is newer,  
and
>
> > I'm missing the db-?.?.?? package, must not be used in the new install  
(I'm
>
> > going non gui because it just wastes space)...
>
> >
>
> > I'll try the script stuff after trying to just copy it manually and see  
if
>
> > it yells again..
>
> >
>
> > thanks,
>
> > -Skip
>
> >
>
> > On Dec 27, 2008 1:35am, Alain Spineux aspineux at gmail.com> wrote:
>
> >> On Sat, Dec 27, 2008 at 8:54 AM, Lucidblue0 at gmail.com> wrote:
>
> >>
>
> >> > Hi all,
>
> >>
>
> >> >
>
> >>
>
> >> > I'm trying to migrate a current install of 2.1 to a 2.2 server.
>
> >>
>
> >> >
>
> >>
>
> >> > I first exported the LDAP on the original system. I ran  
kolab_bootstrap
>
> >> > -b
>
> >>
>
> >> > on the new system and then cleared out the new LDAP, changed the  
hashes
>
> >> > for
>
> >>
>
> >> > the nobody and manager accounts in the exported ldif file, then had a
>
> >>
>
> >> > successful import. This finally was the easiest approach, even after
>
> >> > trying
>
> >>
>
> >> > to find all the config files, I guess the hash was still different  
even
>
> >>
>
> >> > though it was the same pass...
>
> >>
>
> >> >
>
> >>
>
> >> > Next I was able to export and then import the mailboxes.db.
>
> >>
>
> >> >
>
> >>
>
> >> > The last vital step (aside from rsync'ing the mail), is to somehow  
copy
>
> >> > the
>
> >>
>
> >> > annotations.db, I remember when I tried to do this in the past, I  
just
>
> >>
>
> >> > copied the file and I was getting DB_ERROR's in the log files.
>
> >>
>
> >> >
>
> >>
>
> >> > After much googling, I'm not seeing anything that actually mentions  
how
>
> >> > to
>
> >>
>
> >> > do this, all the backup docs I've found just skip over it,  
saying "and
>
> >> > you
>
> >>
>
> >> > might want to backup the annotations.db too".
>
> >>
>
> >>
>
> >>
>
> >> Yes, you have to copy the annotation.db too
>
> >>
>
> >>
>
> >>
>
> >> Happy New Year !
>
> >>
>
> >>
>
> >>
>
> >> >
>
> >>
>
> >> > Should I be able to just copy that file and put it into the new  
install?
>
> >> > I
>
> >>
>
> >> > have multiple calendar and contact folders on group account and also  
one
>
> >> > or
>
> >>
>
> >> > more per user account.
>
> >>
>
> >> >
>
> >>
>
> >> > Any ideas about this would be great. The migration is going from a  
SuSE
>
> >> > 10.2
>
> >>
>
> >> > native (Kolab 2.1) to a SuSE 10.3 native (Kolab 2.2).
>
> >>
>
> >>
>
> >>
>
> >> .... hum, it depent the Berkely DB package, run this on both machine  
and
>
> >> compare
>
> >>
>
> >>
>
> >>
>
> >> # rpm -qa "bdb*" "db*"
>
> >>
>
> >>
>
> >>
>
> >> If they is enought different then it could be not compatible.
>
> >>
>
> >>
>
> >>
>
> >> If so here it part of my backup/restore restore script :
>
> >>
>
> >>
>
> >>
>
> >> # backup
>
> >>
>
> >> su $eg_cyrus_user -c "/kolab/bin/cvt_cyrusdb $ANNOTATIONS_DB
>
> >>
>
> >> berkeley $ANNOTATIONS_BAK skiplist"
>
> >>
>
> >>
>
> >>
>
> >> # restore
>
> >>
>
> >> chown $eg_cyrus_user.$eg_cyrus_user $ANNOTATIONS_BAK
>
> >>
>
> >> su $eg_cyrus_user -c "/kolab/bin/cvt_cyrusdb $ANNOTATIONS_BAK
>
> >>
>
> >> skiplist $ANNOTATIONS_DB berkeley"
>
> >>
>
> >>
>
> >>
>
> >>
>
> >>
>
> >> >
>
> >>
>
> >> > Thanks,
>
> >>
>
> >> > -Skip
>
> >>
>
> >> > _______________________________________________
>
> >>
>
> >> > 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
>
> >>
>
> >>
>
> >>
>
> >> _______________________________________________
>
> >>
>
> >> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081228/9a4e5c61/attachment.html

From kcaesar at hotmail.com  Tue Dec 30 10:55:26 2008
From: kcaesar at hotmail.com (kiser Caesar)
Date: Tue, 30 Dec 2008 10:55:26 +0100
Subject: Kolab-users Digest, Vol 58, Issue 18
In-Reply-To: <mailman.3857.1229641475.2135.kolab-users@kolab.org>
References: <mailman.3857.1229641475.2135.kolab-users@kolab.org>
Message-ID: <BLU122-W13DDF2819317C4DED3A559A3E70@phx.gbl>




From: kolab-users-request at kolab.org
Subject: Kolab-users Digest, Vol 58, Issue 18
To: kolab-users at kolab.org
Date: Fri, 19 Dec 2008 00:04:35 +0100

Send Kolab-users mailing list submissions to
	kolab-users at kolab.org
 
To subscribe or unsubscribe via the World Wide Web, visit
	https://kolab.org/mailman/listinfo/kolab-users
or, via email, send a message with subject or body 'help' to
	kolab-users-request at kolab.org
 
You can reach the person managing the list at
	kolab-users-owner at kolab.org
 
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Kolab-users digest..."


--Pi?ce jointe du message transmise--
Subject: Creating/deleting folders stopped working
Date: Thu, 18 Dec 2008 10:12:58 -0500
To: kolab-users at kolab.org
From: vladislav.tchernev at broadsign.com

Hi all,
Since recently, I am having a weird problem. When I create a new user via the 
web GIU, kolab reports that the operation is successfull but it doesn't 
create a mailbox for the new user. When I try to delete the newly created 
user the the process hags showing "User Deleted, awaiting cleanup..." in the 
web interface. If I try to create an imap folder manually via cyradm it's 
working. Trying to delete the same folder via the kolab GUI still fails. So 
for some reason kolab is not able to perform any disk related operations. The  
permitions for /kolab/var/imapd/spool/domain/****/user/ looks right. 
Any ideas?
 
Regrads
Vlad
 
 


--Pi?ce jointe du message transmise--
Subject: SyncML
Date: Thu, 18 Dec 2008 11:35:49 -0500
To: kolab-users at kolab.org
From: christian.tardif at servinfo.ca








Hi,



Is SyncML known to work under 2.2.1b1?  If so, what are the needed
infos to make it work?



Thanks,

-- 




 
Christian Tardif






--Pi?ce jointe du message transmise--
Subject: RE: cannot delete shared calendar with spaces in the name
Date: Thu, 18 Dec 2008 22:13:20 +0100
To: kolab-users at kolab.org
From: wrobel at pardus.de

Quoting Lucas Hendricks <LHendricks at austinent.com>:
 
> I was able to delete one shared folder with a space, and now I only have 1
> left which seems to be a phantom shared folder which indicates as far as
> deleting the folder: an isolated problem not related to the space in the
> name.
>
> Retrieving an ics file via the subscription link does not work for shared
> folders with a space in the name for me, though.  Using IE as a
> troubleshooting tool to connect to the Debian 4.0 binary install of 2.2:
>
 
Created https://www.intevation.de/roundup/kolab/issue3330
 
Cheers,
 
Gunnar
 
> Shared folder name: mycal
> type: events
> https://kolab.mydomain.com/horde/rpc.php/kronolith/shared.mycal.ics
> This works fine and prompts me to download the ics file through IE
>
> Shared folder name: my calendar
> type: events
> https://kolab.mydomain.com/horde/rpc.php/kronolith/shared.my%20calendar.ics
> This gives a blank response with no file download prompt
>
> I think I might have made the phantom folder during 2.2-rc3 and done an
> upgrade from that to 2.2 which I could easily have done incorrectly to
> prevent the issue (I might have marked it to delete then done the upgrade
> before it ran the cleanup or something).  Since that is isolated to the one
> phantom folder and I plan on doing a clean wipe and fresh install with 2.2.1
> it probably doesn't need any more attention.
>
> Info for if you are just interested, though: folder appears in horde as:
> [anonymous]shared.doc surgery
>
> I cannot delete it while logged on to the horde as my only user account nor
> as the manager logon, and it does not appear in shared folders in the
> web-admin interface logged on as the default manager account.  I created a
> maintainer account and administrator account, neither of which even has the
> calendar show up as visible either in horde or the web-admin interface for
> kolab.
>
> Lucas
>
> -----Original Message-----
> From: Gunnar Wrobel [mailto:wrobel at pardus.de]
> Sent: Friday, December 05, 2008 2:36 AM
> To: kolab-users at kolab.org
> Subject: Re: cannot delete shared calendar with spaces in the name
>
> Hi Lucas,
>
> Quoting Lucas Hendricks <LHendricks at austinent.com>:
>
>>   font-family: Arial;">Hello,  font-family: Arial;">
>> font-family: Arial;">I have created some shared calendars in the
>> horde admin interface that included spaces in the name and they
> seem
>> buggy.
>
> In the horde admin interface? I guess you rather mean the web-admin, right?
>
>> I could not subscribe to them via url and they will not let
>> me delete them either through admin or horde.
>
> How exactly do you try to delete it in horde? Did you give admin
> rights to the user trying to delete the shared folder?
>
>> When I set them to
>> delete in the admin interface they say "Folder deleted,
>> awaiting cleanup..." but then never delete and after cleanup
>> runs they're still there.
>
> What kind of a cleanup run? Does your kolabd run? kolabd should be
> responsible for removing the folders.
>
>>
>>  font-family: Arial;">   font-family: Arial;">I'm only on a beta
>> install and I will most
>> likely do a clean install when 2.2.1 comes out so it's not an issue
>> that needs much thought wasted on it (I will just not use spaces in
>> folder names in the future).   I just wanted to check here to see
> if
>> someone knows how to fix this off the top of their heads or if it
>> should be considered a feature.
>
> Deleting such folders works fine for me (albeit on a 2.2.1
> installation). I don't think we had some changes in that area though
> and I would expect it to also work on 2.2.0. I could check 2.2.0 also
> if required.
>
> Cheers,
>
> Gunnar
>
>>
>>  font-family: Arial;">   style="font-size: 10pt; font-family:
>> Arial; color: blue;">Lucas
>> Hendricks
>
> --
> ____ 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 <<
> --------------------------------------------------------------------
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
> _______________________________________________
> 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://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 <<
--------------------------------------------------------------------
 
 
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


--Pi?ce jointe du message transmise--
Subject: Re: How I can connect calendars ?
Date: Thu, 18 Dec 2008 23:55:08 +0100
To: kolab-users at kolab.org
From: wrobel at pardus.de

 
Quoting kiser Caesar <kcaesar at hotmail.com>:
 
> Hello,
>
> I have certainly a stupid question, but I want to know if it's
> possible to connect directly to calendars with ICS or Webdav under
> thunderbird + lightning mod ?
 
You can do this via the Kolab web client. The URLs look like this:
 
https://example.com/client/rpc.php/kronolith/wrobel at example.com/wrobel at example.com.ics
 
for a default Calendar and like this
 
https://example.com/client/rpc.php/kronolith/wrobel at example.com/Kalender.ics
 
for other calendars.
 
Cheers,
 
Gunnar

Hi Gunnar !

I can't connect some calendars with this way under Thunderbird + lighting. It's not working.. :'


>
> Thank :)
>
>
> -------------------------
> T?l?phonez gratuitement ? tous vos proches avec Windows Live
> Messenger  !
href=\"http://www.windowslive.fr/messenger/1.asp\">T?l?chargez-le
> maintenant !
 
-- 
____ 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 <<
--------------------------------------------------------------------
 
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


--Pi?ce jointe du message transmise--
Subject: Re: SyncML
Date: Fri, 19 Dec 2008 00:03:16 +0100
To: kolab-users at kolab.org
From: wrobel at pardus.de

 
Quoting Christian Tardif <christian.tardif at servinfo.ca>:
 
> Hi,
>  Is SyncML known to work under 2.2.1b1?  If so, what are the needed
> infos to make it work?
 
It works, yes. Probably not with each and every possible device but  
that is a problem of SyncML itself not so much of the implementation.
 
For infos see:
 
http://wiki.horde.org/SyncHowTo
 
Cheers,
 
Gunnar
 
>  Thanks,
> -- 
>   CHRISTIAN TARDIF
>
 
-- 
____ 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 <<
--------------------------------------------------------------------
 
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


--Pi?ce jointe du message transmise--
Subject: Re: Creating/deleting folders stopped working
Date: Fri, 19 Dec 2008 00:04:28 +0100
To: kolab-users at kolab.org
From: wrobel at pardus.de

Quoting Vladislav Tchernev <vladislav.tchernev at broadsign.com>:
 
> Hi all,
> Since recently, I am having a weird problem. When I create a new user via the
> web GIU, kolab reports that the operation is successfull but it doesn't
> create a mailbox for the new user. When I try to delete the newly created
> user the the process hags showing "User Deleted, awaiting cleanup..." in the
> web interface. If I try to create an imap folder manually via cyradm it's
> working. Trying to delete the same folder via the kolab GUI still fails. So
> for some reason kolab is not able to perform any disk related operations. The
> permitions for /kolab/var/imapd/spool/domain/****/user/ looks right.
> Any ideas?
 
Sounds like the kolabd process broke down. Try to restart it with:
 
/kolab/bin/openpkg rc kolabd restart
 
>
> Regrads
> Vlad
>
> _______________________________________________
> 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 <<
--------------------------------------------------------------------
 
 
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

_________________________________________________________________
T?l?phonez gratuitement ? tous vos proches avec Windows Live Messenger? !? T?l?chargez-le maintenant !?
http://www.windowslive.fr/messenger/1.asp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081230/c67f9ff8/attachment.html

From devgioiatech at gmail.com  Tue Dec 30 15:11:36 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Tue, 30 Dec 2008 15:11:36 +0100
Subject: kolab user for samba access
In-Reply-To: <d53357b70812142354y62dafb05yfa4839fcca8a6f27@mail.gmail.com>
References: <d53357b70812111228v494cff2aua40f7d3420e0677d@mail.gmail.com>
	<1229068001l.6902l.0l@pc-adr2.lios-koeln.de>
	<4945663C.40501@gmail.com>
	<d53357b70812142354y62dafb05yfa4839fcca8a6f27@mail.gmail.com>
Message-ID: <d53357b70812300611v5edd751cj8d926326e1bc83aa@mail.gmail.com>

Hi all,
i tried the solution proposed...

I tried it on a single machine and the process goes forward without
any problem, but when i try it on two different server i've the
following error on

# smbldap-populate -b guest -l 65534 -a myadmin

on the samba server.

It returns:

Populating LDAP directory for domain DEMO-TST
(S-1-5-21-3554714494-4109302710-169134865)
(using builtin directory structure)

Use of uninitialized value in concatenation (.) or string at
/usr/local/sbin/smbldap-populate line 173.
adding new entry: cn=internal,dc=demo,dc=tst
failed to add entry: objectclass: value #0 invalid per syntax at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 2.
entry dc=demo,dc=tst already exist.
adding new entry: ou=SmbGroups,cn=internal,dc=demo,dc=tst
failed to add entry: modifications require authentication at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 4.
adding new entry: ou=SmbComputers,cn=internal,dc=demo,dc=tst
failed to add entry: modifications require authentication at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 5.
adding new entry: ou=SmbIdmap,cn=internal,dc=demo,dc=tst
failed to add entry: modifications require authentication at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 6.
adding new entry: uid=myadmin,dc=demo,dc=tst
failed to add entry: modifications require authentication at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 7.
adding new entry: uid=guest,dc=demo,dc=tst
failed to add entry: modifications require authentication at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 8.
adding new entry: cn=Domain Admins,ou=SmbGroups,cn=internal,dc=demo,dc=tst
failed to add entry: modifications require authentication at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 9.
adding new entry: cn=Domain Users,ou=SmbGroups,cn=internal,dc=demo,dc=tst
failed to add entry: modifications require authentication at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 10.
adding new entry: cn=Domain Guests,ou=SmbGroups,cn=internal,dc=demo,dc=tst
failed to add entry: modifications require authentication at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 11.
adding new entry: cn=Domain Computers,ou=SmbGroups,cn=internal,dc=demo,dc=tst
failed to add entry: modifications require authentication at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 12.
adding new entry: cn=Administrators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
failed to add entry: modifications require authentication at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 16.
adding new entry: cn=Account Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
failed to add entry: modifications require authentication at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 18.
adding new entry: cn=Print Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
failed to add entry: modifications require authentication at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 19.
adding new entry: cn=Backup Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
failed to add entry: modifications require authentication at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 20.
adding new entry: cn=Replicators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
failed to add entry: modifications require authentication at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 21.
adding new entry: sambaDomainName=DEMO-TST,cn=internal,dc=demo,dc=tst
failed to add entry: modifications require authentication at
/usr/local/sbin/smbldap-populate line 498, <GEN1> line 21.

Please provide a password for the domain myadmin:
/usr/local/sbin/smbldap-passwd: user myadmin doesn't exist

I use same user myadmin as administrator.

Any idea?

2008/12/15 Antonio Straziota <devgioiatech at gmail.com>:
> I'm going to try it... ;)
>
> thanks to all for the link... i was searching for samba-openldap and i
> haven't found this tutorial.
> I'll give you a feedback asap.
>
> bye.
>
>
> 2008/12/14 schmerold1 at gmail.com <schmerold1 at gmail.com>:
>> Any feedback regarding following the Ubuntu directions on a Centos 5.2
>> box are appreciated.
>>
>> Ubuntu directions:
>> http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy
>>
>>
>> Albrecht Dre? wrote:
>>> Am 11.12.2008 21:28:50 schrieb(en) Antonio Straziota:
>>>
>>>> i need to make kolab user capable to access samba shares. I'm trying
>>>> to authenticate samba user against kolab openldap following some
>>>> tutorial found on the web, but any attempt fails.
>>>>
>>>
>>> Did you try
>>> <http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy>?
>>> Works nicely for me...
>>>
>>> Hth,
>>> Albrecht.
>>>
>>> _______________________________________________
>>> 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
>>
>



From devgioiatech at gmail.com  Tue Dec 30 17:07:07 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Tue, 30 Dec 2008 17:07:07 +0100
Subject: kolab user for samba access
In-Reply-To: <d53357b70812300611v5edd751cj8d926326e1bc83aa@mail.gmail.com>
References: <d53357b70812111228v494cff2aua40f7d3420e0677d@mail.gmail.com>
	<1229068001l.6902l.0l@pc-adr2.lios-koeln.de>
	<4945663C.40501@gmail.com>
	<d53357b70812142354y62dafb05yfa4839fcca8a6f27@mail.gmail.com>
	<d53357b70812300611v5edd751cj8d926326e1bc83aa@mail.gmail.com>
Message-ID: <d53357b70812300807y4a8740dhd084c00b2d1a6c88@mail.gmail.com>

another issue:
when i check smbd and nmbd status i get:

smbd dead but pid file exists
nmbd dead but pid file exists


Do you know why?
Thanks.

2008/12/30 Antonio Straziota <devgioiatech at gmail.com>:
> Hi all,
> i tried the solution proposed...
>
> I tried it on a single machine and the process goes forward without
> any problem, but when i try it on two different server i've the
> following error on
>
> # smbldap-populate -b guest -l 65534 -a myadmin
>
> on the samba server.
>
> It returns:
>
> Populating LDAP directory for domain DEMO-TST
> (S-1-5-21-3554714494-4109302710-169134865)
> (using builtin directory structure)
>
> Use of uninitialized value in concatenation (.) or string at
> /usr/local/sbin/smbldap-populate line 173.
> adding new entry: cn=internal,dc=demo,dc=tst
> failed to add entry: objectclass: value #0 invalid per syntax at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 2.
> entry dc=demo,dc=tst already exist.
> adding new entry: ou=SmbGroups,cn=internal,dc=demo,dc=tst
> failed to add entry: modifications require authentication at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 4.
> adding new entry: ou=SmbComputers,cn=internal,dc=demo,dc=tst
> failed to add entry: modifications require authentication at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 5.
> adding new entry: ou=SmbIdmap,cn=internal,dc=demo,dc=tst
> failed to add entry: modifications require authentication at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 6.
> adding new entry: uid=myadmin,dc=demo,dc=tst
> failed to add entry: modifications require authentication at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 7.
> adding new entry: uid=guest,dc=demo,dc=tst
> failed to add entry: modifications require authentication at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 8.
> adding new entry: cn=Domain Admins,ou=SmbGroups,cn=internal,dc=demo,dc=tst
> failed to add entry: modifications require authentication at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 9.
> adding new entry: cn=Domain Users,ou=SmbGroups,cn=internal,dc=demo,dc=tst
> failed to add entry: modifications require authentication at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 10.
> adding new entry: cn=Domain Guests,ou=SmbGroups,cn=internal,dc=demo,dc=tst
> failed to add entry: modifications require authentication at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 11.
> adding new entry: cn=Domain Computers,ou=SmbGroups,cn=internal,dc=demo,dc=tst
> failed to add entry: modifications require authentication at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 12.
> adding new entry: cn=Administrators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
> failed to add entry: modifications require authentication at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 16.
> adding new entry: cn=Account Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
> failed to add entry: modifications require authentication at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 18.
> adding new entry: cn=Print Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
> failed to add entry: modifications require authentication at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 19.
> adding new entry: cn=Backup Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
> failed to add entry: modifications require authentication at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 20.
> adding new entry: cn=Replicators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
> failed to add entry: modifications require authentication at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 21.
> adding new entry: sambaDomainName=DEMO-TST,cn=internal,dc=demo,dc=tst
> failed to add entry: modifications require authentication at
> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 21.
>
> Please provide a password for the domain myadmin:
> /usr/local/sbin/smbldap-passwd: user myadmin doesn't exist
>
> I use same user myadmin as administrator.
>
> Any idea?
>
> 2008/12/15 Antonio Straziota <devgioiatech at gmail.com>:
>> I'm going to try it... ;)
>>
>> thanks to all for the link... i was searching for samba-openldap and i
>> haven't found this tutorial.
>> I'll give you a feedback asap.
>>
>> bye.
>>
>>
>> 2008/12/14 schmerold1 at gmail.com <schmerold1 at gmail.com>:
>>> Any feedback regarding following the Ubuntu directions on a Centos 5.2
>>> box are appreciated.
>>>
>>> Ubuntu directions:
>>> http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy
>>>
>>>
>>> Albrecht Dre? wrote:
>>>> Am 11.12.2008 21:28:50 schrieb(en) Antonio Straziota:
>>>>
>>>>> i need to make kolab user capable to access samba shares. I'm trying
>>>>> to authenticate samba user against kolab openldap following some
>>>>> tutorial found on the web, but any attempt fails.
>>>>>
>>>>
>>>> Did you try
>>>> <http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy>?
>>>> Works nicely for me...
>>>>
>>>> Hth,
>>>> Albrecht.
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>
>



From devgioiatech at gmail.com  Wed Dec 31 18:33:26 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Wed, 31 Dec 2008 18:33:26 +0100
Subject: kolab user for samba access
In-Reply-To: <d53357b70812300807y4a8740dhd084c00b2d1a6c88@mail.gmail.com>
References: <d53357b70812111228v494cff2aua40f7d3420e0677d@mail.gmail.com>
	<1229068001l.6902l.0l@pc-adr2.lios-koeln.de>
	<4945663C.40501@gmail.com>
	<d53357b70812142354y62dafb05yfa4839fcca8a6f27@mail.gmail.com>
	<d53357b70812300611v5edd751cj8d926326e1bc83aa@mail.gmail.com>
	<d53357b70812300807y4a8740dhd084c00b2d1a6c88@mail.gmail.com>
Message-ID: <d53357b70812310933i20411ef7t8138768e48b25b25@mail.gmail.com>

i've solved.
the problem was in smbldap_bind.conf

i had
masterDN="cn=internal,cn=manager,dc=demo,dc=tst"

instead of

masterDN="cn=manager,cn=internal,dc=demo,dc=tst"

bye!

Happy new year! ;)



2008/12/30 Antonio Straziota <devgioiatech at gmail.com>:
> another issue:
> when i check smbd and nmbd status i get:
>
> smbd dead but pid file exists
> nmbd dead but pid file exists
>
>
> Do you know why?
> Thanks.
>
> 2008/12/30 Antonio Straziota <devgioiatech at gmail.com>:
>> Hi all,
>> i tried the solution proposed...
>>
>> I tried it on a single machine and the process goes forward without
>> any problem, but when i try it on two different server i've the
>> following error on
>>
>> # smbldap-populate -b guest -l 65534 -a myadmin
>>
>> on the samba server.
>>
>> It returns:
>>
>> Populating LDAP directory for domain DEMO-TST
>> (S-1-5-21-3554714494-4109302710-169134865)
>> (using builtin directory structure)
>>
>> Use of uninitialized value in concatenation (.) or string at
>> /usr/local/sbin/smbldap-populate line 173.
>> adding new entry: cn=internal,dc=demo,dc=tst
>> failed to add entry: objectclass: value #0 invalid per syntax at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 2.
>> entry dc=demo,dc=tst already exist.
>> adding new entry: ou=SmbGroups,cn=internal,dc=demo,dc=tst
>> failed to add entry: modifications require authentication at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 4.
>> adding new entry: ou=SmbComputers,cn=internal,dc=demo,dc=tst
>> failed to add entry: modifications require authentication at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 5.
>> adding new entry: ou=SmbIdmap,cn=internal,dc=demo,dc=tst
>> failed to add entry: modifications require authentication at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 6.
>> adding new entry: uid=myadmin,dc=demo,dc=tst
>> failed to add entry: modifications require authentication at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 7.
>> adding new entry: uid=guest,dc=demo,dc=tst
>> failed to add entry: modifications require authentication at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 8.
>> adding new entry: cn=Domain Admins,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>> failed to add entry: modifications require authentication at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 9.
>> adding new entry: cn=Domain Users,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>> failed to add entry: modifications require authentication at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 10.
>> adding new entry: cn=Domain Guests,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>> failed to add entry: modifications require authentication at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 11.
>> adding new entry: cn=Domain Computers,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>> failed to add entry: modifications require authentication at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 12.
>> adding new entry: cn=Administrators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>> failed to add entry: modifications require authentication at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 16.
>> adding new entry: cn=Account Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>> failed to add entry: modifications require authentication at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 18.
>> adding new entry: cn=Print Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>> failed to add entry: modifications require authentication at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 19.
>> adding new entry: cn=Backup Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>> failed to add entry: modifications require authentication at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 20.
>> adding new entry: cn=Replicators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>> failed to add entry: modifications require authentication at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 21.
>> adding new entry: sambaDomainName=DEMO-TST,cn=internal,dc=demo,dc=tst
>> failed to add entry: modifications require authentication at
>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 21.
>>
>> Please provide a password for the domain myadmin:
>> /usr/local/sbin/smbldap-passwd: user myadmin doesn't exist
>>
>> I use same user myadmin as administrator.
>>
>> Any idea?
>>
>> 2008/12/15 Antonio Straziota <devgioiatech at gmail.com>:
>>> I'm going to try it... ;)
>>>
>>> thanks to all for the link... i was searching for samba-openldap and i
>>> haven't found this tutorial.
>>> I'll give you a feedback asap.
>>>
>>> bye.
>>>
>>>
>>> 2008/12/14 schmerold1 at gmail.com <schmerold1 at gmail.com>:
>>>> Any feedback regarding following the Ubuntu directions on a Centos 5.2
>>>> box are appreciated.
>>>>
>>>> Ubuntu directions:
>>>> http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy
>>>>
>>>>
>>>> Albrecht Dre? wrote:
>>>>> Am 11.12.2008 21:28:50 schrieb(en) Antonio Straziota:
>>>>>
>>>>>> i need to make kolab user capable to access samba shares. I'm trying
>>>>>> to authenticate samba user against kolab openldap following some
>>>>>> tutorial found on the web, but any attempt fails.
>>>>>>
>>>>>
>>>>> Did you try
>>>>> <http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy>?
>>>>> Works nicely for me...
>>>>>
>>>>> Hth,
>>>>> Albrecht.
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>
>>>
>>
>



From devgioiatech at gmail.com  Wed Dec 31 19:50:21 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Wed, 31 Dec 2008 19:50:21 +0100
Subject: kolab user for samba access
In-Reply-To: <d53357b70812310933i20411ef7t8138768e48b25b25@mail.gmail.com>
References: <d53357b70812111228v494cff2aua40f7d3420e0677d@mail.gmail.com>
	<1229068001l.6902l.0l@pc-adr2.lios-koeln.de>
	<4945663C.40501@gmail.com>
	<d53357b70812142354y62dafb05yfa4839fcca8a6f27@mail.gmail.com>
	<d53357b70812300611v5edd751cj8d926326e1bc83aa@mail.gmail.com>
	<d53357b70812300807y4a8740dhd084c00b2d1a6c88@mail.gmail.com>
	<d53357b70812310933i20411ef7t8138768e48b25b25@mail.gmail.com>
Message-ID: <d53357b70812311050o10128ce9g749fdd6d1ce1787f@mail.gmail.com>

hi again :)

my problem now is in user.php...
when i try to create a user (or modify existing one) i got an empty page...

thanks for the help and again HAPPY NEW YEAR.

2008/12/31 Antonio Straziota <devgioiatech at gmail.com>:
> i've solved.
> the problem was in smbldap_bind.conf
>
> i had
> masterDN="cn=internal,cn=manager,dc=demo,dc=tst"
>
> instead of
>
> masterDN="cn=manager,cn=internal,dc=demo,dc=tst"
>
> bye!
>
> Happy new year! ;)
>
>
>
> 2008/12/30 Antonio Straziota <devgioiatech at gmail.com>:
>> another issue:
>> when i check smbd and nmbd status i get:
>>
>> smbd dead but pid file exists
>> nmbd dead but pid file exists
>>
>>
>> Do you know why?
>> Thanks.
>>
>> 2008/12/30 Antonio Straziota <devgioiatech at gmail.com>:
>>> Hi all,
>>> i tried the solution proposed...
>>>
>>> I tried it on a single machine and the process goes forward without
>>> any problem, but when i try it on two different server i've the
>>> following error on
>>>
>>> # smbldap-populate -b guest -l 65534 -a myadmin
>>>
>>> on the samba server.
>>>
>>> It returns:
>>>
>>> Populating LDAP directory for domain DEMO-TST
>>> (S-1-5-21-3554714494-4109302710-169134865)
>>> (using builtin directory structure)
>>>
>>> Use of uninitialized value in concatenation (.) or string at
>>> /usr/local/sbin/smbldap-populate line 173.
>>> adding new entry: cn=internal,dc=demo,dc=tst
>>> failed to add entry: objectclass: value #0 invalid per syntax at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 2.
>>> entry dc=demo,dc=tst already exist.
>>> adding new entry: ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>> failed to add entry: modifications require authentication at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 4.
>>> adding new entry: ou=SmbComputers,cn=internal,dc=demo,dc=tst
>>> failed to add entry: modifications require authentication at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 5.
>>> adding new entry: ou=SmbIdmap,cn=internal,dc=demo,dc=tst
>>> failed to add entry: modifications require authentication at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 6.
>>> adding new entry: uid=myadmin,dc=demo,dc=tst
>>> failed to add entry: modifications require authentication at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 7.
>>> adding new entry: uid=guest,dc=demo,dc=tst
>>> failed to add entry: modifications require authentication at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 8.
>>> adding new entry: cn=Domain Admins,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>> failed to add entry: modifications require authentication at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 9.
>>> adding new entry: cn=Domain Users,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>> failed to add entry: modifications require authentication at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 10.
>>> adding new entry: cn=Domain Guests,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>> failed to add entry: modifications require authentication at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 11.
>>> adding new entry: cn=Domain Computers,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>> failed to add entry: modifications require authentication at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 12.
>>> adding new entry: cn=Administrators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>> failed to add entry: modifications require authentication at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 16.
>>> adding new entry: cn=Account Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>> failed to add entry: modifications require authentication at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 18.
>>> adding new entry: cn=Print Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>> failed to add entry: modifications require authentication at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 19.
>>> adding new entry: cn=Backup Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>> failed to add entry: modifications require authentication at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 20.
>>> adding new entry: cn=Replicators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>> failed to add entry: modifications require authentication at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 21.
>>> adding new entry: sambaDomainName=DEMO-TST,cn=internal,dc=demo,dc=tst
>>> failed to add entry: modifications require authentication at
>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 21.
>>>
>>> Please provide a password for the domain myadmin:
>>> /usr/local/sbin/smbldap-passwd: user myadmin doesn't exist
>>>
>>> I use same user myadmin as administrator.
>>>
>>> Any idea?
>>>
>>> 2008/12/15 Antonio Straziota <devgioiatech at gmail.com>:
>>>> I'm going to try it... ;)
>>>>
>>>> thanks to all for the link... i was searching for samba-openldap and i
>>>> haven't found this tutorial.
>>>> I'll give you a feedback asap.
>>>>
>>>> bye.
>>>>
>>>>
>>>> 2008/12/14 schmerold1 at gmail.com <schmerold1 at gmail.com>:
>>>>> Any feedback regarding following the Ubuntu directions on a Centos 5.2
>>>>> box are appreciated.
>>>>>
>>>>> Ubuntu directions:
>>>>> http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy
>>>>>
>>>>>
>>>>> Albrecht Dre? wrote:
>>>>>> Am 11.12.2008 21:28:50 schrieb(en) Antonio Straziota:
>>>>>>
>>>>>>> i need to make kolab user capable to access samba shares. I'm trying
>>>>>>> to authenticate samba user against kolab openldap following some
>>>>>>> tutorial found on the web, but any attempt fails.
>>>>>>>
>>>>>>
>>>>>> Did you try
>>>>>> <http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy>?
>>>>>> Works nicely for me...
>>>>>>
>>>>>> Hth,
>>>>>> Albrecht.
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>
>>>>
>>>
>>
>