From aspineux at gmail.com  Sun Feb  1 10:38:29 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Sun, 1 Feb 2009 10:38:29 +0100
Subject: [Kolab-devel] kolab 2.2.1beta -- apache+php+mysql+memcached
In-Reply-To: <20090131220858.4adff91if4swo4kw@ox.thomasbaumann.com>
References: <20090131220858.4adff91if4swo4kw@ox.thomasbaumann.com>
Message-ID: <71fe4e760902010138s2c6ef64doc2bd6ff7def43e48@mail.gmail.com>

On Sat, Jan 31, 2009 at 10:08 PM, Thomas Baumann <tom at thomasbaumann.com> wrote:
> Hello list,
>
> I tried to get PHP5 working with mysql but I didnt succeed.
>
> I succeeded in rebuild mysql to mysql-5.1.30-20090102.ix86-debian4.0-kolab.rpm
> (taken from openpkg).
> I succeeded in rebuild libevent-1.4.9-20081222.ix86-debian4.0-kolab.rpm and
> memcached-1.3.0-20090130.ix86-debian4.0-kolab.rpm to get all dependencies
> to my php.src.rpm
>
> I did a
>
> /kolab/bin/openpkg rpm -ivh php-5.2.8-20081209_kolab.src.rpm
>
> went to
>
> cd /kolab/RPM/SRC/php
>
> and tried to recompile with
>
>  /kolab/bin/openpkg rpm -ba --define 'with_mysql yes' \
>        --define 'with_pecl_memcache yes'  php.spec

The command looks correct !

Usually, I skip the rpm -i and use a rpm --build like this :

/kolab/bin/openpkg rpm --rebuild \
       php-5.2.8-20081209_kolab.src.rpm \
       --define 'with_mysql yes' \
       --define 'with_pecl_memcache yes'  php.spec

Did you install mysql first, before to build your php package ?

I tried it myself, with mysql installed, but get this :

# /kolab/bin/openpkg rpm --rebuild
/s0/emailgency/kolab_src/php-5.2.6-20080514_kolab.src.rpm --define
'with_mysql yes' --define 'with_mysql yes'
......
checking for specified location of the MySQL UNIX socket... no
checking for MySQL UNIX socket location... no
checking for mysql_close in -lmysqlclient... no
checking for mysql_error in -lmysqlclient... no
configure: error: mysql configure failed. Please check config.log for
more information.
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.71712 (%build)

Hope this give you some ideas


>
> But the result was a installable rpm-file, but it lacks on
> mysql and pecl-memcache support.
>
> What is going wrong - or what do i have to type to get
> a RPM-file with all support as in the original but additional with
> mysql and memcache support ?
>
> The compile log is visible on
>
> http://inhalt.serviert.de/ -->
> http://inhalt.serviert.de/wissen/migration/kolab-2.2-beta-unter-debian-etch ->
> php_recompile
>
> Thanks for your reply in advance.
>
> Thomas.
>
> --
> Thomas Baumann
>
> B?cher und mehr im Internet - meine neue Site: http://www.1-search.de
> - Viel Spass!
>
> ----------------------------------------------------------------
> 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
>



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


From tom at thomasbaumann.com  Sun Feb  1 22:33:15 2009
From: tom at thomasbaumann.com (Thomas Baumann)
Date: Sun, 01 Feb 2009 22:33:15 +0100
Subject: [Kolab-devel] kolab 2.2.1beta -- apache+php+mysql+memcached
In-Reply-To: <71fe4e760902010138s2c6ef64doc2bd6ff7def43e48@mail.gmail.com>
References: <20090131220858.4adff91if4swo4kw@ox.thomasbaumann.com>
	<71fe4e760902010138s2c6ef64doc2bd6ff7def43e48@mail.gmail.com>
Message-ID: <20090201223315.vi3iia98hkwswog8@ox.thomasbaumann.com>

Thanks, Alain,

I got (as referred in my link on http://inhalt.serviert.de )

checking for MySQL support... yes
checking for specified location of the MySQL UNIX socket... no
checking for MySQL UNIX socket location... no
checking for mysql_close in -lmysqlclient... yes
checking for MySQLi support... no
checking whether to enable embedded MySQLi support... no
checking for ncurses support... no

So everything looks fine. Even the RPM builds correctly.

But when I install and look after my phpinfo there
is nothing about mysql nor memcache :-(

That's what I cannot understand.

Hope sb can help me further.

Thanks for your reply in advance,

thomas.

Zitat von Alain Spineux <aspineux at gmail.com>:

> On Sat, Jan 31, 2009 at 10:08 PM, Thomas Baumann   
> <tom at thomasbaumann.com> wrote:
>> Hello list,
>>
>> I tried to get PHP5 working with mysql but I didnt succeed.
>>
>> I succeeded in rebuild mysql to   
>> mysql-5.1.30-20090102.ix86-debian4.0-kolab.rpm
>> (taken from openpkg).
>> I succeeded in rebuild libevent-1.4.9-20081222.ix86-debian4.0-kolab.rpm and
>> memcached-1.3.0-20090130.ix86-debian4.0-kolab.rpm to get all dependencies
>> to my php.src.rpm
>>
>> I did a
>>
>> /kolab/bin/openpkg rpm -ivh php-5.2.8-20081209_kolab.src.rpm
>>
>> went to
>>
>> cd /kolab/RPM/SRC/php
>>
>> and tried to recompile with
>>
>>  /kolab/bin/openpkg rpm -ba --define 'with_mysql yes' \
>>        --define 'with_pecl_memcache yes'  php.spec
>
> The command looks correct !
>
> Usually, I skip the rpm -i and use a rpm --build like this :
>
> /kolab/bin/openpkg rpm --rebuild \
>        php-5.2.8-20081209_kolab.src.rpm \
>        --define 'with_mysql yes' \
>        --define 'with_pecl_memcache yes'  php.spec
>
> Did you install mysql first, before to build your php package ?
>
> I tried it myself, with mysql installed, but get this :
>
> # /kolab/bin/openpkg rpm --rebuild
> /s0/emailgency/kolab_src/php-5.2.6-20080514_kolab.src.rpm --define
> 'with_mysql yes' --define 'with_mysql yes'
> ......
> checking for specified location of the MySQL UNIX socket... no
> checking for MySQL UNIX socket location... no
> checking for mysql_close in -lmysqlclient... no
> checking for mysql_error in -lmysqlclient... no
> configure: error: mysql configure failed. Please check config.log for
> more information.
> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.71712 (%build)
>
> Hope this give you some ideas
>
>
>>
>> But the result was a installable rpm-file, but it lacks on
>> mysql and pecl-memcache support.
>>
>> What is going wrong - or what do i have to type to get
>> a RPM-file with all support as in the original but additional with
>> mysql and memcache support ?
>>
>> The compile log is visible on
>>
>> http://inhalt.serviert.de/ -->
>> http://inhalt.serviert.de/wissen/migration/kolab-2.2-beta-unter-debian-etch  
>>  ->
>> php_recompile
>>
>> Thanks for your reply in advance.
>>
>> Thomas.
>>
>> --
>> Thomas Baumann
>>
>> B?cher und mehr im Internet - meine neue Site: http://www.1-search.de
>> - Viel Spass!
>>
>> ----------------------------------------------------------------
>> 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
>>
>
>
>
> --
> 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
>
>

-- 
B?cher und mehr im Internet - meine neue Site: http://www.1-search.de  
- Viel Spass!

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


From wrobel at pardus.de  Mon Feb  2 07:47:24 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Mon, 02 Feb 2009 07:47:24 +0100
Subject: [Kolab-devel] How to use the tests that are part of the
	pear	modules?
In-Reply-To: <200901292328.08130.ml@radoeka.nl>
References: <200901292328.08130.ml@radoeka.nl>
Message-ID: <20090202074724.19769ttngd1922o0@webmail.pardus.de>

Quoting Richard Bos <ml at radoeka.nl>:

> Hi,
>
> I'm making some nice progress to get all the required pear modules for kolab
> available for openSUSE:
> http://download.opensuse.org/repositories/server:/php:/applications/openSUSE_11.1/repodata/
>
> How can I use the tests that are part of the pear modules to verify that the
> packages are build, and have been installed (include their required packages)
> correctly?
>
> E.g.:
> /usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/AllTests.php
> /usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php
>
> Should one just execute:
> /usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/AllTests.php
> and that's it, or are arguments needed and are there any requirements to the
> environment.  E.g. In case of kolab_freebusy is a webserver needed?

On Kolab/OpenPKG you would run the Kolab_Server Unit tests with

  /kolab/bin/php  -f  
/kolab/lib/php/test/Kolab_Server/Horde/Kolab/Server/AllTests.php

for example. This assumes that you have PHPUnit installed and that is  
the only prerequisite. I added this one on the OpenPKG variant because  
I wanted people to be able to run these tests on an installed machine  
in case they modify the code. It makes it easier to check if your  
modifications might create problems.

At the moment there are no higher order tests that would need a  
complete Kolab web server or IMAP server to be setup. The current test  
suites just run in memory and provide some mock drivers for LDAP and  
IMAP. These mock drivers help tremendously during development.

Higher order tests for the Kolab Server are on my todo list though. I  
think we need unit tests that allow to check functionality of complete  
Kolab systems. That would help us during testing the OpenPKG variant.  
An automatic Kolab test suite would of course also make the life  
easier for the native ports as you would be able to quickly check if  
you are up to par with the Kolab OpenPKG system. At least if the test  
suite is big enough.

I am also considering integration of these unit tests into the next  
version of the Kolab web admin. I still need to see if that works out  
as planned. So far I only wrote a minimal amount of code for the new  
web admin (based on Horde 4).

Cheers,

Gunnar

> I did not yet investigate this, I hope that someone can point me in the right
> direction quickly, at least that would be appreciated!
>
> --
> Kind regards,
>
> Richard
>
> _______________________________________________
> 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/20090202/a3f4b396/attachment.bin

From wrobel at pardus.de  Mon Feb  2 08:07:31 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Mon, 02 Feb 2009 08:07:31 +0100
Subject: [Kolab-devel] kolab 2.2.1beta -- apache+php+mysql+memcached
In-Reply-To: <20090201223315.vi3iia98hkwswog8@ox.thomasbaumann.com>
References: <20090131220858.4adff91if4swo4kw@ox.thomasbaumann.com>
	<71fe4e760902010138s2c6ef64doc2bd6ff7def43e48@mail.gmail.com>
	<20090201223315.vi3iia98hkwswog8@ox.thomasbaumann.com>
Message-ID: <20090202080731.1836585ixmds7008@webmail.pardus.de>

Quoting Thomas Baumann <tom at thomasbaumann.com>:

> Thanks, Alain,
>
> I got (as referred in my link on http://inhalt.serviert.de )
>
> checking for MySQL support... yes
> checking for specified location of the MySQL UNIX socket... no
> checking for MySQL UNIX socket location... no
> checking for mysql_close in -lmysqlclient... yes
> checking for MySQLi support... no
> checking whether to enable embedded MySQLi support... no
> checking for ncurses support... no
>
> So everything looks fine. Even the RPM builds correctly.
>
> But when I install and look after my phpinfo there
> is nothing about mysql nor memcache :-(

Maybe you are running phpinfo() via the Apache (using mod_php which is  
represented by the apache-php pacakge on OpenPKG) rather than on the  
command line. It looks as you are compiling the php package and this  
will only modify the command line PHP.

Cheers,

Gunnar

>
> That's what I cannot understand.
>
> Hope sb can help me further.
>
> Thanks for your reply in advance,
>
> thomas.
>
> Zitat von Alain Spineux <aspineux at gmail.com>:
>
>> On Sat, Jan 31, 2009 at 10:08 PM, Thomas Baumann
>> <tom at thomasbaumann.com> wrote:
>>> Hello list,
>>>
>>> I tried to get PHP5 working with mysql but I didnt succeed.
>>>
>>> I succeeded in rebuild mysql to
>>> mysql-5.1.30-20090102.ix86-debian4.0-kolab.rpm
>>> (taken from openpkg).
>>> I succeeded in rebuild libevent-1.4.9-20081222.ix86-debian4.0-kolab.rpm and
>>> memcached-1.3.0-20090130.ix86-debian4.0-kolab.rpm to get all dependencies
>>> to my php.src.rpm
>>>
>>> I did a
>>>
>>> /kolab/bin/openpkg rpm -ivh php-5.2.8-20081209_kolab.src.rpm
>>>
>>> went to
>>>
>>> cd /kolab/RPM/SRC/php
>>>
>>> and tried to recompile with
>>>
>>>  /kolab/bin/openpkg rpm -ba --define 'with_mysql yes' \
>>>        --define 'with_pecl_memcache yes'  php.spec
>>
>> The command looks correct !
>>
>> Usually, I skip the rpm -i and use a rpm --build like this :
>>
>> /kolab/bin/openpkg rpm --rebuild \
>>        php-5.2.8-20081209_kolab.src.rpm \
>>        --define 'with_mysql yes' \
>>        --define 'with_pecl_memcache yes'  php.spec
>>
>> Did you install mysql first, before to build your php package ?
>>
>> I tried it myself, with mysql installed, but get this :
>>
>> # /kolab/bin/openpkg rpm --rebuild
>> /s0/emailgency/kolab_src/php-5.2.6-20080514_kolab.src.rpm --define
>> 'with_mysql yes' --define 'with_mysql yes'
>> ......
>> checking for specified location of the MySQL UNIX socket... no
>> checking for MySQL UNIX socket location... no
>> checking for mysql_close in -lmysqlclient... no
>> checking for mysql_error in -lmysqlclient... no
>> configure: error: mysql configure failed. Please check config.log for
>> more information.
>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.71712 (%build)
>>
>> Hope this give you some ideas
>>
>>
>>>
>>> But the result was a installable rpm-file, but it lacks on
>>> mysql and pecl-memcache support.
>>>
>>> What is going wrong - or what do i have to type to get
>>> a RPM-file with all support as in the original but additional with
>>> mysql and memcache support ?
>>>
>>> The compile log is visible on
>>>
>>> http://inhalt.serviert.de/ -->
>>> http://inhalt.serviert.de/wissen/migration/kolab-2.2-beta-unter-debian-etch
>>>  ->
>>> php_recompile
>>>
>>> Thanks for your reply in advance.
>>>
>>> Thomas.
>>>
>>> --
>>> Thomas Baumann
>>>
>>> B?cher und mehr im Internet - meine neue Site: http://www.1-search.de
>>> - Viel Spass!
>>>
>>> ----------------------------------------------------------------
>>> 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
>>>
>>
>>
>>
>> --
>> 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
>>
>>
>
> --
> B?cher und mehr im Internet - meine neue Site: http://www.1-search.de
> - Viel Spass!
>
> ----------------------------------------------------------------
> 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/20090202/335a3da2/attachment.bin

From wrobel at pardus.de  Mon Feb  2 08:37:37 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Mon, 02 Feb 2009 08:37:37 +0100
Subject: [Kolab-devel] Horde webmail patch management for the Kolab
	web	client
In-Reply-To: <20090122082426.14606x428ip20nwg@webmail.pardus.de>
References: <20090111223630.41077haocs3qqfds@webmail.pardus.de>
	<20090121163052.GA4838.thomas@intevation.de>
	<20090122082426.14606x428ip20nwg@webmail.pardus.de>
Message-ID: <20090202083737.17885iq1spou1lwk@webmail.pardus.de>

Quoting Gunnar Wrobel <wrobel at pardus.de>:

> Quoting Thomas Arendsen Hein <thomas at intevation.de>:
>
>> * Gunnar Wrobel <wrobel at pardus.de> [20090111 22:36]:
>>> The single patches required for the Kolab web client (based on   
>>> Horde) can be found here:
>>>
>>> http://hg.pardus.de/cgi-bin/hg.cgi/horde/HORDE/
>>
>> I'm getting "abort: consistency error adding group!" when trying to
>> clone it, and I remember getting this in the past (December 2008?),
>> too.
>
> Hm, I admit I never tried cloning from that url.
>
>>
>> When doing minimal incremental pulls I noticed that the server is
>> running out of memory, see
>> http://hg.pardus.de/cgi-bin/hg.cgi/horde/HORDE/rev/51
>
> Hrm.
>
>>
>>> The reason why Mathieu asked about this is because he considers  
>>> the  big monolithic patch in Kolab CVS problematic to track.
>>
>>> I still believe this is the best way to go. But on the other hand   
>>> the way from the mercurial repository linked above to the final   
>>> patch may be somewhat obscure. Do people have better ideas? Or   
>>> should I just
>>> document it better in the wiki? Hoping for comments ;)
>>
>> combinediff from the patchutils package could be used to
>> automatically create the monolithic patch:
>> cat series | xargs combinediff
>
> As I'm moving to Horde 4 soon (and that includes moving away from   
> patch management with mercurial) I guess I won't fix the problems  
> you  mentioned but rather get the current patch queue into Kolab CVS.
>
> The ongoing development on Horde 4 could then be followed using git.  
>  But I still have to get this set up.

I was able to do this quicker than I anticipated. git is a nice tool indeed.

So for everyone interested in the history and / or bleeding edge of  
the kolab-webclient (based on Horde) development:

  - The project repository now resides at

    http://github.com/wrobel/horde-release/tree/master

  - You can easily clone the repository by running

    git clone git://github.com/wrobel/horde-release.git

  - The repository provides a topgit (http://repo.or.cz/w/topgit.git)  
controlled
    patch queue. Don't bother to fully understand topgit (though it is  
definitely
    worth it) if you just want to follow kolab-webclient HEAD. To track the
    latest state of the patch queue for the kolab-webclient you need to run
    within the repository you checked out above:

    git checkout -b kolab origin/t/KOLAB

    This will checkout the remote branch "t/KOLAB" (which is a  
combination of all
    the required patches) into the local branch named  "kolab". In  
order to stay
    up-to-date after that you just need to run:

    git pull

    (as long as you stay on the "kolab" branch. Otherwise issue a "git checkout
     kolab" before pulling).

  - If you are interested in topgit, you can also clone the full patch queue by
    running

    tg remote --populate origin

    from within the original checkout. This will fetch all patches.

  - If you copy /kolab/var/kolab/www/client/config/kolab.php and
    /kolab/var/kolab/www/client/kronolith/config/kolab.php to the respective
    places in your copy of the "t/KOLAB" branch then you should be able to use
    this checkout as a standard kolab-webclient and can test the newest
    fixes/features.

    This might also be the method I will soon recommend for setting up external
    web client installations.

At the current stage the whole thing is not yet very well tested, but  
I effectively switched over to the new patch management and I assume  
this to be useable soon.

Cheers,

Gunnar

>
> Cheers,
>
> Gunnar
>
>>
>> Thomas
>>
>> --
>> 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
>>
>
>
>
> -- 
> ______ 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/20090202/3bd19962/attachment-0001.bin

From bernhard at intevation.de  Mon Feb  2 12:11:54 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 2 Feb 2009 12:11:54 +0100
Subject: [Kolab-devel] martin: server/kolabd/kolabd kolab2.schema, 1.31,
	1.32
In-Reply-To: <20090130164939.GF23543.thomas@intevation.de>
References: <20090107091856.E4A07600948@lists.intevation.de>
	<200901281147.31557.bernhard@intevation.de>
	<20090130164939.GF23543.thomas@intevation.de>
Message-ID: <200902021211.57381.bernhard@intevation.de>

On Freitag, 30. Januar 2009, Thomas Arendsen Hein wrote:
> But wouldn't it be better to add comments in the schema file to note
> what is import and what is deprecated?

Yes, the Wiki page is mainly for the OID overview.


-- 
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/20090202/d23b9287/attachment.bin

From aspineux at gmail.com  Mon Feb  2 13:34:59 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 2 Feb 2009 13:34:59 +0100
Subject: [Kolab-devel] Log management of Kolab from a system
	administrator view
In-Reply-To: <871wfxa6ft.fsf@rdus.de>
References: <467E5F9F.6060701@infosecurity.ch> <871wfxa6ft.fsf@rdus.de>
Message-ID: <71fe4e760902020434m52d16745rad1ea52eef324835@mail.gmail.com>

On Wed, Jun 27, 2007 at 2:11 PM, Gunnar Wrobel <wrobel at pardus.de> wrote:
> "Fabio Pietrosanti (naif)" <lists at infosecurity.ch> writes:
>
>> Hi all,
>>
>> even appreciating the OpenPKG approach used by kolab of self-contained
>> environment i really don't like the approach used for the log files and
>> i am proposing some discussion to re-organize them.
>>
>> Log files are very important, are used for solving problems, analyzing
>> the behaviours of the system and system administrator really require
>> quick system to search for patterns.
>>
>> In tipical unix environment this is done trough the 'grep -ir string
>> /var/log' .
>>
>> With kolab you need to go to /kolab/var/imapd/log to see cyrus log, to
>> /kolab/var/sasl/log to see saslauthd log, to /kolab/var/openldap/log to
>> see openldap log and so on for all other componets.

Just an idea .... you can create symbolic link to all theses files in
one unique directory :-)
And you get what you want !

>
> As mentioned by others this is not really a problem since you can
> either use `find ...` or even "grep /kolab/var/**/log/*.log" directly.
>
>> That's really a annoying, the system administrator can't simply do "tail
>> -f *".
>>
>> I suggest, for kolab 2.2 goals, to put all the logs in only one
>> directory (es: /kolab/logs) and automatically rotate and archive them
>> with a directory structure organized for each day (es:
>> /kolab/logs/2007/06/20/daemon_name_subname.log).
>>
>> This could be done trough modification of FSL definitions on
>> /kolab/etc/fsl and trough /kolab/etc/rc.d/* scripts in the rotate.
>>
>>
>> Otherwise we could simplify and add powerfull log management capability
>> to Kolab by using an OpenPKG based syslog-ng daemon
>> (http://www.openpkg.org/product/packages/?package=syslog-ng) .
>
> Most of the components within Kolab can actually be modified to use
> the syslog. Even most of the Kolab-specific packages like
> kolab-resource-handlers can be switched.
>
> So I see this as a simple matter of preference. If you wish to use
> syslog-ng you can simply install one in the system that is hosting the
> Kolab OpenPKG environment and let all Kolab components report to that
> syslog-ng.
>
> I do also believe that we would find many people that would complain
> if we'd change the way the logs currently work. Though I actually also
> prefer the syslog approach and my native Gentoo version of Kolab
> actually reports to syslog most of the time.
>
> Cheers,
>
> Gunnar
>
> --
> ____ http://www.pardus.de _________________ http://gunnarwrobel.de _
>
>    >> Mail at ease - Rent a kolab groupware server at p at rdus <<
>
> p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
>
> _______________________________________________
> 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  Mon Feb  2 15:13:15 2009
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Mon, 02 Feb 2009 14:13:15 +0000
Subject: [Kolab-devel] [issue3377] Issue warning when emailing to more than
	X recipients
Message-ID: <1233583995.83.0.440064617631.issue3377@intevation.de>


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

Some users wish to have warning shortly before and email is send
towards a large number of recipients.
The number should be configured, e.g. five by default
or no warning at all.

The warning could be a dialog saying: You are trying to send email
to five recipients, really send? Ok, Cancel.
Or in some other obviousy way, e.g. visual marking somewhere.
E.g. a red bar appears, just like with a signature in which you can read
the warning.

As reference point:
Kontact Version: 4:3.5.10.enterprise.0.20090121.914162-kk1 on Etch
does not have the warning.

----------
assignedto: allen
messages: 18367
nosy: allen, bernhard, ludwig
priority: wish
status: unread
title: Issue warning when emailing to more than X recipients
topic: enterprise35, enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3377>
___________________________________________________


From kolab-issues at intevation.de  Mon Feb  2 15:22:39 2009
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Mon, 02 Feb 2009 14:22:39 +0000
Subject: [Kolab-devel] [issue3378] Visually mark distribution lists
Message-ID: <1233584559.46.0.591098917369.issue3378@intevation.de>


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

Kontact/KMail should somehow recognize and mark distribution lists.
Marking could happen by a small icon or something similiar.

Recognition has at least three cases:
a) have a configurable regular expression for email names
that will be considered a distribution list. This is good for some organisation
where email-list have special namens like "list-.*".

b) A flag in the contacts (coming from KAddressbook)
c) Recognition of the kolabGroupOfNames object via the LDAP addresses.

The following version does not have it:
Kontact 3.5.10.enterprise.0.20090121.914162-kk1 on Etch.

----------
assignedto: allen
messages: 18369
nosy: allen, bernhard, ludwig
priority: wish
status: unread
title: Visually mark distribution lists
topic: enterprise35, enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3378>
___________________________________________________


From kolab-issues at intevation.de  Tue Feb  3 11:04:07 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 03 Feb 2009 10:04:07 +0000
Subject: [Kolab-devel] [issue3379] Often syncing stopps,
	because of an unexcepted finish of the process for the imaps
	protocol
Message-ID: <1233655447.35.0.232915555942.issue3379@intevation.de>


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

Kontact-Installer_20090115

While syncing kontact often shows an error message and fails to sync.
The process of the protocol imaps://test.server unexceptedly aborts.
This happens on my test machine very often.
I have one Windows running and use different users. Everytime I switch users,
I stop the kde processes.

Versions:
kdelibs-branch 913389
kdebase-runtime 913393
kdepimlibs-branch 912009
kdepim 913396
l10n-kde4 913445
kowi-crypto-files_gpg4win1.9.13-beta

----------
assignedto: allen
messages: 18383
nosy: allen, bh, ludwig
priority: bug
status: unread
title: Often syncing stopps, because of an unexcepted finish of the process for the imaps protocol
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3379>
___________________________________________________


From kolab-issues at intevation.de  Tue Feb  3 11:20:40 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 03 Feb 2009 10:20:40 +0000
Subject: [Kolab-devel] [issue3380] The update mail which is sent because of
	a moved event cannot be entered into the calendar.
Message-ID: <1233656440.19.0.454719380161.issue3380@intevation.de>


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

enterprise4 windows 
Kontact_Installer_20090115.exe

Test:
1. A invites B to an event.
2. B syncs and accepts the event.
3. A syncs and updates his event.
4. A moves the event to a different time.
5. B syncs and looks at his mail.
=> The update mail cannot be entered into B's calendar.

See the mail 1. for an example update mail.

Versions:
kdelibs-branch 913389
kdebase-runtime 913393
kdepimlibs-branch 912009
kdepim 913396
l10n-kde4 913445
kowi-crypto-files_gpg4win1.9.13-beta

----------
assignedto: allen
files: 1.
messages: 18384
nosy: allen, bh, ludwig
priority: bug
status: unread
title: The update mail which is sent because of a moved event cannot be entered into the calendar.
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3380>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1.
Type: application/octet-stream
Size: 1561 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090203/e2c45807/1.exe

From tom at tiri.li  Sun Feb  1 22:31:03 2009
From: tom at tiri.li (Thomas Baumann)
Date: Sun, 01 Feb 2009 22:31:03 +0100
Subject: [Kolab-devel] kolab 2.2.1beta -- apache+php+mysql+memcached
In-Reply-To: <71fe4e760902010138s2c6ef64doc2bd6ff7def43e48@mail.gmail.com>
References: <20090131220858.4adff91if4swo4kw@ox.thomasbaumann.com>
	<71fe4e760902010138s2c6ef64doc2bd6ff7def43e48@mail.gmail.com>
Message-ID: <20090201223103.gv5reia7s44ksgs8@ox.thomasbaumann.com>

Thanks, Alain,

I got (as referred in my link)

checking for MySQL support... yes
checking for specified location of the MySQL UNIX socket... no
checking for MySQL UNIX socket location... no
checking for mysql_close in -lmysqlclient... yes
checking for MySQLi support... no
checking whether to enable embedded MySQLi support... no
checking for ncurses support... no

So everything looks fine. Even the RPM builds correctly.

But when I install and look after my phpinfo there
is nothing about mysql nor memcache :-(

That's what I cannot understand.

Hope sb can help me further.

Thanks for your reply in advance,

thomas.

Zitat von Alain Spineux <aspineux at gmail.com>:

> On Sat, Jan 31, 2009 at 10:08 PM, Thomas Baumann   
> <tom at thomasbaumann.com> wrote:
>> Hello list,
>>
>> I tried to get PHP5 working with mysql but I didnt succeed.
>>
>> I succeeded in rebuild mysql to   
>> mysql-5.1.30-20090102.ix86-debian4.0-kolab.rpm
>> (taken from openpkg).
>> I succeeded in rebuild libevent-1.4.9-20081222.ix86-debian4.0-kolab.rpm and
>> memcached-1.3.0-20090130.ix86-debian4.0-kolab.rpm to get all dependencies
>> to my php.src.rpm
>>
>> I did a
>>
>> /kolab/bin/openpkg rpm -ivh php-5.2.8-20081209_kolab.src.rpm
>>
>> went to
>>
>> cd /kolab/RPM/SRC/php
>>
>> and tried to recompile with
>>
>>  /kolab/bin/openpkg rpm -ba --define 'with_mysql yes' \
>>        --define 'with_pecl_memcache yes'  php.spec
>
> The command looks correct !
>
> Usually, I skip the rpm -i and use a rpm --build like this :
>
> /kolab/bin/openpkg rpm --rebuild \
>        php-5.2.8-20081209_kolab.src.rpm \
>        --define 'with_mysql yes' \
>        --define 'with_pecl_memcache yes'  php.spec
>
> Did you install mysql first, before to build your php package ?
>
> I tried it myself, with mysql installed, but get this :
>
> # /kolab/bin/openpkg rpm --rebuild
> /s0/emailgency/kolab_src/php-5.2.6-20080514_kolab.src.rpm --define
> 'with_mysql yes' --define 'with_mysql yes'
> ......
> checking for specified location of the MySQL UNIX socket... no
> checking for MySQL UNIX socket location... no
> checking for mysql_close in -lmysqlclient... no
> checking for mysql_error in -lmysqlclient... no
> configure: error: mysql configure failed. Please check config.log for
> more information.
> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.71712 (%build)
>
> Hope this give you some ideas
>
>
>>
>> But the result was a installable rpm-file, but it lacks on
>> mysql and pecl-memcache support.
>>
>> What is going wrong - or what do i have to type to get
>> a RPM-file with all support as in the original but additional with
>> mysql and memcache support ?
>>
>> The compile log is visible on
>>
>> http://inhalt.serviert.de/ -->
>> http://inhalt.serviert.de/wissen/migration/kolab-2.2-beta-unter-debian-etch  
>>  ->
>> php_recompile
>>
>> Thanks for your reply in advance.
>>
>> Thomas.
>>
>> --
>> Thomas Baumann
>>
>> B?cher und mehr im Internet - meine neue Site: http://www.1-search.de
>> - Viel Spass!
>>
>> ----------------------------------------------------------------
>> 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
>>
>
>
>
> --
> 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
>
>



-- 
tiri Limited & Co. KG
Johann-Adolf-Hasse-Str. 2b
21493 Schwarzenbek

Gesch?ftsf?hrerin: Anja Baumann

Sitz der Gesellschaft: Schwarzenbek

Handelsregister: HRA 5078 HL
USt.-ID: DE254262065

Pers?nlich haftender Gesellschafter: tiri Limited

tiri Limited ist eine Gesellschaft nach englischem Recht, zugelassen
bei Companies House zu Cardiff, Company No. 05178378, Registered
Office: 39-40 Calthorpe Road, Birmingham, West Midlands, B15 1TS,
United Kingdom

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


From tom at tiri.li  Mon Feb  2 09:02:54 2009
From: tom at tiri.li (Thomas Baumann)
Date: Mon, 02 Feb 2009 09:02:54 +0100
Subject: [Kolab-devel] kolab 2.2.1beta -- apache+php+mysql+memcached
In-Reply-To: <20090202080731.1836585ixmds7008@webmail.pardus.de>
References: <20090131220858.4adff91if4swo4kw@ox.thomasbaumann.com>
	<71fe4e760902010138s2c6ef64doc2bd6ff7def43e48@mail.gmail.com>
	<20090201223315.vi3iia98hkwswog8@ox.thomasbaumann.com>
	<20090202080731.1836585ixmds7008@webmail.pardus.de>
Message-ID: <20090202090254.7zzspptz0gsso8oc@ox.thomasbaumann.com>

Yes I run phpinfo from apache.
What are the steps to get customized php usable from the
webserver ?

Which RPMs are to be recompiled ?

Thanks for your reply in advance.

Thomas.

Zitat von Gunnar Wrobel <wrobel at pardus.de>:

> Quoting Thomas Baumann <tom at thomasbaumann.com>:
>
>> Thanks, Alain,
>>
>> I got (as referred in my link on http://inhalt.serviert.de )
>>
>> checking for MySQL support... yes
>> checking for specified location of the MySQL UNIX socket... no
>> checking for MySQL UNIX socket location... no
>> checking for mysql_close in -lmysqlclient... yes
>> checking for MySQLi support... no
>> checking whether to enable embedded MySQLi support... no
>> checking for ncurses support... no
>>
>> So everything looks fine. Even the RPM builds correctly.
>>
>> But when I install and look after my phpinfo there
>> is nothing about mysql nor memcache :-(
>
> Maybe you are running phpinfo() via the Apache (using mod_php which is
> represented by the apache-php pacakge on OpenPKG) rather than on the
> command line. It looks as you are compiling the php package and this
> will only modify the command line PHP.
>
> Cheers,
>
> Gunnar
>
>>
>> That's what I cannot understand.
>>
>> Hope sb can help me further.
>>
>> Thanks for your reply in advance,
>>
>> thomas.
>>
>> Zitat von Alain Spineux <aspineux at gmail.com>:
>>
>>> On Sat, Jan 31, 2009 at 10:08 PM, Thomas Baumann
>>> <tom at thomasbaumann.com> wrote:
>>>> Hello list,
>>>>
>>>> I tried to get PHP5 working with mysql but I didnt succeed.
>>>>
>>>> I succeeded in rebuild mysql to
>>>> mysql-5.1.30-20090102.ix86-debian4.0-kolab.rpm
>>>> (taken from openpkg).
>>>> I succeeded in rebuild   
>>>> libevent-1.4.9-20081222.ix86-debian4.0-kolab.rpm and
>>>> memcached-1.3.0-20090130.ix86-debian4.0-kolab.rpm to get all dependencies
>>>> to my php.src.rpm
>>>>
>>>> I did a
>>>>
>>>> /kolab/bin/openpkg rpm -ivh php-5.2.8-20081209_kolab.src.rpm
>>>>
>>>> went to
>>>>
>>>> cd /kolab/RPM/SRC/php
>>>>
>>>> and tried to recompile with
>>>>
>>>> /kolab/bin/openpkg rpm -ba --define 'with_mysql yes' \
>>>>       --define 'with_pecl_memcache yes'  php.spec
>>>
>>> The command looks correct !
>>>
>>> Usually, I skip the rpm -i and use a rpm --build like this :
>>>
>>> /kolab/bin/openpkg rpm --rebuild \
>>>       php-5.2.8-20081209_kolab.src.rpm \
>>>       --define 'with_mysql yes' \
>>>       --define 'with_pecl_memcache yes'  php.spec
>>>
>>> Did you install mysql first, before to build your php package ?
>>>
>>> I tried it myself, with mysql installed, but get this :
>>>
>>> # /kolab/bin/openpkg rpm --rebuild
>>> /s0/emailgency/kolab_src/php-5.2.6-20080514_kolab.src.rpm --define
>>> 'with_mysql yes' --define 'with_mysql yes'
>>> ......
>>> checking for specified location of the MySQL UNIX socket... no
>>> checking for MySQL UNIX socket location... no
>>> checking for mysql_close in -lmysqlclient... no
>>> checking for mysql_error in -lmysqlclient... no
>>> configure: error: mysql configure failed. Please check config.log for
>>> more information.
>>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.71712 (%build)
>>>
>>> Hope this give you some ideas
>>>
>>>
>>>>
>>>> But the result was a installable rpm-file, but it lacks on
>>>> mysql and pecl-memcache support.
>>>>
>>>> What is going wrong - or what do i have to type to get
>>>> a RPM-file with all support as in the original but additional with
>>>> mysql and memcache support ?
>>>>
>>>> The compile log is visible on
>>>>
>>>> http://inhalt.serviert.de/ -->
>>>> http://inhalt.serviert.de/wissen/migration/kolab-2.2-beta-unter-debian-etch
>>>> ->
>>>> php_recompile
>>>>
>>>> Thanks for your reply in advance.
>>>>
>>>> Thomas.
>>>>
>>>> --
>>>> Thomas Baumann
>>>>
>>>> B?cher und mehr im Internet - meine neue Site: http://www.1-search.de
>>>> - Viel Spass!
>>>>
>>>> ----------------------------------------------------------------
>>>> 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
>>>>
>>>
>>>
>>>
>>> --
>>> 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
>>>
>>>
>>
>> --
>> B?cher und mehr im Internet - meine neue Site: http://www.1-search.de
>> - Viel Spass!
>>
>> ----------------------------------------------------------------
>> 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.



-- 
tiri Limited & Co. KG
Johann-Adolf-Hasse-Str. 2b
21493 Schwarzenbek

Gesch?ftsf?hrerin: Anja Baumann

Sitz der Gesellschaft: Schwarzenbek

Handelsregister: HRA 5078 HL
USt.-ID: DE254262065

Pers?nlich haftender Gesellschafter: tiri Limited

tiri Limited ist eine Gesellschaft nach englischem Recht, zugelassen
bei Companies House zu Cardiff, Company No. 05178378, Registered
Office: 39-40 Calthorpe Road, Birmingham, West Midlands, B15 1TS,
United Kingdom

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


From kolab-issues at intevation.de  Wed Feb  4 23:34:43 2009
From: kolab-issues at intevation.de (Mathieu Parent)
Date: Wed, 04 Feb 2009 22:34:43 +0000
Subject: [Kolab-devel] [issue3381] turba's 'kolab_global' source should use
	should use phpdn to connect to LDAP
Message-ID: <1233786883.66.0.604807539528.issue3381@intevation.de>


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

The current turba config binds anonymously. 
The php_dn should be used (some configurations don't allow anonymous search).

Then it will behave like freebusy and filter.

I don't know how to provide a patch (this should be included in
turba/HK-GW-Config.patch)

$cfgSources['kolab_global']['params']['bind_dn'] = $conf['kolab']['ldap']['phpdn'];
$cfgSources['kolab_global']['params']['bind_password'] =
$conf['kolab']['ldap']['phppw']

----------
assignedto: wrobel
messages: 18405
nosy: martin, mathieu.parent, rbos, thomas, wrobel
priority: feature
status: unread
title: turba's 'kolab_global' source should use should use phpdn to connect to LDAP
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3381>
___________________________________________________


From kolab-issues at intevation.de  Thu Feb  5 09:07:31 2009
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Thu, 05 Feb 2009 08:07:31 +0000
Subject: [Kolab-devel] [issue3382] Crash when displaying forwarded email
	form the composer
Message-ID: <1233821250.9.0.934878914107.issue3382@intevation.de>


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

How to reproduce:
a) do a forward as attachment on an email -> composer appears (C)
b) double click on the attachment -> the attached email appears in a window (E)
   -> you get a dialog that Kontact cannot determine when the Editor is
      finished (O)
c) Now close C, E, and okay O
   -> Crash.

I can reproduce with Debian Etch, versions
3.5.10.enterprise.0.20090131.918764-kk1
3.5.10.enterprise.0.20090121.914162-kk1

The backtrace is not conclusive as we run through QObject::activate_signal.
In the console output there is something interesting. I am attaching
a backtrace and console excerpt from 3.5.10.enterprise.0.20090121.914162-kk1.
there seems to be a problem with KMMessagePart::setCharset().

----------
assignedto: allen
files: kontact-crash-20090205-3.txt
messages: 18411
nosy: allen, bernhard, ludwig, tmcguire
priority: bug
status: unread
title: Crash when displaying forwarded email form the composer
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3382>
___________________________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: kontact-crash-20090205-3.txt
Url: http://kolab.org/pipermail/kolab-devel/attachments/20090205/b87725a3/kontact-crash-20090205-3.txt

From kolab-issues at intevation.de  Thu Feb  5 09:50:33 2009
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Thu, 05 Feb 2009 08:50:33 +0000
Subject: [Kolab-devel] [issue3383] Signed only opaque S/MIME emails are
	labled "encrypted" (when they are not)
Message-ID: <1233823833.35.0.351795153304.issue3383@intevation.de>


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

If an S/MIME email is 

i) signed only, 
ii) and send opaque 
iii) and missing the Content-Type attribute "smime-type=signed-data"

3.5.10.enterprise.0.20090121.914162-kk1 on Etch
will not directly display the message claiming that
it is "encrypted".

This is a problem as it might let people to believe that this email
was indeed encrypted when it was not.
I am attaching an example email.

You can create one by sending yourself an email, selecting S/MIME opaque
and then deleting the Content-Type attribute "smime-type=signed-data"
from the email.

It seems some real-world applications still send out such emails,
so this is not an academic issue.

As we probably cannot probe if this encrypted or now, unless we actually
try the decryption .. I believe we should rephrase the blue box
in being less precise about "encryption".

----------
assignedto: allen
messages: 18415
nosy: allen, bernhard, marc, till
priority: bug
status: unread
title: Signed only opaque S/MIME emails are labled "encrypted" (when they are not)
topic: enterprise35, enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3383>
___________________________________________________


From kolab-issues at intevation.de  Thu Feb  5 14:17:05 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 05 Feb 2009 13:17:05 +0000
Subject: [Kolab-devel] [issue3384] For sending a smime encrypted mail,
	the user needs to choose key
Message-ID: <1233839825.8.0.625828698863.issue3384@intevation.de>


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

enterprise4 lenny
kdepim 918783
kdepimlibs 918707

I have two account which only differ in the first name and the e-mail address.
(Smoke1 Smoketestuser <smoke1 at test.hq>, Smoke2 Smoketestuser <smoke2 at test.hq>)
I try to send a s/mime encrypted mail from smoke1 to smoke2, but kontact tells
me that more keys fit and asks me to select a key:
* CN=Smoke1 Smoketestuser...
* CN=Smoke2 Smoketestuser...
are selected. 
I used the LDAP entry of smoke2 as To-address.
I expect, that kontact just find "CN=Smoke2 Smoketestuser..." and uses this key.

Same happens with enterprise4 windows.

If I change the surname of the smoke2 account, it works.

----------
assignedto: allen
messages: 18421
nosy: allen, bernhard, bh, ludwig
priority: bug
status: unread
title: For sending a smime encrypted mail, the user needs to choose key
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3384>
___________________________________________________


From wrobel at pardus.de  Thu Feb  5 15:45:16 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 05 Feb 2009 15:45:16 +0100
Subject: [Kolab-devel] kolab 2.2.1beta -- apache+php+mysql+memcached
In-Reply-To: <20090202090254.7zzspptz0gsso8oc@ox.thomasbaumann.com>
References: <20090131220858.4adff91if4swo4kw@ox.thomasbaumann.com>
	<71fe4e760902010138s2c6ef64doc2bd6ff7def43e48@mail.gmail.com>
	<20090201223315.vi3iia98hkwswog8@ox.thomasbaumann.com>
	<20090202080731.1836585ixmds7008@webmail.pardus.de>
	<20090202090254.7zzspptz0gsso8oc@ox.thomasbaumann.com>
Message-ID: <20090205154516.69133v8yk65h0neo@webmail.pardus.de>

Quoting Thomas Baumann <tom at tiri.li>:

> Yes I run phpinfo from apache.
> What are the steps to get customized php usable from the
> webserver ?
>
> Which RPMs are to be recompiled ?

The apache-php package provides mod_php for the apache server while  
the php package provides command line PHP.

Cheers,

Gunnar

>
> Thanks for your reply in advance.
>
> Thomas.
>
> Zitat von Gunnar Wrobel <wrobel at pardus.de>:
>
>> Quoting Thomas Baumann <tom at thomasbaumann.com>:
>>
>>> Thanks, Alain,
>>>
>>> I got (as referred in my link on http://inhalt.serviert.de )
>>>
>>> checking for MySQL support... yes
>>> checking for specified location of the MySQL UNIX socket... no
>>> checking for MySQL UNIX socket location... no
>>> checking for mysql_close in -lmysqlclient... yes
>>> checking for MySQLi support... no
>>> checking whether to enable embedded MySQLi support... no
>>> checking for ncurses support... no
>>>
>>> So everything looks fine. Even the RPM builds correctly.
>>>
>>> But when I install and look after my phpinfo there
>>> is nothing about mysql nor memcache :-(
>>
>> Maybe you are running phpinfo() via the Apache (using mod_php which is
>> represented by the apache-php pacakge on OpenPKG) rather than on the
>> command line. It looks as you are compiling the php package and this
>> will only modify the command line PHP.
>>
>> Cheers,
>>
>> Gunnar
>>
>>>
>>> That's what I cannot understand.
>>>
>>> Hope sb can help me further.
>>>
>>> Thanks for your reply in advance,
>>>
>>> thomas.
>>>
>>> Zitat von Alain Spineux <aspineux at gmail.com>:
>>>
>>>> On Sat, Jan 31, 2009 at 10:08 PM, Thomas Baumann
>>>> <tom at thomasbaumann.com> wrote:
>>>>> Hello list,
>>>>>
>>>>> I tried to get PHP5 working with mysql but I didnt succeed.
>>>>>
>>>>> I succeeded in rebuild mysql to
>>>>> mysql-5.1.30-20090102.ix86-debian4.0-kolab.rpm
>>>>> (taken from openpkg).
>>>>> I succeeded in rebuild
>>>>> libevent-1.4.9-20081222.ix86-debian4.0-kolab.rpm and
>>>>> memcached-1.3.0-20090130.ix86-debian4.0-kolab.rpm to get all dependencies
>>>>> to my php.src.rpm
>>>>>
>>>>> I did a
>>>>>
>>>>> /kolab/bin/openpkg rpm -ivh php-5.2.8-20081209_kolab.src.rpm
>>>>>
>>>>> went to
>>>>>
>>>>> cd /kolab/RPM/SRC/php
>>>>>
>>>>> and tried to recompile with
>>>>>
>>>>> /kolab/bin/openpkg rpm -ba --define 'with_mysql yes' \
>>>>>       --define 'with_pecl_memcache yes'  php.spec
>>>>
>>>> The command looks correct !
>>>>
>>>> Usually, I skip the rpm -i and use a rpm --build like this :
>>>>
>>>> /kolab/bin/openpkg rpm --rebuild \
>>>>       php-5.2.8-20081209_kolab.src.rpm \
>>>>       --define 'with_mysql yes' \
>>>>       --define 'with_pecl_memcache yes'  php.spec
>>>>
>>>> Did you install mysql first, before to build your php package ?
>>>>
>>>> I tried it myself, with mysql installed, but get this :
>>>>
>>>> # /kolab/bin/openpkg rpm --rebuild
>>>> /s0/emailgency/kolab_src/php-5.2.6-20080514_kolab.src.rpm --define
>>>> 'with_mysql yes' --define 'with_mysql yes'
>>>> ......
>>>> checking for specified location of the MySQL UNIX socket... no
>>>> checking for MySQL UNIX socket location... no
>>>> checking for mysql_close in -lmysqlclient... no
>>>> checking for mysql_error in -lmysqlclient... no
>>>> configure: error: mysql configure failed. Please check config.log for
>>>> more information.
>>>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.71712 (%build)
>>>>
>>>> Hope this give you some ideas
>>>>
>>>>
>>>>>
>>>>> But the result was a installable rpm-file, but it lacks on
>>>>> mysql and pecl-memcache support.
>>>>>
>>>>> What is going wrong - or what do i have to type to get
>>>>> a RPM-file with all support as in the original but additional with
>>>>> mysql and memcache support ?
>>>>>
>>>>> The compile log is visible on
>>>>>
>>>>> http://inhalt.serviert.de/ -->
>>>>> http://inhalt.serviert.de/wissen/migration/kolab-2.2-beta-unter-debian-etch
>>>>> ->
>>>>> php_recompile
>>>>>
>>>>> Thanks for your reply in advance.
>>>>>
>>>>> Thomas.
>>>>>
>>>>> --
>>>>> Thomas Baumann
>>>>>
>>>>> B?cher und mehr im Internet - meine neue Site: http://www.1-search.de
>>>>> - Viel Spass!
>>>>>
>>>>> ----------------------------------------------------------------
>>>>> 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
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> 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
>>>>
>>>>
>>>
>>> --
>>> B?cher und mehr im Internet - meine neue Site: http://www.1-search.de
>>> - Viel Spass!
>>>
>>> ----------------------------------------------------------------
>>> 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.
>
>
>
> --
> tiri Limited & Co. KG
> Johann-Adolf-Hasse-Str. 2b
> 21493 Schwarzenbek
>
> Gesch?ftsf?hrerin: Anja Baumann
>
> Sitz der Gesellschaft: Schwarzenbek
>
> Handelsregister: HRA 5078 HL
> USt.-ID: DE254262065
>
> Pers?nlich haftender Gesellschafter: tiri Limited
>
> tiri Limited ist eine Gesellschaft nach englischem Recht, zugelassen
> bei Companies House zu Cardiff, Company No. 05178378, Registered
> Office: 39-40 Calthorpe Road, Birmingham, West Midlands, B15 1TS,
> United Kingdom
>
> ----------------------------------------------------------------
> 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/20090205/e0ca4e38/attachment.bin

From kolab-issues at intevation.de  Thu Feb  5 16:25:48 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 05 Feb 2009 15:25:48 +0000
Subject: [Kolab-devel] [issue3385] reminder of an event doesn't work
Message-ID: <1233847548.52.0.579761970422.issue3385@intevation.de>


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

enterprise35 20090131.918764

The user enters a new event with alarm on. He then expects that a reminder shows
up before the event. But that doesn't happen. The reminder is missing.

----------
assignedto: allen
messages: 18426
nosy: allen, bernhard, bh, ludwig
priority: critical
status: unread
title: reminder of an event doesn't work
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3385>
___________________________________________________


From kolab-issues at intevation.de  Thu Feb  5 17:15:09 2009
From: kolab-issues at intevation.de (Bernhard Herzog)
Date: Thu, 05 Feb 2009 16:15:09 +0000
Subject: [Kolab-devel] [issue3386] Kontact requires that free/busy urls
	match email addresses
Message-ID: <1233850509.55.0.16836229195.issue3386@intevation.de>


New submission from Bernhard Herzog <bh at intevation.de>:

Tested with Kontact from KDEPIM enterprise 3.5 rev. 914162.

When Kontact tries to fetch the free/busy list for a given Email address (e.g.
while adding participants in the event dialog), it checks whether the hostname
of the free/busy url matches the hostname of the email address.  If they don't
match, Kontact simply does nothing.

For instance, let's assume the email address is "user at example.com" and the
hostname of the kolab server is "kolab.example.com".  If the full hostname is
used in the free/busy url, Kontact tries to fetch the free/busy list.  However,
if you only use "kolab" as the hostname (which should work assuming "kontact"
resolves to the same address as "kolab.example.com") then Kontact doesn't even
try.  Instead one gets the following debug output:

korganizer: Host 'kolab' doesn't match email 'user at example.com'
korganizer: FreeBusyManager::processRetrieveQueue(): url:
korganizer: Invalid FB URL

Setups where the Kolab hostname does not match the email address appear to be
common in practice.  There have been several problem reports because of this.

----------
assignedto: allen
messages: 18427
nosy: allen, bh, ludwig, wilde
priority: bug
status: unread
title: Kontact requires that free/busy urls match email addresses
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3386>
___________________________________________________


From kolab-issues at intevation.de  Thu Feb  5 19:41:13 2009
From: kolab-issues at intevation.de (Mathieu Parent)
Date: Thu, 05 Feb 2009 18:41:13 +0000
Subject: [Kolab-devel] [issue3387] dist_conf configuration in kolab
	webclient templates
Message-ID: <1233859273.15.0.0608782769533.issue3387@intevation.de>


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

For webclient-kolab-conf.template and webclient-kronolith-kolab-conf.template:

1) permissions and ownership:
PERMISSIONS=0400
OWNERSHIP=@webserver_usr@:@webserver_grp@

the web server should not be able to write. the owner and group should be
distribution specific

2) LDAP uri (as in kolab/issue3322)
$conf['kolab']['ldap']['server'] = '@@@ldap_uri@@@';


3) TARGET should be distribution specific.

In debian, we have:
 TARGET=/etc/kolab-webclient/horde3/kolab.php
 TARGET=/etc/kolab-webclient/kronolith2/kolab.php

The configuration can be @horde_confdir@ and @kronolith_confdir at .

I can provide a patch for (3)

----------
assignedto: wrobel
messages: 18435
nosy: mathieu.parent, wrobel
priority: minor bug
status: unread
title: dist_conf configuration in kolab webclient templates
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3387>
___________________________________________________


From kolab-issues at intevation.de  Fri Feb  6 07:44:10 2009
From: kolab-issues at intevation.de (Nadine Dow)
Date: Fri, 06 Feb 2009 06:44:10 +0000
Subject: [Kolab-devel] [issue3388] Love yourself
Message-ID: <000d01c98826$3943cfd0$6400a8c0@brickingy6>


New submission from Nadine Dow <24dzgxar4917 at z.bevels.net>:

I think it's need you. but maybe i'm wrong
http://forwardfirstguide.com.es/

----------
messages: 18438
nosy: 24dzgxar4917
status: unread
title: Love yourself
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3388>
___________________________________________________


From kolab-issues at intevation.de  Fri Feb  6 11:19:29 2009
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Fri, 06 Feb 2009 10:19:29 +0000
Subject: [Kolab-devel] [issue3389] Consult a whitelist for emails to get the
	freebusy infos from one server.
Message-ID: <1233915568.96.0.179442953907.issue3389@intevation.de>


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

Current e35 and e4 can either fetch all freebusy lists
from the server konfigured in korganiser or check on email domain subsets.
There is a configure option, see kolab/issue3386 (Kontact requires that 
free/busy urls match email addresses) from where this issue is split out.

Usually one Kolab Server serves a few different email domains,
and if you disable the check, the server will get
i) more requests
ii) know each recipient that you try to invite, even when
    it is not necessary because the email is send via a different
    path and the calender item is not saved on the server.

Adding a whitelist for one server would help with i) and ii).
The whitelist would contain domains x.y for which the fb lists
for A at x.y and B at z.x.y would be fetched.

----------
assignedto: allen
messages: 18452
nosy: allen, bernhard, till
priority: wish
status: unread
title: Consult a whitelist for emails to get the freebusy infos from one server.
topic: enterprise35, enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3389>
___________________________________________________


From kolab-issues at intevation.de  Sat Feb  7 06:00:52 2009
From: kolab-issues at intevation.de (Kiser Rod)
Date: Sat, 07 Feb 2009 05:00:52 +0000
Subject: [Kolab-devel] [issue3391] Medical Doctor Mailing List
Message-ID: <20090207050047.BCB1E94B657@kolab.intevation.de>


New submission from Kiser Rod <pleasenoemailhere at 62.36.241.57.static.abi.uni2.es>:

Currently in Practice:  Doctors in the United States 

Featuring the most accurate contact information in many different areas of medicine

Over a dozen sortable fields

Now offered at the lower rate:  $394

*** Get These Fr EE with every order this week !!!!!!!

-> Dentists

==> Hospitals

** Pharmaceutical Companies

++ Medical Equipment Suppliers

please contact us by email at - : Rosario at healthcarelistsource.com

If you order by this Friday ==============   kill future mailing by pressing this please send an email to undo at healthcarelistsource.com

----------
messages: 18476
nosy: chad.perkins, hsinfo, info13, pleasenoemailhere, products, rlinsky, storellf, todd.pittenger
status: unread
title: Medical Doctor Mailing List
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3391>
___________________________________________________


From ml at radoeka.nl  Sat Feb  7 15:11:46 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sat, 7 Feb 2009 15:11:46 +0100
Subject: [Kolab-devel] Failing php tests for kolab
Message-ID: <200902071511.47447.ml@radoeka.nl>

Hi,

I just ran tests that come with the kolab pear packages and some tests are 
failing.  Hence I have some questions related to this.  Please find the 
failing tests in the attachment.  This is btw on native openSUSE_11.1

Tests seem to fail because the file Horde/Kolab/Test.php is not present;
What module provides the file Horde/Kolab/Test.php?

A test complains that the class Horde_Kolab_IMAP is not present;
What module provides the class Horde_Kolab_IMAP?

A test complains that the class Horde_Kolab_Server is not present;
What module provides the class Horde_Kolab_Server?
 Is this package http://pear.horde.org/index.php?package=Horde_Kolab_Server 
required?  The same question for Horde_Kolab_Format  (those 2 packages seem to 
he superseeded by just kolab_format and kolab_server, hence my question about 
the ones prefixed with Horde_*).

A test fails because due to the method Horde_Kolab_Server_test::unbind;
What module provides the method Horde_Kolab_Server_test::unbind

What about the module Kolab
http://pear.horde.org/index.php?package=Kolab
Is this needed as well (long time not updated)?

Besides the questions above, there are some test failing although packaging 
wise everything seems okay.  Please have a look at the results file.

Looking forward to your reply(ies).


-- 
Richard
-------------- next part --------------
===>>> /usr/share/php5/PEAR/test/Kolab_Format/Horde/Kolab/Format/AllTests.php (kolab-format-1.0.0-2.2)
PHPUnit 3.3.9 by Sebastian Bergmann.

..PHP Fatal error:  Call to a member function getValue() on a non-object in /srv/www/htdocs/horde/lib/Horde/Prefs/CategoryManager.php on line 26

===>>> /usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/AllTests.php (kolab-freebusy-0.1.2-1.1)
PHP Warning:  require_once(Horde/Kolab/Test.php): failed to open stream: No such file or directory in /usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php on line 17
PHP Fatal error:  require_once(): Failed opening required 'Horde/Kolab/Test.php' (include_path='.:/usr/share/php5:/usr/share/php5/PEAR') in /usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php on line 17

===>>> /usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php (kolab-freebusy-0.1.2-1.1)
PHP Warning:  require_once(Horde/Kolab/Test.php): failed to open stream: No such file or directory in /usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php on line 17
PHP Fatal error:  require_once(): Failed opening required 'Horde/Kolab/Test.php' (include_path='.:/usr/share/php5:/usr/share/php5/PEAR') in /usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php on line 17

===>>> /usr/share/php5/PEAR/Horde/Kolab/IMAP/test.php (kolab-server-0.3.0-2.2)
PHP Fatal error:  Class 'Horde_Kolab_IMAP' not found in /usr/share/php5/PEAR/Horde/Kolab/IMAP/test.php on line 27

===>>> /usr/share/php5/PEAR/Horde/Kolab/Server/test.php (kolab-server-0.3.0-2.2)
PHP Fatal error:  Class 'Horde_Kolab_Server' not found in /srv/www/htdocs/horde/lib/Horde/Kolab/Server/ldap.php on line 27

===>>> /usr/share/php5/PEAR/test/Kolab_Server/Horde/Kolab/Server/AllTests.php (kolab-server-0.3.0-2.2)
PHP Notice:  Use of undefined constant KOLAB_ATTR_KOLABDELEGATE - assumed 'KOLAB_ATTR_KOLABDELEGATE' in /usr/share/php5/PEAR/Horde/Kolab/Test/Server.php on line 399
PHPUnit 3.3.9 by Sebastian Bergmann.

..PHP Fatal error:  Call to undefined method Horde_Kolab_Server_test::unbind() in /usr/share/php5/PEAR/Horde/Kolab/Test/Server.php on line 296

===>>> /usr/share/php5/PEAR/test/Kolab_Storage/Horde/Kolab/Storage/AllTests.php (kolab-storage-0.3.0-1.2)
PHP Warning:  Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of [runtime function name]().  If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in /usr/share/php5/PEAR/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php on line 180
PHP Warning:  Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of [runtime function name]().  If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in /usr/share/php5/PEAR/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php on line 189
PHPUnit 3.3.9 by Sebastian Bergmann.

PHP Fatal error:  Call to undefined method Horde_Kolab_Server_test::unbind() in /usr/share/php5/PEAR/Horde/Kolab/Test/Server.php on line 296

===>>> /usr/share/php5/PEAR/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php (kolab-storage-0.3.0-1.2)
PHP Warning:  Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of [runtime function name]().  If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in /usr/share/php5/PEAR/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php on line 180
PHP Warning:  Call-time pass-by-reference has been deprecated; If you would like to pass it by reference, modify the declaration of [runtime function name]().  If you would like to enable call-time pass-by-reference, you can set allow_call_time_pass_reference to true in your INI file in /usr/share/php5/PEAR/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php on line 189


From kolab-issues at intevation.de  Sat Feb  7 16:46:20 2009
From: kolab-issues at intevation.de (=?utf-8?q?Christian_B=C3=B6ttger?=)
Date: Sat, 07 Feb 2009 15:46:20 +0000
Subject: [Kolab-devel] [issue3393] kolab install on Debian 4.0 fails
Message-ID: <1234021580.1.0.295225530392.issue3393@intevation.de>


New submission from Christian B?ttger <c at boettger.cc>:

Environemtn Environment: fresh Debian 4.0 install
Kolab packages installed via apt-get from debian repositories
same for slapd etc

apt-get gives nor errors

1. error: /etc/apache2/sites-enabled/kolab is there, apache restarted, but:
nothing listens on port 443

2. error: /usr/share/kolabd/kolab-bootstrap -b
asks the usual questions, then wants to start a temporary slapd and dies:
kolab:/usr/share/kolabd# ./kolab_bootstrap -b

KOLAB BOOTSTRAP

Check for running webserver on port 80
Check for running webserver on port 443
Check for running imap server on port 143
Check for running imap server on port 220
Check for running imap server on port 585
Check for running imap server on port 993
Check for running pop3 server on port 109
Check for running pop3 server on port 110
Check for running pop3 server on port 473
Check for running pop3 server on port 995
Check for running smtp server on port 25
Check for running smtp server on port 465
Check for running ftp server on port 21
Check for running Amavis Virus Scanner Interface on port 10024
Check for running Kolab daemon on port 9999
Check for running OpenLDAP server on port 636
Check for running OpenLDAP server on port 389
Check for running Sieve server on port 2000
Excellent all required Ports are available!
LDAP repository is empty - assuming fresh install
Please enter Hostname including Domain Name (e.g. thishost.domain.tld) [kolab]:
kolab.wombat.han.de
Proceeding with Hostname kolab.wombat.han.de
Do you want to set up (1) a master Kolab server or (2) a slave [1] (1/2): 1
Proceeding with master server setup

Please enter your Maildomain - if you do not know your mail domain use the fqdn
from above [wombat.han.de]: boettger.cc
proceeding with Maildomain boettger.cc
Kolab primary email addresses will be of the type user at boettger.cc
Generating default configuration:
 base_dn : dc=boettger,dc=cc
 bind_dn : cn=manager,cn=internal,dc=boettger,dc=cc
Please choose a manager password [413i8dU19+BZlp2k]: taskaf
 bind_pw : XXXXXX
done modifying /etc/kolab/kolab.conf

IMPORTANT NOTE:
use login=manager and passwd=XXXXXX when you log into the webinterface!

Enter fully qualified hostname of slave kolab server e.g. thishost.domain.tld
[empty when done]:
prepare LDAP database...
temporarily starting slapd
Could not start temporary slapd at ./kolab_bootstrap line 437.
kolab:/usr/share/kolabd#

How to proceed?

How to debug this?

----------
messages: 18479
nosy: bofh42
priority: bug
status: unread
title: kolab install on Debian 4.0 fails
topic: debian, release, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3393>
___________________________________________________


From ml at radoeka.nl  Sat Feb  7 17:08:55 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sat, 7 Feb 2009 17:08:55 +0100
Subject: [Kolab-devel] [issue3393] kolab install on Debian 4.0 fails
In-Reply-To: <1234021580.1.0.295225530392.issue3393@intevation.de>
References: <1234021580.1.0.295225530392.issue3393@intevation.de>
Message-ID: <200902071708.56477.ml@radoeka.nl>

Op zaterdag 07 februari 2009 16:46:20 schreef Christian B?ttger:
> Enter fully qualified hostname of slave kolab server e.g.
> thishost.domain.tld [empty when done]:
> prepare LDAP database...
> temporarily starting slapd
> Could not start temporary slapd at ./kolab_bootstrap line 437.
> kolab:/usr/share/kolabd#
>
> How to proceed?

Hack the kolab_bootstrap script to determine the call to start slapd (so that 
will be around line 437, or just read the script and determine the arguments 
your exit.  At that point start slapd bug with (-d 255 (full debug)).  
Hopefully, this tells you what goes wrong (perhaps you can also add -d 255 to 
the slapd call).  It is also possible to increase the log_level in kolab.conf.  
I hope that you get an idea what you can at this point.

-- 
Richard


From tom at thomasbaumann.com  Sat Feb  7 22:17:56 2009
From: tom at thomasbaumann.com (Thomas Baumann)
Date: Sat, 07 Feb 2009 22:17:56 +0100
Subject: [Kolab-devel] HORDE - Failed identifying the UID of the Kolab
	user	thomas.baumann. Error was: Unable to bind to the LDAP
	server as	cn=nobody, cn=internal, dc=example, dc=com
Message-ID: <20090207221756.ilysamtzscgkwgcg@ox.thomasbaumann.com>

Hello list,

I recently setup current kolab with 2.2-beta, and tried to login into
horde, but I cannot login.

I always get the following error:

Failed identifying the UID of the Kolab user {USERNAME}. Error was:
Unable to bind to the LDAP server as
cn=nobody,cn=internal,dc={DOMAIN},dc={TLD}!

I even tried to set a new manager password with

/kolab/bin/kolabpasswd

but with no success in Horde.

Hope I get a hint how to login.

Thanks for your reply in advance.

Thomas.

--
B?cher und mehr im Internet - meine neue Site: http://www.1-search.de  
- Viel Spass!

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


From kolab-issues at intevation.de  Mon Feb  9 09:59:29 2009
From: kolab-issues at intevation.de (Enrico)
Date: Mon, 09 Feb 2009 08:59:29 +0000
Subject: [Kolab-devel] [issue3394] Cannot delete users
Message-ID: <1234169968.97.0.147716346897.issue3394@intevation.de>


New submission from Enrico <ezaffa at gmail.com>:

Hi all, when deleting a user with admin interface the user stay in "awaiting
cleanup" status. Already tried to stop and restart kolabd, to delete
/kolab/var/kolab/mailbox-uidcache.db and restart again but user stay in
"awaiting" state. I'm able to delete users from command line with 'ldapdelete'.
This is a kolab 2.2 self compiled on ubuntu 8.0.4 x86_64, on a Pentium D 3Ghz,
in production with ~30 users.

----------
messages: 18486
nosy: ezaffa
priority: urgent
status: unread
title: Cannot delete users
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3394>
___________________________________________________


From bernhard at intevation.de  Mon Feb  9 12:10:02 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 9 Feb 2009 12:10:02 +0100
Subject: [Kolab-devel] Kolab Server/Debian where to report issues?
Message-ID: <200902091210.05727.bernhard@intevation.de>

The creation of kolab/issue3393 (Kolab Server/Debian Install failure for Etch)
reminds that we need to write down some hints 
where to report Kolab Server/Debian issues
and to guide users towards this.

I've know closed issue3393 with:

> This is Kolab Server/Debian which is in development and
> not officially support so far,  please report to the Debian group. (
> Or help with the development on kolab-devel@ or the corresponding Debian
> group.)
>
> For a stable server right now try Kolab Server/OpenPKG which
> is know to run nicely on Debian Etch.

I cannot say in what state Kolab Server/Debian currently is
and if there is a group being actively about it?

Mathieu, @All, what do you think?



-- 
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/20090209/018524a7/attachment.bin

From math.parent at gmail.com  Mon Feb  9 14:50:44 2009
From: math.parent at gmail.com (Mathieu Parent)
Date: Mon, 9 Feb 2009 14:50:44 +0100
Subject: [Kolab-devel] Kolab Server/Debian where to report issues?
In-Reply-To: <200902091210.05727.bernhard@intevation.de>
References: <200902091210.05727.bernhard@intevation.de>
Message-ID: <960738410902090550l3399a6dcof26e8279606f1a36@mail.gmail.com>

(adding pkg-kolab to cc)

On Mon, Feb 9, 2009 at 12:10 PM, Bernhard Reiter <bernhard at intevation.de> wrote:
> The creation of kolab/issue3393 (Kolab Server/Debian Install failure for Etch)
> reminds that we need to write down some hints
> where to report Kolab Server/Debian issues
> and to guide users towards this.
>
> I've know closed issue3393 with:
>
>> This is Kolab Server/Debian which is in development and
>> not officially support so far,  please report to the Debian group. (
>> Or help with the development on kolab-devel@ or the corresponding Debian
>> group.)
>>
>> For a stable server right now try Kolab Server/OpenPKG which
>> is know to run nicely on Debian Etch.

Good

> I cannot say in what state Kolab Server/Debian currently is

Kolab server will unfortunately not be in lenny (it took to much time
to upload it), but the cyrus-kolab-* are.

Current packages in unstable, 2.2.0, are stable ;). They are intended
for lenny but probably work for etch also (not tested). Kolab server
is feature equivalent to OpenPKG packages (IMHO), without Kolab horde
web client. Upgrading from etch should work (more testing is needed).

I have prepared kolab server 2.2.1beta1 packages. They are stable and
feature equivalent to OpenPKG packages. I have added a new
kolab-webclient package. It works but:
- it doesn't use latest horde versions
(<http://qa.debian.org/developer.php?login=pkg-horde-hackers at lists.alioth.debian.org>)
- it doesn't include all kolab specific patches
So, it is not completely feature complete, but I don't know what is
missing (feel free to make a list)

Installation instructions are here:
<https://wiki.kolab.org/index.php/Debian_-_natively>

> and if there is a group being actively about it?

We, the maintainers of "Debian-native Kolab" packages, are in a team
(<http://wiki.debian.org/Teams/pkg-kolab>). Currently, I am the only
regular committer (help is appreciated), but there are several testers
(thanks!).

> Mathieu, @All, what do you think?
>

I have updated some pages on the kolab wiki about how to report
problems in native packages:
<https://wiki.kolab.org/index.php/Problem_reporting> is the entry
point, and links to
<https://wiki.kolab.org/index.php/Debian_-_Problem_reporting>.

So the process for Debian native is as follow:
* Take a look at open bugs
[http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=maint&data=pkg-kolab-devel%40lists.alioth.debian.org&archive=no&raw=yes&bug-rev=yes&pend-exc=fixed&pend-exc=done
].
* browse the Archives
[http://lists.alioth.debian.org/pipermail/pkg-kolab-devel/
pkg-kolab-devel ]
* ask on pkg-kolab-devel
[http://lists.alioth.debian.org/mailman/listinfo/pkg-kolab-devel
pkg-kolab-devel ]
* fill a bug in Debian bug tracking system [http://bugs.debian.org/ ]

Mathieu Parent


From wrobel at pardus.de  Mon Feb  9 16:50:07 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Mon, 09 Feb 2009 16:50:07 +0100
Subject: [Kolab-devel] Kolab Server/Debian where to report issues?
In-Reply-To: <960738410902090550l3399a6dcof26e8279606f1a36@mail.gmail.com>
References: <200902091210.05727.bernhard@intevation.de>
	<960738410902090550l3399a6dcof26e8279606f1a36@mail.gmail.com>
Message-ID: <20090209165007.17386abmcdjcw04k@webmail.pardus.de>

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

> (adding pkg-kolab to cc)
>
> On Mon, Feb 9, 2009 at 12:10 PM, Bernhard Reiter  
> <bernhard at intevation.de> wrote:
>> The creation of kolab/issue3393 (Kolab Server/Debian Install  
>> failure for Etch)
>> reminds that we need to write down some hints
>> where to report Kolab Server/Debian issues
>> and to guide users towards this.
>>
>> I've know closed issue3393 with:
>>
>>> This is Kolab Server/Debian which is in development and
>>> not officially support so far,  please report to the Debian group. (
>>> Or help with the development on kolab-devel@ or the corresponding Debian
>>> group.)
>>>
>>> For a stable server right now try Kolab Server/OpenPKG which
>>> is know to run nicely on Debian Etch.
>
> Good
>
>> I cannot say in what state Kolab Server/Debian currently is
>
> Kolab server will unfortunately not be in lenny (it took to much time
> to upload it), but the cyrus-kolab-* are.
>
> Current packages in unstable, 2.2.0, are stable ;). They are intended
> for lenny but probably work for etch also (not tested). Kolab server
> is feature equivalent to OpenPKG packages (IMHO), without Kolab horde
> web client. Upgrading from etch should work (more testing is needed).
>
> I have prepared kolab server 2.2.1beta1 packages. They are stable and
> feature equivalent to OpenPKG packages. I have added a new
> kolab-webclient package. It works but:
> - it doesn't use latest horde versions
> (<http://qa.debian.org/developer.php?login=pkg-horde-hackers at lists.alioth.debian.org>)
> - it doesn't include all kolab specific patches
> So, it is not completely feature complete, but I don't know what is
> missing (feel free to make a list)
>
> Installation instructions are here:
> <https://wiki.kolab.org/index.php/Debian_-_natively>
>
>> and if there is a group being actively about it?
>
> We, the maintainers of "Debian-native Kolab" packages, are in a team
> (<http://wiki.debian.org/Teams/pkg-kolab>). Currently, I am the only
> regular committer (help is appreciated), but there are several testers
> (thanks!).
>
>> Mathieu, @All, what do you think?
>>
>
> I have updated some pages on the kolab wiki about how to report
> problems in native packages:
> <https://wiki.kolab.org/index.php/Problem_reporting> is the entry
> point, and links to
> <https://wiki.kolab.org/index.php/Debian_-_Problem_reporting>.
>
> So the process for Debian native is as follow:
> * Take a look at open bugs
> [http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=maint&data=pkg-kolab-devel%40lists.alioth.debian.org&archive=no&raw=yes&bug-rev=yes&pend-exc=fixed&pend-exc=done
> ].
> * browse the Archives
> [http://lists.alioth.debian.org/pipermail/pkg-kolab-devel/
> pkg-kolab-devel ]
> * ask on pkg-kolab-devel
> [http://lists.alioth.debian.org/mailman/listinfo/pkg-kolab-devel
> pkg-kolab-devel ]
> * fill a bug in Debian bug tracking system [http://bugs.debian.org/ ]

Just wanted to say thanks for all the work and effort you put into this!

Cheers,

Gunnar

>
> Mathieu Parent
>
> _______________________________________________
> 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/20090209/83ce4905/attachment.bin

From wrobel at pardus.de  Mon Feb  9 17:30:51 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Mon, 09 Feb 2009 17:30:51 +0100
Subject: [Kolab-devel] HORDE - Failed identifying the UID of the
	Kolab	user	thomas.baumann. Error was: Unable to bind to the
	LDAP server	as	cn=nobody, cn=internal, dc=example, dc=com
In-Reply-To: <20090207221756.ilysamtzscgkwgcg@ox.thomasbaumann.com>
References: <20090207221756.ilysamtzscgkwgcg@ox.thomasbaumann.com>
Message-ID: <20090209173051.30122j0gig0ro50k@webmail.pardus.de>

Quoting Thomas Baumann <tom at thomasbaumann.com>:

> Hello list,
>
> I recently setup current kolab with 2.2-beta, and tried to login into
> horde, but I cannot login.
>
> I always get the following error:
>
> Failed identifying the UID of the Kolab user {USERNAME}. Error was:
> Unable to bind to the LDAP server as
> cn=nobody,cn=internal,dc={DOMAIN},dc={TLD}!
>
> I even tried to set a new manager password with
>
> /kolab/bin/kolabpasswd
>
> but with no success in Horde.
>
> Hope I get a hint how to login.

Did the configuration templates get correctly written into config  
files and does /kolab/var/kolab/www/client/config/kolab.php look right?

Cheers,

Gunnar

>
> Thanks for your reply in advance.
>
> Thomas.
>
> --
> B?cher und mehr im Internet - meine neue Site: http://www.1-search.de
> - Viel Spass!
>
> ----------------------------------------------------------------
> 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/20090209/6823b188/attachment.bin

From wrobel at pardus.de  Mon Feb  9 17:37:33 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Mon, 09 Feb 2009 17:37:33 +0100
Subject: [Kolab-devel] Failing php tests for kolab
In-Reply-To: <200902071511.47447.ml@radoeka.nl>
References: <200902071511.47447.ml@radoeka.nl>
Message-ID: <20090209173733.49601h8zufubyzms@webmail.pardus.de>

Quoting Richard Bos <ml at radoeka.nl>:

> Hi,
>
> I just ran tests that come with the kolab pear packages and some tests are
> failing.  Hence I have some questions related to this.  Please find the
> failing tests in the attachment.  This is btw on native openSUSE_11.1
>
> Tests seem to fail because the file Horde/Kolab/Test.php is not present;
> What module provides the file Horde/Kolab/Test.php?

That file has been removed. I think some of the tests need to be fixed  
upstream. I hope to be able to look at that soon.

>
> A test complains that the class Horde_Kolab_IMAP is not present;
> What module provides the class Horde_Kolab_IMAP?
>
> A test complains that the class Horde_Kolab_Server is not present;
> What module provides the class Horde_Kolab_Server?
>  Is this package http://pear.horde.org/index.php?package=Horde_Kolab_Server
> required?  The same question for Horde_Kolab_Format  (those 2  
> packages seem to
> he superseeded by just kolab_format and kolab_server, hence my question about
> the ones prefixed with Horde_*).

The Horde_Kolab_* packages are indeed deprecated. Only the Kolab_*  
ones are relevant.

>
> A test fails because due to the method Horde_Kolab_Server_test::unbind;
> What module provides the method Horde_Kolab_Server_test::unbind
>
> What about the module Kolab
> http://pear.horde.org/index.php?package=Kolab
> Is this needed as well (long time not updated)?

It is only needed within the webclient for backwards compatibility.  
Otherwise it is deprecated and will get removed within Horde 4.

>
> Besides the questions above, there are some test failing although packaging
> wise everything seems okay.  Please have a look at the results file.
>
> Looking forward to your reply(ies).
>
>
> --
> Richard
>

Cheers,

Gunnar

-- 
______ 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 ml at radoeka.nl  Mon Feb  9 23:01:29 2009
From: ml at radoeka.nl (Richard Bos)
Date: Mon, 9 Feb 2009 23:01:29 +0100
Subject: [Kolab-devel] Failing php tests for kolab
In-Reply-To: <20090209173733.49601h8zufubyzms@webmail.pardus.de>
References: <200902071511.47447.ml@radoeka.nl>
	<20090209173733.49601h8zufubyzms@webmail.pardus.de>
Message-ID: <200902092301.30214.ml@radoeka.nl>

Hi,

Op maandag 09 februari 2009 17:37:33 schreef Gunnar Wrobel:
> > Tests seem to fail because the file Horde/Kolab/Test.php is not present;
> > What module provides the file Horde/Kolab/Test.php?
>
> That file has been removed. I think some of the tests need to be fixed  
> upstream. I hope to be able to look at that soon.

That would be nice, as it gives a good indication about the installed packages 
(good or bad).


> > A test complains that the class Horde_Kolab_IMAP is not present;
> > What module provides the class Horde_Kolab_IMAP?
> >
> > A test complains that the class Horde_Kolab_Server is not present;
> > What module provides the class Horde_Kolab_Server?
> >  Is this package
> > http://pear.horde.org/index.php?package=Horde_Kolab_Server required?  The
> > same question for Horde_Kolab_Format  (those 2
> > packages seem to
> > he superseeded by just kolab_format and kolab_server, hence my question
> > about the ones prefixed with Horde_*).
>
> The Horde_Kolab_* packages are indeed deprecated. Only the Kolab_*  
> ones are relevant.

Is the same reply valid as you made before, that you may have a look at it 
soon?


> > A test fails because due to the method Horde_Kolab_Server_test::unbind;
> > What module provides the method Horde_Kolab_Server_test::unbind
> >
> > What about the module Kolab
> > http://pear.horde.org/index.php?package=Kolab
> > Is this needed as well (long time not updated)?
>
> It is only needed within the webclient for backwards compatibility.  
> Otherwise it is deprecated and will get removed within Horde 4.

Ah I see.  I did not arrive at packaging the webclient yet.  Might I conclude 
from the non failing tests that my current installation of the kolab packages 
from pear.horde.org and their required horde modules is okay?  It looks like 
many tests are pass and the tests that fail do fail because the test is to be 
updated, is that correct?  If this is really true I can go on to the next 
hurdle like installation kolab-webadmin and kolabd :)


-- 
Richard


From bernhard at intevation.de  Tue Feb 10 09:02:04 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 10 Feb 2009 09:02:04 +0100
Subject: [Kolab-devel] Kolab Server/Debian where to report issues?
In-Reply-To: <960738410902090550l3399a6dcof26e8279606f1a36@mail.gmail.com>
References: <200902091210.05727.bernhard@intevation.de>
	<960738410902090550l3399a6dcof26e8279606f1a36@mail.gmail.com>
Message-ID: <200902100902.04793.bernhard@intevation.de>

Mathieu,

On Montag, 9. Februar 2009, Mathieu Parent wrote:
> > and if there is a group being actively about it?
>
> We, the maintainers of "Debian-native Kolab" packages, are in a team
> (<http://wiki.debian.org/Teams/pkg-kolab>). Currently, I am the only
> regular committer (help is appreciated), but there are several testers
> (thanks!).

I saw the team and I appreciate your work!
So a big THANK YOU! :)

Given that you are on kolab-devel@ I think a few of the most
active people from your team should be here to coordinate.
Kolab-devel@ is the highest coordination list we currently have.

About the team label, are you aiming for full "Kolab" (including the KDE Kolab 
Client, the Webclient and the Kolab Server)?
I am trying to be more precise about this, because the Kolab solution requires 
smart clients to work as a groupware solution. 
So it would be coll to call the server "Kolab Server" most of the time.

> I have updated some pages on the kolab wiki about how to report
> problems in native packages:
> <https://wiki.kolab.org/index.php/Problem_reporting> is the entry
> point, and links to
> <https://wiki.kolab.org/index.php/Debian_-_Problem_reporting>.

I saw it, cool!
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/20090210/8f6b0376/attachment.bin

From math.parent at gmail.com  Tue Feb 10 10:46:54 2009
From: math.parent at gmail.com (Mathieu Parent)
Date: Tue, 10 Feb 2009 10:46:54 +0100
Subject: [Kolab-devel] Kolab Server/Debian where to report issues? - and
	some news about annotatemore
Message-ID: <960738410902100146j410b6652y3c7943492dfc386b@mail.gmail.com>

Hi,


On Tue, Feb 10, 2009 at 9:02 AM, Bernhard Reiter <bernhard at intevation.de> wrote:
> Mathieu,
>
> On Montag, 9. Februar 2009, Mathieu Parent wrote:
>> > and if there is a group being actively about it?
>>
>> We, the maintainers of "Debian-native Kolab" packages, are in a team
>> (<http://wiki.debian.org/Teams/pkg-kolab>). Currently, I am the only
>> regular committer (help is appreciated), but there are several testers
>> (thanks!).
>
> I saw the team and I appreciate your work!
> So a big THANK YOU! :)

You're welcome

>
> Given that you are on kolab-devel@ I think a few of the most
> active people from your team should be here to coordinate.
> Kolab-devel@ is the highest coordination list we currently have.

Agree

> About the team label, are you aiming for full "Kolab" (including the KDE Kolab
> Client, the Webclient and the Kolab Server)?
> I am trying to be more precise about this, because the Kolab solution requires
> smart clients to work as a groupware solution.
> So it would be coll to call the server "Kolab Server" most of the time.

Here is the current state of kolab related packages in Debian:

The pkg-kolab team is maintaining kolab-cyrus (cyrus 2.2 with kolab
patches), kolab server (including kolab-webadmin), kolabadmin (seems
to be unmaintained upstream) and kolab-webclient. So it is "Kolab
server" and "Kolab web client".

The 'Debian Qt/KDE Maintainers' is maintaining kdepim (version 3.5.9
and 4.2.0 currently, see
<http://packages.qa.debian.org/k/kdepim.html>). This is not the kolab
branch, so as for kolab-webclient, some features are missing. The
pkg-kolab mailing list is the good place to talk about these missing
features to coordinate effort.

The 'Thunderbird Plugin: SyncKolab' is not packaged in debian, but it
is easy to install, as an addon.

Also, uw-imap libc-client and php5-map are not patched for annotations
(see http://bugs.debian.org/456947 and http://bugs.debian.org/456591),
kolab code is falling back to slower PEAR code. As the RFC
annotatemore is now a proposed standard
(<http://mailman.rfc-editor.org/pipermail/rfc-dist/2009-February/002184.html>),
it may be implemented upstream soon.

The php-imap 'myright' patch is not included in Debian (please vote
for http://bugs.php.net/bug.php?id=43948). There is no bug in Debian
BTS, TODO.

Postfix is up to date.

perl-ldap (libnet-ldap-perl) is up to date in unstable (not in lenny).

>> I have updated some pages on the kolab wiki about how to report
>> problems in native packages:
>> <https://wiki.kolab.org/index.php/Problem_reporting> is the entry
>> point, and links to
>> <https://wiki.kolab.org/index.php/Debian_-_Problem_reporting>.
>
> I saw it, cool!
> Bernhard
>
>

Mathieu Parent


From kolab-issues at intevation.de  Tue Feb 10 21:13:35 2009
From: kolab-issues at intevation.de (Doloritas)
Date: Tue, 10 Feb 2009 20:13:35 +0000
Subject: [Kolab-devel] [issue3395] 5 geile F-otzen zeigen sich
Message-ID: <7A844C5F.A5A8C9DF@vectranet.pl>


New submission from Doloritas <susanne71_2000gypom at vectranet.pl>:

Hallo mein g-eiler Sch-atz, mein Name ist SHERIN. Ich bin eine romantische
Kuschelkatze aber mutiere im Bett zu eine hungrigen Wildkatze! Ich stehe auf
Bodenstaendige Maenner, gerne mit einem Baeuchlein. Mir ist nur wichtig das
Du mich wie eine Prinzessin behandelst um ich befriedigen kannst, denn im
Bett bin ich einfach unersaettlich! Bei er0tischen Massagen bei Kerzenschein
werde ich sofort schwach. Dann will ich dich unbedingt und zwar hart und
stark, ich will deinen harten Kolben in mir spueren und liebe es wenn Du mir
gleichzeitig den Hintern mit Deinen Haenden verwoehnst. Da kann ich mich
nicht mehr halten und komme lustvoll Iive im ch-at!

Blutjunges T.eenie live...
Einfach folgende URL in Deinen Browser tippen:

www . playboybunny-feucht . net

----------
messages: 18532
nosy: susanne71_2000gypom
status: unread
title: 5 geile F-otzen zeigen sich
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3395>
___________________________________________________


From kolab-issues at intevation.de  Tue Feb 10 22:15:30 2009
From: kolab-issues at intevation.de (Ravetti Malas)
Date: Tue, 10 Feb 2009 21:15:30 +0000
Subject: [Kolab-devel] [issue3396] Message Alert - You Have 1 Important
	Unread MMessage
Message-ID: <7733021557.20090210211336@hdtechnics.nl>


New submission from Ravetti Malas <southeastern at hdtechnics.nl>:

How To Impress Your Girlffriend
  http://cid-9cd3f1d3fa388b77.spaces.live.com/blog/cns!9CD3F1D3FA388B77!106entry

Into no. Come now, my dears, what struck you first this large
vote was all the more noteworthy because wrote one of their
prominent men, that before was fortunately able to speak
just before he died, funeral. She left to get their orders.
wonder.

----------
messages: 18533
nosy: southeastern
status: unread
title: Message Alert - You Have 1 Important Unread MMessage
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3396>
___________________________________________________


From bernhard at intevation.de  Wed Feb 11 10:08:49 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 11 Feb 2009 10:08:49 +0100
Subject: [Kolab-devel] Kolab Server/Debian where to report issues? - and
	some news about annotatemore
In-Reply-To: <960738410902100146j410b6652y3c7943492dfc386b@mail.gmail.com>
References: <960738410902100146j410b6652y3c7943492dfc386b@mail.gmail.com>
Message-ID: <200902111008.49488.bernhard@intevation.de>

On Dienstag, 10. Februar 2009, Mathieu Parent wrote:
> Here is the current state of kolab related packages in Debian:

Thanks for the good overview.

> The pkg-kolab team is maintaining kolab-cyrus (cyrus 2.2 with kolab
> patches), kolab server (including kolab-webadmin), kolabadmin (seems
> to be unmaintained upstream) and kolab-webclient. So it is "Kolab
> server" and "Kolab web client".

What do you mean by kolabadmin being unmainteind by upstream? 
(At least the Kolab Server Webadministration is maintained by us on 
kolab-devel at . Is this something else or the same? )

> The 'Debian Qt/KDE Maintainers' is maintaining kdepim (version 3.5.9
> and 4.2.0 currently, see
> <http://packages.qa.debian.org/k/kdepim.html>). This is not the kolab
> branch, 

Ah, we should point them towards using the "enterprise" branches.
"enterprise" is for KDE 3.5.X, we call is "e35"
and "enterprise4" (e4) is for KDE 4.X.

> so as for kolab-webclient, some features are missing. The 
> pkg-kolab mailing list is the good place to talk about these missing
> features to coordinate effort.



-- 
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/20090211/4d65a34b/attachment.bin

From wrobel at pardus.de  Wed Feb 11 10:52:12 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 11 Feb 2009 10:52:12 +0100
Subject: [Kolab-devel] Failing php tests for kolab
In-Reply-To: <200902092301.30214.ml@radoeka.nl>
References: <200902071511.47447.ml@radoeka.nl>
	<20090209173733.49601h8zufubyzms@webmail.pardus.de>
	<200902092301.30214.ml@radoeka.nl>
Message-ID: <20090211105212.4544752lbq57bfwo@webmail.pardus.de>

Quoting Richard Bos <ml at radoeka.nl>:

> Hi,
>
> Op maandag 09 februari 2009 17:37:33 schreef Gunnar Wrobel:
>> > Tests seem to fail because the file Horde/Kolab/Test.php is not present;
>> > What module provides the file Horde/Kolab/Test.php?
>>
>> That file has been removed. I think some of the tests need to be fixed
>> upstream. I hope to be able to look at that soon.
>
> That would be nice, as it gives a good indication about the  
> installed packages
> (good or bad).

I actually intend to do way more than this in the long run. Currently  
the tests are testing the base integrity of the packages and use some  
mockup LDAP and IMAP classes that simulate the backend provided by the  
Kolab Server.

After fixing these basic tests I would like to extend them with real  
Server tests that you should be able to run to test the Server  
functionality of a correctly bootstrapped machine.

The final step would be selenium based frontend test for the web  
client. I currently intend to support the web client version we  
currently use for the next two or three years so these tests would be  
extremely handy for automatic checking when we add new patches.

Let's how long it takes me to get there :)

>
>
>> > A test complains that the class Horde_Kolab_IMAP is not present;
>> > What module provides the class Horde_Kolab_IMAP?
>> >
>> > A test complains that the class Horde_Kolab_Server is not present;
>> > What module provides the class Horde_Kolab_Server?
>> >  Is this package
>> > http://pear.horde.org/index.php?package=Horde_Kolab_Server required?  The
>> > same question for Horde_Kolab_Format  (those 2
>> > packages seem to
>> > he superseeded by just kolab_format and kolab_server, hence my question
>> > about the ones prefixed with Horde_*).
>>
>> The Horde_Kolab_* packages are indeed deprecated. Only the Kolab_*
>> ones are relevant.
>
> Is the same reply valid as you made before, that you may have a look at it
> soon?

I won't do anything concerning this. The Horde_Kolab_* packages are  
deprecated and there is not much more to say about this :)

>
>
>> > A test fails because due to the method Horde_Kolab_Server_test::unbind;
>> > What module provides the method Horde_Kolab_Server_test::unbind
>> >
>> > What about the module Kolab
>> > http://pear.horde.org/index.php?package=Kolab
>> > Is this needed as well (long time not updated)?
>>
>> It is only needed within the webclient for backwards compatibility.
>> Otherwise it is deprecated and will get removed within Horde 4.
>
> Ah I see.  I did not arrive at packaging the webclient yet.  Might I conclude
> from the non failing tests that my current installation of the kolab packages
> from pear.horde.org and their required horde modules is okay?  It looks like
> many tests are pass and the tests that fail do fail because the test is to be
> updated, is that correct?

Yes. If most tests succeed you should indeed be fine.

> If this is really true I can go on to the next
> hurdle like installation kolab-webadmin and kolabd :)

Good luck ;)

Cheers,

Gunnar

>
>
> --
> Richard
>
> _______________________________________________
> 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/20090211/c8309cf4/attachment.bin

From wrobel at pardus.de  Wed Feb 11 11:16:00 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 11 Feb 2009 11:16:00 +0100
Subject: [Kolab-devel] kolabadmin (was: Kolab Server/Debian where to
	report issues? -	and some news about annotatemore)
In-Reply-To: <200902111008.49488.bernhard@intevation.de>
References: <960738410902100146j410b6652y3c7943492dfc386b@mail.gmail.com>
	<200902111008.49488.bernhard@intevation.de>
Message-ID: <20090211111600.18041ra2zg2h2vlw@webmail.pardus.de>

Quoting Bernhard Reiter <bernhard at intevation.de>:

> On Dienstag, 10. Februar 2009, Mathieu Parent wrote:
>> Here is the current state of kolab related packages in Debian:
>
> Thanks for the good overview.
>
>> The pkg-kolab team is maintaining kolab-cyrus (cyrus 2.2 with kolab
>> patches), kolab server (including kolab-webadmin), kolabadmin (seems
>> to be unmaintained upstream)

I think this refers to a cool Qt based app that provided the same  
functionality that the kolab-webadmin offers. I liked it too but the  
project activity vanished as quickly as it appeared. Is the source  
still accessible somewhere? It might be interesting to maintain it  
within one of the Kolab repositories.

Cheers,

Gunnar

>> and kolab-webclient. So it is "Kolab
>> server" and "Kolab web client".
>
> What do you mean by kolabadmin being unmainteind by upstream?
> (At least the Kolab Server Webadministration is maintained by us on
> kolab-devel at . Is this something else or the same? )
>
>> The 'Debian Qt/KDE Maintainers' is maintaining kdepim (version 3.5.9
>> and 4.2.0 currently, see
>> <http://packages.qa.debian.org/k/kdepim.html>). This is not the kolab
>> branch,
>
> Ah, we should point them towards using the "enterprise" branches.
> "enterprise" is for KDE 3.5.X, we call is "e35"
> and "enterprise4" (e4) is for KDE 4.X.
>
>> so as for kolab-webclient, some features are missing. The
>> pkg-kolab mailing list is the good place to talk about these missing
>> features to coordinate effort.
>
>
>
> --
> 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/20090211/328debbb/attachment.bin

From math.parent at gmail.com  Wed Feb 11 13:45:06 2009
From: math.parent at gmail.com (Mathieu Parent)
Date: Wed, 11 Feb 2009 13:45:06 +0100
Subject: [Kolab-devel] kolabadmin (was: Kolab Server/Debian where to
	report issues? - and some news about annotatemore)
In-Reply-To: <20090211111600.18041ra2zg2h2vlw@webmail.pardus.de>
References: <960738410902100146j410b6652y3c7943492dfc386b@mail.gmail.com>
	<200902111008.49488.bernhard@intevation.de>
	<20090211111600.18041ra2zg2h2vlw@webmail.pardus.de>
Message-ID: <960738410902110445i38cff19ej97013c82e4c57afc@mail.gmail.com>

On Wed, Feb 11, 2009 at 11:16 AM, Gunnar Wrobel <wrobel at pardus.de> wrote:
> Quoting Bernhard Reiter <bernhard at intevation.de>:
>
>> On Dienstag, 10. Februar 2009, Mathieu Parent wrote:
>>>
>>> Here is the current state of kolab related packages in Debian:
>>
>> Thanks for the good overview.
>>
>>> The pkg-kolab team is maintaining kolab-cyrus (cyrus 2.2 with kolab
>>> patches), kolab server (including kolab-webadmin), kolabadmin (seems
>>> to be unmaintained upstream)
>
> I think this refers to a cool Qt based app that provided the same
> functionality that the kolab-webadmin offers. I liked it too but the project
> activity vanished as quickly as it appeared. Is the source still accessible
> somewhere? It might be interesting to maintain it within one of the Kolab
> repositories.

The source is copied in the debian archive:
http://ftp.debian.org/debian/pool/main/k/kolabadmin/

current is: http://ftp.debian.org/debian/pool/main/k/kolabadmin/kolabadmin_0.0.20080222.orig.tar.gz

Mathieu Parent


From kolab-issues at intevation.de  Wed Feb 11 15:43:34 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 11 Feb 2009 14:43:34 +0000
Subject: [Kolab-devel] [issue3397] reminder of an event which is added to a
	new local resource doesn't appear.
Message-ID: <1234363414.51.0.845292023077.issue3397@intevation.de>


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

enterprise35 kdepim 20090206.922263(kk2) + patch of kolab/issue3385

To reproduce:
1. Switch to the calendar plugin.
2. Add a new local resource.
3. Create an event with alarm.
4. Wait on the alarm.
But: the reminder won't appear.

----------
assignedto: allen
messages: 18538
nosy: allen, bernhard, bh, ludwig
priority: bug
status: unread
title: reminder of an event which is added to a new local resource doesn't appear.
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3397>
___________________________________________________


From bernhard at intevation.de  Thu Feb 12 09:55:50 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 12 Feb 2009 09:55:50 +0100
Subject: [Kolab-devel] kolabadmin (was: Kolab Server/Debian where to
	report issues? - and some news about annotatemore)
In-Reply-To: <960738410902110445i38cff19ej97013c82e4c57afc@mail.gmail.com>
References: <960738410902100146j410b6652y3c7943492dfc386b@mail.gmail.com>
	<20090211111600.18041ra2zg2h2vlw@webmail.pardus.de>
	<960738410902110445i38cff19ej97013c82e4c57afc@mail.gmail.com>
Message-ID: <200902120955.50614.bernhard@intevation.de>

On Mittwoch, 11. Februar 2009, Mathieu Parent wrote:
> kolabadmin (seems
>
> >>> to be unmaintained upstream)
> >
> > I think this refers to a cool Qt based app that provided the same
> > functionality that the kolab-webadmin offers. I liked it too but the
> > project activity vanished as quickly as it appeared. Is the source still
> > accessible somewhere? It might be interesting to maintain it within one
> > of the Kolab repositories.
>
> The source is copied in the debian archive:
> http://ftp.debian.org/debian/pool/main/k/kolabadmin/
>
> current is:
> http://ftp.debian.org/debian/pool/main/k/kolabadmin/kolabadmin_0.0.20080222
>.orig.tar.gz

Ah, okay. I never tried this.




-- 
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/20090212/6d1bcd7a/attachment.bin

From kolab-issues at intevation.de  Thu Feb 12 13:56:36 2009
From: kolab-issues at intevation.de (Mathieu Parent)
Date: Thu, 12 Feb 2009 12:56:36 +0000
Subject: [Kolab-devel] [issue3398] kolabd fails when folders name contains
	special characters
Message-ID: <1234443396.28.0.350322880051.issue3398@intevation.de>


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

Currently, the kolab web admin doesn't avoid entering special characters (like
"!") in names.

probably two things to consider:
- kolab web admin should control data entered
- kolabd should warn and not stop


(This problem has been identified original is point 5 of
http://lists.alioth.debian.org/pipermail/pkg-kolab-devel/2009-February/002163.html)

----------
messages: 18545
nosy: mathieu.parent
status: unread
title: kolabd fails when folders name contains special characters
topic: server, web admin
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3398>
___________________________________________________


From ml at radoeka.nl  Thu Feb 12 21:06:59 2009
From: ml at radoeka.nl (Richard Bos)
Date: Thu, 12 Feb 2009 21:06:59 +0100
Subject: [Kolab-devel] small patch for kolab_bootstrap: use import i.s.o.
	install for a certificate
Message-ID: <200902122106.59841.ml@radoeka.nl>

Hi,

wouldn't it be better to state that a certificate can be imported than to 
propose to install it?  Hence I therefor propose this change:

-- kolab_bootstrap.in  10 Feb 2009 13:39:55 -0000      1.6
+++ kolab_bootstrap.in  12 Feb 2009 20:03:24 -0000
@@ -651,7 +651,7 @@
 ################################################################################
 CA and certificate creation complete.

-You can install @CONFIG_DIR@/ca/cacert.pem on your clients to allow them
+You can import @CONFIG_DIR@/ca/cacert.pem on your clients to allow them
 to verify the validity of your server certificates.

-- 
Richard


From kolab-issues at intevation.de  Sat Feb  7 14:18:15 2009
From: kolab-issues at intevation.de (=?utf-8?q?Christian_B=C3=B6ttger?=)
Date: Sat, 07 Feb 2009 13:18:15 +0000
Subject: [Kolab-devel] [issue3392] Build error kolab 2.2.0 on openSUSE 11.1
	- OpenPKG fails to build tar
Message-ID: <1234012694.89.0.481624334443.issue3392@intevation.de>


New submission from Christian B?ttger <c at boettger.cc>:

environment: fresh openSUSE 11.1 with all opensuse-supplied updates
source kolab-2.2.0 from kolab repository

starting kolab install script starts OpenPKG build process as expected.
OpenPKG build fails when building tar 1.19 from source with ld linker error.
see log file attached.

Why can't use OpenPKG use - at least as a fallback - the exiting tar of the host
system?

Anyway, there seems to be no chance of building kolab at the moment on openSUSE
11.1.

----------
files: kolab-install.log
messages: 18477
nosy: bofh42
priority: bug
status: unread
title: Build error kolab 2.2.0 on openSUSE 11.1 - OpenPKG fails to build tar
topic: release, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3392>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kolab-install.log
Type: application/octet-stream
Size: 98962 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090207/50d3c218/kolab-install-0001.exe

From tom at tiri.li  Thu Feb  5 17:30:07 2009
From: tom at tiri.li (Thomas Baumann)
Date: Thu, 05 Feb 2009 17:30:07 +0100
Subject: [Kolab-devel] kolab 2.2.1beta -- apache+php+mysql+memcached
In-Reply-To: <20090205154516.69133v8yk65h0neo@webmail.pardus.de>
References: <20090131220858.4adff91if4swo4kw@ox.thomasbaumann.com>
	<71fe4e760902010138s2c6ef64doc2bd6ff7def43e48@mail.gmail.com>
	<20090201223315.vi3iia98hkwswog8@ox.thomasbaumann.com>
	<20090202080731.1836585ixmds7008@webmail.pardus.de>
	<20090202090254.7zzspptz0gsso8oc@ox.thomasbaumann.com>
	<20090205154516.69133v8yk65h0neo@webmail.pardus.de>
Message-ID: <20090205173007.km2dq4co0g00os0g@ox.thomasbaumann.com>

OK. I recompiled apache-php and everything went right.

See:  
http://inhalt.serviert.de/wissen/migration/kolab-2.2-beta-unter-debian-etch#apache_php

Thanks for your help!

Thomas.

Zitat von Gunnar Wrobel <wrobel at pardus.de>:

> Quoting Thomas Baumann <tom at tiri.li>:
>
>> Yes I run phpinfo from apache.
>> What are the steps to get customized php usable from the
>> webserver ?
>>
>> Which RPMs are to be recompiled ?
>
> The apache-php package provides mod_php for the apache server while
> the php package provides command line PHP.
>
> Cheers,
>
> Gunnar
>
>>
>> Thanks for your reply in advance.
>>
>> Thomas.
>>
>> Zitat von Gunnar Wrobel <wrobel at pardus.de>:
>>
>>> Quoting Thomas Baumann <tom at thomasbaumann.com>:
>>>
>>>> Thanks, Alain,
>>>>
>>>> I got (as referred in my link on http://inhalt.serviert.de )
>>>>
>>>> checking for MySQL support... yes
>>>> checking for specified location of the MySQL UNIX socket... no
>>>> checking for MySQL UNIX socket location... no
>>>> checking for mysql_close in -lmysqlclient... yes
>>>> checking for MySQLi support... no
>>>> checking whether to enable embedded MySQLi support... no
>>>> checking for ncurses support... no
>>>>
>>>> So everything looks fine. Even the RPM builds correctly.
>>>>
>>>> But when I install and look after my phpinfo there
>>>> is nothing about mysql nor memcache :-(
>>>
>>> Maybe you are running phpinfo() via the Apache (using mod_php which is
>>> represented by the apache-php pacakge on OpenPKG) rather than on the
>>> command line. It looks as you are compiling the php package and this
>>> will only modify the command line PHP.
>>>
>>> Cheers,
>>>
>>> Gunnar
>>>
>>>>
>>>> That's what I cannot understand.
>>>>
>>>> Hope sb can help me further.
>>>>
>>>> Thanks for your reply in advance,
>>>>
>>>> thomas.
>>>>
>>>> Zitat von Alain Spineux <aspineux at gmail.com>:
>>>>
>>>>> On Sat, Jan 31, 2009 at 10:08 PM, Thomas Baumann
>>>>> <tom at thomasbaumann.com> wrote:
>>>>>> Hello list,
>>>>>>
>>>>>> I tried to get PHP5 working with mysql but I didnt succeed.
>>>>>>
>>>>>> I succeeded in rebuild mysql to
>>>>>> mysql-5.1.30-20090102.ix86-debian4.0-kolab.rpm
>>>>>> (taken from openpkg).
>>>>>> I succeeded in rebuild
>>>>>> libevent-1.4.9-20081222.ix86-debian4.0-kolab.rpm and
>>>>>> memcached-1.3.0-20090130.ix86-debian4.0-kolab.rpm to get all   
>>>>>> dependencies
>>>>>> to my php.src.rpm
>>>>>>
>>>>>> I did a
>>>>>>
>>>>>> /kolab/bin/openpkg rpm -ivh php-5.2.8-20081209_kolab.src.rpm
>>>>>>
>>>>>> went to
>>>>>>
>>>>>> cd /kolab/RPM/SRC/php
>>>>>>
>>>>>> and tried to recompile with
>>>>>>
>>>>>> /kolab/bin/openpkg rpm -ba --define 'with_mysql yes' \
>>>>>>      --define 'with_pecl_memcache yes'  php.spec
>>>>>
>>>>> The command looks correct !
>>>>>
>>>>> Usually, I skip the rpm -i and use a rpm --build like this :
>>>>>
>>>>> /kolab/bin/openpkg rpm --rebuild \
>>>>>      php-5.2.8-20081209_kolab.src.rpm \
>>>>>      --define 'with_mysql yes' \
>>>>>      --define 'with_pecl_memcache yes'  php.spec
>>>>>
>>>>> Did you install mysql first, before to build your php package ?
>>>>>
>>>>> I tried it myself, with mysql installed, but get this :
>>>>>
>>>>> # /kolab/bin/openpkg rpm --rebuild
>>>>> /s0/emailgency/kolab_src/php-5.2.6-20080514_kolab.src.rpm --define
>>>>> 'with_mysql yes' --define 'with_mysql yes'
>>>>> ......
>>>>> checking for specified location of the MySQL UNIX socket... no
>>>>> checking for MySQL UNIX socket location... no
>>>>> checking for mysql_close in -lmysqlclient... no
>>>>> checking for mysql_error in -lmysqlclient... no
>>>>> configure: error: mysql configure failed. Please check config.log for
>>>>> more information.
>>>>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.71712 (%build)
>>>>>
>>>>> Hope this give you some ideas
>>>>>
>>>>>
>>>>>>
>>>>>> But the result was a installable rpm-file, but it lacks on
>>>>>> mysql and pecl-memcache support.
>>>>>>
>>>>>> What is going wrong - or what do i have to type to get
>>>>>> a RPM-file with all support as in the original but additional with
>>>>>> mysql and memcache support ?
>>>>>>
>>>>>> The compile log is visible on
>>>>>>
>>>>>> http://inhalt.serviert.de/ -->
>>>>>> http://inhalt.serviert.de/wissen/migration/kolab-2.2-beta-unter-debian-etch
>>>>>> ->
>>>>>> php_recompile
>>>>>>
>>>>>> Thanks for your reply in advance.
>>>>>>
>>>>>> Thomas.
>>>>>>
>>>>>> --
>>>>>> Thomas Baumann
>>>>>>
>>>>>> B?cher und mehr im Internet - meine neue Site: http://www.1-search.de
>>>>>> - Viel Spass!
>>>>>>
>>>>>> ----------------------------------------------------------------
>>>>>> 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
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> 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
>>>>>
>>>>>
>>>>
>>>> --
>>>> B?cher und mehr im Internet - meine neue Site: http://www.1-search.de
>>>> - Viel Spass!
>>>>
>>>> ----------------------------------------------------------------
>>>> 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.
>>
>>
>>
>> --
>> tiri Limited & Co. KG
>> Johann-Adolf-Hasse-Str. 2b
>> 21493 Schwarzenbek
>>
>> Gesch?ftsf?hrerin: Anja Baumann
>>
>> Sitz der Gesellschaft: Schwarzenbek
>>
>> Handelsregister: HRA 5078 HL
>> USt.-ID: DE254262065
>>
>> Pers?nlich haftender Gesellschafter: tiri Limited
>>
>> tiri Limited ist eine Gesellschaft nach englischem Recht, zugelassen
>> bei Companies House zu Cardiff, Company No. 05178378, Registered
>> Office: 39-40 Calthorpe Road, Birmingham, West Midlands, B15 1TS,
>> United Kingdom
>>
>> ----------------------------------------------------------------
>> 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.



-- 
tiri GmbH
Lauenburger Str. 31a
21493 Schwarzenbek
Tel. 04151 8674995
Fax. 04151 8674996
Net. http://www.tiri.li

Gesch?ftsf?hrer: Anja Baumann, Thomas Baumann
Sitz Schwarzenbek, Amtsgericht L?beck, HRB 8837 HL

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


From tom at tiri.li  Sat Feb  7 21:23:27 2009
From: tom at tiri.li (Thomas Baumann)
Date: Sat, 07 Feb 2009 21:23:27 +0100
Subject: [Kolab-devel] HORDE - Failed identifying the UID of the Kolab
	user	thomas.baumann. Error was: Unable to bind to the LDAP
	server as	cn=nobody, cn=internal, dc=example, dc=com
Message-ID: <20090207212327.6z00ofw6osk088kg@ox.thomasbaumann.com>

Hello list,

I recently setup current kolab with 2.2-beta, and tried to login into
horde, but I cannot login.

I always get the following error:

Failed identifying the UID of the Kolab user {USERNAME}. Error was:  
Unable to bind to the LDAP server as  
cn=nobody,cn=internal,dc={DOMAIN},dc={TLD}!

I even tried to set a new manager password with

/kolab/bin/kolabpasswd

but with no success in Horde.

Hope I get a hint how to login.

Thanks for your reply in advance.

Thomas.




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


From kolab-issues at intevation.de  Fri Feb 13 19:08:36 2009
From: kolab-issues at intevation.de (Felicdad)
Date: Fri, 13 Feb 2009 18:08:36 +0000
Subject: [Kolab-devel] [issue3399] Lass mich Dein Sperma schlecken
Message-ID: <CE052E16.731E365A@gmx.net>


New submission from Felicdad <m.nitschyrakr at gmx.net>:

Hallo Maenner! Mein Name ist g-eileStefanie. Ich bin eine scharfe Wildkatze
mit grossen Bruesten, auf die ich sehr stolz bin! Ich bin immer lustig
drauf, ehrlich und neugierig. Ich stehe auf AnaIen und 0ralen s-e_x, Dild0s
und andere s-e_xspielzeuge, Voyeurismus und auf Deine leckere Sahne wenn ich
Deinen grossen, harten Freudenspender lange und intensiv 0ral verwoehne! Ich
bin eine er0tische Dame und weiss genau was ich im Bett will! Ich brauche
Maenner, die gut im Bett sind, die einiges in der Hose haben und einen guten
Charakter haben. Du solltest alt genug fuer mich sein, ehrlich, s-e_xy,
gutaussehend und gross. Natuerlich solltest Du auch meine riesigen Brueste
und meinen Koerper g-eil finden. Deine Wildkatze wartet auf dich! Erzaehl
mir deine Wuensche, Iive im ch-at!

Shela nackt am Pool
http://Ada.live-hart-versaut-chatten.net

----------
messages: 18564
nosy: m.nitschyrakr
status: unread
title: Lass mich Dein Sperma schlecken
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3399>
___________________________________________________


From ml at radoeka.nl  Sat Feb 14 21:07:46 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sat, 14 Feb 2009 21:07:46 +0100
Subject: [Kolab-devel] kolab on openSUSE natively is a little bit back
Message-ID: <200902142107.48113.ml@radoeka.nl>

Hi,

this is a message for those interested in having kolab available on openSUSE 
natively.  The last months I have been working on the many many packages that 
are required for kolab and they are now available on openSUSE's build service.  
I have updated the wiki page about how to install kolab on openSUSE.

The packages are available for openSUSE_10.3, 11.0 and 11.1.  I have tested 
the packages only on 11.1.  So far the rpms install nicely, and I have the web 
interface up and running.  However, configured users are not created in the 
directory /var/spool/imap  This is to be investigated why this happens.  A 
message in /var/log/messages might give clue:
DBERROR db4: /var/lib/imap/mailboxes.db: unexpected file type or format

Anyway, I just wanted to let you know that progress is made and it would be 
great if others start testing the current packages.  Find more information 
about kolab on openSUSE at: 
http://wiki.kolab.org/index.php/OpenSUSE_-_natively
and
http://en.opensuse.org/Kolab

-- 
Richard


From mario at hummy.org  Sun Feb 15 00:29:22 2009
From: mario at hummy.org (Mario Ramos)
Date: Sat, 14 Feb 2009 23:29:22 +0000
Subject: [Kolab-devel] forwarding oddity - fixed
Message-ID: <d3aeea660902141529v3ebaa912l78ebee4f5969b70b@mail.gmail.com>

Hello.

The other day I wrote this email to the users list:

http://kolab.org/pipermail/kolab-users/2009-February/009457.html

regarding a problem I was experiencing with my kolab installation using
multiple domains.

I realised about the problem because the forwarding feature wasn't working,
as I explained on that email.

I've been digging in this error and I think I've fixed it, it's not a sieve
problem, it was an authentication problem.


In /kolab/etc/kolab/templates/saslauthd.conf.template I added:

ldap_size_limit: 0


And then, in the /kolab/var/sasl/log/saslauthd.log when trying to login as
info at domain2.com, I started getting this:


Feb 14 20:35:27 mrburns <debug> saslauthd[24334]: Duplicate entries found
((&(|(mail=info at domain2.com)(mail=info)(uid=info at domain2.com
)(uid=info))(!(kolabdeleteflag=*)))).
Feb 14 20:35:27 mrburns <debug> saslauthd[24334]: Authentication failed for
info/domain2.com: User not found (-6)
Feb 14 20:35:27 mrburns <info> saslauthd[24334]: do_auth         : auth
failure: [user=info] [service=imap] [realm=domain2.com] [mech=ldap]
[reason=Unknown]
Feb 14 20:35:30 mrburns <debug> saslauthd[24336]: Duplicate entries found
((&(|(mail=info at domain2.com)(mail=info)(uid=info at domain2.com
)(uid=info))(!(kolabdeleteflag=*)))).
Feb 14 20:35:30 mrburns <debug> saslauthd[24336]: Authentication failed for
info/domain2.com: User not found (-6)
Feb 14 20:35:30 mrburns <info> saslauthd[24336]: do_auth         : auth
failure: [user=info] [service=imap] [realm=domain2.com] [mech=ldap]
[reason=Unknown]


If I create a info at domain1.com and another account info at domain2.com

The original ldap filter will return duplicated entries and will not be able
to authenticate info at domain2.com, although it is still possible to
authenticate as info at domain1.com, I don't know why... I'm not an LDAP
expert.

Anyway, the fix was changing the filter to:

#ldap_filter: (&(|(mail=%u@%d)(mail=%u)(uid=%u@
%d)(uid=%u))(!(kolabdeleteflag=*)))
ldap_filter: (&(|(mail=%u@%d)(mail=%u)(uid=%u@%d))(!(kolabdeleteflag=*)))


This seems to have fixed the problem.
Now I can authenticate any user by using its UID.

I wanted to ask in the developers list about this problem, because I think
it's bug and should be corrected, but I'm not sure if what I did is the best
approach to this problem, or what the implications of removing "(uid=%u)"
from the original ldap_filter could be, in regards to the kolab app as a
whole.


Cheers.
Mario.


-- 
PS ? Please help preserve the environment, don't print this email unless you
have to.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-devel/attachments/20090214/ee6fbdb9/attachment.html

From ml at radoeka.nl  Sun Feb 15 11:53:20 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sun, 15 Feb 2009 11:53:20 +0100
Subject: [Kolab-devel] kolab on openSUSE natively is a little bit back
In-Reply-To: <200902142107.48113.ml@radoeka.nl>
References: <200902142107.48113.ml@radoeka.nl>
Message-ID: <200902151153.21271.ml@radoeka.nl>

Op zaterdag 14 februari 2009 21:07:46 schreef Richard Bos:
> The packages are available for openSUSE_10.3, 11.0 and 11.1. ?I have tested
> the packages only on 11.1. ?So far the rpms install nicely, and I have the
> web interface up and running. ?However, configured users are not created in
> the directory /var/spool/imap ?This is to be investigated why this happens.
> ?A message in /var/log/messages might give clue:
> DBERROR db4: /var/lib/imap/mailboxes.db: unexpected file type or format

I tackled this one.  I had been running cyrus before I bootstrapped kolab, as 
the default cyrus is configured to use db4 and kolab is using berkely the 
database formats collides.  I removed all the files /var/lib/imap and after 
that the users are created.  Details can be mentioned in the wiki page, up to 
the next challenge. Which seems to be something with clamav....

-- 
Richard


From kolab-issues at intevation.de  Sun Feb 15 18:33:00 2009
From: kolab-issues at intevation.de (Richard Bos)
Date: Sun, 15 Feb 2009 17:33:00 +0000
Subject: [Kolab-devel] [issue3401] Change font color of the kolab-webadmin
Message-ID: <1234719180.5.0.824565212431.issue3401@intevation.de>


New submission from Richard Bos <ml at radoeka.nl>:

Change the font color from black to #001155 in the kolab-webadmin interface.
This color is already used as font in the webinterface, it is rather dark
too, and it matches the out purple / blue-ish colors very well.

The nice thing of the this color (#001155) is that it makes the interface
friendlier for the user. It just looks nicer...., the black color does not
really match with the other colors...

A patch is attached.

----------
files: style.css.diff
messages: 18568
nosy: rbos
priority: wish
status: unread
title: Change font color of the kolab-webadmin
topic: web admin
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3401>
___________________________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: style.css.diff
Url: http://kolab.org/pipermail/kolab-devel/attachments/20090215/300834ea/style.css.txt

From kolab-issues at intevation.de  Sun Feb 15 20:21:49 2009
From: kolab-issues at intevation.de (Richard Bos)
Date: Sun, 15 Feb 2009 19:21:49 +0000
Subject: [Kolab-devel] [issue3402] Change displayed value of logged in user
Message-ID: <1234725709.64.0.110448221245.issue3402@intevation.de>


New submission from Richard Bos <ml at radoeka.nl>:

The title of this bug report might be hard to understand:
when a user logs in in the right top corner of the web interface the line
is displayed with user and role, like e.g.:
user: uid at domain.tld | role: user | Logout

Instead of using uid at domain.tld, I think that it is nicer to display the users
name, thus:
user: Firstname, Middlename, Lastname | role: user | Logout

(Middle name is not yet present issue606).

Displaying the user's name is more user oriented than displaying the uid, that
is more system oriented.

----------
messages: 18569
nosy: rbos
priority: minor bug
status: unread
title: Change displayed value of logged in user
topic: web admin
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3402>
___________________________________________________


From ml at radoeka.nl  Sun Feb 15 21:11:05 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sun, 15 Feb 2009 21:11:05 +0100
Subject: [Kolab-devel] Will issue 606 (It is not possible to register people
	with middlename correctly) make it into release 2.2.1?
Message-ID: <200902152111.06281.ml@radoeka.nl>

According to the last update in the issue 606, it may be part of release 
2.2.1: https://www.intevation.de/roundup/kolab/issue606
Is this going to happen?

The issue has already a bit of code that at least makes the middle name 
visible in the webinterface.  The part that is missing is to do something with 
it in the ldap database.

It would nice if this 4 year old bug can be closed isn't it?

-- 
Richard


From kolab-issues at intevation.de  Sun Feb 15 21:23:41 2009
From: kolab-issues at intevation.de (Mario Ramos)
Date: Sun, 15 Feb 2009 20:23:41 +0000
Subject: [Kolab-devel] [issue3403] Problem authenticating 2 accounts with
	the same name on different domains and different UID
Message-ID: <1234729421.72.0.888181230897.issue3403@intevation.de>


New submission from Mario Ramos <mario at hummy.org>:

The other day I wrote this email to the users list:

http://kolab.org/pipermail/kolab-users/2009-February/009457.html

regarding a problem I was experiencing with my kolab installation using multiple
domains.

I realised about the problem because the forwarding feature wasn't working, as I
explained on that email.

I've been digging in this error and I think I've fixed it, it's not a sieve
problem, it was an authentication problem.


In /kolab/etc/kolab/templates/saslauthd.conf.template I added:

ldap_size_limit: 0


And then, in the /kolab/var/sasl/log/saslauthd.log when trying to login as
info at domain2.com, I started getting this:


Feb 14 20:35:27 mrburns <debug> saslauthd[24334]: Duplicate entries found
((&(|(mail=info at domain2.com)(mail=info)(uid=info at domain2.com)(uid=info))(!(kolabdeleteflag=*)))).
Feb 14 20:35:27 mrburns <debug> saslauthd[24334]: Authentication failed for
info/domain2.com: User not found (-6)
Feb 14 20:35:27 mrburns <info> saslauthd[24334]: do_auth         : auth failure:
[user=info] [service=imap] [realm=domain2.com] [mech=ldap] [reason=Unknown]
Feb 14 20:35:30 mrburns <debug> saslauthd[24336]: Duplicate entries found
((&(|(mail=info at domain2.com)(mail=info)(uid=info at domain2.com)(uid=info))(!(kolabdeleteflag=*)))).
Feb 14 20:35:30 mrburns <debug> saslauthd[24336]: Authentication failed for
info/domain2.com: User not found (-6)
Feb 14 20:35:30 mrburns <info> saslauthd[24336]: do_auth         : auth failure:
[user=info] [service=imap] [realm=domain2.com] [mech=ldap] [reason=Unknown]


If I create a info at domain1.com and another account info at domain2.com

The original ldap filter will return duplicated entries and will not be able to
authenticate info at domain2.com, although it is still possible to authenticate as
info at domain1.com, I don't know why... I'm not an LDAP expert.

Anyway, the fix was changing the filter to:

#ldap_filter: (&(|(mail=%u@%d)(mail=%u)(uid=%u@%d)(uid=%u))(!(kolabdeleteflag=*)))
ldap_filter: (&(|(mail=%u@%d)(mail=%u)(uid=%u@%d))(!(kolabdeleteflag=*)))


This seems to have fixed the problem.
Now I can authenticate any user by using its UID.

I'm not sure if what I did is the best approach to this problem, or what the
implications of removing "(uid=%u)" from the original ldap_filter could be.

Cheers.
Mario.

----------
messages: 18570
nosy: mariocbgb
priority: bug
status: unread
title: Problem authenticating 2 accounts with the same name on different domains and different UID
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3403>
___________________________________________________


From ml at radoeka.nl  Sun Feb 15 21:32:46 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sun, 15 Feb 2009 21:32:46 +0100
Subject: [Kolab-devel] php failure undefined method
	Horde_Kolab_Server_ldap::uidForIdOrMail (openSUSE native)
Message-ID: <200902152132.47148.ml@radoeka.nl>

Hi,

I have made quite some progress in the getting kolab to run on openSUSE 
native again.  However, at the moment when I sent an email I encounter the 
following error:

Feb 15 11:38:35 kolab postfix/pipe[6783]: AF8D823597: to=<richard at example.org>, relay=kolabmailboxfilter, delay=2.3, delays=0.41/0.27/0/1.6, 
dsn=5.3.0, status=bounced (Command died with status 255: "/usr/bin/php5". Command output: PHP Fatal error:  Call to undefined method 
Horde_Kolab_Server_ldap::uidForIdOrMail() in /usr/share/php5/PEAR/Horde/Kolab/Filter/Incoming.php on line 203 )

The email is sent from the root account, using the following command:
# echo $(date) | mailx -s test richard at radoeka.nl

When checking the code around line 203 in Incoming.php, it is this:
192         /* Load the LDAP library */
193         require_once 'Horde/Kolab/Server.php';
194
195         $server = &Horde_Kolab_Server::singleton();
196         if (is_a($server, 'PEAR_Error')) {
197             $server->code = OUT_LOG | EX_SOFTWARE;
198             return $server;
199         }
200
201         $hosts = array();
202         foreach ($this->_recipients as $recipient) {
203             $dn = $server->uidForIdOrMail($recipient);
204             if (is_a($dn, 'PEAR_Error')) {
205                 return $dn;
206             }

Looking for the method reveals the following:
Horde/Kolab/Server/ldap.php:    function uidForIdOrMail($id)
Horde/Kolab/Server.php:    function uidForIdOrMail($id)

This one; Horde/Kolab/Server/ldap.php has:
class Horde_Kolab_Server_ldap extends Horde_Kolab_Server {
......
    function uidForIdOrMail($id)
    {
        $filter = '(&(objectClass=kolabInetOrgPerson)(|(uid='.
            Horde_LDAP::quote($id) . ')(mail=' .
            Horde_LDAP::quote($id) . ')))';
        return $this->_dnForFilter($filter, KOLAB_SERVER_RESULT_STRICT);
    }
......

So it looks to me that the method is present on the system, but why can't it
located?

Is the require_once of 'Horde/Kolab/Server.php' in line 193 correct?
Shouldn't that be Horde/Kolab/Server/ldap.php?

I hope that one of you can point me in the right direction, it is a pity
to be stuck on this point.

-- 
Richard


From kolab-issues at intevation.de  Sun Feb 15 21:33:24 2009
From: kolab-issues at intevation.de (Richard Bos)
Date: Sun, 15 Feb 2009 20:33:24 +0000
Subject: [Kolab-devel] [issue3404] Present the options in "Action to take
	for messages that fail the check" nicer
Message-ID: <1234730004.51.0.348451852161.issue3404@intevation.de>


New submission from Richard Bos <ml at radoeka.nl>:

The attached patch presents the options for "Action to take for messages that
fail the check" on the settings page in a nicer way.

The long text will not go through to the check buttons.  The patch uses 
a table for this.

----------
files: settings.tpl.diff
messages: 18571
nosy: rbos
status: unread
title: Present the options in "Action to take for messages that fail the check" nicer
topic: web admin
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3404>
___________________________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: settings.tpl.diff
Url: http://kolab.org/pipermail/kolab-devel/attachments/20090215/4a0252d4/settings.tpl.txt

From martin.konold at erfrakon.de  Sun Feb 15 23:36:06 2009
From: martin.konold at erfrakon.de (Martin Konold)
Date: Sun, 15 Feb 2009 23:36:06 +0100
Subject: [Kolab-devel] forwarding oddity - fixed
In-Reply-To: <d3aeea660902141529v3ebaa912l78ebee4f5969b70b@mail.gmail.com>
References: <d3aeea660902141529v3ebaa912l78ebee4f5969b70b@mail.gmail.com>
Message-ID: <200902152336.07205.martin.konold@erfrakon.de>

Am Sonntag, 15. Februar 2009 00:29:22 schrieb Mario Ramos:

Hi Mario,

please open a bug entry at https://www.intevation.de/roundup/kolab/

> This seems to have fixed the problem.
> Now I can authenticate any user by using its UID.
>
> I wanted to ask in the developers list about this problem, because I think
> it's bug and should be corrected, but I'm not sure if what I did is the
> best approach to this problem, or what the implications of removing
> "(uid=%u)" from the original ldap_filter could be, in regards to the kolab
> app as a whole.

Please also provide the slapcat entries for info at domain1.com and 
info at domain2.com.

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/


From bernhard at intevation.de  Mon Feb 16 10:26:38 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 16 Feb 2009 10:26:38 +0100
Subject: [Kolab-devel] kolab on openSUSE natively is a little bit back
In-Reply-To: <200902142107.48113.ml@radoeka.nl>
References: <200902142107.48113.ml@radoeka.nl>
Message-ID: <200902161026.38703.bernhard@intevation.de>

Richard,

On Samstag, 14. Februar 2009, Richard Bos wrote:
> this is a message for those interested in having kolab available on
> openSUSE natively. ?The last months I have been working on the many many
> packages that are required for kolab and they are now available on
> openSUSE's build service. I have updated the wiki page about how to install
> kolab on openSUSE.

thanks for the good work on this!
(And for updating the wiki, this is quite important I think.)

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/20090216/35aaf1a7/attachment.bin

From bernhard at intevation.de  Mon Feb 16 10:29:09 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 16 Feb 2009 10:29:09 +0100
Subject: [Kolab-devel] Will issue 606 (It is not possible to register
	people with middlename correctly) make it into release 2.2.1?
In-Reply-To: <200902152111.06281.ml@radoeka.nl>
References: <200902152111.06281.ml@radoeka.nl>
Message-ID: <200902161029.09381.bernhard@intevation.de>

On Sonntag, 15. Februar 2009, Richard Bos wrote:
> According to the last update in the issue 606, it may be part of release
> 2.2.1: https://www.intevation.de/roundup/kolab/issue606
> Is this going to happen?
>
> The issue has already a bit of code that at least makes the middle name
> visible in the webinterface. ?The part that is missing is to do something
> with it in the ldap database.
>
> It would nice if this 4 year old bug can be closed isn't it?

I would be nice for sure of course,
but again there are issues of higher priority for 2.2.1 than issue606.
Thomas should know if we manage to do this or not.
(And LDAP changes always tend to be problematic, even small ones.)


-- 
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/20090216/af8fffe3/attachment.bin

From kolab-issues at intevation.de  Mon Feb 16 16:01:42 2009
From: kolab-issues at intevation.de (Martin Konold)
Date: Mon, 16 Feb 2009 15:01:42 +0000
Subject: [Kolab-devel] [issue3405] cleanup roundup user DB
Message-ID: <1234796502.33.0.188338375748.issue3405@intevation.de>


New submission from Martin Konold <martin.konold at erfrakon.de>:

Hi,

the roundup user database became a mess over the years. It currently has more
than 850 entries with most of the caused by spammers. This makes it very hard to
use roundup.

Can you cleanup the user db and remove the junk please.

THX,
-- martin

----------
assignedto: bernhard
messages: 18578
nosy: bernhard, martin, thomas, wrobel
priority: bug
status: unread
title: cleanup roundup user DB
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3405>
___________________________________________________


From thomas at intevation.de  Mon Feb 16 16:18:15 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Mon, 16 Feb 2009 16:18:15 +0100
Subject: [Kolab-devel] gunnar: server/php Makefile, 1.17,
	1.18 kolab.patch, 1.13, 1.14 KOLAB_php-5.2.6_Annotations.patch,
	1.1, NONE KOLAB_php-5.2.6_myrights.patch, 1.1, NONE
In-Reply-To: <20090209100827.B2638600936@lists.intevation.de>
References: <20090209100827.B2638600936@lists.intevation.de>
Message-ID: <20090216151815.GE27187.thomas@intevation.de>

Hi Gunnar!

* cvs at kolab.org <cvs at kolab.org> [20090209 11:08]:
> Author: gunnar
> 
> Log Message:
> Update to current 5.2.8 patches.
> 
> ===================================================================
> RCS file: /kolabrepository/server/php/kolab.patch,v
> retrieving revision 1.13
> retrieving revision 1.14
>...
> +--- php.ini.orig	2009-02-09 09:26:40.000000000 +0000
> ++++ php.ini	2009-02-09 09:27:01.000000000 +0000
> +@@ -13,8 +13,8 @@
> + log_errors         = on     ; Errors will be logged
> + max_execution_time = 60     ; Maximum execution time of each script, in seconds
> + max_input_time     = 60     ; Maximum amount of time each script may spend parsing request data
> +-memory_limit       = 8M     ; Maximum amount of memory a script may consume
> +-post_max_size      = 8M     ; Maximum amount of POST data accepted
> ++memory_limit       = 128M   ; Maximum amount of memory a script may consume
> ++post_max_size      = 128M   ; Maximum amount of POST data accepted
> + 
> + ;   Include Paths
> + include_path          = ".:@l_prefix@/lib/php"

Increasing the limits from 8M to 128M looks like an accidental slip
when not mentioned in the commit message.

Is this intentional? If yes, why?

Regards,
Thomas

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


From thomas at intevation.de  Mon Feb 16 16:23:13 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Mon, 16 Feb 2009 16:23:13 +0100
Subject: [Kolab-devel] gunnar: server Makefile,1.70,1.71
In-Reply-To: <20090209100904.0FC3660093B@lists.intevation.de>
References: <20090209100904.0FC3660093B@lists.intevation.de>
Message-ID: <20090216152313.GF27187.thomas@intevation.de>

* cvs at kolab.org <cvs at kolab.org> [20090209 11:09]:
> +.PHONY: test
> +test:
> +	for TEST in $(PHPUNIT_TESTS); \
> +	do                            \
> +		$(PHPUNIT) $$TEST;    \
> +	done

Good idea to add this!

And here's the report of my first run, CVS as of 20090210:


for TEST in /kolab/lib/php/test/Kolab_Format/Horde/Kolab/Format/AllTests.php /kolab/lib/php/test/Kolab_Server/Horde/Kolab/Server/AllTests.php /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/AllTests.php /kolab/lib/php/test/Kolab_Filter/Horde/Kolab/Filter/AllTests.php /kolab/lib/php/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/AllTests.php; \
	do                            \
		/kolab/bin/phpunit $TEST;    \
	done
PHPUnit 3.3.3 by Sebastian Bergmann.

..............

Time: 0 seconds

OK (14 tests, 56 assertions)
PHPUnit 3.3.3 by Sebastian Bergmann.

....................IIIIIIIIIIIIIIIIIIIIII..................  60 / 119
...IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII......................

Time: 0 seconds

OK, but incomplete or skipped tests!
Tests: 119, Assertions: 169, Incomplete: 56.
PHPUnit 3.3.3 by Sebastian Bergmann.

.....EEEEEEEEEEEEEEEEEEEEEEEE....

Time: 0 seconds

There were 24 errors:

1) testConstruct(Horde_Kolab_Storage_DataTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/DataTest.php:41

2) testGetCacheKey(Horde_Kolab_Storage_DataTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/DataTest.php:41

3) testDelete(Horde_Kolab_Storage_DataTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/DataTest.php:41

4) testMove(Horde_Kolab_Storage_DataTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/DataTest.php:41

5) testSave(Horde_Kolab_Storage_DataTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/DataTest.php:41

6) testObjectDeleteAll(Horde_Kolab_Storage_DataTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/DataTest.php:41

7) testConstruct(Horde_Kolab_Storage_FolderTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php:42

8) testSetName(Horde_Kolab_Storage_FolderTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php:42

9) testSave(Horde_Kolab_Storage_FolderTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php:42

10) testGetImapFailNoServer(Horde_Kolab_Storage_FolderTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php:42

11) testTrigger(Horde_Kolab_Storage_FolderTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php:42

12) testConstruct(Horde_Kolab_Storage_ListTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39

13) testListFolders(Horde_Kolab_Storage_ListTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39

14) testGetFolders(Horde_Kolab_Storage_ListTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39

15) testGetByShare(Horde_Kolab_Storage_ListTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39

16) testGetByType(Horde_Kolab_Storage_ListTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39

17) testGetDefault(Horde_Kolab_Storage_ListTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39

18) testGetForeignOwner(Horde_Kolab_Storage_ListTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39

19) testGetForeignDefault(Horde_Kolab_Storage_ListTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39

20) testCreate(Horde_Kolab_Storage_ListTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39

21) testCacheUpdate(Horde_Kolab_Storage_ListTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39

22) testRename(Horde_Kolab_Storage_ListTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39

23) testRemove(Horde_Kolab_Storage_ListTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39

24) testCaching(Horde_Kolab_Storage_ListTest)
include_once(Horde/Notification.php): failed to open stream: No such file or directory
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:299
/kolab/lib/php/Horde/Kolab/Test/Storage.php:140
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39

FAILURES!
Tests: 33, Assertions: 50, Errors: 24.
PHP Fatal error:  Uncaught exception 'InvalidArgumentException' in /kolab/lib/php/PHPUnit/Framework/TestSuite.php:302
Stack trace:
#0 /kolab/lib/php/test/Kolab_Filter/Horde/Kolab/Filter/AllTests.php(53): PHPUnit_Framework_TestSuite->addTestSuite('Horde_Kolab_Fil...')
#1 [internal function]: Horde_Kolab_Filter_AllTests::suite('Horde_Kolab_Fil...')
#2 /kolab/lib/php/PHPUnit/Runner/BaseTestRunner.php(221): ReflectionMethod->invoke(NULL, 'Horde_Kolab_Fil...')
#3 /kolab/lib/php/PHPUnit/TextUI/Command.php(88): PHPUnit_Runner_BaseTestRunner->getTest('/kolab/lib/php/...', '/kolab/lib/php/...', true)
#4 /kolab/lib/php/PHPUnit/TextUI/Command.php(701): PHPUnit_TextUI_Command::main()
#5 /kolab/bin/phpunit(44): require('/kolab/lib/php/...')
#6 {main}
  thrown in /kolab/lib/php/PHPUnit/Framework/TestSuite.php on line 302
PHP Warning:  require_once(Horde/Kolab/Test.php): failed to open stream: No such file or directory in /kolab/lib/php/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php on line 17
PHP Fatal error:  require_once(): Failed opening required 'Horde/Kolab/Test.php' (include_path='.:/kolab/lib/php') in /kolab/lib/php/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php on line 17
make: *** [test] Error 255

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


From wrobel at pardus.de  Mon Feb 16 18:28:02 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Mon, 16 Feb 2009 18:28:02 +0100
Subject: [Kolab-devel] gunnar: server/php Makefile, 1.17,
	1.18 kolab.patch, 1.13, 1.14 KOLAB_php-5.2.6_Annotations.patch,
	1.1, NONE	KOLAB_php-5.2.6_myrights.patch, 1.1, NONE
In-Reply-To: <20090216151815.GE27187.thomas@intevation.de>
References: <20090209100827.B2638600936@lists.intevation.de>
	<20090216151815.GE27187.thomas@intevation.de>
Message-ID: <20090216182802.17523fudq15icsow@webmail.pardus.de>

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

> Hi Gunnar!
>
> * cvs at kolab.org <cvs at kolab.org> [20090209 11:08]:
>> Author: gunnar
>>
>> Log Message:
>> Update to current 5.2.8 patches.
>>
>> ===================================================================
>> RCS file: /kolabrepository/server/php/kolab.patch,v
>> retrieving revision 1.13
>> retrieving revision 1.14
>> ...
>> +--- php.ini.orig	2009-02-09 09:26:40.000000000 +0000
>> ++++ php.ini	2009-02-09 09:27:01.000000000 +0000
>> +@@ -13,8 +13,8 @@
>> + log_errors         = on     ; Errors will be logged
>> + max_execution_time = 60     ; Maximum execution time of each  
>> script, in seconds
>> + max_input_time     = 60     ; Maximum amount of time each script  
>> may spend parsing request data
>> +-memory_limit       = 8M     ; Maximum amount of memory a script  
>> may consume
>> +-post_max_size      = 8M     ; Maximum amount of POST data accepted
>> ++memory_limit       = 128M   ; Maximum amount of memory a script  
>> may consume
>> ++post_max_size      = 128M   ; Maximum amount of POST data accepted
>> +
>> + ;   Include Paths
>> + include_path          = ".:@l_prefix@/lib/php"
>
> Increasing the limits from 8M to 128M looks like an accidental slip
> when not mentioned in the commit message.
>
> Is this intentional? If yes, why?

Yes, this was indeed intentional. Sorry for missing this in the commit  
message. The reason for this are the unit tests which need to be run  
from the command line and require more than 8MB. The unit tests are  
not yet running but this is something I want to fix soon.

Cheers,

Gunnar

>
> Regards,
> Thomas
>
> --
> 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
>



-- 
______ 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/20090216/571090fe/attachment.bin

From kolab-issues at intevation.de  Mon Feb 16 20:44:02 2009
From: kolab-issues at intevation.de (=?utf-8?q?Albrecht_Dre=C3=9F?=)
Date: Mon, 16 Feb 2009 19:44:02 +0000
Subject: [Kolab-devel] [issue3406] Horde: attendee cannot change appointment
Message-ID: <1234813442.65.0.591424848664.issue3406@intevation.de>


New submission from Albrecht Dre? <albrecht.dress at lios-tech.com>:

I ran reproducibly into a situation where attendees cannot update appointments
when they are moved.  I use kolab 2.2, and all users shall manually process
invitations.  Consider two users "a" and "b":

- "a" creates an appointment, invites b and checks to send the invitation.
- "b" accepts the appointment (in the web mail section), which is properly added
  to the calendar.
- "a" opens the appointment again in the calendar, changes the time and sends an
  update to all participants;
- "b" opens the message in the web mailer and tries to accept.  The following
  messages appear:
  [!]Beim Importieren des Termins ist ein Fehler aufgetreten: Existiert bereits.
  [v]Antwort versendet.
- "a" receives the "accept" message from "b".  The appointment in "a"'s calendar
  is properly shifted;
- the same appointment in "b"'s calendar still has the old time.

Result: although "b" properly accepted the changed appointment, the calendar
data doesn't get updated.  This is of course a source of endless confusion!

----------
messages: 18585
nosy: albrecht.dress
status: unread
title: Horde: attendee cannot change appointment
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3406>
___________________________________________________


From ml at radoeka.nl  Mon Feb 16 20:50:19 2009
From: ml at radoeka.nl (Richard Bos)
Date: Mon, 16 Feb 2009 20:50:19 +0100
Subject: [Kolab-devel] Will issue 606 (It is not possible to register
	people with middlename correctly) make it into release 2.2.1?
In-Reply-To: <200902161029.09381.bernhard@intevation.de>
References: <200902152111.06281.ml@radoeka.nl>
	<200902161029.09381.bernhard@intevation.de>
Message-ID: <200902162050.20123.ml@radoeka.nl>

Op maandag 16 februari 2009 10:29:09 schreef Bernhard Reiter:
> > The issue has already a bit of code that at least makes the middle name
> > visible in the webinterface. ?The part that is missing is to do something
> > with it in the ldap database.
> >
> > It would nice if this 4 year old bug can be closed isn't it?
>
> I would be nice for sure of course,
> but again there are issues of higher priority for 2.2.1 than issue606.

I understand, but a long time ago it was proposed to (try to) get this one 
into 2.2.1....  Hence this email as a reminder.

> Thomas should know if we manage to do this or not.
> (And LDAP changes always tend to be problematic, even small ones.)

It is not so much a problem with LDAP, but more the code itself.  Were to put 
the line to add the middle name.  Perhaps this is what you mean with LDAP 
changes.

-- 
Richard


From kolab-issues at intevation.de  Mon Feb 16 22:37:55 2009
From: kolab-issues at intevation.de (Richard Bos)
Date: Mon, 16 Feb 2009 21:37:55 +0000
Subject: [Kolab-devel] [issue3407] kolab_bootstrap: use import i.s.o.
	install for a certificate
Message-ID: <1234820275.25.0.267852917378.issue3407@intevation.de>


New submission from Richard Bos <ml at radoeka.nl>:

Wouldn't it be better (or more correct) to state that a certificate can be 
imported than to propose to install it in kolab_bootstrap?  
Hence I therefor propose this change:

-- kolab_bootstrap.in  10 Feb 2009 13:39:55 -0000      1.6
+++ kolab_bootstrap.in  12 Feb 2009 20:03:24 -0000
@@ -651,7 +651,7 @@
 ###############################################################################
 CA and certificate creation complete.

-You can install @CONFIG_DIR@/ca/cacert.pem on your clients to allow them
+You can import @CONFIG_DIR@/ca/cacert.pem on your clients to allow them
 to verify the validity of your server certificates.

I also tried to discuss this issue on the ML, but no response :(
http://www.kolab.org/pipermail/kolab-devel/2009-February/010070.html

Most browsers (if not all) I have seen propose to import a certificate hence
my proposal.

----------
messages: 18589
nosy: bernhard, martin, rbos, thomas, till, wilde, wrobel
priority: minor bug
status: unread
title: kolab_bootstrap: use import i.s.o. install for a certificate
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3407>
___________________________________________________


From kolab-issues at intevation.de  Mon Feb 16 22:47:54 2009
From: kolab-issues at intevation.de (Richard Bos)
Date: Mon, 16 Feb 2009 21:47:54 +0000
Subject: [Kolab-devel] [issue3408] Template for inclusion in shell scripts
Message-ID: <1234820873.96.0.194579146554.issue3408@intevation.de>


New submission from Richard Bos <ml at radoeka.nl>:

I created a template that can be sourced in by shell scripts.  This way
it makes it possible for me to start or not start services that depend on the
value of the variable @@@postfix-enable-virus-scan@@@.

Based on the value of that variable it is now possible to start (or not start)
the services amavis, spamd, clamav, freshclam.

Is it okay to commit this template to cvs, I think that it is useful for others
too.

To include the template in the build, an small update to the Makefile.am is
needed:
diff -a -u -r1.49 Makefile.am
--- Makefile.am 17 Nov 2008 18:28:40 -0000      1.49
+++ Makefile.am 16 Feb 2009 21:39:00 -0000
@@ -53,6 +53,7 @@
        templates/ldapvirtual.cf.template \
        templates/kolab_smtpdpolicy.conf.template \
        templates/php.ini.template \
+       templates/profile.sh.template \
        templates/relocated.template \
        templates/resmgr.conf.template \
        templates/saslauthd.conf.template \

Once this template is available it can of course be used, to make more
kolab @@@variables know in this template.  It is not restricted to the one
variable that is in the file now.

----------
files: profile.sh.template.in
messages: 18590
nosy: bernhard, martin, mathieu.parent, rbos, thomas, till, wilde, wrobel
priority: feature
status: unread
title: Template for inclusion in shell scripts
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3408>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: profile.sh.template.in
Type: application/octet-stream
Size: 563 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090216/9e914e63/profile.sh.template.exe

From bernhard at intevation.de  Tue Feb 17 09:22:40 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 17 Feb 2009 09:22:40 +0100
Subject: [Kolab-devel] Will issue 606 (It is not possible to register
	people with middlename correctly) make it into release 2.2.1?
In-Reply-To: <200902162050.20123.ml@radoeka.nl>
References: <200902152111.06281.ml@radoeka.nl>
	<200902161029.09381.bernhard@intevation.de>
	<200902162050.20123.ml@radoeka.nl>
Message-ID: <200902170922.40916.bernhard@intevation.de>

Am Montag, 16. Februar 2009 20:50:19 schrieb Richard Bos:
> Op maandag 16 februari 2009 10:29:09 schreef Bernhard Reiter:
> > > The issue has already a bit of code that at least makes the middle name
> > > visible in the webinterface. ?The part that is missing is to do
> > > something with it in the ldap database.
> > >
> > > It would nice if this 4 year old bug can be closed isn't it?
> >
> > I would be nice for sure of course,
> > but again there are issues of higher priority for 2.2.1 than issue606.
>
> I understand, but a long time ago it was proposed to (try to) get this one
> into 2.2.1.... ?Hence this email as a reminder.

Sure, though we are in the get-this-thing-out mode which is bad timing to get 
minor issues fixed as we need to build pressure to actually get a release 
out. 

-- 
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/20090217/3fd36822/attachment.bin

From kolab-issues at intevation.de  Tue Feb 17 10:04:06 2009
From: kolab-issues at intevation.de (Thomas Ribbrock)
Date: Tue, 17 Feb 2009 09:04:06 +0000
Subject: [Kolab-devel] [issue3409] Advanced reminders work only partially
Message-ID: <1234861445.87.0.683997416065.issue3409@intevation.de>


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

(split off issue1837)

When trying to use "Advanced Reminders" in enterprise35, I observed the following:

"Audio" type alarms
These alarms work (even with attendees, as long as the audio file is present on
their machine, too - haven't tested to extensively, though)

"Program" type alarms
These do not work. If I try to run a program (e.g. to play an audio file), the
normal alarm dialog correctly pops up at the designated. However, the assigned
program is not run. For this scenario, I have seen two cases:
 a) I enter the program name (/usr/bin/play) in "Program file" and the sound
file (with full path) in "Program arguments". I can see the following in the dbg
output:
libkcal: CalendarLocal::appendAlarms() 'test6': Thu Feb 12 16:15:00 2009
korgac (check): REMINDER: test6
korganizer: formatAttendees: uid =
korganizer: formatAttendees: uid =
korganizer: formatAttendees: uid =
korganizer: formatAttendees: uid =
korgac: Starting program: '/usr/bin/play '
The argument is nowhere to be seen and no audio is played.

I have retested this case with kdialog as well, with the same results. kdialog
is not run.
b) If I leave the "Program arguments" empty and add the sound file to the
"Program file" field instead, I also get no audio, but the dbg file shows:
korgac (check): Check: Thu Feb 12 16:23:17 2009 - Thu Feb 12 16:24:16 2009
libkcal: CalendarLocal::appendAlarms() 'test6': Thu Feb 12 16:24:00 2009
korgac (check): REMINDER: test6
korganizer: formatAttendees: uid =
korganizer: formatAttendees: uid =
korganizer: formatAttendees: uid =
korganizer: formatAttendees: uid =
korgac: Starting program: '/usr/bin/play /home/ribbrock/sounds/drawswrd.wav'
Again, no audio.
In both cases I have tried to run the "play" command from the command line - in
which case it worked and played the correct audio sample. Same goes for the
kdialog command I used - it works fine from the command line.

"Reminder dialog" type alarms
These also do not work. If I choose "Reminder dialog" and enter some text in
"Reminder Dialog text", only the standard reminder dialog is shown - no sign of
the custom text. The dbg file shows:
korgac (check): Check: Thu Feb 12 16:39:17 2009 - Thu Feb 12 16:40:16 2009
libkcal: CalendarLocal::appendAlarms() 'test6': Thu Feb 12 16:40:00 2009
korgac (check): REMINDER: test6

Repeating alarms
Seem to work, at least with an alarm that's "n minutes before start"

All these were tested with:
kontact --version
Qt: 3.3.8b
KDE: 3.5.10
Kontact: 1.2.9 (enterprise35 20090206.922263)

This particular version also had the patch for incident.cpp from
issue3385/msg18534 applied.

----------
messages: 18593
nosy: itsef_admin
priority: bug
status: unread
title: Advanced reminders work only partially
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3409>
___________________________________________________


From kolab-issues at intevation.de  Tue Feb 17 10:13:07 2009
From: kolab-issues at intevation.de (Thomas Ribbrock)
Date: Tue, 17 Feb 2009 09:13:07 +0000
Subject: [Kolab-devel] [issue3410] Add general standard alarm sound in
	KOrganizer
Message-ID: <1234861986.86.0.279387497445.issue3410@intevation.de>


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

Based on feedback from our users after issue1837 had been resolved:

It would be nice if it was possible to configure a general alarm sound for
events. Right now, there are two options:

a) Use the standard alarm. This alarm type uses the "system bell" as audio
feedback (as far as I can see), so the only way to change this sound is to
change that general notification - with as downside that all other programs that
use system bell also emit this sound (e.g. KMail for new mail) => no audible
distinction
b) Set an advanced reminder, type "Audio". While this works nicely as such, it's
a lot more "click-work" to achieve. A standard reminder is one click away, but
an audio type advanced reminder requires the user to open up the advanced
dialog, configure the correct type of alarm, browse for suitable alarm sound and
apply - for *each* alarm where a special sound is required.
One can improve on this by using templates, however, this does not work well for
alarms that are assigned to events organised by others (i.e. events where one is
attendee).

Having a general alarm sound that could be associated with the standard reminder
would cover many standard situations and make it very simple to set a distinct
sound that is easily distinguishable from other noises the computer might emit.

----------
messages: 18594
nosy: itsef_admin
priority: wish
status: unread
title: Add general standard alarm sound in KOrganizer
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3410>
___________________________________________________


From kolab-issues at intevation.de  Tue Feb 17 14:52:35 2009
From: kolab-issues at intevation.de (Marc Mutz)
Date: Tue, 17 Feb 2009 13:52:35 +0000
Subject: [Kolab-devel] [issue3411] kmail drag and drop (DnD) of email
	addresses with umlauts from reader to composer exposes
	encoded-word encoding
Message-ID: <1234878755.06.0.039196024773.issue3411@intevation.de>


New submission from Marc Mutz <marc at kdab.net>:

Try this:

Open a mail where sender or recipient's display-name contains umlauts.

Open a composer window.

Drag the mailto: link of the email address with the umlaut from the reader into 
an address field of the composer.

Then
   Mirko B?hm <...>
is turned into
   Mirko =?utf-8?q?B=C3=B6hm?= <>
exposing the encoded-word used to represent the umlaut in ASCII-compatible form 
to the user.

What's worse: Unless corrected, when sending, this is turned into
 To: "Mirko =?iso-8859-1?q?B=F6hm?=" <...>
which is illegal (encoded-word in quoted-string), even though for display 
purposes KMail still decodes the encoded-word, so it's not directly visible 
after a draft-reedit roundtrip (or in the outbox).

----------
assignedto: allen
messages: 18602
nosy: allen, marc
priority: bug
status: unread
title: kmail drag and drop (DnD) of email addresses with umlauts from reader to composer exposes encoded-word encoding
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3411>
___________________________________________________


From kolab-issues at intevation.de  Tue Feb 17 15:05:13 2009
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Tue, 17 Feb 2009 14:05:13 +0000
Subject: [Kolab-devel] [issue3412] More efficient building with OpenPKG,
	use more CPU cores with 'make -j'
Message-ID: <1234879512.91.0.151977291789.issue3412@intevation.de>


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

Now that multiple CPU cores are very common, building the server should benefit
from this.
OpenPKG already has a mechanism to use 'make -j CPUs*2' in some situations, see
"obmtool and more than one CPU" on
http://www.kolab.org/pipermail/kolab-users/2006-January/004283.html

$ /kolab/lib/openpkg/rpmtool mflags -O make
--no-print-directory -j4
$ grep 'make.*-j4' /root/kolab-install.log |wc -l
22

It would be good to see which packages can be built with -j and enable this
optimization.

For building the initial openpkg package one could use the flags --use_make to
enable "make -j" and possibly even --use_cc to enable distcc/icecc or ccache

----------
assignedto: thomas
messages: 18603
nosy: bernhard, martin, thl, thomas, till, wilde, wrobel
priority: feature
status: unread
title: More efficient building with OpenPKG, use more CPU cores with 'make -j'
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3412>
___________________________________________________


From kolab-issues at intevation.de  Tue Feb 17 16:54:59 2009
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Tue, 17 Feb 2009 15:54:59 +0000
Subject: [Kolab-devel] [issue3413] freebusy fails after uprading
	Kolab_FreeBusy until kolabconf is run
Message-ID: <1234886099.78.0.502914159138.issue3413@intevation.de>


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

When upgrading the Kolab_FreeBusy package the file
/kolab/var/kolab/www/freebusy/config.php which is generated from a template gets
overwritten with the version in the package.

This makes access to freebusy hang until kolabconf is run again.

No .rpmsave is generated to give the admin a hint about this.
No .rpmnew is generated to let everything work without manual intervention.

I think diverting the package's config.php to .rpmnew is desired by using
%config(noreplace) in the .spec file.

Gunnar, what do you think?

----------
assignedto: wrobel
messages: 18608
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: bug
status: unread
title: freebusy fails after uprading Kolab_FreeBusy until kolabconf is run
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3413>
___________________________________________________


From liste at gelpi.it  Tue Feb 17 17:15:32 2009
From: liste at gelpi.it (Gelpi Andrea)
Date: Tue, 17 Feb 2009 17:15:32 +0100
Subject: [Kolab-devel] Amavisd configuration error?
Message-ID: <499AE2A4.8080305@gelpi.it>

Hi,
	on kolab server 2.2.0 perhaps I found a configuration error in amavisd.

In /kolab/etc/kolab/template/amavisd.conf.template the are the following lines:

$virus_admin = "virusalert\@$mydomain";

. . .

$mailfrom_notify_admin     = "virusalert\@$mydomain";
$mailfrom_notify_recip     = "virusalert\@$mydomain";

When a virus arrives amavisd try to send a mail to virusalert@$mydomain, but the from and to 
fields are the same.

The result is:

This is the mail system at host dafnen.gelpi.it.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                    The mail system

<virusalert at gelpi.it>: service unavailable. Command output: Failed to set
     recipient: Mailbox unknown.  Either there is no mailbox associated with
     this name or you do not have authorization to see it. 5.1.1 User unknown,
     code=550, original code 550


I check the distribution list and it is correctly defined.

The solution is to modify /kolab/etc/kolab/template/amavisd.conf.template
changing $virus_admin to the same value I put in distribution list.

To reproduce you have to edit:

/kolab/etc/postfix/aliases

and modify the line

root:                  /dev/null

with a real mailbox or you can't see the error.

-- 
ing. Andrea Gelpi
***************************************************
La Terra non la abbiamo ereditata dai nostri avi,
ma la abbiamo presa in prestito dai nostri bambini.
***************************************************
We do not inherit the Earth from our parents,
but borrow it from our children.
***************************************************


From kolab-issues at intevation.de  Tue Feb 17 17:19:07 2009
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Tue, 17 Feb 2009 16:19:07 +0000
Subject: [Kolab-devel] [issue3414] Kontact crash in
	KCal::IncidenceBase::isReadOnly on Refresh Cache
Message-ID: <1234887547.32.0.679202328286.issue3414@intevation.de>


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

Kontact Version 1.2.9 (enterprise35 20090206.922263)
on Debian/etch

Kontact dimap account which was configured for a Kolab server.
Account on the server was deleted and an empty account with the same login
recreated. Kontact still sees the old folders, so I wanted to use "Refresh Cache".

Then kontact crashed with the backtrace below. I can't reproduce this with a new
"Refresh Cache", I haven't tried doing all steps (removing/recreating account)
again.

Maybe the same as kolab/issue1505 (Kontact crash on rebuilding cache)?

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1243158848 (LWP 13599)]
[New Thread -1286280272 (LWP 13662)]
[New Thread -1277891664 (LWP 13661)]
[New Thread -1269503056 (LWP 13660)]
[New Thread -1261114448 (LWP 13659)]
[KCrash handler]
#5  0xb65e9be7 in KCal::IncidenceBase::isReadOnly (this=0x8b0d4b0)
    at ../libkcal/incidencebase.h:129
#6  0xb20932b9 in KCal::ResourceKolab::resolveConflict (this=0x8b0d4b0, 
    inc=0x8a61220, subresource=@0xbfcec8d0, sernum=207799)
    at resourcekolab.cpp:380
#7  0xb2093e6b in KCal::ResourceKolab::addIncidence (this=0x8b0d4b0, 
    incidence=0x8a61220, _subresource=@0x8bbb7d8, sernum=207799)
    at resourcekolab.cpp:592
#8  0xb2094511 in KCal::ResourceKolab::addEvent (this=0x8b0d4b0, 
    xml=@0x8d91fd8, subresource=@0x8bbb7d8, sernum=207799)
    at resourcekolab.cpp:651
#9  0xb2094847 in KCal::ResourceKolab::addIncidence (this=0x8b0d4b0, 
    mimetype=0xb20a6462 "application/x-vnd.kolab.event", data=@0x8b0d4b0, 
    subResource=@0x8bbb7d8, sernum=207799) at resourcekolab.cpp:396
#10 0xb2094c93 in KCal::ResourceKolab::loadSubResource (this=0x8b0d4b0, 
    subResource=@0x8bbb7d8, 
    mimetype=0xb20a6462 "application/x-vnd.kolab.event")
    at resourcekolab.cpp:195
#11 0xb2095425 in KCal::ResourceKolab::doLoadAll (this=0x8b0d4b0, 
    map=@0x8b0d5f8, mimetype=0xb20a6462 "application/x-vnd.kolab.event")
    at resourcekolab.cpp:232
#12 0xb209560d in KCal::ResourceKolab::loadAllEvents (this=0x8b0d4b0)
    at resourcekolab.cpp:241
#13 0xb209568e in KCal::ResourceKolab::fromKMailRefresh (this=0x8b0d4b0, 
    type=@0xbfcecc84) at resourcekolab.cpp:897
#14 0xb209d2c2 in Kolab::KMailConnection::fromKMailRefresh (this=0x8b13c20, 
    type=@0xbfcecc84, folder=@0xbfcecc8c) at kmailconnection.cpp:164
#15 0xb20a20d4 in Kolab::KMailConnection::process (this=0x8b13c20, 
    fun=@0xbfceced4, data=@0xbfcececc, replyType=@0xbfcecec4, 
    replyData=@0xbfcecebc) at kmailconnection_skel.cpp:77
#16 0xb7468e3d in DCOPClient::receive (this=0x8089a00, objId=@0xbfcecedc, 
    fun=@0xbfceced4, data=@0xbfcececc, replyType=@0xbfcecec4, 
    replyData=@0xbfcecebc)
    at /build/buildd/kdelibs-3.5.5a.dfsg.1/./dcop/dcopclient.cpp:1640
#17 0xb746a57c in DCOPProcessInternal (d=0x8089a30, opcode=1, key=1, 
    dataReceived=@0xbfcecf98, canPost=true)
    at /build/buildd/kdelibs-3.5.5a.dfsg.1/./dcop/dcopclient.cpp:518
#18 0xb746acb1 in DCOPProcessMessage (iceConn=0x808ab00, 
    clientObject=0x8089a30, opcode=1, length=117, replyWait=0x0, 
    replyWaitRet=0xbfced004)
    at /build/buildd/kdelibs-3.5.5a.dfsg.1/./dcop/dcopclient.cpp:430
#19 0xb747aa52 in KDE_IceProcessMessages (iceConn=0x808ab00, replyWait=0x0, 
    replyReadyRet=0x0)
    at /build/buildd/kdelibs-3.5.5a.dfsg.1/./dcop/KDE-ICE/process.c:326
#20 0xb74612d9 in DCOPClient::processSocketData (this=0x8089a00, fd=3)
    at /build/buildd/kdelibs-3.5.5a.dfsg.1/./dcop/dcopclient.cpp:2009
#21 0xb746a8a9 in DCOPClient::qt_invoke (this=0x8089a00, _id=2, _o=0xbfced1a8)
    at ./dcopclient.moc:176
#22 0xb6f7ad4f in QObject::activate_signal (this=0x80b2cd0, clist=0x80b3b08, 
    o=0xbfced1a8) at kernel/qobject.cpp:2356
#23 0xb6f7b656 in QObject::activate_signal (this=0x80b2cd0, signal=2, param=3)
    at kernel/qobject.cpp:2449
#24 0xb7304957 in QSocketNotifier::activated (this=0x80b2cd0, t0=3)
    at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#25 0xb6f9d4fa in QSocketNotifier::event (this=0x80b2cd0, e=0xbfced500)
    at kernel/qsocketnotifier.cpp:258
#26 0xb6f12c26 in QApplication::internalNotify (this=0xbfced77c, 
    receiver=0x80b2cd0, e=0xbfced500) at kernel/qapplication.cpp:2635
#27 0xb6f14a43 in QApplication::notify (this=0xbfced77c, receiver=0x80b2cd0, 
    e=0xbfced500) at kernel/qapplication.cpp:2358
#28 0xb763ae0e in KApplication::notify (this=0xbfced77c, receiver=0x80b2cd0, 
    event=0xbfced500)
    at /build/buildd/kdelibs-3.5.5a.dfsg.1/./kdecore/kapplication.cpp:550
#29 0xb6ea6421 in QApplication::sendEvent (receiver=0x80b2cd0, 
    event=0xbfced500) at ../include/qapplication.h:520
#30 0xb6f04fd9 in QEventLoop::activateSocketNotifiers (this=0x80ad230)
    at kernel/qeventloop_unix.cpp:578
#31 0xb6eba754 in QEventLoop::processEvents (this=0x80ad230, flags=4)
    at kernel/qeventloop_x11.cpp:383
#32 0xb6f2d179 in QEventLoop::enterLoop (this=0x80ad230)
    at kernel/qeventloop.cpp:198
#33 0xb6f2cf9a in QEventLoop::exec (this=0x80ad230)
    at kernel/qeventloop.cpp:145
#34 0xb6f147bf in QApplication::exec (this=0xbfced77c)
    at kernel/qapplication.cpp:2758
#35 0x0805e2d4 in main (argc=145830928, argv=0x8b07930) at main.cpp:188
#36 0xb76d0ea8 in __libc_start_main () from /lib/tls/libc.so.6
#37 0x0805dbf1 in _start () at ../sysdeps/i386/elf/start.S:119

----------
assignedto: allen
messages: 18609
nosy: allen, bernhard, bh, itsef_admin, laurent, ludwig, osterfeld, thomas, till, tmcguire, vkrause
priority: urgent
status: unread
title: Kontact crash in KCal::IncidenceBase::isReadOnly on Refresh Cache
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3414>
___________________________________________________


From kolab-issues at intevation.de  Tue Feb 17 17:47:03 2009
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Tue, 17 Feb 2009 16:47:03 +0000
Subject: [Kolab-devel] [issue3415] freebusy cache regeneration on the
	command line looks confusing
Message-ID: <1234889222.99.0.438146429744.issue3415@intevation.de>


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

When regenerating the freebusy cache on the command line as described in the
README the output on the command line is ugly:

kolab-n at host$ PHP_AUTH_USER=manager PHP_AUTH_PW='managerpassword' /kolab/bin/php
-c /kolab/etc/apache/php.ini /kolab/var/kolab/www/freebusy/regenerate.php
Regenerated calendar "user/theuser/Folder1 at example.com"!
<br/>Regenerated calendar "user/theuser/Folder1/subfolder at example.com"!
<br/>Regenerated calendar "user/theuser/Kalender at example.com"!
<br/>kolab-n at host$

Ideally the <br/> should not appear when not sending the output to a web
browser, a quick workaround would be to write <br/> at the end of each line, not
at the beginning of the next one, i.e.:

kolab-n at host$ PHP...
Regenerated calender "..."! <br/>
Regenerated calender "..."! <br/>
kolab-n at host$

----------
assignedto: wrobel
messages: 18610
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: minor bug
status: unread
title: freebusy cache regeneration on the command line looks confusing
topic: freebusy, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3415>
___________________________________________________


From kolab-issues at intevation.de  Tue Feb 17 17:57:28 2009
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Tue, 17 Feb 2009 16:57:28 +0000
Subject: [Kolab-devel] [issue3416] webclient hangs if freebusy
	triggering/retrieving hangs
Message-ID: <1234889848.5.0.694734768463.issue3416@intevation.de>


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

Due to kolab/issue3413 (freebusy fails after uprading Kolab_FreeBusy until
kolabconf is run) I had a setup where http access to free/busy hangs for a long
(maybe indefinite) time.

When creating an event in the webclient, it tries to trigger regeneration and
just hangs, too.
With non-local free/busy URLs this could be even worse, I haven't tested this.

(side note: kontact does not hang in this case)

----------
assignedto: wrobel
messages: 18611
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: urgent
status: unread
title: webclient hangs if freebusy triggering/retrieving hangs
topic: freebusy, web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3416>
___________________________________________________


From ml at radoeka.nl  Tue Feb 17 22:54:46 2009
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 17 Feb 2009 22:54:46 +0100
Subject: [Kolab-devel] Failing php tests for kolab
In-Reply-To: <20090209173733.49601h8zufubyzms@webmail.pardus.de>
References: <200902071511.47447.ml@radoeka.nl>
	<20090209173733.49601h8zufubyzms@webmail.pardus.de>
Message-ID: <200902172254.47719.ml@radoeka.nl>

Op maandag 09 februari 2009 17:37:33 schreef Gunnar Wrobel:
> Quoting Richard Bos <ml at radoeka.nl>:
> > Hi,
> >
> > I just ran tests that come with the kolab pear packages and some tests
> > are failing.  Hence I have some questions related to this.  Please find
> > the failing tests in the attachment.  This is btw on native openSUSE_11.1
> >
> > Tests seem to fail because the file Horde/Kolab/Test.php is not present;
> > What module provides the file Horde/Kolab/Test.php?
>
> That file has been removed. I think some of the tests need to be fixed
> upstream. I hope to be able to look at that soon.
>
> > A test complains that the class Horde_Kolab_IMAP is not present;
> > What module provides the class Horde_Kolab_IMAP?
> >
> > A test complains that the class Horde_Kolab_Server is not present;
> > What module provides the class Horde_Kolab_Server?
> >  Is this package
> > http://pear.horde.org/index.php?package=Horde_Kolab_Server required?  The
> > same question for Horde_Kolab_Format  (those 2
> > packages seem to
> > he superseeded by just kolab_format and kolab_server, hence my question
> > about the ones prefixed with Horde_*).
>
> The Horde_Kolab_* packages are indeed deprecated. Only the Kolab_*
> ones are relevant.

Is it possible to patch this upstream:
=== /usr/share/php5/PEAR/Horde/Kolab/IMAP/test.php ===                                                                                         
PHP Fatal error:  Class 'Horde_Kolab_IMAP' not found in /usr/share/php5/PEAR/Horde/Kolab/IMAP/test.php on line 27                              

kolab:/usr/share/php5 # diff -u /usr/share/php5/PEAR/Horde/Kolab/IMAP/test.php.org /usr/share/php5/PEAR/Horde/Kolab/IMAP/test.php
--- /usr/share/php5/PEAR/Horde/Kolab/IMAP/test.php.org  2009-02-17 22:45:39.000000000 +0100                                      
+++ /usr/share/php5/PEAR/Horde/Kolab/IMAP/test.php      2009-02-17 22:45:03.000000000 +0100                                      
@@ -5,6 +5,7 @@                                                                                                                  
  * $Horde: framework/Kolab_Server/lib/Horde/Kolab/IMAP/test.php,v 1.1.2.1 2008/10/27 09:50:35 wrobel Exp $                      
  */                                                                                                                             
                                                                                                                                 
+require_once('Horde/Kolab/IMAP.php');                                                                                           
 /**                                                                                                                             
  * Indicate that a mail has been marked as deleted                                                                              
  */                                                                                                                             


The same for this one:
kolab:/usr/share/php5 # php /srv/www/htdocs/horde/lib/Horde/Kolab/Server/ldap.php
PHP Fatal error:  Class 'Horde_Kolab_Server' not found in /srv/www/htdocs/horde/lib/Horde/Kolab/Server/ldap.php on line 27

kolab:/usr/share/php5 # diff -u /srv/www/htdocs/horde/lib/Horde/Kolab/Server/ldap.php 
/srv/www/htdocs/horde/lib/Horde/Kolab/Server/ldap.php.new--- /srv/www/htdocs/horde/lib/Horde/Kolab/Server/ldap.php       2009-02-17 
22:52:51.000000000 +0100
+++ /srv/www/htdocs/horde/lib/Horde/Kolab/Server/ldap.php.new   2009-02-17 22:51:41.000000000 +0100
@@ -9,6 +9,7 @@

 /** We need the Horde LDAP tools for this class **/
 require_once 'Horde/LDAP.php';
+require_once 'Horde/Kolab/Server.php';

-- 
Richard


From ml at radoeka.nl  Tue Feb 17 22:59:58 2009
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 17 Feb 2009 22:59:58 +0100
Subject: [Kolab-devel] php failure undefined method
	Horde_Kolab_Server_ldap::uidForIdOrMail (openSUSE native)
In-Reply-To: <200902152132.47148.ml@radoeka.nl>
References: <200902152132.47148.ml@radoeka.nl>
Message-ID: <200902172259.59040.ml@radoeka.nl>

Op zondag 15 februari 2009 21:32:46 schreef Richard Bos:
> 203 ? ? ? ? ? ? $dn = $server->uidForIdOrMail($recipient);
> 204 ? ? ? ? ? ? if (is_a($dn, 'PEAR_Error')) {
> 205 ? ? ? ? ? ? ? ? return $dn;
> 206 ? ? ? ? ? ? }

if I replace line 203 above with an straight assignment, the email is 
delivered succesfully!:

202         foreach ($this->_recipients as $recipient) {
203             # $dn = $server->uidForIdOrMail($recipient);
204             $dn = "cn=Rich Boss,dc=radoeka,dc=nl";
205             if (is_a($dn, 'PEAR_Error')) {
206                 return $dn;
207             }
208             if (!$dn) {
209                 Horde::logMessage(sprintf('User %s does not exist!', 
$recipient),
210                                   __FILE__, __LINE__, PEAR_LOG_DEBUG);
211             }
212             $user = $server->fetch($dn, KOLAB_OBJECT_USER);
213             if (is_a($user, 'PEAR_Error')) {
214                 $user->code = OUT_LOG | EX_NOUSER;
215                 return $user;
216             }

I find this weird as the rest of code uses $server-> too, like e.g. the fetch 
method on line 212.  The fetch and the uidForIdOrMail or both defined in the 
same source file...

Any idea why the uidForIdOrMail is not found?  Is the include path perhaps 
incorrect, where one uidForIdOrMail overwrites the other?

-- 
Richard


From bernhard at intevation.de  Wed Feb 18 08:40:10 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 18 Feb 2009 08:40:10 +0100
Subject: [Kolab-devel] Amavisd configuration error?
In-Reply-To: <499AE2A4.8080305@gelpi.it>
References: <499AE2A4.8080305@gelpi.it>
Message-ID: <200902180840.14558.bernhard@intevation.de>

Andrea,

thanks for the report.

Am Dienstag, 17. Februar 2009 17:15:32 schrieb Gelpi Andrea:
> The solution is to modify /kolab/etc/kolab/template/amavisd.conf.template
> changing $virus_admin to the same value I put in distribution list.

Hmm, I do not quite understand your solution. Are you saying that
changing 
$virus_admin = "virusalert\@$mydomain";
to 
$virus_admin = "virusalert at gelpi.it";

solved the issue?

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: 198 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090218/363949b7/attachment.bin

From bernhard at intevation.de  Wed Feb 18 08:41:26 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 18 Feb 2009 08:41:26 +0100
Subject: [Kolab-devel] php failure undefined method
	Horde_Kolab_Server_ldap::uidForIdOrMail (openSUSE native)
In-Reply-To: <200902172259.59040.ml@radoeka.nl>
References: <200902152132.47148.ml@radoeka.nl>
	<200902172259.59040.ml@radoeka.nl>
Message-ID: <200902180841.26875.bernhard@intevation.de>

Am Dienstag, 17. Februar 2009 22:59:58 schrieb Richard Bos:
> Any idea why the uidForIdOrMail is not found? ?Is the include path perhaps
> incorrect, where one uidForIdOrMail overwrites the other?

No idea here, I guess you would need to look up the details of pathfinding and 
debugging with php.
Gunnar should have an idea 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: 198 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090218/395d143a/attachment.bin

From kolab-issues at intevation.de  Wed Feb 18 09:02:36 2009
From: kolab-issues at intevation.de (=?utf-8?q?Albrecht_Dre=C3=9F?=)
Date: Wed, 18 Feb 2009 08:02:36 +0000
Subject: [Kolab-devel] [issue3417] Toltec series appointment w/o times in
	Horde
Message-ID: <1234944156.13.0.366669438493.issue3417@intevation.de>


New submission from Albrecht Dre? <albrecht.dress at lios-tech.com>:

I noticed that series appointments created w/ Toltec running OL 2002 SP 3 do not
have time stamps in Horde.  Steps to re-produce:

- create a series appointment on OL, e.g. from 1200 to 1300 on three days;
- sync to the server;
- open the appointment in Horde: says that it starts and ends at 0000 (see
  screenshot, merged OL and Horde display).

Looking at the "application/x-vnd.kolab.event" part stored on Cyrus, the event
actually doesn't contain any time stamps:

[snip]
<?xml version="1.0" encoding="UTF-8"?>
<event version="1.0">
  <product-id>Toltec Connector Open Format (2.0)</product-id>
  <uid>TOLTEC.40A3A71D1D544B5C83CEC449F687C542</uid>
  <creation-date>2009-02-18T07:44:29Z</creation-date>
  <last-modification-date>2009-02-18T07:44:29Z</last-modification-date>
  <sensitivity>public</sensitivity>
  <summary>Testtermin</summary>
  <start-date>2009-02-24</start-date>
  <end-date>2009-02-23</end-date>
  <show-time-as>busy</show-time-as>
  <color-label>none</color-label>
  <creator>
    <display-name>Albrecht Dre?</display-name>
    <smtp-address>albrecht.dress at my-company.com</smtp-address>
  </creator>
  <recurrence cycle="daily">
    <interval>1</interval>
    <range type="number">3</range>
  </recurrence>
</event>
[/snip]

Thus I assume this is a bug in Toltec.

----------
files: Clipboard01.png
messages: 18615
nosy: albrecht.dress
priority: bug
status: unread
title: Toltec series appointment w/o times in Horde
topic: toltec, web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3417>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Clipboard01.png
Type: image/png
Size: 36962 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090218/6361e7a9/Clipboard01-0001.png

From kolab-issues at intevation.de  Wed Feb 18 09:49:53 2009
From: kolab-issues at intevation.de (=?utf-8?q?Albrecht_Dre=C3=9F?=)
Date: Wed, 18 Feb 2009 08:49:53 +0000
Subject: [Kolab-devel] [issue3418] Shift element of appointment series w/
	Toltec: disappears in Horde
Message-ID: <1234946993.26.0.581710131889.issue3418@intevation.de>


New submission from Albrecht Dre? <albrecht.dress at lios-tech.com>:

If I create a series of appointments in Toltec and then shift /one/ of the
series to a different date, it will disappear in Horde.  I use OL 2002 SP 3,
Toltec 2.3.1 and Kolab 2.2.0 on Ubuntu/Hardy x86_64.

To reproduce:
1. create a series of appointments, say, 3 days, always 0830 to 0900.  Sync,
   properly shown in Horde;
2. edit the second /element/ (not the series!) in OL, shift the time to 0930 ..
   1000.  Sync, the shifted appointment is missing in Horde.

The XML file on the server reads

<?xml version="1.0" encoding="UTF-8"?>
<event version="1.0">
  <product-id>Toltec Connector Open Format (2.0)</product-id>
  <uid>TOLTEC.CC3117C41C2F4C8CA07E4A99731C065A</uid>
  <creation-date>2009-02-18T08:37:12Z</creation-date>
  <last-modification-date>2009-02-18T08:38:27Z</last-modification-date>
  <sensitivity>public</sensitivity>
  <summary>Test 2</summary>
  <start-date>2009-02-24T07:30:00Z</start-date>
  <end-date>2009-02-24T08:00:00Z</end-date>
  <alarm>15</alarm>
  <show-time-as>busy</show-time-as>
  <color-label>none</color-label>
  <creator>
    <display-name>Albrecht Dre?</display-name>
    <smtp-address>albrecht.dress at my-company.com</smtp-address>
  </creator>
  <recurrence cycle="daily">
    <interval>1</interval>
    <range type="number">3</range>
    <exclusion>2009-02-25</exclusion>
  </recurrence>
</event>

I.e., there is an exclusion, but it doesn't say that it actually should occur at
a different time.  Might be related to bug 3417?

----------
messages: 18620
nosy: albrecht.dress
priority: bug
status: unread
title: Shift element of appointment series w/ Toltec: disappears in Horde
topic: toltec, web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3418>
___________________________________________________


From joon at radleys.co.za  Wed Feb 18 12:11:27 2009
From: joon at radleys.co.za (Joon Radley)
Date: Wed, 18 Feb 2009 13:11:27 +0200
Subject: [Kolab-devel] [issue3417] Toltec series appointment w/o times
	in	Horde
In-Reply-To: <1234944156.13.0.366669438493.issue3417@intevation.de>
References: <1234944156.13.0.366669438493.issue3417@intevation.de>
Message-ID: <000d01c991b9$a73eae50$f5bc0af0$@co.za>

Hi Albrecht,

> I noticed that series appointments created w/ Toltec running OL 2002 SP
> 3 do not have time stamps in Horde.  Steps to re-produce:
> 
> - create a series appointment on OL, e.g. from 1200 to 1300 on three
> days;
> - sync to the server;
> - open the appointment in Horde: says that it starts and ends at 0000
> (see
>   screenshot, merged OL and Horde display).

>   <start-date>2009-02-24</start-date>

> Thus I assume this is a bug in Toltec.

This is object is detected as a whole day event, that is why the time element is not part of the start-date field.

Best Regards

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


From kolab-issues at intevation.de  Wed Feb 18 12:30:06 2009
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Wed, 18 Feb 2009 11:30:06 +0000
Subject: [Kolab-devel] [issue3419] Crash when canceling the retry dialog
	coming for deprecated non-mime OpenPKG emails after selecting
	a different email.
Message-ID: <1234956606.53.0.774211809316.issue3419@intevation.de>


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

I can reproduce a crash.
Kontact (enterprise35 20090206.922263).

* Configure Email/Security to always try to encrypt and email immedeately
* Select a deprecated non-MIME OpenPGP email.
* Cancel the upcoming pinentry dialog.
Observation: I get a retry dialog.
Expectation: The same behaviour than with real OpenPGP emails?
(I am not sure, why do I get the dialog here?)

* Now before answering the retry dialog, select a different email, e.g. a plain 
one.
* Now Cancel the retry dialog 
Observation: Crash.

----------
assignedto: marc
files: kontact-crash-20090218-1.txt
messages: 18625
nosy: allen, bernhard, ludwig, marc, till
priority: bug
status: unread
title: Crash when canceling the retry dialog coming for deprecated non-mime OpenPKG emails  after selecting a different email.
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3419>
___________________________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: kontact-crash-20090218-1.txt
Url: http://kolab.org/pipermail/kolab-devel/attachments/20090218/915a1751/kontact-crash-20090218-1.txt

From aspineux at gmail.com  Wed Feb 18 22:09:54 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Wed, 18 Feb 2009 22:09:54 +0100
Subject: [Kolab-devel] Amavisd configuration error?
In-Reply-To: <499AE2A4.8080305@gelpi.it>
References: <499AE2A4.8080305@gelpi.it>
Message-ID: <71fe4e760902181309y5c602306v262b60242c049253@mail.gmail.com>

On Tue, Feb 17, 2009 at 5:15 PM, Gelpi Andrea <liste at gelpi.it> wrote:
> Hi,
>        on kolab server 2.2.0 perhaps I found a configuration error in amavisd.
>
> In /kolab/etc/kolab/template/amavisd.conf.template the are the following lines:
>
> $virus_admin = "virusalert\@$mydomain";
>
> . . .
>
> $mailfrom_notify_admin     = "virusalert\@$mydomain";
> $mailfrom_notify_recip     = "virusalert\@$mydomain";
>
> When a virus arrives amavisd try to send a mail to virusalert@$mydomain, but the from and to
> fields are the same.
>
> The result is:
>
> This is the mail system at host dafnen.gelpi.it.
>
> I'm sorry to have to inform you that your message could not
> be delivered to one or more recipients. It's attached below.
>
> For further assistance, please send mail to postmaster.
>
> If you do so, please include this problem report. You can
> delete your own text from the attached returned message.
>
>                    The mail system
>
> <virusalert at gelpi.it>: service unavailable. Command output: Failed to set
>     recipient: Mailbox unknown.  Either there is no mailbox associated with
>     this name or you do not have authorization to see it. 5.1.1 User unknown,
>     code=550, original code 550
>
>
> I check the distribution list and it is correctly defined.
>
> The solution is to modify /kolab/etc/kolab/template/amavisd.conf.template
> changing $virus_admin to the same value I put in distribution list.

This is unclear ! Con you give an sample ?

Isn't it related to https://www.intevation.de/roundup/kolab/issue1863 ?

>
> To reproduce you have to edit:
>
> /kolab/etc/postfix/aliases
>
> and modify the line
>
> root:                  /dev/null
>
> with a real mailbox or you can't see the error.
>
> --
> ing. Andrea Gelpi
> ***************************************************
> La Terra non la abbiamo ereditata dai nostri avi,
> ma la abbiamo presa in prestito dai nostri bambini.
> ***************************************************
> We do not inherit the Earth from our parents,
> but borrow it from our children.
> ***************************************************
>
> _______________________________________________
> 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 ml at radoeka.nl  Wed Feb 18 23:09:07 2009
From: ml at radoeka.nl (Richard Bos)
Date: Wed, 18 Feb 2009 23:09:07 +0100
Subject: [Kolab-devel] php failure undefined method
	Horde_Kolab_Server_ldap::uidForIdOrMail (openSUSE native)
In-Reply-To: <200902172259.59040.ml@radoeka.nl>
References: <200902152132.47148.ml@radoeka.nl>
	<200902172259.59040.ml@radoeka.nl>
Message-ID: <200902182309.08121.ml@radoeka.nl>

Op dinsdag 17 februari 2009 22:59:58 schreef Richard Bos:
> Any idea why the uidForIdOrMail is not found? ?Is the include path perhaps
> incorrect, where one uidForIdOrMail overwrites the other?

My continues struggle with Incoming.php  This time I added debug lines to
the file, with the following result:

193         require_once 'Horde/Kolab/Server.php';
194
195         Horde::logMessage(sprintf('DEBUG: Going to Horde/Kolab/Server:singleton'), __FILE__, __LINE__, PEAR_LOG_DEBUG);
196         $server = &Horde_Kolab_Server::singleton();
197         if (is_a($server, 'PEAR_Error')) {
198             $server->code = OUT_LOG | EX_SOFTWARE;
199             return $server;
200         }
201         Horde::logMessage(sprintf('DEBUG: Left the Horde/Kolab/Server:singleton'), __FILE__, __LINE__, PEAR_LOG_DEBUG);
202         Horde::logMessage(sprintf('DEBUG: server = %s', $server), __FILE__, __LINE__, PEAR_LOG_DEBUG);
203
204         $hosts = array();
205         foreach ($this->_recipients as $recipient) {
206             Horde::logMessage(sprintf('DEBUG: Looking up %s', $recipient), __FILE__, __LINE__, PEAR_LOG_DEBUG);


Feb 18 22:45:41 kolab kolabfilter[8316]: [horde] DEBUG: Going to Horde/Kolab/Server:singleton [pid 8316 on line 195 of 
"/usr/share/php5/PEAR/Horde/Kolab/Filter/Incoming.php"]
Feb 18 22:45:41 kolab kolabfilter[8316]: [horde] DEBUG: Left the Horde/Kolab/Server:singleton [pid 8316 on line 201 of 
"/usr/share/php5/PEAR/Horde/Kolab/Filter/Incoming.php"]
Feb 18 22:45:41 kolab kolabfilter[8316]: [horde] PHP Error: Object of class Horde_Kolab_Server_ldap could not be converted to string; Code: 0 [pid 
8316 on line 176 of "/usr/share/php5/PEAR/Horde/Kolab/Filter/Response.php"]

How can I check that the code actually enters the &Horde_Kolab_Server::singleton();
I added an Horde::logMessage in to the singleton function in:
Horde/Kolab/Server.php:    function &singleton($params = null)
but nothing was printed.  Is it the wrong singleton, or is it not entered?  
If the later, why isn't it entered?

Any idea?

-- 
Richard


From liste at gelpi.it  Thu Feb 19 09:48:25 2009
From: liste at gelpi.it (Gelpi Andrea)
Date: Thu, 19 Feb 2009 09:48:25 +0100
Subject: [Kolab-devel] Amavisd configuration error?
In-Reply-To: <200902180840.14558.bernhard@intevation.de>
References: <499AE2A4.8080305@gelpi.it>
	<200902180840.14558.bernhard@intevation.de>
Message-ID: <499D1CD9.2060805@gelpi.it>

Bernhard Reiter wrote:
> Andrea,
> 
> thanks for the report.
> 
> Am Dienstag, 17. Februar 2009 17:15:32 schrieb Gelpi Andrea:
>> The solution is to modify /kolab/etc/kolab/template/amavisd.conf.template
>> changing $virus_admin to the same value I put in distribution list.
> 
> Hmm, I do not quite understand your solution. Are you saying that
> changing 
> $virus_admin = "virusalert\@$mydomain";
> to 
> $virus_admin = "virusalert at gelpi.it";
> 
> solved the issue?

Sorry, I try to clarify.

I change
$virus_admin = "virusalert\@$mydomain";
to
$virus_admin = "support\@gelpi.it";

where support at gelpi.it is the mailbox I inserted in distribution list soon after installation 
and for every new domain I added to kolab.

The problem arises when "from" and "to" fields are the same.

Another solution could be to change the from fields to something different from 
virusalert@$mydomain.

-- 
ing. Andrea Gelpi
***************************************************
La Terra non la abbiamo ereditata dai nostri avi,
ma la abbiamo presa in prestito dai nostri bambini.
***************************************************
We do not inherit the Earth from our parents,
but borrow it from our children.
***************************************************


From liste at gelpi.it  Thu Feb 19 11:04:45 2009
From: liste at gelpi.it (Gelpi Andrea)
Date: Thu, 19 Feb 2009 11:04:45 +0100
Subject: [Kolab-devel] Amavisd configuration error?
In-Reply-To: <71fe4e760902181309y5c602306v262b60242c049253@mail.gmail.com>
References: <499AE2A4.8080305@gelpi.it>
	<71fe4e760902181309y5c602306v262b60242c049253@mail.gmail.com>
Message-ID: <499D2EBD.1030806@gelpi.it>

Alain Spineux wrote:

. . .

>> The solution is to modify /kolab/etc/kolab/template/amavisd.conf.template
>> changing $virus_admin to the same value I put in distribution list.
> 
> This is unclear ! Con you give an sample ?

Please have a look to my other replay to Bernard.

> 
> Isn't it related to https://www.intevation.de/roundup/kolab/issue1863 ?
> 

I'm not sure, but perhaps. Virusalert is not defined as an alias, is it?
Is it possible that distribution list are also not checked when notification is sent to port 10026?

Here is the postfix log.

The first two messages are from amavisd to notify administrator via virusalert distribution 
list. This bounces.

Feb 13 09:34:33 dafnen <info> postfix/qmgr[642]: CFDFD107CF: from=<virusalert at gelpi.it>, 
size=4580, nrcpt=1 (queue active)

Feb 13 09:34:34 dafnen <info> postfix/pipe[11931]: CFDFD107CF: to=<virusalert at gelpi.it>, 
relay=kolabmailboxfilter, delay=0.91, delays=0.02/0.01/0/0.88, dsn=5.3.0, status=bounced 
(service unavailable. Command  output: Failed to set recipient: Mailbox unknown.  Either there 
is no mailbox associated with this name or you do not have authorization to see it. 5.1.1 User 
unknown, code=550, original code 550)

The following two are the notification to the final user destination mailbox. As you can see 
here it works.

Feb 13 09:34:33 dafnen <info> postfix/qmgr[642]: E30A610865: from=<virusalert at gelpi.it>, 
size=1136, nrcpt=1 (queue active)

Feb 13 09:34:34 dafnen <info> postfix/pipe[11934]: E30A610865: to=<agint at gelpi.it>, 
relay=kolabmailboxfilter, delay=0.36, delays=0.01/0.01/0/0.34, dsn=2.0.0, status=sent (delivered 
via kolabmailboxfilter service)


-- 
ing. Andrea Gelpi
***************************************************
La Terra non la abbiamo ereditata dai nostri avi,
ma la abbiamo presa in prestito dai nostri bambini.
***************************************************
We do not inherit the Earth from our parents,
but borrow it from our children.
***************************************************


From kolab-issues at intevation.de  Thu Feb 19 12:42:01 2009
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Thu, 19 Feb 2009 11:42:01 +0000
Subject: [Kolab-devel] [issue3420] web client prefs and hooks should be
	configurable via templates
Message-ID: <1235043720.85.0.667850729898.issue3420@intevation.de>


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

/kolab/var/kolab/www/client/config/ contains some .php files which often need to
be adjusted by the admin, but on the other hand get changed by us, too:
conf.php, prefs.php, hooks.php

For conf.php the solution is to have a template which generates the file
kolab.php which in turn gets included by conf.php.

I suggest the same mechanism for prefs.php and hooks.php, the files should be named:
conf-kolab.php (instead of just conf.php)
prefs-kolab.php
hooks-kolab.php

Maybe add a hint for admins to look at the templates in the original files.

Should templates for other files be add, too?

As this change is not very invasive it can be done after 2.2.1-rc1

----------
assignedto: wrobel
messages: 18649
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: urgent
status: unread
title: web client prefs and hooks should be configurable via templates
topic: server, web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3420>
___________________________________________________


From kolab-issues at intevation.de  Thu Feb 19 18:47:13 2009
From: kolab-issues at intevation.de (Sascha Wilde)
Date: Thu, 19 Feb 2009 17:47:13 +0000
Subject: [Kolab-devel] [issue3421] Locales with UTF8 support needed for web
	client to work properly
Message-ID: <1235065632.98.0.515426938567.issue3421@intevation.de>


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

As the subject says:
when using the web client utf8 locales must be installed and
configured at the Kolab Server system.

More precisely this was observed with the dimp frontend in german
language where a invitation mail was not displayed unless the
de_DE.UTF-8 locale was properly set up.  (de_DE and de_DE at euro _were_
already in place!)

I doubt that the web client should depend on the host configuration in
such a way.  (I'm well aware that other parts of the server have
similar problems, though.)

----------
assignedto: wrobel
messages: 18661
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: bug
status: unread
title: Locales with UTF8 support needed for web client to work properly
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3421>
___________________________________________________


From kolab-issues at intevation.de  Thu Feb 19 18:59:29 2009
From: kolab-issues at intevation.de (Tom Malone)
Date: Thu, 19 Feb 2009 17:59:29 +0000
Subject: [Kolab-devel] [issue3422] Upcoming Funambol client changes.
Message-ID: <1235066369.15.0.00734279889815.issue3422@intevation.de>


New submission from Tom Malone <tmalone at lancer-ins.com>:

I was poking around on the Funambol discussion boards and I came across 
this posting.

https://core.forge.funambol.org/ds/viewMessage.do?dsForumId=405&dsMessageId=33397

According to the author the next version of the Funambol Blackberry 
client will not support the sif format for Contacts.  It will only 
support vcard.  If you want sif support you will need to recompile the 
Blackberry client.

I have been testing the 7.1 alpha/beta version of the Blackberry client 
and I can confirm that this is indeed true.

Furthermore, according to this post on the developers list sif* is going 
to be phased out altogether.

https://core.forge.funambol.org/ds/viewMessage.do?dsForumId=402&dsMessageId=30652

It appears that the Sync4j driver in Horde will need to dynamically 
determine if the content needs to be converted rather than just assuming 
that the client wants sif.

Tom

----------
messages: 18662
nosy: tmalone
priority: wish
status: unread
title: Upcoming Funambol client changes.
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3422>
___________________________________________________


From kolab-issues at intevation.de  Thu Feb 19 20:56:03 2009
From: kolab-issues at intevation.de (Tom Malone)
Date: Thu, 19 Feb 2009 19:56:03 +0000
Subject: [Kolab-devel] [issue3423] [horde] Sync Speed Issue with large
	number of items
Message-ID: <1235073363.71.0.0762669069039.issue3423@intevation.de>


New submission from Tom Malone <tmalone at lancer-ins.com>:

We have recently changed our carrier for our Blackberries and as a result we
have run into an interesting issue.

When trying to do a refresh sync on the contacts for a user we were getting
almost constant time outs.  However, other users were not getting time outs when
trying to do a refresh of their contacts.

It turns out the the user who was having the problems had 2030 contacts while
the other users had 500 contacts.  

The sequence of events that leads to the failure is as follows:

1. The client makes a request to the server for a refresh sync.
2. The Horde reads its history database for all the entries to add and begins
   to build the response packet.  I assume that it also contacts cyrus for the
   actual data.
3. While the Horde is working the network gateway/proxy for the Blackberry
   times out and shuts down the connection for the client.

Since the gateway has already timed out the connection the client fails and the
sync process ends.

This only seems to happen on a large number of items.  If the number is small 
enough the Horde is able to get the response sent out to the client quick enough
and the sync proceeds.

I was able to monkey with the sync packet size in Sync.php to make the Horde
send its response to the client quicker.  This allowed the 2000 contacts to make
it to the client.  However, I'm sure that the issue will crop up again when
someone goes to a larger number of items.

I was wondering if there was a more elegant way of accomplishing this.  Is there
some way to split things up so that the Horde does not need to read all 2000
contacts at once?

If it could do something like read 100 contacts, build and send the packet, and
then read another 100 contacts it might speed up the whole process and avoid the
timeout issue.

Thanks for listening.
Tom

----------
messages: 18664
nosy: tmalone
priority: wish
status: unread
title: [horde] Sync Speed Issue with large number of items
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3423>
___________________________________________________


From wrobel at pardus.de  Thu Feb 19 22:29:29 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 19 Feb 2009 22:29:29 +0100
Subject: [Kolab-devel] gunnar: server Makefile,1.70,1.71
In-Reply-To: <20090216152313.GF27187.thomas@intevation.de>
References: <20090209100904.0FC3660093B@lists.intevation.de>
	<20090216152313.GF27187.thomas@intevation.de>
Message-ID: <20090219222929.17043ztzhfuzdjk0@webmail.pardus.de>

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

> * cvs at kolab.org <cvs at kolab.org> [20090209 11:09]:
>> +.PHONY: test
>> +test:
>> +	for TEST in $(PHPUNIT_TESTS); \
>> +	do                            \
>> +		$(PHPUNIT) $$TEST;    \
>> +	done
>
> Good idea to add this!
>
> And here's the report of my first run, CVS as of 20090210:

Yes, I know. Currently there are parts not yet working. As I told  
Richard recently: I hope to be able to fix that soon.

Cheers,
Gunnar

>
>
> for TEST in  
> /kolab/lib/php/test/Kolab_Format/Horde/Kolab/Format/AllTests.php  
> /kolab/lib/php/test/Kolab_Server/Horde/Kolab/Server/AllTests.php  
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/AllTests.php  
> /kolab/lib/php/test/Kolab_Filter/Horde/Kolab/Filter/AllTests.php  
> /kolab/lib/php/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/AllTests.php;  
> \
> 	do                            \
> 		/kolab/bin/phpunit $TEST;    \
> 	done
> PHPUnit 3.3.3 by Sebastian Bergmann.
>
> ..............
>
> Time: 0 seconds
>
> OK (14 tests, 56 assertions)
> PHPUnit 3.3.3 by Sebastian Bergmann.
>
> ....................IIIIIIIIIIIIIIIIIIIIII..................  60 / 119
> ...IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII......................
>
> Time: 0 seconds
>
> OK, but incomplete or skipped tests!
> Tests: 119, Assertions: 169, Incomplete: 56.
> PHPUnit 3.3.3 by Sebastian Bergmann.
>
> .....EEEEEEEEEEEEEEEEEEEEEEEE....
>
> Time: 0 seconds
>
> There were 24 errors:
>
> 1) testConstruct(Horde_Kolab_Storage_DataTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/DataTest.php:41
>
> 2) testGetCacheKey(Horde_Kolab_Storage_DataTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/DataTest.php:41
>
> 3) testDelete(Horde_Kolab_Storage_DataTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/DataTest.php:41
>
> 4) testMove(Horde_Kolab_Storage_DataTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/DataTest.php:41
>
> 5) testSave(Horde_Kolab_Storage_DataTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/DataTest.php:41
>
> 6) testObjectDeleteAll(Horde_Kolab_Storage_DataTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/DataTest.php:41
>
> 7) testConstruct(Horde_Kolab_Storage_FolderTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php:42
>
> 8) testSetName(Horde_Kolab_Storage_FolderTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php:42
>
> 9) testSave(Horde_Kolab_Storage_FolderTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php:42
>
> 10) testGetImapFailNoServer(Horde_Kolab_Storage_FolderTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php:42
>
> 11) testTrigger(Horde_Kolab_Storage_FolderTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php:42
>
> 12) testConstruct(Horde_Kolab_Storage_ListTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39
>
> 13) testListFolders(Horde_Kolab_Storage_ListTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39
>
> 14) testGetFolders(Horde_Kolab_Storage_ListTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39
>
> 15) testGetByShare(Horde_Kolab_Storage_ListTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39
>
> 16) testGetByType(Horde_Kolab_Storage_ListTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39
>
> 17) testGetDefault(Horde_Kolab_Storage_ListTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39
>
> 18) testGetForeignOwner(Horde_Kolab_Storage_ListTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39
>
> 19) testGetForeignDefault(Horde_Kolab_Storage_ListTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39
>
> 20) testCreate(Horde_Kolab_Storage_ListTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39
>
> 21) testCacheUpdate(Horde_Kolab_Storage_ListTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39
>
> 22) testRename(Horde_Kolab_Storage_ListTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39
>
> 23) testRemove(Horde_Kolab_Storage_ListTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39
>
> 24) testCaching(Horde_Kolab_Storage_ListTest)
> include_once(Horde/Notification.php): failed to open stream: No such  
> file or directory
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:299
> /kolab/lib/php/Horde/Kolab/Test/Storage.php:140
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/ListTest.php:39
>
> FAILURES!
> Tests: 33, Assertions: 50, Errors: 24.
> PHP Fatal error:  Uncaught exception 'InvalidArgumentException' in  
> /kolab/lib/php/PHPUnit/Framework/TestSuite.php:302
> Stack trace:
> #0  
> /kolab/lib/php/test/Kolab_Filter/Horde/Kolab/Filter/AllTests.php(53):  
> PHPUnit_Framework_TestSuite->addTestSuite('Horde_Kolab_Fil...')
> #1 [internal function]:  
> Horde_Kolab_Filter_AllTests::suite('Horde_Kolab_Fil...')
> #2 /kolab/lib/php/PHPUnit/Runner/BaseTestRunner.php(221):  
> ReflectionMethod->invoke(NULL, 'Horde_Kolab_Fil...')
> #3 /kolab/lib/php/PHPUnit/TextUI/Command.php(88):  
> PHPUnit_Runner_BaseTestRunner->getTest('/kolab/lib/php/...',  
> '/kolab/lib/php/...', true)
> #4 /kolab/lib/php/PHPUnit/TextUI/Command.php(701):  
> PHPUnit_TextUI_Command::main()
> #5 /kolab/bin/phpunit(44): require('/kolab/lib/php/...')
> #6 {main}
>   thrown in /kolab/lib/php/PHPUnit/Framework/TestSuite.php on line 302
> PHP Warning:  require_once(Horde/Kolab/Test.php): failed to open  
> stream: No such file or directory in  
> /kolab/lib/php/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php on  
> line 17
> PHP Fatal error:  require_once(): Failed opening required  
> 'Horde/Kolab/Test.php' (include_path='.:/kolab/lib/php') in  
> /kolab/lib/php/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php on  
> line 17
> make: *** [test] Error 255
>
> --
> 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
>
> _______________________________________________
> 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  Fri Feb 20 12:38:02 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Fri, 20 Feb 2009 11:38:02 +0000
Subject: [Kolab-devel] [issue3424] The comment of an event rejection is not
	seen with toltec
Message-ID: <1235129882.28.0.641666958588.issue3424@intevation.de>


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

tested with enterprise35 kdepim 20090213.925498
       and  toltec 2.3.2 beta 9

Test:
1. A toltec user invites a kontact user to an appointment.
2. The kontact user rejects the appointment with a comment.
3. The rejection is entered into the calendar of the toltec user, but he cannot
read the comment.
Expection: It would be possible for the toltec user to read the event.

The rejection mail calendar part looks like:
BEGIN:VCALENDAR
PRODID:-//K Desktop Environment//NONSGML libkcal 3.5//EN
VERSION:2.0
METHOD:REPLY
BEGIN:VEVENT
DTSTAMP:20090220T112031Z
ORGANIZER:MAILTO:ltest3 at test.hq
ATTENDEE;RSVP=TRUE;PARTSTAT=DECLINED;ROLE=REQ-PARTICIPANT:mailto:
 ltest1 at test.hq
COMMENT:Reject this appointment 1111\nblablabla\ntest text
X-MICROSOFT-CDO-IMPORTANCE:1
CREATED:20090220T111954Z
UID:
 040000008200E00074C5B7101A82E0080000000010AF37695593C901000000000000000010
 000000EB3A6700F779564F9F807FC71B695B62
LAST-MODIFIED:20090220T111954Z
DESCRIPTION:Zeit: Freitag\, 20. Februar 2009 14:00-15:00 (GMT+01:00) 
 Amsterdam\, Berlin\, Bern\, Rom\, Stockholm\, 
 Wien.\n\n*~*~*~*~*~*~*~*~*~*\n\n\n
SUMMARY:Test xxxx
PRIORITY:5
DTSTART:20090220T130000Z
DTEND:20090220T140000Z
TRANSP:OPAQUE
REQUEST-STATUS:2.0;Success.
BEGIN:VALARM
DESCRIPTION:Reminder
ACTION:DISPLAY
TRIGGER;VALUE=DURATION:-PT15M
END:VALARM

END:VEVENT

END:VCALENDAR

----------
assignedto: allen
messages: 18676
nosy: allen, bernhard, bh, joonradley, ludwig
priority: bug
status: unread
title: The comment of an event rejection is not seen with toltec
topic: enterprise35, kde client, kkc, toltec
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3424>
___________________________________________________


From kolab-issues at intevation.de  Fri Feb 20 14:29:26 2009
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Fri, 20 Feb 2009 13:29:26 +0000
Subject: [Kolab-devel] [issue3425] Strange conflict when another client
	updates an event
Message-ID: <1235136566.27.0.245154021794.issue3425@intevation.de>


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

Kontact 3.5.10.enterprise.0.20090213.925498-kk1

There is a conflict message coming if 
a different client updates an appointment.
I do not quite know why this happens, but here is the case for reproduction.

i) Put 2000. on an event folder on the server.
ii) sync Kontact
iii) Delete 2000. and add 2001. which is the updated appointment on the server
iv) sync Kontact
Observation: A conflict dialog comes up.
Expectation: No conflict, just the event should change.

v) select both on the conflict dialog and sync.
Observation: Two events shown in Kontact, only one object on the server.
Expectation: Two events in both, but maybe this is an infection from iv).

Note trying to delete non-existing leads to the following console messages:
QGDict::hashKeyString: Invalid null key
korganizer: IncidenceChanger::deleteIncidence for incidence "Testtermin"
korganizer: KODayMatrix::updateView() Mo Jan 26 2009, day start=Mo Jan 26 2009
libkcal: CalendarResources::beginChange()
libkcal: CalendarResources::deleteEvent
kmail: 
KMailICalIfaceImpl::deleteIncidenceKolab( /home/etch3/.kde/share/apps/kmail/dimap/.1932292954.directory/.INBOX.directory/.Kalender3.directory/Kalender, 
12835)
kmail: WARNING: findMessageBySerNum( 12835 ) invalid serial number
kmail:
kmail: Message not found, cannot remove serNum 12835
libkcal: CalendarResource::endChange()


So what is going on here?
Note for step iii) if I delete all cyrus-header before using cyrreconstruct
there is not conflict dialog coming up.
I am attaching the emails in kontact-conflict-20090220-1.zip

----------
assignedto: allen
files: kontact-conflict-20090220-1.zip
messages: 18680
nosy: allen, bernhard, ludwig, till, vkrause
priority: urgent
status: unread
title: Strange conflict when another client updates an event
topic: enterprise35, kde client, kksa
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3425>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kontact-conflict-20090220-1.zip
Type: application/zip
Size: 2556 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090220/c7095f19/kontact-conflict-20090220-1.zip

From kolab-issues at intevation.de  Fri Feb 20 17:30:18 2009
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Fri, 20 Feb 2009 16:30:18 +0000
Subject: [Kolab-devel] [issue3426] php error when sending mail with enabled
	mail filter checking
Message-ID: <1235147418.43.0.248271232724.issue3426@intevation.de>


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

In 2.2.1-beta1 and current CVS With "Mail Filter Settings -> Check messages for
mismatching From header and envelope from." enabled:

Authenticated SMTP from user at example.com to himself or to a different user in
the same domain bounces. Mails from outside (if enabled) or to outside work fine.

The bounce message just contains:
Command died with status 255: "/kolab/bin/php"

To reproduce easily, login as kolab-n and execute:
echo -e 'Subject: test\nFrom: user at example.com\nTo:
user at example.com\n\ntest'|/kolab/bin/php -c /kolab/etc/apache/php.ini -f
/kolab/bin/kolabfilter -- --host=example.com --sender=user at example.com
--recipient=user at example.com --client=192.168.11.254 --user=user at example.com
--config=/kolab/etc/kolab/kolabfilter.conf; echo $?

/kolab/var/kolab-filter/log/filter.log contains nothing except:

Feb 20 17:18:54 Kolab Filter [debug] [horde] Arguments: Horde_Argv_Values Object
(
    [sender] => user at example.com
    [recipient] => Array
        (
            [0] => user at example.com
        )

    [host] => example.com
    [client] => 192.168.11.254
    [user] => user at example.com
    [config] => /kolab/etc/kolab/kolabfilter.conf
)
 [on line 244 of "/kolab/lib/php/Horde/Kolab/Filter/Base.php"]

----------
assignedto: wrobel
messages: 18685
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: critical
status: unread
title: php error when sending mail with enabled mail filter checking
topic: filter, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3426>
___________________________________________________


From ml at radoeka.nl  Sat Feb 21 16:14:39 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sat, 21 Feb 2009 16:14:39 +0100
Subject: [Kolab-devel] php failure undefined method
	Horde_Kolab_Server_ldap::uidForIdOrMail (openSUSE native)
In-Reply-To: <200902182309.08121.ml@radoeka.nl>
References: <200902152132.47148.ml@radoeka.nl>
	<200902172259.59040.ml@radoeka.nl>
	<200902182309.08121.ml@radoeka.nl>
Message-ID: <200902211614.41008.ml@radoeka.nl>

Hi,

Op woensdag 18 februari 2009 23:09:07 schreef Richard Bos:
> > Any idea why the uidForIdOrMail is not found? ?Is the include path
> > perhaps incorrect, where one uidForIdOrMail overwrites the other?
>
> My continues struggle with Incoming.php

I found the cause of the problem!  The file Incoming.php uses the Server.php 
file that it finds at:
/srv/www/htdocs/horde/lib/Horde/Kolab/Server.php
instead of the one located at:
/usr/share/php5/PEAR/Horde/Kolab/Server.php

The diff between the 2 files contains:
-    function mailForUidOrMail($id)
+    function mailForIdOrMail($id)
     {
which clarifies the error (Call to undefined method 
Horde_Kolab_Server_ldap::uidForIdOrMail) 

The include path contains the following paths:
.:/usr/share/php5:/usr/share/php5/PEAR
So, why does the file Incoming.php uses Horde/Kolab/Server.php from 
/srv/www/htdocs/horde/lib instead of the one located at 
/usr/share/php5/PEAR???
I renamed the file /srv/www/htdocs/horde/lib/Horde/Kolab/Server.php and after 
the Incoming.php started to work correctly......

The horde package provides some files that now are also provided by the 
packages:
horde-auth
horde-group
horde-prefs
kolab-filter
kolab-format
kolab-freebusy
kolab-server
kolab-storage
Shouldn't those files be removed from the horde tarball (the files are listed 
below, under the signature)?  

Last, the horde tarball provides some kolab related files that are not 
provided in an separate module, is this as expected?
Horde/Kolab.php
Horde/Kolab/Storage/IMAP/cclient.php
Horde/Kolab/Storage/IMAP/pear.php
Horde/Kolab/Storage/IMAP.php
Horde/Kolab/Storage/IMAP/test.php
Horde/Kolab/Storage/Session.php
Horde/Prefs/kolab_imap.php
Horde/Share/kolab.php

-- 
Richard



Common files (common between horde and horde-* and kolab-* packages.  The 
files in horde look outdated (so why are they still shipped with horde?)):
Horde/Auth/kolab.php                                           
Horde/Group/kolab.php                                          
Horde/Kolab/Deprecated.php                                     
Horde/Kolab/Format/Date.php                                    
Horde/Kolab/Format.php                                         
Horde/Kolab/Format/XML/annotation.php                          
Horde/Kolab/Format/XML/contact.php                             
Horde/Kolab/Format/XML/distributionlist.php                    
Horde/Kolab/Format/XML/event.php                               
Horde/Kolab/Format/XML/hprefs.php                              
Horde/Kolab/Format/XML/note.php                                
Horde/Kolab/Format/XML.php                                     
Horde/Kolab/Format/XML/task.php                                
Horde/Kolab/Server/ldap.php
Horde/Kolab/Server/Object/address.php
Horde/Kolab/Server/Object/administrator.php
Horde/Kolab/Server/Object/domainmaintainer.php
Horde/Kolab/Server/Object/group.php
Horde/Kolab/Server/Object/maintainer.php
Horde/Kolab/Server/Object.php
Horde/Kolab/Server/Object/server.php
Horde/Kolab/Server/Object/sharedfolder.php
Horde/Kolab/Server/Object/user.php
Horde/Kolab/Server.php
Horde/Kolab/Server/test.php
Horde/Kolab/Storage/Cache.php
Horde/Kolab/Storage/Data.php
Horde/Kolab/Storage/Folder.php
Horde/Kolab/Storage/List.php
Horde/Kolab/Storage/Perms.php
Horde/Kolab/Storage.php
Horde/Prefs/kolab.php


From ml at radoeka.nl  Sat Feb 21 20:50:03 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sat, 21 Feb 2009 20:50:03 +0100
Subject: [Kolab-devel] php failure undefined method
	Horde_Kolab_Server_ldap::uidForIdOrMail (openSUSE native)
In-Reply-To: <200902211614.41008.ml@radoeka.nl>
References: <200902152132.47148.ml@radoeka.nl>
	<200902182309.08121.ml@radoeka.nl>
	<200902211614.41008.ml@radoeka.nl>
Message-ID: <200902212050.04343.ml@radoeka.nl>

Hi,

Op zaterdag 21 februari 2009 16:14:39 schreef Richard Bos:
> The include path contains the following paths:
> .:/usr/share/php5:/usr/share/php5/PEAR
> So, why does the file Incoming.php uses Horde/Kolab/Server.php from
> /srv/www/htdocs/horde/lib instead of the one located at
> /usr/share/php5/PEAR???

I've now also discovered why the file Horde/Kolab/Server.php is included from 
/srv/www/htdocs/horde/libs/Horde/Kolab/Server.php  That's because the latter 
is linked to /usr/share/php5/Horde.  Finally it is no mystery anymore :)
I'm now in the process to build a horde rpm, without the outdated kolab files 
in provided by the horde tarball....

-- 
Richard


From kolab-issues at intevation.de  Sun Feb 22 04:15:58 2009
From: kolab-issues at intevation.de (NOKIA UK PROMOTION)
Date: Sun, 22 Feb 2009 03:15:58 +0000
Subject: [Kolab-devel] [issue3427] For Your Kind Attention
Message-ID: <64452.41.220.75.3.1235271097.squirrel@mail.drn.go.id>


New submission from NOKIA UK PROMOTION <award at nokiapromotion.net>:

-- 
NOKIA Promotion Head Office
2nd Floor Berkley Square House Berkley Square
London W1J 6BD
London, United Kingdom.

OFFICIAL PRIZE NOTIFICATION

Reference Number: BT:12052005/21
Batch Number: 12/25/0034

We are pleased to inform you the result of the just concluded NOKIA UK
Online Email Winners International programs in

collaboration with the National U.K Lottery in our Anual end of Year
promotions. held on 17th of February, 2009.

Your email address has been randomly selected as one of the 16 lucky
winning address in this 2nd category draw of our Nokia

end of year promotions, you have therefore been approved to claim a total
sum of ?1,000,000.00 (One million Pound Sterlings)

in cash credited to file VERIFICATION NUMBER.: CN-435-663-6.

All participants for the online version were selected randomly from World
Wide Web sites through computer draw system and

extracted from over 100,000 unions, associations, and corporate bodies
that are listed online.

To file and claim your winnings, contact your claims agent with your:

Full Names:..........
Address:.............
Contry Of Residence:.......
Age:...............
Tel./Mobile Number:........
Verification Number:..........
Reference Number:.........
Winning Batch Number:..........

Contact Person:Mr.Peterson O'Connelly
Tel: +44-(0) 703-593-1853
Email: nokia.uk.claimsdepartment009 at msn.com

For further clarification/verification of your claims, Please call
Mr.Peterson O'Connelly or Contact him via E-mail immediately.

(nokia.uk.claimsdepartment009 at msn.com )

CONGRATULATIONS AND HAPPY NEW YEAR .

Yours Faithfully,

Mrs. Carol Jefferson
Promotions Manager.

----------
messages: 18695
nosy: award
status: unread
title: For Your Kind Attention
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3427>
___________________________________________________


From kolab-issues at intevation.de  Sun Feb 22 20:22:31 2009
From: kolab-issues at intevation.de (Richard Bos)
Date: Sun, 22 Feb 2009 19:22:31 +0000
Subject: [Kolab-devel] [issue3428] Present the checkbox in the "accept
	internet email" nicer
Message-ID: <1235330551.57.0.413596938642.issue3428@intevation.de>


New submission from Richard Bos <ml at radoeka.nl>:

This issue is similar to issue3404.
Using a table to separate the checkbox and text, for nicer formatting.
If okay I'll commit.

----------
files: settings.tpl.diff
messages: 18698
nosy: bernhard, martin, rbos, thomas, till, wilde, wrobel
priority: minor bug
status: unread
title: Present the checkbox in the "accept internet email" nicer
topic: server, web admin
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3428>
___________________________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: settings.tpl.diff
Url: http://kolab.org/pipermail/kolab-devel/attachments/20090222/2fe8b8de/settings.tpl.txt

From kolab-issues at intevation.de  Mon Feb 23 04:44:09 2009
From: kolab-issues at intevation.de (Allyce)
Date: Mon, 23 Feb 2009 03:44:09 +0000
Subject: [Kolab-devel] [issue3429] Lucia mit einem geilen Stripp
Message-ID: <920EC144.4C942E35@prima.net.ar>


New submission from Allyce <storm1975iovfr at prima.net.ar>:

Hallo, ich bin die DevoteKamilla und ich stehe auf selbstbewusste, starke
und D0minante Maenner, die sich im Bett durchsetzen koennen ohne dabei
brutal zu werden. Denn ich fuege mich gerne voll und ganz in meine
unterwuerfige Rolle und gebe mich am liebsten heissen Spielen mit Wachs,
Fesseln und Klammern hin! Aber auch fuer g-eile Spiele mit Dild0s und
Flaschen bin ich zu haben. Die Kombination aus Lust und Schmerz erregt mich
sehr und darum darfst Du mir auch gerne immer wieder mal einen saftigen
Klaps verpassen! In scharfen Lack- und Lederoutfits erwarte ich Dich Iive im
ch-at!

10 Minuten gratis mit mir chatten

20% Rabatt Aktion, jetzt chatten!

Folgende URL einfach in Deinen Browser abtippen:

www . juenger-als-erlaubt . net

----------
messages: 18699
nosy: storm1975iovfr
status: unread
title: Lucia mit einem geilen Stripp
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3429>
___________________________________________________


From g.adamczyk at netkult.eu  Mon Feb 23 10:14:42 2009
From: g.adamczyk at netkult.eu (Gregor Adamczyk)
Date: Mon, 23 Feb 2009 10:14:42 +0100
Subject: [Kolab-devel] KDE4.2: SOLVED : Unintentional Kmail starting outside
 Kontact after login
Message-ID: <49A26902.9050404@netkult.eu>

Only for information:

Unintentional starts of KMail after login are caused by:
krunner or the calendar reminder.

You can simply disable the reminder (Taskbar) and the contacts search in 
krunner settings (ALT+F2) to solve the problem.

See:
https://lists.ubuntu.com/archives/kubuntu-users/2008-December/036418.html

With best regards
G. A.


From kolab-issues at intevation.de  Mon Feb 23 19:09:55 2009
From: kolab-issues at intevation.de (Maryjane)
Date: Mon, 23 Feb 2009 18:09:55 +0000
Subject: [Kolab-devel] [issue3430] Dauerfeuchte Schlampe schluckt
Message-ID: <94C4A68C.C031068E@skynet-telecom.ro>


New submission from Maryjane <adette_breyersp at skynet-telecom.ro>:

Hallo mein Suesser! Ich bin die g-eileAlyson und ich hoere gerne Radio und
sehe auch gerne fern. Doch noch viel mehr als das geniesse ich romantische
Abende zu zweit in der Badewanne oder auch am Strand. Ich lasse mich gerne
in den verschiedensten Stellungen sanft aber ausdauernd verwoehnen! Und
natuerlich lasse ich es mir auch nicht nehmen, Dir Iive im ch-at Deinen
heissen Eierlikoer auszusaugen!

Lass mich an Deinem Schwanz lutschen

20% Rabatt Aktion, jetzt chatten!

Um mit ihr zu chatten, einfach folgende URL in Deinen Browser abtippen:

www .  juenger-als-erlaubt .  net

----------
messages: 18719
nosy: adette_breyersp
status: unread
title: Dauerfeuchte Schlampe schluckt
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3430>
___________________________________________________


From wrobel at pardus.de  Mon Feb 23 23:31:45 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Mon, 23 Feb 2009 23:31:45 +0100
Subject: [Kolab-devel] kolab 2.2.1beta -- apache+php+mysql+memcached
In-Reply-To: <20090205173007.km2dq4co0g00os0g@ox.thomasbaumann.com>
References: <20090131220858.4adff91if4swo4kw@ox.thomasbaumann.com>
	<71fe4e760902010138s2c6ef64doc2bd6ff7def43e48@mail.gmail.com>
	<20090201223315.vi3iia98hkwswog8@ox.thomasbaumann.com>
	<20090202080731.1836585ixmds7008@webmail.pardus.de>
	<20090202090254.7zzspptz0gsso8oc@ox.thomasbaumann.com>
	<20090205154516.69133v8yk65h0neo@webmail.pardus.de>
	<20090205173007.km2dq4co0g00os0g@ox.thomasbaumann.com>
Message-ID: <20090223233145.24162mynrv8b0hk4@webmail.pardus.de>

Quoting Thomas Baumann <tom at tiri.li>:

> OK. I recompiled apache-php and everything went right.
>
> See:
> http://inhalt.serviert.de/wissen/migration/kolab-2.2-beta-unter-debian-etch#apache_php
>

Cool, looks good!

I hope I'll find the time to condense some of the instructions into our wiki.

Cheers,

Gunnar

> Thanks for your help!
>
> Thomas.
>
> Zitat von Gunnar Wrobel <wrobel at pardus.de>:
>
>> Quoting Thomas Baumann <tom at tiri.li>:
>>
>>> Yes I run phpinfo from apache.
>>> What are the steps to get customized php usable from the
>>> webserver ?
>>>
>>> Which RPMs are to be recompiled ?
>>
>> The apache-php package provides mod_php for the apache server while
>> the php package provides command line PHP.
>>
>> Cheers,
>>
>> Gunnar
>>
>>>
>>> Thanks for your reply in advance.
>>>
>>> Thomas.
>>>
>>> Zitat von Gunnar Wrobel <wrobel at pardus.de>:
>>>
>>>> Quoting Thomas Baumann <tom at thomasbaumann.com>:
>>>>
>>>>> Thanks, Alain,
>>>>>
>>>>> I got (as referred in my link on http://inhalt.serviert.de )
>>>>>
>>>>> checking for MySQL support... yes
>>>>> checking for specified location of the MySQL UNIX socket... no
>>>>> checking for MySQL UNIX socket location... no
>>>>> checking for mysql_close in -lmysqlclient... yes
>>>>> checking for MySQLi support... no
>>>>> checking whether to enable embedded MySQLi support... no
>>>>> checking for ncurses support... no
>>>>>
>>>>> So everything looks fine. Even the RPM builds correctly.
>>>>>
>>>>> But when I install and look after my phpinfo there
>>>>> is nothing about mysql nor memcache :-(
>>>>
>>>> Maybe you are running phpinfo() via the Apache (using mod_php which is
>>>> represented by the apache-php pacakge on OpenPKG) rather than on the
>>>> command line. It looks as you are compiling the php package and this
>>>> will only modify the command line PHP.
>>>>
>>>> Cheers,
>>>>
>>>> Gunnar
>>>>
>>>>>
>>>>> That's what I cannot understand.
>>>>>
>>>>> Hope sb can help me further.
>>>>>
>>>>> Thanks for your reply in advance,
>>>>>
>>>>> thomas.
>>>>>
>>>>> Zitat von Alain Spineux <aspineux at gmail.com>:
>>>>>
>>>>>> On Sat, Jan 31, 2009 at 10:08 PM, Thomas Baumann
>>>>>> <tom at thomasbaumann.com> wrote:
>>>>>>> Hello list,
>>>>>>>
>>>>>>> I tried to get PHP5 working with mysql but I didnt succeed.
>>>>>>>
>>>>>>> I succeeded in rebuild mysql to
>>>>>>> mysql-5.1.30-20090102.ix86-debian4.0-kolab.rpm
>>>>>>> (taken from openpkg).
>>>>>>> I succeeded in rebuild
>>>>>>> libevent-1.4.9-20081222.ix86-debian4.0-kolab.rpm and
>>>>>>> memcached-1.3.0-20090130.ix86-debian4.0-kolab.rpm to get all
>>>>>>> dependencies
>>>>>>> to my php.src.rpm
>>>>>>>
>>>>>>> I did a
>>>>>>>
>>>>>>> /kolab/bin/openpkg rpm -ivh php-5.2.8-20081209_kolab.src.rpm
>>>>>>>
>>>>>>> went to
>>>>>>>
>>>>>>> cd /kolab/RPM/SRC/php
>>>>>>>
>>>>>>> and tried to recompile with
>>>>>>>
>>>>>>> /kolab/bin/openpkg rpm -ba --define 'with_mysql yes' \
>>>>>>>      --define 'with_pecl_memcache yes'  php.spec
>>>>>>
>>>>>> The command looks correct !
>>>>>>
>>>>>> Usually, I skip the rpm -i and use a rpm --build like this :
>>>>>>
>>>>>> /kolab/bin/openpkg rpm --rebuild \
>>>>>>      php-5.2.8-20081209_kolab.src.rpm \
>>>>>>      --define 'with_mysql yes' \
>>>>>>      --define 'with_pecl_memcache yes'  php.spec
>>>>>>
>>>>>> Did you install mysql first, before to build your php package ?
>>>>>>
>>>>>> I tried it myself, with mysql installed, but get this :
>>>>>>
>>>>>> # /kolab/bin/openpkg rpm --rebuild
>>>>>> /s0/emailgency/kolab_src/php-5.2.6-20080514_kolab.src.rpm --define
>>>>>> 'with_mysql yes' --define 'with_mysql yes'
>>>>>> ......
>>>>>> checking for specified location of the MySQL UNIX socket... no
>>>>>> checking for MySQL UNIX socket location... no
>>>>>> checking for mysql_close in -lmysqlclient... no
>>>>>> checking for mysql_error in -lmysqlclient... no
>>>>>> configure: error: mysql configure failed. Please check config.log for
>>>>>> more information.
>>>>>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.71712 (%build)
>>>>>>
>>>>>> Hope this give you some ideas
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> But the result was a installable rpm-file, but it lacks on
>>>>>>> mysql and pecl-memcache support.
>>>>>>>
>>>>>>> What is going wrong - or what do i have to type to get
>>>>>>> a RPM-file with all support as in the original but additional with
>>>>>>> mysql and memcache support ?
>>>>>>>
>>>>>>> The compile log is visible on
>>>>>>>
>>>>>>> http://inhalt.serviert.de/ -->
>>>>>>> http://inhalt.serviert.de/wissen/migration/kolab-2.2-beta-unter-debian-etch
>>>>>>> ->
>>>>>>> php_recompile
>>>>>>>
>>>>>>> Thanks for your reply in advance.
>>>>>>>
>>>>>>> Thomas.
>>>>>>>
>>>>>>> --
>>>>>>> Thomas Baumann
>>>>>>>
>>>>>>> B?cher und mehr im Internet - meine neue Site: http://www.1-search.de
>>>>>>> - Viel Spass!
>>>>>>>
>>>>>>> ----------------------------------------------------------------
>>>>>>> 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
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> B?cher und mehr im Internet - meine neue Site: http://www.1-search.de
>>>>> - Viel Spass!
>>>>>
>>>>> ----------------------------------------------------------------
>>>>> 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.
>>>
>>>
>>>
>>> --
>>> tiri Limited & Co. KG
>>> Johann-Adolf-Hasse-Str. 2b
>>> 21493 Schwarzenbek
>>>
>>> Gesch?ftsf?hrerin: Anja Baumann
>>>
>>> Sitz der Gesellschaft: Schwarzenbek
>>>
>>> Handelsregister: HRA 5078 HL
>>> USt.-ID: DE254262065
>>>
>>> Pers?nlich haftender Gesellschafter: tiri Limited
>>>
>>> tiri Limited ist eine Gesellschaft nach englischem Recht, zugelassen
>>> bei Companies House zu Cardiff, Company No. 05178378, Registered
>>> Office: 39-40 Calthorpe Road, Birmingham, West Midlands, B15 1TS,
>>> United Kingdom
>>>
>>> ----------------------------------------------------------------
>>> 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.
>
>
>
> --
> tiri GmbH
> Lauenburger Str. 31a
> 21493 Schwarzenbek
> Tel. 04151 8674995
> Fax. 04151 8674996
> Net. http://www.tiri.li
>
> Gesch?ftsf?hrer: Anja Baumann, Thomas Baumann
> Sitz Schwarzenbek, Amtsgericht L?beck, HRB 8837 HL
>
> ----------------------------------------------------------------
> 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://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  Tue Feb 24 03:08:33 2009
From: kolab-issues at intevation.de (Cristina)
Date: Tue, 24 Feb 2009 02:08:33 +0000
Subject: [Kolab-devel] [issue3431] Geil mit dem Dild0 gew.ichst
Message-ID: <AF27D74B.36C27F43@012.net.il>


New submission from Cristina <ekm-manchingiiuci at 012.net.il>:

Hallo mein Suesser! Ich bin Dein scharfer s.e:xENGEL, was aber keinesfalls
bedeutet das ich immer nur sanftmuetig bin! Denn auch ein Engel kann mal
D0minant und frech sein. Doch wenn Du es schaffst mich dahinschmelzen zu
lassen, dann liege ich Dir vollkommen zu Fuessen! Vor allem, wenn Du mir mit
Deinen Haenden und Deinen Lippen einheizt, kann ich Dir garantiert keinen
Wunsch abschlagen und geniesse es, Dir dann auch jede Menge Gutes zu tun!
Wenn Du nicht nur stark und phantasievoll bist, sondern auch ueber Potenz
und Ausdauer verfuegst, dann kannst Du Dich darauf einstellen, mit mir
zusammen Iive im ch-at die heissesten Naechte Deines Lebens durch zu machen!

In meinem Chat geht die Post ab

20% Rabatt Aktion, jetzt chatten!

Um mit ihr zu chatten, einfach folgende URL in Deinen Browser abtippen:

www .  juenger-als-erlaubt .  net

----------
messages: 18722
nosy: ekm-manchingiiuci
status: unread
title: Geil mit dem Dild0 gew.ichst
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3431>
___________________________________________________


From kolab-issues at intevation.de  Tue Feb 24 03:43:04 2009
From: kolab-issues at intevation.de (Senator David Mark)
Date: Tue, 24 Feb 2009 02:43:04 +0000
Subject: [Kolab-devel] [issue3432] Our Ref: FGN /SNT/STB
Message-ID: <20090224020037.M74113@ikobo.com>


New submission from Senator David Mark <info at atm.com>:

CHAIRMAN SENATE COMMITTEE ON FOREIGN PAYMENT.
OFFICE OF THE SENATE HOUSE
FEDERAL REPUBLIC OF NIGERIA
COMMITTEE ON FOREIGN PAYMENT
(RESOLUTION PANEL ON CONTRACT PAYMENT)
IKOYI-LAGOS NIGERIA
Our Ref: FGN /SNT/STB

This is to officially inform you that (ATM Card Number 4278763100030014) has been
accredited with your favor.Your Personal 

Identification Number is 882.The ATM Card Value is $6.8MILLION USD. You are advised to
contact my Secretary  for delivery as 

soon as possible:

Mrs. Linda Hills
Email:lindahillpayout822 at yahoo.com.hk

with the following information's
FULL NAME:
DELIVERY ADDRESS:  
PHONE NUMBER:  
COUNTRY: 
OCCUPATION: 
SEX:
AGE: 
EMAIL:

KINDEST REGARDS,
(SEN).DAVID MARK
CONTACT:+2348032727700
CHAIRMAN SENATE COMMITTEE ON FOREIGN PAYMENT.

----------
messages: 18723
nosy: info14
status: unread
title: Our Ref: FGN /SNT/STB
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3432>
___________________________________________________


From kolab-issues at intevation.de  Tue Feb 24 08:07:11 2009
From: kolab-issues at intevation.de (Audrye)
Date: Tue, 24 Feb 2009 07:07:11 +0000
Subject: [Kolab-devel] [issue3434] Blankrasierte blonde Goere beim Dild0f-ick
Message-ID: <B6C7DBF0.EAC56306@telenet.ru>


New submission from Audrye <strasshoferjtac at telenet.ru>:

Hallo mein Suesser! Ich bin Deine g-eileSummer und in meiner Freizeit spiele
ich gerne Fussball, Squash und treibe auch sonst viel Sport. Ganz besonders
liebe ich reiche und nette Maenner und auch von blonden Haaren und blauen
Augen lasse ich mich nur zu gerne verzaubern! Zum s.e:x gehoeren fuer mich
auf jeden Fall eine Menge Romantik, aber hin und wieder will ich auch
einfach nur gnadenlos hart durchgestossen werden! Und nun willst Du sicher
wissen, wonach mir in diesem Moment der Sinn steht? Na, dann komm zu mir und
finde es heraus - Iive im ch-at!

In meinem Chat geht die Post ab

http://Adrian.chatte-jetzt-versaut-live.net

----------
messages: 18726
nosy: strasshoferjtac
status: unread
title: Blankrasierte blonde Goere beim Dild0f-ick
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3434>
___________________________________________________


From g.adamczyk at netkult.eu  Tue Feb 24 09:44:34 2009
From: g.adamczyk at netkult.eu (Gregor Adamczyk)
Date: Tue, 24 Feb 2009 09:44:34 +0100
Subject: [Kolab-devel] KDE 4.2 Reminder / Korganizer does not work with
	Kolab configuration
Message-ID: <49A3B372.8000003@netkult.eu>

Hello, I have at the moment the problem that on my KDE 4.2 System, 
Kontact does not inform / alarm me about the appointments.

I spend some time to test different configurations.

Kontact / Korganizer Alarms works fine with the local calender but not 
the Kolab IMAP one.

Any Idea?

Regards,
G.A.


From kolab-issues at intevation.de  Tue Feb 24 12:00:32 2009
From: kolab-issues at intevation.de (Sascha Wilde)
Date: Tue, 24 Feb 2009 11:00:32 +0000
Subject: [Kolab-devel] [issue3435] Delivery of invitations fails with no
	"kolabInvitationPolicy" is in ldap
Message-ID: <1235473232.31.0.730778763367.issue3435@intevation.de>


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

When an invitation is delivered to an user with no
"kolabInvitationPolicy" attribute, the resource manager fails and the
mail is not delivered.  From the log file:

  PHP Error: Invalid argument supplied for foreach(); Code: 0 [on line 95 of
"/home/kolab/lib/php/Horde/Kolab/Resource.php"]

This problem is new: in Kolab Server 2.2.0 the default in this case
used to be "ACT_MANUAL".  Which IMO is an sensible default.

The old behavior should be restored for 2.2.1.

----------
assignedto: wrobel
messages: 18731
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: urgent
status: unread
title: Delivery of invitations fails with no "kolabInvitationPolicy" is in ldap
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3435>
___________________________________________________


From bernhard at intevation.de  Tue Feb 24 12:33:02 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 24 Feb 2009 12:33:02 +0100
Subject: [Kolab-devel] KDE 4.2 Reminder / Korganizer does not work with
	Kolab configuration
In-Reply-To: <49A3B372.8000003@netkult.eu>
References: <49A3B372.8000003@netkult.eu>
Message-ID: <200902241233.05752.bernhard@intevation.de>

Am Dienstag, 24. Februar 2009 09:44:34 schrieb Gregor Adamczyk:
> Hello, I have at the moment the problem that on my KDE 4.2 System,
> Kontact does not inform / alarm me about the appointments.
>
> I spend some time to test different configurations.
>
> Kontact / Korganizer Alarms works fine with the local calender but not
> the Kolab IMAP one.

There used to be recent issue for this, you can search the tracker.
In general note
http://wiki.kolab.org/index.php/Problem_reporting

| Your main source for help is the Kolab users mailing list
| If you send an report or a request for support to this mailing list, please 
make sure you include the following information: 
| The version of your Kolab Clients

-- 
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: 198 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090224/ff092792/attachment.bin

From torleif at askedal.net  Tue Feb 24 09:59:36 2009
From: torleif at askedal.net (Torleif)
Date: Tue, 24 Feb 2009 09:59:36 +0100 (CET)
Subject: [Kolab-devel] kolab install
Message-ID: <5479.144.177.50.6.1235465976.squirrel@www.askedal.net>

Just installed Kolab 2.2.1 beta from source on debian 4 (i686).
I can not get the login screen to horde. (https://my.domain.net/horde)
But the admin page works, also https://my.domain.net/fbview works.
Can anybody help?
Should I go for the binary install instead?

Regards

Torleif


From thomas at intevation.de  Tue Feb 24 18:23:40 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Tue, 24 Feb 2009 18:23:40 +0100
Subject: [Kolab-devel] kolab install
In-Reply-To: <5479.144.177.50.6.1235465976.squirrel@www.askedal.net>
References: <5479.144.177.50.6.1235465976.squirrel@www.askedal.net>
Message-ID: <20090224172340.GG6196.thomas@intevation.de>

* Torleif <torleif at askedal.net> [20090224 18:04]:
> Just installed Kolab 2.2.1 beta from source on debian 4 (i686).
> I can not get the login screen to horde. (https://my.domain.net/horde)
> But the admin page works, also https://my.domain.net/fbview works.
> Can anybody help?
> Should I go for the binary install instead?

Use /client instead of /horde ... the next prerelease will contain a
redirect from /horde to /client

Regards,
Thomas Arendsen Hein

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


From ml at radoeka.nl  Tue Feb 24 23:55:37 2009
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 24 Feb 2009 23:55:37 +0100
Subject: [Kolab-devel] thomas: server release-notes.txt,1.387,1.388
In-Reply-To: <20090224164727.190E3600920@lists.intevation.de>
References: <20090224164727.190E3600920@lists.intevation.de>
Message-ID: <200902242355.38317.ml@radoeka.nl>

Hello,

some questions related to newly released kolab packages and packaging them on 
openSUSE:

Op dinsdag 24 februari 2009 17:47:27 schreef cvs at kolab.org:
> + ? ?- Horde_Notification-0.0.2-20090223
> +
> +???????New package needed for running unit tests of Kolab PHP packages.

Which module is really using this module when tests are executed?  Are e.g. 
tests in kolab-filter using methods from this Horde_Notification module?
  I would like to know this to determine which rpm should pull in this package 
as a dependency.  Or do all kolab-* packages requires this package?

> + ? ?- Horde_Prefs-0.0.3-20090223
> +
> +???????New package needed for running unit tests of Kolab PHP packages.
> +
> ? ? ?- Kolab_Filter-0.1.4-20090224

The build of this package results in some files on unexpected locations.  
These files are:
   /usr/share/doc/packages/kolab-filter/Kolab_Filter/man/man1/kolabfilter.1
   /usr/share/php5/PEAR/data/Kolab_Filter/locale/de_DE/LC_MESSAGES/Kolab_Filter.mo

I would expect the file  
/usr/share/doc/packages/kolab-filter/Kolab_Filter/man/man1/kolabfilter.1 to 
end up in  /usr/share/man/man1  Is to possible to enforce this location with 
the pear install command?  Is something like this: 
pear -d man_dir=/usr/share/man
possible?  It does not work for me.  This is explainable if I read this page:
http://pear.php.net/manual/en/guide.users.commandline.config.php

Is the file Kolab_Filter.mo going to be stored at the right spot, see listing 
above?

-- 
Richard


From wrobel at pardus.de  Wed Feb 25 08:28:46 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 25 Feb 2009 08:28:46 +0100
Subject: [Kolab-devel] thomas: server release-notes.txt,1.387,1.388
In-Reply-To: <200902242355.38317.ml@radoeka.nl>
References: <20090224164727.190E3600920@lists.intevation.de>
	<200902242355.38317.ml@radoeka.nl>
Message-ID: <20090225082846.29327c8yzf4hhnok@webmail.pardus.de>

Quoting Richard Bos <ml at radoeka.nl>:

> Hello,
>
> some questions related to newly released kolab packages and packaging them on
> openSUSE:
>
> Op dinsdag 24 februari 2009 17:47:27 schreef cvs at kolab.org:
>> +    - Horde_Notification-0.0.2-20090223
>> +
>> +       New package needed for running unit tests of Kolab PHP packages.
>
> Which module is really using this module when tests are executed?  Are e.g.
> tests in kolab-filter using methods from this Horde_Notification module?
>   I would like to know this to determine which rpm should pull in  
> this package
> as a dependency.  Or do all kolab-* packages requires this package?

The modules Kolab_Storage, Kolab_FreeBusy, and Kolab_Filter use these  
new modules for their unit tests. I only added these optional  
dependencies in Kolab_Filter at the moment (see that package spec).

Currently running the tests on an OpenPKG system yields:

PHPUnit 3.3.3 by Sebastian Bergmann.

..............

Time: 0 seconds

OK (14 tests, 58 assertions)
PHPUnit 3.3.3 by Sebastian Bergmann.

.......IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII...................  60 / 121
.......................................IIIIIIIIIIIIIIIIIIIII 120 / 121
I

Time: 0 seconds

OK, but incomplete or skipped tests!
Tests: 121, Assertions: 177, Incomplete: 56.
PHPUnit 3.3.3 by Sebastian Bergmann.

...........................F.....

Time: 1 second

There was 1 failure:

1) testGetImapFailNoServer(Horde_Kolab_Storage_FolderTest)
Failed asserting that two strings are equal.
expected string <localhost>
difference      <xxxxxxxxx???????>
got string      <imap.example.org>
/kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php:167

FAILURES!
Tests: 33, Assertions: 197, Failures: 1.
PHPUnit 3.3.3 by Sebastian Bergmann.

.....................

Time: 2 seconds

OK (21 tests, 44 assertions)
PHP Warning:  require_once(Horde/Kolab/Test.php): failed to open  
stream: No such file or directory in  
/kolab/lib/php/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php on  
line 17
PHP Fatal error:  require_once(): Failed opening required  
'Horde/Kolab/Test.php' (include_path='.:/kolab/lib/php') in  
/kolab/lib/php/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php on  
line 17
make: *** [test] Fehler 255

Basically 1 failure in Kolab_Storage and some bigger problems in  
Kolab_FreeBusy.

Kolab_FreeBusy is still on my ToDo-List.


>
>> +    - Horde_Prefs-0.0.3-20090223
>> +
>> +       New package needed for running unit tests of Kolab PHP packages.
>> +
>>      - Kolab_Filter-0.1.4-20090224
>
> The build of this package results in some files on unexpected locations.
> These files are:
>    /usr/share/doc/packages/kolab-filter/Kolab_Filter/man/man1/kolabfilter.1
>     
> /usr/share/php5/PEAR/data/Kolab_Filter/locale/de_DE/LC_MESSAGES/Kolab_Filter.mo
>
> I would expect the file
> /usr/share/doc/packages/kolab-filter/Kolab_Filter/man/man1/kolabfilter.1 to
> end up in  /usr/share/man/man1  Is to possible to enforce this location with
> the pear install command?  Is something like this:
> pear -d man_dir=/usr/share/man
> possible?  It does not work for me.  This is explainable if I read this page:
> http://pear.php.net/manual/en/guide.users.commandline.config.php

Indeed that does not work. If you look at the Kolab_Filter.spec you  
see that I move that file manually into the correct location. PEAR  
does not know about man files at the moment. Then again there are not  
really that many people writing command line tools in PHP anyhow.  
Though I guess this will appear more and more often and I hope they  
are going to make the PEAR installer into a more decent package  
management tool soon.

>
> Is the file Kolab_Filter.mo going to be stored at the right spot, see listing
> above?

I still have to figure out where to place this one on the Kolab  
server. Storing translations in PEAR packages is something also not  
really supported. I guess Horde will lead the field in that area as we  
will need a solution for that soon as we are currently working on  
Horde 4 which will require support for this, too.

Cheers,

Gunnar

>
> --
> Richard
>
> _______________________________________________
> 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/20090225/4f79bd59/attachment.bin

From wrobel at pardus.de  Wed Feb 25 09:06:09 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 25 Feb 2009 09:06:09 +0100
Subject: [Kolab-devel] php failure undefined
	method	Horde_Kolab_Server_ldap::uidForIdOrMail (openSUSE native)
In-Reply-To: <200902212050.04343.ml@radoeka.nl>
References: <200902152132.47148.ml@radoeka.nl>
	<200902182309.08121.ml@radoeka.nl> <200902211614.41008.ml@radoeka.nl>
	<200902212050.04343.ml@radoeka.nl>
Message-ID: <20090225090609.21231u3mzq9a7g9w@webmail.pardus.de>

Quoting Richard Bos <ml at radoeka.nl>:

> Hi,
>
> Op zaterdag 21 februari 2009 16:14:39 schreef Richard Bos:
>> The include path contains the following paths:
>> .:/usr/share/php5:/usr/share/php5/PEAR
>> So, why does the file Incoming.php uses Horde/Kolab/Server.php from
>> /srv/www/htdocs/horde/lib instead of the one located at
>> /usr/share/php5/PEAR???
>
> I've now also discovered why the file Horde/Kolab/Server.php is included from
> /srv/www/htdocs/horde/libs/Horde/Kolab/Server.php  That's because the latter
> is linked to /usr/share/php5/Horde.

This sounds bad. I hope you did not leave it that way :)

I know that https://www.intevation.de/roundup/kolab/issue3293 (Big  
code duplication and code version messup: Horde libs in 2.2.1) does  
not make things easy at the moment.

I consider the core of the problem to be the current release scheme we  
have upstream within Horde 3. That problem will only be solved with  
Horde 4.

In any case you should have the PEAR packages installating in  
/usr/share/php/. And the kolab-webclient should install the whole  
thing again in /srv/www/htdocs/horde again.

Kolab OpenPKG will soon change that slightly to remove packages that  
are congruent between /kolab/var/kolab/www/client/lib/Horde and  
/kolab/lib/php/Horde (respectively /kolab/var/kolab/www/client/pear  
and /kolab/lib/php).

But that is also just an intermediate solution until we reach Horde 4.

Cheers,

Gunnar

> Finally it is no mystery anymore :)
> I'm now in the process to build a horde rpm, without the outdated kolab files
> in provided by the horde tarball....
>
> --
> Richard
>
> _______________________________________________
> 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/20090225/fc1119bc/attachment-0001.bin

From wrobel at pardus.de  Wed Feb 25 09:07:43 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 25 Feb 2009 09:07:43 +0100
Subject: [Kolab-devel] Failing php tests for kolab
In-Reply-To: <200902172254.47719.ml@radoeka.nl>
References: <200902071511.47447.ml@radoeka.nl>
	<20090209173733.49601h8zufubyzms@webmail.pardus.de>
	<200902172254.47719.ml@radoeka.nl>
Message-ID: <20090225090743.76403svqnp9zosb4@webmail.pardus.de>

Quoting Richard Bos <ml at radoeka.nl>:

> Op maandag 09 februari 2009 17:37:33 schreef Gunnar Wrobel:
>> Quoting Richard Bos <ml at radoeka.nl>:
>> > Hi,
>> >
>> > I just ran tests that come with the kolab pear packages and some tests
>> > are failing.  Hence I have some questions related to this.  Please find
>> > the failing tests in the attachment.  This is btw on native openSUSE_11.1
>> >
>> > Tests seem to fail because the file Horde/Kolab/Test.php is not present;
>> > What module provides the file Horde/Kolab/Test.php?
>>
>> That file has been removed. I think some of the tests need to be fixed
>> upstream. I hope to be able to look at that soon.
>>
>> > A test complains that the class Horde_Kolab_IMAP is not present;
>> > What module provides the class Horde_Kolab_IMAP?
>> >
>> > A test complains that the class Horde_Kolab_Server is not present;
>> > What module provides the class Horde_Kolab_Server?
>> >  Is this package
>> > http://pear.horde.org/index.php?package=Horde_Kolab_Server required?  The
>> > same question for Horde_Kolab_Format  (those 2
>> > packages seem to
>> > he superseeded by just kolab_format and kolab_server, hence my question
>> > about the ones prefixed with Horde_*).
>>
>> The Horde_Kolab_* packages are indeed deprecated. Only the Kolab_*
>> ones are relevant.
>
> Is it possible to patch this upstream:
> === /usr/share/php5/PEAR/Horde/Kolab/IMAP/test.php ===
> PHP Fatal error:  Class 'Horde_Kolab_IMAP' not found in  
> /usr/share/php5/PEAR/Horde/Kolab/IMAP/test.php on line 27
>
> kolab:/usr/share/php5 # diff -u  
> /usr/share/php5/PEAR/Horde/Kolab/IMAP/test.php.org  
> /usr/share/php5/PEAR/Horde/Kolab/IMAP/test.php
> --- /usr/share/php5/PEAR/Horde/Kolab/IMAP/test.php.org  2009-02-17  
> 22:45:39.000000000 +0100
> +++ /usr/share/php5/PEAR/Horde/Kolab/IMAP/test.php      2009-02-17  
> 22:45:03.000000000 +0100
> @@ -5,6 +5,7 @@
>   * $Horde: framework/Kolab_Server/lib/Horde/Kolab/IMAP/test.php,v  
> 1.1.2.1 2008/10/27 09:50:35 wrobel Exp $
>   */
>
> +require_once('Horde/Kolab/IMAP.php');
>  /**
>   * Indicate that a mail has been marked as deleted
>   */
>
>
> The same for this one:
> kolab:/usr/share/php5 # php  
> /srv/www/htdocs/horde/lib/Horde/Kolab/Server/ldap.php
> PHP Fatal error:  Class 'Horde_Kolab_Server' not found in  
> /srv/www/htdocs/horde/lib/Horde/Kolab/Server/ldap.php on line 27
>
> kolab:/usr/share/php5 # diff -u  
> /srv/www/htdocs/horde/lib/Horde/Kolab/Server/ldap.php
> /srv/www/htdocs/horde/lib/Horde/Kolab/Server/ldap.php.new---  
> /srv/www/htdocs/horde/lib/Horde/Kolab/Server/ldap.php       2009-02-17
> 22:52:51.000000000 +0100
> +++ /srv/www/htdocs/horde/lib/Horde/Kolab/Server/ldap.php.new    
> 2009-02-17 22:51:41.000000000 +0100
> @@ -9,6 +9,7 @@
>
>  /** We need the Horde LDAP tools for this class **/
>  require_once 'Horde/LDAP.php';
> +require_once 'Horde/Kolab/Server.php';

This sounds wrong. Do you still have that particular problem?

Cheers,

Gunnar

>
> --
> Richard
>
> _______________________________________________
> 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/20090225/8d6f3c12/attachment.bin

From ml at radoeka.nl  Wed Feb 25 10:02:14 2009
From: ml at radoeka.nl (Richard Bos)
Date: Wed, 25 Feb 2009 10:02:14 +0100
Subject: [Kolab-devel] php failure undefined
	method	Horde_Kolab_Server_ldap::uidForIdOrMail (openSUSE native)
In-Reply-To: <20090225090609.21231u3mzq9a7g9w@webmail.pardus.de>
References: <200902152132.47148.ml@radoeka.nl>
	<200902182309.08121.ml@radoeka.nl>
	<200902211614.41008.ml@radoeka.nl>
	<200902212050.04343.ml@radoeka.nl>
	<20090225090609.21231u3mzq9a7g9w@webmail.pardus.de>
Message-ID: <20090225090214.GA26295@xs4all.nl>

Hi Gunnar!

On Wed, Feb 25, 2009 at 09:06:09AM +0100, Gunnar Wrobel wrote:
> Quoting Richard Bos <ml at radoeka.nl>:
> 
> >Hi,
> >
> >Op zaterdag 21 februari 2009 16:14:39 schreef Richard Bos:
> >>The include path contains the following paths:
> >>.:/usr/share/php5:/usr/share/php5/PEAR
> >>So, why does the file Incoming.php uses Horde/Kolab/Server.php from
> >>/srv/www/htdocs/horde/lib instead of the one located at
> >>/usr/share/php5/PEAR???
> >
> >I've now also discovered why the file Horde/Kolab/Server.php is included 
> >from
> >/srv/www/htdocs/horde/libs/Horde/Kolab/Server.php  That's because the 
> >latter
> >is linked to /usr/share/php5/Horde.
> 
> This sounds bad. I hope you did not leave it that way :)

Hmmm, it should have been:
/srv/www/htdocs/horde/libs is linked to /usr/share/php5/Horde
which is not so bad ;)

> I know that https://www.intevation.de/roundup/kolab/issue3293 (Big  
> code duplication and code version messup: Horde libs in 2.2.1) does  
> not make things easy at the moment.
> 
> I consider the core of the problem to be the current release scheme we  
> have upstream within Horde 3. That problem will only be solved with  
> Horde 4.
> 
> In any case you should have the PEAR packages installating in  
> /usr/share/php/. And the kolab-webclient should install the whole  
> thing again in /srv/www/htdocs/horde again.
> 
> Kolab OpenPKG will soon change that slightly to remove packages that  
> are congruent between /kolab/var/kolab/www/client/lib/Horde and  
> /kolab/lib/php/Horde (respectively /kolab/var/kolab/www/client/pear  
> and /kolab/lib/php).
> 
> But that is also just an intermediate solution until we reach Horde 4.

What I would like to know is the following: are the following files
that are provided by the big horde package:
Horde/Kolab.php
Horde/Kolab/Storage/IMAP/cclient.php
Horde/Kolab/Storage/IMAP/pear.php
Horde/Kolab/Storage/IMAP.php
Horde/Kolab/Storage/IMAP/test.php
Horde/Kolab/Storage/Session.php
used at the moment?  They are not available via http://pear.horde.org
AFAIC determine.  IOW is it okay to drop them from the big horde
package?

-- 
Richard


From kolab-issues at intevation.de  Wed Feb 25 11:34:48 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 25 Feb 2009 10:34:48 +0000
Subject: [Kolab-devel] [issue3436] Crash extractAuditLog at
	urlhandlermanager.cpp:560
Message-ID: <1235558087.87.0.568339506772.issue3436@intevation.de>


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

enterprise35 kdepim 20090217.927605

A user reported, that looking at details of a signed mail sometimes crashs kontact. 
To reproduce:
1. Import the test mail mail-20090225.
2. Look at the details of the mail's signature.
3. Wait a moment.

----------
assignedto: allen
files: mail-20090225
messages: 18755
nosy: allen, bernhard, bh, ludwig
priority: urgent
status: unread
title: Crash extractAuditLog at urlhandlermanager.cpp:560
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3436>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mail-20090225
Type: application/octet-stream
Size: 5545 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090225/e3f09bf3/mail-20090225.exe

From wrobel at pardus.de  Wed Feb 25 12:13:16 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 25 Feb 2009 12:13:16 +0100
Subject: [Kolab-devel] php failure
	undefined	method	Horde_Kolab_Server_ldap::uidForIdOrMail
	(openSUSE native)
In-Reply-To: <20090225090214.GA26295@xs4all.nl>
References: <200902152132.47148.ml@radoeka.nl>
	<200902182309.08121.ml@radoeka.nl> <200902211614.41008.ml@radoeka.nl>
	<200902212050.04343.ml@radoeka.nl>
	<20090225090609.21231u3mzq9a7g9w@webmail.pardus.de>
	<20090225090214.GA26295@xs4all.nl>
Message-ID: <20090225121316.18070vbdg0u0i66o@webmail.pardus.de>

Quoting Richard Bos <ml at radoeka.nl>:

> Hi Gunnar!
>
> On Wed, Feb 25, 2009 at 09:06:09AM +0100, Gunnar Wrobel wrote:
>> Quoting Richard Bos <ml at radoeka.nl>:
>>
>> >Hi,
>> >
>> >Op zaterdag 21 februari 2009 16:14:39 schreef Richard Bos:
>> >>The include path contains the following paths:
>> >>.:/usr/share/php5:/usr/share/php5/PEAR
>> >>So, why does the file Incoming.php uses Horde/Kolab/Server.php from
>> >>/srv/www/htdocs/horde/lib instead of the one located at
>> >>/usr/share/php5/PEAR???
>> >
>> >I've now also discovered why the file Horde/Kolab/Server.php is included
>> >from
>> >/srv/www/htdocs/horde/libs/Horde/Kolab/Server.php  That's because the
>> >latter
>> >is linked to /usr/share/php5/Horde.
>>
>> This sounds bad. I hope you did not leave it that way :)
>
> Hmmm, it should have been:
> /srv/www/htdocs/horde/libs is linked to /usr/share/php5/Horde
> which is not so bad ;)

In my eyes this is very, very bad ;)

You don't link stuff from an installed web application into the system  
libraries. This is not okay.

In general it is a problem when web applications provide their own  
libraries in the web app install location rather than using the  
libraries provided by the system. I'm also unhappy that Horde does  
this but as mentioned before this will only change with Horde 4.

>
>> I know that https://www.intevation.de/roundup/kolab/issue3293 (Big
>> code duplication and code version messup: Horde libs in 2.2.1) does
>> not make things easy at the moment.
>>
>> I consider the core of the problem to be the current release scheme we
>> have upstream within Horde 3. That problem will only be solved with
>> Horde 4.
>>
>> In any case you should have the PEAR packages installating in
>> /usr/share/php/. And the kolab-webclient should install the whole
>> thing again in /srv/www/htdocs/horde again.
>>
>> Kolab OpenPKG will soon change that slightly to remove packages that
>> are congruent between /kolab/var/kolab/www/client/lib/Horde and
>> /kolab/lib/php/Horde (respectively /kolab/var/kolab/www/client/pear
>> and /kolab/lib/php).
>>
>> But that is also just an intermediate solution until we reach Horde 4.
>
> What I would like to know is the following: are the following files
> that are provided by the big horde package:
> Horde/Kolab.php
> Horde/Kolab/Storage/IMAP/cclient.php
> Horde/Kolab/Storage/IMAP/pear.php
> Horde/Kolab/Storage/IMAP.php
> Horde/Kolab/Storage/IMAP/test.php
> Horde/Kolab/Storage/Session.php
> used at the moment?  They are not available via http://pear.horde.org
> AFAIC determine.  IOW is it okay to drop them from the big horde
> package?

The IMAP library was moved from Kolab_Storage to Kolab_Server. So the  
paths need to be Horde/Kolab/Server/IMAP/... This is provided within  
the Kolab_Server package from pear.horde.org.

Looks like you are using the unpatched horde-webmail-1.2.0 release.  
This is plain Horde though and not the Kolab web client. It will not  
be compatible with the Kolab server.

Cheers,

Gunnar

>
> --
> Richard
>
> _______________________________________________
> 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/20090225/069782c3/attachment.bin

From kolab-issues at intevation.de  Wed Feb 25 16:15:12 2009
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Wed, 25 Feb 2009 15:15:12 +0000
Subject: [Kolab-devel] [issue3437] fbview has unneeded "Save and Finish"
	button
Message-ID: <1235574911.97.0.158571097134.issue3437@intevation.de>


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

In server 2.2.0 and in CVS before 2.2.1-rc1:

The /fbview interface has buttons "Save Attendees" and "Save and Finish".
The first one works as expected, the second is unneeded and clicking on it just
shows an empty browser window.

Workaround: just don't click on it.

----------
assignedto: wrobel
messages: 18760
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: minor bug
status: unread
title: fbview has unneeded "Save and Finish" button
topic: fbview, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3437>
___________________________________________________


From kolab-issues at intevation.de  Wed Feb 25 16:22:23 2009
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Wed, 25 Feb 2009 15:22:23 +0000
Subject: [Kolab-devel] [issue3438] kolabFreeBusyPast is not used
Message-ID: <1235575343.8.0.199330527439.issue3438@intevation.de>


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

kolab/issue2461 (kolabFreeBusyPast no longer used) seems to have reappeared,
tested with CVS before 2.2.1-rc1 (20090224)

----------
assignedto: wrobel
messages: 18761
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: urgent
status: unread
title: kolabFreeBusyPast is not used
topic: freebusy, release, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3438>
___________________________________________________


From kolab-issues at intevation.de  Wed Feb 25 18:40:44 2009
From: kolab-issues at intevation.de (Sascha Wilde)
Date: Wed, 25 Feb 2009 17:40:44 +0000
Subject: [Kolab-devel] [issue3439] FreeBusy display in web client and fbview
	depends on kolabHomeServer in LDAP
Message-ID: <1235583644.02.0.0647583862901.issue3439@intevation.de>


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

The Horde turba component (used by stand alone fbview as well as by
the web client) depends on the kolabHomeServer attribute in the LDAP
for the user who's FB information is to be retrieved.

If kolabHomeServer is missing from the ldap a invalid FB URL of the
form https:///freebusy/USER.xfb is created and the query fails.

Horde should use the default Kolab Server as a Fallback if
kolabHomeServer is nonexistent or empty.

Details:

The FB information is retrieved from the freebusyUrl of the user in
question, which in turn is generated on the fly using the
kolabHomeServer LDAP attribute as defined in
/kolab/var/kolab/www/client/turba/config/sources.php:

  'freebusyUrl' => array('fields' => array('kolabHomeServer', 'email'),
                         'format' => 'https://%s/freebusy/%s.xfb'),

----------
assignedto: wrobel
messages: 18768
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: urgent
status: unread
title: FreeBusy display in web client and fbview depends on kolabHomeServer in LDAP
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3439>
___________________________________________________


From kolab-issues at intevation.de  Thu Feb 26 11:31:00 2009
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Thu, 26 Feb 2009 10:31:00 +0000
Subject: [Kolab-devel] [issue3440] unhelpful __FILE__ and __LINE__ in PHP
	log functions
Message-ID: <1235644260.5.0.912753556722.issue3440@intevation.de>


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

Kolab Server before 2.2.1-rc1 (20090224):

A log file contained: PHP Error ... [on line 146 of
"/kolab/lib/php/Horde/Kolab/Filter/Response.php"]

line 146 of Response.php is the function _log() which contains:
        $file = __FILE__;
        $line = __LINE__;

While __FILE__ could still be in the correct file, the __LINE__ will definitely
be wrong.

There are more places with the same problem while some other calls to log
functions have __FILE__ and __LINE__ in the correct place, i.e. in the call, not
the called function.

----------
assignedto: wrobel
messages: 18777
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: bug
status: unread
title: unhelpful __FILE__ and __LINE__ in PHP log functions
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3440>
___________________________________________________


From martin.konold at erfrakon.de  Thu Feb 26 12:50:46 2009
From: martin.konold at erfrakon.de (Martin Konold)
Date: Thu, 26 Feb 2009 12:50:46 +0100
Subject: [Kolab-devel] Adding features to kolab2.schema
Message-ID: <200902261250.47814.martin.konold@erfrakon.de>


Hi,

I am proposing the attached patch to kolab2.schema and adding some external 
definitions (external.kolab.schema) to the Kolab delivery.

The ideas are following:
- add the following attributes to kolabInetOrgPerson
-- dateOfBirth
-- placeOfBirth
-- birthName
-- gender
-- countryOfCitizenship
-- countryOfResidence
-- legalForm
-- tradeRegisterLocation
-- tradeRegisterIdentifier
-- VATNumber
-- germanTaxId

- and add the following new objectclasses
-- kolabExternalPop3Account 
--- this is useful to integrate agregation of externel pop3 accounts e.g. via 
fetchmail
-- kolabGermanBankArrangement
--- often used for billing etc.

All newly added features and modifications are 100% backwards compatible and 
currently erfrakon.de runs on this enhanced LDAP directory schema.

In general I would like to hear your opinion about the proposed change.

Especially I would like to know if you think that the added complexity of 
seperating legal person (like a company or a foundation) from a natural person 
(individual) is worthwile? 

(I have my doubts because mail for a company is not so much different from 
mail for an individual)


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 --------------
# /kolab/etc/openldap/schema/external.kolab.schema
# LDAP schema extension for Kolab
#
# Prefix for OIDs: depending on source
# Prefix for names: depending on source
# Postfix for object classes: Object
#

# extended from apple.schema
attributetype ( 1.3.6.1.4.1.63.1000.1.1.1.1.27
  NAME ( 'apple-birthday' 'dateOfBirth' 'dateOfIncorporation' )
  DESC 'Birthday or date of incorporation'
  EQUALITY generalizedTimeMatch
  SUBSTR caseExactIA5SubstringsMatch
  SINGLE-VALUE
  SYNTAX 1.3.6.1.4.1.1466.115.121.1.24 )

# from http://www.stroeder.com/stroeder.com.schema
attributetype ( 1.3.6.1.4.1.5427.1.389.4.12 
  NAME ( 'birthPlace' 'placeOfBirth' )
  DESC 'Place of birth'
  SUP l
  SINGLE-VALUE )

# from http://www.stroeder.com/stroeder.com.schema
attributetype ( 1.3.6.1.4.1.5427.1.389.4.14
  NAME 'birthName'
  DESC 'Last name at time of birth, e.g. maiden name'
  SUP sn
  SINGLE-VALUE )

# from http://www.stroeder.com/stroeder.com.schema
# The following data items and codes are used (see ISO 5218):
# 	Not known	0
# 	Male		1
# 	Female		2
# 	Not specified	9
#
attributetype ( 1.3.6.1.4.1.5427.1.389.4.7
  NAME 'gender'
  DESC 'Representation of human sex (see ISO 5218)'
  EQUALITY integerMatch
  SINGLE-VALUE
  SYNTAX 1.3.6.1.4.1.1466.115.121.1.27{1} )

# from http://www.stroeder.com/stroeder.com.schema
# tax ID of person or company within Germany
#
attributetype ( 1.3.6.1.4.1.5427.1.389.4.666
  NAME 'germanTaxId'
  DESC 'tax ID of person or company within Germany'
  EQUALITY caseIgnoreMatch
  SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{20} )

# rfc 3039
# ISO 3166 Country Code
# multiple citizenships are possible!
attributetype ( 1.3.6.1.5.5.7.9.4
  NAME 'countryOfCitizenship'
  DESC 'Country of citizenship'
  SYNTAX 1.3.6.1.4.1.1466.115.121.1.11 )
  
# ISO 3166 Country Code 
attributetype ( 1.3.6.1.5.5.7.9.5
  NAME 'countryOfResidence'
  DESC 'Country of residence'
  SYNTAX 1.3.6.1.4.1.1466.115.121.1.11 )

attributetype ( 1.3.6.1.4.1.5427.1.389.4.661
  NAME 'germanBankAccountNumber'
  DESC 'The 8-digits number of a german bank account without spaces'
  SINGLE-VALUE
  SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{10} )

attributetype ( 1.3.6.1.4.1.5427.1.389.4.662
  NAME 'germanBankCode'
  DESC 'The 8-digits number of a german bank code (BLZ) without spaces'
  SINGLE-VALUE
  SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{8} )

attributetype ( 1.3.6.1.4.1.5427.1.389.4.663
  NAME 'germanBankName'
  DESC 'The name of a german bank registered in the BLZ table published by Deutsche Bundesbank.'
  SUP name
  SINGLE-VALUE )

attributetype ( 1.3.6.1.4.1.5427.1.389.4.664
  NAME 'germanBankAccountInfo'
  DESC 'Composed field containing a one-line human-readable representation of all necessary information.'
  SINGLE-VALUE
  SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )

attributetype ( 1.3.6.1.4.1.5427.1.389.4.665
  NAME 'germanBankAccountHolder'
  DESC 'The name of the holder of a german bank account commonly used as recipient name.'
  SINGLE-VALUE
  SUP name )

# http://www.daasi.de/
attributetype ( 1.3.6.1.4.1.5062.1.1.3.16
  NAME 'legalForm'
  DESC 'legal form of a company'
  EQUALITY caseIgnoreMatch
  SUBSTR caseIgnoreSubstringsMatch
  SINGLE-VALUE
  SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )

# http://www.daasi.de/
# location of the trade register authority
attributetype ( 1.3.6.1.4.1.5062.1.1.3.17
  NAME 'tradeRegisterLocation'
  DESC 'Location of the trade registrar where the organization is registered'
  SUP l
  SINGLE-VALUE )
						               
# http://www.daasi.de/
# registration number a the trade register authority
attributetype ( 1.3.6.1.4.1.5062.1.1.3.18
  NAME 'tradeRegisterIdentifier'
  DESC 'Idientifier with which an organization is registered'
  EQUALITY caseIgnoreMatch
  SUBSTR caseIgnoreSubstringsMatch
  SINGLE-VALUE
  SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )

# https://forxa.mancomun.org/plugins/scmsvn/viewcvs.php/trunk/ldap/dxpisi.schema?annotate=29&root=mancomun
# VATNumber
# Identifier number for companies and persons. In Spain it is the same as NIF/CIF.
# In Germany it is called Umsatzsteueridentifikationsnummer.
attributetype ( 1.3.6.1.4.1.27994.1.3.4
  NAME 'VATNumber'
  DESC 'Identifier number for companies and persons'
  EQUALITY caseIgnoreMatch
  SUBSTR caseIgnoreSubstringsMatch
  SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{10} )

objectclass ( 1.3.6.1.4.1.5427.11.3.6.1.4.1.5427.1.389.6.660
  NAME 'germanBankArrangement'
  DESC 'German bank account information'
  SUP top STRUCTURAL
  MUST ( germanBankAccountNumber $ germanBankCode )
  MAY ( germanBankAccountHolder $ germanBankName $ germanBankAccountInfo ) )

# end of external Kolab schema
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kolab2.schema.patch
Type: text/x-patch
Size: 11544 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090226/e3028f73/kolab2.schema.bin

From bernhard at intevation.de  Thu Feb 26 12:58:19 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 26 Feb 2009 12:58:19 +0100
Subject: [Kolab-devel] New Kontact e35 version in apt "testing"!
Message-ID: <200902261258.29754.bernhard@intevation.de>

Hello,

a version of the KDE Kolab Client Enterprise35 for Debian GNU/Linux Etch
got moved to  https://apt.intevation.de/dists/etch/testing/ .
You will find there the typical components of a Debian package with sources.
For those unfamiliar with Debian, this is a tarball with additional files
and course some binaries build out of it which are only provided for ia32
from us.

All this can be a good starting point for rebuilding binaries for Lenny, other 
platforms like ppc or to package for a different distribution like Ubuntu 
oder UCS.

Versions on "testing" come from "unstable".They have survived the internal 
quality control and about one week of real usage. We believe they are ready 
for production quality. As always with software, some issues are known.

We encourage feedback about each current version from "testing"
so it can be moved to "stable". Of course feedback from "unstable" is also 
very valueable and you get the improvements and corrections faster.

Background:
The Kolab-Konsortium people developing and maintaining 
this enterprise 35 (e35)  version use a build service mill
to try to catch errors early: http://saegewerk.intevation.de/
About once a week we identify a drop candiate, which gets picked from the mill
and put up to "experimental". Now we do some internal quality control 
which consists of a small basic test and a more intensive check of the part
that have changed since the last test. If all is fine and this candiate is 
better compared to the last, we will move it to "unstable".

Our small basic test usually is a subset of  
http://wiki.kolab.org/index.php/Kontact_Test_Plan

To find out what has changed between versions that you consider to install,
consult the NewsLog between the drop candidate dates in question:
http://websvn.kde.org/branches/kdepim/enterprise/kdepim/NewsLog.txt?view=log

E35 is strictly for platforms where KDE 3.5 runs, e.g. GNU/Linux, BSD and 
other Unix platforms. The next generation KDE runs on more platforms and its 
Kolab Client is Enterprise4. In case you wonder: Yes, this is KDE Kontact 
using its principal components like KMail, KOrganiser, KAddressbook and more,
enterprise just means that we use a special branch to develop this more 
conservatively.

Best Regards,
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: 198 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090226/6d1d7584/attachment.bin

From kolab-issues at intevation.de  Thu Feb 26 13:02:09 2009
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Thu, 26 Feb 2009 12:02:09 +0000
Subject: [Kolab-devel] [issue3441] Resources with policy "always accept" do
	not work if domain != kolabhost
Message-ID: <1235649729.05.0.0129747481992.issue3441@intevation.de>


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

Kolab Server before 2.2.1-rc1 (CVS 20090224):

Host kolab.example.com hosts resource at example.com which has invitation policy
"always accept".
When trying to invite this resource, the filter.log contains:

Feb 26 12:45:33 Kolab Filter [debug] [horde] Arguments: Horde_Argv_Values Object
(
    [sender] => user at example.com
    [recipient] => Array
        (
            [0] => resource at example.com
        )

    [host] => kolab.example.com
    [client] => 127.0.0.1
    [user] => 
    [config] => /kolab/etc/kolab/kolabfilter.conf
)
 [on line 244 of "/kolab/lib/php/Horde/Kolab/Filter/Base.php"]
Feb 26 12:45:33 Kolab Filter [debug] [horde] Found iCal data in message [on line
78 of "/kolab/lib/php/Horde/Kolab/Filter/Incoming.php"]
Feb 26 12:45:33 Kolab Filter [debug] [horde] Calling
resmgr_filter(kolab.example.com, user at example.com, resource at example.com,
/tmp/IN.Horde_Kolab_Filter_Incoming.2MyAjG) [on line 137 of
"/kolab/lib/php/Horde/Kolab/Filter/Incoming.php"]
Feb 26 12:45:33 Kolab Filter [debug] [horde] Action for user at example.com is
ACT_ALWAYS_ACCEPT [on line 351 of "/kolab/lib/php/Horde/Kolab/Resource.php"]
Feb 26 12:45:33 Kolab Filter [debug] [horde] Processing REQUEST method for
resource at example.com [on line 383 of "/kolab/lib/php/Horde/Kolab/Resource.php"]
Feb 26 12:45:33 Kolab Filter [debug] [horde] Event has UID
libkcal-1152711677.515 [on line 388 of "/kolab/lib/php/Horde/Kolab/Resource.php"]
Feb 26 12:45:33 Kolab Filter [debug] [horde] Request made by user at example.com
[on line 393 of "/kolab/lib/php/Horde/Kolab/Resource.php"]
Feb 26 12:45:33 Kolab Filter [debug] [horde] Converting to epoch 1236254400 [on
line 1071 of "/kolab/lib/php/Horde/Kolab/Resource.php"]
Feb 26 12:45:33 Kolab Filter [debug] [horde] Converted <1236254400> [on line
1082 of "/kolab/lib/php/Horde/Kolab/Resource.php"]
Feb 26 12:45:33 Kolab Filter [debug] [horde] Converting to epoch 1236261600 [on
line 1071 of "/kolab/lib/php/Horde/Kolab/Resource.php"]
Feb 26 12:45:33 Kolab Filter [debug] [horde] Converted <1236261600> [on line
1082 of "/kolab/lib/php/Horde/Kolab/Resource.php"]
Feb 26 12:45:33 Kolab Filter [debug] [horde] Converting to kolab format
1236254400 [on line 1031 of "/kolab/lib/php/Horde/Kolab/Resource.php"]
Feb 26 12:45:33 Kolab Filter [debug] [horde] To <2009-03-05T12:00:00Z> [on line
1056 of "/kolab/lib/php/Horde/Kolab/Resource.php"]
Feb 26 12:45:33 Kolab Filter [debug] [horde] Converting to kolab format
1236261600 [on line 1031 of "/kolab/lib/php/Horde/Kolab/Resource.php"]
Feb 26 12:45:33 Kolab Filter [debug] [horde] To <2009-03-05T14:00:00Z> [on line
1056 of "/kolab/lib/php/Horde/Kolab/Resource.php"]
Feb 26 12:45:33 Kolab Filter [debug] [horde] Event starts on <1236254400>
2009-03-05T12:00:00Z and ends on <1236261600> 2009-03-05T14:00:00Z. [on line 403
of "/kolab/lib/php/Horde/Kolab/Resource.php"]
Feb 26 12:45:33 Kolab Filter [error] [horde] PHP Error: imap_open(): Couldn't
open stream {example.com:143/notls}; Code: 0 [on line 146 of
"/kolab/lib/php/Horde/Kolab/Filter/Response.php"]
Feb 26 12:45:33 Kolab Filter [error] [horde] IMAP error. Server: example.com.
Error: Connection failed to example.com,143: Connection refused; Code:  [on line
105 of "/kolab/lib/php/Horde/Kolab/IMAP/cclient.php"]
Feb 26 12:45:33 Kolab Filter [error] [horde] PHP Error: Unknown: Connection
failed to example.com,143: Connection refused (errflg=2); Code: 0 [on line 146
of "/kolab/lib/php/Horde/Kolab/Filter/Response.php"]



/lib/php/Horde/Kolab/Resource.php:
 handleMessage() calls _imapConnect() which calls
        $list = &Kolab_List::singleton();
        $default = $list->getForeignDefault($id, 'event');
which in turn calls
/kolab/lib/php/Horde/Kolab/Storage/List.php:
    function &listFolders()
    {
        if (!isset($this->_list)) {
            $session = &Horde_Kolab_Session::singleton();
            $imap = &$session->getImap();
            if (is_a($imap, 'PEAR_Error')) {
                return $imap;
            }

/kolab/lib/php/Horde/Kolab/Session.php function &singleton()
is called (the second time, it connected as calendar user earlier which worked)
and tries to login to example.com:143 instead of kolab.example.com:143 or
localhost:143,
which is wrong in many setups.

----------
assignedto: wrobel
messages: 18780
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: urgent
status: unread
title: Resources with policy "always accept" do not work if domain != kolabhost
topic: filter, release, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3441>
___________________________________________________


From gohmann at univention.de  Thu Feb 26 13:22:27 2009
From: gohmann at univention.de (Stefan Gohmann)
Date: Thu, 26 Feb 2009 13:22:27 +0100
Subject: [Kolab-devel] New Kontact e35 version in apt "testing"!
In-Reply-To: <200902261258.29754.bernhard@intevation.de>
References: <200902261258.29754.bernhard@intevation.de>
Message-ID: <200902261322.27844.gohmann@univention.de>

Hi Bernhard,

Am Donnerstag, 26. Februar 2009 schrieb Bernhard Reiter:
> All this can be a good starting point for rebuilding binaries for Lenny,
> other platforms like ppc or to package for a different distribution like
> Ubuntu oder UCS.

this is excellent. We will use this package for the next stable release of 
UCS. Some of us are using the new version and it works.

Cheers
Stefan

-- 
Stefan Gohmann
Head of Software Engineering 

Univention GmbH
Linux for your business
Mary-Somerville-Str.1
28359 Bremen
Tel. : +49 421 22232-45
Fax : +49 421 22232-99

gohmann at univention.de
http://www.univention.de

Gesch?ftsf?hrer: Peter H. Ganten
HRB 20755 Amtsgericht Bremen
Steuer-Nr.: 71-597-02876 


From itsef-admin at brightsight.com  Thu Feb 26 15:16:06 2009
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Thu, 26 Feb 2009 15:16:06 +0100
Subject: [Kolab-devel] New Kontact e35 version in apt "testing"!
In-Reply-To: <200902261258.29754.bernhard@intevation.de>
References: <200902261258.29754.bernhard@intevation.de>
Message-ID: <200902261516.06278.itsef-admin@brightsight.com>

On Thursday 26 February 2009 12:58:19 Bernhard Reiter wrote:
> a version of the KDE Kolab Client Enterprise35 for Debian GNU/Linux Etch
> got moved to  https://apt.intevation.de/dists/etch/testing/ .
[...]
> All this can be a good starting point for rebuilding binaries for Lenny,
> other platforms like ppc or to package for a different distribution like
> Ubuntu oder UCS.

I've been building (K)ubuntu 8.04 packages from the "unstable" packages for 
quite some time now for our users. They probably still have some "quick 
hacks" in them, but if anyone is interested in info please let me know. I've 
tried to find a compromise between the Debian-kk version and the original 
Kubuntu version - mainly, all installation locations/desktop categories are 
those from Kubuntu.


> Versions on "testing" come from "unstable".They have survived the internal
> quality control and about one week of real usage. We believe they are ready
> for production quality. As always with software, some issues are known.

The difference between "unstable" and "testing" is still not quite clear to 
me - "testing" seems to have seen even more testing, but what exactly?

Other than that thanks a lot for the info, much appreciated!

Cheerio,

Thomas


From kolab-issues at intevation.de  Thu Feb 26 15:28:45 2009
From: kolab-issues at intevation.de (Marc Mutz)
Date: Thu, 26 Feb 2009 14:28:45 +0000
Subject: [Kolab-devel] [issue3442] sieve: fails to mark some message as \Seen
Message-ID: <1235658525.37.0.346352710515.issue3442@intevation.de>


New submission from Marc Mutz <marc at kdab.net>:

I'm using the following Sieve filter snippet to file away SPAM into a separate 
folder, and automatically mark them as read (\Seen in IMAP speak):
 if header :contains "x-spam-flag" "yes" {
    setflag "\\Seen";
    fileinto /*:flags "\\Seen"*/ "INBOX/SPAM";
    stop;
 }
I never see the fileinto misbehaving, and I get hundreds of SPAM mails a day, 
but every once in a while the setflag seems to fail. Usually, I have one or two 
SPAM mails a week that are not marked read. However, today, I got five. I've 
also seen non-\Seen mails from this code:
 if anyof( allof( header :regex "x-spam-status" "BAYES_[6-9][0-9]",
		 not header :contains "x-spam-flag" "yes" ),
	  allof( header :regex "x-spam-status" "BAYES_[0-4][0-9]",
		 header :contains "x-spam-flag" "yes" ) )
 {
    if header :is "Subject" "Auto-discard notification" {
        setflag "\\Seen";
    }
    fileinto "INBOX/Not Kosher";
    stop;
 }

It's pretty new, so I can't say for sure, but I think the ratio of correctly 
marked vs. non-correctly marked mails is 2:1 here (very low sample, though).

Again, the fileinto never failed me. Ever. It's the setflag that's a bit shaky.

----------
messages: 18785
nosy: marc
status: unread
title: sieve: fails to mark some message as \Seen
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3442>
___________________________________________________


From bernhard at intevation.de  Fri Feb 27 08:49:35 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 27 Feb 2009 08:49:35 +0100
Subject: [Kolab-devel] New Kontact e35 version in apt "testing"!
In-Reply-To: <200902261322.27844.gohmann@univention.de>
References: <200902261258.29754.bernhard@intevation.de>
	<200902261322.27844.gohmann@univention.de>
Message-ID: <200902270849.36368.bernhard@intevation.de>

Stefan,

Am Donnerstag, 26. Februar 2009 13:22:27 schrieb Stefan Gohmann:
> Am Donnerstag, 26. Februar 2009 schrieb Bernhard Reiter:
> > All this can be a good starting point for rebuilding binaries for Lenny,
> > other platforms like ppc or to package for a different distribution like
> > Ubuntu oder UCS.
>
> this is excellent. We will use this package for the next stable release of
> UCS. Some of us are using the new version and it works.

very good. Note that there might be more versions forthcoming because e35 is 
in maintenance mode and in general we recommend to ship all updates as minor 
updates.

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: 198 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090227/9a7b54d9/attachment.bin

From bernhard at intevation.de  Fri Feb 27 08:54:55 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 27 Feb 2009 08:54:55 +0100
Subject: [Kolab-devel] New Kontact e35 version in apt "testing"!
In-Reply-To: <200902261516.06278.itsef-admin@brightsight.com>
References: <200902261258.29754.bernhard@intevation.de>
	<200902261516.06278.itsef-admin@brightsight.com>
Message-ID: <200902270854.55594.bernhard@intevation.de>

Thomas,

Am Donnerstag, 26. Februar 2009 15:16:06 schrieb ITSEF Admin:
> On Thursday 26 February 2009 12:58:19 Bernhard Reiter wrote:
> > a version of the KDE Kolab Client Enterprise35 for Debian GNU/Linux Etch
> > got moved to ?https://apt.intevation.de/dists/etch/testing/ .
>
> [...]
>
> > All this can be a good starting point for rebuilding binaries for Lenny,
> > other platforms like ppc or to package for a different distribution like
> > Ubuntu oder UCS.
>
> I've been building (K)ubuntu 8.04 packages from the "unstable" packages for
> quite some time now for our users. They probably still have some "quick
> hacks" in them, but if anyone is interested in info please let me know.
> I've tried to find a compromise between the Debian-kk version and the
> original Kubuntu version - mainly, all installation locations/desktop
> categories are those from Kubuntu.

in the mid term we hope to set up a mill for building ubuntu packages
as well, all we need is a maintainer for the packaging of this version. 
Thomas, you are a likely candidate to help us here, aren't you? >;)

As a packager you would want to start once "unstable" has a new version
ideally right now.

> > Versions on "testing" come from "unstable".They have survived the
> > internal quality control and about one week of real usage. We believe
> > they are ready for production quality. As always with software, some
> > issues are known.
>
> The difference between "unstable" and "testing" is still not quite clear to
> me - "testing" seems to have seen even more testing, but what exactly?

A number of people directly install from the "unstable" respository. So it is 
about one week of real usage for at least 10 users.

experimental -> unstable:  basic test, change test and better than before
unstable -> testing: real usage for at least a week
 
I am still considering when to move to stable. Maybe after another week given 
at least about three independent feedbacks that nothing has krept up.

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: 198 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090227/95c4b48a/attachment.bin

From bernhard at intevation.de  Fri Feb 27 09:02:37 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 27 Feb 2009 09:02:37 +0100
Subject: [Kolab-devel] Adding features to kolab2.schema
In-Reply-To: <200902261250.47814.martin.konold@erfrakon.de>
References: <200902261250.47814.martin.konold@erfrakon.de>
Message-ID: <200902270902.38223.bernhard@intevation.de>

Am Donnerstag, 26. Februar 2009 12:50:46 schrieb Martin Konold:
> In general I would like to hear your opinion about the proposed change.

There is a notion when dealing with data privacy and this is that forms should 
be as simple as possible. The problem with many empty slots is that there are 
some sort of people that will try to fill all values in. So an empty slot  
for dateOfBirth, placeOfBirth and birthName will create entries in there in 
some case. Companies might get in trouble filling this data in germany.
Some organisations need this like the citizen registration of the muncipality.
So I guess I am looking for the use case for some of the values.
This is at least an argument against some of the values.

Also they would clutter of the screen in web-admin.

> Especially I would like to know if you think that the added complexity of
> seperating legal person (like a company or a foundation) from a natural
> person (individual) is worthwile?
>
> (I have my doubts because mail for a company is not so much different from
> mail for an individual)

 Ideally someone would want define relationships between objects, like
users A,B,D are a member of company X and can be reached at subsidery M.
I guess that many directory services are not up to this yet, they seem to be 
focussed on digital identities. Given that many companies do have a major 
email and street address, keeping one entry for both seems fine to me.

For billing purposes I would propose a folder with "contact" objects in Kolab.
Still those do not represent the relationships I have mentioned above.

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: 198 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090227/5545f243/attachment.bin

From bernhard at intevation.de  Fri Feb 27 10:12:12 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 27 Feb 2009 10:12:12 +0100
Subject: [Kolab-devel] New Kontact e35 version in apt "testing"!
In-Reply-To: <200902270908.22797.bernhard@intevation.de>
References: <200902261258.29754.bernhard@intevation.de>
	<49A745BC.3070306@advocap.org>
	<200902270908.22797.bernhard@intevation.de>
Message-ID: <200902271012.16171.bernhard@intevation.de>

Am Freitag, 27. Februar 2009 09:08:22 schrieb Bernhard Reiter:
> > In http://wiki.kolab.org/index.php/KDE_Kolab_Client ?proko2 is
> > recommended. I suspect that is a bit dated??
>
> Correct, it is a wiki, please help us to improve it. :)
> (I'll update http://kolab.org/about-kolab-clients.html#kdeclient2 next.)

Done, I've updated about-kolab-clients, the roadmap and download pages now.
Help with updating the wiki is highly appreciated.


-- 
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: 198 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090227/c92b7191/attachment.bin

From kolab-issues at intevation.de  Fri Feb 27 10:32:49 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Fri, 27 Feb 2009 09:32:49 +0000
Subject: [Kolab-devel] [issue3443] Print of a HTML mail with different font
	size fails
Message-ID: <1235727169.68.0.821585124024.issue3443@intevation.de>


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

enterprise35 kdepim 20090217.927605

Test:
1. Start to create a new mail.
2. Set Options-> HTML Format
3. Add a test line with different fontsize and color.
4. Press on print and print this into a file.

=> Just the header is printed. The test line disappears.
I expect kontact to print the whole HTML mail.

----------
assignedto: allen
messages: 18799
nosy: allen, bernhard, bh, ludwig
priority: bug
status: unread
title: Print of a HTML mail with different font size fails
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3443>
___________________________________________________


From kolab-issues at intevation.de  Fri Feb 27 15:29:01 2009
From: kolab-issues at intevation.de (Sascha Wilde)
Date: Fri, 27 Feb 2009 14:29:01 +0000
Subject: [Kolab-devel] [issue3444] No error message when login fails because
	of wrong credentials
Message-ID: <1235744941.25.0.857877891733.issue3444@intevation.de>


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

When logging in with wrong credentials (as non existent user or wrong
password) it takes a loooooong time[0] and then the login mask is
reloaded -- no error message.

The second part is the Problem, the user should be informed that the
login was invalid.

This problem is new and presumably related to the switch to imp
login.

[0] Which is ok, IMO as it protects against brute force attacks.

----------
assignedto: wrobel
messages: 18808
nosy: bernhard, martin, thomas, till, wilde, wrobel
priority: bug
status: unread
title: No error message when login fails because of wrong credentials
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3444>
___________________________________________________


From thomas at intevation.de  Fri Feb 27 15:36:34 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 27 Feb 2009 15:36:34 +0100
Subject: [Kolab-devel] no Kolab Server 2.2.1-rc1 today
Message-ID: <20090227143634.GA21633.thomas@intevation.de>

Hi!

We hoped to have 2.2.1-rc1 ready this month and we already had very
promising internal candidates for rc1, but in the final tests some
regressions and even a new security problem showed up.

Therefore we decided to postpone rc1 to fix the most important
issues and hope we can release it during the next week.

Regards,
Thomas Arendsen Hein

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


From kolab-issues at intevation.de  Fri Feb 27 15:42:04 2009
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Fri, 27 Feb 2009 14:42:04 +0000
Subject: [Kolab-devel] [issue3445] web client does not work with Konqueror
Message-ID: <1235745724.5.0.379742409899.issue3445@intevation.de>


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

When trying to log in to the web client with Konqueror, the user gets redirected
to the login page. Using the same user account and Firefox it works fine.

Tested with CVS before 2.2.1-rc1 (20090224) and Konqueror 3.5.5 (Debian etch)

With server 2.2.0 it works fine, too!

----------
assignedto: wrobel
messages: 18809
nosy: martin, thomas, wilde, wrobel
priority: urgent
status: unread
title: web client does not work with Konqueror
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3445>
___________________________________________________


From kolab-issues at intevation.de  Fri Feb 27 15:47:51 2009
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Fri, 27 Feb 2009 14:47:51 +0000
Subject: [Kolab-devel] [issue3446] SERVER_NAME undefined in
	freebusy/regenerate.php
Message-ID: <1235746071.27.0.12871285304.issue3446@intevation.de>


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

When using freebusy/regenerate.php from the command line (as described in the
README) and there are users with out a kolabHomeServer entry,
/kolab/var/kolab-freebusy/log/php-error.log contains:

[27-Feb-2009 13:02:04] PHP Notice:  Undefined index:  SERVER_NAME in
/kolab/lib/php/Horde/Kolab/Server/Object/user.php on line 231
[27-Feb-2009 13:02:04] PHP Notice:  Undefined index:  SERVER_NAME in
/kolab/lib/php/Horde/Kolab/Server/Object/user.php on line 211

----------
assignedto: wrobel
messages: 18810
nosy: martin, thomas, wilde, wrobel
priority: bug
status: unread
title: SERVER_NAME undefined in freebusy/regenerate.php
topic: freebusy, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3446>
___________________________________________________


From kolab-issues at intevation.de  Fri Feb 27 15:52:30 2009
From: kolab-issues at intevation.de (Sascha Wilde)
Date: Fri, 27 Feb 2009 14:52:30 +0000
Subject: [Kolab-devel] [issue3447] Heavy information leak from webclient
	directories
Message-ID: <1235746349.92.0.0397939885507.issue3447@intevation.de>


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

One can freely retrieve every non-PHP file in the web client directory
and all its sub directories via http.  This is at leas true for the
official openpkg based distribution, where this affects all files
below /kolab/var/kolab/www/client.

This includes, but is not limited to:

- Logfiles
- User preferences
- User session data

As the user sessions are saved in files with hard to guess names the
log files seem to be the biggest source of confidential information I
have currently found.

POC:
https://example.com/client/log/horde.log

It seams that it has been tied to prevent this problem by placing
.htaccess files with "Deny from All" in all the directories --
unfortunately they are not respected by the apache configuration.
Actually this is conceptional wrong anyway, The Right Thing To Do[tm]
is to deny access for all places except the few that are really meant
to be accessed by users.

----------
assignedto: wrobel
messages: 18811
nosy: martin, thomas, wilde, wrobel
priority: critical
status: unread
title: Heavy information leak from webclient directories
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3447>
___________________________________________________


From ml at radoeka.nl  Fri Feb 27 21:46:57 2009
From: ml at radoeka.nl (Richard Bos)
Date: Fri, 27 Feb 2009 21:46:57 +0100
Subject: [Kolab-devel] Is the README.amavisd.in still correct?
Message-ID: <200902272146.58714.ml@radoeka.nl>

This README for amavis:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/doc/README.amavisd.in?rev=1.2&content-type=text/vnd.viewcvs-markup
is it still correct?  This especially with the remark about the amavisd.MYUSERS.patch
I believe that this one is not necessary anymore is that correct?

-- 
Richard


From ml at radoeka.nl  Sat Feb 28 11:04:07 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sat, 28 Feb 2009 11:04:07 +0100
Subject: [Kolab-devel] php tests
In-Reply-To: <20090225082846.29327c8yzf4hhnok@webmail.pardus.de>
References: <20090224164727.190E3600920@lists.intevation.de>
	<200902242355.38317.ml@radoeka.nl>
	<20090225082846.29327c8yzf4hhnok@webmail.pardus.de>
Message-ID: <200902281104.08037.ml@radoeka.nl>

Hi Gunnar,

Op woensdag 25 februari 2009 08:28:46 schreef Gunnar Wrobel:
> > Which module is really using this module when tests are executed? ?Are
> > e.g. tests in kolab-filter using methods from this Horde_Notification
> > module? I would like to know this to determine which rpm should pull in
> > this package
> > as a dependency. ?Or do all kolab-* packages requires this package?
>
> The modules Kolab_Storage, Kolab_FreeBusy, and Kolab_Filter use these ?
> new modules for their unit tests. I only added these optional ?
> dependencies in Kolab_Filter at the moment (see that package spec).

I have added those dependencies to the respective rpms.

> Currently running the tests on an OpenPKG system yields:

I have attached my results of the tests to this email.  I have attached 
results before and after horde-notification was installed.  Without horde-
notification the results are more like yours.  I have horde-notification from 
the pear.horde.org repository without any patches.

A test fails, because it can find the file:
ls: cannot access 
/srv/www/htdocs/horde/lib/Horde/Kolab/../../../../../config/registry.php: 
No such file or directory
There is a file with such a name present at: 
/srv/www/htdocs/horde/config/registry.php

When I remove ../../ the 'ls <above filename>' works:
/srv/www/htdocs/horde/lib/Horde/Kolab/../../../config/registry.php

To test the failing test I copied the file 
/srv/www/htdocs/horde/config/registry.php to 
/srv/www/htdocs/horde/lib/Horde/Kolab/../../../../../config/registry.php
This results in:
1) testFetch(Horde_Kolab_FreeBusy_FreeBusyTest)
Undefined variable: acl                        
/usr/share/php5/PEAR/Horde/Kolab/FreeBusy/Cache.php:175
/usr/share/php5/PEAR/Horde/Kolab/FreeBusy.php:149      
/usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php:91
/usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/AllTests.php:36    
/usr/share/php5/PEAR/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/AllTests.php:63    

What to do with this warning:
PHP Warning:  Call-time pass-by-reference has been deprecated;
Should I indeed set allow_call_time_pass_reference to true in php.ini as 
suggested by the warning?


> PHPUnit 3.3.3 by Sebastian Bergmann.
>
> ..............
>
> Time: 0 seconds
>
> OK (14 tests, 58 assertions)
> PHPUnit 3.3.3 by Sebastian Bergmann.
>
> .......IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII................... ?60 / 121
> .......................................IIIIIIIIIIIIIIIIIIIII 120 / 121
> I
>
> Time: 0 seconds
>
> OK, but incomplete or skipped tests!
> Tests: 121, Assertions: 177, Incomplete: 56.
> PHPUnit 3.3.3 by Sebastian Bergmann.
>
> ...........................F.....
>
> Time: 1 second
>
> There was 1 failure:
>
> 1) testGetImapFailNoServer(Horde_Kolab_Storage_FolderTest)
> Failed asserting that two strings are equal.
> expected string <localhost>
> difference ? ? ?<xxxxxxxxx???????>
> got string ? ? ?<imap.example.org>
> /kolab/lib/php/test/Kolab_Storage/Horde/Kolab/Storage/FolderTest.php:167
>
> FAILURES!
> Tests: 33, Assertions: 197, Failures: 1.
> PHPUnit 3.3.3 by Sebastian Bergmann.
>
> .....................
>
> Time: 2 seconds
>
> OK (21 tests, 44 assertions)
> PHP Warning: ?require_once(Horde/Kolab/Test.php): failed to open ?
> stream: No such file or directory in ?
> /kolab/lib/php/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php on
> ? line 17
> PHP Fatal error: ?require_once(): Failed opening required ?
> 'Horde/Kolab/Test.php' (include_path='.:/kolab/lib/php') in ?
> /kolab/lib/php/test/Kolab_FreeBusy/Horde/Kolab/FreeBusy/FreeBusyTest.php on
> ? line 17
> make: *** [test] Fehler 255
>
> Basically 1 failure in Kolab_Storage and some bigger problems in ?
> Kolab_FreeBusy.
>
> Kolab_FreeBusy is still on my ToDo-List.

-- 
Richard


-------------- next part --------------
A non-text attachment was scrubbed...
Name: kolab-tests-results.tar.bz2
Type: application/x-bzip-compressed-tar
Size: 2087 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090228/8b8434e8/kolab-tests-results.tar.bin

From ml at radoeka.nl  Sat Feb 28 12:06:07 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sat, 28 Feb 2009 12:06:07 +0100
Subject: [Kolab-devel] thomas: server release-notes.txt,1.387,1.388
In-Reply-To: <20090225082846.29327c8yzf4hhnok@webmail.pardus.de>
References: <20090224164727.190E3600920@lists.intevation.de>
	<200902242355.38317.ml@radoeka.nl>
	<20090225082846.29327c8yzf4hhnok@webmail.pardus.de>
Message-ID: <200902281206.07970.ml@radoeka.nl>

Op woensdag 25 februari 2009 08:28:46 schreef Gunnar Wrobel:
> > I would expect the file
> > /usr/share/doc/packages/kolab-filter/Kolab_Filter/man/man1/kolabfilter.1
> > to end up in ?/usr/share/man/man1 ?Is to possible to enforce this
> > location with the pear install command? ?Is something like this:
> > pear -d man_dir=/usr/share/man
> > possible? ?It does not work for me. ?This is explainable if I read this
> > page: http://pear.php.net/manual/en/guide.users.commandline.config.php
>
> Indeed that does not work. If you look at the Kolab_Filter.spec you ?
> see that I move that file manually into the correct location. PEAR ?
> does not know about man files at the moment. Then again there are not ?
> really that many people writing command line tools in PHP anyhow. ?
> Though I guess this will appear more and more often and I hope they ?
> are going to make the PEAR installer into a more decent package ?
> management tool soon.

Thanks, doing the same now.

> > Is the file Kolab_Filter.mo going to be stored at the right spot, see
> > listing above?
>
> I still have to figure out where to place this one on the Kolab ?
> server. Storing translations in PEAR packages is something also not ?
> really supported. I guess Horde will lead the field in that area as we ?
> will need a solution for that soon as we are currently working on ?
> Horde 4 which will require support for this, too.

Okay, I just include it in the rpm.

-- 
Richard


From thomas at intevation.de  Sat Feb 28 22:52:25 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Sat, 28 Feb 2009 22:52:25 +0100
Subject: [Kolab-devel] Is the README.amavisd.in still correct?
In-Reply-To: <200902272146.58714.ml@radoeka.nl>
References: <200902272146.58714.ml@radoeka.nl>
Message-ID: <20090228215225.GA5190.thomas@intevation.de>

* Richard Bos <ml at radoeka.nl> [20090227 21:47]:
> This README for amavis:
> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/doc/README.amavisd.in?rev=1.2&content-type=text/vnd.viewcvs-markup
> is it still correct?  This especially with the remark about the amavisd.MYUSERS.patch
> I believe that this one is not necessary anymore is that correct?

Yes, the patch is no longer needed. Feel free to update the readme
in any way you consider useful.

I just noticed a few days ago that there is a directory kolabd/doc :)

Thomas

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


From bogus@does.not.exist.com  Thu Feb 19 14:36:22 2009
From: bogus@does.not.exist.com ()
Date: Thu, 19 Feb 2009 13:36:22 -0000
Subject: No subject
Message-ID: <mailman.0.1236406925.2108.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>
___________________________________________________