From kolab-issues at intevation.de  Mon Dec  1 11:47:44 2008
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Mon, 01 Dec 2008 10:47:44 +0000
Subject: [Kolab-devel] [issue3278] Filteraction to set a carboncopy (cc)
	reciepient.
Message-ID: <1228128464.58.0.0959150338197.issue3278@intevation.de>


New submission from Bernhard Reiter <bernhard at intevation.de>:

We want to solve the use case to be able to send an
email with set identity, template and carbon copy recipient
via press of a button.

Missing for this is a filter action that set the carbon copy recipient
to be used if this emails is replied to automatically at least.
To be more useful I also hope that it will work, if it is manually
replied to.

Testcase:
* set up a filter that matches everything,
* make it manual with a keypress
* set filteractions for identity (which has a template) 
* set filteraction for cc
* set a filter action for forwarding (with a button press) to a recipient
check that identity, template, cc: and to: is all used when pressing
the button on a selected email.
Kontact: 1.2.9 (enterprise35 20081121.887372)

----------
assignedto: till
messages: 17849
nosy: bernhard, till
priority: urgent
status: unread
title: Filteraction to set a carboncopy (cc) reciepient.
topic: kde client, kkc
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3278>
___________________________________________________


From kolab-issues at intevation.de  Mon Dec  1 15:05:26 2008
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Mon, 01 Dec 2008 14:05:26 +0000
Subject: [Kolab-devel] [issue3279] In the creation of a new appointment
	kontact sometimes hangs.
Message-ID: <1228140326.85.0.329804321673.issue3279@intevation.de>


New submission from Ludwig Reiter <ludwig at intevation.de>:

enterprise4 Kontact-Installer_20081128.exe
          gpg4win1.9.12-beta.exe 
kdelibs-branch  889739
kdepimlibs-branch  889781
kdepim-branch  890007
i10n-kde4  890045
kowi-crypto-files_gpg4win1.9.11-beta

In a new appointment creation dialog, switching between General and Attendee tab
and changeing the event time hangs kontact.

Test:
1. Start to create a new event.
2. Enter an appointment name.
3. Switch to the "Attendee" tab.
4. Switch back to the "General" tab.
5. Change the time via textfield.
6. Switch to the "Attendee" tab.
=> Now kontacts hangs.

----------
assignedto: till
messages: 17859
nosy: bh, ludwig, till
priority: urgent
status: unread
title: In the creation of a new appointment kontact sometimes hangs.
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3279>
___________________________________________________


From kolab-issues at intevation.de  Tue Dec  2 04:45:59 2008
From: kolab-issues at intevation.de (bogota)
Date: Tue, 02 Dec 2008 03:45:59 +0000
Subject: [Kolab-devel] [issue3280] Marketing List of internal medicine
	specialists and many more
Message-ID: <20081202034358.816925AEF4@ms.mail.quarton.com.tw>


New submission from bogota <Wilton at mail.bollmeyer.de>:

Practicing Physicians in the USA 

Featuring coverage for more than 30 specialties like Internal Medicine, Family Practice, Opthalmology, Anesthesiologists, Cardiologists and more

Over a dozen sortable fields

This week's special price =  $390

### Buy this week and get these bonus information directories: ###

++ Hospitals

++ Nursing Homes

++ Visiting Nurses & RN's

++ Chiropractors

your rep is - : Clarke at perfectdatamed.com

above expires on Dec 5 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~   to terminate please send a blank message to exclude at perfectdatamed.com

----------
messages: 17863
nosy: Wilton, kklein649
status: unread
title: Marketing List of internal medicine specialists and many more
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3280>
___________________________________________________


From bernhard at intevation.de  Tue Dec  2 09:36:02 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 2 Dec 2008 09:36:02 +0100
Subject: [Kolab-devel] pear rpmbuild advice
In-Reply-To: <20081129230046.140516oycmtladfk@webmail.pardus.de>
References: <200811212347.39544.richard@radoeka.nl>
	<200811261035.03816.ml@radoeka.nl>
	<20081129230046.140516oycmtladfk@webmail.pardus.de>
Message-ID: <200812020936.02364.bernhard@intevation.de>

Am Samstag, 29. November 2008 23:00:46 schrieb Gunnar Wrobel:
> > Is this a runtime dependency or a buildtime dependency. ?In case it is a
> > runtime dependency, why is a testing framework needed as runtime
> > dependency for the kolab-server module (just curious, wanting to learn
> > something).
>
> Neither runtime nor buildtime but "testtime" :)
>
> It is absolutely not required in your system. I did nevertheless ?
> include it also in the Kolab/OpenPKG server version because I like ?
> having the phpUnit tests also on a productive system.
>
> Often people tend to start patching the installed code. Then it may be ?
> useful to be able to run/extend unit tests on your system.

I second the point: Often it is advisable to keep analysis and assertion 
code in for the production versions.
I think  http://www.whyprogramsfail.com/ has some comments on this.

> It is not ? 
> necessarily the best way of coding stuff but I want to enable people ?
> to contribute as much as possible.


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


From kolab-issues at intevation.de  Tue Dec  2 10:35:53 2008
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Tue, 02 Dec 2008 09:35:53 +0000
Subject: [Kolab-devel] [issue3281] Kontact does not quote CNs in iCalendar
	mails, which Outlook 2003 (OL 2K3) then fails to recognise
Message-ID: <1228210553.3.0.658353967463.issue3281@intevation.de>


New submission from Bernhard Reiter <bernhard at intevation.de>:

This is split out from:

   kolab/issue924 (OL2000 2K3 do not understand requests or answers sent by 
Kontact which include Umlauts.) 

Kontact Version: 4:3.5.10.enterprise.0.20081121.887372-kk3
In my experiement I could repair invitations send from Kontact
by quoting the CN part in the ORGANIZER and ATTENDEE lines.
Then Outlook 2003 accepted the invitation as invitation,
even when it was uft-8 and quoted-printable.

----------
assignedto: till
messages: 17865
nosy: bernhard, ludwig, till, vkrause
priority: critical
status: unread
title: Kontact does not quote CNs in iCalendar mails, which Outlook 2003 (OL 2K3) then fails to recognise
topic: kde client, kowi, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3281>
___________________________________________________


From kolab-issues at intevation.de  Tue Dec  2 16:54:20 2008
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Tue, 02 Dec 2008 15:54:20 +0000
Subject: [Kolab-devel] [issue3282] web client does not handle missing inbox
	gracefully
Message-ID: <1228233260.18.0.631951740216.issue3282@intevation.de>


New submission from Thomas Arendsen Hein <thomas at intevation.de>:

CVS HEAD 2008-12-02 (before 2.2.1-beta1):

If the Horde web client successfully authenticates against LDAP, but does not
have an IMAP spool (e.g. because kolabd failed to create the inbox), it does not
handle this error condition well.

One example is when you click on Calendar, nothing useful happens in the web
interface and error messages appear in the log file.

----------
assignedto: wrobel
messages: 17873
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: bug
status: unread
title: web client does not handle missing inbox gracefully
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3282>
___________________________________________________


From kolab-issues at intevation.de  Tue Dec  2 17:03:27 2008
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Tue, 02 Dec 2008 16:03:27 +0000
Subject: [Kolab-devel] [issue3283] web client: Document reasons for
	switching to LDAP auth instead of IMAP auth
Message-ID: <1228233807.73.0.232923837395.issue3283@intevation.de>


New submission from Thomas Arendsen Hein <thomas at intevation.de>:

The Horde web client changed from IMAP to LDAP authentication between server
2.2.0 and 2.2.1, the only hint about this I found is:
kolab/issue2258 (Horde authentication fails)

Usually mail clients authenticate against IMAP and SMTP and the web client
somehow is a client.

A problem revealed by this change is:
kolab/issue3282 (web client does not handle missing inbox gracefully)

A good reason to do it is:
kolab/issue2207 (Make it possible to enable and disable users to be able to use
the webclient)

But since I do not think that the change was done to solve the first or the last
issue, it would be good idea to document why the change was done.
Are there mailing list discussions?
What CVS commit contained the change?

----------
assignedto: wrobel
messages: 17875
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: feature
status: unread
title: web client: Document reasons for switching to LDAP auth instead of IMAP auth
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3283>
___________________________________________________


From kolab-issues at intevation.de  Tue Dec  2 17:29:43 2008
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Tue, 02 Dec 2008 16:29:43 +0000
Subject: [Kolab-devel] [issue3284] Webclient might send invitations that
	Outlook 2003 does not understand (unquoted CN for Organizer)
Message-ID: <1228235382.87.0.823243209901.issue3284@intevation.de>


New submission from Bernhard Reiter <bernhard at intevation.de>:

With kolab-webclient-1.2.0-20081117,
it is possible that an invitation has the following lines:

ORGANIZER;CN=3DBest =C3=A4 1 Tester:mailto:best1 at burlywood1.rgb
ATTENDEE;ROLE=3DREQ-PARTICIPANT;PARTSTAT=3DNEEDS-ACTION;RSVP=3DTRUE;CN=3D"H=
=C3=BCh
  h=C3=B6b":mailto:bernhard at intevation.de

Note that while CN in the ATTENDEE is quoted, the CN in the ORGANIZER is not,
this causes Outlook 2003 (11.8169.8172) SP3 (German as the XP SP3) to
not recognise the invitation, it is displayed as raw email where you can
see the iCalendar as text.

Note that there is a sister issue with Kontact:
kolab/issue3281 (Kontact does not quote CNs in iCalendar mails, which Outlook 
2003 (OL 2K3) then fails to recognise)

----------
assignedto: wrobel
messages: 17879
nosy: bernhard, thomas, wilde, wrobel
priority: urgent
status: unread
title: Webclient might send invitations that Outlook 2003 does not understand (unquoted CN for Organizer)
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3284>
___________________________________________________


From kolab-issues at intevation.de  Tue Dec  2 17:36:42 2008
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Tue, 02 Dec 2008 16:36:42 +0000
Subject: [Kolab-devel] [issue3285] Encodings in invitations missmatch with
	content-type
Message-ID: <1228235802.74.0.216082139737.issue3285@intevation.de>


New submission from Bernhard Reiter <bernhard at intevation.de>:

When adding an umlaut in the full name of the identity,
and invitation send out has the wrong encoding in the  text/calendar part.
As the From: is okay, I assume it is the encoding of this part
that is wrong.

kolab-webadmin-2.2.0-20081126

Here see the problem with from and location, an excerpt from the email:
From: Best =?iso-8859-1?b?5A==?= 1 Tester <best1 at kolab.example.org>

MIME-Version: 1.0
Content-Type: multipart/alternative;
  boundary="=_1pwtkhlf2ksk"

Content-Type: text/plain;
	charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Ort: h=F6r

Content-Type: text/calendar;
	charset=ISO-8859-1;
	name="event-invitation.ics";
	METHOD="REQUEST"
Content-Transfer-Encoding: quoted-printable

ORGANIZER;CN=3DBest =C3=A4 1 Tester:mailto:best1 at kolab.example.org

LOCATION:h=C3=B6r

----------
assignedto: wrobel
messages: 17881
nosy: bernhard, thomas, wilde, wrobel
priority: bug
status: unread
title: Encodings in invitations missmatch with content-type
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3285>
___________________________________________________


From itsef-admin at brightsight.com  Tue Dec  2 18:14:31 2008
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Tue, 2 Dec 2008 18:14:31 +0100
Subject: [Kolab-devel] Policy wrt "unstable" Debian Kontact packages?
Message-ID: <200812021814.31429.itsef-admin@brightsight.com>

Hi all,

Over the past months, I'm tracking the unstable Debian packages for the 
Kontact enterprise35 client 
(http://apt.intevation.de/dists/etch/unstable/source/) as I use them as base 
for our custom Kubuntu Hardy packages. Given that packages show up 
infrequently in this directory, I'm using an update tracker plugin in Firefox 
to find out about new "releases". Over the past few days I noted that kontact 
886071 was added to the directory and I got it and rolled it out for Kubuntu, 
as it contained two bugfixes I'm interested in (issue3196 and issue2472). A 
short while later, version 887372 appeared, which I did not install, as I 
wasn't sure about the status of issue2472 in that version (see discussion 
there).

Today *both* versions were removed from "unstable" and the latest version is 
now 862683. Which makes me wonder about the reasoning behind this - if a new, 
severe regression was found in these I'd definitely like to know about it... 
Is there any place where I can see why these decisions are made?

Thanks in advance,

Thomas


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-devel] 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-devel/attachments/20081202/bb264847/attachment.bin

From wrobel at pardus.de  Tue Dec  2 23:29:18 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Tue, 02 Dec 2008 23:29:18 +0100
Subject: [Kolab-devel] [issue3283] web client: Document reasons
	for	switching to LDAP auth instead of IMAP auth
In-Reply-To: <1228233807.73.0.232923837395.issue3283@intevation.de>
References: <1228233807.73.0.232923837395.issue3283@intevation.de>
Message-ID: <20081202232918.1064119t3nwwuxus@webmail.pardus.de>

Quoting Thomas Arendsen Hein <kolab-issues at intevation.de>:

>
> New submission from Thomas Arendsen Hein <thomas at intevation.de>:
>
> The Horde web client changed from IMAP to LDAP authentication between server
> 2.2.0 and 2.2.1, the only hint about this I found is:
> kolab/issue2258 (Horde authentication fails)
>
> Usually mail clients authenticate against IMAP and SMTP and the web client
> somehow is a client.
>
> A problem revealed by this change is:
> kolab/issue3282 (web client does not handle missing inbox gracefully)
>
> A good reason to do it is:
> kolab/issue2207 (Make it possible to enable and disable users to be  
> able to use
> the webclient)
>
> But since I do not think that the change was done to solve the first  
> or the last
> issue, it would be good idea to document why the change was done.
> Are there mailing list discussions?
> What CVS commit contained the change?

This is a somewhat complex story. The auth change from IMAP to LDAP  
was in fact not the intended goal but just a side effect. One that I  
didn't mind though.

Horde offers you more than twenty different authentication modules.  
IMAP authentication is among those as well as a Kolab specific  
authentication module. The latter was the module I always used for the  
Horde installation on the Kolab server. It would be no problem to  
change this to the IMAP driver.

The Kolab authentication module traditionally derived from the Horde  
IMAP auth driver and this is what I changed recently to LDAP. The  
reasons for that were manifold and in fact the logical conclusion to a  
series of restructurings in the Horde Kolab modules. I won't go too  
much into detail here.

But let me say that an authentication module that really represents  
the Kolab authentication concept must authenticate against LDAP as  
this holds the user credentials.

And nowadays it is not only Horde using the Kolab auth module but also  
Kolab_FreeBusy as well as Kolab_Filter. This was also one of the  
driving forces behind the restructurings I mentioned above: We had  
four different auth implementations in the old Kolab CVS code. You  
know that the reduction of this type of code duplication is what the  
upstream Kolab_* modules are mainly about.

While I agree that a mail client should auth via IMAP I also see a  
benefit from using the new LDAP based Kolab module. The bug you  
mentioned is among them. There was another one about retrieving user  
information from LDAP and using it for initialization of the web  
client preferences. In addition I consider the whole Kolab session  
approach I now use within Kolab_Server a significant improvement over  
what we had before (mainly for caching reasons which saves us a number  
of LDAP requests).

The negative point (kolab/issue3282) is something I acknowledge as a  
bug but it is not more than that and I don't see it as a blocker to  
changing to LDAP auth. Of course Horde should ensure that the users  
primary storage space is available by using the LDAP credentials. This  
is something that currently does not happen and that needs fixing  
indeed.

I cannot pinpoint a single CVS commit as this has been a succession of  
structural changes. But this one was at least the crucial change from  
IMAP to LDAP:

http://cvs.horde.org/co.php/framework/Auth/Auth/kolab.php?r=1.1.10.18

Enough documentation? I don't think this should go into the wiki but  
correct me if I'm wrong.

Cheers,

Gunnar

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

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


----------------------------------------------------------------
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-devel/attachments/20081202/0b811f7c/attachment-0001.bin

From kolab-issues at intevation.de  Wed Dec  3 02:01:13 2008
From: kolab-issues at intevation.de (fenugreek Bassett)
Date: Wed, 03 Dec 2008 01:01:13 +0000
Subject: [Kolab-devel] [issue3286] D entists Contact List for the United
	States
Message-ID: <SRV-SBS01vXee4fDGCl00000d23@ma-dieterle.de>


New submission from fenugreek Bassett <Claudette at mail.cooper-energy.com>:

Comes with unlimited use license and at a very resonable price:

++> 164,466 Den Tists 
++> 158,424 Business Addresses
++> 163,922 Tel #'s
++> 77,035 Fax Numbers
++> 45,878 office emails

for this week the new lowered price is $296

Send an email to Covington at perfectdatamed.com to inquire about this and other Database we have

to terminate please send a blank message to exclude at perfectdatamed.com

----------
messages: 17885
nosy: Claudette, admin2, doralynnemicklos, flyingschool, info12, multimedia, now968, tom1, wohrt
status: unread
title: D entists Contact List for the United States
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3286>
___________________________________________________


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: [Kolab-devel] 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 kolab-issues at intevation.de  Wed Dec  3 09:56:20 2008
From: kolab-issues at intevation.de (Gunnar Wrobel)
Date: Wed, 03 Dec 2008 08:56:20 +0000
Subject: [Kolab-devel] [issue3287] Document the Kolab_Filter policies
Message-ID: <1228294580.3.0.019713138665.issue3287@intevation.de>


New submission from Gunnar Wrobel <p at rdus.de>:

Do we have any documentation of the Kolab_Filter policies?


From wrobel at pardus.de  Wed Dec  3 10:07:59 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 03 Dec 2008 10:07:59 +0100
Subject: [Kolab-devel] Why the use of SPF pointer is becoming
	more	important
In-Reply-To: <71fe4e760812022052q1436049fgb015e9717f4f766f@mail.gmail.com>
References: <71fe4e760812022052q1436049fgb015e9717f4f766f@mail.gmail.com>
Message-ID: <20081203100759.60023a133lk04wao@webmail.pardus.de>

Quoting Alain Spineux <aspineux at 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 ?

Sure, would be good to have it. I'd suggest opening a feature request  
in the bug tracker.

Cheers,

Gunnar

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



-- 
______ 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-devel/attachments/20081203/dae66d79/attachment.bin

From kolab-issues at intevation.de  Wed Dec  3 10:46:46 2008
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 03 Dec 2008 09:46:46 +0000
Subject: [Kolab-devel] [issue3288] Use of the "Save password" option in the
	kolabwizard doesn't save the password.
Message-ID: <1228297605.87.0.871979472016.issue3288@intevation.de>


New submission from Ludwig Reiter <ludwig at intevation.de>:

enterprise4 windows Kontact-Installer_20081128.exe

Kontact asks for the smtp-auth password on a fresh configured account, even
when "Save password" option in the kolabwizard is choosen.

Versions:
gpg4win1.9.12-beta.exe 
kdelibs-branch  889739
kdepimlibs-branch  889781
kdepim-branch  890007
i10n-kde4  890045
kowi-crypto-files_gpg4win1.9.11-beta

----------
assignedto: till
messages: 17889
nosy: bh, ludwig, till
priority: minor bug
status: unread
title: Use of the "Save password" option in the kolabwizard doesn't save the password.
topic: kde client, kowi, windows
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3288>
___________________________________________________


From kolab-issues at intevation.de  Wed Dec  3 18:17:08 2008
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Wed, 03 Dec 2008 17:17:08 +0000
Subject: [Kolab-devel] [issue3289] resmgr dies when it should accept,
	but has not Calender folder access
Message-ID: <1228324628.67.0.80595206566.issue3289@intevation.de>


New submission from Bernhard Reiter <bernhard at intevation.de>:

Kolab_Filter-0.1.1-20081125
(Kolab Server/OpenPKG CVS),

I am sending an invitation to a fresh account
which has all : accept as policy.
(But because it is a user account, it has no Calender folder.)

Got a bounce saying:
Command died with status 255: "/kolab/bin/php"

To reproduce:
a) create a fresh user F with policy all: accept.
b) send an invitation there, e.g. 
with /kolabrepository/utils/testing/test-send-invitation-issue 3236.py
c) check the results in both accounts
Expected behaviour the email should be delivered to the account F
if the resmgr encounters problems.

/kolab/var/kolab-filter/log/filter.log has
Dec 03 18:09:07 Kolab Filter [error] [horde] PHP Error: Unknown: SECURITY 
PROBLEM: insecure server advertised AUTH=PLAIN (errflg=1); Code: 0 [on line 176 
of "/kolab/lib/php/Horde/Kolab/Filter/Response.php"]

----------
assignedto: wrobel
messages: 17911
nosy: bernhard, thomas, wilde, wrobel
priority: bug
status: unread
title: resmgr dies when it should accept, but has not Calender folder access
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3289>
___________________________________________________


From wrobel at pardus.de  Thu Dec  4 06:53:59 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 04 Dec 2008 06:53:59 +0100
Subject: [Kolab-devel] PEAR packaging problems
Message-ID: <20081204065359.94722qdlowfvuem8@webmail.pardus.de>

We experienced some problems with PEAR packaging during preparations  
for the next Kolab server release. Maybe some packagers from other  
distros have additional insight or can make use of the information.

 From https://www.intevation.de/roundup/kolab/issue3260:

And in fact, looking at the PEAR packaging and installation mechanisms now I
tend to say that they use a somewhat broken concept since they  
directly install
from a tgz. And these tgz's are only installable as a package not when  
unpacked
-> this irritated Thomas and after checking this I definitely agree.

There are two ways around this:

1) Patching the installed files. As there is no compilation we could apply
patches in the RPM_BUILD_ROOT. I consider this to be bad monkey patching and
would like to avoid this. If I remember the chat with Thomas correctly he also
mentioned the same thing.

2) Completing the unpacked tgz with package.xml from upstream and  
using this for
installation. The drawback here is that it is somewhat complicated as you will
need to modify the packages spec file and add the package.xml once you  
decide a
package needs patching.

I consider solution 2) to be the more attractive one and I checked this in for
Kolab_Filter as an example now.

In general we should probably try to avoid patching and rather rely on  
upstream
releases. Especially for the Kolab_* packages this is a simple thing for me to
do. I could have also done this for the patch attached by Thomas here but I
choose not to for demonstration purposes on how to patch a PEAR package.

-- 
______ 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-devel/attachments/20081204/950c289a/attachment.bin

From ml at radoeka.nl  Thu Dec  4 08:48:14 2008
From: ml at radoeka.nl (Richard Bos)
Date: Thu, 4 Dec 2008 08:48:14 +0100
Subject: [Kolab-devel] PEAR packaging problems
In-Reply-To: <20081204065359.94722qdlowfvuem8@webmail.pardus.de>
References: <20081204065359.94722qdlowfvuem8@webmail.pardus.de>
Message-ID: <20081204074814.GA71589@xs4all.nl>

> We experienced some problems with PEAR packaging during preparations for
> the next Kolab server release. Maybe some packagers from other distros
> have additional insight or can make use of the information.

I encounter the same thing.
My specfiles contain:
# %setup -q -n %{prj}-%{version}  
# %__cp %{SOURCE0} %{prj}-%{version}.tgz  

The last line (%__cp) should not be needed as the package is
there already, but in an unpackage format.  The cp is there
because the pear install command expects a package, just
as you stated.

> From https://www.intevation.de/roundup/kolab/issue3260:
> 
> And in fact, looking at the PEAR packaging and installation mechanisms now
> I tend to say that they use a somewhat broken concept since they directly
> install from a tgz. And these tgz's are only installable as a package not
> when unpacked
> -> this irritated Thomas and after checking this I definitely agree.
> 
> There are two ways around this:

There is a third item that can be added to your list.  But this
won't be a workaroround but a solution.  Patch 'pear install', so it really knows how
to install a unpackage tarball.  Perhaps the same patch can also take care
that the channel information is in that case not needed, as that took
me some days to figure out, how to deal with that in an offline
virtual build image.


> 1) Patching the installed files. As there is no compilation we could apply               
> patches in the RPM_BUILD_ROOT. I consider this to be bad monkey patching and 
> would like to avoid this. If I remember the chat with Thomas correctly he
> also mentioned the same thing.

This is indeed a workaround.  RPM has a mechanism to apply patches, this
mechanism cannot be used with pear modules, which shows that the concept
is not correct => improve 'pear install'


> 2) Completing the unpacked tgz with package.xml from upstream and using
> this for installation. The drawback here is that it is somewhat complicated
> as you will need to modify the packages spec file and add the package.xml
> once you decide a package needs patching.

Sounds complicated...  Do you mean that the pear module is to be patched
before the rpm build?  If that is what you mean, is not a good idea either
as it decouples the native tarbal with the applied patches.  E.g. someone
who unpacks the src.rpm won't see what are the native sources, and what are
the patches....

> I consider solution 2) to be the more attractive one and I checked this in
> for Kolab_Filter as an example now.

> In general we should probably try to avoid patching and rather rely on
> upstream releases. Especially for the Kolab_* packages this is a simple
> thing for me to do. I could have also done this for the patch attached
> by Thomas here but I choose not to for demonstration purposes on how to
> patch a PEAR package.

Good demonstration :)

I hope, that a bug report will be opened against 'pear install' to make
it possible to install unpacked sources.  As you mentioned the package.xml
install file; in case a pear modules is patche, the patch should probably
also update the package.xml file.  But that seems doable, and can be part
of the patch that is applied against the pear module.

-- 
Richard


From kolab-issues at intevation.de  Thu Dec  4 15:28:00 2008
From: kolab-issues at intevation.de (Clement Walls)
Date: Thu, 04 Dec 2008 14:28:00 +0000
Subject: [Kolab-devel] [issue3291] Get her the most incredible christmas gift
Message-ID: <9556138954.20081111103511@teachers.net>


New submission from Clement Walls <DionfiendishFoley at teachers.net>:

Just in: the latest 2008 released luxury timepieces, from dozens of famous designer brands.

http://cehlefoz.cn/

----------
messages: 17934
nosy: DionfiendishFoley
status: unread
title: Get her the most incredible christmas gift
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3291>
___________________________________________________


From kolab-issues at intevation.de  Thu Dec  4 18:03:19 2008
From: kolab-issues at intevation.de (Sascha Wilde)
Date: Thu, 04 Dec 2008 17:03:19 +0000
Subject: [Kolab-devel] [issue3292] Sharing Groupware Resources does not work
	in Webclient
Message-ID: <1228410199.13.0.708444701936.issue3292@intevation.de>


New submission from Sascha Wilde <wilde at intevation.de>:

One of the core groupware features in Kolab is the ability to share
groupware objects (like events, contacts etc.) between users.

This is done by setting the ACLs of the containing IMAP folders
accordingly.

Unfortunately this doesn't work with the Horde based Kolab client.
Given two users A and B:
- user A creates a event in his calendar
- user A sets ACLs for his calender folder (Options/Mail/Share
  Folders)  so that B is allowed to list and read it.
- now user B should be able to see A's event but he isn't

B does see A'a calendar folder as mail/user/A/Calender and it is
correctly displayed as calender folder but clicking on it displays
only B's own events, not A's.  (Additional I would expect A's calender
to appear in the "My Calendars" list in Organizing/Calendar view, but
it doesn't).

The same holds true for shared contacts.  I haven't tested tasks and
notes but I assume they are equally broken.

----------
assignedto: wrobel
messages: 17935
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: critical
status: unread
title: Sharing Groupware Resources does not work in Webclient
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3292>
___________________________________________________


From kolab-issues at intevation.de  Thu Dec  4 18:41:56 2008
From: kolab-issues at intevation.de (Sascha Wilde)
Date: Thu, 04 Dec 2008 17:41:56 +0000
Subject: [Kolab-devel] [issue3293] Big code duplication and code version
	messup: Horde libs in 2.2.1
Message-ID: <1228412515.87.0.463905140637.issue3293@intevation.de>


New submission from Sascha Wilde <wilde at intevation.de>:

I just learned that in the current version of the upcoming
Kolab-Server 2.2.1 large parts of the Horde library code are
installed twice: under /kolab/lib/php/Horde and
/kolab/var/kolab/www/client/lib/Horde

Even worse, the versions of the code in both places are not in sync,
quick scan done like this:

n=0
m=0
for i in `find /kolab/lib/php/Horde -type f`
do 
   j=/kolab/var/kolab/www/client/lib/${i#*/php/}
   if [ -f $j ] ; then
     echo "$(( ++n )) `basename $j:`" 
     cmp $i $j || m=$(( m + 1 ))
   fi
done
echo "Found $n identical named files, $m with differing content."

shows: Found 191 identical named files, 123 with differing content.

The differences range from mere cosmetic changes in comments to quite
big code changes.

To me this is quite alarming, not only because code duplicate per se
is a bad thing (which IMNSHO it is!) but especially because of the
different versions.  I guess this will increase the effort of tracking
down and fixing of bugs significantly as they have to be investigated
and solved in two different places maybe even different code versions.

Gunnar, maybe you could put a short rational for the current state of
things into this issue.  Then we should try to solve this in a
sensible manner ASAP.

----------
assignedto: wrobel
messages: 17937
nosy: bernhard, martin, thomas, till, wilde, wrobel
status: unread
title: Big code duplication and code version messup: Horde libs in 2.2.1
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3293>
___________________________________________________


From liste at gelpi.it  Thu Dec  4 18:48:42 2008
From: liste at gelpi.it (Gelpi Andrea)
Date: Thu, 04 Dec 2008 18:48:42 +0100
Subject: [Kolab-devel] [issue3292] Sharing Groupware Resources does not
 work	in Webclient
In-Reply-To: <1228410199.13.0.708444701936.issue3292@intevation.de>
References: <1228410199.13.0.708444701936.issue3292@intevation.de>
Message-ID: <493817FA.3060603@gelpi.it>

Sascha Wilde ha scritto:
> New submission from Sascha Wilde <wilde at intevation.de>:
> 
> One of the core groupware features in Kolab is the ability to share
> groupware objects (like events, contacts etc.) between users.
> 
> This is done by setting the ACLs of the containing IMAP folders
> accordingly.
> 
> Unfortunately this doesn't work with the Horde based Kolab client.
> Given two users A and B:
> - user A creates a event in his calendar
> - user A sets ACLs for his calender folder (Options/Mail/Share
>   Folders)  so that B is allowed to list and read it.
> - now user B should be able to see A's event but he isn't
> 
> B does see A'a calendar folder as mail/user/A/Calender and it is
> correctly displayed as calender folder but clicking on it displays
> only B's own events, not A's.  (Additional I would expect A's calender
> to appear in the "My Calendars" list in Organizing/Calendar view, but
> it doesn't).
> 
> The same holds true for shared contacts.  I haven't tested tasks and
> notes but I assume they are equally broken.

Hope this can help.

In kolab server 2.2.0 installed in debian etch I can see and use events 
in calendar of A, users contacts and so on if A set ACL properly.
I set up acl using horde.
Workgroup sharing is working for me.

-- 
ing. Andrea Gelpi
***************************************************
La Terra non la abbiamo ereditata dai nostri avi,
ma la abbiamo presa in prestito dai nostri bambini.
***************************************************


From ml at radoeka.nl  Fri Dec  5 08:40:23 2008
From: ml at radoeka.nl (Richard Bos)
Date: Fri, 5 Dec 2008 08:40:23 +0100
Subject: [Kolab-devel] PEAR packaging problems
In-Reply-To: <20081204074814.GA71589@xs4all.nl>
References: <20081204065359.94722qdlowfvuem8@webmail.pardus.de>
	<20081204074814.GA71589@xs4all.nl>
Message-ID: <200812050840.23326.ml@radoeka.nl>

Op Thursday 04 December 2008 08:48:14 schreef Richard Bos:
> > We experienced some problems with PEAR packaging during preparations for
> > the next Kolab server release. Maybe some packagers from other distros
> > have additional insight or can make use of the information.
>
> I encounter the same thing.
> My specfiles contain:
> # %setup -q -n %{prj}-%{version}
> # %__cp %{SOURCE0} %{prj}-%{version}.tgz
>
> The last line (%__cp) should not be needed as the package is
> there already, but in an unpackage format.  The cp is there
> because the pear install command expects a package, just
> as you stated.

Thanks to an example provided by Mathieu P, I was able to improve the rpm 
build (for openSUSE), I added a update to issue 3260
https://www.intevation.de/roundup/kolab/issue3260 :

I made first the following change:

horde-cli> osc diff horde-cli.spec
Index: horde-cli.spec
===================================================================
--- horde-cli.spec     (revision 1)
+++ horde-cli.spec     (working copy)
@@ -27,17 +27,17 @@

 %prep
 %setup -q -n %{prj}-%{version}
-%__cp %{SOURCE0} %{prj}-%{version}.tgz

 %build
+%__mv ../package.xml .

 %install
-pear 
install --packagingroot %{buildroot} --nodeps --offline %{prj}-%{version}.tgz
+pear install --packagingroot %{buildroot} --nodeps package.xml

 %__rm -rf %{buildroot}/%{peardir}/.
{filemap,lock,registry,channels,depdb,depdblock}

 %__mkdir_p %{buildroot}%{xmldir}
-%__cp %{_builddir}/package.xml %{buildroot}%{xmldir}/%{prj}.xml
+%__cp package.xml %{buildroot}%{xmldir}/%{prj}.xml

 %clean
 %__rm -rf %{buildroot}
@@ -57,6 +57,10 @@


 %changelog
+* Thu Dec 04 2008 
+- Changed the build method to use the unpacked tarbal.  This will allow the
+  rpm to apply patches against the pristine sources, with the former method
+  this was not possible.
 * Fri Nov 28 2008 
 - initial version

This copies the package.xml into the unpacked sources directory, which makes
it possible to build from the unpacked sources.

Next I tried to build an rpm for a patched pear module.  This works quite
well now :)  But it is with some trickery:


horde-cli> osc diff
Index: horde-cli.spec
===================================================================
--- horde-cli.spec     (revision 2)
+++ horde-cli.spec     (working copy)
@@ -13,6 +13,7 @@
 Group:         Productivity/Networking/Web/Servers
 Url:           http://pear.horde.org/index.php?package=%{prj}
 Source0:       %{prj}-%{version}.tgz
+Patch0:        horde.patch
 BuildArch:     noarch
 BuildRoot:     %{_tmppath}/%{name}-%{version}-build
 PreReq:        %{_bindir}/pear
@@ -27,6 +28,8 @@

 %prep
 %setup -q -n %{prj}-%{version}
+cd ..
+%patch0 -p0

 %build
 %__mv ../package.xml .

The horde.patch file contains 2 patches (in this case); 1 patched pear module
and a patched package.xml file (providing a updated md5sum for the file).

The patch is obtained using the following commands:
#  (diff -u package.xml package.xml.new; diff -Naur Horde_CLI-0.0.2 
Horde_CLI-0.0.2.new) > horde.patch

The trickery is the line with 'cd ..'  as the setup tag moves into the
unpacked sources directory the only way to patch the package.xml file, is
to return to the parent directory.  This all seems to work well :)

Hopefully this build method can be used by others too.

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


From kolab-issues at intevation.de  Fri Dec  5 09:11:40 2008
From: kolab-issues at intevation.de (Gunnar Wrobel)
Date: Fri, 05 Dec 2008 08:11:40 +0000
Subject: [Kolab-devel] [issue3294] Patching and installing PEAR packages
Message-ID: <1228464700.8.0.0665582540479.issue3294@intevation.de>


New submission from Gunnar Wrobel <p at rdus.de>:

This bug has been derived from issue3260.

There have been additional discussions on the mailing list:

http://kolab.org/pipermail/kolab-devel/2008-December/009844.html
http://kolab.org/pipermail/kolab-devel/2008-December/009845.html
http://kolab.org/pipermail/kolab-devel/2008-December/009850.html

Original problem:

PEAR directly installs from a tgz. And these tgz's are only installable as a
package not when unpacked. This prevents standard patching.

Possible workarounds:

1) Unpack the package, move package.xml from outside the package back into the
package, patch the files that require patching and also patch the md5sum in
package.xml. Install using package.xml.

2) Unpack the package and copy package.xml from upstream into the unpacked
package directory. Patch the files that require patching. Install using package.xml

In general we assume that this is a PEAR bug as one should be able to unpack,
patch and install a PEAR package.

----------
assignedto: wrobel
messages: 17945
nosy: bernhard, mathieu.parent, rbos, thomas, wilde, wrobel
priority: bug
status: unread
title: Patching and installing PEAR packages
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3294>
___________________________________________________


From wrobel at pardus.de  Fri Dec  5 09:22:24 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Fri, 05 Dec 2008 09:22:24 +0100
Subject: [Kolab-devel] PEAR packaging problems
In-Reply-To: <200812050840.23326.ml@radoeka.nl>
References: <20081204065359.94722qdlowfvuem8@webmail.pardus.de>
	<20081204074814.GA71589@xs4all.nl> <200812050840.23326.ml@radoeka.nl>
Message-ID: <20081205092224.14113m8ga1d2c728@webmail.pardus.de>

Hi Richard,

Quoting Richard Bos <ml at radoeka.nl>:

> Op Thursday 04 December 2008 08:48:14 schreef Richard Bos:
>> > We experienced some problems with PEAR packaging during preparations for
>> > the next Kolab server release. Maybe some packagers from other distros
>> > have additional insight or can make use of the information.
>>
>> I encounter the same thing.
>> My specfiles contain:
>> # %setup -q -n %{prj}-%{version}
>> # %__cp %{SOURCE0} %{prj}-%{version}.tgz
>>
>> The last line (%__cp) should not be needed as the package is
>> there already, but in an unpackage format.  The cp is there
>> because the pear install command expects a package, just
>> as you stated.
>
> Thanks to an example provided by Mathieu P, I was able to improve the rpm
> build (for openSUSE), I added a update to issue 3260
> https://www.intevation.de/roundup/kolab/issue3260 :
>
> I made first the following change:
>
> horde-cli> osc diff horde-cli.spec
> Index: horde-cli.spec
> ===================================================================
> --- horde-cli.spec     (revision 1)
> +++ horde-cli.spec     (working copy)
> @@ -27,17 +27,17 @@
>
>  %prep
>  %setup -q -n %{prj}-%{version}
> -%__cp %{SOURCE0} %{prj}-%{version}.tgz
>
>  %build
> +%__mv ../package.xml .
>
>  %install
> -pear
> install --packagingroot %{buildroot} --nodeps --offline %{prj}-%{version}.tgz
> +pear install --packagingroot %{buildroot} --nodeps package.xml
>
>  %__rm -rf %{buildroot}/%{peardir}/.
> {filemap,lock,registry,channels,depdb,depdblock}
>
>  %__mkdir_p %{buildroot}%{xmldir}
> -%__cp %{_builddir}/package.xml %{buildroot}%{xmldir}/%{prj}.xml
> +%__cp package.xml %{buildroot}%{xmldir}/%{prj}.xml
>
>  %clean
>  %__rm -rf %{buildroot}
> @@ -57,6 +57,10 @@
>
>
>  %changelog
> +* Thu Dec 04 2008
> +- Changed the build method to use the unpacked tarbal.  This will allow the
> +  rpm to apply patches against the pristine sources, with the former method
> +  this was not possible.
>  * Fri Nov 28 2008
>  - initial version
>
> This copies the package.xml into the unpacked sources directory, which makes
> it possible to build from the unpacked sources.
>
> Next I tried to build an rpm for a patched pear module.  This works quite
> well now :)  But it is with some trickery:
>
>
> horde-cli> osc diff
> Index: horde-cli.spec
> ===================================================================
> --- horde-cli.spec     (revision 2)
> +++ horde-cli.spec     (working copy)
> @@ -13,6 +13,7 @@
>  Group:         Productivity/Networking/Web/Servers
>  Url:           http://pear.horde.org/index.php?package=%{prj}
>  Source0:       %{prj}-%{version}.tgz
> +Patch0:        horde.patch
>  BuildArch:     noarch
>  BuildRoot:     %{_tmppath}/%{name}-%{version}-build
>  PreReq:        %{_bindir}/pear
> @@ -27,6 +28,8 @@
>
>  %prep
>  %setup -q -n %{prj}-%{version}
> +cd ..
> +%patch0 -p0
>
>  %build
>  %__mv ../package.xml .
>
> The horde.patch file contains 2 patches (in this case); 1 patched pear module
> and a patched package.xml file (providing a updated md5sum for the file).
>
> The patch is obtained using the following commands:
> #  (diff -u package.xml package.xml.new; diff -Naur Horde_CLI-0.0.2
> Horde_CLI-0.0.2.new) > horde.patch
>
> The trickery is the line with 'cd ..'  as the setup tag moves into the
> unpacked sources directory the only way to patch the package.xml file, is
> to return to the parent directory.  This all seems to work well :)
>
> Hopefully this build method can be used by others too.

Thanks for your insight. Also thanks to Mathieu for his comments. I  
closed kolab/issue3260 again as it is in fact resolved and opened  
kolab/issue3294 (https://www.intevation.de/roundup/kolab/issue3294).

Send upstream a bug report: http://pear.php.net/bugs/bug.php?id=15242

Cheers,

Gunnar

>
> --
> Richard Bos
> We are borrowing the world of our children,
> It is not inherited from our parents.
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



-- 
______ 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-devel/attachments/20081205/0d412774/attachment-0001.bin

From kolab-issues at intevation.de  Fri Dec  5 10:19:35 2008
From: kolab-issues at intevation.de (Sascha Wilde)
Date: Fri, 05 Dec 2008 09:19:35 +0000
Subject: [Kolab-devel] [issue3295] [Webclient] Newly created groupware
	folders don't appear in the interface
Message-ID: <1228468775.2.0.119715789818.issue3295@intevation.de>


New submission from Sascha Wilde <wilde at intevation.de>:

Newly created groupware folders don't appear in the interface of the
webmail client.  Well, actually they do appear in some places but not
everywhere needed...

When creating a new calender folder:
- click "Organizing/Calendar" and there "[Manage Calendars]"
- then choose "Create Calendar" name it and click "create"
the new calendar is immediately available in the calender view.

Unfortunately it isn't visible neither in the navigation bar at the
left nor in the "Options/Mail/Shared Folders" dialog.

So a freshly created calender folder cannot be setup for sharing.

After logging out and back in the folder is fully available.

This is with soon to bee 2.2.1 cvs code...

----------
assignedto: wrobel
messages: 17949
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: bug
status: unread
title: [Webclient] Newly created groupware folders don't appear in the interface
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3295>
___________________________________________________


From kolab-issues at intevation.de  Sat Dec  6 17:27:50 2008
From: kolab-issues at intevation.de (Tsistinas Langhans)
Date: Sat, 06 Dec 2008 16:27:50 +0000
Subject: [Kolab-devel] [issue3296] love love love love llove :)
Message-ID: <2064035728.20081206162725@dbs-tech.com.tw>


New submission from Tsistinas Langhans <stereoscopy at dbs-tech.com.tw>:

Show your sweeetheart how much you love her!!!
 http://cid-24b7e1a309bcf723.spaces.live.com/blog/cns!24B7E1A309BCF723!106.entry

Again airing his french. That's garsong, twopennorth tortoises
and other aquatic animals. From that i replied. More amenities
were exchanged, the george turned to me. There is not the
faintest back to his place of rest. It seemed that his.

----------
messages: 17968
nosy: stereoscopy
status: unread
title: love love love love llove :)
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3296>
___________________________________________________


From kolab-issues at intevation.de  Mon Dec  8 11:24:40 2008
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Mon, 08 Dec 2008 10:24:40 +0000
Subject: [Kolab-devel] [issue3297] f kontact is started via knotes,
	knotes sometimes crashed while renaming a note
Message-ID: <1228731880.12.0.40093386047.issue3297@intevation.de>


New submission from Ludwig Reiter <ludwig at intevation.de>:

enterprise35 20081202.891698-kk2

Test:
In a KDE environment:
1. Start knotes.
2. Create a new note with the popup menu of the knotes icon on the system tray.
3. Edit the text of the note.
4. Rename the title of the note. (Open a popup menu on the note title and choose
to rename it.)
=> In 4 of 5 tries knotes crashed.

The excepted result should be that the note is renamed.
But knotes crashs.

----------
assignedto: till
messages: 17971
nosy: bernhard, bh, ludwig, osterfeld, pradeepto, till
priority: urgent
status: unread
title: f kontact is started via knotes, knotes sometimes crashed while renaming a note
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3297>
___________________________________________________


From kolab-issues at intevation.de  Mon Dec  8 15:37:08 2008
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Mon, 08 Dec 2008 14:37:08 +0000
Subject: [Kolab-devel] [issue3298] kolab2.schema uses wrong enterprise
	number in some attributes
Message-ID: <1228747028.1.0.864433535932.issue3298@intevation.de>


New submission from Thomas Arendsen Hein <thomas at intevation.de>:

This is similar to kolab/issue19 (kolab.schema uses unowned private-enterprise OID):

I just noticed that kolab2.schema does not always use the OID space below
1.3.6.1.4.1.19414, but probably due to a copy&paste error 1.3.6.1.4.1.19419, too.
19419 is a German company not related to Kolab.

This number was introduced in a change made between revisions 1.9 and 1.10 of
server/kolab/kolab/kolab.schema and got copy&pasted to other attributes, so
there are 19 attributes using this now.

Can it simply be changed to 19414, of course with making sure that there are no
conflicts with existing OIDs? Or is there some kind of migration needed in this
case?

Martin, what do you think?

----------
assignedto: martin
messages: 17985
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: critical
status: unread
title: kolab2.schema uses wrong enterprise number in some attributes
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3298>
___________________________________________________


From kolab-issues at intevation.de  Mon Dec  8 17:03:57 2008
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Mon, 08 Dec 2008 16:03:57 +0000
Subject: [Kolab-devel] [issue3299] Kolab_Filter: big.eml is too big
Message-ID: <1228752237.78.0.569016990106.issue3299@intevation.de>


New submission from Thomas Arendsen Hein <thomas at intevation.de>:

Kolab_Filter-0.1.2 (and before):
test/Horde/Kolab/Filter/fixtures/big.eml causes the package to be much bigger
than needed. 1311K for this file compared to 245K for everything (code and test)
else is a waste of resources. The tarball is >1MB in size.

It would be better to generate a big mail, not only for above reasons, but also
to easily allow testing with much bigger emails.

----------
assignedto: wrobel
messages: 17987
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: minor bug
status: unread
title: Kolab_Filter: big.eml is too big
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3299>
___________________________________________________


From kolab-issues at intevation.de  Mon Dec  8 17:11:42 2008
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Mon, 08 Dec 2008 16:11:42 +0000
Subject: [Kolab-devel] [issue3300] Kolab_Filter: unsatisfied dependency?
Message-ID: <1228752702.02.0.896443507324.issue3300@intevation.de>


New submission from Thomas Arendsen Hein <thomas at intevation.de>:

When building Kolab_Filter-0.1.2-20081205.src.rpm I see the message:
warning: channel://pear.horde.org/Kolab_Filter-0.1.2 requires package
"channel://pear.horde.org/Horde_Util" (version >= 0.0.2)

But only Horde_Util-0.1.0-20080925 is available in CVS HEAD.

Installing Kolab_Filter is possible though.

----------
assignedto: wrobel
messages: 17989
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: bug
status: unread
title: Kolab_Filter: unsatisfied dependency?
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3300>
___________________________________________________


From kolab-issues at intevation.de  Mon Dec  8 17:56:13 2008
From: kolab-issues at intevation.de (Sascha Wilde)
Date: Mon, 08 Dec 2008 16:56:13 +0000
Subject: [Kolab-devel] [issue3301] [Webclient] Freshl;
	y deleted calendar-folders still visible in calendar view
Message-ID: <1228755373.07.0.673965699985.issue3301@intevation.de>


New submission from Sascha Wilde <wilde at intevation.de>:

After deleting a calendar folder the folder is still shown (and
selectable) in the calendar view (Organazing/Calendar).

This doesn't even change after using "Rebuild Folder Tree" or page
reloads.  Even the "Create Event" dialog still lists the folder as
possible calendar target, which (no surprise) leads to an error when
chosen.

The only way I found to refresh the calendar module is by logging out
and in.

This is with upcoming Kolab Server 2.2.1.

PS. Haven't tested anything besides calendar nut I strongly suspect
that there might be similar issue with other types of groupware
folders, too.

----------
assignedto: wrobel
messages: 17993
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: bug
status: unread
title: [Webclient] Freshl;y deleted calendar-folders still visible in calendar view
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3301>
___________________________________________________


From kolab-issues at intevation.de  Mon Dec  8 21:33:27 2008
From: kolab-issues at intevation.de (Chris Hastie)
Date: Mon, 08 Dec 2008 20:33:27 +0000
Subject: [Kolab-devel] [issue3302] Kolab fails to build on Ubuntu 8.10
	(Intrepid Ibex)
Message-ID: <1228768407.0.0.554666599509.issue3302@intevation.de>


New submission from Chris Hastie <chris at oak-wood.co.uk>:

Two issues (at least) prevent Kolab from building on Ubuntu 8.10 (64 bit).

openpkg will not compile with gcc 4.3. This can be worked around by installing
gcc-4.2 and executing 

ln -s /usr/bin/gcc-4.2 /usr/bin/gcc

openldap then fails to compile, exiting with:

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

There is some info on this error here:

http://bugs.gentoo.org/show_bug.cgi?id=225369

which suggests this issue comes with glibc-2.8. A patch is there, but may be
system specific.

----------
messages: 17994
nosy: tipichris
priority: urgent
status: unread
title: Kolab fails to build on Ubuntu 8.10 (Intrepid Ibex)
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3302>
___________________________________________________


From kolab-issues at intevation.de  Tue Dec  9 11:34:48 2008
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 09 Dec 2008 10:34:48 +0000
Subject: [Kolab-devel] [issue3303] The name title of a contact is not saved.
Message-ID: <1228818887.97.0.832605786333.issue3303@intevation.de>


New submission from Ludwig Reiter <ludwig at intevation.de>:

enterprise35 20081202.891698-kk2

Test:
1. Create a new contact
2. Edit this contact and enter a title under details.
3. Open the contact again.
Actual Result: The title is lost.
Excepted Result: The title is saved and displayed.

----------
assignedto: till
messages: 17995
nosy: bernhard, bh, ludwig, osterfeld, pradeepto, till
priority: bug
status: unread
title: The name title of a contact is not saved.
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3303>
___________________________________________________


From kolab-issues at intevation.de  Tue Dec  9 12:23:59 2008
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 09 Dec 2008 11:23:59 +0000
Subject: [Kolab-devel] [issue3304] Pasting a contact opens a edit dialog
Message-ID: <1228821839.08.0.29169158378.issue3304@intevation.de>


New submission from Ludwig Reiter <ludwig at intevation.de>:

enterprise35 kdepim 20081202.891698-kk2

Test:
A test contact in the contacts folder.
1. Copy with Ctrl+C the test contact.
2. Paste with Ctrl+V the test contact.
Actual Result: An edit dialog of the contact opens, and if I press "cancel"
the contact is saved in the resource folder.
Excepted Result: No Edit dialog should appear and the contact should be copied.

----------
assignedto: till
messages: 17999
nosy: bernhard, bh, ludwig, osterfeld, pradeepto, till
priority: bug
status: unread
title: Pasting a contact opens a edit dialog
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3304>
___________________________________________________


From kolab-issues at intevation.de  Tue Dec  9 12:43:01 2008
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 09 Dec 2008 11:43:01 +0000
Subject: [Kolab-devel] [issue3305] Double click on a distribution list in
	the distribution list editor should open an edit dialog
Message-ID: <1228822981.28.0.0698482119305.issue3305@intevation.de>


New submission from Ludwig Reiter <ludwig at intevation.de>:

enterprise35 kdepim 20081202.891698-kk2

Test:
1. Switch to contact plugin.
2. Create a new distribution list.
3. Double click on the distribution list in the editor.
Actual Result: Nothing happens
Excepted Result: An editor dialog of the clicked distribution list should appear.

It is possilbe to double click on an contact to open an edit dialog, so the user
expects to double click on a dist list to open a dist list edit dialog.

----------
assignedto: till
messages: 18002
nosy: bernhard, bh, ludwig, osterfeld, pradeepto, till
priority: minor bug
status: unread
title: Double click on a distribution list in the distribution list editor should open an edit dialog
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3305>
___________________________________________________


From kolab-issues at intevation.de  Tue Dec  9 14:28:45 2008
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 09 Dec 2008 13:28:45 +0000
Subject: [Kolab-devel] [issue3306] "No attendees" behind the title of a new
	event or task not translated into German.
Message-ID: <1228829325.12.0.32949829443.issue3306@intevation.de>


New submission from Ludwig Reiter <ludwig at intevation.de>:

enterprise35 kdepim 20081202.891698-kk2
             kde-i18n 20081203.891904

Test:
1. Start to create an new task or event.
Behind the title is the string "No attendees" not translated into German.

----------
assignedto: till
messages: 18006
nosy: bernhard, bh, ludwig, osterfeld, pradeepto, till
priority: minor bug
status: unread
title: "No attendees" behind the title of a new event or task not translated into German.
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3306>
___________________________________________________


From kolab-issues at intevation.de  Tue Dec  9 15:05:55 2008
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 09 Dec 2008 14:05:55 +0000
Subject: [Kolab-devel] [issue3307] After d'n'd a task on the calendar icon
	an appointment with an unopenable attachment is opened
Message-ID: <1228831555.37.0.107498680925.issue3307@intevation.de>


New submission from Ludwig Reiter <ludwig at intevation.de>:

enterprise35 20081202.891698-kk2

Test:
1. Create a test to-do.
2. D'n'd the test todo on the calendar icon on the left toolbar.
=> An appointment create dialog with an attachment, which cannot be openend,
appears.
The attachment should contain the todo.

----------
assignedto: till
messages: 18009
nosy: bernhard, bh, ludwig, osterfeld, pradeepto, till
priority: bug
status: unread
title: After d'n'd a task on the calendar icon an appointment with an unopenable attachment is opened
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3307>
___________________________________________________


From kolab-issues at intevation.de  Tue Dec  9 16:00:57 2008
From: kolab-issues at intevation.de (T. Ribbrock)
Date: Tue, 09 Dec 2008 15:00:57 +0000
Subject: [Kolab-devel] [issue3308] Add "room number" attribute for contacts
Message-ID: <1228834857.79.0.216669744873.issue3308@intevation.de>


New submission from T. Ribbrock <itsef-admin at brightsight.com>:

Based on a question I asked on kolab-users:

One of the fields one can fill in for a user in the Kolab webadmin interface is
the "Room Number". I find this a handy attribute to have, but until now it is
not part of the kolab format and hence not visible in the clients (despite being
there in the webadmin interface). Hence, if possible, please consider adding
this attribute to the format and - subsequently - client(s). Thanks in advance!

----------
messages: 18011
nosy: itsef_admin
priority: wish
status: unread
title: Add "room number" attribute for contacts
topic: format, kde client, server, web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3308>
___________________________________________________


From kolab-issues at intevation.de  Wed Dec 10 11:17:24 2008
From: kolab-issues at intevation.de (Sascha Wilde)
Date: Wed, 10 Dec 2008 10:17:24 +0000
Subject: [Kolab-devel] [issue3309] [WebClient] Can nott login directly in to
	dimp
Message-ID: <1228904244.39.0.635739942149.issue3309@intevation.de>


New submission from Sascha Wilde <wilde at intevation.de>:

One of the broadly requested and therefore important new features of
the upcoming release is the availability of dimp (the more modern,
dynamic web client) in the WebClient (aka. Horde).

Unfortunately currently its not possible for a user to login using
dimp:

- When using https://example.com/client/ at login time one gets imp
- When using https://example.com/client/dimp/ at login time one gets
  an unholy mix up of imp and dimp (navigation bars of both interfaces
  at the same time)
- I have been told (and I believe to have it seen my self once at some
  state of the development process) that in the original Horde there
  is a button in the login mask to select whether to use dimp -- but
  this button is missing from the Kolab Server variant.

A workaround is to log into imp and then manually switch the URL to
client/dimp/, but that is not acceptable for ordinary users.

It is important that we get a way to login directly using dimp for the
release.  And I would highly appreciate if there would be a way to
configure the default interface used when logging in under
https://example.com/client/

----------
assignedto: wrobel
messages: 18017
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: critical
status: unread
title: [WebClient] Can nott login directly in to dimp
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3309>
___________________________________________________


From kolab-issues at intevation.de  Wed Dec 10 12:23:35 2008
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 10 Dec 2008 11:23:35 +0000
Subject: [Kolab-devel] [issue3310] Sending a signed mail with unsigned
	attachment doesn't work
Message-ID: <1228908215.58.0.782137557558.issue3310@intevation.de>


New submission from Ludwig Reiter <ludwig at intevation.de>:

enterprise35 20081202.891698

Test:
Has a OpenPGP key configured.
1. Switch to the mail plugin.
2. Start to send a signed mail.(encryption type "all")
3. Add an attachment.
4. Deactivate to sign the attachment.
5. Send the mail.
Actual behaviour: The signature of the mail includes the attachment.
Excepted behavior: The signature should not included the atttachment as 
I choose not to sign the attachment.

If I choose as encryption type "OpenPGP", all works fine.

----------
assignedto: till
messages: 18018
nosy: bernhard, bh, ludwig, osterfeld, pradeepto, till
priority: bug
status: unread
title: Sending a signed mail with unsigned attachment doesn't work
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3310>
___________________________________________________


From kolab-issues at intevation.de  Thu Dec 11 21:15:37 2008
From: kolab-issues at intevation.de (Malone A Dina)
Date: Thu, 11 Dec 2008 20:15:37 +0000
Subject: [Kolab-devel] [issue3311] Healthcare Industry Listing
Message-ID: <AGRI-EXCHANGETRURqY0000079b@agri-exchange.agrimaster.com.au>


New submission from Malone A Dina <Reva at bvv66.internetdsl.tpnet.pl>:

Licensed MDs in the USA 

788,837 in total <> 17,276 emails

Coverage for many different medical specialties

many fields which can easily be sorted in excel

Regular price is $492 but this week you only pay: $392

======= Take all 4 items below for F REE when you order =======

Directory of US Pharma Companies
Personal email addresses (47,000 in total) and names for top level executives

American Hospital Mailing List
complete contact information for CEO's, CFO's, Directors and more - over 23,000 listings in total for more than 7,000 hospitals in the USA

Dentists in the USA
More than half a million listings [worth $499 alone!]

Database of US Chiropractors
100k Chiropractors offices with full contact data including email, postal address, phone and fax

contact your rep:      Willis at contactpluscorp.com

from today until this Friday

Forward email to suspend at contactpluscorp.com to purge you from our records

----------
messages: 18031
nosy: Reva
status: unread
title: Healthcare Industry Listing
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3311>
___________________________________________________


From martin.konold at erfrakon.de  Thu Dec 11 22:14:27 2008
From: martin.konold at erfrakon.de (Martin Konold)
Date: Thu, 11 Dec 2008 22:14:27 +0100
Subject: [Kolab-devel] bug in seperator and freebusy ?
In-Reply-To: <492D1927.6080300@kovoks.nl>
References: <492D1927.6080300@kovoks.nl>
Message-ID: <200812112214.28683.martin.konold@erfrakon.de>

Am Mittwoch, 26. November 2008 10:38:47 schrieb Ronald van Eendenburg:

Hi Ronald,

>  I have a quaestion regarding the separator used.
>
>  Why is the seperator used a '.' instead of a '/' in the shared folder.
>  Now the 'shared' folder shows a series of shared.foldername folders. If i
> change the foldernames in cyrus, in for instance shared/foldername the
> folders become subfolders of shared. This is, as far as i know, some kind
> of a standard in shared folder use.

I don'T fully understand this question but the display of the folder hierarchy 
is a matter of the IMAP client not the server.

>  And also why is it not named 'shared folders' instead of 'shared'.

This is also up to the IMAP to decide how to display an IMAP namespace. E.g. 
the German Version of KONSEC Konnektor displays "Freigegebene Ordner".

>  If i adjust this, the management is lost of this folders. is there any way
> to change this in some kind of way so when i make a new folder in the kolab
> admin page, this will set in also LDAP and in cyrus with a / as seperator?

Why do you want to modify the IMAP separator?

> If i adjust the foldername in cyrus to 'shared folder', horde will start,
> but without sidebar. Maybe it will be nice to aks in the bootstrap the name
> of the shared folder instance, like: Name of shared folder: [Shared
> Folder]:?? < (as default)

The presentation of folders need to be changed in Horde Webclient not in the 
Server.

>  Also the freebusy doesn't work. it generates an error is i want to make an
> appointment in the calendar and try to lookup an attendee's free busy.

>  I installed kolab server 2.2 final (horde parts show 2.2RC3) in debian,
> with the debian-source.

Please note that the horde released with 2.2 final is not of production 
quality. Thigs will improve with the upcoming 2.2.1 which mainly got fixes for 
Horde.

Regards,
-- martin

-- 
e r f r a k o n
Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
Sitz: Adolfstra?e 23, 70469 Stuttgart, Partnerschaftsregister Stuttgart PR 126
http://www.erfrakon.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-devel/attachments/20081211/7462e34e/attachment.html

From ml at radoeka.nl  Thu Dec 11 22:37:21 2008
From: ml at radoeka.nl (Richard Bos)
Date: Thu, 11 Dec 2008 22:37:21 +0100
Subject: [Kolab-devel] bug in seperator and freebusy ?
In-Reply-To: <200812112214.28683.martin.konold@erfrakon.de>
References: <492D1927.6080300@kovoks.nl>
	<200812112214.28683.martin.konold@erfrakon.de>
Message-ID: <200812112237.21968.ml@radoeka.nl>

Op Thursday 11 December 2008 22:14:27 schreef Martin Konold:
> > ?If i adjust this, the management is lost of this folders. is there any
> > way to change this in some kind of way so when i make a new folder in the
> > kolab admin page, this will set in also LDAP and in cyrus with a / as
> > seperator?
>
> Why do you want to modify the IMAP separator?

I assume because at the moment it is possible to get a folder hierarchy for 
regular folders, like:

folder-A
  folder-1
  folder-2
folder-B
  folder-1
etc

But the shared folders are all shown in the folder-[AB] level not on 
folder-[12] level.  Currently it is like this:
folder-A
  folder-1
  folder-2
folder-B
  folder-1
shared.folder1
shared.folder2
...
shared.folder20

I think that it would indeed be better that, like:
folder-A
  folder-1
  folder-2
folder-B
  folder-1
shared
  folder
  folder2
  ...
  folder20

> > If i adjust the foldername in cyrus to 'shared folder', horde will start,
> > but without sidebar. Maybe it will be nice to aks in the bootstrap the
> > name of the shared folder instance, like: Name of shared folder: [Shared
> > Folder]:   < (as default)
>
> The presentation of folders need to be changed in Horde Webclient not in
> the Server.

It's not only in horde, also in kontact.


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


From martin.konold at erfrakon.de  Fri Dec 12 09:59:40 2008
From: martin.konold at erfrakon.de (Martin Konold)
Date: Fri, 12 Dec 2008 09:59:40 +0100
Subject: [Kolab-devel] bug in seperator and freebusy ?
In-Reply-To: <200812112237.21968.ml@radoeka.nl>
References: <492D1927.6080300@kovoks.nl>
	<200812112214.28683.martin.konold@erfrakon.de>
	<200812112237.21968.ml@radoeka.nl>
Message-ID: <200812120959.41241.martin.konold@erfrakon.de>

Am Donnerstag, 11. Dezember 2008 22:37:21 schrieb Richard Bos:

Hi Richard,

> I assume because at the moment it is possible to get a folder hierarchy for
> regular folders, like:
>
> folder-A
>   folder-1
>   folder-2
> folder-B
>   folder-1
> etc
>
> But the shared folders are all shown in the folder-[AB] level not on
> folder-[12] level.  Currently it is like this:
> folder-A
>   folder-1
>   folder-2
> folder-B
>   folder-1
> shared.folder1
> shared.folder2
> ...
> shared.folder20

> I think that it would indeed be better that, like:
> folder-A
>   folder-1
>   folder-2
> folder-B
>   folder-1
> shared
>   folder
>   folder2
>   ...
>   folder20

But folder-A and folder-B are below the INBOX namespace while folder1 is below 
the shared Namespace. In your example 

shared
  folder1
  folder2
  ---
  folder20

would not be distinguishable from folders

INBOX/shared/folder1
INBOX/shared/folder2
....

Basically this means that it must be clear that these folders are not 
subfolders of the users INBOX but that they are shared/public folders.

In general there are three namespaces in Kolab.

1. personal namespace
These are all folders which are located below the users INBOX

- shared folders
There are folders which are made available to other users and groups using 
IMAP ACLs. This namespace is indicated by "user/"

- public folders
These are folders created by an administrator which do not belong to any user. 
Unfortunately these public folders are announces using the keyword "shared". 

Yours,
-- martin

-- 
e r f r a k o n
Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
Sitz: Adolfstra?e 23, 70469 Stuttgart, Partnerschaftsregister Stuttgart PR 126
http://www.erfrakon.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-devel/attachments/20081212/407ffcea/attachment-0001.html

From kolab-issues at intevation.de  Fri Dec 12 10:26:01 2008
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Fri, 12 Dec 2008 09:26:01 +0000
Subject: [Kolab-devel] [issue3312] Kontact smoetimes crashs,
	if a contact is changed with the contact editor
Message-ID: <1229073961.53.0.868919609561.issue3312@intevation.de>


New submission from Ludwig Reiter <ludwig at intevation.de>:

enterprise 20081202.891698-kk2

Changing the name of a contact in the contact editor and switching to another
contact in the contact list, sometimes crashs kontact.
I can reproduce this bug with some tries. Kontact doesn't crash every time.

Test 
1. Switch to the contact plugin
2. Activate the editor view.
3. Change the name of a contact and switch to another contact. (repeat this for
   many times)

Auto sync of groupware folders by change is activated.
See bt.

----------
assignedto: till
files: crash-contact-editor-20081212.txt
messages: 18032
nosy: bernhard, bh, ludwig, osterfeld, pradeepto, till
priority: urgent
status: unread
title: Kontact smoetimes crashs, if a contact is changed with the contact editor
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3312>
___________________________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: crash-contact-editor-20081212.txt
Url: http://kolab.org/pipermail/kolab-devel/attachments/20081212/7f94f71c/crash-contact-editor-20081212.txt

From kolab-issues at intevation.de  Fri Dec 12 20:10:13 2008
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Fri, 12 Dec 2008 19:10:13 +0000
Subject: [Kolab-devel] [issue3313] free/busy regeneration as manager broken
	in 2.2.1-beta1
Message-ID: <1229109013.63.0.444259000154.issue3313@intevation.de>


New submission from Thomas Arendsen Hein <thomas at intevation.de>:

The new URL is https://kolab.example.com/freebusy/regenerate.php

Regeneration as user is still possible, but when doing it as manager, the
following error occurs:
Failed regenerating calendar user/theUser/Calendar at exampple.com: IMAP error.
Server: example.com. Error: IMAP Authentication cancelled

This worked in 2.2.0

----------
assignedto: wrobel
messages: 18053
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: critical
status: unread
title: free/busy regeneration as manager broken in 2.2.1-beta1
topic: release, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3313>
___________________________________________________


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-devel] 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-devel/attachments/20081212/7d077f3f/attachment-0001.bin

From soliva at comcept.ch  Mon Dec 15 05:34:36 2008
From: soliva at comcept.ch (ComCept Soliva)
Date: Mon, 15 Dec 2008 05:34:36 +0100
Subject: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1 SSL/TLS
	libraries were missing or unusable
Message-ID: <9268C7D7C7AB4CDCBF0DCE7A201F33F9@comcept.ch>

Hi all

your modifications within the install-kolab.sh script regarding PLATTAG
seems to work fine. 

All positions regarding mindepth/maxdepth I had to remove because Solaris
does not support mindepth/maxdepth within find ([Kolab-devel] [issue2924]).

Before I started I verified that there is nothing at all within tmp and
following env variable are in use:

SunOS dev 5.10 Generic_137111-08 sun4u sparc SUNW,Ultra-4

# env

_=/usr/bin/env
LANG=C
HZ=
PATH=/usr/sbin:/usr/bin:/usr/dt/bin:/usr/openwin/bin:/bin:/usr/ucb:/opt/sfw/
bin:/usr/local/bin:/usr/ccs/bin
HISTFILE=/root/.sh_history
LOGNAME=root
MAIL=/var/mail/root
PS1=[root at dev $PWD]# 
SHELL=/sbin/sh
HISTSIZE=200
HOME=/root
TERM=vt100
PWD=/kolabtmp
TZ=MET
ENV=/root/.kshrc

# crle

Configuration file [version 4]: /var/ld/ld.config  
  Default Library Path (ELF):   /lib:/usr/lib:/usr/local/lib
  Trusted Directories (ELF):    /lib/secure:/usr/lib/secure  (system
default)


The compilation stopps within apache regarding SSL/TLS:

checking whether to enable mod_ssl... checking dependencies
checking for SSL/TLS toolkit base... /kolab
  adding "-R/kolab/lib" to LDFLAGS
checking for OpenSSL version... checking openssl/opensslv.h usability... yes
checking openssl/opensslv.h presence... yes
checking for openssl/opensslv.h... yes
checking openssl/ssl.h usability... yes
checking openssl/ssl.h presence... yes
checking for openssl/ssl.h... yes
OK
  forcing SSL_LIBS to "-lssl -lcrypto"
checking openssl/engine.h usability... yes
checking openssl/engine.h presence... yes
checking for openssl/engine.h... yes
checking for SSLeay_version... yes
checking for SSL_CTX_new... no
checking for ENGINE_init... no
checking for ENGINE_load_builtin_engines... no
checking for SSL_set_cert_store... no
configure: error: ... Error, SSL/TLS libraries were missing or unusable
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)


RPM build errors:
    Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
+ exit 1 



Full Log File can be downloaeded from following link:

http://www.comcept.ch/kolab2/2.2.1-beta1/kolab-install-Dec-14-08_44_54.zip

More information about install can be found at:

http://www.comcept.ch/kolab2/2.2.1-beta1/solaris_10_kolab2_install.txt



OpenSSL was compiled and installed successful:


Processing files: openssl-0.9.8g-20080101
Wrote: /kolab/RPM/PKG/openssl-0.9.8g-20080101.sparc64-solaris10-kolab.rpm
Executing(%clean): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix
-e /kolab/RPM/TMP/rpm-tmp.699
+ cd /kolab/RPM/TMP
+ cd openssl-0.9.8g
+ rm -rf /kolab/RPM/TMP/openssl-0.9.8g-root
+ exit 0
Executing(--clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
--posix -e /kolab/RPM/TMP/rpm-tmp.17537
+ cd /kolab/RPM/TMP
+ rm -rf openssl-0.9.8g
+ exit 0
Preparing...
##################################################
openssl
##################################################
:::: /tmp/install-kolab....27392/openssl-0.9.8g-20080101.src.rpm = 0 ::::

The library is also there:

# ls -la /kolab/lib/libssl*
-rw-r--r--   1 kolab    kolab     403268 Dec 14 18:00 /kolab/lib/libssl.a



Within the include dir openssl dir exists:

# ls -la /kolab/include/openssl
total 1264
drwxr-xr-x   2 kolab    kolab         70 Dec 14 18:02 .
drwxr-xr-x  14 kolab    kolab         41 Dec 14 21:39 ..
-rw-r--r--   1 kolab    kolab       5372 Dec 14 17:59 aes.h
-rw-r--r--   1 kolab    kolab      46728 Dec 14 17:59 asn1.h
-rw-r--r--   1 kolab    kolab      18956 Dec 14 17:59 asn1_mac.h
-rw-r--r--   1 kolab    kolab      27838 Dec 14 17:59 asn1t.h
-rw-r--r--   1 kolab    kolab      30772 Dec 14 17:59 bio.h
-rw-r--r--   1 kolab    kolab       5073 Dec 14 17:59 blowfish.h
-rw-r--r--   1 kolab    kolab      33035 Dec 14 17:59 bn.h
-rw-r--r--   1 kolab    kolab       4565 Dec 14 17:59 buffer.h
-rw-r--r--   1 kolab    kolab       4349 Dec 14 17:59 cast.h
-rw-r--r--   1 kolab    kolab       1601 Dec 14 17:59 comp.h
-rw-r--r--   1 kolab    kolab       9484 Dec 14 17:59 conf.h
-rw-r--r--   1 kolab    kolab       4080 Dec 14 17:59 conf_api.h
-rw-r--r--   1 kolab    kolab      22121 Dec 14 17:59 crypto.h
-rw-r--r--   1 kolab    kolab      10724 Dec 14 17:59 des.h
-rw-r--r--   1 kolab    kolab      18226 Dec 14 17:59 des_old.h
-rw-r--r--   1 kolab    kolab       8372 Dec 14 17:59 dh.h
-rw-r--r--   1 kolab    kolab      10474 Dec 14 17:59 dsa.h
-rw-r--r--   1 kolab    kolab      16252 Dec 14 17:59 dso.h
-rw-r--r--   1 kolab    kolab       6146 Dec 14 17:59 dtls1.h
-rw-r--r--   1 kolab    kolab       9632 Dec 14 17:59 e_os2.h
-rw-r--r--   1 kolab    kolab        540 Dec 14 17:59 ebcdic.h
-rw-r--r--   1 kolab    kolab      21389 Dec 14 17:59 ec.h
-rw-r--r--   1 kolab    kolab       4609 Dec 14 17:59 ecdh.h
-rw-r--r--   1 kolab    kolab      10578 Dec 14 17:59 ecdsa.h
-rw-r--r--   1 kolab    kolab      37839 Dec 14 17:59 engine.h
-rw-r--r--   1 kolab    kolab      12493 Dec 14 17:59 err.h
-rw-r--r--   1 kolab    kolab      35620 Dec 14 17:59 evp.h
-rw-r--r--   1 kolab    kolab       4368 Dec 14 17:59 hmac.h
-rw-r--r--   1 kolab    kolab       7642 Dec 14 17:59 krb5_asn.h
-rw-r--r--   1 kolab    kolab       5927 Dec 14 17:59 kssl.h
-rw-r--r--   1 kolab    kolab       7429 Dec 14 17:59 lhash.h
-rw-r--r--   1 kolab    kolab       3897 Dec 14 17:59 md2.h
-rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md4.h
-rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md5.h
-rw-r--r--   1 kolab    kolab     113729 Dec 14 17:59 obj_mac.h
-rw-r--r--   1 kolab    kolab      33396 Dec 14 17:59 objects.h
-rw-r--r--   1 kolab    kolab      23795 Dec 14 17:59 ocsp.h
-rw-r--r--   1 kolab    kolab       6533 Dec 14 17:59 opensslconf.h
-rw-r--r--   1 kolab    kolab       3751 Dec 14 17:59 opensslv.h
-rw-r--r--   1 kolab    kolab       6446 Dec 14 17:59 ossl_typ.h
-rw-r--r--   1 kolab    kolab      27927 Dec 14 17:59 pem.h
-rw-r--r--   1 kolab    kolab       2863 Dec 14 17:59 pem2.h
-rw-r--r--   1 kolab    kolab      12677 Dec 14 17:59 pkcs12.h
-rw-r--r--   1 kolab    kolab      16333 Dec 14 17:59 pkcs7.h
-rw-r--r--   1 kolab    kolab       6150 Dec 14 17:59 pq_compat.h
-rw-r--r--   1 kolab    kolab       3519 Dec 14 17:59 pqueue.h
-rw-r--r--   1 kolab    kolab       5251 Dec 14 17:59 rand.h
-rw-r--r--   1 kolab    kolab       4294 Dec 14 17:59 rc2.h
-rw-r--r--   1 kolab    kolab       3707 Dec 14 17:59 rc4.h
-rw-r--r--   1 kolab    kolab       4284 Dec 14 17:59 ripemd.h
-rw-r--r--   1 kolab    kolab      18202 Dec 14 17:59 rsa.h
-rw-r--r--   1 kolab    kolab     126893 Dec 14 17:59 safestack.h
-rw-r--r--   1 kolab    kolab       7329 Dec 14 17:59 sha.h
-rw-r--r--   1 kolab    kolab      82501 Dec 14 17:59 ssl.h
-rw-r--r--   1 kolab    kolab      10716 Dec 14 17:59 ssl2.h
-rw-r--r--   1 kolab    kolab       3744 Dec 14 17:59 ssl23.h
-rw-r--r--   1 kolab    kolab      22283 Dec 14 17:59 ssl3.h
-rw-r--r--   1 kolab    kolab       4418 Dec 14 17:59 stack.h
-rw-r--r--   1 kolab    kolab      26481 Dec 14 17:59 store.h
-rw-r--r--   1 kolab    kolab      19456 Dec 14 17:59 symhacks.h
-rw-r--r--   1 kolab    kolab      18121 Dec 14 17:59 tls1.h
-rw-r--r--   1 kolab    kolab       4117 Dec 14 17:59 tmdiff.h
-rw-r--r--   1 kolab    kolab       4300 Dec 14 17:59 txt_db.h
-rw-r--r--   1 kolab    kolab      16418 Dec 14 17:59 ui.h
-rw-r--r--   1 kolab    kolab       3439 Dec 14 17:59 ui_compat.h
-rw-r--r--   1 kolab    kolab      47946 Dec 14 17:59 x509.h
-rw-r--r--   1 kolab    kolab      20782 Dec 14 17:59 x509_vfy.h
-rw-r--r--   1 kolab    kolab      29980 Dec 14 17:59 x509v3.h


What is going wrong here....? How to proceed.....? If you need more
information please tell me.

kinde regards

Andrea Soliva

Mail: soliva at comcept.ch 


From kolab-issues at intevation.de  Mon Dec 15 08:47:47 2008
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Mon, 15 Dec 2008 07:47:47 +0000
Subject: [Kolab-devel] [issue3314] Contact folder selection statenot saved
	between KDE sessions
Message-ID: <1229327267.36.0.706733630302.issue3314@intevation.de>


New submission from Bernhard Reiter <bernhard at intevation.de>:

To reproduce
a) have an account where you have a few contact folders deselected
when you start kontact (e.g. 1 seleted, 2 deselected)
b) now select a few more (e.g. all) contact folders
c) close kontact, start kontact
   Observation: the selection from b) is there. (Matches expectation)
d) close the KDE session (e.g. logout or kill all kde processes, dcopserver..)
   start kontact again
   Observation: Selection is back to a).
   Expectation: Should still be b).


Version: 4:3.5.10.enterprise.0.20081202.891698-kk2

----------
assignedto: till
messages: 18076
nosy: bernhard, ludwig, till, vkrause
priority: bug
status: unread
title: Contact folder selection statenot saved between KDE sessions
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3314>
___________________________________________________


From itsef-admin at brightsight.com  Mon Dec 15 09:24:30 2008
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Mon, 15 Dec 2008 09:24:30 +0100
Subject: [Kolab-devel] Policy wrt "unstable" Debian Kontact packages?
In-Reply-To: <200812021814.31429.itsef-admin@brightsight.com>
References: <200812021814.31429.itsef-admin@brightsight.com>
Message-ID: <200812150924.31009.itsef-admin@brightsight.com>

On Tuesday 2 December 2008 18:14:31 ITSEF Admin wrote:
> Over the past months, I'm tracking the unstable Debian packages for the
> Kontact enterprise35 client
> (http://apt.intevation.de/dists/etch/unstable/source/) as I use them as
> base for our custom Kubuntu Hardy packages.
[...]
> Today *both* versions were removed from "unstable" and the latest version
> is now 862683.

As it just happened again (891698 got pulled - 862683 is yet again the latest 
version in "unstable"), I'd like to repeat my question: How is the decision 
made to have a version in "unstable" and is there a place where I can find 
the reasoning behind that decision?

Thanks in advance,

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


From kolab-issues at intevation.de  Tue Dec 16 09:46:02 2008
From: kolab-issues at intevation.de (Daniel Vergien)
Date: Tue, 16 Dec 2008 08:46:02 +0000
Subject: [Kolab-devel] [issue3315] PEAR-Horde-Channel-1.0 fails to compile
	on solaris 10
Message-ID: <1229417162.59.0.780352058727.issue3315@intevation.de>


New submission from Daniel Vergien <daniel.vergien at web.de>:

Compiling the package fails on solaris 10 because /usr/sbin/install is called
with the -p option which does not exists on solaris install. As a workaround I
placed another install script in /usr/sbin/install during installation. Is -p
realy needed?

Daniel

----------
messages: 18088
nosy: daniel.vergien
status: unread
title: PEAR-Horde-Channel-1.0 fails to compile on solaris 10
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3315>
___________________________________________________


From math.parent at gmail.com  Tue Dec 16 11:22:24 2008
From: math.parent at gmail.com (Mathieu Parent)
Date: Tue, 16 Dec 2008 11:22:24 +0100
Subject: [Kolab-devel] KDE Kolab Clients betas
Message-ID: <960738410812160222s6dd07008t1283a184c76b9f9e@mail.gmail.com>

Hi,

What is the status of enterprise4, on linux and on windows ? I'm
interested to test but can't find windows builds, or build procedure.

Roadmap says beta end of 2008 (http://kolab.org/roadmap.html).

Regards

Mathieu Parent


From kolab-issues at intevation.de  Tue Dec 16 11:50:16 2008
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Tue, 16 Dec 2008 10:50:16 +0000
Subject: [Kolab-devel] [issue3316] Doubled folder lists in move-to
	filteraction selection dialog
Message-ID: <1229424616.37.0.934393261666.issue3316@intevation.de>


New submission from Bernhard Reiter <bernhard at intevation.de>:

Go to the configuration of filters in the email view,
select a filter action of move into folder and use the folder selection
button.

Now you can see that each folder is listed twice starting from the two
top folders. (See attached screenshot.)
Kontact Version: 4:3.5.10.enterprise.0.20081202.891698-kk2

Note: There are also reports that it might be possible that the two lists
for one top folder are different. This might be an update problem
and should be solved with this issue as it leads to problems in folder 
selection.

----------
assignedto: till
files: kontact-e35-filter-problem.png
messages: 18089
nosy: bernhard, ludwig, till, vkrause
priority: bug
status: unread
title: Doubled folder lists in move-to filteraction selection dialog
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3316>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kontact-e35-filter-problem.png
Type: image/png
Size: 23014 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20081216/674a4666/kontact-e35-filter-problem-0001.png

From kolab-issues at intevation.de  Tue Dec 16 12:03:23 2008
From: kolab-issues at intevation.de (Daniel Vergien)
Date: Tue, 16 Dec 2008 11:03:23 +0000
Subject: [Kolab-devel] [issue3318] kolab-fbview-1.2.0-20081212 fails to
	compile on solaris 10
Message-ID: <1229425403.68.0.398336650757.issue3318@intevation.de>


New submission from Daniel Vergien <daniel.vergien at web.de>:

Trying to build 2.2.1-beta on solaris 10 fails at kolab-fbview with the
following messeage:

+ cp -r COPYING README admin config docs index.php js kronolith lib locale log
login.php notconfigured.html pear po rpc rpc.php scripts services signup.php
storage templates themes tmp turba util
/kolab/RPM/TMP/kolab-fbview-1.2.0-root/kolab/var/kolab/www/fbview/
cp: cannot open log/.htaccess.orig: Permission denied
cp: cannot open storage/.htaccess.orig: Permission denied
cp: cannot open tmp/.htaccess.orig: Permission denied
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.135 (%install)

In the dir
/kolab/RPM/TMP/kolab-fbview-1.2.0-root/kolab/var/kolab/www/fbview/log/ there is
no .htaccess.orig just a .htaccess - the same in storage and tmp.


Full log is attached

----------
files: kolab-build.log
messages: 18092
nosy: daniel.vergien
priority: bug
status: unread
title: kolab-fbview-1.2.0-20081212 fails to compile on solaris 10
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3318>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kolab-build.log
Type: application/octet-stream
Size: 21783 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20081216/02aba5b2/kolab-build-0001.exe

From kolab-issues at intevation.de  Tue Dec 16 12:12:16 2008
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Tue, 16 Dec 2008 11:12:16 +0000
Subject: [Kolab-devel] [issue3319] kmail executes "gpg" for decrypting
	(deprecated) inline OpenPGP, should be gpg2
Message-ID: <1229425935.97.0.665196819461.issue3319@intevation.de>


New submission from Bernhard Reiter <bernhard at intevation.de>:

With Kontact Version: 4:3.5.10.enterprise.0.20081202.891698-kk2
clicking on a (deprecated) inline OpenPGP encrypted email
the console output has:

ibkdenetwork: user uses gpg-agent -> don't ask for passphrase
libkdenetwork: GnuPG exited with exit status 2
libkdenetwork: gpg stderr:
libkdenetwork: libkdenetwork: pgp cmd = LANGUAGE=C 
gpg --use-agent --batch --decrypt

Now here comes the problem, because of gpg2 options set this does not work:
gpg: /home/btee/.gnupg/gpg.conf:17: invalid option

There is no error message, the email just stays encrypted and is shown
in raw text format. (Which probably is fine I guess as this deprecated format 
cannot reliably detected.)

This might come out of Package: libkleopatra1
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 1856
Maintainer: Kolab-Konsortium Packager <packaging at kolab-konsortium.de>
Architecture: i386
Source: kdepim
Version: 4:3.5.10.enterprise.0.20081215.896091-kk1
Replaces: libkdenetwork2, libkleopatra0a
Depends: kdelibs4c2a (>= 4:3.5.5a.dfsg.1-8etch1), libc6 (>= 2.3.6-6), libgcc1 
(>= 1:4.1.1-12), libgpg-error0 (>= 1.6), libgpgme11 (>= 1.1.6), libice6 (>= 
1:1.0.0), libpng12-0 (>= 1.2.13-4), libqt3-mt (>= 3:3.3.7), libsm6, libstdc++6 
(>= 4.1.1-12), libx11-6, libxext6, zlib1g (>= 1:1.2.1), perl, gnupg

My open is that gpg2 is used, if installed
and the mid term goal to keep our packages clear of gpg(1)
so that it could be deinstalled.

Bh, can you see if we can fix this?

----------
assignedto: bh
messages: 18093
nosy: bernhard, bh, ludwig
priority: bug
status: unread
title: kmail executes "gpg" for decrypting (deprecated) inline OpenPGP, should be gpg2
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3319>
___________________________________________________


From kolab-issues at intevation.de  Tue Dec 16 14:35:23 2008
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 16 Dec 2008 13:35:23 +0000
Subject: [Kolab-devel] [issue3320] Export a contact with umlauts in his name
	as VCard3 and import it, breaks the umlaut.
Message-ID: <1229434523.66.0.0242895346906.issue3320@intevation.de>


New submission from Ludwig Reiter <ludwig at intevation.de>:

enterprise35 kdepim rev. 20081215.896091

Export a contact, which has umlauts in its name, like "G?nther Goblin" as
VCard3, and importing it, breaks the display of the umlauts.
This should work.

----------
assignedto: till
messages: 18098
nosy: bernhard, bh, ludwig, osterfeld, pradeepto, till
priority: bug
status: unread
title: Export a contact with umlauts in his name as VCard3 and import it, breaks the umlaut.
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3320>
___________________________________________________


From kolab-issues at intevation.de  Tue Dec 16 16:32:57 2008
From: kolab-issues at intevation.de (Mathieu Parent)
Date: Tue, 16 Dec 2008 15:32:57 +0000
Subject: [Kolab-devel] [issue3321] slapd.replicas.template and
	slapd.access.template can be absent
Message-ID: <1229441577.01.0.133946071572.issue3321@intevation.de>


New submission from Mathieu Parent <mathieuparent at users.sourceforge.net>:

In some configurations, the LDAP server can be on another machine, or configured
outside of kolabconf.

This patch permit this.

I will commit it within 2 weeks if there is no objection (no risk).

----------
assignedto: mathieu.parent
files: issue.diff
messages: 18100
nosy: mathieu.parent, rbos, thomas
priority: wish
status: unread
title: slapd.replicas.template and slapd.access.template can be absent
topic: patch, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3321>
___________________________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: issue.diff
Url: http://kolab.org/pipermail/kolab-devel/attachments/20081216/97fb166d/issue.txt

From kolab-issues at intevation.de  Tue Dec 16 16:45:10 2008
From: kolab-issues at intevation.de (Mathieu Parent)
Date: Tue, 16 Dec 2008 15:45:10 +0000
Subject: [Kolab-devel] [issue3322] freebusy.conf.template: ldap server can
	be on another machine
Message-ID: <1229442310.2.0.074351911653.issue3322@intevation.de>


New submission from Mathieu Parent <mathieuparent at users.sourceforge.net>:

Current configuration of freebusy connects to local host (fqdn). This is good
because readonly access is sufficient (as available on slave LDAP servers).

but ;)

If the LDAP server(s) are on another machine, it failed. The attached patch
makes it always connect to ldap master.

Is this OK to apply it?

----------
assignedto: mathieu.parent
files: freebusy.conf.template.in.diff
messages: 18102
nosy: mathieu.parent, rbos, thomas, wrobel
priority: feature
status: unread
title: freebusy.conf.template: ldap server can be on another machine
topic: freebusy, patch, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3322>
___________________________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: freebusy.conf.template.in.diff
Url: http://kolab.org/pipermail/kolab-devel/attachments/20081216/b715f56b/freebusy.conf.template.in.txt

From kolab-issues at intevation.de  Wed Dec 17 06:33:20 2008
From: kolab-issues at intevation.de (custer Ponce)
Date: Wed, 17 Dec 2008 05:33:20 +0000
Subject: [Kolab-devel] [issue3323] D e ntists Directory in the USA
Message-ID: <47AF4C90-4E42-4F56-ACD1-67CD74C03B77@mail.pc-connect.be>


New submission from custer Ponce <Terry at mal-mail.mobileaccess.com>:

Generate more targeted sales leads

** 164,248 Dentists 
** 158,359 Mailing Addresses
** 163,759 Phone Nos
** 77,922 Fax Nos.
** 45,050 Emails

only during this week this can be yours for just $290 (usually $596)

Send an email to Pettit at idocinfo.com to inquire about this and other Listing we have

By emailing unlisting at idocinfo.com you will have your email taken off

----------
messages: 18105
nosy: Terry, adjusthealth, finance, jeff.ganley, journals_marketing, mserpe, rkatz
status: unread
title: D e ntists Directory in the USA
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3323>
___________________________________________________


From kolab-issues at intevation.de  Wed Dec 17 14:15:23 2008
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Wed, 17 Dec 2008 13:15:23 +0000
Subject: [Kolab-devel] [issue3324] can delete attachments in read-only
	folders
Message-ID: <1229519723.13.0.68087555737.issue3324@intevation.de>


New submission from Bernhard Reiter <bernhard at intevation.de>:

Kontact Version 1.2.9 (enterprise35 20081215.896091)
I've been given a mailinglist from a group users as read-only.
On an email I've deleted the attachment and it looked fine.
With the next sync this email was moved to lost-and-found.

IMHO attachment deletion should not be possible on read-only folders.

----------
assignedto: till
messages: 18108
nosy: bernhard, ludwig, till, vkrause
priority: bug
status: unread
title: can delete attachments in read-only folders
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3324>
___________________________________________________


From kolab-issues at intevation.de  Wed Dec 17 14:32:20 2008
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 17 Dec 2008 13:32:20 +0000
Subject: [Kolab-devel] [issue3325] Importing a vCard Contact list with many
	contacts while no resource is activated,
	throws a lot of error messages.
Message-ID: <1229520740.3.0.204249632931.issue3325@intevation.de>


New submission from Ludwig Reiter <ludwig at intevation.de>:

enterprise35 kdepim 20081215.896091

Test:
Req: A vCard file "test1.vcf" with 3 contacts in it.
1. Switch to the contacts plugin
2. Deactivate all resources.
3. Import the test1.vcf with Import->vCard.
=> The "No resource" error message appears three times.

----------
assignedto: till
messages: 18109
nosy: bernhard, bh, ludwig, osterfeld, pradeepto, till
priority: minor bug
status: unread
title: Importing a vCard Contact list with many contacts while no resource is activated, throws a lot of error messages.
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3325>
___________________________________________________


From kolab-issues at intevation.de  Wed Dec 17 15:31:12 2008
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 17 Dec 2008 14:31:12 +0000
Subject: [Kolab-devel] [issue3326] calendar schedule menu items doesn't work
Message-ID: <1229524272.29.0.623810803431.issue3326@intevation.de>


New submission from Ludwig Reiter <ludwig at intevation.de>:

enterprise35 kdepim 20081215.896091

The calendar plugin "Schedule" menu entries doesn't seem to work.

Test:
1. Switch to the calnedar plugin.
2. Create a new event.
3. Select the event.
4. Choose Schedule->Send invitation to attendees.
=> An error message appears:
   Unable to send the item 'test C'. 
   Method: Request
and the invitation is send. 
This error message is missleading. It seems like the invition is not send,
but it is send.

Please look at the other items in the "Schedule" menu, too.

----------
assignedto: till
messages: 18113
nosy: bernhard, bh, ludwig, osterfeld, pradeepto, till
priority: bug
status: unread
title: calendar schedule menu items doesn't work
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3326>
___________________________________________________


From kolab-issues at intevation.de  Thu Dec 18 10:50:47 2008
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 18 Dec 2008 09:50:47 +0000
Subject: [Kolab-devel] [issue3327] Crash in KMCommand::transferSelectedMsgs
	while selection of a folder
Message-ID: <1229593847.51.0.736259310514.issue3327@intevation.de>


New submission from Ludwig Reiter <ludwig at intevation.de>:

enterprise35 20081202.891698

A user reported a crash.
He has selected a folder and the crash appears.

See the backtrace.

----------
assignedto: till
files: kontact_crash-20081217.txt
messages: 18118
nosy: bernhard, bh, ludwig, osterfeld, pradeepto, till
priority: urgent
status: unread
title: Crash in KMCommand::transferSelectedMsgs while selection of a folder
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3327>
___________________________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: kontact_crash-20081217.txt
Url: http://kolab.org/pipermail/kolab-devel/attachments/20081218/f3f2fb36/kontact_crash-20081217.txt

From kolab-issues at intevation.de  Thu Dec 18 15:56:01 2008
From: kolab-issues at intevation.de (Sascha Wilde)
Date: Thu, 18 Dec 2008 14:56:01 +0000
Subject: [Kolab-devel] [issue3328] [Webclient] DIMP groupware folder names
	display bug
Message-ID: <1229612161.32.0.293801230839.issue3328@intevation.de>


New submission from Sascha Wilde <wilde at intevation.de>:

When using Dimp (Dynamic Mail) the names of the groupware folders in the mail
folder navigation are displayed _below_ their respective icons and overlap the
icons and foldernames below.  They should be displayed on the right of the icons
as with all other folders.

----------
assignedto: wrobel
messages: 18125
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: critical
status: unread
title: [Webclient] DIMP groupware folder names display bug
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3328>
___________________________________________________


From kolab-issues at intevation.de  Thu Dec 18 16:14:44 2008
From: kolab-issues at intevation.de (Sascha Wilde)
Date: Thu, 18 Dec 2008 15:14:44 +0000
Subject: [Kolab-devel] [issue3329] [WebClient] Can not accept/deny
	invitations in Dimp
Message-ID: <1229613284.39.0.919317546234.issue3329@intevation.de>


New submission from Sascha Wilde <wilde at intevation.de>:

When using Dimp the actions-menu is missing from messages containing an
invitation, when using Imp this menu contains options to accept, deny the
requested event.

This is an essential feature of the groupware functionality and therefor has to
be fixed for the release.

----------
assignedto: wrobel
messages: 18126
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: critical
status: unread
title: [WebClient] Can not accept/deny invitations in Dimp
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3329>
___________________________________________________


From kolab-issues at intevation.de  Thu Dec 18 22:12:10 2008
From: kolab-issues at intevation.de (Gunnar Wrobel)
Date: Thu, 18 Dec 2008 21:12:10 +0000
Subject: [Kolab-devel] [issue3330] Ics files via Horde do not work for
	folders containing spaces in the name
Message-ID: <1229634730.68.0.79458077235.issue3330@intevation.de>


New submission from Gunnar Wrobel <p at rdus.de>:


From wrobel at pardus.de  Thu Dec 18 23:50:01 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 18 Dec 2008 23:50:01 +0100
Subject: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1
	SSL/TLS	libraries were missing or unusable
In-Reply-To: <9268C7D7C7AB4CDCBF0DCE7A201F33F9@comcept.ch>
References: <9268C7D7C7AB4CDCBF0DCE7A201F33F9@comcept.ch>
Message-ID: <20081218235001.69731dnw12732e9w@webmail.pardus.de>

Quoting ComCept Soliva <soliva at comcept.ch>:

> Hi all
>
> your modifications within the install-kolab.sh script regarding PLATTAG
> seems to work fine.
>
> All positions regarding mindepth/maxdepth I had to remove because Solaris
> does not support mindepth/maxdepth within find ([Kolab-devel] [issue2924]).
>
> Before I started I verified that there is nothing at all within tmp and
> following env variable are in use:
>
> SunOS dev 5.10 Generic_137111-08 sun4u sparc SUNW,Ultra-4
>
> # env
>
> _=/usr/bin/env
> LANG=C
> HZ=
> PATH=/usr/sbin:/usr/bin:/usr/dt/bin:/usr/openwin/bin:/bin:/usr/ucb:/opt/sfw/
> bin:/usr/local/bin:/usr/ccs/bin
> HISTFILE=/root/.sh_history
> LOGNAME=root
> MAIL=/var/mail/root
> PS1=[root at dev $PWD]#
> SHELL=/sbin/sh
> HISTSIZE=200
> HOME=/root
> TERM=vt100
> PWD=/kolabtmp
> TZ=MET
> ENV=/root/.kshrc
>
> # crle
>
> Configuration file [version 4]: /var/ld/ld.config
>   Default Library Path (ELF):   /lib:/usr/lib:/usr/local/lib
>   Trusted Directories (ELF):    /lib/secure:/usr/lib/secure  (system
> default)
>
>
> The compilation stopps within apache regarding SSL/TLS:
>
> checking whether to enable mod_ssl... checking dependencies
> checking for SSL/TLS toolkit base... /kolab
>   adding "-R/kolab/lib" to LDFLAGS
> checking for OpenSSL version... checking openssl/opensslv.h usability... yes
> checking openssl/opensslv.h presence... yes
> checking for openssl/opensslv.h... yes
> checking openssl/ssl.h usability... yes
> checking openssl/ssl.h presence... yes
> checking for openssl/ssl.h... yes
> OK
>   forcing SSL_LIBS to "-lssl -lcrypto"
> checking openssl/engine.h usability... yes
> checking openssl/engine.h presence... yes
> checking for openssl/engine.h... yes
> checking for SSLeay_version... yes
> checking for SSL_CTX_new... no
> checking for ENGINE_init... no
> checking for ENGINE_load_builtin_engines... no
> checking for SSL_set_cert_store... no
> configure: error: ... Error, SSL/TLS libraries were missing or unusable
> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)

Is there still a configure.log file available from this step? It  
should be the unpacked apache source directory.

Cheers,

Gunnar

>
>
> RPM build errors:
>     Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
> + exit 1
>
>
>
> Full Log File can be downloaeded from following link:
>
> http://www.comcept.ch/kolab2/2.2.1-beta1/kolab-install-Dec-14-08_44_54.zip
>
> More information about install can be found at:
>
> http://www.comcept.ch/kolab2/2.2.1-beta1/solaris_10_kolab2_install.txt
>
>
>
> OpenSSL was compiled and installed successful:
>
>
> Processing files: openssl-0.9.8g-20080101
> Wrote: /kolab/RPM/PKG/openssl-0.9.8g-20080101.sparc64-solaris10-kolab.rpm
> Executing(%clean): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix
> -e /kolab/RPM/TMP/rpm-tmp.699
> + cd /kolab/RPM/TMP
> + cd openssl-0.9.8g
> + rm -rf /kolab/RPM/TMP/openssl-0.9.8g-root
> + exit 0
> Executing(--clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
> --posix -e /kolab/RPM/TMP/rpm-tmp.17537
> + cd /kolab/RPM/TMP
> + rm -rf openssl-0.9.8g
> + exit 0
> Preparing...
> ##################################################
> openssl
> ##################################################
> :::: /tmp/install-kolab....27392/openssl-0.9.8g-20080101.src.rpm = 0 ::::
>
> The library is also there:
>
> # ls -la /kolab/lib/libssl*
> -rw-r--r--   1 kolab    kolab     403268 Dec 14 18:00 /kolab/lib/libssl.a
>
>
>
> Within the include dir openssl dir exists:
>
> # ls -la /kolab/include/openssl
> total 1264
> drwxr-xr-x   2 kolab    kolab         70 Dec 14 18:02 .
> drwxr-xr-x  14 kolab    kolab         41 Dec 14 21:39 ..
> -rw-r--r--   1 kolab    kolab       5372 Dec 14 17:59 aes.h
> -rw-r--r--   1 kolab    kolab      46728 Dec 14 17:59 asn1.h
> -rw-r--r--   1 kolab    kolab      18956 Dec 14 17:59 asn1_mac.h
> -rw-r--r--   1 kolab    kolab      27838 Dec 14 17:59 asn1t.h
> -rw-r--r--   1 kolab    kolab      30772 Dec 14 17:59 bio.h
> -rw-r--r--   1 kolab    kolab       5073 Dec 14 17:59 blowfish.h
> -rw-r--r--   1 kolab    kolab      33035 Dec 14 17:59 bn.h
> -rw-r--r--   1 kolab    kolab       4565 Dec 14 17:59 buffer.h
> -rw-r--r--   1 kolab    kolab       4349 Dec 14 17:59 cast.h
> -rw-r--r--   1 kolab    kolab       1601 Dec 14 17:59 comp.h
> -rw-r--r--   1 kolab    kolab       9484 Dec 14 17:59 conf.h
> -rw-r--r--   1 kolab    kolab       4080 Dec 14 17:59 conf_api.h
> -rw-r--r--   1 kolab    kolab      22121 Dec 14 17:59 crypto.h
> -rw-r--r--   1 kolab    kolab      10724 Dec 14 17:59 des.h
> -rw-r--r--   1 kolab    kolab      18226 Dec 14 17:59 des_old.h
> -rw-r--r--   1 kolab    kolab       8372 Dec 14 17:59 dh.h
> -rw-r--r--   1 kolab    kolab      10474 Dec 14 17:59 dsa.h
> -rw-r--r--   1 kolab    kolab      16252 Dec 14 17:59 dso.h
> -rw-r--r--   1 kolab    kolab       6146 Dec 14 17:59 dtls1.h
> -rw-r--r--   1 kolab    kolab       9632 Dec 14 17:59 e_os2.h
> -rw-r--r--   1 kolab    kolab        540 Dec 14 17:59 ebcdic.h
> -rw-r--r--   1 kolab    kolab      21389 Dec 14 17:59 ec.h
> -rw-r--r--   1 kolab    kolab       4609 Dec 14 17:59 ecdh.h
> -rw-r--r--   1 kolab    kolab      10578 Dec 14 17:59 ecdsa.h
> -rw-r--r--   1 kolab    kolab      37839 Dec 14 17:59 engine.h
> -rw-r--r--   1 kolab    kolab      12493 Dec 14 17:59 err.h
> -rw-r--r--   1 kolab    kolab      35620 Dec 14 17:59 evp.h
> -rw-r--r--   1 kolab    kolab       4368 Dec 14 17:59 hmac.h
> -rw-r--r--   1 kolab    kolab       7642 Dec 14 17:59 krb5_asn.h
> -rw-r--r--   1 kolab    kolab       5927 Dec 14 17:59 kssl.h
> -rw-r--r--   1 kolab    kolab       7429 Dec 14 17:59 lhash.h
> -rw-r--r--   1 kolab    kolab       3897 Dec 14 17:59 md2.h
> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md4.h
> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md5.h
> -rw-r--r--   1 kolab    kolab     113729 Dec 14 17:59 obj_mac.h
> -rw-r--r--   1 kolab    kolab      33396 Dec 14 17:59 objects.h
> -rw-r--r--   1 kolab    kolab      23795 Dec 14 17:59 ocsp.h
> -rw-r--r--   1 kolab    kolab       6533 Dec 14 17:59 opensslconf.h
> -rw-r--r--   1 kolab    kolab       3751 Dec 14 17:59 opensslv.h
> -rw-r--r--   1 kolab    kolab       6446 Dec 14 17:59 ossl_typ.h
> -rw-r--r--   1 kolab    kolab      27927 Dec 14 17:59 pem.h
> -rw-r--r--   1 kolab    kolab       2863 Dec 14 17:59 pem2.h
> -rw-r--r--   1 kolab    kolab      12677 Dec 14 17:59 pkcs12.h
> -rw-r--r--   1 kolab    kolab      16333 Dec 14 17:59 pkcs7.h
> -rw-r--r--   1 kolab    kolab       6150 Dec 14 17:59 pq_compat.h
> -rw-r--r--   1 kolab    kolab       3519 Dec 14 17:59 pqueue.h
> -rw-r--r--   1 kolab    kolab       5251 Dec 14 17:59 rand.h
> -rw-r--r--   1 kolab    kolab       4294 Dec 14 17:59 rc2.h
> -rw-r--r--   1 kolab    kolab       3707 Dec 14 17:59 rc4.h
> -rw-r--r--   1 kolab    kolab       4284 Dec 14 17:59 ripemd.h
> -rw-r--r--   1 kolab    kolab      18202 Dec 14 17:59 rsa.h
> -rw-r--r--   1 kolab    kolab     126893 Dec 14 17:59 safestack.h
> -rw-r--r--   1 kolab    kolab       7329 Dec 14 17:59 sha.h
> -rw-r--r--   1 kolab    kolab      82501 Dec 14 17:59 ssl.h
> -rw-r--r--   1 kolab    kolab      10716 Dec 14 17:59 ssl2.h
> -rw-r--r--   1 kolab    kolab       3744 Dec 14 17:59 ssl23.h
> -rw-r--r--   1 kolab    kolab      22283 Dec 14 17:59 ssl3.h
> -rw-r--r--   1 kolab    kolab       4418 Dec 14 17:59 stack.h
> -rw-r--r--   1 kolab    kolab      26481 Dec 14 17:59 store.h
> -rw-r--r--   1 kolab    kolab      19456 Dec 14 17:59 symhacks.h
> -rw-r--r--   1 kolab    kolab      18121 Dec 14 17:59 tls1.h
> -rw-r--r--   1 kolab    kolab       4117 Dec 14 17:59 tmdiff.h
> -rw-r--r--   1 kolab    kolab       4300 Dec 14 17:59 txt_db.h
> -rw-r--r--   1 kolab    kolab      16418 Dec 14 17:59 ui.h
> -rw-r--r--   1 kolab    kolab       3439 Dec 14 17:59 ui_compat.h
> -rw-r--r--   1 kolab    kolab      47946 Dec 14 17:59 x509.h
> -rw-r--r--   1 kolab    kolab      20782 Dec 14 17:59 x509_vfy.h
> -rw-r--r--   1 kolab    kolab      29980 Dec 14 17:59 x509v3.h
>
>
> What is going wrong here....? How to proceed.....? If you need more
> information please tell me.
>
> kinde regards
>
> Andrea Soliva
>
> Mail: soliva at comcept.ch
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



-- 
______ 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-devel/attachments/20081218/d00b7a0c/attachment.bin

From wrobel at pardus.de  Thu Dec 18 23:51:43 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 18 Dec 2008 23:51:43 +0100
Subject: [Kolab-devel] KDE Kolab Clients betas
In-Reply-To: <960738410812160222s6dd07008t1283a184c76b9f9e@mail.gmail.com>
References: <960738410812160222s6dd07008t1283a184c76b9f9e@mail.gmail.com>
Message-ID: <20081218235143.35303sgtlgnc4t2c@webmail.pardus.de>

Quoting Mathieu Parent <math.parent at gmail.com>:

> Hi,
>
> What is the status of enterprise4, on linux and on windows ? I'm
> interested to test but can't find windows builds, or build procedure.
>
> Roadmap says beta end of 2008 (http://kolab.org/roadmap.html).

As far as I know (I'm server not client ;) but you know that...) it is  
currently in preparation. Shouldn't take too long anymore.

Cheers,

Gunnar

>
> Regards
>
> Mathieu Parent
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



-- 
____ 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 soliva at comcept.ch  Fri Dec 19 02:35:50 2008
From: soliva at comcept.ch (ComCept Soliva)
Date: Fri, 19 Dec 2008 02:35:50 +0100
Subject: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1 SSL/TLS
	libraries were missing or unusable
In-Reply-To: <20081218235001.69731dnw12732e9w@webmail.pardus.de>
References: <9268C7D7C7AB4CDCBF0DCE7A201F33F9@comcept.ch>
	<20081218235001.69731dnw12732e9w@webmail.pardus.de>
Message-ID: <E96DBF20E3D046079698C8804C040486@comcept.ch>

Hi 

in RPM/TMP/httpd-2.2.10 there is the config.log.

Please find it attached 

Andrea

Mail: soliva at comcept.ch 
-----Urspr?ngliche Nachricht-----
Von: Gunnar Wrobel [mailto:wrobel at pardus.de] Im Auftrag von
kolab-devel-bounces at kolab.org
Gesendet: Donnerstag, 18. Dezember 2008 23:50
An: kolab-devel at kolab.org
Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS libraries
were missing or unusable

Quoting ComCept Soliva <soliva at comcept.ch>:

> Hi all
>
> your modifications within the install-kolab.sh script regarding PLATTAG
> seems to work fine.
>
> All positions regarding mindepth/maxdepth I had to remove because Solaris
> does not support mindepth/maxdepth within find ([Kolab-devel]
[issue2924]).
>
> Before I started I verified that there is nothing at all within tmp and
> following env variable are in use:
>
> SunOS dev 5.10 Generic_137111-08 sun4u sparc SUNW,Ultra-4
>
> # env
>
> _=/usr/bin/env
> LANG=C
> HZ=
>
PATH=/usr/sbin:/usr/bin:/usr/dt/bin:/usr/openwin/bin:/bin:/usr/ucb:/opt/sfw/
> bin:/usr/local/bin:/usr/ccs/bin
> HISTFILE=/root/.sh_history
> LOGNAME=root
> MAIL=/var/mail/root
> PS1=[root at dev $PWD]#
> SHELL=/sbin/sh
> HISTSIZE=200
> HOME=/root
> TERM=vt100
> PWD=/kolabtmp
> TZ=MET
> ENV=/root/.kshrc
>
> # crle
>
> Configuration file [version 4]: /var/ld/ld.config
>   Default Library Path (ELF):   /lib:/usr/lib:/usr/local/lib
>   Trusted Directories (ELF):    /lib/secure:/usr/lib/secure  (system
> default)
>
>
> The compilation stopps within apache regarding SSL/TLS:
>
> checking whether to enable mod_ssl... checking dependencies
> checking for SSL/TLS toolkit base... /kolab
>   adding "-R/kolab/lib" to LDFLAGS
> checking for OpenSSL version... checking openssl/opensslv.h usability...
yes
> checking openssl/opensslv.h presence... yes
> checking for openssl/opensslv.h... yes
> checking openssl/ssl.h usability... yes
> checking openssl/ssl.h presence... yes
> checking for openssl/ssl.h... yes
> OK
>   forcing SSL_LIBS to "-lssl -lcrypto"
> checking openssl/engine.h usability... yes
> checking openssl/engine.h presence... yes
> checking for openssl/engine.h... yes
> checking for SSLeay_version... yes
> checking for SSL_CTX_new... no
> checking for ENGINE_init... no
> checking for ENGINE_load_builtin_engines... no
> checking for SSL_set_cert_store... no
> configure: error: ... Error, SSL/TLS libraries were missing or unusable
> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)

Is there still a configure.log file available from this step? It  
should be the unpacked apache source directory.

Cheers,

Gunnar

>
>
> RPM build errors:
>     Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
> + exit 1
>
>
>
> Full Log File can be downloaeded from following link:
>
> http://www.comcept.ch/kolab2/2.2.1-beta1/kolab-install-Dec-14-08_44_54.zip
>
> More information about install can be found at:
>
> http://www.comcept.ch/kolab2/2.2.1-beta1/solaris_10_kolab2_install.txt
>
>
>
> OpenSSL was compiled and installed successful:
>
>
> Processing files: openssl-0.9.8g-20080101
> Wrote: /kolab/RPM/PKG/openssl-0.9.8g-20080101.sparc64-solaris10-kolab.rpm
> Executing(%clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
--posix
> -e /kolab/RPM/TMP/rpm-tmp.699
> + cd /kolab/RPM/TMP
> + cd openssl-0.9.8g
> + rm -rf /kolab/RPM/TMP/openssl-0.9.8g-root
> + exit 0
> Executing(--clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
> --posix -e /kolab/RPM/TMP/rpm-tmp.17537
> + cd /kolab/RPM/TMP
> + rm -rf openssl-0.9.8g
> + exit 0
> Preparing...
> ##################################################
> openssl
> ##################################################
> :::: /tmp/install-kolab....27392/openssl-0.9.8g-20080101.src.rpm = 0 ::::
>
> The library is also there:
>
> # ls -la /kolab/lib/libssl*
> -rw-r--r--   1 kolab    kolab     403268 Dec 14 18:00 /kolab/lib/libssl.a
>
>
>
> Within the include dir openssl dir exists:
>
> # ls -la /kolab/include/openssl
> total 1264
> drwxr-xr-x   2 kolab    kolab         70 Dec 14 18:02 .
> drwxr-xr-x  14 kolab    kolab         41 Dec 14 21:39 ..
> -rw-r--r--   1 kolab    kolab       5372 Dec 14 17:59 aes.h
> -rw-r--r--   1 kolab    kolab      46728 Dec 14 17:59 asn1.h
> -rw-r--r--   1 kolab    kolab      18956 Dec 14 17:59 asn1_mac.h
> -rw-r--r--   1 kolab    kolab      27838 Dec 14 17:59 asn1t.h
> -rw-r--r--   1 kolab    kolab      30772 Dec 14 17:59 bio.h
> -rw-r--r--   1 kolab    kolab       5073 Dec 14 17:59 blowfish.h
> -rw-r--r--   1 kolab    kolab      33035 Dec 14 17:59 bn.h
> -rw-r--r--   1 kolab    kolab       4565 Dec 14 17:59 buffer.h
> -rw-r--r--   1 kolab    kolab       4349 Dec 14 17:59 cast.h
> -rw-r--r--   1 kolab    kolab       1601 Dec 14 17:59 comp.h
> -rw-r--r--   1 kolab    kolab       9484 Dec 14 17:59 conf.h
> -rw-r--r--   1 kolab    kolab       4080 Dec 14 17:59 conf_api.h
> -rw-r--r--   1 kolab    kolab      22121 Dec 14 17:59 crypto.h
> -rw-r--r--   1 kolab    kolab      10724 Dec 14 17:59 des.h
> -rw-r--r--   1 kolab    kolab      18226 Dec 14 17:59 des_old.h
> -rw-r--r--   1 kolab    kolab       8372 Dec 14 17:59 dh.h
> -rw-r--r--   1 kolab    kolab      10474 Dec 14 17:59 dsa.h
> -rw-r--r--   1 kolab    kolab      16252 Dec 14 17:59 dso.h
> -rw-r--r--   1 kolab    kolab       6146 Dec 14 17:59 dtls1.h
> -rw-r--r--   1 kolab    kolab       9632 Dec 14 17:59 e_os2.h
> -rw-r--r--   1 kolab    kolab        540 Dec 14 17:59 ebcdic.h
> -rw-r--r--   1 kolab    kolab      21389 Dec 14 17:59 ec.h
> -rw-r--r--   1 kolab    kolab       4609 Dec 14 17:59 ecdh.h
> -rw-r--r--   1 kolab    kolab      10578 Dec 14 17:59 ecdsa.h
> -rw-r--r--   1 kolab    kolab      37839 Dec 14 17:59 engine.h
> -rw-r--r--   1 kolab    kolab      12493 Dec 14 17:59 err.h
> -rw-r--r--   1 kolab    kolab      35620 Dec 14 17:59 evp.h
> -rw-r--r--   1 kolab    kolab       4368 Dec 14 17:59 hmac.h
> -rw-r--r--   1 kolab    kolab       7642 Dec 14 17:59 krb5_asn.h
> -rw-r--r--   1 kolab    kolab       5927 Dec 14 17:59 kssl.h
> -rw-r--r--   1 kolab    kolab       7429 Dec 14 17:59 lhash.h
> -rw-r--r--   1 kolab    kolab       3897 Dec 14 17:59 md2.h
> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md4.h
> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md5.h
> -rw-r--r--   1 kolab    kolab     113729 Dec 14 17:59 obj_mac.h
> -rw-r--r--   1 kolab    kolab      33396 Dec 14 17:59 objects.h
> -rw-r--r--   1 kolab    kolab      23795 Dec 14 17:59 ocsp.h
> -rw-r--r--   1 kolab    kolab       6533 Dec 14 17:59 opensslconf.h
> -rw-r--r--   1 kolab    kolab       3751 Dec 14 17:59 opensslv.h
> -rw-r--r--   1 kolab    kolab       6446 Dec 14 17:59 ossl_typ.h
> -rw-r--r--   1 kolab    kolab      27927 Dec 14 17:59 pem.h
> -rw-r--r--   1 kolab    kolab       2863 Dec 14 17:59 pem2.h
> -rw-r--r--   1 kolab    kolab      12677 Dec 14 17:59 pkcs12.h
> -rw-r--r--   1 kolab    kolab      16333 Dec 14 17:59 pkcs7.h
> -rw-r--r--   1 kolab    kolab       6150 Dec 14 17:59 pq_compat.h
> -rw-r--r--   1 kolab    kolab       3519 Dec 14 17:59 pqueue.h
> -rw-r--r--   1 kolab    kolab       5251 Dec 14 17:59 rand.h
> -rw-r--r--   1 kolab    kolab       4294 Dec 14 17:59 rc2.h
> -rw-r--r--   1 kolab    kolab       3707 Dec 14 17:59 rc4.h
> -rw-r--r--   1 kolab    kolab       4284 Dec 14 17:59 ripemd.h
> -rw-r--r--   1 kolab    kolab      18202 Dec 14 17:59 rsa.h
> -rw-r--r--   1 kolab    kolab     126893 Dec 14 17:59 safestack.h
> -rw-r--r--   1 kolab    kolab       7329 Dec 14 17:59 sha.h
> -rw-r--r--   1 kolab    kolab      82501 Dec 14 17:59 ssl.h
> -rw-r--r--   1 kolab    kolab      10716 Dec 14 17:59 ssl2.h
> -rw-r--r--   1 kolab    kolab       3744 Dec 14 17:59 ssl23.h
> -rw-r--r--   1 kolab    kolab      22283 Dec 14 17:59 ssl3.h
> -rw-r--r--   1 kolab    kolab       4418 Dec 14 17:59 stack.h
> -rw-r--r--   1 kolab    kolab      26481 Dec 14 17:59 store.h
> -rw-r--r--   1 kolab    kolab      19456 Dec 14 17:59 symhacks.h
> -rw-r--r--   1 kolab    kolab      18121 Dec 14 17:59 tls1.h
> -rw-r--r--   1 kolab    kolab       4117 Dec 14 17:59 tmdiff.h
> -rw-r--r--   1 kolab    kolab       4300 Dec 14 17:59 txt_db.h
> -rw-r--r--   1 kolab    kolab      16418 Dec 14 17:59 ui.h
> -rw-r--r--   1 kolab    kolab       3439 Dec 14 17:59 ui_compat.h
> -rw-r--r--   1 kolab    kolab      47946 Dec 14 17:59 x509.h
> -rw-r--r--   1 kolab    kolab      20782 Dec 14 17:59 x509_vfy.h
> -rw-r--r--   1 kolab    kolab      29980 Dec 14 17:59 x509v3.h
>
>
> What is going wrong here....? How to proceed.....? If you need more
> information please tell me.
>
> kinde regards
>
> Andrea Soliva
>
> Mail: soliva at comcept.ch
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



-- 
______ 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: config.zip
Type: application/octet-stream
Size: 9161 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20081219/cd6a8b3b/config-0001.exe

From math.parent at gmail.com  Fri Dec 19 08:39:58 2008
From: math.parent at gmail.com (Mathieu Parent)
Date: Fri, 19 Dec 2008 08:39:58 +0100
Subject: [Kolab-devel] KDE Kolab Clients betas
In-Reply-To: <20081218235143.35303sgtlgnc4t2c@webmail.pardus.de>
References: <960738410812160222s6dd07008t1283a184c76b9f9e@mail.gmail.com>
	<20081218235143.35303sgtlgnc4t2c@webmail.pardus.de>
Message-ID: <960738410812182339x4e139ffax26131941577b5b99@mail.gmail.com>

Hi,


2008/12/18 Gunnar Wrobel <wrobel at pardus.de>:
> Quoting Mathieu Parent <math.parent at gmail.com>:
>
>> Hi,
>>
>> What is the status of enterprise4, on linux and on windows ? I'm
>> interested to test but can't find windows builds, or build procedure.
>>
>> Roadmap says beta end of 2008 (http://kolab.org/roadmap.html).
>
> As far as I know (I'm server not client ;) but you know that...) it is
> currently in preparation. Shouldn't take too long anymore.
((Hm, isn't horde a client? (joking)))

Thanks.
I'm ready to help, even with a NO-WARRANTY-THIS-MAY-CRASH-YOUR-SYSTEM
win32 version.


> Cheers,
>
> Gunnar
>
>>
>> Regards
>>
>> Mathieu Parent

Reagrds

Mathieu Parent


From bernhard at intevation.de  Fri Dec 19 09:42:47 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 19 Dec 2008 09:42:47 +0100
Subject: [Kolab-devel] Policy wrt "unstable" Debian Kontact packages?
In-Reply-To: <200812150924.31009.itsef-admin@brightsight.com>
References: <200812021814.31429.itsef-admin@brightsight.com>
	<200812150924.31009.itsef-admin@brightsight.com>
Message-ID: <200812190942.50479.bernhard@intevation.de>

Am Montag, 15. Dezember 2008 09:24:30 schrieb ITSEF Admin:
> On Tuesday 2 December 2008 18:14:31 ITSEF Admin wrote:
> > Over the past months, I'm tracking the unstable Debian packages for the
> > Kontact enterprise35 client
> > (http://apt.intevation.de/dists/etch/unstable/source/) as I use them as
> > base for our custom Kubuntu Hardy packages.
>
> [...]
>
> > Today *both* versions were removed from "unstable" and the latest version
> > is now 862683.
>
> As it just happened again (891698 got pulled - 862683 is yet again the
> latest version in "unstable"), I'd like to repeat my question: How is the
> decision made to have a version in "unstable" and is there a place where I
> can find the reasoning behind that decision?

This email list is the right place to discuss and make the policy.
Currently we just move over stuff as it comes out from experimental
when we believe it is ready. 

Versions from experimental can just vanish after a while
and we need also a process to delete old versions from unstable as well.
Our idea is to move stuff from unstable to testing and then to stable or 
delete.

(I was not aware we've removed stuff from unstable, I will inquire, thanks for 
the hint.)

Best,
Bernhard

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- 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-devel/attachments/20081219/0d42e70a/attachment.bin

From bernhard at intevation.de  Fri Dec 19 09:48:44 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 19 Dec 2008 09:48:44 +0100
Subject: [Kolab-devel]
	=?utf-8?q?=5Bissue3283=5D_web_client=3A_Document_re?=
	=?utf-8?q?asons_for=09switching_to_LDAP_auth_instead_of_IMAP_auth?=
In-Reply-To: <20081202232918.1064119t3nwwuxus@webmail.pardus.de>
References: <1228233807.73.0.232923837395.issue3283@intevation.de>
	<20081202232918.1064119t3nwwuxus@webmail.pardus.de>
Message-ID: <200812190948.44874.bernhard@intevation.de>

Am Dienstag, 2. Dezember 2008 23:29:18 schrieb Gunnar Wrobel:
> Enough documentation?

Yep.

> I don't think this should go into the wiki but ? 
> correct me if I'm wrong.

I should be put in a place where it can be found.
The mailinglist archive is _not_ the best place for it.
Actually there should be a web client implementation documentation
or a php module implementation documentation where the consequences of such 
decisions are put down.

-- 
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-devel/attachments/20081219/5c053a2f/attachment.bin

From bernhard at intevation.de  Fri Dec 19 10:01:39 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 19 Dec 2008 10:01:39 +0100
Subject: [Kolab-devel] KDE Kolab Clients betas
In-Reply-To: <20081218235143.35303sgtlgnc4t2c@webmail.pardus.de>
References: <960738410812160222s6dd07008t1283a184c76b9f9e@mail.gmail.com>
	<20081218235143.35303sgtlgnc4t2c@webmail.pardus.de>
Message-ID: <200812191001.40153.bernhard@intevation.de>

Am Donnerstag, 18. Dezember 2008 23:51:43 schrieb Gunnar Wrobel:
> > What is the status of enterprise4, on linux and on windows ? I'm
> > interested to test but can't find windows builds, or build procedure.
> >
> > Roadmap says beta end of 2008 (http://kolab.org/roadmap.html).
>
> As far as I know (I'm server not client ;) but you know that...) it is ?
> currently in preparation. Shouldn't take too long anymore.

I can confirm this,
we are preparing to publish a beta-huge-debug build 
within the next working days. The server is in place, we have the builds alpha 
tested from early november, but it is all huge. If all runs well, maybe 
today - watch this space. ;)

Bernhard


-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-devel/attachments/20081219/9a1e967e/attachment.bin

From bernhard at intevation.de  Fri Dec 19 10:27:39 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 19 Dec 2008 10:27:39 +0100
Subject: [Kolab-devel] SyncML
In-Reply-To: <20081219000316.11584o9f0cf76c8w@webmail.pardus.de>
References: <494A7BE5.7050100@servinfo.ca>
	<20081219000316.11584o9f0cf76c8w@webmail.pardus.de>
Message-ID: <200812191027.39829.bernhard@intevation.de>

Gunnar,

Am Freitag, 19. Dezember 2008 00:03:16 schrieb Gunnar Wrobel:
> 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

I think we should have a short page which is specific from the Kolab Webclient 
perspective of 2.2.1-beta and listing the url Kolab Server/OpenPKG users 
would need to enter in their device.
(Of course linking to the page above as well.)


-- 
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-devel/attachments/20081219/d390765a/attachment.bin

From wrobel at pardus.de  Fri Dec 19 10:56:17 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Fri, 19 Dec 2008 10:56:17 +0100
Subject: [Kolab-devel] SyncML
In-Reply-To: <200812191027.39829.bernhard@intevation.de>
References: <494A7BE5.7050100@servinfo.ca>
	<20081219000316.11584o9f0cf76c8w@webmail.pardus.de>
	<200812191027.39829.bernhard@intevation.de>
Message-ID: <20081219105617.937336civ4qlbikg@webmail.pardus.de>

Quoting Bernhard Reiter <bernhard at intevation.de>:

> Gunnar,
>
> Am Freitag, 19. Dezember 2008 00:03:16 schrieb Gunnar Wrobel:
>> 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
>
> I think we should have a short page which is specific from the Kolab  
> Webclient
> perspective of 2.2.1-beta and listing the url Kolab Server/OpenPKG users
> would need to enter in their device.
> (Of course linking to the page above as well.)

I agree and I hope I find the time to write it soon :) It will exist  
before we get the 2.2.1 release, promised.

Cheers,
Gunnar

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



-- 
____ 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 kolab-issues at intevation.de  Fri Dec 19 17:34:32 2008
From: kolab-issues at intevation.de (Gunnar Wrobel)
Date: Fri, 19 Dec 2008 16:34:32 +0000
Subject: [Kolab-devel] [issue3331] kolabfilter uses incorrect delivery
	backend
Message-ID: <1229704472.77.0.378990462761.issue3331@intevation.de>


New submission from Gunnar Wrobel <p at rdus.de>:

http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/templates/resmgr.conf.template.in

uses an incorrect default backend:

/* Local delivery backend (default LMTP) */
$conf['kolab']['filter']['delivery_backend'] = 'LMTP';


It must be set to "lmtp". This completely breaks LMTP delivery in the kolab-filter.

This has been missed in testing before the beta release as the setting had been
added to allow for dovecot delivery. The merge to Horde disabled the setting and
it got reenabled shortly before the beta.

----------
assignedto: wrobel
messages: 18141
nosy: bernhard, thomas, wilde, wrobel
priority: critical
status: unread
title: kolabfilter uses incorrect delivery backend
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3331>
___________________________________________________


From bernhard at intevation.de  Fri Dec 19 17:35:37 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 19 Dec 2008 17:35:37 +0100
Subject: [Kolab-devel] KDE Kolab Clients betas
In-Reply-To: <200812191001.40153.bernhard@intevation.de>
References: <960738410812160222s6dd07008t1283a184c76b9f9e@mail.gmail.com>
	<20081218235143.35303sgtlgnc4t2c@webmail.pardus.de>
	<200812191001.40153.bernhard@intevation.de>
Message-ID: <200812191735.41885.bernhard@intevation.de>

Am Freitag, 19. Dezember 2008 10:01:39 schrieb Bernhard Reiter:
> we are preparing to publish a beta-huge-debug build
> within the next working days. The server is in place, we have the builds
> alpha tested from early november, but it is all huge. If all runs well,
> maybe today - watch this space. ;)

For the early birds, Kontact for windows, big clunky beta-testing is uploaded:
http://files.kolab.org/clients/kontact-enterprise4/windows/beta-huge-debug/20081113/

Announcement texts will come when stuff is fully uploaded.
(Macosx is currently uploading.)

Bernhard

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-devel/attachments/20081219/d3802c56/attachment.bin

From bernhard at intevation.de  Fri Dec 19 22:14:59 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 19 Dec 2008 22:14:59 +0100
Subject: [Kolab-devel] KDE Kolab Clients betas
In-Reply-To: <200812191735.41885.bernhard@intevation.de>
References: <960738410812160222s6dd07008t1283a184c76b9f9e@mail.gmail.com>
	<200812191001.40153.bernhard@intevation.de>
	<200812191735.41885.bernhard@intevation.de>
Message-ID: <200812192215.06411.bernhard@intevation.de>

On Freitag, 19. Dezember 2008, Bernhard Reiter wrote:
> For the early birds, Kontact for windows, big clunky beta-testing is
> uploaded:
> 
http://files.kolab.org/clients/kontact-enterprise4/windows/beta-huge-debug/20081113/
(Hint: Do not download everything, decide for one installer, nsis (aka exe) or 
msi. They have the same contents.)

Macosx (10.5) will be there (but we still upload a few more files.)
http://files.kolab.org/clients/kontact-enterprise4/macos/beta-huge-debug/20081119/

> Announcement texts will come when stuff is fully uploaded.




-- 
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-devel/attachments/20081219/9dc523a2/attachment.bin

From math.parent at gmail.com  Sat Dec 20 21:17:40 2008
From: math.parent at gmail.com (Mathieu Parent)
Date: Sat, 20 Dec 2008 21:17:40 +0100
Subject: [Kolab-devel] Kolab Server 2.2.1 Beta 1
In-Reply-To: <20081212191815.GA21528.thomas@intevation.de>
References: <20081212191815.GA21528.thomas@intevation.de>
Message-ID: <960738410812201217i713fe045mf61bb35ce0297a4e@mail.gmail.com>

Hi,


2008/12/12 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!
>
> Again many thanks to all the people who helped with this!
>

The Debian native packages for 2.2.1beta1 are available in the snapshot
area (experimental). Stable 2.2.0 version is also available in current
Debian sid. Installation instructions are in the Kolab wiki [1].

Keep in mind that Debian native packages are not the reference
implementation of Kolab (which is OpenPKG). The main goal is
to integrate better with with debian (following FHS, using APT,
OpenLDAP 2.4, ...).

Feedback is welcome (to pkg-kolab-devel AT lists.alioth.debian.org).

Regards

Mathieu Parent

[1]: http://wiki.kolab.org/index.php/Debian_-_Administrators_-_Kolab_Installation


From lists at infosecurity.ch  Sun Dec 21 10:24:04 2008
From: lists at infosecurity.ch (Fabio Pietrosanti (naif))
Date: Sun, 21 Dec 2008 10:24:04 +0100
Subject: [Kolab-devel] [pkg-kolab]  Kolab Server 2.2.1 Beta 1
In-Reply-To: <960738410812201217i713fe045mf61bb35ce0297a4e@mail.gmail.com>
References: <20081212191815.GA21528.thomas@intevation.de>
	<960738410812201217i713fe045mf61bb35ce0297a4e@mail.gmail.com>
Message-ID: <494E0B34.4090301@infosecurity.ch>

Mathieu Parent wrote:
> The Debian native packages for 2.2.1beta1 are available in the snapshot
> area (experimental). Stable 2.2.0 version is also available in current
> Debian sid. Installation instructions are in the Kolab wiki [1].
>
> Keep in mind that Debian native packages are not the reference
> implementation of Kolab (which is OpenPKG). The main goal is
> to integrate better with with debian (following FHS, using APT,
> OpenLDAP 2.4, ...).
>
> Feedback is welcome (to pkg-kolab-devel AT lists.alioth.debian.org).
>   

Would be really interesting to find out a OpenPKG to Debian packages 
migration guide, that would help to migrate (and upgrade) a Kolab 
OpenPKG based installation to a Debian based one.

I think that the management of packages trough debian apt respect to 
OpenPKG (i mean simplicity of installation and maintenance for upgrades) 
is 1 order of magnitude simpler (ie: cost less money).

I would be very happy to migrate from OpenPKG to Debian packages!

Fabio


From bernhard at intevation.de  Sun Dec 21 15:04:57 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Sun, 21 Dec 2008 15:04:57 +0100
Subject: [Kolab-devel] [pkg-kolab]  Kolab Server 2.2.1 Beta 1
In-Reply-To: <494E0B34.4090301@infosecurity.ch>
References: <20081212191815.GA21528.thomas@intevation.de>
	<960738410812201217i713fe045mf61bb35ce0297a4e@mail.gmail.com>
	<494E0B34.4090301@infosecurity.ch>
Message-ID: <200812211505.01807.bernhard@intevation.de>

On Sonntag, 21. Dezember 2008, Fabio Pietrosanti (naif) wrote:
> I think that the management of packages trough debian apt respect to
> OpenPKG (i mean simplicity of installation and maintenance for upgrades)
> is 1 order of magnitude simpler (ie: cost less money).

Our experience is the other way around using Kolab Server/OpenPKG
is one order of magnitude simple (and thus costs less money).

-- 
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-devel/attachments/20081221/81fc1ef4/attachment.bin

From math.parent at gmail.com  Sun Dec 21 16:19:29 2008
From: math.parent at gmail.com (Mathieu Parent)
Date: Sun, 21 Dec 2008 16:19:29 +0100
Subject: [Kolab-devel] [pkg-kolab]  Kolab Server 2.2.1 Beta 1
In-Reply-To: <494E0B34.4090301@infosecurity.ch>
References: <20081212191815.GA21528.thomas@intevation.de>
	<960738410812201217i713fe045mf61bb35ce0297a4e@mail.gmail.com>
	<494E0B34.4090301@infosecurity.ch>
Message-ID: <960738410812210719m773bb1cfv4f87b357bb95621a@mail.gmail.com>

Hi,
Mathieu Parent



2008/12/21 Fabio Pietrosanti (naif) <lists at infosecurity.ch>:
> Mathieu Parent wrote:
>> The Debian native packages for 2.2.1beta1 are available in the snapshot
>> area (experimental). Stable 2.2.0 version is also available in current
>> Debian sid. Installation instructions are in the Kolab wiki [1].
>>
>> Keep in mind that Debian native packages are not the reference
>> implementation of Kolab (which is OpenPKG). The main goal is
>> to integrate better with with debian (following FHS, using APT,
>> OpenLDAP 2.4, ...).
>>
>> Feedback is welcome (to pkg-kolab-devel AT lists.alioth.debian.org).
>>
>
> Would be really interesting to find out a OpenPKG to Debian packages
> migration guide, that would help to migrate (and upgrade) a Kolab
> OpenPKG based installation to a Debian based one.
I've already suggested such a migration path (see
http://lists.alioth.debian.org/pipermail/pkg-kolab-devel/2008-November/001930.html).

Any help is appreciated to test and document.

>
> I think that the management of packages trough debian apt respect to
> OpenPKG (i mean simplicity of installation and maintenance for upgrades)
> is 1 order of magnitude simpler (ie: cost less money).

This is a matter of choice (open source is!). Both solutions have pros and cons.

> I would be very happy to migrate from OpenPKG to Debian packages!
Great!


> Fabio
>
> _______________________________________________
> pkg-kolab-devel mailing list
> pkg-kolab-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-kolab-devel
>


From wrobel at pardus.de  Sun Dec 21 22:55:48 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sun, 21 Dec 2008 22:55:48 +0100
Subject: [Kolab-devel] [issue3283] web client: Document
	reasons	for	switching to LDAP auth instead of IMAP auth
In-Reply-To: <200812190948.44874.bernhard@intevation.de>
References: <1228233807.73.0.232923837395.issue3283@intevation.de>
	<20081202232918.1064119t3nwwuxus@webmail.pardus.de>
	<200812190948.44874.bernhard@intevation.de>
Message-ID: <20081221225548.715859r0byk1bk4k@webmail.pardus.de>

Quoting Bernhard Reiter <bernhard at intevation.de>:

> Am Dienstag, 2. Dezember 2008 23:29:18 schrieb Gunnar Wrobel:
>> Enough documentation?
>
> Yep.
>
>> I don't think this should go into the wiki but  correct me if I'm wrong.
>
> I should be put in a place where it can be found.
> The mailinglist archive is _not_ the best place for it.
> Actually there should be a web client implementation documentation
> or a php module implementation documentation where the consequences of such
> decisions are put down.

True. Horde is pretty complex in its configuration possibilities and I  
should add more information about this in the wiki.

An implementation documentation might be possible but is really a lot  
of work if it spans the whole "Kolab within Horde". A lot of general  
Horde information would have to be included. I guess I could write a  
whole book about it :)

Cheers,

Gunnar

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



-- 
______ 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-devel/attachments/20081221/81517ce4/attachment.bin

From wrobel at pardus.de  Sun Dec 21 23:17:34 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sun, 21 Dec 2008 23:17:34 +0100
Subject: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1
	SSL/TLS	libraries were missing or unusable
In-Reply-To: <E96DBF20E3D046079698C8804C040486@comcept.ch>
References: <9268C7D7C7AB4CDCBF0DCE7A201F33F9@comcept.ch>
	<20081218235001.69731dnw12732e9w@webmail.pardus.de>
	<E96DBF20E3D046079698C8804C040486@comcept.ch>
Message-ID: <20081221231734.58874cp3kwclwpz4@webmail.pardus.de>

Quoting ComCept Soliva <soliva at comcept.ch>:

> Hi
>
> in RPM/TMP/httpd-2.2.10 there is the config.log.
>
> Please find it attached

Thanks, that helped to identify the following conversation:

http://www.mail-archive.com/openpkg-users at openpkg.org/msg03467.html

It might help.

Cheers,

Gunnar

>
> Andrea
>
> Mail: soliva at comcept.ch
> -----Urspr?ngliche Nachricht-----
> Von: Gunnar Wrobel [mailto:wrobel at pardus.de] Im Auftrag von
> kolab-devel-bounces at kolab.org
> Gesendet: Donnerstag, 18. Dezember 2008 23:50
> An: kolab-devel at kolab.org
> Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS libraries
> were missing or unusable
>
> Quoting ComCept Soliva <soliva at comcept.ch>:
>
>> Hi all
>>
>> your modifications within the install-kolab.sh script regarding PLATTAG
>> seems to work fine.
>>
>> All positions regarding mindepth/maxdepth I had to remove because Solaris
>> does not support mindepth/maxdepth within find ([Kolab-devel]
> [issue2924]).
>>
>> Before I started I verified that there is nothing at all within tmp and
>> following env variable are in use:
>>
>> SunOS dev 5.10 Generic_137111-08 sun4u sparc SUNW,Ultra-4
>>
>> # env
>>
>> _=/usr/bin/env
>> LANG=C
>> HZ=
>>
> PATH=/usr/sbin:/usr/bin:/usr/dt/bin:/usr/openwin/bin:/bin:/usr/ucb:/opt/sfw/
>> bin:/usr/local/bin:/usr/ccs/bin
>> HISTFILE=/root/.sh_history
>> LOGNAME=root
>> MAIL=/var/mail/root
>> PS1=[root at dev $PWD]#
>> SHELL=/sbin/sh
>> HISTSIZE=200
>> HOME=/root
>> TERM=vt100
>> PWD=/kolabtmp
>> TZ=MET
>> ENV=/root/.kshrc
>>
>> # crle
>>
>> Configuration file [version 4]: /var/ld/ld.config
>>   Default Library Path (ELF):   /lib:/usr/lib:/usr/local/lib
>>   Trusted Directories (ELF):    /lib/secure:/usr/lib/secure  (system
>> default)
>>
>>
>> The compilation stopps within apache regarding SSL/TLS:
>>
>> checking whether to enable mod_ssl... checking dependencies
>> checking for SSL/TLS toolkit base... /kolab
>>   adding "-R/kolab/lib" to LDFLAGS
>> checking for OpenSSL version... checking openssl/opensslv.h usability...
> yes
>> checking openssl/opensslv.h presence... yes
>> checking for openssl/opensslv.h... yes
>> checking openssl/ssl.h usability... yes
>> checking openssl/ssl.h presence... yes
>> checking for openssl/ssl.h... yes
>> OK
>>   forcing SSL_LIBS to "-lssl -lcrypto"
>> checking openssl/engine.h usability... yes
>> checking openssl/engine.h presence... yes
>> checking for openssl/engine.h... yes
>> checking for SSLeay_version... yes
>> checking for SSL_CTX_new... no
>> checking for ENGINE_init... no
>> checking for ENGINE_load_builtin_engines... no
>> checking for SSL_set_cert_store... no
>> configure: error: ... Error, SSL/TLS libraries were missing or unusable
>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
>
> Is there still a configure.log file available from this step? It
> should be the unpacked apache source directory.
>
> Cheers,
>
> Gunnar
>
>>
>>
>> RPM build errors:
>>     Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
>> + exit 1
>>
>>
>>
>> Full Log File can be downloaeded from following link:
>>
>> http://www.comcept.ch/kolab2/2.2.1-beta1/kolab-install-Dec-14-08_44_54.zip
>>
>> More information about install can be found at:
>>
>> http://www.comcept.ch/kolab2/2.2.1-beta1/solaris_10_kolab2_install.txt
>>
>>
>>
>> OpenSSL was compiled and installed successful:
>>
>>
>> Processing files: openssl-0.9.8g-20080101
>> Wrote: /kolab/RPM/PKG/openssl-0.9.8g-20080101.sparc64-solaris10-kolab.rpm
>> Executing(%clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
> --posix
>> -e /kolab/RPM/TMP/rpm-tmp.699
>> + cd /kolab/RPM/TMP
>> + cd openssl-0.9.8g
>> + rm -rf /kolab/RPM/TMP/openssl-0.9.8g-root
>> + exit 0
>> Executing(--clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
>> --posix -e /kolab/RPM/TMP/rpm-tmp.17537
>> + cd /kolab/RPM/TMP
>> + rm -rf openssl-0.9.8g
>> + exit 0
>> Preparing...
>> ##################################################
>> openssl
>> ##################################################
>> :::: /tmp/install-kolab....27392/openssl-0.9.8g-20080101.src.rpm = 0 ::::
>>
>> The library is also there:
>>
>> # ls -la /kolab/lib/libssl*
>> -rw-r--r--   1 kolab    kolab     403268 Dec 14 18:00 /kolab/lib/libssl.a
>>
>>
>>
>> Within the include dir openssl dir exists:
>>
>> # ls -la /kolab/include/openssl
>> total 1264
>> drwxr-xr-x   2 kolab    kolab         70 Dec 14 18:02 .
>> drwxr-xr-x  14 kolab    kolab         41 Dec 14 21:39 ..
>> -rw-r--r--   1 kolab    kolab       5372 Dec 14 17:59 aes.h
>> -rw-r--r--   1 kolab    kolab      46728 Dec 14 17:59 asn1.h
>> -rw-r--r--   1 kolab    kolab      18956 Dec 14 17:59 asn1_mac.h
>> -rw-r--r--   1 kolab    kolab      27838 Dec 14 17:59 asn1t.h
>> -rw-r--r--   1 kolab    kolab      30772 Dec 14 17:59 bio.h
>> -rw-r--r--   1 kolab    kolab       5073 Dec 14 17:59 blowfish.h
>> -rw-r--r--   1 kolab    kolab      33035 Dec 14 17:59 bn.h
>> -rw-r--r--   1 kolab    kolab       4565 Dec 14 17:59 buffer.h
>> -rw-r--r--   1 kolab    kolab       4349 Dec 14 17:59 cast.h
>> -rw-r--r--   1 kolab    kolab       1601 Dec 14 17:59 comp.h
>> -rw-r--r--   1 kolab    kolab       9484 Dec 14 17:59 conf.h
>> -rw-r--r--   1 kolab    kolab       4080 Dec 14 17:59 conf_api.h
>> -rw-r--r--   1 kolab    kolab      22121 Dec 14 17:59 crypto.h
>> -rw-r--r--   1 kolab    kolab      10724 Dec 14 17:59 des.h
>> -rw-r--r--   1 kolab    kolab      18226 Dec 14 17:59 des_old.h
>> -rw-r--r--   1 kolab    kolab       8372 Dec 14 17:59 dh.h
>> -rw-r--r--   1 kolab    kolab      10474 Dec 14 17:59 dsa.h
>> -rw-r--r--   1 kolab    kolab      16252 Dec 14 17:59 dso.h
>> -rw-r--r--   1 kolab    kolab       6146 Dec 14 17:59 dtls1.h
>> -rw-r--r--   1 kolab    kolab       9632 Dec 14 17:59 e_os2.h
>> -rw-r--r--   1 kolab    kolab        540 Dec 14 17:59 ebcdic.h
>> -rw-r--r--   1 kolab    kolab      21389 Dec 14 17:59 ec.h
>> -rw-r--r--   1 kolab    kolab       4609 Dec 14 17:59 ecdh.h
>> -rw-r--r--   1 kolab    kolab      10578 Dec 14 17:59 ecdsa.h
>> -rw-r--r--   1 kolab    kolab      37839 Dec 14 17:59 engine.h
>> -rw-r--r--   1 kolab    kolab      12493 Dec 14 17:59 err.h
>> -rw-r--r--   1 kolab    kolab      35620 Dec 14 17:59 evp.h
>> -rw-r--r--   1 kolab    kolab       4368 Dec 14 17:59 hmac.h
>> -rw-r--r--   1 kolab    kolab       7642 Dec 14 17:59 krb5_asn.h
>> -rw-r--r--   1 kolab    kolab       5927 Dec 14 17:59 kssl.h
>> -rw-r--r--   1 kolab    kolab       7429 Dec 14 17:59 lhash.h
>> -rw-r--r--   1 kolab    kolab       3897 Dec 14 17:59 md2.h
>> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md4.h
>> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md5.h
>> -rw-r--r--   1 kolab    kolab     113729 Dec 14 17:59 obj_mac.h
>> -rw-r--r--   1 kolab    kolab      33396 Dec 14 17:59 objects.h
>> -rw-r--r--   1 kolab    kolab      23795 Dec 14 17:59 ocsp.h
>> -rw-r--r--   1 kolab    kolab       6533 Dec 14 17:59 opensslconf.h
>> -rw-r--r--   1 kolab    kolab       3751 Dec 14 17:59 opensslv.h
>> -rw-r--r--   1 kolab    kolab       6446 Dec 14 17:59 ossl_typ.h
>> -rw-r--r--   1 kolab    kolab      27927 Dec 14 17:59 pem.h
>> -rw-r--r--   1 kolab    kolab       2863 Dec 14 17:59 pem2.h
>> -rw-r--r--   1 kolab    kolab      12677 Dec 14 17:59 pkcs12.h
>> -rw-r--r--   1 kolab    kolab      16333 Dec 14 17:59 pkcs7.h
>> -rw-r--r--   1 kolab    kolab       6150 Dec 14 17:59 pq_compat.h
>> -rw-r--r--   1 kolab    kolab       3519 Dec 14 17:59 pqueue.h
>> -rw-r--r--   1 kolab    kolab       5251 Dec 14 17:59 rand.h
>> -rw-r--r--   1 kolab    kolab       4294 Dec 14 17:59 rc2.h
>> -rw-r--r--   1 kolab    kolab       3707 Dec 14 17:59 rc4.h
>> -rw-r--r--   1 kolab    kolab       4284 Dec 14 17:59 ripemd.h
>> -rw-r--r--   1 kolab    kolab      18202 Dec 14 17:59 rsa.h
>> -rw-r--r--   1 kolab    kolab     126893 Dec 14 17:59 safestack.h
>> -rw-r--r--   1 kolab    kolab       7329 Dec 14 17:59 sha.h
>> -rw-r--r--   1 kolab    kolab      82501 Dec 14 17:59 ssl.h
>> -rw-r--r--   1 kolab    kolab      10716 Dec 14 17:59 ssl2.h
>> -rw-r--r--   1 kolab    kolab       3744 Dec 14 17:59 ssl23.h
>> -rw-r--r--   1 kolab    kolab      22283 Dec 14 17:59 ssl3.h
>> -rw-r--r--   1 kolab    kolab       4418 Dec 14 17:59 stack.h
>> -rw-r--r--   1 kolab    kolab      26481 Dec 14 17:59 store.h
>> -rw-r--r--   1 kolab    kolab      19456 Dec 14 17:59 symhacks.h
>> -rw-r--r--   1 kolab    kolab      18121 Dec 14 17:59 tls1.h
>> -rw-r--r--   1 kolab    kolab       4117 Dec 14 17:59 tmdiff.h
>> -rw-r--r--   1 kolab    kolab       4300 Dec 14 17:59 txt_db.h
>> -rw-r--r--   1 kolab    kolab      16418 Dec 14 17:59 ui.h
>> -rw-r--r--   1 kolab    kolab       3439 Dec 14 17:59 ui_compat.h
>> -rw-r--r--   1 kolab    kolab      47946 Dec 14 17:59 x509.h
>> -rw-r--r--   1 kolab    kolab      20782 Dec 14 17:59 x509_vfy.h
>> -rw-r--r--   1 kolab    kolab      29980 Dec 14 17:59 x509v3.h
>>
>>
>> What is going wrong here....? How to proceed.....? If you need more
>> information please tell me.
>>
>> kinde regards
>>
>> Andrea Soliva
>>
>> Mail: soliva at comcept.ch
>>
>> _______________________________________________
>> Kolab-devel mailing list
>> Kolab-devel at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-devel
>>
>
>
>
> --
> ______ 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.
>



-- 
______ 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-devel/attachments/20081221/6f804944/attachment.bin

From wrobel at pardus.de  Sun Dec 21 23:42:48 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sun, 21 Dec 2008 23:42:48 +0100
Subject: [Kolab-devel] Horde can now store Preferences in IMAP
	(was:	Horde preferences: LDAP or IMAP?)
In-Reply-To: <87ejaf84wp.fsf_-_@home.pardus.de>
References: <87zlz1trxh.fsf@home.pardus.de>
	<200710022328.32145.martin.konold@erfrakon.de>
	<71fe4e760710021605l6a2d79c0le78f0d70adb8347d@mail.gmail.com>
	<200710301025.13994.stephane@voyageonline.co.uk>
	<87odeetdzx.fsf@home.pardus.de> <87ejaf84wp.fsf_-_@home.pardus.de>
Message-ID: <20081221234248.12067680kz9f5dgc@webmail.pardus.de>

Hi!

A while back (beginning of this year) we had a discussion on how to  
store the user preferences of the Kolab webclient (based on Horde).

Horde preferences are being handled by a single module called "prefs".  
This module supports several backends. Among them are

  - SQL
  - LDAP
  - File based
  - IMAP

Horde usually uses SQL. Kolab has traditionally used the LDAP backend.  
This LDAP backend has been replaced with the file based backend for  
Kolab Server 2.2.1 beta 1. An alternative would also be the storage in  
IMAP similar to the other groupware data of the Kolab server.

The decision to switch to the file based approach was made since the  
developer team did not consider LDAP to be a decent place for such  
data anymore. It makes the LDAP entries rather complex and LDAP is  
usually meant primarily for read access rater than a standard storage  
space.

We decided not to use IMAP at the moment as that would mean we would  
need to discuss the Kolab format for such entries wich would take a  
while until we finalize it.

So the file based approach has been selected for now.

This does not hinder anyone to choose any of the other possible  
backends. People that like to remain on LDAP can do so without  
problems while people preferring IMAP storage can also choose to do so.

But the question still is: What is the best default?

It would be great if people could add the pros and cons they see for  
the different solutions. I'll try to add an overview once we have some  
opinions and I'll include the relevant pieces from the discussion we  
had at the beginning of this year.

I would like to add that I personally see the IMAP driver as the best  
choice. For me the Kolab server architecture results in one simple  
conclusion: User data belongs into IMAP. And preferences are user data.

Cheers,

Gunnar

Quoting Gunnar Wrobel <wrobel at pardus.de>:

> Gunnar Wrobel <wrobel at pardus.de> writes:
>
>> Stephane Konstantaropoulos <stephane at voyageonline.co.uk> writes:
>>
>>> Hello,
>>>
>>> I fully agree with Alain, the LDAP preferences backend for Horde  
>>> is efficient
>>> and is there, I see no point in creating a new one. Plus it is very easy to
>>> admin for shops that use LDAP for a lot of things, such as Samba or POSIX
>>> auth. We use LDAP as a backend for most of our users' stuff and it is very
>>> solid.
>>
>> Thanks for the feedback. The LDAP preferences backend will definitely
>> stay the default backend now. People convinced me :)
>>
>> The IMAP preferences backend might still find it's way into Horde CVS
>> at some point. But it will be purely optional then.
>
> The IMAP driver for preferences is available since yesterday within Horde.
>
> While most people will probably use the older LDAP driver I want to be
> able to have an "IMAP-only" Horde/Kolab with Horde 4.
>
> Cheers,
>
> Gunnar
>
>>
>> Cheers,
>>
>> Gunnar
>>
>>>
>>> We store iPlanet prefs, Samba prefs, Posix prefs and user data in there and
>>> that's what it is there for.
>>>
>>> I think you should stick to it with Horde, and perhaps see if you  
>>> can optmize
>>> some stuff, like session caching or something.
>>>
>>> My production Horde is slowed down by the Imap server more than the LDAP
>>> server. (a few thousand users).
>>>
>>> My 2 cents
>>>
>>> Stephane
>>>
>>> Le Wednesday 03 October 2007 00:05:27 Alain Spineux, vous avez ?crit :
>>>> On 10/2/07, Martin Konold <martin.konold at erfrakon.de> wrote:
>>>> > Am Dienstag 02 Oktober 2007 schrieb Gunnar Wrobel: out
>>>> >
>>>> > Hi Gunnar,
>>>> >
>>>> > thanks for taking up with this initiative.
>>>> >
>>>> > I am also not very happy with the current LDAP approach which  
>>>> clutters up
>>>> > the LDAP namespace very much and looks more like an abuse than like a
>>>> > useful directory. (e.g. many unused empty entries)
>>>>
>>>> This is the way LDAP works.
>>>>
>>>> LDAP is the perfect place to store data from different application
>>>> (but all related to the same object). Different apps can share the
>>>> same data from different place. LDAP provide ACL at
>>>> object and field level !
>>>>
>>>> > > I regard LDAP as a bad storage place for the web client preferences
>>>> > > and wrote a new preferences driver for Horde that uses an IMAP folder
>>>> >
>>>> > Why did you rule out the simple option to use a plain file for  
>>>> each user?
>>>> > If this plain file is protected using Apache access control it would be
>>>> > trivial to make it available anywhere whithin a Kolab server cluster.
>>>> > E.g. you could store the file on the kolabHomeServer and use a URL like
>>>> > https://kolabhomeserver.domain.tld/config/horde-preferences. Because
>>>> > horde knows the users credentials it would be trivial to provide them to
>>>> > Apache. Using these credentials Apache or some php script could
>>>> > internally use the correct user specific file
>>>>
>>>> And how do you modify this file from remote location ?
>>>>
>>>> You are designing file format, data access ... while LDAP already
>>>> exist, with all this stuff.
>>>> Why do you want to reinvent the wheel ?
>>>>
>>>> > If figuring out the kolabhomeserver via LDAP is not an option  
>>>> it could be
>>>> > handled trivially by the php script running on any server in a
>>>> > transparent manner.
>>>> >
>>>> > > The advantages of this driver: The LDAP schemas don't have to be
>>>> > > modified
>>>>
>>>> just add a "include" in slapd.conf ... not to much works
>>>>
>>>> >and the users can be plain KolabInetOrgPerson objects.
>>>>
>>>> is it an advantage ?  Could not my users be samba users ? Or  
>>>> asterisk one ?
>>>>
>>>> > In
>>>> >
>>>> > > addition this reduces LDAP read/write operations.
>>>>
>>>> Do you need to economize LDAP, are imap or file access cheaper ?
>>>> You can cache these data into the PHP sessions data !
>>>>
>>>> > I fully agree!
>>>> >
>>>> > > The disadvantages: There is a new folder type and the other clients
>>>> > > might display a "Preferences"-Folder with mails they can't really use.
>>>> >
>>>> > Well, you would still have the option of "hiding" this special folder
>>>> > from other clients using ACLs and subscription state.
>>>>
>>>> Sure ? completely hidden ? No risk for the user to erase this "strange"
>>>> folder ?
>>>>
>>>> > > 1) Do people regard it as a desired alternative to store the
>>>> > > preferences on IMAP? Any specific drawbacks or advantages I missed?
>>>>
>>>> The main kolab idea was to retrieve/store all data from LDAP and then
>>>> kolabd was synchronizing them into IMAP (creating mailbox, .......)
>>>> Why do you want to put data somewhere else ?
>>>> Then why not write directly postfix, apache, cyrus template from the GUI ?
>>>>
>>>> > I think that IMAP is an option while a plain URL pointing at  
>>>> some trivial
>>>> > PHP script is better. This script could provide transparency in  
>>>> case of a
>>>> > clustering setup and as an added bonus it could allow trivial REST
>>>> > features.
>>>>
>>>> LDAP already provide this out of the box :-)
>>>>
>>>> > This means that calling the script without parameters e.g.
>>>> > https://kolabhomeserver.domain.tld/config/horde-preferences will provide
>>>> > a single document with some trivial file format (e.g. key=value or some
>>>> > simple XML). E.g. in doing a HTTP GET to
>>>> > https://kolabhomeserver.domain.tld/config/hordePrefs would provide
>>>> > something like:
>>>>
>>>> Still imagining powerful, but less standard data access ?
>>>>
>>>> > [...]
>>>> > summary_refresh_time=10
>>>> > show_sidebar=true
>>>> > sidebar_width=40
>>>> > menu_refresh_time=100
>>>> > [...]
>>>> >
>>>> > On the other hand
>>>> >  
>>>> https://kolabhomeserver.domain.tld/config/hordePrefs?action=get&key=show_
>>>> >sidebar would return a document only containing the string "true". If the
>>>> > implementation benefits returning "show_sidebar=true" is also an option.
>>>> >
>>>> > In this simple model it would be the job of the horde  
>>>> application to know
>>>> > that the string "true" refers to a bool. Doing so is imho  
>>>> trivial in case
>>>> > of horde. This would allow to limit the capabilities of the preference
>>>> > storage service to simple strings.
>>>> >
>>>> > The php script hordePrefs.php would trivially be able to distinguish the
>>>> > users from the mandatory credentials.
>>>> >
>>>> > The actual backend used (e.g. a flat file or a small berkley DB) is then
>>>> > a simple opaque implementation detail.
>>>>
>>>> Did I already suggested you can use LDAP instead ? :-)
>>>>
>>>> > Storing a single key would be done using an URL like
>>>> >  
>>>> https://kolabhomeserver.domain.tld/config/hordePrefs?action=set&key=show_
>>>> >sidebar&value=false
>>>> >
>>>> > > 2) If this driver should be available what should be the default
>>>> > > option?
>>>> >
>>>> > IMAP is definetly better than LDAP but imho other options like my
>>>> > proposal should be considered.
>>>>
>>>> Yes IMAP is excel in storing /retrieving emails :-)
>>>>
>>>> > > The second question is important since we would need to ship the
>>>> > > driver with the earliest release possible. Otherwise we might get
>>>> > > people running this in production that will have to run "preferences
>>>> > > conversion scripts" (that would have to be written) if we ever change
>>>> > > the default option.
>>>> >
>>>> > Regards,
>>>> > -- martin konold
>>>> >
>>>> > --
>>>> > e r f r a k o n
>>>> > Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
>>>> > Sitz: Adolfstra?e 23 Stuttgart - Partnerschaftsregister Stuttgart PR 126
>>>> > http://www.erfrakon.com/
>>>> >
>>>> > _______________________________________________
>>>> > Kolab-devel mailing list
>>>> > Kolab-devel at kolab.org
>>>> > https://kolab.org/mailman/listinfo/kolab-devel
>>>
>>>
>>>
>>> --
>>> St?phane Konstantaropoulos
>>> -- Creator, Web Applications
>>> _______________________________________________
>>> Kolab-devel mailing list
>>> Kolab-devel at kolab.org
>>> https://kolab.org/mailman/listinfo/kolab-devel
>>
>> --
>> ______ 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 40 432 72335                           Bundesstrasse 29
>> Fax    : +49 40 432 70855                            D-20146 Hamburg
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>    >> Mail at ease - Rent a kolab groupware server at p at rdus <<
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> _______________________________________________
>> Kolab-devel mailing list
>> Kolab-devel at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-devel
>
> --
> ______ http://kdab.com _______________ http://kolab-konsortium.com _
>
> p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
>
> ____ http://www.pardus.de _________________ http://gunnarwrobel.de _
> E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
> Tel.   : +49 700 6245 0000                          Bundesstrasse 29
> Fax    : +49 721 1513 52322                          D-20146 Hamburg
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>    >> Mail at ease - Rent a kolab groupware server at p at rdus <<
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel



-- 
______ 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-devel/attachments/20081221/681137e4/attachment-0001.bin

From kolab-issues at intevation.de  Mon Dec 22 06:02:23 2008
From: kolab-issues at intevation.de (Gunnar Wrobel)
Date: Mon, 22 Dec 2008 05:02:23 +0000
Subject: [Kolab-devel] [issue3332] PGP Content-Description not MIME encoded
Message-ID: <1229922143.15.0.164395559704.issue3332@intevation.de>


New submission from Gunnar Wrobel <p at rdus.de>:

Encrypted messages sent by Horde may contain an unencoded 'Content-description'
header.

Already resolved upstream:

http://bugs.horde.org/ticket/7376

----------
assignedto: wrobel
messages: 18144
nosy: bernhard, thomas, wilde, wrobel
priority: minor bug
status: unread
title: PGP Content-Description not MIME encoded
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3332>
___________________________________________________


From soliva at comcept.ch  Mon Dec 22 08:47:03 2008
From: soliva at comcept.ch (ComCept Soliva)
Date: Mon, 22 Dec 2008 08:47:03 +0100
Subject: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS	libraries
	were missing or unusable
In-Reply-To: <20081221231734.58874cp3kwclwpz4@webmail.pardus.de>
References: <9268C7D7C7AB4CDCBF0DCE7A201F33F9@comcept.ch><20081218235001.69731dnw12732e9w@webmail.pardus.de><E96DBF20E3D046079698C8804C040486@comcept.ch>
	<20081221231734.58874cp3kwclwpz4@webmail.pardus.de>
Message-ID: <071079DF0B324333A4F3E68B37A7A046@comcept.ch>

Hi Gunnar

many thanks to identify the problem. If I run again the compilation it will
stop at apache2 compilation and I manipulate the .spec file that within
apache2 the option zlib will be compiled with_zlib=no. Fine so far but is
there a possibility to manipulate this in advanced? What would be the best
choice?

If there is no possibility is it still the same that If the compilation
stops --> I manipulation .spec --> start again with install-kolab.sh --> and
the compilation will not start from beginn instead it will run at this point
it stops? Why I'm asking is because I have to remove on Solaris within
install-kolab.sh the option "-mindepth 1 -maxdepth 1" (find on Solaris does
not support this option)? If I understand the script correct the option
"-mindepth 1 -maxdepth 1" checks if there is already something within /tmp
and if so will probably remove the stuff and if so beginn the compilation at
scratch?

How should I proceed? What advice you would give me?

Andrea

Mail: soliva at comcept.ch 
-----Urspr?ngliche Nachricht-----
Von: Gunnar Wrobel [mailto:wrobel at pardus.de] Im Auftrag von
kolab-devel-bounces at kolab.org
Gesendet: Sonntag, 21. Dezember 2008 23:18
An: kolab-devel at kolab.org
Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS libraries
were missing or unusable

Quoting ComCept Soliva <soliva at comcept.ch>:

> Hi
>
> in RPM/TMP/httpd-2.2.10 there is the config.log.
>
> Please find it attached

Thanks, that helped to identify the following conversation:

http://www.mail-archive.com/openpkg-users at openpkg.org/msg03467.html

It might help.

Cheers,

Gunnar

>
> Andrea
>
> Mail: soliva at comcept.ch
> -----Urspr?ngliche Nachricht-----
> Von: Gunnar Wrobel [mailto:wrobel at pardus.de] Im Auftrag von
> kolab-devel-bounces at kolab.org
> Gesendet: Donnerstag, 18. Dezember 2008 23:50
> An: kolab-devel at kolab.org
> Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS
libraries
> were missing or unusable
>
> Quoting ComCept Soliva <soliva at comcept.ch>:
>
>> Hi all
>>
>> your modifications within the install-kolab.sh script regarding PLATTAG
>> seems to work fine.
>>
>> All positions regarding mindepth/maxdepth I had to remove because Solaris
>> does not support mindepth/maxdepth within find ([Kolab-devel]
> [issue2924]).
>>
>> Before I started I verified that there is nothing at all within tmp and
>> following env variable are in use:
>>
>> SunOS dev 5.10 Generic_137111-08 sun4u sparc SUNW,Ultra-4
>>
>> # env
>>
>> _=/usr/bin/env
>> LANG=C
>> HZ=
>>
>
PATH=/usr/sbin:/usr/bin:/usr/dt/bin:/usr/openwin/bin:/bin:/usr/ucb:/opt/sfw/
>> bin:/usr/local/bin:/usr/ccs/bin
>> HISTFILE=/root/.sh_history
>> LOGNAME=root
>> MAIL=/var/mail/root
>> PS1=[root at dev $PWD]#
>> SHELL=/sbin/sh
>> HISTSIZE=200
>> HOME=/root
>> TERM=vt100
>> PWD=/kolabtmp
>> TZ=MET
>> ENV=/root/.kshrc
>>
>> # crle
>>
>> Configuration file [version 4]: /var/ld/ld.config
>>   Default Library Path (ELF):   /lib:/usr/lib:/usr/local/lib
>>   Trusted Directories (ELF):    /lib/secure:/usr/lib/secure  (system
>> default)
>>
>>
>> The compilation stopps within apache regarding SSL/TLS:
>>
>> checking whether to enable mod_ssl... checking dependencies
>> checking for SSL/TLS toolkit base... /kolab
>>   adding "-R/kolab/lib" to LDFLAGS
>> checking for OpenSSL version... checking openssl/opensslv.h usability...
> yes
>> checking openssl/opensslv.h presence... yes
>> checking for openssl/opensslv.h... yes
>> checking openssl/ssl.h usability... yes
>> checking openssl/ssl.h presence... yes
>> checking for openssl/ssl.h... yes
>> OK
>>   forcing SSL_LIBS to "-lssl -lcrypto"
>> checking openssl/engine.h usability... yes
>> checking openssl/engine.h presence... yes
>> checking for openssl/engine.h... yes
>> checking for SSLeay_version... yes
>> checking for SSL_CTX_new... no
>> checking for ENGINE_init... no
>> checking for ENGINE_load_builtin_engines... no
>> checking for SSL_set_cert_store... no
>> configure: error: ... Error, SSL/TLS libraries were missing or unusable
>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
>
> Is there still a configure.log file available from this step? It
> should be the unpacked apache source directory.
>
> Cheers,
>
> Gunnar
>
>>
>>
>> RPM build errors:
>>     Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
>> + exit 1
>>
>>
>>
>> Full Log File can be downloaeded from following link:
>>
>>
http://www.comcept.ch/kolab2/2.2.1-beta1/kolab-install-Dec-14-08_44_54.zip
>>
>> More information about install can be found at:
>>
>> http://www.comcept.ch/kolab2/2.2.1-beta1/solaris_10_kolab2_install.txt
>>
>>
>>
>> OpenSSL was compiled and installed successful:
>>
>>
>> Processing files: openssl-0.9.8g-20080101
>> Wrote: /kolab/RPM/PKG/openssl-0.9.8g-20080101.sparc64-solaris10-kolab.rpm
>> Executing(%clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
> --posix
>> -e /kolab/RPM/TMP/rpm-tmp.699
>> + cd /kolab/RPM/TMP
>> + cd openssl-0.9.8g
>> + rm -rf /kolab/RPM/TMP/openssl-0.9.8g-root
>> + exit 0
>> Executing(--clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
>> --posix -e /kolab/RPM/TMP/rpm-tmp.17537
>> + cd /kolab/RPM/TMP
>> + rm -rf openssl-0.9.8g
>> + exit 0
>> Preparing...
>> ##################################################
>> openssl
>> ##################################################
>> :::: /tmp/install-kolab....27392/openssl-0.9.8g-20080101.src.rpm = 0 ::::
>>
>> The library is also there:
>>
>> # ls -la /kolab/lib/libssl*
>> -rw-r--r--   1 kolab    kolab     403268 Dec 14 18:00 /kolab/lib/libssl.a
>>
>>
>>
>> Within the include dir openssl dir exists:
>>
>> # ls -la /kolab/include/openssl
>> total 1264
>> drwxr-xr-x   2 kolab    kolab         70 Dec 14 18:02 .
>> drwxr-xr-x  14 kolab    kolab         41 Dec 14 21:39 ..
>> -rw-r--r--   1 kolab    kolab       5372 Dec 14 17:59 aes.h
>> -rw-r--r--   1 kolab    kolab      46728 Dec 14 17:59 asn1.h
>> -rw-r--r--   1 kolab    kolab      18956 Dec 14 17:59 asn1_mac.h
>> -rw-r--r--   1 kolab    kolab      27838 Dec 14 17:59 asn1t.h
>> -rw-r--r--   1 kolab    kolab      30772 Dec 14 17:59 bio.h
>> -rw-r--r--   1 kolab    kolab       5073 Dec 14 17:59 blowfish.h
>> -rw-r--r--   1 kolab    kolab      33035 Dec 14 17:59 bn.h
>> -rw-r--r--   1 kolab    kolab       4565 Dec 14 17:59 buffer.h
>> -rw-r--r--   1 kolab    kolab       4349 Dec 14 17:59 cast.h
>> -rw-r--r--   1 kolab    kolab       1601 Dec 14 17:59 comp.h
>> -rw-r--r--   1 kolab    kolab       9484 Dec 14 17:59 conf.h
>> -rw-r--r--   1 kolab    kolab       4080 Dec 14 17:59 conf_api.h
>> -rw-r--r--   1 kolab    kolab      22121 Dec 14 17:59 crypto.h
>> -rw-r--r--   1 kolab    kolab      10724 Dec 14 17:59 des.h
>> -rw-r--r--   1 kolab    kolab      18226 Dec 14 17:59 des_old.h
>> -rw-r--r--   1 kolab    kolab       8372 Dec 14 17:59 dh.h
>> -rw-r--r--   1 kolab    kolab      10474 Dec 14 17:59 dsa.h
>> -rw-r--r--   1 kolab    kolab      16252 Dec 14 17:59 dso.h
>> -rw-r--r--   1 kolab    kolab       6146 Dec 14 17:59 dtls1.h
>> -rw-r--r--   1 kolab    kolab       9632 Dec 14 17:59 e_os2.h
>> -rw-r--r--   1 kolab    kolab        540 Dec 14 17:59 ebcdic.h
>> -rw-r--r--   1 kolab    kolab      21389 Dec 14 17:59 ec.h
>> -rw-r--r--   1 kolab    kolab       4609 Dec 14 17:59 ecdh.h
>> -rw-r--r--   1 kolab    kolab      10578 Dec 14 17:59 ecdsa.h
>> -rw-r--r--   1 kolab    kolab      37839 Dec 14 17:59 engine.h
>> -rw-r--r--   1 kolab    kolab      12493 Dec 14 17:59 err.h
>> -rw-r--r--   1 kolab    kolab      35620 Dec 14 17:59 evp.h
>> -rw-r--r--   1 kolab    kolab       4368 Dec 14 17:59 hmac.h
>> -rw-r--r--   1 kolab    kolab       7642 Dec 14 17:59 krb5_asn.h
>> -rw-r--r--   1 kolab    kolab       5927 Dec 14 17:59 kssl.h
>> -rw-r--r--   1 kolab    kolab       7429 Dec 14 17:59 lhash.h
>> -rw-r--r--   1 kolab    kolab       3897 Dec 14 17:59 md2.h
>> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md4.h
>> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md5.h
>> -rw-r--r--   1 kolab    kolab     113729 Dec 14 17:59 obj_mac.h
>> -rw-r--r--   1 kolab    kolab      33396 Dec 14 17:59 objects.h
>> -rw-r--r--   1 kolab    kolab      23795 Dec 14 17:59 ocsp.h
>> -rw-r--r--   1 kolab    kolab       6533 Dec 14 17:59 opensslconf.h
>> -rw-r--r--   1 kolab    kolab       3751 Dec 14 17:59 opensslv.h
>> -rw-r--r--   1 kolab    kolab       6446 Dec 14 17:59 ossl_typ.h
>> -rw-r--r--   1 kolab    kolab      27927 Dec 14 17:59 pem.h
>> -rw-r--r--   1 kolab    kolab       2863 Dec 14 17:59 pem2.h
>> -rw-r--r--   1 kolab    kolab      12677 Dec 14 17:59 pkcs12.h
>> -rw-r--r--   1 kolab    kolab      16333 Dec 14 17:59 pkcs7.h
>> -rw-r--r--   1 kolab    kolab       6150 Dec 14 17:59 pq_compat.h
>> -rw-r--r--   1 kolab    kolab       3519 Dec 14 17:59 pqueue.h
>> -rw-r--r--   1 kolab    kolab       5251 Dec 14 17:59 rand.h
>> -rw-r--r--   1 kolab    kolab       4294 Dec 14 17:59 rc2.h
>> -rw-r--r--   1 kolab    kolab       3707 Dec 14 17:59 rc4.h
>> -rw-r--r--   1 kolab    kolab       4284 Dec 14 17:59 ripemd.h
>> -rw-r--r--   1 kolab    kolab      18202 Dec 14 17:59 rsa.h
>> -rw-r--r--   1 kolab    kolab     126893 Dec 14 17:59 safestack.h
>> -rw-r--r--   1 kolab    kolab       7329 Dec 14 17:59 sha.h
>> -rw-r--r--   1 kolab    kolab      82501 Dec 14 17:59 ssl.h
>> -rw-r--r--   1 kolab    kolab      10716 Dec 14 17:59 ssl2.h
>> -rw-r--r--   1 kolab    kolab       3744 Dec 14 17:59 ssl23.h
>> -rw-r--r--   1 kolab    kolab      22283 Dec 14 17:59 ssl3.h
>> -rw-r--r--   1 kolab    kolab       4418 Dec 14 17:59 stack.h
>> -rw-r--r--   1 kolab    kolab      26481 Dec 14 17:59 store.h
>> -rw-r--r--   1 kolab    kolab      19456 Dec 14 17:59 symhacks.h
>> -rw-r--r--   1 kolab    kolab      18121 Dec 14 17:59 tls1.h
>> -rw-r--r--   1 kolab    kolab       4117 Dec 14 17:59 tmdiff.h
>> -rw-r--r--   1 kolab    kolab       4300 Dec 14 17:59 txt_db.h
>> -rw-r--r--   1 kolab    kolab      16418 Dec 14 17:59 ui.h
>> -rw-r--r--   1 kolab    kolab       3439 Dec 14 17:59 ui_compat.h
>> -rw-r--r--   1 kolab    kolab      47946 Dec 14 17:59 x509.h
>> -rw-r--r--   1 kolab    kolab      20782 Dec 14 17:59 x509_vfy.h
>> -rw-r--r--   1 kolab    kolab      29980 Dec 14 17:59 x509v3.h
>>
>>
>> What is going wrong here....? How to proceed.....? If you need more
>> information please tell me.
>>
>> kinde regards
>>
>> Andrea Soliva
>>
>> Mail: soliva at comcept.ch
>>
>> _______________________________________________
>> Kolab-devel mailing list
>> Kolab-devel at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-devel
>>
>
>
>
> --
> ______ 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.
>



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


From bernhard at intevation.de  Mon Dec 22 15:53:16 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 22 Dec 2008 15:53:16 +0100
Subject: [Kolab-devel] Help with getting email working:
	kolab-server-2.2.1-beta-1
In-Reply-To: <20081220193453.62192mxnz0gvejsw@webmail.pardus.de>
References: <54EC12E8D9B4476596228C52EF134C6F@mdmbxp>
	<8634029a0812190919q3d8510fbofc1d702d24a6484c@mail.gmail.com>
	<20081220193453.62192mxnz0gvejsw@webmail.pardus.de>
Message-ID: <200812221553.16930.bernhard@intevation.de>

Am Samstag, 20. Dezember 2008 19:34:53 schrieb Gunnar Wrobel:
> 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.

We should update the readme for 2.2.1-beta1, shouldn't we?

-- 
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-devel/attachments/20081222/2eba383e/attachment.bin

From wrobel at pardus.de  Mon Dec 22 21:44:38 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Mon, 22 Dec 2008 21:44:38 +0100
Subject: [Kolab-devel] Help with getting email
	working:	kolab-server-2.2.1-beta-1
In-Reply-To: <200812221553.16930.bernhard@intevation.de>
References: <54EC12E8D9B4476596228C52EF134C6F@mdmbxp>
	<8634029a0812190919q3d8510fbofc1d702d24a6484c@mail.gmail.com>
	<20081220193453.62192mxnz0gvejsw@webmail.pardus.de>
	<200812221553.16930.bernhard@intevation.de>
Message-ID: <20081222214438.211362adrwtyeio0@webmail.pardus.de>

Quoting Bernhard Reiter <bernhard at intevation.de>:

> Am Samstag, 20. Dezember 2008 19:34:53 schrieb Gunnar Wrobel:
>> 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.
>
> We should update the readme for 2.2.1-beta1, shouldn't we?

Yes we should if that is possible.

Cheers,

Gunnar

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



-- 
______ 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-devel/attachments/20081222/0065528c/attachment.bin

From bernhard at intevation.de  Tue Dec 23 11:10:42 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 23 Dec 2008 11:10:42 +0100
Subject: [Kolab-devel]
	=?iso-8859-15?q?Help_with_getting_email_working=3A?=
	=?iso-8859-15?q?=09kolab-server-2=2E2=2E1-beta-1?=
In-Reply-To: <20081222214438.211362adrwtyeio0@webmail.pardus.de>
References: <54EC12E8D9B4476596228C52EF134C6F@mdmbxp>
	<200812221553.16930.bernhard@intevation.de>
	<20081222214438.211362adrwtyeio0@webmail.pardus.de>
Message-ID: <200812231110.42924.bernhard@intevation.de>

On Montag, 22. Dezember 2008, Gunnar Wrobel wrote:
> > We should update the readme for 2.2.1-beta1, shouldn't we?
>
> Yes we should if that is possible.

Give me the text, I can change it of course. :)


-- 
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-devel/attachments/20081223/d4c19d96/attachment.bin

From kolab-issues at intevation.de  Tue Dec 23 17:15:02 2008
From: kolab-issues at intevation.de (Celle)
Date: Tue, 23 Dec 2008 16:15:02 +0000
Subject: [Kolab-devel] [issue3335] amateure sex
Message-ID: <5CB7EC2E.B304C56B@zappmobile.ro>


New submission from Celle <bbwxjic at zappmobile.ro>:

Hallo, mein Name ist JEISA und meine Hobbys sind zeichnen, shoppen und vor
allem Sex! Der richtige Mann fuer mich sollte mich fuehren koennen und mir
im Leben und im Bett alles geben, was ich brauche! Ausserdem machen mich
sportliche und humorvolle Maenner total scharf! Ich liebe phantasievollen
Sex in allen Variationen bei denen natuerlich auch unsere Zungen richtig
geil zum Einsatz kommen sollen! Und wenn mich dann die Geilheit packt nehme
ich live im Chat auch nur zu gerne mein Spielzeug zur Hand!

Gib folgende URL einfach ohne die Leerzeichen in Deinen Browser ein:
www. sexcamy .ch

----------
messages: 18149
nosy: bbwxjic
status: unread
title: amateure sex
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3335>
___________________________________________________


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: [Kolab-devel] 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 kolab-issues at intevation.de  Thu Dec 25 01:08:27 2008
From: kolab-issues at intevation.de (Cassey)
Date: Thu, 25 Dec 2008 00:08:27 +0000
Subject: [Kolab-devel] [issue3336] Abbe will Spe_rma schlucken
Message-ID: <2D5D9A8E.FD9D30BC@interbgc.com>


New submission from Cassey <andreckoltyt at interbgc.com>:

Hallo Suesser, ich bin Deine heisse s:e:xmaus NAOMY. Ich liebe Maenner die
nicht nur reichlich Phantasie, sondern auch viel Durchhaltevermoegen im Bett
haben. Vor allem wenn Du dazu noch gut gebaut und durchtrainiert bist, werde
ich alleine schon vom Anblick heiss! Langeweile kenne ich beim s:e:x nicht,
denn ich liebe es immer wieder Neues auszuprobieren und bin stets fuer
heisse Experimente zu haben! Ich wuerde mich selbst als spontan,
eigensinnig, lustig und offenherzig beschreiben. Lass Dich - live im Chat
von mir verzaubern!

Gib folgende URL einfach ohne die Leerzeichen in Deinen Browser ein:
www . privateamateure . tv

----------
messages: 18150
nosy: andreckoltyt
status: unread
title: Abbe will Spe_rma schlucken
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3336>
___________________________________________________


From kolab-issues at intevation.de  Fri Dec 26 01:02:55 2008
From: kolab-issues at intevation.de (Lucie)
Date: Fri, 26 Dec 2008 00:02:55 +0000
Subject: [Kolab-devel] [issue3337] Agnola will Sp.erma s_chlucken
Message-ID: <E6C7C17B.05825792@canals.ro>


New submission from Lucie <gabriele.handstangersuguy at canals.ro>:

An alle starken und geilen Maenner, hier ist Dein heisses Luder TRIXI und
ich warte darauf, es Dir geil zu besorgen! Bei meinen
Lieblingsbeschaeftigungen steht s:e:x an erster Stelle. Ich brauche es oft
und hart. Darum suche ich einen Mann, der es mir mit richtig geil und hart
besorgen kann. Wenn ich Dich dann so scharf gemacht habe, dass Du bereit
fuer die 2. Runde bist, dann moechte ich es richtig wild und hemmungslos.
Dann kann es auch schon mal passieren, dass ich sehr laut werde ;-) Ich
treibe es gerne an ungewoehnlichen Orten, zum Beispiel auf der Toilette im
Restaurant oder im Aufzug. Aber auch fuer einen geilen 3er bin ich zu
haben....ich bin fuer alles offen Baby, also komm und treibe es wild mit mir
- live im Chat!

Meine M-uschi ist schon ganz nass!
Und nicht nur zu Weihnachten ;-)

Gib folgende URL einfach ohne die Leerzeichen in Deinen Browser ein:
www . privateamateure . tv

----------
messages: 18151
nosy: gabriele.handstangersuguy
status: unread
title: Agnola will Sp.erma s_chlucken
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3337>
___________________________________________________


From wrobel at pardus.de  Sat Dec 27 11:54:45 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sat, 27 Dec 2008 11:54:45 +0100
Subject: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1
	Beta	1SSL/TLS	libraries were missing or unusable
In-Reply-To: <071079DF0B324333A4F3E68B37A7A046@comcept.ch>
References: <9268C7D7C7AB4CDCBF0DCE7A201F33F9@comcept.ch><20081218235001.69731dnw12732e9w@webmail.pardus.de><E96DBF20E3D046079698C8804C040486@comcept.ch>
	<20081221231734.58874cp3kwclwpz4@webmail.pardus.de>
	<071079DF0B324333A4F3E68B37A7A046@comcept.ch>
Message-ID: <20081227115445.11314omit5dq7m2o@webmail.pardus.de>

Quoting ComCept Soliva <soliva at comcept.ch>:

> Hi Gunnar
>
> many thanks to identify the problem. If I run again the compilation it will
> stop at apache2 compilation and I manipulate the .spec file that within
> apache2 the option zlib will be compiled with_zlib=no. Fine so far but is
> there a possibility to manipulate this in advanced? What would be the best
> choice?

I think it should be possible to set that in install-kolab.sh:

Line 25 -> DEFINE="... -D apache::with_zlib=no"

>
> If there is no possibility is it still the same that If the compilation
> stops --> I manipulation .spec --> start again with install-kolab.sh --> and
> the compilation will not start from beginn instead it will run at this point
> it stops? Why I'm asking is because I have to remove on Solaris within
> install-kolab.sh the option "-mindepth 1 -maxdepth 1" (find on Solaris does
> not support this option)? If I understand the script correct the option
> "-mindepth 1 -maxdepth 1" checks if there is already something within /tmp
> and if so will probably remove the stuff and if so beginn the compilation at
> scratch?
>
> How should I proceed? What advice you would give me?

Try the hint given above. In addition you should open a bug in the  
issue tracker. I'll assign it to Thomas and we'll see if we can set  
this option by default as long as this problem exists.

Cheers,

Gunnar

>
> Andrea
>
> Mail: soliva at comcept.ch
> -----Urspr?ngliche Nachricht-----
> Von: Gunnar Wrobel [mailto:wrobel at pardus.de] Im Auftrag von
> kolab-devel-bounces at kolab.org
> Gesendet: Sonntag, 21. Dezember 2008 23:18
> An: kolab-devel at kolab.org
> Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS libraries
> were missing or unusable
>
> Quoting ComCept Soliva <soliva at comcept.ch>:
>
>> Hi
>>
>> in RPM/TMP/httpd-2.2.10 there is the config.log.
>>
>> Please find it attached
>
> Thanks, that helped to identify the following conversation:
>
> http://www.mail-archive.com/openpkg-users at openpkg.org/msg03467.html
>
> It might help.
>
> Cheers,
>
> Gunnar
>
>>
>> Andrea
>>
>> Mail: soliva at comcept.ch
>> -----Urspr?ngliche Nachricht-----
>> Von: Gunnar Wrobel [mailto:wrobel at pardus.de] Im Auftrag von
>> kolab-devel-bounces at kolab.org
>> Gesendet: Donnerstag, 18. Dezember 2008 23:50
>> An: kolab-devel at kolab.org
>> Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS
> libraries
>> were missing or unusable
>>
>> Quoting ComCept Soliva <soliva at comcept.ch>:
>>
>>> Hi all
>>>
>>> your modifications within the install-kolab.sh script regarding PLATTAG
>>> seems to work fine.
>>>
>>> All positions regarding mindepth/maxdepth I had to remove because Solaris
>>> does not support mindepth/maxdepth within find ([Kolab-devel]
>> [issue2924]).
>>>
>>> Before I started I verified that there is nothing at all within tmp and
>>> following env variable are in use:
>>>
>>> SunOS dev 5.10 Generic_137111-08 sun4u sparc SUNW,Ultra-4
>>>
>>> # env
>>>
>>> _=/usr/bin/env
>>> LANG=C
>>> HZ=
>>>
>>
> PATH=/usr/sbin:/usr/bin:/usr/dt/bin:/usr/openwin/bin:/bin:/usr/ucb:/opt/sfw/
>>> bin:/usr/local/bin:/usr/ccs/bin
>>> HISTFILE=/root/.sh_history
>>> LOGNAME=root
>>> MAIL=/var/mail/root
>>> PS1=[root at dev $PWD]#
>>> SHELL=/sbin/sh
>>> HISTSIZE=200
>>> HOME=/root
>>> TERM=vt100
>>> PWD=/kolabtmp
>>> TZ=MET
>>> ENV=/root/.kshrc
>>>
>>> # crle
>>>
>>> Configuration file [version 4]: /var/ld/ld.config
>>>   Default Library Path (ELF):   /lib:/usr/lib:/usr/local/lib
>>>   Trusted Directories (ELF):    /lib/secure:/usr/lib/secure  (system
>>> default)
>>>
>>>
>>> The compilation stopps within apache regarding SSL/TLS:
>>>
>>> checking whether to enable mod_ssl... checking dependencies
>>> checking for SSL/TLS toolkit base... /kolab
>>>   adding "-R/kolab/lib" to LDFLAGS
>>> checking for OpenSSL version... checking openssl/opensslv.h usability...
>> yes
>>> checking openssl/opensslv.h presence... yes
>>> checking for openssl/opensslv.h... yes
>>> checking openssl/ssl.h usability... yes
>>> checking openssl/ssl.h presence... yes
>>> checking for openssl/ssl.h... yes
>>> OK
>>>   forcing SSL_LIBS to "-lssl -lcrypto"
>>> checking openssl/engine.h usability... yes
>>> checking openssl/engine.h presence... yes
>>> checking for openssl/engine.h... yes
>>> checking for SSLeay_version... yes
>>> checking for SSL_CTX_new... no
>>> checking for ENGINE_init... no
>>> checking for ENGINE_load_builtin_engines... no
>>> checking for SSL_set_cert_store... no
>>> configure: error: ... Error, SSL/TLS libraries were missing or unusable
>>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
>>
>> Is there still a configure.log file available from this step? It
>> should be the unpacked apache source directory.
>>
>> Cheers,
>>
>> Gunnar
>>
>>>
>>>
>>> RPM build errors:
>>>     Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
>>> + exit 1
>>>
>>>
>>>
>>> Full Log File can be downloaeded from following link:
>>>
>>>
> http://www.comcept.ch/kolab2/2.2.1-beta1/kolab-install-Dec-14-08_44_54.zip
>>>
>>> More information about install can be found at:
>>>
>>> http://www.comcept.ch/kolab2/2.2.1-beta1/solaris_10_kolab2_install.txt
>>>
>>>
>>>
>>> OpenSSL was compiled and installed successful:
>>>
>>>
>>> Processing files: openssl-0.9.8g-20080101
>>> Wrote: /kolab/RPM/PKG/openssl-0.9.8g-20080101.sparc64-solaris10-kolab.rpm
>>> Executing(%clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
>> --posix
>>> -e /kolab/RPM/TMP/rpm-tmp.699
>>> + cd /kolab/RPM/TMP
>>> + cd openssl-0.9.8g
>>> + rm -rf /kolab/RPM/TMP/openssl-0.9.8g-root
>>> + exit 0
>>> Executing(--clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
>>> --posix -e /kolab/RPM/TMP/rpm-tmp.17537
>>> + cd /kolab/RPM/TMP
>>> + rm -rf openssl-0.9.8g
>>> + exit 0
>>> Preparing...
>>> ##################################################
>>> openssl
>>> ##################################################
>>> :::: /tmp/install-kolab....27392/openssl-0.9.8g-20080101.src.rpm = 0 ::::
>>>
>>> The library is also there:
>>>
>>> # ls -la /kolab/lib/libssl*
>>> -rw-r--r--   1 kolab    kolab     403268 Dec 14 18:00 /kolab/lib/libssl.a
>>>
>>>
>>>
>>> Within the include dir openssl dir exists:
>>>
>>> # ls -la /kolab/include/openssl
>>> total 1264
>>> drwxr-xr-x   2 kolab    kolab         70 Dec 14 18:02 .
>>> drwxr-xr-x  14 kolab    kolab         41 Dec 14 21:39 ..
>>> -rw-r--r--   1 kolab    kolab       5372 Dec 14 17:59 aes.h
>>> -rw-r--r--   1 kolab    kolab      46728 Dec 14 17:59 asn1.h
>>> -rw-r--r--   1 kolab    kolab      18956 Dec 14 17:59 asn1_mac.h
>>> -rw-r--r--   1 kolab    kolab      27838 Dec 14 17:59 asn1t.h
>>> -rw-r--r--   1 kolab    kolab      30772 Dec 14 17:59 bio.h
>>> -rw-r--r--   1 kolab    kolab       5073 Dec 14 17:59 blowfish.h
>>> -rw-r--r--   1 kolab    kolab      33035 Dec 14 17:59 bn.h
>>> -rw-r--r--   1 kolab    kolab       4565 Dec 14 17:59 buffer.h
>>> -rw-r--r--   1 kolab    kolab       4349 Dec 14 17:59 cast.h
>>> -rw-r--r--   1 kolab    kolab       1601 Dec 14 17:59 comp.h
>>> -rw-r--r--   1 kolab    kolab       9484 Dec 14 17:59 conf.h
>>> -rw-r--r--   1 kolab    kolab       4080 Dec 14 17:59 conf_api.h
>>> -rw-r--r--   1 kolab    kolab      22121 Dec 14 17:59 crypto.h
>>> -rw-r--r--   1 kolab    kolab      10724 Dec 14 17:59 des.h
>>> -rw-r--r--   1 kolab    kolab      18226 Dec 14 17:59 des_old.h
>>> -rw-r--r--   1 kolab    kolab       8372 Dec 14 17:59 dh.h
>>> -rw-r--r--   1 kolab    kolab      10474 Dec 14 17:59 dsa.h
>>> -rw-r--r--   1 kolab    kolab      16252 Dec 14 17:59 dso.h
>>> -rw-r--r--   1 kolab    kolab       6146 Dec 14 17:59 dtls1.h
>>> -rw-r--r--   1 kolab    kolab       9632 Dec 14 17:59 e_os2.h
>>> -rw-r--r--   1 kolab    kolab        540 Dec 14 17:59 ebcdic.h
>>> -rw-r--r--   1 kolab    kolab      21389 Dec 14 17:59 ec.h
>>> -rw-r--r--   1 kolab    kolab       4609 Dec 14 17:59 ecdh.h
>>> -rw-r--r--   1 kolab    kolab      10578 Dec 14 17:59 ecdsa.h
>>> -rw-r--r--   1 kolab    kolab      37839 Dec 14 17:59 engine.h
>>> -rw-r--r--   1 kolab    kolab      12493 Dec 14 17:59 err.h
>>> -rw-r--r--   1 kolab    kolab      35620 Dec 14 17:59 evp.h
>>> -rw-r--r--   1 kolab    kolab       4368 Dec 14 17:59 hmac.h
>>> -rw-r--r--   1 kolab    kolab       7642 Dec 14 17:59 krb5_asn.h
>>> -rw-r--r--   1 kolab    kolab       5927 Dec 14 17:59 kssl.h
>>> -rw-r--r--   1 kolab    kolab       7429 Dec 14 17:59 lhash.h
>>> -rw-r--r--   1 kolab    kolab       3897 Dec 14 17:59 md2.h
>>> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md4.h
>>> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md5.h
>>> -rw-r--r--   1 kolab    kolab     113729 Dec 14 17:59 obj_mac.h
>>> -rw-r--r--   1 kolab    kolab      33396 Dec 14 17:59 objects.h
>>> -rw-r--r--   1 kolab    kolab      23795 Dec 14 17:59 ocsp.h
>>> -rw-r--r--   1 kolab    kolab       6533 Dec 14 17:59 opensslconf.h
>>> -rw-r--r--   1 kolab    kolab       3751 Dec 14 17:59 opensslv.h
>>> -rw-r--r--   1 kolab    kolab       6446 Dec 14 17:59 ossl_typ.h
>>> -rw-r--r--   1 kolab    kolab      27927 Dec 14 17:59 pem.h
>>> -rw-r--r--   1 kolab    kolab       2863 Dec 14 17:59 pem2.h
>>> -rw-r--r--   1 kolab    kolab      12677 Dec 14 17:59 pkcs12.h
>>> -rw-r--r--   1 kolab    kolab      16333 Dec 14 17:59 pkcs7.h
>>> -rw-r--r--   1 kolab    kolab       6150 Dec 14 17:59 pq_compat.h
>>> -rw-r--r--   1 kolab    kolab       3519 Dec 14 17:59 pqueue.h
>>> -rw-r--r--   1 kolab    kolab       5251 Dec 14 17:59 rand.h
>>> -rw-r--r--   1 kolab    kolab       4294 Dec 14 17:59 rc2.h
>>> -rw-r--r--   1 kolab    kolab       3707 Dec 14 17:59 rc4.h
>>> -rw-r--r--   1 kolab    kolab       4284 Dec 14 17:59 ripemd.h
>>> -rw-r--r--   1 kolab    kolab      18202 Dec 14 17:59 rsa.h
>>> -rw-r--r--   1 kolab    kolab     126893 Dec 14 17:59 safestack.h
>>> -rw-r--r--   1 kolab    kolab       7329 Dec 14 17:59 sha.h
>>> -rw-r--r--   1 kolab    kolab      82501 Dec 14 17:59 ssl.h
>>> -rw-r--r--   1 kolab    kolab      10716 Dec 14 17:59 ssl2.h
>>> -rw-r--r--   1 kolab    kolab       3744 Dec 14 17:59 ssl23.h
>>> -rw-r--r--   1 kolab    kolab      22283 Dec 14 17:59 ssl3.h
>>> -rw-r--r--   1 kolab    kolab       4418 Dec 14 17:59 stack.h
>>> -rw-r--r--   1 kolab    kolab      26481 Dec 14 17:59 store.h
>>> -rw-r--r--   1 kolab    kolab      19456 Dec 14 17:59 symhacks.h
>>> -rw-r--r--   1 kolab    kolab      18121 Dec 14 17:59 tls1.h
>>> -rw-r--r--   1 kolab    kolab       4117 Dec 14 17:59 tmdiff.h
>>> -rw-r--r--   1 kolab    kolab       4300 Dec 14 17:59 txt_db.h
>>> -rw-r--r--   1 kolab    kolab      16418 Dec 14 17:59 ui.h
>>> -rw-r--r--   1 kolab    kolab       3439 Dec 14 17:59 ui_compat.h
>>> -rw-r--r--   1 kolab    kolab      47946 Dec 14 17:59 x509.h
>>> -rw-r--r--   1 kolab    kolab      20782 Dec 14 17:59 x509_vfy.h
>>> -rw-r--r--   1 kolab    kolab      29980 Dec 14 17:59 x509v3.h
>>>
>>>
>>> What is going wrong here....? How to proceed.....? If you need more
>>> information please tell me.
>>>
>>> kinde regards
>>>
>>> Andrea Soliva
>>>
>>> Mail: soliva at comcept.ch
>>>
>>> _______________________________________________
>>> Kolab-devel mailing list
>>> Kolab-devel at kolab.org
>>> https://kolab.org/mailman/listinfo/kolab-devel
>>>
>>
>>
>>
>> --
>> ______ 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.
>>
>
>
>
> --
> ______ 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-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



-- 
______ 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-devel/attachments/20081227/1a61044f/attachment.bin

From wrobel at pardus.de  Sat Dec 27 12:04:40 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sat, 27 Dec 2008 12:04:40 +0100
Subject: [Kolab-devel] Help with getting
	email	working:	kolab-server-2.2.1-beta-1
In-Reply-To: <200812231110.42924.bernhard@intevation.de>
References: <54EC12E8D9B4476596228C52EF134C6F@mdmbxp>
	<200812221553.16930.bernhard@intevation.de>
	<20081222214438.211362adrwtyeio0@webmail.pardus.de>
	<200812231110.42924.bernhard@intevation.de>
Message-ID: <20081227120440.19644247b8whyqio@webmail.pardus.de>

Quoting Bernhard Reiter <bernhard at intevation.de>:

> On Montag, 22. Dezember 2008, Gunnar Wrobel wrote:
>> > We should update the readme for 2.2.1-beta1, shouldn't we?
>>
>> Yes we should if that is possible.
>
> Give me the text, I can change it of course. :)

Suggested patch attached.

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



-- 
______ 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: README.patch
Type: text/x-diff
Size: 1045 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20081227/562a079b/README.bin
-------------- 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-devel/attachments/20081227/562a079b/attachment.bin

From kolab-issues at intevation.de  Sat Dec 27 17:25:50 2008
From: kolab-issues at intevation.de (Daniel Vergien)
Date: Sat, 27 Dec 2008 16:25:50 +0000
Subject: [Kolab-devel] [issue3338] No Webclient on 2.2-beta1
Message-ID: <1230395150.1.0.605903314836.issue3338@intevation.de>


New submission from Daniel Vergien <daniel.vergien at web.de>:

When I try to login to the webclient on a solaris installation via
https://kolab.xx/client I just get a welcome message, but no username/password
fields.

apache-access.log says:
192.168.1.11 - - [27/Dec/2008:17:23:29 +0100] "GET /client/login.php HTTP/1.1"
500 801
192.168.1.11 - - [27/Dec/2008:17:23:29 +0100] "GET /client/js/horde.js HTTP/1.1"
304 -
192.168.1.11 - - [27/Dec/2008:17:23:29 +0100] "GET /client/themes/screen.css
HTTP/1.1" 304 -
192.168.1.11 - - [27/Dec/2008:17:23:29 +0100] "GET
/client/themes/silver/screen.css HTTP/1.1" 304 -
192.168.1.11 - - [27/Dec/2008:17:23:29 +0100] "GET
/client/themes/silver/graphics/menu.png HTTP/1.1" 304 -

apache.error.log and php/php-errors.log says nothing.
The admin site is working

----------
messages: 18176
nosy: daniel.vergien
priority: bug
status: unread
title: No Webclient on 2.2-beta1
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3338>
___________________________________________________


From kolab-issues at intevation.de  Sun Dec 28 03:12:54 2008
From: kolab-issues at intevation.de (Beilul)
Date: Sun, 28 Dec 2008 02:12:54 +0000
Subject: [Kolab-devel] [issue3339] Abby moechte S_perma s:chlucken
Message-ID: <4E7A3C92.80636FC3@erdves.lt>


New submission from Beilul <elplastajustoxo at erdves.lt>:

Hallo Du Geiler! Ich bin die HeisseHelena und ich will Dein privates
s:e:xspielzeug sein! Um Dir zu gefallen bin ich bereit so gut wie alles zu
tun und darum geniesse ich es ganz besonders wenn wir dabei in die Rolle des
Meisters und seiner Sklavin schluepfen! Lass mich Dir gehorchen und Dir
jeden Wunsch von den Augen ablesen. Fuer Dich lasse ich meine Finger und
meine Toys einfach ueberall verschwinden und selbst vor Handspiele mache ich
dabei keinen Halt! Du darfst mich auch mit sanften Schlaegen und Klapsen
erziehen! Und natuerlich werde ich Dir auch fuer Fetish-Spiele zur
Verfuegung stehen! Mache mich live im Chat zum Spielball Deiner Lust!

Gebe folgendeURL einfach ohne die Leer Zeichen in den Browser ein:
www .  privateamateure  .  tv

----------
messages: 18178
nosy: elplastajustoxo
status: unread
title: Abby moechte S_perma s:chlucken
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3339>
___________________________________________________


From kolab-issues at intevation.de  Sun Dec 28 21:06:45 2008
From: kolab-issues at intevation.de (Gunnar Wrobel)
Date: Sun, 28 Dec 2008 20:06:45 +0000
Subject: [Kolab-devel] [issue3340] net-libs/c-client <2007e: Denial of
	Service (CVE-2008-5514)
Message-ID: <1230494804.97.0.711779640225.issue3340@intevation.de>


New submission from Gunnar Wrobel <p at rdus.de>:

https://bugs.gentoo.org/show_bug.cgi?id=252567

Just fixed this for Gentoo and thought it might be relevant for us on OpenPKG, too.

----------
assignedto: thomas
messages: 18179
nosy: thomas, wilde, wrobel
priority: urgent
status: unread
title: net-libs/c-client <2007e: Denial of Service (CVE-2008-5514)
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3340>
___________________________________________________


From kolab-issues at intevation.de  Mon Dec 29 07:17:42 2008
From: kolab-issues at intevation.de (Andrea)
Date: Mon, 29 Dec 2008 06:17:42 +0000
Subject: [Kolab-devel] [issue3341] Solaris 10 Sparc Kolab V2.2.1 Beta 1
	SSL/TLS libraries were missing or unusable
Message-ID: <1230531461.95.0.857491680828.issue3341@intevation.de>


New submission from Andrea <soliva at comcept.ch>:

Issue was identified and recognized:

http://www.mail-archive.com/openpkg-users at openpkg.org/msg03467.html

--------------- msg03467.html --------------- 
Thanks for the config.log. I see the problem. You built "openssl" with
option "with_zlib=yes". Sorry, although this works fine for OpenSSL
itself, not many upstream vendors use pkg-config and the "openssl.pc"
file in order to determine the _dependencies_ of OpenSSL. They just try
to link against "-lssl -lcrypto" and hope this works. It does, but not
if OpenSSL is built with ZLib support. As a workaround just build and
install "openssl" with "with_zlib=no", please.

                                       Ralf S. Engelschall
                                       [EMAIL PROTECTED]
                                       www.engelschall.com

--------------- msg03467.html --------------- 

Modify instal-kolab-sh in following way:


ATTENTION Delete all entries below in "install-kolab.sh" with because Solaris:
********* does not support within find these options:

		-mindepth 1 -maxdepth 1

ATTENTION Change line 25 to cover "-D apache::with_zlib=no" within 
********* apache/openssl compilation to exclude zlib otherwise the compilation 
          will fail (see below error message):


Line 25 to change within install-kolab.sh
******************************************

DEFINE="-D openldap::with_pth=no -D sasl::with_ldap -D sasl::with_login -D 
sasl::with_ntlm -D postfix::with_sasl -D postfix::with_ssl -D 
postfix::with_ldap -D imapd::with_kolab_nocaps -D apache::with_zlib=no"



	Output error install-kolab.sh if no change
	******************************************

........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
checking whether to enable mod_ssl... checking dependencies
checking for SSL/TLS toolkit base... /kolab
  adding "-R/kolab/lib" to LDFLAGS
checking for OpenSSL version... checking openssl/opensslv.h usability... yes
checking openssl/opensslv.h presence... yes
checking for openssl/opensslv.h... yes
checking openssl/ssl.h usability... yes
checking openssl/ssl.h presence... yes
checking for openssl/ssl.h... yes
OK
  forcing SSL_LIBS to "-lssl -lcrypto"
checking openssl/engine.h usability... yes
checking openssl/engine.h presence... yes
checking for openssl/engine.h... yes
checking for SSLeay_version... yes
checking for SSL_CTX_new... no
checking for ENGINE_init... no
checking for ENGINE_load_builtin_engines... no
checking for SSL_set_cert_store... no
configure: error: ... Error, SSL/TLS libraries were missing or unusable
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)


RPM build errors:
    Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
+ exit 1

----------
messages: 18180
nosy: soliva
status: unread
title: Solaris 10 Sparc Kolab V2.2.1 Beta 1 SSL/TLS libraries were missing or unusable
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3341>
___________________________________________________


From soliva at comcept.ch  Mon Dec 29 07:19:56 2008
From: soliva at comcept.ch (ComCept Soliva)
Date: Mon, 29 Dec 2008 07:19:56 +0100
Subject: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS libraries
	were missing or unusable
In-Reply-To: <20081227115445.11314omit5dq7m2o@webmail.pardus.de>
References: <9268C7D7C7AB4CDCBF0DCE7A201F33F9@comcept.ch><20081218235001.69731dnw12732e9w@webmail.pardus.de><E96DBF20E3D046079698C8804C040486@comcept.ch><20081221231734.58874cp3kwclwpz4@webmail.pardus.de><071079DF0B324333A4F3E68B37A7A046@comcept.ch>
	<20081227115445.11314omit5dq7m2o@webmail.pardus.de>
Message-ID: <00D4B4903A4940408CE0E2E1CE655C49@comcept.ch>

Hi Gunnar

issue open:

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

new compilation running at the moment..will give feedback as soon as I have
a result/overview.

kind regards

Mail: soliva at comcept.ch 
-----Urspr?ngliche Nachricht-----
Von: Gunnar Wrobel [mailto:wrobel at pardus.de] Im Auftrag von
kolab-devel-bounces at kolab.org
Gesendet: Samstag, 27. Dezember 2008 11:55
An: kolab-devel at kolab.org
Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS libraries
were missing or unusable

Quoting ComCept Soliva <soliva at comcept.ch>:

> Hi Gunnar
>
> many thanks to identify the problem. If I run again the compilation it
will
> stop at apache2 compilation and I manipulate the .spec file that within
> apache2 the option zlib will be compiled with_zlib=no. Fine so far but is
> there a possibility to manipulate this in advanced? What would be the best
> choice?

I think it should be possible to set that in install-kolab.sh:

Line 25 -> DEFINE="... -D apache::with_zlib=no"

>
> If there is no possibility is it still the same that If the compilation
> stops --> I manipulation .spec --> start again with install-kolab.sh -->
and
> the compilation will not start from beginn instead it will run at this
point
> it stops? Why I'm asking is because I have to remove on Solaris within
> install-kolab.sh the option "-mindepth 1 -maxdepth 1" (find on Solaris
does
> not support this option)? If I understand the script correct the option
> "-mindepth 1 -maxdepth 1" checks if there is already something within /tmp
> and if so will probably remove the stuff and if so beginn the compilation
at
> scratch?
>
> How should I proceed? What advice you would give me?

Try the hint given above. In addition you should open a bug in the  
issue tracker. I'll assign it to Thomas and we'll see if we can set  
this option by default as long as this problem exists.

Cheers,

Gunnar

>
> Andrea
>
> Mail: soliva at comcept.ch
> -----Urspr?ngliche Nachricht-----
> Von: Gunnar Wrobel [mailto:wrobel at pardus.de] Im Auftrag von
> kolab-devel-bounces at kolab.org
> Gesendet: Sonntag, 21. Dezember 2008 23:18
> An: kolab-devel at kolab.org
> Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS
libraries
> were missing or unusable
>
> Quoting ComCept Soliva <soliva at comcept.ch>:
>
>> Hi
>>
>> in RPM/TMP/httpd-2.2.10 there is the config.log.
>>
>> Please find it attached
>
> Thanks, that helped to identify the following conversation:
>
> http://www.mail-archive.com/openpkg-users at openpkg.org/msg03467.html
>
> It might help.
>
> Cheers,
>
> Gunnar
>
>>
>> Andrea
>>
>> Mail: soliva at comcept.ch
>> -----Urspr?ngliche Nachricht-----
>> Von: Gunnar Wrobel [mailto:wrobel at pardus.de] Im Auftrag von
>> kolab-devel-bounces at kolab.org
>> Gesendet: Donnerstag, 18. Dezember 2008 23:50
>> An: kolab-devel at kolab.org
>> Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS
> libraries
>> were missing or unusable
>>
>> Quoting ComCept Soliva <soliva at comcept.ch>:
>>
>>> Hi all
>>>
>>> your modifications within the install-kolab.sh script regarding PLATTAG
>>> seems to work fine.
>>>
>>> All positions regarding mindepth/maxdepth I had to remove because
Solaris
>>> does not support mindepth/maxdepth within find ([Kolab-devel]
>> [issue2924]).
>>>
>>> Before I started I verified that there is nothing at all within tmp and
>>> following env variable are in use:
>>>
>>> SunOS dev 5.10 Generic_137111-08 sun4u sparc SUNW,Ultra-4
>>>
>>> # env
>>>
>>> _=/usr/bin/env
>>> LANG=C
>>> HZ=
>>>
>>
>
PATH=/usr/sbin:/usr/bin:/usr/dt/bin:/usr/openwin/bin:/bin:/usr/ucb:/opt/sfw/
>>> bin:/usr/local/bin:/usr/ccs/bin
>>> HISTFILE=/root/.sh_history
>>> LOGNAME=root
>>> MAIL=/var/mail/root
>>> PS1=[root at dev $PWD]#
>>> SHELL=/sbin/sh
>>> HISTSIZE=200
>>> HOME=/root
>>> TERM=vt100
>>> PWD=/kolabtmp
>>> TZ=MET
>>> ENV=/root/.kshrc
>>>
>>> # crle
>>>
>>> Configuration file [version 4]: /var/ld/ld.config
>>>   Default Library Path (ELF):   /lib:/usr/lib:/usr/local/lib
>>>   Trusted Directories (ELF):    /lib/secure:/usr/lib/secure  (system
>>> default)
>>>
>>>
>>> The compilation stopps within apache regarding SSL/TLS:
>>>
>>> checking whether to enable mod_ssl... checking dependencies
>>> checking for SSL/TLS toolkit base... /kolab
>>>   adding "-R/kolab/lib" to LDFLAGS
>>> checking for OpenSSL version... checking openssl/opensslv.h usability...
>> yes
>>> checking openssl/opensslv.h presence... yes
>>> checking for openssl/opensslv.h... yes
>>> checking openssl/ssl.h usability... yes
>>> checking openssl/ssl.h presence... yes
>>> checking for openssl/ssl.h... yes
>>> OK
>>>   forcing SSL_LIBS to "-lssl -lcrypto"
>>> checking openssl/engine.h usability... yes
>>> checking openssl/engine.h presence... yes
>>> checking for openssl/engine.h... yes
>>> checking for SSLeay_version... yes
>>> checking for SSL_CTX_new... no
>>> checking for ENGINE_init... no
>>> checking for ENGINE_load_builtin_engines... no
>>> checking for SSL_set_cert_store... no
>>> configure: error: ... Error, SSL/TLS libraries were missing or unusable
>>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
>>
>> Is there still a configure.log file available from this step? It
>> should be the unpacked apache source directory.
>>
>> Cheers,
>>
>> Gunnar
>>
>>>
>>>
>>> RPM build errors:
>>>     Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
>>> + exit 1
>>>
>>>
>>>
>>> Full Log File can be downloaeded from following link:
>>>
>>>
> http://www.comcept.ch/kolab2/2.2.1-beta1/kolab-install-Dec-14-08_44_54.zip
>>>
>>> More information about install can be found at:
>>>
>>> http://www.comcept.ch/kolab2/2.2.1-beta1/solaris_10_kolab2_install.txt
>>>
>>>
>>>
>>> OpenSSL was compiled and installed successful:
>>>
>>>
>>> Processing files: openssl-0.9.8g-20080101
>>> Wrote:
/kolab/RPM/PKG/openssl-0.9.8g-20080101.sparc64-solaris10-kolab.rpm
>>> Executing(%clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
>> --posix
>>> -e /kolab/RPM/TMP/rpm-tmp.699
>>> + cd /kolab/RPM/TMP
>>> + cd openssl-0.9.8g
>>> + rm -rf /kolab/RPM/TMP/openssl-0.9.8g-root
>>> + exit 0
>>> Executing(--clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
>>> --posix -e /kolab/RPM/TMP/rpm-tmp.17537
>>> + cd /kolab/RPM/TMP
>>> + rm -rf openssl-0.9.8g
>>> + exit 0
>>> Preparing...
>>> ##################################################
>>> openssl
>>> ##################################################
>>> :::: /tmp/install-kolab....27392/openssl-0.9.8g-20080101.src.rpm = 0
::::
>>>
>>> The library is also there:
>>>
>>> # ls -la /kolab/lib/libssl*
>>> -rw-r--r--   1 kolab    kolab     403268 Dec 14 18:00
/kolab/lib/libssl.a
>>>
>>>
>>>
>>> Within the include dir openssl dir exists:
>>>
>>> # ls -la /kolab/include/openssl
>>> total 1264
>>> drwxr-xr-x   2 kolab    kolab         70 Dec 14 18:02 .
>>> drwxr-xr-x  14 kolab    kolab         41 Dec 14 21:39 ..
>>> -rw-r--r--   1 kolab    kolab       5372 Dec 14 17:59 aes.h
>>> -rw-r--r--   1 kolab    kolab      46728 Dec 14 17:59 asn1.h
>>> -rw-r--r--   1 kolab    kolab      18956 Dec 14 17:59 asn1_mac.h
>>> -rw-r--r--   1 kolab    kolab      27838 Dec 14 17:59 asn1t.h
>>> -rw-r--r--   1 kolab    kolab      30772 Dec 14 17:59 bio.h
>>> -rw-r--r--   1 kolab    kolab       5073 Dec 14 17:59 blowfish.h
>>> -rw-r--r--   1 kolab    kolab      33035 Dec 14 17:59 bn.h
>>> -rw-r--r--   1 kolab    kolab       4565 Dec 14 17:59 buffer.h
>>> -rw-r--r--   1 kolab    kolab       4349 Dec 14 17:59 cast.h
>>> -rw-r--r--   1 kolab    kolab       1601 Dec 14 17:59 comp.h
>>> -rw-r--r--   1 kolab    kolab       9484 Dec 14 17:59 conf.h
>>> -rw-r--r--   1 kolab    kolab       4080 Dec 14 17:59 conf_api.h
>>> -rw-r--r--   1 kolab    kolab      22121 Dec 14 17:59 crypto.h
>>> -rw-r--r--   1 kolab    kolab      10724 Dec 14 17:59 des.h
>>> -rw-r--r--   1 kolab    kolab      18226 Dec 14 17:59 des_old.h
>>> -rw-r--r--   1 kolab    kolab       8372 Dec 14 17:59 dh.h
>>> -rw-r--r--   1 kolab    kolab      10474 Dec 14 17:59 dsa.h
>>> -rw-r--r--   1 kolab    kolab      16252 Dec 14 17:59 dso.h
>>> -rw-r--r--   1 kolab    kolab       6146 Dec 14 17:59 dtls1.h
>>> -rw-r--r--   1 kolab    kolab       9632 Dec 14 17:59 e_os2.h
>>> -rw-r--r--   1 kolab    kolab        540 Dec 14 17:59 ebcdic.h
>>> -rw-r--r--   1 kolab    kolab      21389 Dec 14 17:59 ec.h
>>> -rw-r--r--   1 kolab    kolab       4609 Dec 14 17:59 ecdh.h
>>> -rw-r--r--   1 kolab    kolab      10578 Dec 14 17:59 ecdsa.h
>>> -rw-r--r--   1 kolab    kolab      37839 Dec 14 17:59 engine.h
>>> -rw-r--r--   1 kolab    kolab      12493 Dec 14 17:59 err.h
>>> -rw-r--r--   1 kolab    kolab      35620 Dec 14 17:59 evp.h
>>> -rw-r--r--   1 kolab    kolab       4368 Dec 14 17:59 hmac.h
>>> -rw-r--r--   1 kolab    kolab       7642 Dec 14 17:59 krb5_asn.h
>>> -rw-r--r--   1 kolab    kolab       5927 Dec 14 17:59 kssl.h
>>> -rw-r--r--   1 kolab    kolab       7429 Dec 14 17:59 lhash.h
>>> -rw-r--r--   1 kolab    kolab       3897 Dec 14 17:59 md2.h
>>> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md4.h
>>> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md5.h
>>> -rw-r--r--   1 kolab    kolab     113729 Dec 14 17:59 obj_mac.h
>>> -rw-r--r--   1 kolab    kolab      33396 Dec 14 17:59 objects.h
>>> -rw-r--r--   1 kolab    kolab      23795 Dec 14 17:59 ocsp.h
>>> -rw-r--r--   1 kolab    kolab       6533 Dec 14 17:59 opensslconf.h
>>> -rw-r--r--   1 kolab    kolab       3751 Dec 14 17:59 opensslv.h
>>> -rw-r--r--   1 kolab    kolab       6446 Dec 14 17:59 ossl_typ.h
>>> -rw-r--r--   1 kolab    kolab      27927 Dec 14 17:59 pem.h
>>> -rw-r--r--   1 kolab    kolab       2863 Dec 14 17:59 pem2.h
>>> -rw-r--r--   1 kolab    kolab      12677 Dec 14 17:59 pkcs12.h
>>> -rw-r--r--   1 kolab    kolab      16333 Dec 14 17:59 pkcs7.h
>>> -rw-r--r--   1 kolab    kolab       6150 Dec 14 17:59 pq_compat.h
>>> -rw-r--r--   1 kolab    kolab       3519 Dec 14 17:59 pqueue.h
>>> -rw-r--r--   1 kolab    kolab       5251 Dec 14 17:59 rand.h
>>> -rw-r--r--   1 kolab    kolab       4294 Dec 14 17:59 rc2.h
>>> -rw-r--r--   1 kolab    kolab       3707 Dec 14 17:59 rc4.h
>>> -rw-r--r--   1 kolab    kolab       4284 Dec 14 17:59 ripemd.h
>>> -rw-r--r--   1 kolab    kolab      18202 Dec 14 17:59 rsa.h
>>> -rw-r--r--   1 kolab    kolab     126893 Dec 14 17:59 safestack.h
>>> -rw-r--r--   1 kolab    kolab       7329 Dec 14 17:59 sha.h
>>> -rw-r--r--   1 kolab    kolab      82501 Dec 14 17:59 ssl.h
>>> -rw-r--r--   1 kolab    kolab      10716 Dec 14 17:59 ssl2.h
>>> -rw-r--r--   1 kolab    kolab       3744 Dec 14 17:59 ssl23.h
>>> -rw-r--r--   1 kolab    kolab      22283 Dec 14 17:59 ssl3.h
>>> -rw-r--r--   1 kolab    kolab       4418 Dec 14 17:59 stack.h
>>> -rw-r--r--   1 kolab    kolab      26481 Dec 14 17:59 store.h
>>> -rw-r--r--   1 kolab    kolab      19456 Dec 14 17:59 symhacks.h
>>> -rw-r--r--   1 kolab    kolab      18121 Dec 14 17:59 tls1.h
>>> -rw-r--r--   1 kolab    kolab       4117 Dec 14 17:59 tmdiff.h
>>> -rw-r--r--   1 kolab    kolab       4300 Dec 14 17:59 txt_db.h
>>> -rw-r--r--   1 kolab    kolab      16418 Dec 14 17:59 ui.h
>>> -rw-r--r--   1 kolab    kolab       3439 Dec 14 17:59 ui_compat.h
>>> -rw-r--r--   1 kolab    kolab      47946 Dec 14 17:59 x509.h
>>> -rw-r--r--   1 kolab    kolab      20782 Dec 14 17:59 x509_vfy.h
>>> -rw-r--r--   1 kolab    kolab      29980 Dec 14 17:59 x509v3.h
>>>
>>>
>>> What is going wrong here....? How to proceed.....? If you need more
>>> information please tell me.
>>>
>>> kinde regards
>>>
>>> Andrea Soliva
>>>
>>> Mail: soliva at comcept.ch
>>>
>>> _______________________________________________
>>> Kolab-devel mailing list
>>> Kolab-devel at kolab.org
>>> https://kolab.org/mailman/listinfo/kolab-devel
>>>
>>
>>
>>
>> --
>> ______ 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.
>>
>
>
>
> --
> ______ 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-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



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


From kolab-issues at intevation.de  Mon Dec 29 10:06:27 2008
From: kolab-issues at intevation.de (Gunnar Wrobel)
Date: Mon, 29 Dec 2008 09:06:27 +0000
Subject: [Kolab-devel] [issue3342] The Kolab format does not support the
	state "cancelle" for events
Message-ID: <1230541587.32.0.33539351618.issue3342@intevation.de>


New submission from Gunnar Wrobel <p at rdus.de>:

Horde allows to mark an event as "cancelled". At the same time "free" is also
supported.

The Kolab format only supports "free, tentative, busy, or outofoffice".

I consider "free" to be the best match for the Horde definition of "free" and
"cancelled".

Which now leads to the confusing situation that you set an event to "cancelled"
and it will be marked "free" later.

As I consider "cancelled" a sensible status I think it should be added to the
Kolab format definition.

See also http://bugs.horde.org/ticket/7799

----------
assignedto: bernhard
messages: 18181
nosy: bernhard, thomas, wilde, wrobel
priority: minor bug
status: unread
title: The Kolab format does not support the state "cancelle" for events
topic: format, web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3342>
___________________________________________________


From bernhard at intevation.de  Mon Dec 29 13:32:33 2008
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 29 Dec 2008 13:32:33 +0100
Subject: [Kolab-devel]
	=?iso-8859-15?q?Help_with_getting_email=09working?=
	=?iso-8859-15?q?=3A=09kolab-server-2=2E2=2E1-beta-1?=
In-Reply-To: <20081227120440.19644247b8whyqio@webmail.pardus.de>
References: <54EC12E8D9B4476596228C52EF134C6F@mdmbxp>
	<200812231110.42924.bernhard@intevation.de>
	<20081227120440.19644247b8whyqio@webmail.pardus.de>
Message-ID: <200812291332.37130.bernhard@intevation.de>

On Samstag, 27. Dezember 2008, Gunnar Wrobel wrote:
> Quoting Bernhard Reiter <bernhard at intevation.de>:
> > On Montag, 22. Dezember 2008, Gunnar Wrobel wrote:
> >> > We should update the readme for 2.2.1-beta1, shouldn't we?
> >>
> >> Yes we should if that is possible.
> >
> > Give me the text, I can change it of course. :)
>
> Suggested patch attached.

Thanks. 
I've changed the text on the master in 1st.README now.
And while at it I've also switched to sha1sum for checking
the file integrity.

-- 
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-devel/attachments/20081229/75dd4c7d/attachment.bin

From soliva at comcept.ch  Tue Dec 30 07:56:34 2008
From: soliva at comcept.ch (ComCept Soliva)
Date: Tue, 30 Dec 2008 07:56:34 +0100
Subject: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1 Script stopped
	before OpenPKG install
Message-ID: <EA23DF78ADC646A69BD961758D39B5D1@comcept.ch>

Hi all

this is the first feedback regarding:

"[Kolab-devel] [issue3341] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS
libraries were missing or unusable"

the compilation/installation stopped before openpkg install which means the
files for openpkg are there and was successful compiled but the script did
not install at all anything (I can not see any error?). I launched the
installation manual which means folllowing workaround was used to proceed
(Full Log Details at
http://www.comcept.ch/kolab2/2.2.1-beta1/kolab-install-Dec-29-07_24_22.zip
Full install details at
http://www.comcept.ch/kolab2/2.2.1-beta1/solaris_10_kolab2_install.txt ):

# sh -x install-kolab.sh 2>&1 | tee kolab-install-Dec-29-07_24_22.log


........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
| fixing something) to reinstall (but then with RPM available).
|
|
|
| The third result file is the OpenPKG Binary Bootstrap Package,
|
| containing the installation files as a self-extracting shell
|
| script for the OpenPKG instance /kolab. Use this in YOUR NEXT
|
| STEP to initially create the OpenPKG instance from scratch.
|
| Hence, proceed now by running the following command:
|
|
|
|     $ sh openpkg-20071227-20071227.sparc64-solaris10-kolab.sh
|
+---------------------------------------------------------------------------
--+
+ [  ] 
+ [ -n openpkg-20071227-20071227.sparc64-solaris10-kolab.sh ] 
+ sh openpkg-20071227-20071227.sparc64-solaris10-kolab.sh 
OpenPKG CURRENT Binary Bootstrap Package, version 20071227
Built for prefix /kolab on target platform sparc64-solaris10
++ hooking OpenPKG instance into system environment
ln: rc0.d/K00kolab: File exists
ln: rc1.d/K00kolab: File exists
+ exit 2 

#    

# sh
/tmp/install-kolab....8544/openpkg-20071227-20071227.sparc64-solaris10-kolab
.sh

OpenPKG CURRENT Binary Bootstrap Package, version 20071227
Built for prefix /kolab on target platform sparc64-solaris10
++ hooking OpenPKG instance into system environment
++ fixating OpenPKG instance root directory "/kolab"
++ extracting OpenPKG binary distribution
++ installing OpenPKG binary distribution
++ fixating OpenPKG instance filesystem hierarchy
++ post-processing OpenPKG bootstrap installation
+---------------------------------------------------------------------------
--+
| Congratulations!
|
|
|
| You have successfully installed an OpenPKG CURRENT instance
|
| under prefix /kolab on target platform sparc64-solaris10.
|
|
|
| For details about this OpenPKG instance, run any of the
|
| following typical OpenPKG RPM query commands:
|
|
|
|     $ /kolab/bin/openpkg rpm -qa
|
|     $ /kolab/bin/openpkg rpm -qi  openpkg
|
|     $ /kolab/bin/openpkg rpm -qlv openpkg
|
|
|
| To check the integrity of the entire OpenPKG instance,
|
| run the following OpenPKG RPM verify command:
|
|
|
|     $ /kolab/bin/openpkg rpm -Va
|
|
|
| To install software packages into this OpenPKG instance, run
|
| the following two OpenPKG RPM build commands for each package:
|
|
|
"install-kolab.sh" 317 lines, 10143 characters to/foo-*.src.rpm
|
|     $ /kolab/bin/openpkg rpm -Uvh /kolab/RPM/PKG/foo-*.rpm
|
|
|
| To remove a software package later, just run:
|
|
|
|     $ /kolab/bin/openpkg rpm -e foo
|
|
|
| To remove the whole OpenPKG instance under prefix /kolab,
|
| just remove every package as shown above. As you finally
|
| remove the package "openpkg", the OpenPKG instance itself
|
| will be unlinked from the system and removed as well.
|
|
|
| Thank you for flying OpenPKG...
|
|                                         Ralf S. Engelschall
|
|                                         The OpenPKG Project
|
|                                         openpkg at openpkg.org
|
+---------------------------------------------------------------------------
--+

# /kolab/bin/openpkg rpm -qa
openpkg-20071227-20071227
gpg-pubkey-61b7ae34-4544a6af
gpg-pubkey-63c4cb9f-3c591eda
gpg-pubkey-52197903-4544a74d




ATTENTION Prevent that install script creates another tmpdir or WORKDIR
otherwise 
********* compilation etc will beginn again from scratch. Define as WORKDIR
existing
          WORKDIR in "/tmp":


# vi /kolabtmp/install-kolab.sh


    62  #mktmpdir() {
    63  #  newtmp="${TMPDIR-/tmp}/install-kolab.$RANDOM.$RANDOM.$RANDOM.$$"
    64  #  (umask 022 && mkdir "$newtmp") || {
    65  #    echo "Could not create temporary directory! Exiting." 1>&2
    66  #    exit 1
    67  #  }
    68  #  echo "$newtmp"
    69  #}



   193  SRCDIR=`pwd`
   194  #WORKDIR=`mktmpdir`
   195  WORKDIR="/tmp/install-kolab....8544"
   196  echo "Changing to temporary working directory $WORKDIR ..."
   197  cd "$WORKDIR"
   198  populate_workdir


# sh -x install-kolab.sh 2>&1 | tee kolab-install-Dec-30-07-22-50.log


Will give feedback as soon as the compilation/installation finished...
 
kind regards

Andrea

Mail: soliva at comcept.ch 

-----Urspr?ngliche Nachricht-----
Von: ComCept Soliva [mailto:soliva at comcept.ch] 
Gesendet: Montag, 29. Dezember 2008 07:20
An: 'kolab-devel at kolab.org'
Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS libraries
were missing or unusable

Hi Gunnar

issue open:

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

new compilation running at the moment..will give feedback as soon as I have
a result/overview.

kind regards

Mail: soliva at comcept.ch 
-----Urspr?ngliche Nachricht-----
Von: Gunnar Wrobel [mailto:wrobel at pardus.de] Im Auftrag von
kolab-devel-bounces at kolab.org
Gesendet: Samstag, 27. Dezember 2008 11:55
An: kolab-devel at kolab.org
Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS libraries
were missing or unusable

Quoting ComCept Soliva <soliva at comcept.ch>:

> Hi Gunnar
>
> many thanks to identify the problem. If I run again the compilation it
will
> stop at apache2 compilation and I manipulate the .spec file that within
> apache2 the option zlib will be compiled with_zlib=no. Fine so far but is
> there a possibility to manipulate this in advanced? What would be the best
> choice?

I think it should be possible to set that in install-kolab.sh:

Line 25 -> DEFINE="... -D apache::with_zlib=no"

>
> If there is no possibility is it still the same that If the compilation
> stops --> I manipulation .spec --> start again with install-kolab.sh -->
and
> the compilation will not start from beginn instead it will run at this
point
> it stops? Why I'm asking is because I have to remove on Solaris within
> install-kolab.sh the option "-mindepth 1 -maxdepth 1" (find on Solaris
does
> not support this option)? If I understand the script correct the option
> "-mindepth 1 -maxdepth 1" checks if there is already something within /tmp
> and if so will probably remove the stuff and if so beginn the compilation
at
> scratch?
>
> How should I proceed? What advice you would give me?

Try the hint given above. In addition you should open a bug in the  
issue tracker. I'll assign it to Thomas and we'll see if we can set  
this option by default as long as this problem exists.

Cheers,

Gunnar

>
> Andrea
>
> Mail: soliva at comcept.ch
> -----Urspr?ngliche Nachricht-----
> Von: Gunnar Wrobel [mailto:wrobel at pardus.de] Im Auftrag von
> kolab-devel-bounces at kolab.org
> Gesendet: Sonntag, 21. Dezember 2008 23:18
> An: kolab-devel at kolab.org
> Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS
libraries
> were missing or unusable
>
> Quoting ComCept Soliva <soliva at comcept.ch>:
>
>> Hi
>>
>> in RPM/TMP/httpd-2.2.10 there is the config.log.
>>
>> Please find it attached
>
> Thanks, that helped to identify the following conversation:
>
> http://www.mail-archive.com/openpkg-users at openpkg.org/msg03467.html
>
> It might help.
>
> Cheers,
>
> Gunnar
>
>>
>> Andrea
>>
>> Mail: soliva at comcept.ch
>> -----Urspr?ngliche Nachricht-----
>> Von: Gunnar Wrobel [mailto:wrobel at pardus.de] Im Auftrag von
>> kolab-devel-bounces at kolab.org
>> Gesendet: Donnerstag, 18. Dezember 2008 23:50
>> An: kolab-devel at kolab.org
>> Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS
> libraries
>> were missing or unusable
>>
>> Quoting ComCept Soliva <soliva at comcept.ch>:
>>
>>> Hi all
>>>
>>> your modifications within the install-kolab.sh script regarding PLATTAG
>>> seems to work fine.
>>>
>>> All positions regarding mindepth/maxdepth I had to remove because
Solaris
>>> does not support mindepth/maxdepth within find ([Kolab-devel]
>> [issue2924]).
>>>
>>> Before I started I verified that there is nothing at all within tmp and
>>> following env variable are in use:
>>>
>>> SunOS dev 5.10 Generic_137111-08 sun4u sparc SUNW,Ultra-4
>>>
>>> # env
>>>
>>> _=/usr/bin/env
>>> LANG=C
>>> HZ=
>>>
>>
>
PATH=/usr/sbin:/usr/bin:/usr/dt/bin:/usr/openwin/bin:/bin:/usr/ucb:/opt/sfw/
>>> bin:/usr/local/bin:/usr/ccs/bin
>>> HISTFILE=/root/.sh_history
>>> LOGNAME=root
>>> MAIL=/var/mail/root
>>> PS1=[root at dev $PWD]#
>>> SHELL=/sbin/sh
>>> HISTSIZE=200
>>> HOME=/root
>>> TERM=vt100
>>> PWD=/kolabtmp
>>> TZ=MET
>>> ENV=/root/.kshrc
>>>
>>> # crle
>>>
>>> Configuration file [version 4]: /var/ld/ld.config
>>>   Default Library Path (ELF):   /lib:/usr/lib:/usr/local/lib
>>>   Trusted Directories (ELF):    /lib/secure:/usr/lib/secure  (system
>>> default)
>>>
>>>
>>> The compilation stopps within apache regarding SSL/TLS:
>>>
>>> checking whether to enable mod_ssl... checking dependencies
>>> checking for SSL/TLS toolkit base... /kolab
>>>   adding "-R/kolab/lib" to LDFLAGS
>>> checking for OpenSSL version... checking openssl/opensslv.h usability...
>> yes
>>> checking openssl/opensslv.h presence... yes
>>> checking for openssl/opensslv.h... yes
>>> checking openssl/ssl.h usability... yes
>>> checking openssl/ssl.h presence... yes
>>> checking for openssl/ssl.h... yes
>>> OK
>>>   forcing SSL_LIBS to "-lssl -lcrypto"
>>> checking openssl/engine.h usability... yes
>>> checking openssl/engine.h presence... yes
>>> checking for openssl/engine.h... yes
>>> checking for SSLeay_version... yes
>>> checking for SSL_CTX_new... no
>>> checking for ENGINE_init... no
>>> checking for ENGINE_load_builtin_engines... no
>>> checking for SSL_set_cert_store... no
>>> configure: error: ... Error, SSL/TLS libraries were missing or unusable
>>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
>>
>> Is there still a configure.log file available from this step? It
>> should be the unpacked apache source directory.
>>
>> Cheers,
>>
>> Gunnar
>>
>>>
>>>
>>> RPM build errors:
>>>     Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
>>> + exit 1
>>>
>>>
>>>
>>> Full Log File can be downloaeded from following link:
>>>
>>>
> http://www.comcept.ch/kolab2/2.2.1-beta1/kolab-install-Dec-14-08_44_54.zip
>>>
>>> More information about install can be found at:
>>>
>>> http://www.comcept.ch/kolab2/2.2.1-beta1/solaris_10_kolab2_install.txt
>>>
>>>
>>>
>>> OpenSSL was compiled and installed successful:
>>>
>>>
>>> Processing files: openssl-0.9.8g-20080101
>>> Wrote:
/kolab/RPM/PKG/openssl-0.9.8g-20080101.sparc64-solaris10-kolab.rpm
>>> Executing(%clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
>> --posix
>>> -e /kolab/RPM/TMP/rpm-tmp.699
>>> + cd /kolab/RPM/TMP
>>> + cd openssl-0.9.8g
>>> + rm -rf /kolab/RPM/TMP/openssl-0.9.8g-root
>>> + exit 0
>>> Executing(--clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
>>> --posix -e /kolab/RPM/TMP/rpm-tmp.17537
>>> + cd /kolab/RPM/TMP
>>> + rm -rf openssl-0.9.8g
>>> + exit 0
>>> Preparing...
>>> ##################################################
>>> openssl
>>> ##################################################
>>> :::: /tmp/install-kolab....27392/openssl-0.9.8g-20080101.src.rpm = 0
::::
>>>
>>> The library is also there:
>>>
>>> # ls -la /kolab/lib/libssl*
>>> -rw-r--r--   1 kolab    kolab     403268 Dec 14 18:00
/kolab/lib/libssl.a
>>>
>>>
>>>
>>> Within the include dir openssl dir exists:
>>>
>>> # ls -la /kolab/include/openssl
>>> total 1264
>>> drwxr-xr-x   2 kolab    kolab         70 Dec 14 18:02 .
>>> drwxr-xr-x  14 kolab    kolab         41 Dec 14 21:39 ..
>>> -rw-r--r--   1 kolab    kolab       5372 Dec 14 17:59 aes.h
>>> -rw-r--r--   1 kolab    kolab      46728 Dec 14 17:59 asn1.h
>>> -rw-r--r--   1 kolab    kolab      18956 Dec 14 17:59 asn1_mac.h
>>> -rw-r--r--   1 kolab    kolab      27838 Dec 14 17:59 asn1t.h
>>> -rw-r--r--   1 kolab    kolab      30772 Dec 14 17:59 bio.h
>>> -rw-r--r--   1 kolab    kolab       5073 Dec 14 17:59 blowfish.h
>>> -rw-r--r--   1 kolab    kolab      33035 Dec 14 17:59 bn.h
>>> -rw-r--r--   1 kolab    kolab       4565 Dec 14 17:59 buffer.h
>>> -rw-r--r--   1 kolab    kolab       4349 Dec 14 17:59 cast.h
>>> -rw-r--r--   1 kolab    kolab       1601 Dec 14 17:59 comp.h
>>> -rw-r--r--   1 kolab    kolab       9484 Dec 14 17:59 conf.h
>>> -rw-r--r--   1 kolab    kolab       4080 Dec 14 17:59 conf_api.h
>>> -rw-r--r--   1 kolab    kolab      22121 Dec 14 17:59 crypto.h
>>> -rw-r--r--   1 kolab    kolab      10724 Dec 14 17:59 des.h
>>> -rw-r--r--   1 kolab    kolab      18226 Dec 14 17:59 des_old.h
>>> -rw-r--r--   1 kolab    kolab       8372 Dec 14 17:59 dh.h
>>> -rw-r--r--   1 kolab    kolab      10474 Dec 14 17:59 dsa.h
>>> -rw-r--r--   1 kolab    kolab      16252 Dec 14 17:59 dso.h
>>> -rw-r--r--   1 kolab    kolab       6146 Dec 14 17:59 dtls1.h
>>> -rw-r--r--   1 kolab    kolab       9632 Dec 14 17:59 e_os2.h
>>> -rw-r--r--   1 kolab    kolab        540 Dec 14 17:59 ebcdic.h
>>> -rw-r--r--   1 kolab    kolab      21389 Dec 14 17:59 ec.h
>>> -rw-r--r--   1 kolab    kolab       4609 Dec 14 17:59 ecdh.h
>>> -rw-r--r--   1 kolab    kolab      10578 Dec 14 17:59 ecdsa.h
>>> -rw-r--r--   1 kolab    kolab      37839 Dec 14 17:59 engine.h
>>> -rw-r--r--   1 kolab    kolab      12493 Dec 14 17:59 err.h
>>> -rw-r--r--   1 kolab    kolab      35620 Dec 14 17:59 evp.h
>>> -rw-r--r--   1 kolab    kolab       4368 Dec 14 17:59 hmac.h
>>> -rw-r--r--   1 kolab    kolab       7642 Dec 14 17:59 krb5_asn.h
>>> -rw-r--r--   1 kolab    kolab       5927 Dec 14 17:59 kssl.h
>>> -rw-r--r--   1 kolab    kolab       7429 Dec 14 17:59 lhash.h
>>> -rw-r--r--   1 kolab    kolab       3897 Dec 14 17:59 md2.h
>>> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md4.h
>>> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md5.h
>>> -rw-r--r--   1 kolab    kolab     113729 Dec 14 17:59 obj_mac.h
>>> -rw-r--r--   1 kolab    kolab      33396 Dec 14 17:59 objects.h
>>> -rw-r--r--   1 kolab    kolab      23795 Dec 14 17:59 ocsp.h
>>> -rw-r--r--   1 kolab    kolab       6533 Dec 14 17:59 opensslconf.h
>>> -rw-r--r--   1 kolab    kolab       3751 Dec 14 17:59 opensslv.h
>>> -rw-r--r--   1 kolab    kolab       6446 Dec 14 17:59 ossl_typ.h
>>> -rw-r--r--   1 kolab    kolab      27927 Dec 14 17:59 pem.h
>>> -rw-r--r--   1 kolab    kolab       2863 Dec 14 17:59 pem2.h
>>> -rw-r--r--   1 kolab    kolab      12677 Dec 14 17:59 pkcs12.h
>>> -rw-r--r--   1 kolab    kolab      16333 Dec 14 17:59 pkcs7.h
>>> -rw-r--r--   1 kolab    kolab       6150 Dec 14 17:59 pq_compat.h
>>> -rw-r--r--   1 kolab    kolab       3519 Dec 14 17:59 pqueue.h
>>> -rw-r--r--   1 kolab    kolab       5251 Dec 14 17:59 rand.h
>>> -rw-r--r--   1 kolab    kolab       4294 Dec 14 17:59 rc2.h
>>> -rw-r--r--   1 kolab    kolab       3707 Dec 14 17:59 rc4.h
>>> -rw-r--r--   1 kolab    kolab       4284 Dec 14 17:59 ripemd.h
>>> -rw-r--r--   1 kolab    kolab      18202 Dec 14 17:59 rsa.h
>>> -rw-r--r--   1 kolab    kolab     126893 Dec 14 17:59 safestack.h
>>> -rw-r--r--   1 kolab    kolab       7329 Dec 14 17:59 sha.h
>>> -rw-r--r--   1 kolab    kolab      82501 Dec 14 17:59 ssl.h
>>> -rw-r--r--   1 kolab    kolab      10716 Dec 14 17:59 ssl2.h
>>> -rw-r--r--   1 kolab    kolab       3744 Dec 14 17:59 ssl23.h
>>> -rw-r--r--   1 kolab    kolab      22283 Dec 14 17:59 ssl3.h
>>> -rw-r--r--   1 kolab    kolab       4418 Dec 14 17:59 stack.h
>>> -rw-r--r--   1 kolab    kolab      26481 Dec 14 17:59 store.h
>>> -rw-r--r--   1 kolab    kolab      19456 Dec 14 17:59 symhacks.h
>>> -rw-r--r--   1 kolab    kolab      18121 Dec 14 17:59 tls1.h
>>> -rw-r--r--   1 kolab    kolab       4117 Dec 14 17:59 tmdiff.h
>>> -rw-r--r--   1 kolab    kolab       4300 Dec 14 17:59 txt_db.h
>>> -rw-r--r--   1 kolab    kolab      16418 Dec 14 17:59 ui.h
>>> -rw-r--r--   1 kolab    kolab       3439 Dec 14 17:59 ui_compat.h
>>> -rw-r--r--   1 kolab    kolab      47946 Dec 14 17:59 x509.h
>>> -rw-r--r--   1 kolab    kolab      20782 Dec 14 17:59 x509_vfy.h
>>> -rw-r--r--   1 kolab    kolab      29980 Dec 14 17:59 x509v3.h
>>>
>>>
>>> What is going wrong here....? How to proceed.....? If you need more
>>> information please tell me.
>>>
>>> kinde regards
>>>
>>> Andrea Soliva
>>>
>>> Mail: soliva at comcept.ch
>>>
>>> _______________________________________________
>>> Kolab-devel mailing list
>>> Kolab-devel at kolab.org
>>> https://kolab.org/mailman/listinfo/kolab-devel
>>>
>>
>>
>>
>> --
>> ______ 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.
>>
>
>
>
> --
> ______ 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-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



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


From soliva at comcept.ch  Wed Dec 31 09:42:56 2008
From: soliva at comcept.ch (ComCept Soliva)
Date: Wed, 31 Dec 2008 09:42:56 +0100
Subject: [Kolab-devel] [issue3341] Solaris 10 Sparc Kolab V2.2.1 Beta
	1SSL/TLS libraries were missing or unusable
References: <9268C7D7C7AB4CDCBF0DCE7A201F33F9@comcept.ch><20081218235001.69731dnw12732e9w@webmail.pardus.de><E96DBF20E3D046079698C8804C040486@comcept.ch><20081221231734.58874cp3kwclwpz4@webmail.pardus.de><071079DF0B324333A4F3E68B37A7A046@comcept.ch>
	<20081227115445.11314omit5dq7m2o@webmail.pardus.de> 
Message-ID: <3FC4C23517694A6BBEBD3468BF79C6F1@comcept.ch>

Hi Gunnar

the workaround to exclude zlib within apache compilation within
install-kolab.sh does not work (install-kolab.sh fails at the exact same
point and way):

DEFINE="-D openldap::with_pth=no -D sasl::with_ldap -D sasl::with_login -D
sasl::with_ntlm -D postfix::with_sasl -D postfix::with_ssl -D
postfix::with_ldap -D imapd::with_kolab_nocaps -D apache::with_zlib=no"

I manipulated the apache.spec file manually (--without-zlib) and started
apache configuration/compilation manually.

# vi /kolab/RPM/SRC/apache/apache.spec

    ./configure \
        --without-zlib \


The installation from apache was successful. I updated the documentation and
will proceed with the installation:

http://www.comcept.ch/kolab2/2.2.1-beta1/solaris_10_kolab2_install.txt
http://www.comcept.ch/kolab2/2.2.1-beta1/kolab-install-Dec-30-07-22-50.zip

Happy New Year and all the best.

Andrea

Mail: soliva at comcept.ch 
-----Urspr?ngliche Nachricht-----
Von: ComCept Soliva [mailto:soliva at comcept.ch] 
Gesendet: Montag, 29. Dezember 2008 07:20
An: 'kolab-devel at kolab.org'
Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS libraries
were missing or unusable

Hi Gunnar

issue open:

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

new compilation running at the moment..will give feedback as soon as I have
a result/overview.

kind regards

Mail: soliva at comcept.ch 
-----Urspr?ngliche Nachricht-----
Von: Gunnar Wrobel [mailto:wrobel at pardus.de] Im Auftrag von
kolab-devel-bounces at kolab.org
Gesendet: Samstag, 27. Dezember 2008 11:55
An: kolab-devel at kolab.org
Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS libraries
were missing or unusable

Quoting ComCept Soliva <soliva at comcept.ch>:

> Hi Gunnar
>
> many thanks to identify the problem. If I run again the compilation it
will
> stop at apache2 compilation and I manipulate the .spec file that within
> apache2 the option zlib will be compiled with_zlib=no. Fine so far but is
> there a possibility to manipulate this in advanced? What would be the best
> choice?

I think it should be possible to set that in install-kolab.sh:

Line 25 -> DEFINE="... -D apache::with_zlib=no"

>
> If there is no possibility is it still the same that If the compilation
> stops --> I manipulation .spec --> start again with install-kolab.sh -->
and
> the compilation will not start from beginn instead it will run at this
point
> it stops? Why I'm asking is because I have to remove on Solaris within
> install-kolab.sh the option "-mindepth 1 -maxdepth 1" (find on Solaris
does
> not support this option)? If I understand the script correct the option
> "-mindepth 1 -maxdepth 1" checks if there is already something within /tmp
> and if so will probably remove the stuff and if so beginn the compilation
at
> scratch?
>
> How should I proceed? What advice you would give me?

Try the hint given above. In addition you should open a bug in the  
issue tracker. I'll assign it to Thomas and we'll see if we can set  
this option by default as long as this problem exists.

Cheers,

Gunnar

>
> Andrea
>
> Mail: soliva at comcept.ch
> -----Urspr?ngliche Nachricht-----
> Von: Gunnar Wrobel [mailto:wrobel at pardus.de] Im Auftrag von
> kolab-devel-bounces at kolab.org
> Gesendet: Sonntag, 21. Dezember 2008 23:18
> An: kolab-devel at kolab.org
> Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS
libraries
> were missing or unusable
>
> Quoting ComCept Soliva <soliva at comcept.ch>:
>
>> Hi
>>
>> in RPM/TMP/httpd-2.2.10 there is the config.log.
>>
>> Please find it attached
>
> Thanks, that helped to identify the following conversation:
>
> http://www.mail-archive.com/openpkg-users at openpkg.org/msg03467.html
>
> It might help.
>
> Cheers,
>
> Gunnar
>
>>
>> Andrea
>>
>> Mail: soliva at comcept.ch
>> -----Urspr?ngliche Nachricht-----
>> Von: Gunnar Wrobel [mailto:wrobel at pardus.de] Im Auftrag von
>> kolab-devel-bounces at kolab.org
>> Gesendet: Donnerstag, 18. Dezember 2008 23:50
>> An: kolab-devel at kolab.org
>> Betreff: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1SSL/TLS
> libraries
>> were missing or unusable
>>
>> Quoting ComCept Soliva <soliva at comcept.ch>:
>>
>>> Hi all
>>>
>>> your modifications within the install-kolab.sh script regarding PLATTAG
>>> seems to work fine.
>>>
>>> All positions regarding mindepth/maxdepth I had to remove because
Solaris
>>> does not support mindepth/maxdepth within find ([Kolab-devel]
>> [issue2924]).
>>>
>>> Before I started I verified that there is nothing at all within tmp and
>>> following env variable are in use:
>>>
>>> SunOS dev 5.10 Generic_137111-08 sun4u sparc SUNW,Ultra-4
>>>
>>> # env
>>>
>>> _=/usr/bin/env
>>> LANG=C
>>> HZ=
>>>
>>
>
PATH=/usr/sbin:/usr/bin:/usr/dt/bin:/usr/openwin/bin:/bin:/usr/ucb:/opt/sfw/
>>> bin:/usr/local/bin:/usr/ccs/bin
>>> HISTFILE=/root/.sh_history
>>> LOGNAME=root
>>> MAIL=/var/mail/root
>>> PS1=[root at dev $PWD]#
>>> SHELL=/sbin/sh
>>> HISTSIZE=200
>>> HOME=/root
>>> TERM=vt100
>>> PWD=/kolabtmp
>>> TZ=MET
>>> ENV=/root/.kshrc
>>>
>>> # crle
>>>
>>> Configuration file [version 4]: /var/ld/ld.config
>>>   Default Library Path (ELF):   /lib:/usr/lib:/usr/local/lib
>>>   Trusted Directories (ELF):    /lib/secure:/usr/lib/secure  (system
>>> default)
>>>
>>>
>>> The compilation stopps within apache regarding SSL/TLS:
>>>
>>> checking whether to enable mod_ssl... checking dependencies
>>> checking for SSL/TLS toolkit base... /kolab
>>>   adding "-R/kolab/lib" to LDFLAGS
>>> checking for OpenSSL version... checking openssl/opensslv.h usability...
>> yes
>>> checking openssl/opensslv.h presence... yes
>>> checking for openssl/opensslv.h... yes
>>> checking openssl/ssl.h usability... yes
>>> checking openssl/ssl.h presence... yes
>>> checking for openssl/ssl.h... yes
>>> OK
>>>   forcing SSL_LIBS to "-lssl -lcrypto"
>>> checking openssl/engine.h usability... yes
>>> checking openssl/engine.h presence... yes
>>> checking for openssl/engine.h... yes
>>> checking for SSLeay_version... yes
>>> checking for SSL_CTX_new... no
>>> checking for ENGINE_init... no
>>> checking for ENGINE_load_builtin_engines... no
>>> checking for SSL_set_cert_store... no
>>> configure: error: ... Error, SSL/TLS libraries were missing or unusable
>>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
>>
>> Is there still a configure.log file available from this step? It
>> should be the unpacked apache source directory.
>>
>> Cheers,
>>
>> Gunnar
>>
>>>
>>>
>>> RPM build errors:
>>>     Bad exit status from /kolab/RPM/TMP/rpm-tmp.9292 (%build)
>>> + exit 1
>>>
>>>
>>>
>>> Full Log File can be downloaeded from following link:
>>>
>>>
> http://www.comcept.ch/kolab2/2.2.1-beta1/kolab-install-Dec-14-08_44_54.zip
>>>
>>> More information about install can be found at:
>>>
>>> http://www.comcept.ch/kolab2/2.2.1-beta1/solaris_10_kolab2_install.txt
>>>
>>>
>>>
>>> OpenSSL was compiled and installed successful:
>>>
>>>
>>> Processing files: openssl-0.9.8g-20080101
>>> Wrote:
/kolab/RPM/PKG/openssl-0.9.8g-20080101.sparc64-solaris10-kolab.rpm
>>> Executing(%clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
>> --posix
>>> -e /kolab/RPM/TMP/rpm-tmp.699
>>> + cd /kolab/RPM/TMP
>>> + cd openssl-0.9.8g
>>> + rm -rf /kolab/RPM/TMP/openssl-0.9.8g-root
>>> + exit 0
>>> Executing(--clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
>>> --posix -e /kolab/RPM/TMP/rpm-tmp.17537
>>> + cd /kolab/RPM/TMP
>>> + rm -rf openssl-0.9.8g
>>> + exit 0
>>> Preparing...
>>> ##################################################
>>> openssl
>>> ##################################################
>>> :::: /tmp/install-kolab....27392/openssl-0.9.8g-20080101.src.rpm = 0
::::
>>>
>>> The library is also there:
>>>
>>> # ls -la /kolab/lib/libssl*
>>> -rw-r--r--   1 kolab    kolab     403268 Dec 14 18:00
/kolab/lib/libssl.a
>>>
>>>
>>>
>>> Within the include dir openssl dir exists:
>>>
>>> # ls -la /kolab/include/openssl
>>> total 1264
>>> drwxr-xr-x   2 kolab    kolab         70 Dec 14 18:02 .
>>> drwxr-xr-x  14 kolab    kolab         41 Dec 14 21:39 ..
>>> -rw-r--r--   1 kolab    kolab       5372 Dec 14 17:59 aes.h
>>> -rw-r--r--   1 kolab    kolab      46728 Dec 14 17:59 asn1.h
>>> -rw-r--r--   1 kolab    kolab      18956 Dec 14 17:59 asn1_mac.h
>>> -rw-r--r--   1 kolab    kolab      27838 Dec 14 17:59 asn1t.h
>>> -rw-r--r--   1 kolab    kolab      30772 Dec 14 17:59 bio.h
>>> -rw-r--r--   1 kolab    kolab       5073 Dec 14 17:59 blowfish.h
>>> -rw-r--r--   1 kolab    kolab      33035 Dec 14 17:59 bn.h
>>> -rw-r--r--   1 kolab    kolab       4565 Dec 14 17:59 buffer.h
>>> -rw-r--r--   1 kolab    kolab       4349 Dec 14 17:59 cast.h
>>> -rw-r--r--   1 kolab    kolab       1601 Dec 14 17:59 comp.h
>>> -rw-r--r--   1 kolab    kolab       9484 Dec 14 17:59 conf.h
>>> -rw-r--r--   1 kolab    kolab       4080 Dec 14 17:59 conf_api.h
>>> -rw-r--r--   1 kolab    kolab      22121 Dec 14 17:59 crypto.h
>>> -rw-r--r--   1 kolab    kolab      10724 Dec 14 17:59 des.h
>>> -rw-r--r--   1 kolab    kolab      18226 Dec 14 17:59 des_old.h
>>> -rw-r--r--   1 kolab    kolab       8372 Dec 14 17:59 dh.h
>>> -rw-r--r--   1 kolab    kolab      10474 Dec 14 17:59 dsa.h
>>> -rw-r--r--   1 kolab    kolab      16252 Dec 14 17:59 dso.h
>>> -rw-r--r--   1 kolab    kolab       6146 Dec 14 17:59 dtls1.h
>>> -rw-r--r--   1 kolab    kolab       9632 Dec 14 17:59 e_os2.h
>>> -rw-r--r--   1 kolab    kolab        540 Dec 14 17:59 ebcdic.h
>>> -rw-r--r--   1 kolab    kolab      21389 Dec 14 17:59 ec.h
>>> -rw-r--r--   1 kolab    kolab       4609 Dec 14 17:59 ecdh.h
>>> -rw-r--r--   1 kolab    kolab      10578 Dec 14 17:59 ecdsa.h
>>> -rw-r--r--   1 kolab    kolab      37839 Dec 14 17:59 engine.h
>>> -rw-r--r--   1 kolab    kolab      12493 Dec 14 17:59 err.h
>>> -rw-r--r--   1 kolab    kolab      35620 Dec 14 17:59 evp.h
>>> -rw-r--r--   1 kolab    kolab       4368 Dec 14 17:59 hmac.h
>>> -rw-r--r--   1 kolab    kolab       7642 Dec 14 17:59 krb5_asn.h
>>> -rw-r--r--   1 kolab    kolab       5927 Dec 14 17:59 kssl.h
>>> -rw-r--r--   1 kolab    kolab       7429 Dec 14 17:59 lhash.h
>>> -rw-r--r--   1 kolab    kolab       3897 Dec 14 17:59 md2.h
>>> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md4.h
>>> -rw-r--r--   1 kolab    kolab       4661 Dec 14 17:59 md5.h
>>> -rw-r--r--   1 kolab    kolab     113729 Dec 14 17:59 obj_mac.h
>>> -rw-r--r--   1 kolab    kolab      33396 Dec 14 17:59 objects.h
>>> -rw-r--r--   1 kolab    kolab      23795 Dec 14 17:59 ocsp.h
>>> -rw-r--r--   1 kolab    kolab       6533 Dec 14 17:59 opensslconf.h
>>> -rw-r--r--   1 kolab    kolab       3751 Dec 14 17:59 opensslv.h
>>> -rw-r--r--   1 kolab    kolab       6446 Dec 14 17:59 ossl_typ.h
>>> -rw-r--r--   1 kolab    kolab      27927 Dec 14 17:59 pem.h
>>> -rw-r--r--   1 kolab    kolab       2863 Dec 14 17:59 pem2.h
>>> -rw-r--r--   1 kolab    kolab      12677 Dec 14 17:59 pkcs12.h
>>> -rw-r--r--   1 kolab    kolab      16333 Dec 14 17:59 pkcs7.h
>>> -rw-r--r--   1 kolab    kolab       6150 Dec 14 17:59 pq_compat.h
>>> -rw-r--r--   1 kolab    kolab       3519 Dec 14 17:59 pqueue.h
>>> -rw-r--r--   1 kolab    kolab       5251 Dec 14 17:59 rand.h
>>> -rw-r--r--   1 kolab    kolab       4294 Dec 14 17:59 rc2.h
>>> -rw-r--r--   1 kolab    kolab       3707 Dec 14 17:59 rc4.h
>>> -rw-r--r--   1 kolab    kolab       4284 Dec 14 17:59 ripemd.h
>>> -rw-r--r--   1 kolab    kolab      18202 Dec 14 17:59 rsa.h
>>> -rw-r--r--   1 kolab    kolab     126893 Dec 14 17:59 safestack.h
>>> -rw-r--r--   1 kolab    kolab       7329 Dec 14 17:59 sha.h
>>> -rw-r--r--   1 kolab    kolab      82501 Dec 14 17:59 ssl.h
>>> -rw-r--r--   1 kolab    kolab      10716 Dec 14 17:59 ssl2.h
>>> -rw-r--r--   1 kolab    kolab       3744 Dec 14 17:59 ssl23.h
>>> -rw-r--r--   1 kolab    kolab      22283 Dec 14 17:59 ssl3.h
>>> -rw-r--r--   1 kolab    kolab       4418 Dec 14 17:59 stack.h
>>> -rw-r--r--   1 kolab    kolab      26481 Dec 14 17:59 store.h
>>> -rw-r--r--   1 kolab    kolab      19456 Dec 14 17:59 symhacks.h
>>> -rw-r--r--   1 kolab    kolab      18121 Dec 14 17:59 tls1.h
>>> -rw-r--r--   1 kolab    kolab       4117 Dec 14 17:59 tmdiff.h
>>> -rw-r--r--   1 kolab    kolab       4300 Dec 14 17:59 txt_db.h
>>> -rw-r--r--   1 kolab    kolab      16418 Dec 14 17:59 ui.h
>>> -rw-r--r--   1 kolab    kolab       3439 Dec 14 17:59 ui_compat.h
>>> -rw-r--r--   1 kolab    kolab      47946 Dec 14 17:59 x509.h
>>> -rw-r--r--   1 kolab    kolab      20782 Dec 14 17:59 x509_vfy.h
>>> -rw-r--r--   1 kolab    kolab      29980 Dec 14 17:59 x509v3.h
>>>
>>>
>>> What is going wrong here....? How to proceed.....? If you need more
>>> information please tell me.
>>>
>>> kinde regards
>>>
>>> Andrea Soliva
>>>
>>> Mail: soliva at comcept.ch
>>>
>>> _______________________________________________
>>> Kolab-devel mailing list
>>> Kolab-devel at kolab.org
>>> https://kolab.org/mailman/listinfo/kolab-devel
>>>
>>
>>
>>
>> --
>> ______ 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.
>>
>
>
>
> --
> ______ 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-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



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


From soliva at comcept.ch  Wed Dec 31 10:24:25 2008
From: soliva at comcept.ch (ComCept Soliva)
Date: Wed, 31 Dec 2008 10:24:25 +0100
Subject: [Kolab-devel]  Solaris 10 Sparc Kolab V2.2.1 Beta 1 db4 not found
Message-ID: <D7E1E2868F9A4302AED632FE60B9BF29@comcept.ch>

Hi all

proceeded as mentioned but installation fails again with old issue
[issue1809]:


checking if we should use cURL for url streams... no
checking size of long... (cached) 4
checking size of int... (cached) 4
checking for int32_t... yes
checking for uint32_t... yes
checking for sys/types.h... (cached) yes
checking for inttypes.h... (cached) yes
checking for stdint.h... (cached) yes
checking for string.h... (cached) yes
checking for stdlib.h... (cached) yes
checking for strtoll... yes
checking for atoll... yes
checking for strftime... (cached) yes
checking for QDBM support... no
checking for GDBM support... no
checking for NDBM support... no
checking for db4 major version... configure: error: Header contains
different version
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.12696 (%build)

RPM build errors:
    Bad exit status from /kolab/RPM/TMP/rpm-tmp.12696 (%build)
+ exit 1 


ATTENTION DB4 can not be recognized because of not correct recognized
headers.
********* Manipulate the db4 spec file (changed only from "--disable-shared 
          to enable-shared=yes" ) manually and proceed to install db4
manually:

/kolab/bin/openpkg rpm -iv
/tmp/install-kolab....8544/db-4.5.20.2-20070628.src.rpm

-------------------- output /kolab/bin/openpkg --------------------

db-4.5.20.2-20070628

-------------------- output /kolab/bin/openpkg --------------------


# vi /kolab/RPM/SRC/db/db.spec

-------------------- /kolab/RPM/SRC/db/db.spec --------------------

%endif
        --disable-java \
        --with-mutex="$mutex" \
        --enable-shared=yes

-------------------- /kolab/RPM/SRC/db/db.spec --------------------

# opa /kolab

# /kolab/bin/openpkg rpmbuild -bb /kolab/RPM/SRC/db/db.spec

# /kolab/bin/openpkg rpm --force -Uvh
/kolab/RPM/PKG/db-4.5.20.2-20070628.sparc64-solaris10-kolab.rpm


# ls -la /kolab/include/db*
-r--r--r--   1 kolab      102110 Dec 31 10:11 /kolab/include/db.h

# ls -la /kolab/lib/libdb*
-rw-r--r--   1 kolab         797 Dec 31 10:17 /kolab/lib/libdb-4.5.la
-rwxr-xr-x   1 kolab     1107337 Dec 31 10:17 /kolab/lib/libdb-4.5.so
lrwxrwxrwx   1 kolab          12 Dec 31 10:18 /kolab/lib/libdb-4.so ->
libdb-4.5.so
-rw-r--r--   1 kolab     1451450 Dec 31 10:17 /kolab/lib/libdb.a
lrwxrwxrwx   1 kolab          12 Dec 31 10:18 /kolab/lib/libdb.so ->
libdb-4.5.so

Used the known workaround and proceeded. Updated documentation:

http://www.comcept.ch/kolab2/2.2.1-beta1/solaris_10_kolab2_install.txt
http://www.comcept.ch/kolab2/2.2.1-beta1/kolab-install-Dec-31-09-36-14.zip

kind regards

Andrea

Mail: soliva at comcept.ch 


From soliva at comcept.ch  Wed Dec 31 15:37:08 2008
From: soliva at comcept.ch (ComCept Soliva)
Date: Wed, 31 Dec 2008 15:37:08 +0100
Subject: [Kolab-devel] Solaris 10 Sparc Kolab V2.2.1 Beta 1
	PEAR-Horde-Channel-1.0 find: cannot follow symbolic link
Message-ID: <F095FCE31D23483AA7CA445E013F429E@comcept.ch>

Hi Gunnar

the install-kolab.sh failed again also with a old issue for
PEAR-Horde-Channel-1.0 (I think I saw already this issue). I have no idea
how to proceed? Any suggestion? 

Log is available
http://www.comcept.ch/kolab2/2.2.1-beta1/kolab-install-Dec-31-10-14-54.zip:



:::: /tmp/install-kolab....8544/PEAR-Horde-Channel-1.0-20081210.src.rpm ::::
Installing
/tmp/install-kolab....8544/PEAR-Horde-Channel-1.0-20081210.src.rpm
Executing(%prep): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix
-e /kolab/RPM/TMP/rpm-tmp.6248
+ cd /kolab/RPM/TMP
+ set +x
+----------------------------------Warning----------------------------------
--+
| This OpenPKG package is of class JUNK.
|
| This means it is still in DEVELOPMENT state.
|
| Hence it is still NOT ready even for general evaluation.
|
| Do not use it at all, except in development environments!
|
| It is definitely unstable and incompletely packaged.
|
+---------------------------------------------------------------------------
--+
+ cd /kolab/RPM/TMP
+ rm -rf PEAR-Horde-Channel-1.0
+ /kolab/lib/openpkg/shtool mkdir -f -p -m 755 PEAR-Horde-Channel-1.0
+ cd PEAR-Horde-Channel-1.0
+ exit 0
Executing(%build): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix
-e /kolab/RPM/TMP/rpm-tmp.6248
+ cd /kolab/RPM/TMP
+ cd PEAR-Horde-Channel-1.0
+ exit 0
Executing(%install): env -i /kolab/lib/openpkg/bash --norc --noprofile
--posix -e /kolab/RPM/TMP/rpm-tmp.6248
+ cd /kolab/RPM/TMP
+ cd PEAR-Horde-Channel-1.0
+ rm -rf /kolab/RPM/TMP/PEAR-Horde-Channel-1.0-root
+ mkdir -p /kolab/RPM/TMP/PEAR-Horde-Channel-1.0-root/kolab/var/pear
+ install -pm 644 /kolab/RPM/SRC/PEAR-Horde-Channel/channel.xml
/kolab/RPM/TMP/PEAR-Horde-Channel-1.0-root/kolab/var/pear/pear.horde.org.xml
find: stat() error 644: No such file or directory
find: stat() error
/kolab/RPM/TMP/PEAR-Horde-Channel-1.0-root/kolab/var/pear/pear.horde.org.xml
: No such file or directory
find: cannot read dir /etc/inet/secret: Permission denied
find: cannot read dir /etc/flash/postcreation: Permission denied
find: cannot read dir /etc/flash/precreation: Permission denied
find: cannot read dir /etc/flash/preexit: Permission denied
find: cannot follow symbolic link /usr/lib/llib-lgen: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lnvpair.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ltermlib: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lsec.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lumem: No such file or
directory
find: cannot follow symbolic link /usr/lib/libmeta.so.1: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lsendfile: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lsendfile.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/llib-lrtld_db.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lresolv.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lsec: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-luuid: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lrt.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ldoor: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lposix4: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lrt: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lscf.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lcurses: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lrtld_db.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-lrt.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lcurses.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-lefi.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lcontract.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/64/llib-lintl.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-laio.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-ldevid.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-ltermcap: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lpam.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lelf.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-ltsnet.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-lthread_db.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/64/llib-ltermlib.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-lpthread.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-ldl.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lgen.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lctf.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lthread.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-ltermlib: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-ldevice.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-lposix4.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-lscf.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lkstat.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-lsendfile.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/64/llib-lsocket.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-lc.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lsec.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-ldoor.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lsecdb.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-ltsol.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lumem.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lsysevent.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/64/llib-lbsm.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-ladm.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-ldevinfo.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-lnsl.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-ltermcap.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-lnvpair.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-lmd5.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lxnet.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lcmd.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/64/llib-lresolv.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/64/llib-luuid.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lc.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lnsl.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ltermcap: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lc: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lcmd.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lsysevent.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/llib-lmd5.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lintl: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lsecdb.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lpthread.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ltermlib.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lbsm.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lsocket: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ldevinfo: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lkstat.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ladm.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lintl.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lsecdb: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lsocket.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ldl.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lsysevent: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lctf: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lcontract: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lposix4.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lxnet.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lrtld_db: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ldevice.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lcontract.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/llib-luuid.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ladm: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ldevice: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lkstat: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lthread.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lcurses: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lthread_db: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lumem.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lefi.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lscf: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-laio.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lefi: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ltsnet.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ldevid.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lgen.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lpthread: No such file or
directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lcurses: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lrtld_db.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lrt.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lcurses.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lefi.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lcontract.ln: No
such file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lintl.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-laio.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-ldevid.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-ltermcap: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lpam.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lelf.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-ltsnet.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lthread_db.ln: No
such file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-ltermlib.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lpthread.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-ldl.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lgen.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lctf.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lthread.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-ltermlib: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-ldevice.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lposix4.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lscf.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lkstat.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lsendfile.ln: No
such file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lsocket.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lc.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lsec.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-ldoor.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lsecdb.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-ltsol.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lumem.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lsysevent.ln: No
such file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lbsm.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-ladm.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-ldevinfo.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lnsl.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-ltermcap.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lnvpair.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lmd5.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lxnet.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lcmd.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-lresolv.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/sparcv9/llib-luuid.ln: No such
file or directory
find: cannot follow symbolic link /usr/lib/llib-lelf: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lctf.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ltsol.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lbsm: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lthread: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lthread_db.ln: No such file
or directory
find: cannot follow symbolic link /usr/lib/llib-ldoor.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ldevid: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ldevinfo.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/libmeta.so: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ltermcap.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-laio: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lelf.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lpam.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lcurses.ln: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lnvpair: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lmd5: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lnsl: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lcmd: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lpam: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lresolv: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-lxnet: No such file or
directory
find: cannot follow symbolic link /usr/lib/llib-ldl: No such file or
directory
install: -pm was not found anywhere!
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.6248 (%install)


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


kind regards

Andrea



Mail: soliva at comcept.ch 


From bogus@does.not.exist.com  Tue Dec 30 07:56:46 2008
From: bogus@does.not.exist.com ()
Date: Tue, 30 Dec 2008 06:56:46 -0000
Subject: No subject
Message-ID: <mailman.0.1231417042.2110.kolab-devel@kolab.org>

solve
the issue because for some reason it breaks or excludes the ssl =
compilation.

Any idea.....=20

kind regards

Andrea Soliva

Mail: soliva at comcept.ch=20
-----Urspr=FCngliche Nachricht-----
Von: Gunnar Wrobel [mailto:kolab-issues at intevation.de]=20
Gesendet: Mittwoch, 7. Januar 2009 20:37
An: soliva at comcept.ch; thomas at intevation.de; wilde at intevation.de
Betreff: [issue3341] Solaris 10 Sparc Kolab V2.2.1 Beta 1 SSL/TLS =
libraries
were missing or unusable


Gunnar Wrobel <p at rdus.de> added the comment:

Thanks for the report. Assigning to Thomas for the decision if this can =
be a
default setting.

----------
assignedto:  -> thomas
nosy: +thomas, wilde, wrobel
priority:  -> bug
status: unread -> chatting
topic: +server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3341>
___________________________________________________