From issues at kolab.org  Fri Jun  3 09:09:48 2011
From: issues at kolab.org (Izak)
Date: Fri, 03 Jun 2011 07:09:48 +0000
Subject: [Kolab-devel] [issue4741] kolab 2.3.1 - horde webmail do not read
	email with big	attachment
In-Reply-To: <1307084988.57.0.291445204765.issue4741@kolab.org>
Message-ID: <1307084988.57.0.291445204765.issue4741@kolab.org>


Hello,
i have horde from kolab and is problem with read email with big (about 2MB and
bigger) 
Horde don't show email and only waiting.
from imap client (Thunderbird) work

i am find similar issue and i am edit: php.ini in /kolab/etc/php
and php.ini + apache-php.ini (in template too)

[PHP]

;   Resource Limits
register_globals   = off    ; Global variables are no longer registered for
input data
allow_url_fopen    = off    ; Disable the opening of remote URLs
display_errors     = off    ; Errors will NOT be displayed
log_errors         = on     ; Errors will be logged
max_execution_time = 180     ; Maximum execution time of each script, in seconds
max_input_time     = 180     ; Maximum amount of time each script may spend
parsing request data
memory_limit       = 256M   ; Maximum amount of memory a script may consume
post_max_size      = 25M   ; Maximum amount of POST data accepted
upload_max_filesize = 25M

;   Include Paths
include_path          = ".:/kolab/lib/php"


maybe log from php log:
[03-Jun-2011 10:25:00] PHP Warning:  register_shutdown_function() [<a
href='function.register-shutdown-function'>function.register-shutdown-function</a>]:
Invalid shutdown callback 'Array' passed in
/kolab/lib/php/Horde/Kolab/Storage/List.php on line 139

----------
messages: 27867
nosy: izak
priority: critical
status: unread
title: kolab 2.3.1 - horde webmail do not read email with big attachment

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4741>
______________________________________



From issues at kolab.org  Fri Jun  3 11:53:05 2011
From: issues at kolab.org (Alvaro Lopez)
Date: Fri, 03 Jun 2011 09:53:05 +0000
Subject: [Kolab-devel] [issue4742] webadmin: Domain Maintainer error loading
	domain list	when create new user, filter error on user list
In-Reply-To: <1307094785.24.0.0216972035327.issue4742@kolab.org>
Message-ID: <1307094785.24.0.0216972035327.issue4742@kolab.org>


Hi, 
When i try to create an user with a domain maintainer the select field of
domains is empty, and in the user list, the accounts listed are all of the
server the filter of domains don work.

thnx

----------
messages: 27871
nosy: raxar
priority: urgent
status: unread
title: webadmin: Domain Maintainer error loading domain list when create new user, filter error on user list

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4742>
______________________________________



From wickert at kolabsys.com  Fri Jun  3 16:14:54 2011
From: wickert at kolabsys.com (Christoph Wickert)
Date: Fri, 3 Jun 2011 16:14:54 +0200
Subject: [Kolab-devel] Announcing the Kolab Server 2.3.2
Message-ID: <201106031615.00719.wickert@kolabsys.com>

I'm sorry it took so long, but good things take a while.

I am relieved the release is out because now that the problems with FreeBusy 
are solved, the 2.3 series offer the same functionality as 2.2.4  - plus much 
more of course.

NEW FEATUES

The update to postfix 2.8 brings a lot of new features like postscreen and 
multi-instance support. However none of them is enabled by default and old 
configuration files continue to work. Have fun while exploring the new 
possibilities, we will make use of them in the next major release.

BUGFIXES

Most of the bugfixes affect Kolab_* packages such as Kolab_FreeBusy:

- apache-php: Security update fixing various CVEs
- Kolab_FreeBusy: Generating free/busy cache works again
- Kolab_Resource: Answers from resources no longer contain extra "\r\n\r\n"
  characters
- Kolab_Server: IMAP connection issues fixed
- Kolab_Storage: Webclient no longer hangs if freebusy triggering/retrieving
  hangs
- kolab-webadmin: Listing of sub-folders and sub-calendars was fixed
- kolabd: Fixed an imap annotatoin so SyncML can sync contacts
- php: Security update fixing various CVEs
- postfix: Security update to 2.8.3. This also brings a lot of new features
- z-push: New version with many bug fixes, rebuilding with prefixes other than
  /kolab fixed.

For a complete list of changes please refer to
http://files.kolab.org/server/release/kolab-server-2.3.2/sources/release-
notes.txt

UPGRADING

The upgrade form 2.3.1 is straight forward, there is nothing special you need 
to care about.

If you are upgrading from 2.2.4, please follow the instructions to upgrade  
from 2.2.4 to 2.3.0 as outlined in 
http://files.kolab.org/server/release/kolab-server-2.3.1/sources/1st.README

DOWNLOADS

Binary packages for Debian GNU/Linux 6.0 (Squeeze/stable) and 5.0 
(Lenny/oldstable) on x86 platforms can be found next to the sources.

As soon as they have synced, you can also use the the mirrors listed on 
http://kolab.org/mirrors.html

You can check the integrity of the downloaded files by importing our file
distribution key and verify the OpenPGP signature and SHA1 checksums:

$ wget https://ssl.intevation.de/Intevation-Distribution-Key.asc
$ gpg --import Intevation-Distribution-Key.asc
$ gpg --verify SHA1SUMS.sig
$ sha1sum -c SHA1SUMS

KNOWN BUGS
https://bugzilla.kolabsys.com/show_bug.cgi?id=98 - Not all folders in the new 
ActiveSync config are displayed. We are working on that.

Please report bugs in our bug tracker at https://bugzilla.kolabsys.com/

Regards,
Christoph

-- 
Christoph Wickert
Senior Engineer

Kolab Systems AG
Z?rich, Switzerland

e: wickert at kolabsys.com
t: +49 251 871 369 77
w: http://kolabsys.com

pgp: 85DACC63 Christoph Wickert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110603/ec54c2fb/attachment.sig>

From vanmeeuwen at kolabsys.com  Mon Jun  6 12:19:24 2011
From: vanmeeuwen at kolabsys.com (Jeroen van Meeuwen (Kolab Systems))
Date: Mon, 6 Jun 2011 11:19:24 +0100
Subject: [Kolab-devel] Closing Call on KEP #3
Message-ID: <201106061119.24865.vanmeeuwen@kolabsys.com>

Hello,

I would like to announce the closing call stage for KEP #3, on the 
introduction of a subevent tag for exceptions in recurrences;

  http://wiki.kolab.org/index.php?title=User:Greve/Drafts:KEP:3&oldid=11472

This KEP was proposed November 16th, 2010, and has heard little objection.

With the closing call, we now enter a two week period for final objections. 
This means that unless serious objections are raised, KEP #3 defaults to being 
accepted on Monday, June 20th, 2011.

Thank you for your continued support!

Kind regards,

Jeroen van Meeuwen

-- 
Senior Engineer, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110606/ebf3c921/attachment.sig>

From issues at kolab.org  Wed Jun  8 14:36:50 2011
From: issues at kolab.org (noreply)
Date: Wed, 08 Jun 2011 12:36:50 +0000
Subject: [Kolab-devel] [issue4744] Google Groups: You've been invited to
	shivai395
In-Reply-To: <20110608123647.B5051953671@kolab.intevation.de>
Message-ID: <20110608123647.B5051953671@kolab.intevation.de>


sina_fathi525105 at yahoo.com has invited you to join the shivai395 group with 
this message:

can we this step conclusion database the play He new planning important. those
to establish initial .

Here is the group's description:

lars. Het Amerikaanse dollar (USD) LIBOR rente tarief is beschikbaar in

---------------------- Google Groups Information ----------------------

You can accept this invitation by clicking the following URL:

http://groups.google.com/group/shivai395/sub?s=fRyQahQAAABfv7fFP1KzVon9i3aklHfeX1zXKUA0W2XcVvWtV_nB1w&hl=en

--------------------- If This Message Is Unwanted ---------------------

If you feel that this message is abuse, please inform the Google Groups staff 
by using the URL below.

http://groups.google.com/groups/abuse?invite=YgAAAMs1L-cGAAAAS_2WV1QAAAAAADdBWJ8_4DGso42Nvck5NR8QUZY&hl=en

----------
messages: 27891
nosy: noreply
status: unread
title: Google Groups: You've been invited to shivai395

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4744>
______________________________________



From issues at kolab.org  Wed Jun  8 20:01:12 2011
From: issues at kolab.org (Christoph Wickert)
Date: Wed, 08 Jun 2011 18:01:12 +0000
Subject: [Kolab-devel] [issue4745] Horde preferences woes in Kolab 2.3.x
In-Reply-To: <1307556072.96.0.203976840222.issue4745@kolab.org>
Message-ID: <1307556072.96.0.203976840222.issue4745@kolab.org>


Strange things are happening to the new preferences in
/kolab/var/kolab/webclient_data/storage:

test91-3:/kolab/var/kolab/webclient_data/storage# ls -l 
total 64
-rw------- 1 kolab-n kolab-n   728 2011-06-01 17:27 as at doe.org.prefs
-rw------- 1 kolab-n kolab-n  1169 2011-05-23 14:50 b at doe.org.prefs
-rw-r--r-- 1 kolab-n kolab-n 26624 2010-12-24 18:13 horde.db
-rw-r--r-- 1 kolab-n kolab-n  8192 2010-12-24 18:15 imp.db
-rw------- 1 kolab-n kolab-n   764 2011-06-03 15:49 jane at doe.org.prefs
-rw------- 1 kolab-n kolab-n   833 2011-05-18 11:55 joe at sixpack.com.prefs
-rw------- 1 kolab-n kolab-n  1234 2011-06-03 15:48 john at doe.org.prefs
-rw------- 1 kolab-n kolab-n   116 2011-05-19 09:48 manager.prefs
-rw------- 1 kolab-n kolab-n   711 2011-05-19 10:02 max at doe.org.prefs

Why is there a prefs file for 'manager'?

I am seeing similar things on kolab.kolabsys.com and Thomas has confirmed it on
Intevation's server. However it is not an upgrade problem, this is a fresh
install. test91-3 is 2.3.1 upgraded to 2.3.2.

----------
assignedto: wrobel
keyword: webclient
messages: 27892
nosy: thomas, wickert, wilde, wrobel
priority: bug
status: unread
title: Horde preferences woes in Kolab 2.3.x

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4745>
______________________________________



From issues at kolab.org  Fri Jun 10 01:58:48 2011
From: issues at kolab.org (matt)
Date: Thu, 09 Jun 2011 23:58:48 +0000
Subject: [Kolab-devel] [issue4746] Email won't load in Horde
In-Reply-To: <1307663928.41.0.896951811113.issue4746@kolab.org>
Message-ID: <1307663928.41.0.896951811113.issue4746@kolab.org>


I have received  3 emails so far that won't open in the Horde web client.
They open fine on my phone and in Thunderbird.

The progress wheel continually spins, and eventually when the webclient
refreshes, I am returned to the Inbox, and the message is still showing unread.

I can forward examples if needed.

----------
messages: 27899
nosy: masfocus
priority: bug
status: unread
title: Email won't load in Horde

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4746>
______________________________________



From issues at kolab.org  Tue Jun 14 15:03:22 2011
From: issues at kolab.org (Sascha Wilde)
Date: Tue, 14 Jun 2011 13:03:22 +0000
Subject: [Kolab-devel] [issue4747] Z-Push with N900 client stopped working
	in Server 2.3.2
In-Reply-To: <1308056602.63.0.443317445727.issue4747@kolab.org>
Message-ID: <1308056602.63.0.443317445727.issue4747@kolab.org>


Hi *,

we upgraded from Server 2.3.0 to 2.3.2.

While with 2.3.0 Z-Push worked well to sync events and contacts on a
Nokia N900 with 2.3.2 it stopped working.

Synchronization runs without errors (according to the log in
/kolab/var/z-push/log/access.log and to the client).  But nothing gets
synced even though there are new events on the client as well as on
the server.

I tried:
- shutting down apache
- removing caches from /kolab/var/z-push/kolabindex/
- restarting apache
- complete resync of the client
but with no luck.

I attached anonymous versions of the log and debug.txt.

As this worked in 2.3.0 I'd say it's an regression...

----------
assignedto: alain.abbas
files: zpush-2.3.2-debug.txt
keyword: zpush
messages: 27940
nosy: alain.abbas, thomas, wickert, wilde
priority: critical
status: unread
title: Z-Push with N900 client stopped working in Server 2.3.2

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4747>
______________________________________
-------------- next part --------------
06/14/11 14:40:19 [27964] [foo.bar at example.com] Start
06/14/11 14:40:19 [27964] [foo.bar at example.com] Z-Push version: 1.5.2 (551)
06/14/11 14:40:19 [27964] [foo.bar at example.com] Client IP: 10.42.7.144
06/14/11 14:40:19 [27964] [foo.bar at example.com] Client supports version 2.5
06/14/11 14:40:19 [27964] [foo.bar at example.com] KolabBackend Version : 0.7.4
06/14/11 14:40:19 [27964] [foo.bar at example.com] KolabActiveSyndData Version : 20100707
06/14/11 14:40:19 [27964] [foo.bar at example.com] POST cmd: FolderSync
06/14/11 14:40:19 [27964] [foo.bar at example.com] Initializing folder diff engine
06/14/11 14:40:20 [27964] [foo.bar at example.com] Found 3 folder changes
06/14/11 14:40:20 [27964] [foo.bar at example.com] retreive Parent for INBOX/Kalender INBOX
06/14/11 14:40:20 [27964] [foo.bar at example.com] Parent id is dc063b45c92f64f79f0d1ed01e6d5b314f04886c for INBOX/Kalender
06/14/11 14:40:20 [27964] [foo.bar at example.com] IMAP-GetFolder(id: 'df09f97b033b56c15612e9a598d0cda7a5827ada') -> SyncFolder Object
(
    [serverid] => df09f97b033b56c15612e9a598d0cda7a5827ada
    [parentid] => dc063b45c92f64f79f0d1ed01e6d5b314f04886c
    [displayname] => kalender
    [type] => 8
    [_mapping] => Array
        (
            [FolderHierarchy:ServerEntryId] => Array
                (
                    [1] => serverid
                )

            [FolderHierarchy:ParentId] => Array
                (
                    [1] => parentid
                )

            [FolderHierarchy:DisplayName] => Array
                (
                    [1] => displayname
                )

            [FolderHierarchy:Type] => Array
                (
                    [1] => type
                )

        )

    [content] => 
    [attributes] => 
    [flags] => 
)

06/14/11 14:40:20 [27964] [foo.bar at example.com] retreive Parent for INBOX/Kalender INBOX
06/14/11 14:40:20 [27964] [foo.bar at example.com] Parent id is dc063b45c92f64f79f0d1ed01e6d5b314f04886c for INBOX/Kalender
06/14/11 14:40:20 [27964] [foo.bar at example.com] IMAP-GetFolder(id: 'df09f97b033b56c15612e9a598d0cda7a5827ada') -> SyncFolder Object
(
    [serverid] => df09f97b033b56c15612e9a598d0cda7a5827ada
    [parentid] => dc063b45c92f64f79f0d1ed01e6d5b314f04886c
    [displayname] => kalender
    [type] => 8
    [_mapping] => Array
        (
            [FolderHierarchy:ServerEntryId] => Array
                (
                    [1] => serverid
                )

            [FolderHierarchy:ParentId] => Array
                (
                    [1] => parentid
                )

            [FolderHierarchy:DisplayName] => Array
                (
                    [1] => displayname
                )

            [FolderHierarchy:Type] => Array
                (
                    [1] => type
                )

        )

    [content] => 
    [attributes] => 
    [flags] => 
)

06/14/11 14:40:20 [27964] [foo.bar at example.com] Change for folder 'kalender' will not be sent as modification is not relevant
06/14/11 14:40:20 [27964] [foo.bar at example.com] retreive Parent for INBOX/Kontakte INBOX
06/14/11 14:40:20 [27964] [foo.bar at example.com] Parent id is dc063b45c92f64f79f0d1ed01e6d5b314f04886c for INBOX/Kontakte
06/14/11 14:40:20 [27964] [foo.bar at example.com] IMAP-GetFolder(id: '97b145b54d28df7cb68e1b49c6cad0030ed6c336') -> SyncFolder Object
(
    [serverid] => 97b145b54d28df7cb68e1b49c6cad0030ed6c336
    [parentid] => dc063b45c92f64f79f0d1ed01e6d5b314f04886c
    [displayname] => kontakte
    [type] => 9
    [_mapping] => Array
        (
            [FolderHierarchy:ServerEntryId] => Array
                (
                    [1] => serverid
                )

            [FolderHierarchy:ParentId] => Array
                (
                    [1] => parentid
                )

            [FolderHierarchy:DisplayName] => Array
                (
                    [1] => displayname
                )

            [FolderHierarchy:Type] => Array
                (
                    [1] => type
                )

        )

    [content] => 
    [attributes] => 
    [flags] => 
)

06/14/11 14:40:20 [27964] [foo.bar at example.com] retreive Parent for INBOX/Kontakte INBOX
06/14/11 14:40:20 [27964] [foo.bar at example.com] Parent id is dc063b45c92f64f79f0d1ed01e6d5b314f04886c for INBOX/Kontakte
06/14/11 14:40:20 [27964] [foo.bar at example.com] IMAP-GetFolder(id: '97b145b54d28df7cb68e1b49c6cad0030ed6c336') -> SyncFolder Object
(
    [serverid] => 97b145b54d28df7cb68e1b49c6cad0030ed6c336
    [parentid] => dc063b45c92f64f79f0d1ed01e6d5b314f04886c
    [displayname] => kontakte
    [type] => 9
    [_mapping] => Array
        (
            [FolderHierarchy:ServerEntryId] => Array
                (
                    [1] => serverid
                )

            [FolderHierarchy:ParentId] => Array
                (
                    [1] => parentid
                )

            [FolderHierarchy:DisplayName] => Array
                (
                    [1] => displayname
                )

            [FolderHierarchy:Type] => Array
                (
                    [1] => type
                )

        )

    [content] => 
    [attributes] => 
    [flags] => 
)

06/14/11 14:40:20 [27964] [foo.bar at example.com] Change for folder 'kontakte' will not be sent as modification is not relevant
06/14/11 14:40:20 [27964] [foo.bar at example.com] retreive Parent for INBOX/Aufgaben INBOX
06/14/11 14:40:20 [27964] [foo.bar at example.com] Parent id is dc063b45c92f64f79f0d1ed01e6d5b314f04886c for INBOX/Aufgaben
06/14/11 14:40:20 [27964] [foo.bar at example.com] IMAP-GetFolder(id: '92dd8e60104251c47bf2196ae476ab889334d56d') -> SyncFolder Object
(
    [serverid] => 92dd8e60104251c47bf2196ae476ab889334d56d
    [parentid] => dc063b45c92f64f79f0d1ed01e6d5b314f04886c
    [displayname] => aufgaben
    [type] => 7
    [_mapping] => Array
        (
            [FolderHierarchy:ServerEntryId] => Array
                (
                    [1] => serverid
                )

            [FolderHierarchy:ParentId] => Array
                (
                    [1] => parentid
                )

            [FolderHierarchy:DisplayName] => Array
                (
                    [1] => displayname
                )

            [FolderHierarchy:Type] => Array
                (
                    [1] => type
                )

        )

    [content] => 
    [attributes] => 
    [flags] => 
)

06/14/11 14:40:20 [27964] [foo.bar at example.com] retreive Parent for INBOX/Aufgaben INBOX
06/14/11 14:40:20 [27964] [foo.bar at example.com] Parent id is dc063b45c92f64f79f0d1ed01e6d5b314f04886c for INBOX/Aufgaben
06/14/11 14:40:20 [27964] [foo.bar at example.com] IMAP-GetFolder(id: '92dd8e60104251c47bf2196ae476ab889334d56d') -> SyncFolder Object
(
    [serverid] => 92dd8e60104251c47bf2196ae476ab889334d56d
    [parentid] => dc063b45c92f64f79f0d1ed01e6d5b314f04886c
    [displayname] => aufgaben
    [type] => 7
    [_mapping] => Array
        (
            [FolderHierarchy:ServerEntryId] => Array
                (
                    [1] => serverid
                )

            [FolderHierarchy:ParentId] => Array
                (
                    [1] => parentid
                )

            [FolderHierarchy:DisplayName] => Array
                (
                    [1] => displayname
                )

            [FolderHierarchy:Type] => Array
                (
                    [1] => type
                )

        )

    [content] => 
    [attributes] => 
    [flags] => 
)

06/14/11 14:40:20 [27964] [foo.bar at example.com] Change for folder 'aufgaben' will not be sent as modification is not relevant
06/14/11 14:40:20 [27964] [foo.bar at example.com] IMAP-errors: SECURITY PROBLEM: insecure server advertised AUTH=PLAIN
06/14/11 14:40:20 [27964] [foo.bar at example.com] IMAP connection closed
06/14/11 14:40:20 [27964] [foo.bar at example.com] end
06/14/11 14:40:20 [27964] [foo.bar at example.com] --------
06/14/11 14:40:20 [27964] [foo.bar at example.com] Start
06/14/11 14:40:20 [27964] [foo.bar at example.com] Z-Push version: 1.5.2 (551)
06/14/11 14:40:20 [27964] [foo.bar at example.com] Client IP: 10.42.7.144
06/14/11 14:40:20 [27964] [foo.bar at example.com] Client supports version 2.5
06/14/11 14:40:20 [27964] [foo.bar at example.com] KolabBackend Version : 0.7.4
06/14/11 14:40:20 [27964] [foo.bar at example.com] KolabActiveSyndData Version : 20100707
06/14/11 14:40:20 [27964] [foo.bar at example.com] Killing process 27964 

From aheinecke at intevation.de  Thu Jun 16 10:51:41 2011
From: aheinecke at intevation.de (Andre Heinecke)
Date: Thu, 16 Jun 2011 10:51:41 +0200
Subject: [Kolab-devel] Updated Version of the Kolab E5 Client for Windows
	Package
Message-ID: <201106161051.41838.aheinecke@intevation.de>

Hello,
there has been an update of the Installation package for the Kolab Enterprise5 
Client - Rough Cut Edition. It now contains the latest versions of the newly 
released KDEPIM 4.6.0 Software.

You can download and test it at:
http://files.kolab.org/local/windows/kolab-enterprise5/experimental/latest

Please check out http://wiki.kolab.org/Kontact_for_Windows_(Enterprise-5) 
for more information.

Feedback is appreciated.
Regards,
Andre

-- 
Andre Heinecke |  ++49-541-335083-262 |  http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabr?ck | AG Osnabr?ck, HR B 18998
Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110616/40886148/attachment.sig>

From issues at kolab.org  Fri Jun 17 17:02:14 2011
From: issues at kolab.org (Thomas Arendsen Hein)
Date: Fri, 17 Jun 2011 15:02:14 +0000
Subject: [Kolab-devel] [issue4748] Z-Push: Events not synced from server to
	N900 client
In-Reply-To: <1308322934.52.0.318735318288.issue4748@kolab.org>
Message-ID: <1308322934.52.0.318735318288.issue4748@kolab.org>


After working around kolab/issue4747 (Z-Push with N900 client stopped working in
Server 2.3.2) by using an updated kolab.php for kolab-z-push, syncing events
from the N900 to Kolab Server 2.3.2 works fine.
But new events created on the server do not show up on the client.
Downgrading z-push from 1.5.3-1 to 1.5.1-1 solves the problem.

Alain, can you reproduce this?

Christoph: I copied the critical priority from 4747, feel free to downgrade if
you think this is more appropriate.

----------
assignedto: alain.abbas
keyword: zpush
messages: 27958
nosy: alain.abbas, thomas, wickert, wilde
priority: critical
related: Z-Push with N900 client stopped working in Server 2.3.2
status: unread
title: Z-Push: Events not synced from server to N900 client

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4748>
______________________________________



From issues at kolab.org  Fri Jun 17 17:22:14 2011
From: issues at kolab.org (Alain Abbas)
Date: Fri, 17 Jun 2011 15:22:14 +0000
Subject: [Kolab-devel] [issue4749] Z-push encoding problem where the
	accentued characters	are not in iso-8859-1 table
In-Reply-To: <1308324134.89.0.871523688732.issue4749@kolab.org>
Message-ID: <1308324134.89.0.871523688732.issue4749@kolab.org>


characters from russian for example are displayed ? and sometimes block the synchro
the default conversion for Kolab_Format is in ISO-8859-1 not in UTF-8

----------
keyword: zpush
messages: 27960
nosy: alain.abbas
priority: urgent
status: unread
title: Z-push encoding problem where the accentued characters are not in iso-8859-1 table

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4749>
______________________________________



From greve at kolabsys.com  Mon Jun 20 17:42:19 2011
From: greve at kolabsys.com (Georg C. F. Greve)
Date: Mon, 20 Jun 2011 17:42:19 +0200
Subject: [Kolab-devel] APPROVED: KEP #2: Modification of datetime: store
	local time, add 'tz' attribute
Message-ID: <4307137.Va2J6J0RA3@katana.lair>

Hi all,

Following the closing call on Mon Jun 6 12:19:20 CEST 2011

	http://kolab.org/pipermail/kolab-format/2011-June/001359.html

I'm happy to announce that "KEP #2: Modification of datetime: store local time, 
add 'tz' attribute" has been approved. 

It's final version is available in the canonical location at:

	http://wiki.kolab.org/KEP:2

With best regards,
Georg Greve


-- 
Georg C. F. Greve
Chief Executive Officer

Kolab Systems AG
Z?rich, Switzerland

e: greve at kolabsys.com
t: +41 78 904 43 33
w: http://kolabsys.com

pgp: 86574ACA Georg C. F. Greve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 308 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110620/289e3bd9/attachment.sig>

From greve at kolabsys.com  Mon Jun 20 17:42:26 2011
From: greve at kolabsys.com (Georg C. F. Greve)
Date: Mon, 20 Jun 2011 17:42:26 +0200
Subject: [Kolab-devel] APPROVED: KEP #3: Introduction of 'subevent' sub-tag
	for 'exclusion' from 'recurrence'
Message-ID: <4004370.dK1PDkYayg@katana.lair>

Hi all,

Following the closing call on Mon Jun 6 12:19:24 CEST 2011

	http://kolab.org/pipermail/kolab-devel/2011-June/012850.html

I'm happy to announce that "KEP #3: Introduction of 'subevent' sub-tag for 
'exclusion' from 'recurrence'" has been approved. 

It's final version is available in the canonical location at:

	http://wiki.kolab.org/KEP:3

With best regards,
Georg Greve


-- 
Georg C. F. Greve
Chief Executive Officer

Kolab Systems AG
Z?rich, Switzerland

e: greve at kolabsys.com
t: +41 78 904 43 33
w: http://kolabsys.com

pgp: 86574ACA Georg C. F. Greve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 308 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110620/5a216bf7/attachment.sig>

From geoffn at gnaa.net  Mon Jun 20 21:00:10 2011
From: geoffn at gnaa.net (Geoff Nordli)
Date: Mon, 20 Jun 2011 12:00:10 -0700
Subject: [Kolab-devel] Debian or Ubuntu repository
Message-ID: <000601cc2f7c$475959f0$d60c0dd0$@gnaa.net>

Hi.

 

Are there any plans to move to a Debian or Ubuntu repository to allow for
installation via apt-get?

 

The OpenPKG format works OK, but my goal is to automate the installations
via Puppet and provide easier updates. 

 

Thanks,

 

Geoff 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110620/f6944c0d/attachment.html>

From wickert at kolabsys.com  Mon Jun 20 23:51:14 2011
From: wickert at kolabsys.com (Christoph Wickert)
Date: Mon, 20 Jun 2011 23:51:14 +0200
Subject: [Kolab-devel] Debian or Ubuntu repository
In-Reply-To: <000601cc2f7c$475959f0$d60c0dd0$@gnaa.net>
References: <000601cc2f7c$475959f0$d60c0dd0$@gnaa.net>
Message-ID: <201106202351.19031.wickert@kolabsys.com>

On Monday 20 June 2011 21:00:10 Geoff Nordli wrote:

> Are there any plans to move to a Debian or Ubuntu repository to allow for
> installation via apt-get?

Yes, at http://mirror.kolabsys.com/pub/debian/ but it is work in progress. 
More to come soon.

> The OpenPKG format works OK, but my goal is to automate the installations
> via Puppet and provide easier updates.

So do we. OpenPKG is going to be phased out because it is no longer free 
software. 

Regards,
Christoph

-- 
Christoph Wickert
Senior Engineer

Kolab Systems AG
Z?rich, Switzerland

e: wickert at kolabsys.com
t: +49 251 871 369 77
w: http://kolabsys.com

pgp: 85DACC63 Christoph Wickert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110620/dfd45b01/attachment.sig>

From geoffn at gnaa.net  Tue Jun 21 03:24:54 2011
From: geoffn at gnaa.net (Geoff Nordli)
Date: Mon, 20 Jun 2011 18:24:54 -0700
Subject: [Kolab-devel] Debian or Ubuntu repository
In-Reply-To: <201106202351.19031.wickert@kolabsys.com>
References: <000601cc2f7c$475959f0$d60c0dd0$@gnaa.net>
	<201106202351.19031.wickert@kolabsys.com>
Message-ID: <002401cc2fb2$064a2b70$12de8250$@gnaa.net>

>From: Christoph Wickert
>Sent: Monday, June 20, 2011 2:51 PM
>Subject: Re: [Kolab-devel] Debian or Ubuntu repository
>
>On Monday 20 June 2011 21:00:10 Geoff Nordli wrote:
>
>> Are there any plans to move to a Debian or Ubuntu repository to allow
>> for installation via apt-get?
>
>Yes, at http://mirror.kolabsys.com/pub/debian/ but it is work in progress.
>More to come soon.
>
>> The OpenPKG format works OK, but my goal is to automate the
>> installations via Puppet and provide easier updates.
>
>So do we. OpenPKG is going to be phased out because it is no longer free
>software.
>

That is great news, creating a binary repository will make it easier for the
new people to get it running and hopefully increase mindshare.  I think
Kolab has a lot of potential providing core groupware functionality to the
SMB market. 

BTW, what is the long-term goal on the client side?   It seems that Kontact
E5 is the plan there, but it needs lots of work.    

Thanks,

Geoff  



From thomas at btspuhler.com  Tue Jun 21 06:30:13 2011
From: thomas at btspuhler.com (Thomas Spuhler)
Date: Mon, 20 Jun 2011 21:30:13 -0700
Subject: [Kolab-devel] Debian or Ubuntu repository
In-Reply-To: <002401cc2fb2$064a2b70$12de8250$@gnaa.net>
References: <000601cc2f7c$475959f0$d60c0dd0$@gnaa.net>
	<201106202351.19031.wickert@kolabsys.com>
	<002401cc2fb2$064a2b70$12de8250$@gnaa.net>
Message-ID: <201106202130.14069.thomas@btspuhler.com>

On Monday, June 20, 2011 06:24:54 pm Geoff Nordli wrote:
> >From: Christoph Wickert
> >Sent: Monday, June 20, 2011 2:51 PM
> >Subject: Re: [Kolab-devel] Debian or Ubuntu repository
> >
> >On Monday 20 June 2011 21:00:10 Geoff Nordli wrote:
> >> Are there any plans to move to a Debian or Ubuntu repository to allow
> >> for installation via apt-get?
> >
> >Yes, at http://mirror.kolabsys.com/pub/debian/ but it is work in progress.
> >More to come soon.
> >
> >> The OpenPKG format works OK, but my goal is to automate the
> >> installations via Puppet and provide easier updates.
> >
> >So do we. OpenPKG is going to be phased out because it is no longer free
> >software.
> 
> That is great news, creating a binary repository will make it easier for
> the new people to get it running and hopefully increase mindshare.  I
> think Kolab has a lot of potential providing core groupware functionality
> to the SMB market.
> 
> BTW, what is the long-term goal on the client side?   It seems that Kontact
> E5 is the plan there, but it needs lots of work.
> 
> Thanks,
> 
> Geoff
> 
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel

 I agree with: < I think Kolab has a lot of potential providing core groupware 
functionality to the SMB market>

But it will certainly get wider usage if folks can get it natively installed 
(apt or rpm)  and for that, packaging and maintaining needs to become less 
bothersome. Otherwise more maintainers will give up. My predecessor gave up 
because of the work needed, there is nobody at SUSE anymore because of too 
much work needed to package it. Mageia's version doesn't work because of the 
smarty upgrade to version 3 very late and the kolab-webadmin isn't usable with 
it.

-- 
Thomas



From issues at kolab.org  Tue Jun 21 22:04:33 2011
From: issues at kolab.org (Daniel Vergien)
Date: Tue, 21 Jun 2011 20:04:33 +0000
Subject: [Kolab-devel] [issue4750] db-4.5.20.2 fails to build on x86-solaris
	-10
In-Reply-To: <1308686673.07.0.356740355749.issue4750@kolab.org>
Message-ID: <1308686673.07.0.356740355749.issue4750@kolab.org>


Building kolab 2.3.2 on x86-solaris 10 fails with the following message:

{standard input}: Assembler messages:
{standard input}:73: Error: bad register name `%rax'
{standard input}:76: Error: bad register name `%rax'
make: *** [mut_tas.o] Error 1
make: *** Waiting for unfinished jobs....
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.3606 (%build)


RPM build errors:
    Bad exit status from /kolab/RPM/TMP/rpm-tmp.3606 (%build)
Installation completed.
/kolab/RPM/PKG now contains the installed packages.

----------
messages: 27967
nosy: daniel.vergien
priority: bug
status: unread
title: db-4.5.20.2 fails to build on x86-solaris -10

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4750>
______________________________________



From geoffn at gnaa.net  Tue Jun 21 23:56:40 2011
From: geoffn at gnaa.net (Geoff Nordli)
Date: Tue, 21 Jun 2011 14:56:40 -0700
Subject: [Kolab-devel] Kontact E5 questions
Message-ID: <018601cc305e$1a00a250$4e01e6f0$@gnaa.net>

Hi.

 

I installed E5 again on Windows 7 64bit to see what functionality currently
exists.  As a bonus the client looks really pretty.  J 

 

Is there documentation anywhere that describes how to configure it with a
Kolab server?  

 

How do I configure it so the calendar and tasks list pull from the Kolab
Server?

 

Can I configure Notebooks and Popup Notes to be stored on the Kolab server
too? 

 

Do I need to configure a SMTP connection to send email out from the client? 

 

How do I configure the client so when I type an email address it does
"auto-complete"?  It seems I need to query ldap for that, but there is no
ldap client for Kontact on Windows.

 

Can I do S/MIME? 

 

Thanks,

 

Geoff 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110621/1cf786ab/attachment.html>

From bernhard at intevation.de  Wed Jun 22 10:34:26 2011
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 22 Jun 2011 10:34:26 +0200
Subject: [Kolab-devel] Kontact E5 questions
In-Reply-To: <018601cc305e$1a00a250$4e01e6f0$@gnaa.net>
References: <018601cc305e$1a00a250$4e01e6f0$@gnaa.net>
Message-ID: <201106221034.29811.bernhard@intevation.de>

Hi Geoff,

Am Dienstag, 21. Juni 2011 23:56:40 schrieb Geoff Nordli:
> I installed E5 again on Windows 7 64bit to see what functionality currently
> exists.  As a bonus the client looks really pretty.  J

thanks for trying. I assume you've tried RouchCut Version 
Kolab-E5RC-2011-06-15-19-24.exe as linked from
http://wiki.kolab.org/Kontact_for_Windows_(Enterprise-5)

> Is there documentation anywhere that describes how to configure it with a
> Kolab server?

Just select "Kolab Server" in the account wizard with your address,
server and password. That should set up things nicely.
Help us to improve the documentation starting in the wiki,
if you need more. Probably pointers to other documentation
would be cool to have there as well.

> How do I configure it so the calendar and tasks list pull from the Kolab
> Server?

See above.

> Can I configure Notebooks and Popup Notes to be stored on the Kolab server
> too?

Yes, done by default.

> Do I need to configure a SMTP connection to send email out from the client?

Will be done by default. You can configure more SMTP outgoing connections 
manually, if you like.

> How do I configure the client so when I type an email address it does
> "auto-complete"?  It seems I need to query ldap for that, but there is no
> ldap client for Kontact on Windows.

As far as I remember this is currently not fully implemented on window.
If it works, the account wizard will enter your Kolab Server as first 
directory server to query.

> Can I do S/MIME?

The current roughcut version and gpg4win versions slightly missmatch. All the 
functions are there, once this has been matched S/MIME will work as nicely as 
everywhere with Kontact.

Best,
Bernhard
-- 
Managing Director + Owner: www.Intevation.net <- A Free Software Company
Kolabsys.com: Board Member          FSFE.org: Founding GA Member
Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998
Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3696 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110622/c96c3c9f/attachment.p7s>

From geoffn at gnaa.net  Wed Jun 22 16:20:34 2011
From: geoffn at gnaa.net (Geoff Nordli)
Date: Wed, 22 Jun 2011 07:20:34 -0700
Subject: [Kolab-devel] Kontact E5 questions
In-Reply-To: <201106221034.29811.bernhard@intevation.de>
References: <018601cc305e$1a00a250$4e01e6f0$@gnaa.net>
	<201106221034.29811.bernhard@intevation.de>
Message-ID: <008e01cc30e7$8cdeebe0$a69cc3a0$@gnaa.net>

Thanks for your reply Bernhard.
>
>Hi Geoff,
>
>Am Dienstag, 21. Juni 2011 23:56:40 schrieb Geoff Nordli:
>> I installed E5 again on Windows 7 64bit to see what functionality currently
>> exists.  As a bonus the client looks really pretty.  J
>
>thanks for trying. I assume you've tried RouchCut Version
>Kolab-E5RC-2011-06-15-19-24.exe as linked from
>http://wiki.kolab.org/Kontact_for_Windows_(Enterprise-5)

Yes, that is the version I installed.  

>
>> Is there documentation anywhere that describes how to configure it with a
>> Kolab server?
>
>Just select "Kolab Server" in the account wizard with your address,
>server and password. That should set up things nicely.
>Help us to improve the documentation starting in the wiki,
>if you need more. Probably pointers to other documentation
>would be cool to have there as well.

Wow!!  Going through the wizard made a huge difference.   :)

>
>> How do I configure the client so when I type an email address it does
>> "auto-complete"?  It seems I need to query ldap for that, but there is no
>> ldap client for Kontact on Windows.

>As far as I remember this is currently not fully implemented on window.
>If it works, the account wizard will enter your Kolab Server as first
>directory server to query.
>

Yes, it does auto-complete when it searches for address.  

>> Can I do S/MIME?
>
>The current roughcut version and gpg4win versions slightly missmatch. All the
>functions are there, once this has been matched S/MIME will work as nicely as
>everywhere with Kontact.


Another question, is there a way to remove the "local folders" options so people only see the Kolab Server data stores?

Thanks Bernhard.

Geoff 




From wrobel at horde.org  Thu Jun 23 11:21:15 2011
From: wrobel at horde.org (Gunnar Wrobel)
Date: Thu, 23 Jun 2011 11:21:15 +0200
Subject: [Kolab-devel] Kolab commit messages (was: list.php)
In-Reply-To: <201106161129.p5GBToOp007724@app01.kolabsys.com>
References: <201106161129.p5GBToOp007724@app01.kolabsys.com>
Message-ID: <20110623112115.Horde._BFFPQ6_GnlOAwWLoxMTcZA@wrbl.de>

Hi!

This reply is actually not about the commit displayed below but rather  
about its format.

Quoting Bogomil Shopov <shopov at kolabsys.com>:

> list.php |    5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
>
> New commits:
> commit 223404104f9a4560918febf54a11d883da3fe0ae
> Author: Bogomil Shopov (Kolab Systems) <shopov at kolabsys.com>
> Date:   Thu Jun 16 14:29:18 2011 +0300
>
>     Fixing problem with not-showing mail folders. Horde alrternative  
> of: https://bugzilla.kolabsys.com/show_bug.cgi?id=98#c15
>
> diff --git a/list.php b/list.php
> index 5f36359..abb708d 100755
> --- a/list.php
> +++ b/list.php
> @@ -173,7 +173,10 @@ function ReturnDataArray($list,$type)
>
>  }
>  //mail
> -$mails= ReturnDataArray($list,"");
> +$mails1= ReturnDataArray($list,"");
> +$mails2= ReturnDataArray($list,"mail");
> +
> +$mails=array_merge($mails1,$mails2);
>
>  //contact
>  $conts = ReturnDataArray($list,'contact');
>
>
> _______________________________________________
> kolab-commits mailing list
> kolab-commits at kolab.org
> https://kolab.org/mailman/listinfo/kolab-commits

Would it be possible to somehow add the name of the source repository  
in here? I know it is in the mail headers but it would be convenient  
to immediately see from the mail body which of the Kolab repositories  
the commit belongs to.

Cheers,

Gunnar

-- 
Core Developer
The Horde Project

e: wrobel at horde.org
t: +49 700 6245 0000
w: http://www.horde.org

pgp: 9703 43BE
tweets: http://twitter.com/pardus_de
blog: http://log.pardus.de



From wrobel at horde.org  Thu Jun 23 12:37:35 2011
From: wrobel at horde.org (Gunnar Wrobel)
Date: Thu, 23 Jun 2011 12:37:35 +0200
Subject: [Kolab-devel] lib/KolabAdmin package.xml www/admin
In-Reply-To: <201106230955.p5N9twPN032496@app01.kolabsys.com>
References: <201106230955.p5N9twPN032496@app01.kolabsys.com>
Message-ID: <20110623123735.Horde.jn6uIQ6_GnlOAxdvx1-zUbA@wrbl.de>

Quoting Bogomil Shopov <shopov at kolabsys.com>:

> lib/KolabAdmin/include/menu.php |   35 ++++++++++++++++++++++++++++-------
>  package.xml                     |   11 +++++++----
>  www/admin/user/activesync.php   |   16 ++++++++++------
>  3 files changed, 45 insertions(+), 17 deletions(-)
>
> New commits:
> commit 253dd2c9f6054919036ccc56e07b6ccdb8608608
> Author: Bogomil Shopov (Kolab Systems) <shopov at kolabsys.com>
> Date:   Thu Jun 23 12:55:37 2011 +0300
>
>     Adding ACL checking for ActiveSync. Removing duplicated menu  
> Items. Hiding menu and functionalities depends on ACL.
>
>     Changinf package xml with adding file tasks.
>
> diff --git a/lib/KolabAdmin/include/menu.php  
> b/lib/KolabAdmin/include/menu.php
> index b079453..e1bc874 100644
> --- a/lib/KolabAdmin/include/menu.php
> +++ b/lib/KolabAdmin/include/menu.php
> @@ -3,7 +3,8 @@
>   *  Copyright (c) 2004 Klar?lvdalens Datakonsult AB
>   *
>   *    Written by Steffen Hansen <steffen at klaralvdalens-datakonsult.se>
> - *
> + *	  Updated by Bogomil Shopov <shopov at kolabsys.com>
> + *
>   *  This  program is free  software; you can redistribute  it and/or
>   *  modify it  under the terms of the GNU  General Public License as
>   *  published by the  Free Software Foundation; either version 2, or
> @@ -20,8 +21,28 @@
>
>  require_once('locale.php');
>
> +/*
> + * z-Push part for activesync
> + *
> + * */
> +
> +include_once '@www_dir@/z-push/config.php';
> +$showasmenu=true;
> +if(defined('KOLAB_LDAP_ACL') and KOLAB_LDAP_ACL !=""){
> +	$showasmenu=false;
> +	$filter = '(member='.$_SESSION['auth_user'].')';
> +	$result = $ldap->search( KOLAB_LDAP_ACL, $filter);
> +	if (ldap_count_entries($ldap->connection, $result) > 0)
> +		$showasmenu=true;
> +}
> +
> +/*
> + * end z-push activesync part
> + * */
> +
>  $menuitems = array();
>
> +
>  if( $auth->group() == "admin" || $auth->group() == "maintainer" ||  
> $auth->group() == 'domain-maintainer' ) {
>    $menuitems['user'] = array( 'name' => _('Users'),
>  							  'url'  => $topdir.'/user/',
> @@ -39,14 +60,14 @@ if( $auth->group() == "admin" || $auth->group()  
> == "maintainer" || $auth->group(
>  												 array( 'name' => _('Forward Email'),
>  														'url'  => 'forward.php' ),
>  												 array( 'name' => _('Vacation'),
> -														'url'  => 'vacation.php' ),
> -												array( 'name' => _('ActiveSync'),
> -														'url'  => 'activesync.php' ),
> -																		));
> -
> +														'url'  => 'vacation.php' )
> +																	));
> +if($showasmenu){
> +
>  	$menuitems['activesync'] = array( 'name' => _('ActiveSync'),
>  							  'url'  => $topdir.'/user/activesync.php',
> -							  'title' => _('ActiveSync'));
> +							  'title' => _('ActiveSync'));
> + }
>  }
>  if( $auth->group() == "admin" || $auth->group() == "maintainer") {
>    $menuitems['addressbook'] = array( 'name' => _('Addressbook'),
> diff --git a/package.xml b/package.xml
> index 572b22c..c60bc4b 100644
> --- a/package.xml
> +++ b/package.xml
> @@ -121,7 +121,9 @@
>        <file name="headers.php" role="php" />
>        <file name="ldap.class.php" role="php" />
>        <file name="locale.php" role="php" />
> -      <file name="menu.php" role="php" />
> +      <file name="menu.php" role="php" >
> +      	<replace from="@www_dir@" to="www_dir" type="pear-config"/>
> +      	</file>
>        <file name="mysmarty.php" role="php" />
>        <file name="passwd.php" role="php" />
>        <file name="Sieve.php" role="php" />
> @@ -244,14 +246,15 @@
>        <file name="sf.php" role="www" />
>       </dir> <!-- /www/admin/sharedfolder -->
>       <dir name="user">
> -      <file name="activesync.php" role="www" />
> +      <file name="activesync.php" role="php">
> +      	<replace from="@www_dir@" to="www_dir" type="pear-config"/>
> +      </file>
>        <file name="deliver.php" role="www" />
>        <file name="forward.php" role="www" />
>        <file name="index.php" role="www" />
>        <file name="user.php" role="www" />
>        <file name="vacation.php" role="www" />
> -      <file name="activesync.php" role="www" />
> -     </dir> <!-- /www/admin/user -->
> +      </dir> <!-- /www/admin/user -->
>       <file name="custom.css" role="www" />
>       <file name="favicon.ico" role="www" />
>       <file name="favicon.png" role="www" />
> diff --git a/www/admin/user/activesync.php b/www/admin/user/activesync.php
> index 0b211cb..0c51e96 100755
> --- a/www/admin/user/activesync.php
> +++ b/www/admin/user/activesync.php
> @@ -27,12 +27,8 @@ require_once('KolabAdmin/include/authenticate.php');
>  require_once('KolabAdmin/include/form.class.php');
>  require_once('KolabAdmin/include/passwd.php');
>
> -//try to include ALL possible configuration files
> - at include_once '/kolab/var/kolab/www/z-push/config.php';
> - at include_once '/etc/z-push/config.php';
> - at include_once '/usr/share/z-push/config.php';
> - at include_once '/var/www/z-push/config.php';
> -
> +//include z-Push config file file
> +include_once '@www_dir@/z-push/config.php';

It was a lot of work to get hardcoded paths out of the web admin. You  
should avoid hardcoding the knowledge of the installation path to  
z-push in the code. While "@www_dir@" is variable it is being replaced  
with a hard coded path when building the distributable package. In  
theory the system administrator should be able to place the z-push  
application anywhere he would like. I know: on OpenPKG this is usually  
not the case but we shouldn't code specifically for OpenPKG.

So this should go into a configuration variable.

Cheers,

Gunnar

>
>
>  //define errors array
> @@ -43,6 +39,14 @@ if((@include_once  
> 'Horde/Kolab/Kolab_Zpush/lib/kolabActivesyncData.php') === fal
>  	$errors[] =_('zPush in not enabled in your system.');
>  }
>
> +//check for permissions ACL from zpush config file
> +if(defined('KOLAB_LDAP_ACL') and KOLAB_LDAP_ACL !=""){
> +	$filter = '(member='.$_SESSION['auth_user'].')';
> +	$result = $ldap->search( KOLAB_LDAP_ACL, $filter);
> +	if (ldap_count_entries($ldap->connection, $result) == 0)
> +		$errors[] ="You don't have permissions to manage your activeSync  
> devices.";
> +}
> +
>  /*read from her value of the KOLAB_LAXPIC
>   -1 = allow the user to select (or if the constant doesn't exist)
>   0  = same as the annotations (no lax mode just jpeg)

-- 
Core Developer
The Horde Project

e: wrobel at horde.org
t: +49 700 6245 0000
w: http://www.horde.org

pgp: 9703 43BE
tweets: http://twitter.com/pardus_de
blog: http://log.pardus.de



From shopov at kolabsys.com  Thu Jun 23 16:04:50 2011
From: shopov at kolabsys.com (Bogomil "Bogo" Shopov)
Date: Thu, 23 Jun 2011 17:04:50 +0300
Subject: [Kolab-devel] HORDE ACL
Message-ID: <4E034802.1040602@kolabsys.com>

Hey there,
Where I can see some hints/examples documentation on working with ACL
from HORDE using rfc2086 driver or anything else?

The situation is I want to restrict access to an application if the
logged in (in Horde) user is not member of a LDAP group.

-- 
Bogomil "Bogo" Shopov
Senior Web Engineer

Kolab Systems AG
Z?rich, Switzerland

e: shopov at kolabsys.com
t: +359 888 098 768
w: http://kolabsys.com

pgp: 0xE69A226A Bogomil Shopov



From shopov at kolabsys.com  Thu Jun 23 16:07:28 2011
From: shopov at kolabsys.com (Bogomil "Bogo" Shopov)
Date: Thu, 23 Jun 2011 17:07:28 +0300
Subject: [Kolab-devel] HORDE ACL
In-Reply-To: <4E034802.1040602@kolabsys.com>
References: <4E034802.1040602@kolabsys.com>
Message-ID: <4E0348A0.1050305@kolabsys.com>

On 06/23/2011 05:04 PM, Bogomil "Bogo" Shopov wrote:
> Hey there,
> Where I can see some hints/examples documentation on working with ACL
> from HORDE using rfc2086 driver or anything else?
In fact I need it for that - read bellow:
> The situation is I want to restrict access to an application if the
> logged in (in Horde) user is not member of a LDAP group.
>


-- 
Bogomil "Bogo" Shopov
Senior Web Engineer

Kolab Systems AG
Z?rich, Switzerland

e: shopov at kolabsys.com
t: +359 888 098 768
w: http://kolabsys.com

pgp: 0xE69A226A Bogomil Shopov



From shopov at kolabsys.com  Thu Jun 23 13:16:07 2011
From: shopov at kolabsys.com (Bogomil "Bogo" Shopov)
Date: Thu, 23 Jun 2011 14:16:07 +0300
Subject: [Kolab-devel] lib/KolabAdmin package.xml www/admin
In-Reply-To: <20110623123735.Horde.jn6uIQ6_GnlOAxdvx1-zUbA@wrbl.de>
References: <201106230955.p5N9twPN032496@app01.kolabsys.com>
	<20110623123735.Horde.jn6uIQ6_GnlOAxdvx1-zUbA@wrbl.de>
Message-ID: <4E032077.1070103@kolabsys.com>

On 06/23/2011 01:37 PM, Gunnar Wrobel wrote:
> Quoting Bogomil Shopov <shopov at kolabsys.com>:
>
>> lib/KolabAdmin/include/menu.php |   35 ++++++++++++++++++++++++++++-------
>>  package.xml                     |   11 +++++++----
>>  www/admin/user/activesync.php   |   16 ++++++++++------
>>  3 files changed, 45 insertions(+), 17 deletions(-)
>>
>> New commits:
>> commit 253dd2c9f6054919036ccc56e07b6ccdb8608608
>> Author: Bogomil Shopov (Kolab Systems) <shopov at kolabsys.com>
>> Date:   Thu Jun 23 12:55:37 2011 +0300
>>
>>     Adding ACL checking for ActiveSync. Removing duplicated menu
>> Items. Hiding menu and functionalities depends on ACL.
>>
>>     Changinf package xml with adding file tasks.
>>
>> diff --git a/lib/KolabAdmin/include/menu.php
>> b/lib/KolabAdmin/include/menu.php
>> index b079453..e1bc874 100644
>> --- a/lib/KolabAdmin/include/menu.php
>> +++ b/lib/KolabAdmin/include/menu.php
>> @@ -3,7 +3,8 @@
>>   *  Copyright (c) 2004 Klar?lvdalens Datakonsult AB
>>   *
>>   *    Written by Steffen Hansen <steffen at klaralvdalens-datakonsult.se>
>> - *
>> + *	  Updated by Bogomil Shopov <shopov at kolabsys.com>
>> + *
>>   *  This  program is free  software; you can redistribute  it and/or
>>   *  modify it  under the terms of the GNU  General Public License as
>>   *  published by the  Free Software Foundation; either version 2, or
>> @@ -20,8 +21,28 @@
>>
>>  require_once('locale.php');
>>
>> +/*
>> + * z-Push part for activesync
>> + *
>> + * */
>> +
>> +include_once '@www_dir@/z-push/config.php';
>> +$showasmenu=true;
>> +if(defined('KOLAB_LDAP_ACL') and KOLAB_LDAP_ACL !=""){
>> +	$showasmenu=false;
>> +	$filter = '(member='.$_SESSION['auth_user'].')';
>> +	$result = $ldap->search( KOLAB_LDAP_ACL, $filter);
>> +	if (ldap_count_entries($ldap->connection, $result) > 0)
>> +		$showasmenu=true;
>> +}
>> +
>> +/*
>> + * end z-push activesync part
>> + * */
>> +
>>  $menuitems = array();
>>
>> +
>>  if( $auth->group() == "admin" || $auth->group() == "maintainer" ||
>> $auth->group() == 'domain-maintainer' ) {
>>    $menuitems['user'] = array( 'name' => _('Users'),
>>  							  'url'  => $topdir.'/user/',
>> @@ -39,14 +60,14 @@ if( $auth->group() == "admin" || $auth->group()
>> == "maintainer" || $auth->group(
>>  												 array( 'name' => _('Forward Email'),
>>  														'url'  => 'forward.php' ),
>>  												 array( 'name' => _('Vacation'),
>> -														'url'  => 'vacation.php' ),
>> -												array( 'name' => _('ActiveSync'),
>> -														'url'  => 'activesync.php' ),
>> -																		));
>> -
>> +														'url'  => 'vacation.php' )
>> +																	));
>> +if($showasmenu){
>> +
>>  	$menuitems['activesync'] = array( 'name' => _('ActiveSync'),
>>  							  'url'  => $topdir.'/user/activesync.php',
>> -							  'title' => _('ActiveSync'));
>> +							  'title' => _('ActiveSync'));
>> + }
>>  }
>>  if( $auth->group() == "admin" || $auth->group() == "maintainer") {
>>    $menuitems['addressbook'] = array( 'name' => _('Addressbook'),
>> diff --git a/package.xml b/package.xml
>> index 572b22c..c60bc4b 100644
>> --- a/package.xml
>> +++ b/package.xml
>> @@ -121,7 +121,9 @@
>>        <file name="headers.php" role="php" />
>>        <file name="ldap.class.php" role="php" />
>>        <file name="locale.php" role="php" />
>> -      <file name="menu.php" role="php" />
>> +      <file name="menu.php" role="php" >
>> +      	<replace from="@www_dir@" to="www_dir" type="pear-config"/>
>> +      	</file>
>>        <file name="mysmarty.php" role="php" />
>>        <file name="passwd.php" role="php" />
>>        <file name="Sieve.php" role="php" />
>> @@ -244,14 +246,15 @@
>>        <file name="sf.php" role="www" />
>>       </dir> <!-- /www/admin/sharedfolder -->
>>       <dir name="user">
>> -      <file name="activesync.php" role="www" />
>> +      <file name="activesync.php" role="php">
>> +      	<replace from="@www_dir@" to="www_dir" type="pear-config"/>
>> +      </file>
>>        <file name="deliver.php" role="www" />
>>        <file name="forward.php" role="www" />
>>        <file name="index.php" role="www" />
>>        <file name="user.php" role="www" />
>>        <file name="vacation.php" role="www" />
>> -      <file name="activesync.php" role="www" />
>> -     </dir> <!-- /www/admin/user -->
>> +      </dir> <!-- /www/admin/user -->
>>       <file name="custom.css" role="www" />
>>       <file name="favicon.ico" role="www" />
>>       <file name="favicon.png" role="www" />
>> diff --git a/www/admin/user/activesync.php b/www/admin/user/activesync.php
>> index 0b211cb..0c51e96 100755
>> --- a/www/admin/user/activesync.php
>> +++ b/www/admin/user/activesync.php
>> @@ -27,12 +27,8 @@ require_once('KolabAdmin/include/authenticate.php');
>>  require_once('KolabAdmin/include/form.class.php');
>>  require_once('KolabAdmin/include/passwd.php');
>>
>> -//try to include ALL possible configuration files
>> - at include_once '/kolab/var/kolab/www/z-push/config.php';
>> - at include_once '/etc/z-push/config.php';
>> - at include_once '/usr/share/z-push/config.php';
>> - at include_once '/var/www/z-push/config.php';
>> -
>> +//include z-Push config file file
>> +include_once '@www_dir@/z-push/config.php';
> It was a lot of work to get hardcoded paths out of the web admin. You
> should avoid hardcoding the knowledge of the installation path to
> z-push in the code. While "@www_dir@" is variable it is being replaced
> with a hard coded path when building the distributable package. 

> In
> theory the system administrator should be able to place the z-push
> application anywhere he would like.
I don't think he can so easy to do that :)
>  I know: on OpenPKG this is usually
> not the case but we shouldn't code specifically for OpenPKG.
>
> So this should go into a configuration variable.
Any recommendations  then?
> Cheers,
>
> Gunnar
>
>>
>>  //define errors array
>> @@ -43,6 +39,14 @@ if((@include_once
>> 'Horde/Kolab/Kolab_Zpush/lib/kolabActivesyncData.php') === fal
>>  	$errors[] =_('zPush in not enabled in your system.');
>>  }
>>
>> +//check for permissions ACL from zpush config file
>> +if(defined('KOLAB_LDAP_ACL') and KOLAB_LDAP_ACL !=""){
>> +	$filter = '(member='.$_SESSION['auth_user'].')';
>> +	$result = $ldap->search( KOLAB_LDAP_ACL, $filter);
>> +	if (ldap_count_entries($ldap->connection, $result) == 0)
>> +		$errors[] ="You don't have permissions to manage your activeSync
>> devices.";
>> +}
>> +
>>  /*read from her value of the KOLAB_LAXPIC
>>   -1 = allow the user to select (or if the constant doesn't exist)
>>   0  = same as the annotations (no lax mode just jpeg)
> --
> Core Developer
> The Horde Project
>
> e: wrobel at horde.org
> t: +49 700 6245 0000
> w: http://www.horde.org
>
> pgp: 9703 43BE
> tweets: http://twitter.com/pardus_de
> blog: http://log.pardus.de
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel


-- 
Bogomil "Bogo" Shopov
Senior Web Engineer

Kolab Systems AG
Z?rich, Switzerland

e: shopov at kolabsys.com
t: +359 888 098 768
w: http://kolabsys.com

pgp: 0xE69A226A Bogomil Shopov



From wrobel at horde.org  Fri Jun 24 05:38:30 2011
From: wrobel at horde.org (Gunnar Wrobel)
Date: Fri, 24 Jun 2011 05:38:30 +0200
Subject: [Kolab-devel] lib/KolabAdmin package.xml www/admin
In-Reply-To: <4E032077.1070103@kolabsys.com>
References: <201106230955.p5N9twPN032496@app01.kolabsys.com>
	<20110623123735.Horde.jn6uIQ6_GnlOAxdvx1-zUbA@wrbl.de>
	<4E032077.1070103@kolabsys.com>
Message-ID: <20110624053830.Horde.4amQEA6_GnlOBAa2irLzxOA@wrbl.de>

Quoting "Bogomil \"Bogo\" Shopov" <shopov at kolabsys.com>:

> On 06/23/2011 01:37 PM, Gunnar Wrobel wrote:
>> Quoting Bogomil Shopov <shopov at kolabsys.com>:

[snip]

>> It was a lot of work to get hardcoded paths out of the web admin. You
>> should avoid hardcoding the knowledge of the installation path to
>> z-push in the code. While "@www_dir@" is variable it is being replaced
>> with a hard coded path when building the distributable package.
>
>> In
>> theory the system administrator should be able to place the z-push
>> application anywhere he would like.
>
> I don't think he can so easy to do that :)

Why exactly? To me there seems to be no technical reason why the  
z-push application would have to be installed in the same document  
root in the same directory where you place the web admin.

>
>>  I know: on OpenPKG this is usually
>> not the case but we shouldn't code specifically for OpenPKG.
>>
>> So this should go into a configuration variable.
> Any recommendations  then?

A configuration variable typically lives in the configuration file.  
For the Kolab web admin this would be  
/kolab/var/kolab/php/admin/include/config.php on OpenPKG. This is  
where we also configure other paths.

Cheers,

Gunnar


-- 
Core Developer
The Horde Project

e: wrobel at horde.org
t: +49 700 6245 0000
w: http://www.horde.org

pgp: 9703 43BE
tweets: http://twitter.com/pardus_de
blog: http://log.pardus.de



From wrobel at horde.org  Fri Jun 24 05:54:30 2011
From: wrobel at horde.org (Gunnar Wrobel)
Date: Fri, 24 Jun 2011 05:54:30 +0200
Subject: [Kolab-devel] HORDE ACL
Message-ID: <20110624055430.Horde.NdWEHQ6_GnlOBAp2GF6XLoA@wrbl.de>

Quoting "Bogomil \"Bogo\" Shopov" <shopov at kolabsys.com>:

> On 06/23/2011 05:04 PM, Bogomil "Bogo" Shopov wrote:
>> Hey there,
>> Where I can see some hints/examples documentation on working with ACL
>> from HORDE using rfc2086 driver or anything else?
> In fact I need it for that - read bellow:
>> The situation is I want to restrict access to an application if the
>> logged in (in Horde) user is not member of a LDAP group.

This sounds like something that is easy to do by using Horde_Ldap. You  
can get it via PEAR like this:

pear discover-channel pear.horde.org
pear install horde/horde_ldap

Cheers,

Gunnar

>>
>
>
> --
> Bogomil "Bogo" Shopov
> Senior Web Engineer
>
> Kolab Systems AG
> Z?rich, Switzerland
>
> e: shopov at kolabsys.com
> t: +359 888 098 768
> w: http://kolabsys.com
>
> pgp: 0xE69A226A Bogomil Shopov
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel

-- 
Core Developer
The Horde Project

e: wrobel at horde.org
t: +49 700 6245 0000
w: http://www.horde.org

pgp: 9703 43BE
tweets: http://twitter.com/pardus_de
blog: http://log.pardus.de



From vanmeeuwen at kolabsys.com  Sat Jun 25 19:44:47 2011
From: vanmeeuwen at kolabsys.com (Jeroen van Meeuwen (Kolab Systems))
Date: Sat, 25 Jun 2011 18:44:47 +0100
Subject: [Kolab-devel] Kolab commit messages (was: list.php)
In-Reply-To: <20110623112115.Horde._BFFPQ6_GnlOAwWLoxMTcZA@wrbl.de>
References: <201106161129.p5GBToOp007724@app01.kolabsys.com>
	<20110623112115.Horde._BFFPQ6_GnlOAwWLoxMTcZA@wrbl.de>
Message-ID: <201106251844.48609.vanmeeuwen@kolabsys.com>

Gunnar Wrobel wrote:
> Would it be possible to somehow add the name of the source repository
> in here? I know it is in the mail headers but it would be convenient
> to immediately see from the mail body which of the Kolab repositories
> the commit belongs to.
> 

A typical sysadmin-main request, which is hence-forth in CC.

I'll take a look at it some time tomorrow if I have sufficient opportunity to 
recover from tonight's party ;-)

Kind regards,

Jeroen van Meeuwen

-- 
Senior Engineer, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08



From h.helwich at tarent.de  Mon Jun 27 12:30:17 2011
From: h.helwich at tarent.de (Hendrik Helwich)
Date: Mon, 27 Jun 2011 12:30:17 +0200
Subject: [Kolab-devel] New Kolab client: Evolution
Message-ID: <201106271230.17949.h.helwich@tarent.de>

Hi everyone.

After a period of much work, the evolution-kolab team gladly announces what 
you could call a first release candidate of the Kolab plugin for Evolution.
Source code, packages, user manual and some supplemental files can be found 
on the project's website, located at SourceForge:

http://evolution-kolab.sourceforge.net/

Christian has made a detailed announcement on the project mailing list:

https://sourceforge.net/mailarchive/message.php?msg_id=27679445

We're looking forward to receiving your feedback on the project, preferably 
via the project mailing list or the project bug tracker:

http://sourceforge.net/tracker/?limit=50&group_id=343941&atid=1439212

Kind regards,

Hendrik

P.S.:
these two findings might also be of interest for developers in the realm of 
Kolab: 
1. While analysing the reference client's (Konatct-E35 and Toltec) behavior 
and their conformance to the Kolab-Format specification, we discovered some 
flaws, which are also documented in "Conversion Issues": 
http://sourceforge.net/apps/mediawiki/evolution-kolab/index.php?title=Conversion_Issues
2. We discovered a couple of bugs in Kontact (and Evolution), most of which we 
were not able to find in the kolab-bugtracker. In order not to lose track of 
these deficiencies, we created a table of these in our wiki: 
http://sourceforge.net/apps/mediawiki/evolution-kolab/index.php?title=Known_Kontact/Evolution_Bugs


-- 
tarent solutions GmbH
Rochusstra?e 2-4, D-53123 Bonn ? http://www.tarent.de/
Tel: +49 228 52675-0 ? Fax: +49 228 52675-25
HRB AG Bonn 5168 ? USt-ID (VAT): DE122264941
Gesch?ftsf?hrer: Boris Esser, Elmar Geese



From thomas at koch.ro  Mon Jun 27 18:44:47 2011
From: thomas at koch.ro (Thomas Koch)
Date: Mon, 27 Jun 2011 18:44:47 +0200
Subject: [Kolab-devel] dovecot?
Message-ID: <201106271844.47259.thomas@koch.ro>

Hi,

there has been some discussion and work been done on making Kolab work with 
dovecot back in 2008. But I couldn't find any more recent information on the 
subject.
Could somebody please give a summary and maybe outlook, whether Kolab could be 
used with dovecot?

Thank you!

Thomas Koch, http://www.koch.ro



From greve at kolabsys.com  Mon Jun 27 19:25:36 2011
From: greve at kolabsys.com (Georg C. F. Greve)
Date: Mon, 27 Jun 2011 19:25:36 +0200
Subject: [Kolab-devel] dovecot?
In-Reply-To: <201106271844.47259.thomas@koch.ro>
References: <201106271844.47259.thomas@koch.ro>
Message-ID: <1848755.tUqggdKlYv@katana.lair>

Hi Thomas,

On Monday 27 June 2011 18.44:47 Thomas Koch wrote:
> there has been some discussion and work been done on making Kolab work with 
> dovecot back in 2008. But I couldn't find any more recent information on
> the subject.

There is a patch that would enable METADATA now [1] so the barrier for using 
Dovecot has decreased substantially. The question is which server side parts 
are still using ANNOTATEMORE exclusively - these would have to be updated.

If you want to play with it please go ahead and let us know where you 
encountered issues.

Best regards,
Georg


[1] ttp://hg.dovecot.org/dovecot-metadata-plugin/

-- 
Georg C. F. Greve
Chief Executive Officer

Kolab Systems AG
Z?rich, Switzerland

e: greve at kolabsys.com
t: +41 78 904 43 33
w: http://kolabsys.com

pgp: 86574ACA Georg C. F. Greve



From thomas at koch.ro  Tue Jun 28 09:15:55 2011
From: thomas at koch.ro (Thomas Koch)
Date: Tue, 28 Jun 2011 09:15:55 +0200
Subject: [Kolab-devel] Searching a topic for my university paper/lab work
Message-ID: <201106280915.56844.thomas@koch.ro>

Hi,

to finish my bachelor in computer science I still have to do ~7 weeks of lab 
work and write my thesis (3 months). I'd like to work in the area of groupware 
(or a photo gallery, but that's not Kolab).

I'd very much like to do my project in Scala.

Do you have ideas for projects / topics?
Is there any company who would like to sponsor my work?

I've already worked 5 years as a developer, hold a degree in physics, 33 years 
old, living near Konstanz in Switzerland. I've given conference talks in the 
area of quality assurance, NoSQL and GIT.

Best regards,

Thomas Koch, http://www.koch.ro



From thomas at koch.ro  Tue Jun 28 10:45:13 2011
From: thomas at koch.ro (Thomas Koch)
Date: Tue, 28 Jun 2011 10:45:13 +0200
Subject: [Kolab-devel] small questions
Message-ID: <201106281045.13201.thomas@koch.ro>

Hi,

- I've once read, that Kolab would be hard to package because it patches many 
of the components it uses. However today the only patches remaining are for 
Cyrus, right?

- The only authorative VCS used for Kolab is GIT? It would be useful to erase 
all references to Hg and CVS to avoid confusion.

- What is in the kolab-server git repository (compared to the "server" repo)?

- Does Kolab work with Kontact from Debian testing? stable? 
http://packages.debian.org/search?keywords=kontact

- Have you heard of the GIT based coder review tool Gerrit[1]? I've given 
talks about it recently and would love to help projects to use it. Make sure 
to watch the 10 minuted video about it![2]

[1] http://en.wikipedia.org/wiki/Gerrit_(software)
[2] http://alblue.bandlem.com/2011/02/gerrit-git-review-with-jenkins-ci.html

Thank you!

Thomas Koch, http://www.koch.ro



From alain.abbas at libertech.fr  Tue Jun 28 12:11:44 2011
From: alain.abbas at libertech.fr (Alain Abbas)
Date: Tue, 28 Jun 2011 12:11:44 +0200
Subject: [Kolab-devel] small questions
In-Reply-To: <201106281045.13201.thomas@koch.ro>
References: <201106281045.13201.thomas@koch.ro>
Message-ID: <4E09A8E0.4020304@libertech.fr>

Thomas Koch a ?crit :
> Hi,
>
> - I've once read, that Kolab would be hard to package because it patches many 
> of the components it uses. However today the only patches remaining are for 
> Cyrus, right?
>   
there are a patch for php-imap too for annotations
> - The only authorative VCS used for Kolab is GIT? It would be useful to erase 
> all references to Hg and CVS to avoid confusion.
>
> - What is in the kolab-server git repository (compared to the "server" repo)?
>
> - Does Kolab work with Kontact from Debian testing? stable? 
> http://packages.debian.org/search?keywords=kontact
>
> - Have you heard of the GIT based coder review tool Gerrit[1]? I've given 
> talks about it recently and would love to help projects to use it. Make sure 
> to watch the 10 minuted video about it![2]
>
> [1] http://en.wikipedia.org/wiki/Gerrit_(software)
> [2] http://alblue.bandlem.com/2011/02/gerrit-git-review-with-jenkins-ci.html
>
> Thank you!
>
> Thomas Koch, http://www.koch.ro
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>   



From issues at kolab.org  Tue Jun 28 14:49:12 2011
From: issues at kolab.org (Emanuel Schuetze)
Date: Tue, 28 Jun 2011 12:49:12 +0000
Subject: [Kolab-devel] [issue4751] Event with start/end time "00:00" is not
	visible in	monthview and summary
In-Reply-To: <1309265352.95.0.0815452432885.issue4751@kolab.org>
Message-ID: <1309265352.95.0.0815452432885.issue4751@kolab.org>


Test with Kontact enterprise35 20110527.ef1b0d7:

1. Create all-day event E
2. Edit E: disable all-day checkbox 
-> E changes to an event with start/end time: from 00:00 to 00:00 (same day)

Observation:
a) E is visible in agenda view, from 00:00 to 24:00 h. 
b) E is NOT visible in month view.
c) E is NOT visible in Kontact's summary component.

Problem: (b) and (c)

Workaround for both problems: edit the end time of E manually from "00:00" to
"00:15". => Then, E is visible in (b) and (c).

Possible solutions:
i)  Change default end time from "00:00" to "00:15".
ii) Fix bug that E is also visible in (b) and (c) with end time "00:00".

Please estimate both solutions first!

----------
assignedto: allen
keyword: enterprise35, kde client, kkc
messages: 27990
nosy: allen, emanuel, laurent, ludwig, sergio, till, vkrause
priority: urgent
status: unread
title: Event with start/end time "00:00" is not visible in monthview and summary

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4751>
______________________________________



From issues at kolab.org  Tue Jun 28 19:27:35 2011
From: issues at kolab.org (Christoph Wickert)
Date: Tue, 28 Jun 2011 17:27:35 +0000
Subject: [Kolab-devel] [issue4752] Adress book confusion
In-Reply-To: <1309282055.71.0.126986041417.issue4752@kolab.org>
Message-ID: <1309282055.71.0.126986041417.issue4752@kolab.org>


There is some confusion about my address books: I have two address books, one is
'Contacts' the other is 'Kontakte'. The first is what Kontact uses, the other is
empty. From a file system perspective this is correct 'Kontakte' indeed is empty.

I wonder why I have this address book in first place. It was created November
20, 2010. At this time our server was still on 2.2.3. Could be it was Kontact
that created it while I was experimenting with akonadi, so I don't consider this
really a problem that needs to be treated here.

What needs fixing however is:
1. When I try to delete 'Kontakte' Horde returns "This address book cannot be
deleted".

2. 'Contacts' is not my address book but user/shared/Contacts. I cannot access
private address book.

3. I deleted the folder 'Kontakte' in Kontact. When I logged into Horde again, I
had a new address book called 'Contacts'. I can now access my private address
book, however I cannot distinguish private and shared address books. Paul
complained about this problem, too.

I guess (I cannot look it up any more), the folder 'Kontakte' had folder-type:
contact.default, so Horde refused to delete it. Maybe it was Kontact/akonadi
that incorrectly created a 2nd folder with this type although there already was
one. But I set 'Contacts' default for new contacts in Horde, at this point Horde
should have removed contact.default from 'Kontakte', right?

----------
assignedto: wrobel
keyword: webclient
messages: 27994
nosy: padams, thomas, wickert, wilde, wrobel
priority: bug
status: unread
title: Adress book confusion

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4752>
______________________________________



From greve at kolabsys.com  Tue Jun 28 20:15:36 2011
From: greve at kolabsys.com (Georg C. F. Greve)
Date: Tue, 28 Jun 2011 20:15:36 +0200
Subject: [Kolab-devel] [NEW KEP] KEP #8: Priority for events,
	matching iCalendar priority range
Message-ID: <8789711.EHG9fXPJyb@katana.lair>

Dear all,

Based on the conversations we had about priorities for events on kolab-
format@, I've begun drafting the following KEP which is awaiting your kind 
review and consideration:

	http://wiki.kolab.org/User:Greve/Drafts/KEP:8

All followup discussions should go to kolab-format at kolab.org.

Best regards,
Georg


-- 
Georg C. F. Greve
Chief Executive Officer

Kolab Systems AG
Z?rich, Switzerland

e: greve at kolabsys.com
t: +41 78 904 43 33
w: http://kolabsys.com

pgp: 86574ACA Georg C. F. Greve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 308 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110628/f476eaac/attachment.sig>

From vanmeeuwen at kolabsys.com  Tue Jun 28 21:32:42 2011
From: vanmeeuwen at kolabsys.com (Jeroen van Meeuwen (Kolab Systems))
Date: Tue, 28 Jun 2011 20:32:42 +0100
Subject: [Kolab-devel] Debian or Ubuntu repository
In-Reply-To: <000601cc2f7c$475959f0$d60c0dd0$@gnaa.net>
References: <000601cc2f7c$475959f0$d60c0dd0$@gnaa.net>
Message-ID: <201106282032.43024.vanmeeuwen@kolabsys.com>

Geoff Nordli wrote:
> Hi.
> 
> The OpenPKG format works OK, but my goal is to automate the installations
> via Puppet and provide easier updates.
> 

Hi Geoff,

one of my many goals is to work towards a Puppet module for Kolab. If you have 
ideas I'd be interested in hearing them!

For what I'm thinking, I'm pretty much locked in on Puppet's storeconfig 
features (exported resources) and extension functions to facter and the Puppet 
master (discovery).

Kind regards,

Jeroen van Meeuwen

-- 
Senior Engineer, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08



From wickert at kolabsys.com  Wed Jun 29 00:19:03 2011
From: wickert at kolabsys.com (Christoph Wickert)
Date: Wed, 29 Jun 2011 00:19:03 +0200
Subject: [Kolab-devel] small questions
In-Reply-To: <201106281045.13201.thomas@koch.ro>
References: <201106281045.13201.thomas@koch.ro>
Message-ID: <201106290019.07089.wickert@kolabsys.com>

On Tuesday 28 June 2011 10:45:13 Thomas Koch wrote:
> Hi,
> 
> - I've once read, that Kolab would be hard to package because it patches
> many of the components it uses. However today the only patches remaining
> are for Cyrus, right?

Nope, php as well, see http://git.kolab.org/server/tree/php/patches
 
> - The only authorative VCS used for Kolab is GIT?

Yes

> It would be useful to erase all references to Hg and CVS to avoid confusion.

What references? I think the repos themselves should still be around to 
preserver the history. CVS contains more than only the 'server' repo, so the 
only thing that could be deleted is HG.

> - What is in the kolab-server git repository (compared to the "server"
> repo)?

kolab-server looks looks misconfiguration to me.

> - Does Kolab work with Kontact from Debian testing? stable?
> http://packages.debian.org/search?keywords=kontact

I am using 4.4.11.1 (same version as in Debian testing) on Fedora and it works 
fine. Previous versions worked fine, too, but around 4.4.10 there were some 
problems when Kontact was used not in KDE and akonadi was started on demand 
rather than on login.

> - Have you heard of the GIT based coder review tool Gerrit[1]? 

Yes, I we would like to implement it in long term, but just didn't find the 
time yet.

Regards,
Christoph

-- 
Christoph Wickert
Senior Engineer

Kolab Systems AG
Z?rich, Switzerland

e: wickert at kolabsys.com
t: +49 251 871 369 77
w: http://kolabsys.com

pgp: 85DACC63 Christoph Wickert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110629/f70de21e/attachment.sig>

From wickert at kolabsys.com  Wed Jun 29 00:21:47 2011
From: wickert at kolabsys.com (Christoph Wickert)
Date: Wed, 29 Jun 2011 00:21:47 +0200
Subject: [Kolab-devel] Kontact E5 questions
In-Reply-To: <008e01cc30e7$8cdeebe0$a69cc3a0$@gnaa.net>
References: <018601cc305e$1a00a250$4e01e6f0$@gnaa.net>
	<201106221034.29811.bernhard@intevation.de>
	<008e01cc30e7$8cdeebe0$a69cc3a0$@gnaa.net>
Message-ID: <201106290021.48061.wickert@kolabsys.com>

On Wednesday 22 June 2011 16:20:34 Geoff Nordli wrote:

> Another question, is there a way to remove the "local folders" options so
> people only see the Kolab Server data stores?

I *guess* you can remove the akonadi-resource for local folders, but I'm not 
sure if "Local Folders" will disappear. I don't think it is a wise decision 
because you need some folders (Drafts, Trash, ...) when working offline.

Regards,
Christoph

-- 
Christoph Wickert
Senior Engineer

Kolab Systems AG
Z?rich, Switzerland

e: wickert at kolabsys.com
t: +49 251 871 369 77
w: http://kolabsys.com

pgp: 85DACC63 Christoph Wickert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110629/71063691/attachment.sig>

From geoffn at gnaa.net  Wed Jun 29 05:29:04 2011
From: geoffn at gnaa.net (Geoff Nordli)
Date: Tue, 28 Jun 2011 20:29:04 -0700
Subject: [Kolab-devel] Kontact E5 questions
In-Reply-To: <201106290021.48061.wickert@kolabsys.com>
References: <018601cc305e$1a00a250$4e01e6f0$@gnaa.net>	<201106221034.29811.bernhard@intevation.de>	<008e01cc30e7$8cdeebe0$a69cc3a0$@gnaa.net>
	<201106290021.48061.wickert@kolabsys.com>
Message-ID: <022d01cc360c$b21e9d40$165bd7c0$@gnaa.net>

>From: Christoph Wickert
>Sent: Tuesday, June 28, 2011 3:22 PM
>
>On Wednesday 22 June 2011 16:20:34 Geoff Nordli wrote:
>
>> Another question, is there a way to remove the "local folders" options
>> so people only see the Kolab Server data stores?
>
>I *guess* you can remove the akonadi-resource for local folders, but I'm
not sure
>if "Local Folders" will disappear. I don't think it is a wise decision
because you
>need some folders (Drafts, Trash, ...) when working offline.
>

Hi Christoph.

That makes perfect sense.

Thanks,

Geoff 



From geoffn at gnaa.net  Wed Jun 29 05:48:47 2011
From: geoffn at gnaa.net (Geoff Nordli)
Date: Tue, 28 Jun 2011 20:48:47 -0700
Subject: [Kolab-devel] Kontact E5 client bug (event acceptance doesn't show
	properly)
Message-ID: <023501cc360f$737c5840$5a7508c0$@gnaa.net>

When an attendee "accepts" an invitation to attend an event, you receive an
email in the inbox indicating their acceptance, but the acceptance data
doesn't show up on the event details area.  

 

It still shows the attendee's status as "needs action".

 

Let me know if you need more info around this.

 

Thanks,

 

Geoff 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110628/0646b719/attachment.html>

From geoffn at gnaa.net  Wed Jun 29 06:29:21 2011
From: geoffn at gnaa.net (Geoff Nordli)
Date: Tue, 28 Jun 2011 21:29:21 -0700
Subject: [Kolab-devel] Debian or Ubuntu repository
In-Reply-To: <201106282032.43024.vanmeeuwen@kolabsys.com>
References: <000601cc2f7c$475959f0$d60c0dd0$@gnaa.net>
	<201106282032.43024.vanmeeuwen@kolabsys.com>
Message-ID: <024901cc3615$1e170520$5a450f60$@gnaa.net>

>From: Jeroen van Meeuwen (Kolab Systems)
>Sent: Tuesday, June 28, 2011 12:33 PM
>
>Geoff Nordli wrote:
>> Hi.
>>
>> The OpenPKG format works OK, but my goal is to automate the
>> installations via Puppet and provide easier updates.
>>
>
>Hi Geoff,
>
>one of my many goals is to work towards a Puppet module for Kolab. If you
have
>ideas I'd be interested in hearing them!
>
>For what I'm thinking, I'm pretty much locked in on Puppet's storeconfig
features
>(exported resources) and extension functions to facter and the Puppet
master
>(discovery).
>
Hi 

I am not a puppet expert by any stretch.  I would look to the puppet mailing
list to get some feedback on what the best approach for Kolab packaging
would be.  

Drop me an email though if you need someone to help out with the testing of
those packages.  

Geoff 




From geoffn at gnaa.net  Wed Jun 29 06:42:00 2011
From: geoffn at gnaa.net (Geoff Nordli)
Date: Tue, 28 Jun 2011 21:42:00 -0700
Subject: [Kolab-devel] Kontact E5 client bug (event acceptance doesn't
	show	properly)
In-Reply-To: <023501cc360f$737c5840$5a7508c0$@gnaa.net>
References: <023501cc360f$737c5840$5a7508c0$@gnaa.net>
Message-ID: <025401cc3616$e2e99100$a8bcb300$@gnaa.net>

>From: Geoff Nordli
>Sent: Tuesday, June 28, 2011 8:49 PM
>
>When an attendee "accepts" an invitation to attend an event, you receive an
>email in the inbox indicating their acceptance, but the acceptance data
doesn't
>show up on the event details area.
>
>It still shows the attendee's status as "needs action".
>
>Let me know if you need more info around this.
>

OK, this doesn't look like a bug, but only a design decision to not
automatically register people's reply to meetings.

I found the spot where you can accept their response and have it update the
event listing.

Is there a way where you can auto update any responses?

Thanks,

Geoff 




From vanmeeuwen at kolabsys.com  Wed Jun 29 10:39:37 2011
From: vanmeeuwen at kolabsys.com (Jeroen van Meeuwen (Kolab Systems))
Date: Wed, 29 Jun 2011 09:39:37 +0100
Subject: [Kolab-devel] Debian or Ubuntu repository
In-Reply-To: <024901cc3615$1e170520$5a450f60$@gnaa.net>
References: <000601cc2f7c$475959f0$d60c0dd0$@gnaa.net>
	<201106282032.43024.vanmeeuwen@kolabsys.com>
	<024901cc3615$1e170520$5a450f60$@gnaa.net>
Message-ID: <201106290939.38411.vanmeeuwen@kolabsys.com>

Geoff Nordli wrote:
> Hi
> 
> I am not a puppet expert by any stretch.  I would look to the puppet
> mailing list to get some feedback on what the best approach for Kolab
> packaging would be.
> 
> Drop me an email though if you need someone to help out with the testing of
> those packages.
> 

I'm a fan of letting these things evolve as they go, actually, and so attached 
is the simple class I currently use for the kolab* parts of the Roundcube 
development environment [1].

Let's note the following;

- The reference implementation is Enterprise Linux 5,

- This has originally been created for another single specific Kolab 
deployment (in terms of architecture and topology), and has since then evolved 
little by little,

- The classes included and custom types used (that are not prefixed with 
'test90-') are from puppetmanaged.org, which I own, modules are at [2] and 
documentation (insert work in progress disclaimer here) is at [3].

Kind regards,

Jeroen van Meeuwen

[1] https://wiki.kolab.org/Roundcube_Development_Environment
[2] http://git.puppetmanaged.org
[3] http://www.puppetmanaged.org/documentation/

-- 
Senior Engineer, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08
-------------- next part --------------
class test90-kolab {
    class cyrus inherits test90-kolab {
        include test90-kolab::fqdncerts
        include test90-kolab::saslauthd

        file { "/etc/cyrus.conf":
            mode => 640,
            owner => root,
            group => mail,
            source => [
                    "puppet://$server/private/$environment/cyrus/cyrus.conf.$hostname",
                    "puppet://$server/private/$environment/cyrus/cyrus.conf"
                ],
            require => [
                    Package["cyrus-imapd"]
                ],
            notify => [
                    Service["cyrus-imapd"]
                ]
        }

        file { "/etc/imapd.annotations.conf":
            mode => 640,
            owner => "root",
            group => "mail",
            source => [
                    "puppet://$server/private/$environment/cyrus/imapd.annotations.conf"
                ],
            require => [
                    Package["cyrus-imapd"]
                ],
            notify => [
                    Service["cyrus-imapd"]
                ]
        }

        file { "/etc/imapd.conf":
            mode => 640,
            owner => "root",
            group => "mail",
            source => [
                    "puppet://$server/private/$environment/cyrus/imapd.conf.$hostname",
                    "puppet://$server/private/$environment/cyrus/imapd.conf"
                ],
            require => [
                    Package["cyrus-imapd"]
                ],
            notify => [
                    Service["cyrus-imapd"]
                ]
        }

        package { [
                "cyrus-imapd"
            ]:
            ensure => installed
        }

        service { "cyrus-imapd":
            ensure => running,
            enable => true,
            require => [
                    File["/etc/cyrus.conf"],
                    File["/etc/imapd.conf"],
                    File["/etc/imapd.annotations.conf"],
                    Package["cyrus-imapd"]
                ]
        }

        class backend inherits cyrus {
            include test90-kolab::postfix::backend

            munin::plugin { [
                    "cpuload_imapd",
                ]:
                enable => true,
                source => true,
                plugin_name => "cpuload_"
            }

            munin::plugin { [
                    "multips_memory"
                ]:
                enable => true,
                conf => "puppet://$server/private/$environment/munin/plugin-conf.d/multips_memory.backend",
                conf_name => "multips_memory"
            }

            package { [
                    "kolabd"
                ]:
                ensure => installed
            }
        }

        class frontend inherits cyrus {

            File["/etc/cyrus.conf"] {
                source => "puppet://$server/private/$environment/cyrus/cyrus.conf.frontend"
            }

            munin::plugin { [
                    "cpuload_mupdate",
                    "cpuload_proxyd"
                ]:
                enable => true,
                source => true,
                plugin_name => "cpuload_"
            }

            munin::plugin { [
                    "multips_memory"
                ]:
                enable => true,
                source => true,
                conf => "puppet://$server/private/$environment/munin/plugin-conf.d/multips_memory.frontend",
                conf_name => "multips_memory"
            }

        }

        class mupdate inherits frontend {
            File["/etc/cyrus.conf"] {
                source => "puppet://$server/private/$environment/cyrus/cyrus.conf.mupdate"
            }

            File["/etc/imapd.conf"] {
                source => "puppet://$server/private/$environment/cyrus/imapd.conf.mupdate"
            }

        }
    }

    ##
    ##
    ##
    ##
    class int-mx inherits postfix {
        File["/etc/postfix/ldap/"] {
            recurse => true,
            purge => true,
            force => true,
            source => "puppet://$server/private/$environment/postfix/ldap.int-mx/"
        }

        file { "/etc/amavisd/amavisd.conf":
            mode => 644,
            owner => "root",
            group => "root",
            source => "puppet://$server/private/$environment/amavisd/amavisd.conf",
            require => Package["amavisd-new"],
            notify => Service["amavisd"]
        }

        file { "/etc/clamd.d/amavisd.conf":
            mode => 644,
            owner => "root",
            group => "root",
            source => "puppet://$server/private/$environment/amavisd/clamd.conf",
            require => Package["clamav"],
            notify => Service["clamd.amavisd"]
        }

        file { "/var/run/clamd.amavisd/":
            ensure => directory,
            owner => "amavis",
            group => "amavis",
            mode => 750,
            require => [
                    Package["amavisd-new"],
                    Package["clamav"]
                ]
        }

        package { [
                "amavisd-new",
                "clamav"
            ]:
            ensure => installed
        }

        service { "amavisd":
            ensure => running,
            enable => true,
            require => [
                    File["/etc/amavisd/amavisd.conf"],
                    Package["amavisd-new"]
                ]
        }

        service { "clamd.amavisd":
            ensure => running,
            enable => true,
            require => [
                    File["/etc/clamd.d/amavisd.conf"],
                    File["/var/run/clamd.amavisd/"],
                    Package["clamav"]
                ]
        }

    }

    class postfix inherits test90-kolab {
        include test90-kolab::fqdncerts
        include test90-kolab::saslauthd

        file { "/etc/kolab/kolab_smtpdpolicy.conf":
            mode => 644,
            owner => "root",
            group => "kolab-n",
            source => [
                    "puppet://$server/private/$environment/kolab/kolab_smtpdpolicy.conf.$hostname",
                    "puppet://$server/private/$environment/kolab/kolab_smtpdpolicy.conf"
                ],
            require => Package["kolabd-server"],
            notify => Service["postfix"]
        }

        file { "/etc/kolab/kolabfilter.conf":
            mode => 644,
            owner => "root",
            group => "kolab-n",
            source => [
                    "puppet://$server/private/$environment/kolab/kolabfilter.conf.$hostname",
                    "puppet://$server/private/$environment/kolab/kolabfilter.conf"
                ],
            require => Package["kolabd-server"],
            notify => Service["postfix"]
        }

        file { "/etc/postfix/main.cf":
            mode => 644,
            owner => "root",
            group => "root",
            source => [
                    "puppet://$server/private/$environment/postfix/main.cf.$hostname",
                    "puppet://$server/private/$environment/postfix/main.cf"
                ],
            notify => Service["postfix"]
        }

        file { "/etc/postfix/master.cf":
            mode => 644,
            owner => "root",
            group => "root",
            source => [
                    "puppet://$server/private/$environment/postfix/master.cf.$hostname",
                    "puppet://$server/private/$environment/postfix/master.cf"
                ],
            notify => Service["postfix"]
        }

        file { "/etc/postfix/ldap/":
            owner => "root",
            group => "root",
            recurse => true,
            force => true,
            ensure => directory,
            source => [
                    "puppet://$server/private/$environment/postfix/ldap.$hostname/",
                    "puppet://$server/private/$environment/postfix/ldap/"
                ],
            notify => Service["postfix"]
        }

        munin::plugin { [
                "postfix_mailqueue",
                "postfix_mailstats",
                "postfix_mailvolume"
            ]:
            enable => true
        }

        munin::plugin { [
                "cpuload_postfix"
            ]:
            enable => true,
            plugin_name => "cpuload_",
            conf => "puppet://$server/private/$environment/munin/plugin-conf.d/cpuload_postfix",
            conf_name => "cpuload_postfix"
        }

        package { "sendmail":
            ensure => absent,
            require => Package["postfix"]
        }

        package { [
                "kolabd-server",
                "postfix"
            ]:
            ensure => installed
        }

        service { "postfix":
            ensure => running,
            enable => true,
            require => [
                    File["/etc/kolab/kolab_smtpdpolicy.conf"],
                    File["/etc/postfix/main.cf"],
                    File["/etc/postfix/master.cf"],
                    File["/etc/postfix/ldap/"],
                    Package["kolabd-server"],
                    Package["postfix"]
                ]
        }

        class backend inherits postfix {
            File["/etc/postfix/ldap/"] {
                recurse => true,
                purge => true,
                force => true,
                source => "puppet://$server/private/$environment/postfix/ldap.backend/"
            }
        }
    }

    class webserver inherits test90-kolab {
        include webserver

        include test90-munin::webserver

        file { "/etc/horde/":
            owner => "root",
            group => "apache",
            recurse => true,
            source => [
                    "puppet://$server/private/$environment/files/horde/"
                ]
        }

        file { "/etc/php.ini":
            mode => 644,
            owner => "root",
            group => "root",
            source => [
                    "puppet://$server/private/$environment/php/php.ini.$hostname",
                    "puppet://$server/private/$environment/php/php.ini"
                ],
            notify => Service["httpd"]
        }

        file { "/etc/php.d/":
            mode => 644,
            owner => "root",
            group => "root",
            recurse => true,
            purge => false,
            source => [
                    "puppet://$server/private/$environment/php/php.d.$hostname/",
                    "puppet://$server/private/$environment/php/php.d/"
                ],
            require => [
                    Package["php-pecl-apc"],
                    Package["php-pecl-memcache"]
                ],
            notify => Service["httpd"]
        }

        file { "/etc/roundcubemail/":
            owner => "root",
            group => "apache",
            recurse => true,
            purge => true,
            force => true,
            source => [
                    "puppet://$server/private/$environment/files/roundcubemail/"
                ]
        }

        package { [
                "php-pecl-apc",
                "php-pecl-memcache"
            ]:
            ensure => installed
        }

        package { [
                "kolab-fbview",
                "roundcubemail",
                "roundcubemail-kolab"
            ]:
            ensure => latest
        }

        webserver::module::enable { [
                "mod_ssl",
                "php"
            ]:
        }

        webserver::virtualhost { [
                "ko24rc06.klab.cc"
            ]:
            enable => true
        }

    }

    ##
    ## Shortcut classes to be included by other classes.
    ##

    class fqdncerts {
        file { "/etc/pki/tls/certs/kolab_ca.crt":
            mode => 644,
            owner => "root",
            group => "mail",
            source => "puppet://$server/private/$environment/files/ssl/certs/ca.crt"
        }

        file { "/etc/pki/tls/certs/$fqdn.crt":
            mode => 644,
            owner => "root",
            group => "mail",
            source => "puppet://$server/private/$environment/files/ssl/certs/$fqdn.crt"
        }

        file { "/etc/pki/tls/private/$fqdn.key":
            mode => 640,
            owner => "root",
            group => "mail",
            source => "puppet://$server/private/$environment/files/ssl/certs/$fqdn.key"
        }
    }

    class saslauthd {
        file { "/etc/saslauthd.conf":
            mode => 640,
            owner => "root",
            group => "root",
            source => [
                    "puppet://$server/private/$environment/files/saslauthd.conf.$hostname",
                    "puppet://$server/private/$environment/files/saslauthd.conf"
                ],
            require => [
                    Package["cyrus-sasl"],
                    Package["cyrus-sasl-ldap"]
                ],
            notify => Service["saslauthd"]
        }

        file { "/etc/sysconfig/saslauthd":
            mode => 640,
            owner => "root",
            group => "root",
            source => [
                    "puppet://$server/private/$environment/files/saslauthd.sysconfig.$hostname",
                    "puppet://$server/private/$environment/files/saslauthd.sysconfig"
                ],
            require => [
                    Package["cyrus-sasl"],
                    Package["cyrus-sasl-ldap"]
                ],
            notify => Service["saslauthd"]
        }

        package { [
                "cyrus-sasl",
                "cyrus-sasl-ldap"
            ]:
            ensure => installed
        }

        service { "saslauthd":
            ensure => running,
            enable => true,
            require => [
                    File["/etc/saslauthd.conf"],
                    File["/etc/sysconfig/saslauthd"],
                    Package["cyrus-sasl"],
                    Package["cyrus-sasl-ldap"]
                ]
        }

    }
}

From issues at kolab.org  Wed Jun 29 12:06:37 2011
From: issues at kolab.org (Christoph Wickert)
Date: Wed, 29 Jun 2011 10:06:37 +0000
Subject: [Kolab-devel] [issue4753] Cannot destinguish two address book with
	the same name in	the webclient
In-Reply-To: <1309341997.3.0.183693165438.issue4753@kolab.org>
Message-ID: <1309341997.3.0.183693165438.issue4753@kolab.org>


As mentioned in issue4752:

My private address book in the Horde webclient is called 'Contacts'. Another
user also shares his address book with me and it is called 'Contacts', too. In
the webclient all address books are shown as 'Contacts', so there is no way to
distinguish them.

For the address book itself there actually is a little trick: In the list of
address you can hover the mouse over the icon of an address book and look at the
status bar of the webbrowser to see the URL. But for the settings page this does
not work.

----------
assignedto: wrobel
keyword: webclient
messages: 28002
nosy: padams, thomas, wickert, wilde, wrobel
priority: bug
related: Adress book confusion
status: unread
title: Cannot destinguish two address book with the same name in the webclient

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4753>
______________________________________



From vanmeeuwen at kolabsys.com  Wed Jun 29 19:20:07 2011
From: vanmeeuwen at kolabsys.com (Jeroen van Meeuwen (Kolab Systems))
Date: Wed, 29 Jun 2011 18:20:07 +0100
Subject: [Kolab-devel] Kolab commit messages (was: list.php)
In-Reply-To: <20110623112115.Horde._BFFPQ6_GnlOAwWLoxMTcZA@wrbl.de>
References: <201106161129.p5GBToOp007724@app01.kolabsys.com>
	<20110623112115.Horde._BFFPQ6_GnlOAwWLoxMTcZA@wrbl.de>
Message-ID: <201106291820.08895.vanmeeuwen@kolabsys.com>

Gunnar Wrobel wrote:
> Hi!
> 
> Would it be possible to somehow add the name of the source repository
> in here? I know it is in the mail headers but it would be convenient
> to immediately see from the mail body which of the Kolab repositories
> the commit belongs to.
> 

Hi Gunnar,

rest assured I've not forgotten and I'm not ignoring you, it's just that I 
haven't gotten around to actually implementing it.

Apologies for the delay!

Kind regards,

Jeroen van Meeuwen

-- 
Senior Engineer, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08



From vanmeeuwen at kolabsys.com  Wed Jun 29 20:29:46 2011
From: vanmeeuwen at kolabsys.com (Jeroen van Meeuwen (Kolab Systems))
Date: Wed, 29 Jun 2011 19:29:46 +0100
Subject: [Kolab-devel] Renaming LDAP attribute and implementing functionality
Message-ID: <201106291929.47673.vanmeeuwen@kolabsys.com>

Hi there,

I would like to propose renaming the following LDAP attribute:

- kolabAllowSMTPFrom

to:

- kolabAllowSMTPSender

in order to make it more consistent with kolabAllowSMTPRecipient then the old 
name, kolabAllowSMTPFrom, used to be.

I'm not aware of 

Both LDAP attributes should, subsequently, get a new description as well;

For kolabAllowSMTPRecipient:

# Describes the allowed or disallowed smtp recipient addresses for mail sent
# by the user associated with the LDAP object this attribute is associated 
with.
#
# If this attribute is not set for a user or distribution group,
# no Kolab recipient access policy is applied.

For kolabAllowSMTPSender:

# Describes the allowed or disallowed smtp envelope sender addresses used for
# the recipient this attribute is associated with.
#
# If this attribute is not set for a user or distribution group,
# no Kolab sender access policy is applied.

Furthermore, as I'm unaware of any current program using it, I would like to 
actually implement kolabAllowSMTPSender to provide the functionality stated in 
the aforementioned description.

I would then also like to add the attributes to the list of allowed attributes 
for the following object classes:

- kolabSharedFolder
- kolabGroupOfUniqueNames
- kolabGroupOfUrls

Afterwards, I'd like to implement a conversion for both attributes, to have 
them both allow:

- Regular Expressions,
- Distinguished Names,
- Search Queries.

I would appreciate your thoughts.

Kind regards,

Jeroen van Meeuwen

-- 
Senior Engineer, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08



From issues at kolab.org  Thu Jun 30 15:39:53 2011
From: issues at kolab.org (Sascha Wilde)
Date: Thu, 30 Jun 2011 13:39:53 +0000
Subject: [Kolab-devel] =?utf-8?q?=5Bissue4754=5D_Kolab_Server_providing_Zp?=
 =?utf-8?q?ush_services_must_adhere_to_=C2=A76d=29_of_AGPL?=
In-Reply-To: <1309441193.86.0.70804321346.issue4754@kolab.org>
Message-ID: <1309441193.86.0.70804321346.issue4754@kolab.org>


Kolab Server includes Z-Push which is licensed under AGPL.  A standard
Kolab Server installation provides access to the Z-Push service by
default to all users.  So the provider of the Kolab Server is --
according to section 6 d) of the AGPL -- obliged to:

    [...] offer equivalent access to the Corresponding Source in the same
    way through the same place at no further charge. [...]

Unfortunately Kolab Server currently does not provide any mechanism to
satisfy this requirement.

I would suggest:

1. As part or dependency of the z-push package put the corresponding
   source package somewhere below /kolab/var/kolab/www/ (or whatever
   the Kolab Server's http document root may be on the targed
   distribution).

2. Put at
   https://kolab-server.example.com/Microsoft-Server-ActiveSync/
   (/kolab/var/kolab/www/z-push/index.php) a link which allows to
   download the source package.  The page there already provides
   additional information on z-push and a link to the AGPL, so this
   seems a very appropriate place.

3. Optionally put an additionally download link in the web-admin
   interface.

(One might argue that "equivalent access" would really mean to offer
the source via active sync, but I'd say that would be just olympic
nitpicking -- not to say I'm not found of that discipline...)

Btw: the license information in the z-push RPM of the Kolab OpenPKG
distribution is wrong:

  $ /kolab/bin/openpkg rpm -qi z-push | grep License
  License:  GPLv2

----------
assignedto: wickert
keyword: zpush
messages: 28006
nosy: alain.abbas, thomas, wickert, wilde
priority: critical
status: unread
title: Kolab Server providing Zpush services must adhere to ?6d) of AGPL

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue4754>
______________________________________



From alain.abbas at libertech.fr  Thu Jun 30 15:58:08 2011
From: alain.abbas at libertech.fr (Alain Abbas)
Date: Thu, 30 Jun 2011 15:58:08 +0200
Subject: [Kolab-devel]
 =?utf-8?q?=5Bissue4754=5D_Kolab_Server_providing_Zp?=
 =?utf-8?q?ush_services_must_adhere_to_=C2=A76d=29_of_AGPL?=
In-Reply-To: <1309441193.86.0.70804321346.issue4754@kolab.org>
References: <1309441193.86.0.70804321346.issue4754@kolab.org>
Message-ID: <4E0C80F0.8040003@libertech.fr>

An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110630/f3f61d23/attachment.html>

From mephisto at gmx.net  Fri Jun 24 13:12:30 2011
From: mephisto at gmx.net (Heiner Markert)
Date: Fri, 24 Jun 2011 11:12:30 -0000
Subject: [Kolab-devel] Kontact E5 questions
In-Reply-To: <008e01cc30e7$8cdeebe0$a69cc3a0$@gnaa.net>
References: <018601cc305e$1a00a250$4e01e6f0$@gnaa.net>
	<201106221034.29811.bernhard@intevation.de>
	<008e01cc30e7$8cdeebe0$a69cc3a0$@gnaa.net>
Message-ID: <201106241312.25535.mephisto@gmx.net>

Am Mittwoch, 22. Juni 2011, 16:20:34 schrieb Geoff Nordli:
> >Hi Geoff,
> >
> >Am Dienstag, 21. Juni 2011 23:56:40 schrieb Geoff Nordli:
> >> I installed E5 again on Windows 7 64bit to see what functionality
> >> currently exists.  As a bonus the client looks really pretty.  J
> >
> >thanks for trying. I assume you've tried RouchCut Version
> >Kolab-E5RC-2011-06-15-19-24.exe as linked from
> >http://wiki.kolab.org/Kontact_for_Windows_(Enterprise-5)
> 
> Yes, that is the version I installed.
> 

Hi,

I also installed Kontact E5, however the 32 Bit version on Windows XP. I 
noticed some additional issues:
- shutting down the client (full shutdown in the file menu) does not work.
- closing and reopening the client usually does not work, the windows session 
has to be closed in order to allow for a restart of the application.
- Notes are now handled by the "kjots" part. However, notes taken with that 
component can not be seen on Linux/KDE clients that use the old knotes 
components. Notes taken in Linux/KDE with knotes do appear as raw rich text in 
windows, all tags are displayed and no formatting is done. Very annoying, as 
all lists get completely unreadable.
The last points regarding the notes also happens with an earlier KDEPIM beta 
version I tested on ubuntu linux a few weeks ago.

Are any of these issues known?

Best regards
Heiner