From kolab-issues at intevation.de  Sat May  2 16:23:22 2009
From: kolab-issues at intevation.de (Alar)
Date: Sat, 02 May 2009 14:23:22 +0000
Subject: [Kolab-devel] [issue3602] apache config error
Message-ID: <1241274202.78.0.261403488688.issue3602@intevation.de>


New submission from Alar <alar.sing at err.ee>:

In httpd.conf.template.in there is line
# Redirect from the old Kolab web client location (Kolab-Server-2.2.0)
# to the new one (Kolab-Server >= 2.2.1)
Redirect /horde /client

Put apache 2.0 Redirect needs full url for redirecting
http://httpd.apache.org/docs/2.0/mod/mod_alias.html#redirect

So to get it working on opensuse 10.3 this redirect line must be
Redirect /horde http://@@@fqdnhostname@@@/client 
or apache does not start

----------
messages: 19983
nosy: arclyde
priority: critical
status: unread
title: apache config error
topic: server, web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3602>
___________________________________________________


From kolab-issues at intevation.de  Sat May  2 17:37:44 2009
From: kolab-issues at intevation.de (Alar)
Date: Sat, 02 May 2009 15:37:44 +0000
Subject: [Kolab-devel] [issue3603] kolab-webclient turba global addressbook
Message-ID: <1241278663.9.0.455513618804.issue3603@intevation.de>


New submission from Alar <alar.sing at err.ee>:

kolab-webclient from cvs does not have global addressbook selected for
displaying and global addressbook is selected for default importing or adding
contact.

----------
messages: 19984
nosy: arclyde
priority: bug
status: unread
title: kolab-webclient turba global addressbook
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3603>
___________________________________________________


From kolab-issues at intevation.de  Sat May  2 17:44:10 2009
From: kolab-issues at intevation.de (Alar)
Date: Sat, 02 May 2009 15:44:10 +0000
Subject: [Kolab-devel] [issue3604] all templates to not have RUNONCHANGE
Message-ID: <1241279050.09.0.273678330807.issue3604@intevation.de>


New submission from Alar <alar.sing at err.ee>:

Ldap related templates to not have RUNONCHANGE wich makes it harder to port
kolab to opensuse

Templates that do not have RUNONCHANGE
ldap.conf.template
slapd.access.template
slapd.conf.template
slapd.replicas.template

----------
messages: 19985
nosy: arclyde
priority: bug
status: unread
title: all templates to not have RUNONCHANGE
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3604>
___________________________________________________


From kolab-issues at intevation.de  Mon May  4 16:25:30 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Mon, 04 May 2009 14:25:30 +0000
Subject: [Kolab-devel] [issue3605] System tray icon displayed,
	even when there is no unread mail.
Message-ID: <1241447130.79.0.411568215198.issue3605@intevation.de>


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

enterprise35 kdepim 20090430.961755

Test:
1. Configure: KMail->View->System tray
   Set view icon on the system tray, if and only if there are unread/new mails.
2. Mark one mail as unread.
3. Close kontact.
=> The system tray icon is displayed with a one.
4. Click on the system tray icon of Kontact.
5. Read the unread mail.
6. Close kontact.
=> The system tray icon is displayed without an unread mail.

----------
assignedto: allen
messages: 20001
nosy: allen, bh, ludwig
priority: minor bug
status: unread
title: System tray icon displayed, even when there is no unread mail.
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3605>
___________________________________________________


From kolab-issues at intevation.de  Tue May  5 15:07:22 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 05 May 2009 13:07:22 +0000
Subject: [Kolab-devel] [issue3606] Some common folder properties are missing
Message-ID: <1241528842.49.0.951534449567.issue3606@intevation.de>


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

enterprise35 20090430.961755

Test:
1. Switch to kmail.
2. Deactivate the configuration: "Hide groupware folders"
3. Look at the common properties of a default calendar folder. 

The options: name, use custom icon, folder contents, generate freebusy.. and
block free/busy... are missing.

A second non-default calendar folder has these options.
I expect the "folder contents" of a groupware folder to be read-only and the
rest of the options should be normal.

----------
assignedto: allen
messages: 20022
nosy: allen, bernhard, bh, ludwig
priority: urgent
status: unread
title: Some common folder properties are missing
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3606>
___________________________________________________


From kolab-issues at intevation.de  Tue May  5 15:41:12 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 05 May 2009 13:41:12 +0000
Subject: [Kolab-devel] [issue3607] composer hangs after closing kontact
Message-ID: <1241530871.83.0.326529924038.issue3607@intevation.de>


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

tested with enterprise35 20090430.961755

Test:
1. Start kontact and switch to the mail component.
2. Start to create two(!) new mails and enter a test line to each one.
=> Two composer windows are open.
3. Close kontact.
4. Start kontact.
=> The kwallet password dialog, kontact and two composer appear.
5. Click on the [x] of the grey kontact.
6. Enter the kwallet password.
=> kontact closes, but not the two composers.
The composers hang. After killing the composers, it is not possible to start
kontact again.

----------
assignedto: allen
messages: 20027
nosy: allen, bh, ludwig
priority: urgent
status: unread
title: composer hangs after closing kontact
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3607>
___________________________________________________


From alar.sing at err.ee  Tue May  5 16:10:34 2009
From: alar.sing at err.ee (Alar Sing)
Date: Tue, 05 May 2009 17:10:34 +0300
Subject: [Kolab-devel] opensuse native kolabmailboxfilter php segfault
Message-ID: <4A0048DA.6040702@err.ee>

Hello,

I have problem with kolabmailboxfilter in opensuse native kolab 
installation. Attached log's are from postfix and kolab filter
This segfault ocures when user try's sends invite to resurce account 
that is configured to auto accept invites. After getting bounce message 
saying that php has died with singal 11 user gets accpet from resource.


And segfault messega from syslog
May  5 14:10:59 linux kernel: php5[4305]: segfault at 4c503d48 ip 
081b0473 sp bfed4d7c error 4 in php5[8048000+23d000]

php version is 5.2.9 in opensuse

What could be causing this?



-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: filter.log
Url: http://kolab.org/pipermail/kolab-devel/attachments/20090505/b08976f0/filter.txt
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: mail.log
Url: http://kolab.org/pipermail/kolab-devel/attachments/20090505/b08976f0/mail.txt

From ml at radoeka.nl  Wed May  6 08:21:35 2009
From: ml at radoeka.nl (Richard Bos)
Date: Wed, 6 May 2009 08:21:35 +0200
Subject: [Kolab-devel] kolab on openSUSE natively is a little bit back
In-Reply-To: <200905060504.03731.martin.zboril@gmail.com>
References: <200905060504.03731.martin.zboril@gmail.com>
Message-ID: <20090506062135.GA85121@xs4all.nl>

On Wed, May 06, 2009 at 05:04:02AM +0200, Martin Zbo??il wrote:
> Good morning gentlemen,
>  
> Recently I tried both OpenSuSE 11.1 and Mandriva 2009.1, in both I was trying
> the most recent kolab version with same results in both distros, the problem I found, after
> almost 8 hours of troubleshooting, is actually in slapd.conf.template  on lines 59 & 60
> 
> slapd.conf.template line 59
> idletimeout     80 # The value can be increased if some clients develop problems.
>                    # Please report to kolab-devel at kolab.org if you encounter such a client.
> 
> slapd parses comments only if a line with commentary *starts* with # sign.

What problems did you see?  Is it possible to reproduce.  The same should
also be visible on the openpkg version, as it uses the same template.
It might be good to open an issue in the kolab tracker at
https://www.intevation.de/roundup/kolab/  This most often ensures a fix.

-- 
Richard


From ml at radoeka.nl  Wed May  6 08:42:34 2009
From: ml at radoeka.nl (Richard Bos)
Date: Wed, 6 May 2009 08:42:34 +0200
Subject: [Kolab-devel] kolab on openSUSE natively is a little bit back
In-Reply-To: <20090506062135.GA85121@xs4all.nl>
References: <200905060504.03731.martin.zboril@gmail.com>
	<20090506062135.GA85121@xs4all.nl>
Message-ID: <20090506064234.GA87119@xs4all.nl>

On Wed, May 06, 2009 at 08:21:35AM +0200, Richard Bos wrote:
> On Wed, May 06, 2009 at 05:04:02AM +0200, Martin Zbo??il wrote:
> > Good morning gentlemen,
> >  
> > Recently I tried both OpenSuSE 11.1 and Mandriva 2009.1, in both I was trying
> > the most recent kolab version with same results in both distros, the problem I found, after
> > almost 8 hours of troubleshooting, is actually in slapd.conf.template  on lines 59 & 60
> > 
> > slapd.conf.template line 59
> > idletimeout     80 # The value can be increased if some clients develop problems.
> >                    # Please report to kolab-devel at kolab.org if you encounter such a client.
> > 
> > slapd parses comments only if a line with commentary *starts* with # sign.
> 
> What problems did you see?  Is it possible to reproduce.  The same should
> also be visible on the openpkg version, as it uses the same template.
> It might be good to open an issue in the kolab tracker at
> https://www.intevation.de/roundup/kolab/  This most often ensures a fix.

What version (of kolab) did you use.  The current slapd template contains
     62 # The idletimeout can be increased if some clients develop problems.
     63 # Please report to kolab-devel at kolab.org if you encounter such a client.
     64 idletimeout     300

There are no lines that contain a "#" after an assignment.  See,
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/templates/slapd.conf.template.in?rev=1.26&content-type=text/vnd.viewcvs-markup

-- 
Richard


From kolab-issues at intevation.de  Wed May  6 15:43:20 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 06 May 2009 13:43:20 +0000
Subject: [Kolab-devel] [issue3608] Lastname of an attendee is missing.
Message-ID: <1241617400.25.0.831839207941.issue3608@intevation.de>


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

enterprise35 20090430.961755

Test:
1. Configure the name of the standard identity to  Lastname, Firstname
2. Start to create a new event.
3. Look at the attendee tab.
=> The organisator attendee is just Firstname <mailaddress>
I expect that the lastname is also displayed in this context.

----------
assignedto: allen
messages: 20043
nosy: allen, bh, ludwig
priority: urgent
status: unread
title: Lastname of an attendee is missing.
topic: enterprise35, kde client, kkc
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3608>
___________________________________________________


From ml at radoeka.nl  Wed May  6 19:39:44 2009
From: ml at radoeka.nl (Richard Bos)
Date: Wed, 6 May 2009 19:39:44 +0200
Subject: [Kolab-devel] opensuse native kolabmailboxfilter php segfault
In-Reply-To: <4A0048DA.6040702@err.ee>
References: <4A0048DA.6040702@err.ee>
Message-ID: <200905061939.44712.ml@radoeka.nl>

Hi Alar,

Op dinsdag 05 mei 2009 16:10:34 schreef Alar Sing:
> Hello,
>
> I have problem with kolabmailboxfilter in opensuse native kolab
> installation. Attached logs are from postfix and kolab filter
> This segfault occures when user tries to sent an invite to a resource 
account
> that is configured to auto accept invites. After getting a bounce message
> saying that php has died with signal 11 user gets accept from resource.
>
> And segfault messega from syslog
> May  5 14:10:59 linux kernel: php5[4305]: segfault at 4c503d48 ip
> 081b0473 sp bfed4d7c error 4 in php5[8048000+23d000]
>
> php version is 5.2.9 in opensuse
>
> What could be causing this?

No Idea ;)  The line to look at in your original posting is this one:
May  5 14:10:59 linux postfix/pipe[4304]: 3951113235C: to=<resource at domain>, 
relay=kolabmailboxfilter, delay=1.6, delays=0.09/0.01/0/1.5, dsn=5.3.0, 
status=bounced (Command died with signal 11: "/usr/bin/php5")
(just for others, so they don't need to look carefully to the log files).

The To address looks strange to me: "resource at domain".  Did you edit it?
Would it be possible to add printf statements, to obtain more information in 
the log file(s)?  It's a pity that the timestamp does not include 
milliseconds, that would make it easier to interleave the filter.log and 
mail.log.  Perhaps it is possible with the printf statements to find the line, 
that is the reason for the segmentation fault....

Oh, and at openSUSE we use kolab-filter-0.1.5

-- 
Richard


From alar.sing at err.ee  Wed May  6 19:47:08 2009
From: alar.sing at err.ee (Alar Sing)
Date: Wed, 06 May 2009 20:47:08 +0300
Subject: [Kolab-devel] opensuse native kolabmailboxfilter php segfault
In-Reply-To: <200905061939.44712.ml@radoeka.nl>
References: <4A0048DA.6040702@err.ee> <200905061939.44712.ml@radoeka.nl>
Message-ID: <4A01CD1C.6030302@err.ee>



Richard Bos wrote:
> Hi Alar,
> 
> Op dinsdag 05 mei 2009 16:10:34 schreef Alar Sing:
>> Hello,
>>
>> I have problem with kolabmailboxfilter in opensuse native kolab
>> installation. Attached logs are from postfix and kolab filter
>> This segfault occures when user tries to sent an invite to a resource 
> account
>> that is configured to auto accept invites. After getting a bounce message
>> saying that php has died with signal 11 user gets accept from resource.
>>
>> And segfault messega from syslog
>> May  5 14:10:59 linux kernel: php5[4305]: segfault at 4c503d48 ip
>> 081b0473 sp bfed4d7c error 4 in php5[8048000+23d000]
>>
>> php version is 5.2.9 in opensuse
>>
>> What could be causing this?
> 
> No Idea ;)  The line to look at in your original posting is this one:
> May  5 14:10:59 linux postfix/pipe[4304]: 3951113235C: to=<resource at domain>, 
> relay=kolabmailboxfilter, delay=1.6, delays=0.09/0.01/0/1.5, dsn=5.3.0, 
> status=bounced (Command died with signal 11: "/usr/bin/php5")
> (just for others, so they don't need to look carefully to the log files).
> 
> The To address looks strange to me: "resource at domain".  Did you edit it?

Yes this is edited all because they were in estonina and hard to follow 
which was user whom invited and which was resource.

> Would it be possible to add printf statements, to obtain more information in 
> the log file(s)?  It's a pity that the timestamp does not include 
> milliseconds, that would make it easier to interleave the filter.log and 
> mail.log.  Perhaps it is possible with the printf statements to find the line, 
> that is the reason for the segmentation fault....
> 
> Oh, and at openSUSE we use kolab-filter-0.1.5
> 


From ml at radoeka.nl  Wed May  6 20:26:53 2009
From: ml at radoeka.nl (Richard Bos)
Date: Wed, 6 May 2009 20:26:53 +0200
Subject: [Kolab-devel] kolab on openSUSE natively is a little bit back
In-Reply-To: <200905061941.46321.martin.zboril@gmail.com>
References: <200905060504.03731.martin.zboril@gmail.com>
	<20090506064234.GA87119@xs4all.nl>
	<200905061941.46321.martin.zboril@gmail.com>
Message-ID: <200905062026.54623.ml@radoeka.nl>

Op woensdag 06 mei 2009 19:41:45 schreef Martin Zbo?il:
> Dne st?eda 06 Kv?ten 2009 08:42:34 Richard Bos napsal(a):
> > What version (of kolab) did you use.  The current slapd template contains
> >      62 # The idletimeout can be increased if some clients develop
> > problems. 63 # Please report to kolab-devel at kolab.org if you encounter
> > such a client. 64 idletimeout     300
> >
> > There are no lines that contain a "#" after an assignment.  See,
> > http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/templates
> >/s lapd.conf.template.in?rev=1.26&content-type=text/vnd.viewcvs-markup
> >
> > --
> > Richard
>
> the most recent Kolab package in OpenSuSE stable is
> 2.2.1.90_cvs20090503-2.1 and the problem is not there anymore, at least I
> think so, I cannot test that now, but I will eventually try to.
>
> Mandriva is still distributing Kolab version 2.1.0-9mdv2009.0 where the
> problem was found.
>  Also slapd.conf.template line 64 points to nonexistent folder, the correct
> one is at /var/lib/ldap-kolab.
>  amavisd is failing to open log file /var/log/amavisd: file does not exist
> as asked from /usr/sbin/amavisd line
> 1822 - the logfile of amavisd in mandriva is located at
> /var/log/amavis/amavisd.log, after changing this, amavisd works fine.

There is a mandrake bug report out there, that lists those issues.  I could 
not find the report back in my email archive.  Perhaps you can find it on the 
web.  I think that the title contains: kolab does not start right out the box.

-- 
Richard


From kolab-issues at intevation.de  Thu May  7 11:49:03 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 07 May 2009 09:49:03 +0000
Subject: [Kolab-devel] [issue3609] IMAP-Troubleshooting crashes kontact
Message-ID: <1241689742.88.0.20112046356.issue3609@intevation.de>


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

enterprise4 windows 20090430.961761

Test:
1. Start Kontact.
2. RMB on the Kolab Server in the folder view and select IMAP Troubleshooting.
3. Select "Refresh Cache"
=>Crash.

----------
assignedto: allen
messages: 20055
nosy: allen, bh, ludwig
priority: urgent
status: unread
title: IMAP-Troubleshooting crashes kontact
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3609>
___________________________________________________


From kolab-issues at intevation.de  Thu May  7 13:18:02 2009
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Thu, 07 May 2009 11:18:02 +0000
Subject: [Kolab-devel] [issue3610] Mail to unknown@something.example.com
	gets accepted and yields kolabmailboxfilter exit 38
Message-ID: <1241695082.73.0.0436709400719.issue3610@intevation.de>


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

Kolab Server 2.2.1:

Mail from localhost (via telnet/nc) to unknown at example.com correctly gets
rejected with
550 5.1.1 <unknown at example.com>: Recipient address rejected: User unknown in
local recipient table

But when sending to unknown at something.example.com (probably) the
masquerade_domains feature kicks in and the mail gets accepted and passed to
kolabmailboxfilter which results in a bounce and postfix logs:
(Command died with status 38: "/kolab/bin/php". Command output:   )

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

May 07 13:14:14 Kolab Filter [debug] [horde] Arguments: Horde_Argv_Values Object
(
    [sender] => user at example.com
    [recipient] => Array
        (
            [0] => unknown at example.com
        )

    [host] => cipactli.aztec.intevation.de
    [client] => 127.0.0.1
    [user] => 
    [config] => /kolab/etc/kolab/kolabfilter.conf
)
 [on line 244 of "/kolab/lib/php/Horde/Kolab/Filter/Base.php"]
May 07 13:14:14 Kolab Filter [info] [horde] Horde_Kolab_Filter_Content
successfully completed (sender=user at example.com, recipients=unknown at example.com,
client_address=127.0.0.1,
id=<20090507111359.E4B34343973C at cipactli.aztec.intevation.de>) [on line 141 of
"/kolab/lib/php/Horde/Kolab/Filter/Base.php"]
May 07 13:14:26 Kolab Filter [debug] [horde] Arguments: Horde_Argv_Values Object
(
    [sender] => user at example.com
    [recipient] => Array
        (
            [0] => unknown at example.com
        )

    [host] => cipactli.aztec.intevation.de
    [client] => 127.0.0.1
    [user] => 
    [config] => /kolab/etc/kolab/kolabfilter.conf
)
 [on line 244 of "/kolab/lib/php/Horde/Kolab/Filter/Base.php"]
May 07 13:14:26 Kolab Filter [debug] [horde] Arguments: Horde_Argv_Values Object
(
    [sender] => 
    [recipient] => Array
        (
            [0] => user at example.com
        )

    [host] => cipactli.aztec.intevation.de
    [client] => 
    [user] => 
    [config] => /kolab/etc/kolab/kolabfilter.conf
)
 [on line 244 of "/kolab/lib/php/Horde/Kolab/Filter/Base.php"]
May 07 13:14:26 Kolab Filter [debug] [horde] Filter_Incoming successfully
completed. [on line 167 of "/kolab/lib/php/Horde/Kolab/Filter/Incoming.php"]
May 07 13:14:26 Kolab Filter [info] [horde] Horde_Kolab_Filter_Incoming
successfully completed (sender=, recipients=user at example.com, client_address=,
id=<20090507111426.1B893343973D at cipactli.aztec.intevation.de>) [on line 141 of
"/kolab/lib/php/Horde/Kolab/Filter/Base.php"]

The last block is for the bounce message,
fatal.log does not show any new messages.

Despite the unsuccessful exit there is no indication of a problem in the
filter log!

Besides the filter problem I think that even with masquerade_domains the mail
should not get accepted, I'll look into this part.

----------
assignedto: wrobel
messages: 20060
nosy: martin, thomas, wilde, wrobel
priority: urgent
status: unread
title: Mail to unknown at something.example.com gets accepted and yields kolabmailboxfilter exit 38
topic: filter, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3610>
___________________________________________________


From wrobel at pardus.de  Thu May  7 21:37:34 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 07 May 2009 21:37:34 +0200
Subject: [Kolab-devel] opensuse native kolabmailboxfilter php segfault
In-Reply-To: <200905061939.44712.ml@radoeka.nl>
References: <4A0048DA.6040702@err.ee> <200905061939.44712.ml@radoeka.nl>
Message-ID: <20090507213734.61954w85wajam1s0@webmail.pardus.de>

Quoting Richard Bos <ml at radoeka.nl>:

> Hi Alar,
>
> Op dinsdag 05 mei 2009 16:10:34 schreef Alar Sing:
>> Hello,
>>
>> I have problem with kolabmailboxfilter in opensuse native kolab
>> installation. Attached logs are from postfix and kolab filter
>> This segfault occures when user tries to sent an invite to a resource
> account
>> that is configured to auto accept invites. After getting a bounce message
>> saying that php has died with signal 11 user gets accept from resource.
>>
>> And segfault messega from syslog
>> May  5 14:10:59 linux kernel: php5[4305]: segfault at 4c503d48 ip
>> 081b0473 sp bfed4d7c error 4 in php5[8048000+23d000]
>>
>> php version is 5.2.9 in opensuse
>>
>> What could be causing this?
>
> No Idea ;)  The line to look at in your original posting is this one:
> May  5 14:10:59 linux postfix/pipe[4304]: 3951113235C: to=<resource at domain>,
> relay=kolabmailboxfilter, delay=1.6, delays=0.09/0.01/0/1.5, dsn=5.3.0,
> status=bounced (Command died with signal 11: "/usr/bin/php5")
> (just for others, so they don't need to look carefully to the log files).

This line

May 05 14:10:58 Kolab Filter [error] [horde] PHP Error:  
file_get_contents(/tmp/Kolab_Filter_locks/resource at domain.lock):  
failed to open stream: No such file or directory; Code: 0 [on line 146  
of "/usr/share/php5/PEAR/Horde/Kolab/Filter/Response.php"]

looks problematic, too.

It seems the lock directory has been left unconfigured or does not exist.

Has

$conf['kolab']['filter']['simple_locks_dir']

been set for the Kolab_Filter configuration? And does it contain a  
valid directory?

Nevertheless even this should not lead to a segfault. I did not test  
php-5.2.9 yet.

Cheers,

Gunnar

>
> The To address looks strange to me: "resource at domain".  Did you edit it?
> Would it be possible to add printf statements, to obtain more information in
> the log file(s)?  It's a pity that the timestamp does not include
> milliseconds, that would make it easier to interleave the filter.log and
> mail.log.  Perhaps it is possible with the printf statements to find  
> the line,
> that is the reason for the segmentation fault....
>
> Oh, and at openSUSE we use kolab-filter-0.1.5
>
> --
> Richard
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



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

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

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


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

From ml at radoeka.nl  Thu May  7 21:59:20 2009
From: ml at radoeka.nl (Richard Bos)
Date: Thu, 7 May 2009 21:59:20 +0200
Subject: [Kolab-devel] opensuse native kolabmailboxfilter php segfault
In-Reply-To: <20090507213734.61954w85wajam1s0@webmail.pardus.de>
References: <4A0048DA.6040702@err.ee> <200905061939.44712.ml@radoeka.nl>
	<20090507213734.61954w85wajam1s0@webmail.pardus.de>
Message-ID: <200905072159.20637.ml@radoeka.nl>

Hi Gunnar,

Op donderdag 07 mei 2009 21:37:34 schreef Gunnar Wrobel:
> This line
>
> May 05 14:10:58 Kolab Filter [error] [horde] PHP Error:  
> file_get_contents(/tmp/Kolab_Filter_locks/resource at domain.lock):  
> failed to open stream: No such file or directory; Code: 0 [on line 146  
> of "/usr/share/php5/PEAR/Horde/Kolab/Filter/Response.php"]
>
> looks problematic, too.
>
> It seems the lock directory has been left unconfigured or does not exist.
>
> Has
> $conf['kolab']['filter']['simple_locks_dir']
> been set for the Kolab_Filter configuration? And does it contain a  
> valid directory?

It is not set:
kolab2:/etc/kolab/templates # grep simple_lo *
resmgr.conf.template:$conf['kolab']['filter']['simple_locks'] = true;
resmgr.conf.template:$conf['kolab']['filter']['simple_locks_timeout'] = 60;
resmgr.conf.template:$conf['kolab']['filter']['simple_locks_dir'] = '';

It's because we (openSUSE (or oS)) did not define it in cvs:
kolabd/dist_conf> grep resmgr_locksdir *
common: -e 's=[@]resmgr_locksdir[@]=$(resmgr_locksdir)=g' \
debian:resmgr_locksdir=${kolab_statedir}/filter/locks
kolab:resmgr_locksdir=${localstatedir}/kolab-filter/locks

Thanks for pointing this out!

-- 
Richard


From kolab-issues at intevation.de  Fri May  8 10:04:47 2009
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Fri, 08 May 2009 08:04:47 +0000
Subject: [Kolab-devel] [issue3611] Crash in K3ListView::startDrag
Message-ID: <1241769886.98.0.522311563951.issue3611@intevation.de>


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

Got a crash on ppc. No idea how to reproduce it, 
so this is a collecting issue.

I was on the road with flaky, slow internet connection via umts
and was working when the crash happened.

Architecture: powerpc
Source: kdepim Version: 4:4.1.1.enterprise4.0.20090424.958783-kk1
Source: kde4libs
Version: 4:4.1.1.enterprise4.0.20090423.958303-kk1

----------
assignedto: bernhard
files: 20090506-kontact.kcrash
messages: 20097
nosy: allen, bernhard, bh, ludwig, till
priority: bug
status: need-eg
title: Crash in K3ListView::startDrag
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3611>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 20090506-kontact.kcrash
Type: application/octet-stream
Size: 2383 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090508/f424fdad/20090506-kontact.exe

From kolab-issues at intevation.de  Fri May  8 10:56:44 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Fri, 08 May 2009 08:56:44 +0000
Subject: [Kolab-devel] [issue3612] Export web page overwrites files without
	warning
Message-ID: <1241773004.76.0.994468597836.issue3612@intevation.de>


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

enterprise35 20090430.961755

Test:
1. Switch to calendar.
2. Files->Export->Export as webpage.
3. Press Okay.

The calendar.html is overwritten without warning.

----------
assignedto: ludwig
messages: 20105
nosy: allen, bh, ludwig
priority: bug
status: testing
title: Export web page overwrites files without warning
topic: enterprise35, enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3612>
___________________________________________________


From kolab-issues at intevation.de  Fri May  8 13:36:47 2009
From: kolab-issues at intevation.de (Mike Gabriel)
Date: Fri, 08 May 2009 11:36:47 +0000
Subject: [Kolab-devel] [issue3613] Toltec displays private events to
	non-owners
Message-ID: <1241782607.24.0.594701944349.issue3613@intevation.de>


New submission from Mike Gabriel <m.gabriel at das-netzwerkteam.de>:

with Outlook 2003, Toltec 2.3.1 do as follows:

  o let userA create a Calendar_for_A+B and let userA share it with userB
  o check permissions with cyradm

    (authenticated to KolabCyrus as userA)  

    localhost.localdomain> lam "INBOX/Calendar_for_A+B"
    userA at domain.tld lrswipcda
    userB at domain.tld lrswipcd

  o let userA enter a _private_ event in Outlook
  o sync Calendar_for_A+B as userA to the Kolab server with Toltec Connector
  o let userB sync his Outlook Folders with Toltec Connector
  o userB will be able to see the private event userA just entered.

any ideas how to fix this?

BTW: after applying horde patch in horde bug
http://bugs.horde.org/ticket/8240

horde shows the event as private (and hides it from userB).

----------
messages: 20116
nosy: joonradley, mike
status: unread
title: Toltec displays private events to non-owners
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3613>
___________________________________________________


From kolab-issues at intevation.de  Mon May 11 11:37:30 2009
From: kolab-issues at intevation.de (Mike Gabriel)
Date: Mon, 11 May 2009 09:37:30 +0000
Subject: [Kolab-devel] [issue3614] Toltec: default Calendar,
	default Task folders got deleted
Message-ID: <1242034650.04.0.26518672791.issue3614@intevation.de>


New submission from Mike Gabriel <m.gabriel at das-netzwerkteam.de>:

though it is probably hard to reproduce i want to let you know about a hard
weekend...

try the following:

KOLAB-SERVER:

  o in addition to default Calendar and Tasks folder create another calendar 
    share calEXTRA and another task share taskEXTRA (use cyradm)
  o use cyradm mboxcfg to make calEXTRA, tasksEXTRA your default share

    (kontact does something like this, if no default groupware folder is 
    present it selects any folder - i suppose the first in alphanumeric order, 
    that's how my default folders became a mess... anyway)
  
  o store events and task in the folders: Calendar, calEXTRA(default), Tasks, 
    tasksEXTRA(default), use a client like Horde to create events (not 
    Outlook!).

  o connect with MS Outlook 2007 and Toltec Connector 2.3.1

  o sync all folders

  o Calendar share and Tasks share in Outlook stay empty (although there should 
    be items, as we created them before, s.above)

  o after a second/third sync the Calendar share on the KOLAB server vanishes 
    (Arggghh... I love my backup server, in Outlook Calendar share is still 
    present, though unsynced/empty)

  o Create Tasks in Outlook's Tasks share

  o sync

  o Tasks share on KOLAB server vanishes (not so in Outlook)

  o with luck, the Tasks created in Outlook have been synced to tasksEXTRA 
    (which is the Tasks default share on the KOLAB server), this behaviour only 
    occurred with tasks, events always got lost completely...

to fix it...

  o create Calendar, Tasks share on KOLAB server, make it the default gw shares 
    for their types, use same share names as Outlook does(!)
  o change folder-type: from event.default to event on calEXTRA
  o change folder-type: from task.default to task on tasksEXTRA
  o restore mails in all shares from backup
  o run cyrreconstruct
  o delete outlook profile
  o delete .pst file
  o create new outlook account

After fiddling around with my Production account for two nights i have the
impression that Toltec/Outlook get confused when the default groupware share
names on the KOLAB server are not of the same name as the groupware share names
in outlook. how does toltec map these default gw folders from outlook to
kolab??? outlook is rather ridig with its default gw share names, kolab is quite
tolerant about default gw names. how does this come together? does toltec sync
from Outlook ,,Calendar'' in to the default event.default gw share, regardless
of its name?

Taking into consideration that KDE Kontact is really arbitrary with default gw
names and in some situation (when there is no default gw folder for a certain gw
type) even sets any of the present gw folders as the default for its type, it
can be very vulnerable to your folders ,,Calendar'' and ,,Tasks'' (default
Outlook names) if you use both clients in parallel. to my mind it only works if 

  (a) Toltec is the first Groupware-Client that creates gw folders on the server
  (b) the naming scheme of gw shares on the kolab server is conform to 
      outlook's localized(!) gw share names 
  (c) i guess toltec even breaks if you use a german and english ms outlook 
      version

my last weekend's experiences are quite worrying to me.

PS: similar problem occurred with the default Contact share...

----------
messages: 20136
nosy: joonradley, mike
status: unread
title: Toltec: default Calendar, default Task folders got deleted
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3614>
___________________________________________________


From kolab-issues at intevation.de  Tue May 12 08:57:10 2009
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Tue, 12 May 2009 06:57:10 +0000
Subject: [Kolab-devel] [issue3615] KMail evaluation all uids of a key it
	trieds to encrypt to, leading to missleading warnings
Message-ID: <1242111430.81.0.722964269059.issue3615@intevation.de>


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

I am getting a confusing warning when trying to encrypt
to an email address where the key has several uids
and some are not fully valid.

My expectation is that only the uid in question is checked against
validity. 

To reproduce this issue you would need to have a key with several
uids that some have a valididy of 0 (aka unkown) in gpg2 --edit-key.
E.g. for me I can demostrate this on the key of Matthias (attached).

I have deleted one uid which I had "unknown", and now I cannot reproduce:
LANG=C gpg2 --edit-key mk at fsfe.org
gpg (GnuPG) 2.0.11; 
pub  1024D/8EF520D1  created: 2002-11-21  expires: never       usage: SC
                     trust: unknown       validity: full
sub  1024g/64A4C81B  created: 2002-11-21  expires: never       usage: E
sub  1024R/1216110F  created: 2005-10-13  expires: never       usage: A
sub  1024R/A5D6BFBC  created: 2005-10-13  expires: never       usage: S
sub  1024R/323CE763  created: 2005-10-13  expires: never       usage: E
[  full  ] (1). Matthias Kirschner <mk at mbwg.de>
[  full  ] (2)  Matthias Kirschner <mk at office.fsfeurope.org>
[  full  ] (3)  Matthias Kirschner <matze at mbwg.de>
[  full  ] (4)  Matthias Kirschner <matze at difficulties.de>
[  full  ] (5)  Matthias Kirschner <mk at fsfe.org>
[ revoked] (6)  Matthias Kirschner <matthias.kirschner at gmx.de>
[ revoked] (7)  Matthias Kirschner <greve-assist at fsfeurope.org>
[ revoked] (8)  Matthias Kirschner <matthias.kirschner at uni-konstanz.de>

Importing this uid again:
gpg2 --import tmp/mk.key
 LANG=C gpg2 --edit-key mk at fsfe.org
gpg (GnuPG) 2.0.11;
pub  1024D/8EF520D1  created: 2002-11-21  expires: never       usage: SC
                     trust: unknown       validity: full
sub  1024g/64A4C81B  created: 2002-11-21  expires: never       usage: E
sub  1024R/1216110F  created: 2005-10-13  expires: never       usage: A
sub  1024R/A5D6BFBC  created: 2005-10-13  expires: never       usage: S
sub  1024R/323CE763  created: 2005-10-13  expires: never       usage: E
[  full  ] (1). Matthias Kirschner <mk at mbwg.de>
[  full  ] (2)  Matthias Kirschner <mk at office.fsfeurope.org>
[  full  ] (3)  Matthias Kirschner <matze at mbwg.de>
[  full  ] (4)  Matthias Kirschner <matze at difficulties.de>
[  full  ] (5)  Matthias Kirschner <mk at fsfe.org>
[ revoked] (6)  Matthias Kirschner <matthias.kirschner at gmx.de>
[ revoked] (7)  Matthias Kirschner <greve-assist at fsfeurope.org>
[ revoked] (8)  Matthias Kirschner <matthias.kirschner at uni-konstanz.de>
[ unknown] (9)  Matthias Kirschner <kirschner at fsfeurope.org>

Now I am getting the missleading warning when trying to encrypt, e.g.
to mk at fsfe.org. There should not be a warning as "mk at fsfe.org" is a fully valid 
uid.

I think it should be possible to create a test-setup for you,
just delete your signatures on one of the uids for a key until you
have something like above.

----------
assignedto: allen
files: mk.key
messages: 20164
nosy: allen, bernhard, marc, till
priority: bug
status: unread
title: KMail evaluation all uids of a key it trieds to encrypt to, leading to missleading warnings
topic: crypto, enterprise35, enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3615>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mk.key
Type: application/octet-stream
Size: 14332 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090512/b514c462/mk.exe

From thomas at intevation.de  Tue May 12 14:39:31 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Tue, 12 May 2009 14:39:31 +0200
Subject: [Kolab-devel] Patches for cyrus imapd 2.3.14 (was: Re:
	thomas:	server/patches/cyrus-imapd/cyrus-imapd-2.3.13	KOLAB_cyrus-imapd-2.3.13_Groups2.patch,
	1.1.2.1, 1.1.2.2)
In-Reply-To: <20090423235556.202726oxqw3d1wjo@webmail.pardus.de>
References: <20090406144837.7AC0C60082F@lists.intevation.de>
	<20090419111249.187956qd3sxsup8o@webmail.pardus.de>
	<20090423235556.202726oxqw3d1wjo@webmail.pardus.de>
Message-ID: <20090512123931.GA32568.thomas@intevation.de>

* Gunnar Wrobel <wrobel at pardus.de> [20090423 23:56]:
> I was somehow unable to fetch the imapd-2.3.14-RPM from OpenPKG. So the package has not been updated to this newer version.

For the archive, as mentioned a while ago on the phone:
http://files.kolab.org/server/development-2.2/openpkg-orig-srpms/imapd-2.3.14-20090326.src.rpm

Maybe we need a development-2.3 directory soon :)

Regards,
Thomas Arendsen Hein

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

From kolab-issues at intevation.de  Tue May 12 17:15:38 2009
From: kolab-issues at intevation.de (Thomas Arendsen Hein)
Date: Tue, 12 May 2009 15:15:38 +0000
Subject: [Kolab-devel] [issue3616] automatic replies to invitations contain
	127.0.0.1 in Message-ID
Message-ID: <1242141338.76.0.871259767931.issue3616@intevation.de>


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

Replies sent by automatic resources now have a Message-ID header and oldest
Received header containing 127.0.0.1, this is only cosmetic for Received, but
at least a minor bug for the Message-ID:

With 2.2.1 and almost-2.2.2:
Received: from 127.0.0.1 ([127.0.0.1]) by 127.0.0.1 (Horde MIME library)
        with HTTP; Tue, 31 Mar 2009 18:29:04 +0200
Message-ID: <20090331182904.ikiz17om65w88w8o at 127.0.0.1>

With 2.2.0:
Received: from localhost ([localhost]) by example.com (Horde Framework)
        with HTTP; Mon, 02 Mar 2009 23:06:13 +0100
Message-ID: <20090302230613.1099234rlsufcwv4 at example.com>

----------
assignedto: wrobel
messages: 20181
nosy: martin, thomas, wilde, wrobel
priority: minor bug
status: unread
title: automatic replies to invitations contain 127.0.0.1 in Message-ID
topic: filter, server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3616>
___________________________________________________


From kolab-issues at intevation.de  Wed May 13 10:46:31 2009
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Wed, 13 May 2009 08:46:31 +0000
Subject: [Kolab-devel] [issue3617] Kleopatra's setting dialog cannot show
	the set number with gpgconf TYPE=0 (simple option) FLAGS=4
	(list) options like gpg's "verbose"
Message-ID: <1242204390.94.0.11226118118.issue3617@intevation.de>


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

Some gpg options have no argument but can be set a number of time.
An example is "verbose" for gnupg2.

gnupg 2.0.11-0kk1

gpgconf --list-options gpg | grep verbose
verbose:4:0:Detaillierte Informationen:0:0::::2

This means "verbose" is set twice, but Kleopatra displays "0".
Expectation: It should display "2".
(Documentation in "info gnupg2" node "gpgconf". The second field is FLAGS
and the TYPE=0 and the VALUE=2 in the above lines.)

Setting works, except for setting "0" because of a potential
gnupg2 defect, watch https://bugs.g10code.com/gnupg/issue1052 (Unable to 
unset "verbose" option for gpg with gpgconf)

----------
assignedto: allen
messages: 20190
nosy: allen, bernhard, ludwig, marc, till
priority: bug
status: unread
title: Kleopatra's setting dialog cannot show the set number with gpgconf TYPE=0 (simple option) FLAGS=4 (list) options like gpg's "verbose"
topic: crypto, enterprise35, enterprise4, kde client, kkc
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3617>
___________________________________________________


From kolab-issues at intevation.de  Wed May 13 15:39:09 2009
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Wed, 13 May 2009 13:39:09 +0000
Subject: [Kolab-devel] [issue3618] Enable kDebug() output for all builds.
Message-ID: <1242221949.09.0.451830658436.issue3618@intevation.de>


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

In kolab/issue3045 (A valid signature is not recognized.)
we were unsure if we can see the kDebug() output on windows.

It turns out that even with EMERGE_BUILDTYPE=RelWithDebInfo this is 
_not_ the case. See

http://websvn.kde.org/branches/kdepim/enterprise4/kdelibs-4.1-branch/kdecore/io/kdebug.h?revision=849447&view=markup
has
# if defined(QT_NO_DEBUG) || defined(QT_NO_DEBUG_OUTPUT) || 
defined(QT_NO_DEBUG_STREAM)
#  define KDE_NO_DEBUG_OUTPUT
# endif

and "grep kdebug.cpp build-20090505-01.log" shows me that:
cd E:\kderoot\tmp\kdelibs-branch-20080902\work\mingw-RelWithDebInfo\kdecore && 
e:
\kderoot\mingw\bin\g++.exe   -DQT_NO_DEBUG -DQT_DLL -DQT_NO_STL -DQT_NO_CAST_TO_ASCII -D_REENTRANT -DKDE_DEPRECATED_WARNINGS -DNO_DISPLAY -DMAKE_KDECORE_LIB  -Woverloaded-virtual -O2 -g
[..]
  -o CMakeFiles\kdecore.dir\io\kdebug.obj -c E:
\kderoot\svn\tags\kdepim\enterprise4.0.20090430.961761\kdelibs-4.1-branch\kdecore\io\kdebug.cpp

the "-DQT_NO_DEBUG" is the culprit. I suggest for the next build to change
kdebug.h to remove the check for "-DQT_NO_DEBUG". 
Ludwig, please start the next build with this changed.

Allen, (or anybody from KDAB): Can you shed some light on the 
QT_NO_DEBUG_OUTPUT QT_NO_DEBUG_STREAM
defines? What do they mean? Can we savely ignore them?

----------
assignedto: ludwig
messages: 20203
nosy: allen, bernhard, bh, ludwig, marc, till
priority: urgent
status: unread
title: Enable kDebug() output for all builds.
topic: kde client, kowi, windows
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3618>
___________________________________________________


From bh at intevation.de  Wed May 13 20:22:22 2009
From: bh at intevation.de (Bernhard Herzog)
Date: Wed, 13 May 2009 20:22:22 +0200
Subject: [Kolab-devel] Automatically built KDEPIM packages now published
	on files.kolab.org
In-Reply-To: <960738410904290051w5df59e91s1bc51f5e26eb1272@mail.gmail.com>
References: <200904282008.16616.bh@intevation.de>
	<960738410904290051w5df59e91s1bc51f5e26eb1272@mail.gmail.com>
Message-ID: <200905132022.25198.bh@intevation.de>

On 29.04.2009, Mathieu Parent wrote:
> On Tue, Apr 28, 2009 at 8:08 PM, Bernhard Herzog <bh at intevation.de> wrote:
> > We've automated the build system a bit more, and 
> > the newest automatically built packages are now available on
> > files.kolab.org.
[...]
> Might be good to put this on wiki.kolab.org

Indeed.  I've added a page for it now:
http://wiki.kolab.org/index.php/KDEPIM_Snapshot_Packages

   Bernhard

-- 
Bernhard Herzog  |  ++49-541-335 08 30  |  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: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090513/0c1c3955/attachment.bin

From kolab-issues at intevation.de  Thu May 14 12:52:12 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 14 May 2009 10:52:12 +0000
Subject: [Kolab-devel] [issue3619] A mail sent to a local distribution list
	doesn't contain the dist list email-addresses
Message-ID: <1242298332.36.0.266366797587.issue3619@intevation.de>


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

enterprise4 windows 20090430.961761

Test:
1. Switch to the contacts component
2. Create a local distribution list.
3. Switch to the mail component.
4. Send a mail to the dist list.
=> The mail is sent to the distlistname at server. I expect the mail to be sent to
the mail addresses of the contacts of the distribution list.
So this is wrong.

----------
assignedto: allen
messages: 20224
nosy: allen, bh, ludwig
priority: urgent
status: unread
title: A mail sent to a local distribution list doesn't contain the dist list email-addresses
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3619>
___________________________________________________


From kolab-issues at intevation.de  Thu May 14 13:02:34 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 14 May 2009 11:02:34 +0000
Subject: [Kolab-devel] [issue3620] After deletion of a selected contact from
	a distribution list no contact is selected and the details of
	the deleted contact are shown.
Message-ID: <1242298954.07.0.241193962168.issue3620@intevation.de>


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

enterprise4 windows 20090430.961761

Test:
1.Create a dist list with three contacts.
2. Select The dist list in the distribution list view.
3. Select a contact from the dist list.
=> details of that contact are shown.
4. Press the delete from dist list button.
=> No contact is selected and the details of removed contact are still shown.

I expect that another contact of the dist list is selected and its details are
shown.

----------
assignedto: allen
messages: 20226
nosy: allen, bh, ludwig
priority: minor bug
status: unread
title: After deletion of a selected contact from a distribution list no contact is selected and the details of the deleted contact are shown.
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3620>
___________________________________________________


From kolab-issues at intevation.de  Fri May 15 09:22:22 2009
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Fri, 15 May 2009 07:22:22 +0000
Subject: [Kolab-devel] [issue3621] Freebusy list not shown because
	FreeBusyManager::iCalToFreeBusy: Error parsing free/busy, shortened
Message-ID: <1242372142.07.0.960105076979.issue3621@intevation.de>


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

Architecture: powerpc
Source: kdepim
Version: 4:4.1.1.enterprise4.0.20090424.958783-kk1
Architecture: powerpc
Source: kde4libs
Version: 4:4.1.1.enterprise4.0.20090423.958303-kk1

Freebusy lists are not loaded, it seems they are truncated after a while
in .xsessions (though not after a fixed number of bytes). Konqueror
fully downloads and saves the files in question.

kded(3687)/kio (KPasswdServer) KPasswdServer::addAuthInfoItem: Creating 
AuthInfoContainer
kontact(7884)/korganizer 
FreeBusyDownloadJob::slotResult: "umts.usb2 at intevation.de"
kontact(7884)/korganizer FreeBusyManager::iCalToFreeBusy: "BEGIN:VCALENDAR^M   
VERSION:2.0^M
PRODID:-//kolab.org//NONSGML Kolab Server 2//EN^M                              
METHOD:PUBLISH^M
BEGIN:VFREEBUSY^M                                                              
ORGANIZER;cn=umts usb2:MAILTO:umts.usb2 at intevation.de^M
DTSTAMP:20090515T071146Z^M                                                     
URL:http://kolab.intevation.de/freebusy/umts.usb2 at intevation.de.ifb^M
DTSTART:20090308T230000Z^M                                                     
DTEND:20100508T220000Z^M
FREEBUSY:20090306T170000Z/20090309T080000Z^M                                   
FREEBUSY:20090313T110000Z/20090318T150000Z^M
FREEBUSY:20090401T070000Z/20090402T160000Z^M                                   
FREEBUSY:20090409T220000Z/20090414T073000Z^M
FREEBUSY:20090416T080000Z/20090416T110000Z                                     
kontact(7884)/korganizer FreeBusyManager::iCalToFreeBusy: Error parsing 
free/bu
sy                                                                             
kontact(7884)/korganizer FreeBusyManager::iCalToFreeBusy: "BEGIN:VCALENDAR^M
VERSION:2.0^M                                                                  
PRODID:-//kolab.org//NONSGML Kolab Server 2//EN^M
METHOD:PUBLISH^M                                                               
BEGIN:VFREEBUSY^M
ORGANIZER;cn=umts usb2:MAILTO:umts.usb2 at intevation.de^M                        
DTSTAMP:20090515T071146Z^M
URL:http://kolab.intevation.de/freebusy/umts.usb2 at intevation.de.ifb^M          
DTSTART:20090308T230000Z^M
DTEND:20100508T220000Z^M                                                       
FREEBUSY:20090306T170000Z/20090309T080000Z^M
FREEBUSY:20090313T110000Z/20090318T150000Z^M                                   
FREEBUSY:20090401T070000Z/20090402T160000Z^M
FREEBUSY:20090409T220000Z/20090414T073000Z^M                                   
FREEBUSY:20090416T080000Z/20090416T110000Z"
kio_http(8742)/kssl KIO::TCPSlaveBase::disconnectFromHost:

----------
assignedto: allen
messages: 20254
nosy: allen, bernhard, ludwig, till
priority: urgent
status: unread
title: Freebusy list not shown because FreeBusyManager::iCalToFreeBusy: Error parsing free/busy, shortened
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3621>
___________________________________________________


From thomas at intevation.de  Fri May 15 15:42:02 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 15 May 2009 15:42:02 +0200
Subject: [Kolab-devel] Kolab Server 2.2.2 Final Release
Message-ID: <20090515134202.GC31326.thomas@intevation.de>

Hi!

I just uploaded the final release of Kolab Server 2.2.2, which
contains 12 enhancements and fixes compared to the previous release.

ClamAV was updated to the current release to fix some security issues,
the web client received some enhancements in the dynamic interface and
the mail and invitation handling received some important fixes.

Upgrading from 2.2.1 should be straightforward, if you follow the
upgrade instructions in 1st.README.

Documentation and OpenPKG packages are available from
http://files.kolab.org/server/release/kolab-server-2.2.2/
as shown on http://kolab.org/download.html and from the mirrors
listed on http://kolab.org/mirrors.html

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

All files updated since 2.2.1 are available in the directory
server/development-2.2/20090515-since-20090407/

You can check the integrity of the downloaded files with:

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

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

For the first time we provide binary packages for Debian GNU/Linux 5.0
(lenny/stable) on x86 platforms, too, which can be found in the
ix86-debian5.0 directory.

For install instructions and more information about this release, look at
http://files.kolab.org/server/release/kolab-server-2.2.2/sources/1st.README and
http://files.kolab.org/server/release/kolab-server-2.2.2/sources/release-notes.txt

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

Regards,
Thomas Arendsen Hein

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

From martin.zboril at gmail.com  Wed May  6 05:04:02 2009
From: martin.zboril at gmail.com (Martin =?utf-8?q?Zbo=C5=99il?=)
Date: Wed, 6 May 2009 05:04:02 +0200
Subject: [Kolab-devel] kolab on openSUSE natively is a little bit back
Message-ID: <200905060504.03731.martin.zboril@gmail.com>

Good morning gentlemen,
 
Recently I tried both OpenSuSE 11.1 and Mandriva 2009.1, in both I was trying
the most recent kolab version with same results in both distros, the problem I found, after
almost 8 hours of troubleshooting, is actually in slapd.conf.template  on lines 59 & 60

slapd.conf.template line 59
idletimeout     80 # The value can be increased if some clients develop problems.
                   # Please report to kolab-devel at kolab.org if you encounter such a client.

slapd parses comments only if a line with commentary *starts* with # sign.

Happy hacking ;-)

Martin Zbo?il


From martin.zboril at gmail.com  Wed May  6 19:41:45 2009
From: martin.zboril at gmail.com (Martin =?utf-8?q?Zbo=C5=99il?=)
Date: Wed, 6 May 2009 19:41:45 +0200
Subject: [Kolab-devel] kolab on openSUSE natively is a little bit back
In-Reply-To: <20090506064234.GA87119@xs4all.nl>
References: <200905060504.03731.martin.zboril@gmail.com>
	<20090506062135.GA85121@xs4all.nl>
	<20090506064234.GA87119@xs4all.nl>
Message-ID: <200905061941.46321.martin.zboril@gmail.com>

Dne st?eda 06 Kv?ten 2009 08:42:34 Richard Bos napsal(a):
> What version (of kolab) did you use.  The current slapd template contains
>      62 # The idletimeout can be increased if some clients develop
> problems. 63 # Please report to kolab-devel at kolab.org if you encounter such
> a client. 64 idletimeout     300
>
> There are no lines that contain a "#" after an assignment.  See,
> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/templates/s
>lapd.conf.template.in?rev=1.26&content-type=text/vnd.viewcvs-markup
>
> --
> Richard
the most recent Kolab package in OpenSuSE stable is 2.2.1.90_cvs20090503-2.1 
and the problem is not there anymore, at least I think so, I cannot test that 
now, but I will eventually try to.

Mandriva is still distributing Kolab version 2.1.0-9mdv2009.0 where the 
problem was found.
 Also slapd.conf.template line 64 points to nonexistent folder, the correct 
one is at /var/lib/ldap-kolab.
 amavisd is failing to open log file /var/log/amavisd: file does not exist as 
asked from /usr/sbin/amavisd line 
1822 - the logfile of amavisd in mandriva is located at 
/var/log/amavis/amavisd.log, after changing this, amavisd works fine.




From aspineux at gmail.com  Fri May 15 23:24:25 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Fri, 15 May 2009 23:24:25 +0200
Subject: [Kolab-devel] Fwd: Which MUA for the CLI?
In-Reply-To: <6913EB1A-7020-4206-92E3-4563618ADBA0@izsr.de>
References: <04E197D8-ECAD-4B99-9C31-D25094AEDE05@izsr.de>
	<71fe4e760905110438l668d9197g6b8ec795aa694432@mail.gmail.com>
	<6913EB1A-7020-4206-92E3-4563618ADBA0@izsr.de>
Message-ID: <71fe4e760905151424x4eb39cf0tc9809eb322f1b3de@mail.gmail.com>

This could be part of the kolab installation script, or at least in
the 1st.Readme ?


---------- Forwarded message ----------
From: Tim Golz <kolab at izsr.de>
Date: Wed, May 13, 2009 at 12:11 AM
Subject: Re: Which MUA for the CLI?
To: kolab-users at kolab.org


Hi Alain,


>> on a Kolab 2.2.0 on a Debian Etch, which MUA could I use when I just
>> want to send a testmail via the CLI?
>
> Try replacing your sendmail binary by the kolab's one.
>
> Try this :
>
> mv /usr/sbin/sendmail /usr/sbin/sendmail.save
> ln -sf /kolab/sbin/sendmail /usr/sbin/sendmail
>
> Then try your mail or mailx utility


thanx really a lot - it took me 2,5 seconds and works like a charm ;-)


thanx, too, to Bernhard.


greetings


Tim

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



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


From ml at radoeka.nl  Sat May 16 16:52:43 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sat, 16 May 2009 16:52:43 +0200
Subject: [Kolab-devel] Is comment on line 181 in kolabd/Makefile.am still
	valid?
Message-ID: <200905161652.43460.ml@radoeka.nl>

Hi,

in kolabd/Makefile.am, the following lines are present:
181 # Please update the perl-kolab, kolab-webadmin and kolab-resource-handlers
182 # Makefile.ams too when the underneath EXTRA_DIST assignment is altered
184         dist_conf/debian \
185         dist_conf/kolab \
186         dist_conf/kolabsrv \
187         dist_conf/mandriva \
188         dist_conf/suse


Are the comment lines (181 and 182) still valid?  kolab-resource-handlers is 
gone, so that can be removed.  But what about perl-kolab, is that still using 
the values from the dist_conf files?  I believe, it doesn't, hence the comment 
lines should become (I think):

181 # Please update the kolab-webadmin
182 # Makefile.am too when the underneath EXTRA_DIST assignment is altered

Is this assumption correct?

-- 
Richard


From bernhard at intevation.de  Mon May 18 10:12:59 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 18 May 2009 10:12:59 +0200
Subject: [Kolab-devel] Fwd: Which MUA for the CLI?
In-Reply-To: <71fe4e760905151424x4eb39cf0tc9809eb322f1b3de@mail.gmail.com>
References: <04E197D8-ECAD-4B99-9C31-D25094AEDE05@izsr.de>
	<6913EB1A-7020-4206-92E3-4563618ADBA0@izsr.de>
	<71fe4e760905151424x4eb39cf0tc9809eb322f1b3de@mail.gmail.com>
Message-ID: <200905181013.00913.bernhard@intevation.de>

On Friday 15 May 2009, Alain Spineux wrote:
> This could be part of the kolab installation script, or at least in
> the 1st.Readme ?

In the installation script? I am unsure about it.
We should mention "nullmailer" or the linking solution somewhere in
the docs in a general way. 


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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090518/64054087/attachment.bin

From kolab-issues at intevation.de  Mon May 18 14:13:29 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Mon, 18 May 2009 12:13:29 +0000
Subject: [Kolab-devel] [issue3622] Export a contact as vCard 2.1 doesn't work
Message-ID: <1242648808.94.0.776955150029.issue3622@intevation.de>


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

enterprise4 windows tag 20090508.965288 + kdelibs 4.2

Test:
1. Switch to contacts plugin.
2. Select a contact.
3. File->Export->Exoprt as vCard 2.1
4. Press twice okay.
=>Just the main window remains. And kontact enters a zombie mode and tries some
KUrl::setPath operations. No file selection dialog appears.

----------
assignedto: allen
messages: 20283
nosy: allen, bh, ludwig
priority: bug
status: unread
title: Export a contact as vCard 2.1 doesn't work
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3622>
___________________________________________________


From kolab-issues at intevation.de  Tue May 19 10:21:57 2009
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Tue, 19 May 2009 08:21:57 +0000
Subject: [Kolab-devel] [issue3623] quick contact search busy loop freezes
	kontact
Message-ID: <1242721317.79.0.0587191966275.issue3623@intevation.de>


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

With about 111 contacts from four folders the quicksearch of
the contacts view of Kontact makes Kontact very busy until it is unusable.
Kontact can recover, and it can be closed but it will run with full cpu
power for a few minutes.

Architecture: powerpc
Source: kdepim
Version: 4:4.1.1.enterprise4.0.20090424.958783-kk1

How to reproduce here:
a) Switch to contact view
b) type a few characters (maybe delete and type a few again)
Observation: Kontact now needs all cpu-time
and will increasingly get slower and slower. (Takes a few seconds sometimes.)

----------
assignedto: allen
messages: 20298
nosy: allen, bernhard, ludwig, till
priority: urgent
status: unread
title: quick contact search busy loop freezes kontact
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3623>
___________________________________________________


From kolab-issues at intevation.de  Tue May 19 12:11:38 2009
From: kolab-issues at intevation.de (Mike Gabriel)
Date: Tue, 19 May 2009 10:11:38 +0000
Subject: [Kolab-devel] [issue3624] Freebusy: tentative events shown as free
Message-ID: <1242727898.75.0.188130603071.issue3624@intevation.de>


New submission from Mike Gabriel <m.gabriel at das-netzwerkteam.de>:

to my understanding tentative events should be shown as busy periods in
kolab/horde freebusy view.

if desired it needs to be changed in class: 

  Kolab_Event

in 

  Horde/Kolab/Freebusy/Imap.php

----------
messages: 20301
nosy: mike
status: unread
title: Freebusy: tentative events shown as free
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3624>
___________________________________________________


From kolab-issues at intevation.de  Tue May 19 13:33:18 2009
From: kolab-issues at intevation.de (Iban Ameneiros)
Date: Tue, 19 May 2009 11:33:18 +0000
Subject: [Kolab-devel] [issue3625] Recipient domain rewrited to "localhost"
Message-ID: <1242732798.21.0.918128346522.issue3625@intevation.de>


New submission from Iban Ameneiros <iba at ghesa.com>:

Yesterday i updated to version 2.2.2, since then kolabfilter ?? rewrites the
recipient addresses to "user at localhost". This is not a valid address so the mail
cannot be delivered, instead a returning message is sent to sender.

Here are my logs and part of the returning message


May 19 09:03:16 kolabfe <info> postfix/qmgr[4030]: 338B66AC001:
from=<aaa at external_domain.com>, size=116016, nrcpt=1 (queue active)
May 19 09:03:16 kolabfe <info> postfix/smtpd[7284]: disconnect from
localhost[127.0.0.1]
May 19 09:03:16 kolabfe <info> postfix/smtp[7281]: 9751F4C8452:
to=<bbb at localhost>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.62,
delays=0.02/0.01/0/0.59, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as
338B66AC001)
May 19 09:03:16 kolabfe <info> postfix/qmgr[4030]: 9751F4C8452: removed
May 19 09:03:19 kolabfe <info> postfix/smtp[7285]: 338B66AC001:
to=<bbb at localhost>, relay=mail.something.com[172.20.150.7]:25, delay=3,
delays=0.02/0.01/0.35/2.6, dsn=2.0.0, status=sent (250 Data received OK.)

Returning message:

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

bbb at localhost
   SMTP error: 550 5.1.1 <bbb at localhost>: Recipient address rejected: User
unknown in local recipient table

Any ideas?

----------
messages: 20304
nosy: iba
status: unread
title: Recipient domain rewrited to "localhost"
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3625>
___________________________________________________


From kolab-issues at intevation.de  Wed May 20 14:29:58 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 20 May 2009 12:29:58 +0000
Subject: [Kolab-devel] [issue3626] While updating kontact the settings get
	lost.
Message-ID: <1242822598.21.0.587815989344.issue3626@intevation.de>


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

enterprise4 windows 
Update from Kontact tag 20090508.965288 + kdelibs4.2 to Kontact tag
20090515.968370, but the settings got lost.

Test:
1. Install Kontact 20090508 to a test machine.
2. Use kolabwizard to configure an account.
3. Remove Kontact 20090508
4. Install Kontact 20090515
5. Look at the configurations.
=> The old settings got lost.
I expect that the account is still configured.

----------
assignedto: allen
messages: 20324
nosy: allen, bh, ludwig
priority: critical
status: unread
title: While updating kontact the settings get lost.
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3626>
___________________________________________________


From kolab-issues at intevation.de  Wed May 20 18:15:39 2009
From: kolab-issues at intevation.de (Thomas Ribbrock)
Date: Wed, 20 May 2009 16:15:39 +0000
Subject: [Kolab-devel] [issue3627] Restore "Default event color" as was
	present in proko2
Message-ID: <1242836139.62.0.987541910343.issue3627@intevation.de>


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

In the Calendar part (KOrganizer) of proko2, there used to be a "Default event
color" under Settings -> Colors. With this option, it was possible to define a
colour that would be applied to all events that do not have a category set, in
addition to the resource colour (never used it without resource colours, as I
was always using at least two resources).

In enterprise35, this option first got broken (i.e. did not have any effect
anymore - events without category suddenly were painted with a variation of the
corresponding resource colour instead of the default event colour), then later
partially removed (for a full history, please refer to issue2472 ), so it only
is used when no resource colours are used (AFAIK).

Given that this removes a very useful feature that was present in proko2 and
that there is no other way to make "category-less" events stand out while also
using resource colours, I would like to ask to re-introduce this feature in some
form in enterprise35 (and subsequent - never looked at e4 so far).

For some additional description and *one* possible idea for a solution, please
refer to msg17802 .

----------
messages: 20338
nosy: itsef_admin
priority: wish
status: unread
title: Restore "Default event color" as was present in proko2
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3627>
___________________________________________________


From kolab-issues at intevation.de  Thu May 21 19:35:08 2009
From: kolab-issues at intevation.de (Alar)
Date: Thu, 21 May 2009 17:35:08 +0000
Subject: [Kolab-devel] [issue3628] filter sessions
Message-ID: <1242927308.35.0.0491519855897.issue3628@intevation.de>


New submission from Alar <alar.sing at err.ee>:

Kolab/Filter/Base.php trys to start session, but why kolabfilter tasks does not
need this to do it's job.

filter.log fail shows

May 20 19:13:08 Kolab Filter [info] [horde] Horde_Kolab_Filter_Incoming
successfully completed (sender=alar at dyn.etv.ee, recipients=,
client_address=127.0.0.1,
id=<20090520191305.6028274hgeohuvi8 at linux-k21n.dyn.etv.ee>) [on line 141 of
"/usr/share/php5/PEAR/Horde/Kolab/Filter/Base.php"]
May 20 19:13:08 Kolab Filter [error] [horde] PHP Error: Unknown:
open(/var/lib/php5/sess_u93obs6pik5mk6l4cse3fh60vlufjv1u, O_RDWR) failed:
Permission denied (13); Code: 0 [on line 146 of
"/usr/share/php5/PEAR/Horde/Kolab/Filter/Response.php"]
May 20 19:13:08 Kolab Filter [error] [horde] PHP Error: Unknown: Failed to write
session data (files). Please verify that the current setting of
session.save_path is correct (/var/lib/php5); Code: 0 [on line 146 of
"/usr/share/php5/PEAR/Horde/Kolab/Filter/Response.php"]


This happens when I try do invite resource to event.
I have kolab native on opensuse
Versions
kolab-freebusy-0.1.5-4.5
kolab-server-0.5.0-4.1
kolab-format-1.0.1-2.5
kolab-storage-0.4.0-3.7
kolab-2.2.2-1.1
kolab-filter-0.1.5-3.1

----------
messages: 20340
nosy: arclyde, rbos
priority: bug
status: unread
title: filter sessions
topic: filter
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3628>
___________________________________________________


From kolab-issues at intevation.de  Thu May 21 19:49:05 2009
From: kolab-issues at intevation.de (Alar)
Date: Thu, 21 May 2009 17:49:05 +0000
Subject: [Kolab-devel] [issue3629] Php segaults when user invites resource
	to event.
Message-ID: <1242928145.64.0.394466028952.issue3629@intevation.de>


New submission from Alar <alar.sing at err.ee>:

Php segaults when user invites resource to event.
This happens when I invite a resource to my event. But what makes it strange is
that resource will send accept back to me. After I
have got bounce from postfix.
User who sends invite is alar at dyn.etv.ee and resource is kalender at dyn.etv.ee.
All the
logs are attached.
In messages I see
May 20 19:13:08 linux-k21n kernel: php5[27309]: segfault at 4c503d48 ip 081b0473 sp
bffbee6c error 4 in php5[8048000+23d000] 

How to make an php segfault:
First you create 2 Accounts in kolab webadmin. One with type User Account and
One with
type Resource Account, I selected Invitation Policy for Anyone to Reject if
conflicts but
it works with Always accept also.

After that is done you have to have webclient I do not have any other means to
test this
problem.

Log into the webclient whit User Account and locate Organixing->Calendar you
will see
This month calendar. On top of this page there is New Event click on that button.

Type in Title and Location, choose time from Time span and From Attendees->Edit
Attendees
add your Resource by typing Add attendees box its mail address and click Save or
Save and
Finish.
After that is done Click to Send invitations to all attendees? and Save Event.

This will take less than minute to get two mails first is the bounce and second
one is
response from resource.

I use native kolab on opensuse
Versions:
cyrus-imapd-kolab-2.3.13-63.1
perl-kolab-2.2.1.90_cvs20090503-1.3
kolab-freebusy-0.1.5-4.5
kolab-server-0.5.0-4.1
kolab-format-1.0.1-2.5
kolab-storage-0.4.0-3.7
kolab-2.2.2-1.1
imap-kolab-lib-2006c1_suse-71.3
php5-imap-kolab-5.2.9-1.1
kolab-webadmin-2.2.0.99_cvs20090222-2.10
kolab-filter-0.1.5-3.1
kolab-webclient-1.2-2.1

----------
files: mail.txt
messages: 20341
nosy: arclyde, rbos
priority: critical
status: unread
title: Php segaults when user invites resource to event.
topic: filter
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3629>
___________________________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: mail.txt
Url: http://kolab.org/pipermail/kolab-devel/attachments/20090521/4790bfea/mail.txt

From kolab-issues at intevation.de  Fri May 22 13:03:24 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Fri, 22 May 2009 11:03:24 +0000
Subject: [Kolab-devel] [issue3630] folder aren't displayed with threads,
	if the global option display with threads is set.
Message-ID: <1242990204.72.0.620612171949.issue3630@intevation.de>


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

enterprise4 windows 20090515.968370

Test:
Req: Some mails which belong to the same thread are in the inbox. The mails are
not displayed with threads.
1. Switch to the mail plugin.
2. Configure Mail->View->message list->display with threads.
3. Look at the message list.
=> The mails are not grouped into threads.
4. Deactivate and activate Folder->Use message threads.
=> Now the mails are grouped correctly.
I expect the mails list to be grouped into threads after step 3.

----------
assignedto: allen
messages: 20350
nosy: allen, bh, ludwig
priority: bug
status: unread
title: folder aren't displayed with threads, if the global option display with threads is set.
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3630>
___________________________________________________


From kolab-issues at intevation.de  Fri May 22 13:35:38 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Fri, 22 May 2009 11:35:38 +0000
Subject: [Kolab-devel] [issue3631] Mouse click cannot accept a selection
	from a mail address completion list
Message-ID: <1242992138.36.0.887785425775.issue3631@intevation.de>


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

tested with enterprise4 windows tag 20090515.968370

Test:
1. Switch to the mail plugin.
2. Start to create a new mail.
3. Type the first letters of a mail address into the "to:" field.
=> A popup list with this address appears.
4. Click on the selected address.
=> The letters in the "to:" field stay the same.
I expect the clicked on address to be in the "to:" field.

----------
assignedto: allen
messages: 20352
nosy: allen, bernhard, bh, ludwig
priority: urgent
status: unread
title: Mouse click cannot accept a selection from a mail address completion list
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3631>
___________________________________________________


From kolab-issues at intevation.de  Fri May 22 14:01:23 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Fri, 22 May 2009 12:01:23 +0000
Subject: [Kolab-devel] [issue3632] Plus left of the inbox,
	but no subfolder visible
Message-ID: <1242993682.83.0.112985461819.issue3632@intevation.de>


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

enterprise4 windows tag 20090515.968370

There is a plus/minus displayed left from the inbox, even when there only not
visible groupware folder in the inbox.
If no mail folder is in the inbox and hide groupware folder is activated, I
expect, that no plus or minus is displayed before the inbox in the folder view.

----------
assignedto: allen
messages: 20354
nosy: allen, bernhard, bh, ludwig
priority: minor bug
status: unread
title: Plus left of the inbox, but no subfolder visible
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3632>
___________________________________________________


From kolab-issues at intevation.de  Fri May 22 14:13:13 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Fri, 22 May 2009 12:13:13 +0000
Subject: [Kolab-devel] [issue3633] In the composer local distributions are
	not shown in the "select ..." button
Message-ID: <1242994392.99.0.743284590944.issue3633@intevation.de>


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

enterprise4 windows tag 20090515.968370

Test:
1. Create a test local distribution list.
2. Switch to the mail plugin.
3. Start to create a new mail.
=> composer opens.
4. Click on the "Select..." button right to the "to:"-field.
=> A address selection dialog opens. But in most cases this dialog doesn't 
contain the local distribution lists.
I expect that it is possible to select distribution lists with this dialog, too.

----------
assignedto: allen
messages: 20355
nosy: allen, bernhard, bh, ludwig
priority: bug
status: unread
title: In the composer local distributions are not shown in the "select ..." button
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3633>
___________________________________________________


From kolab-issues at intevation.de  Fri May 22 14:20:42 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Fri, 22 May 2009 12:20:42 +0000
Subject: [Kolab-devel] [issue3634] The semicolon cannot be used as mail
	address seperator anymore by default.
Message-ID: <1242994842.75.0.0862462224896.issue3634@intevation.de>


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

enterprise4 windows tag 20090515.968370

Test:
1. Start to create a new mail.
2. Enter into the "to:"-field two mail addresses seperated by a semicolon.
3. Send the mail.
=> A warning appears, that the mail is not valid, because of two @ in the   
   To-field and the mail is not send.
I expect, that by default the ; could also be used as address seperator.

----------
assignedto: allen
messages: 20357
nosy: allen, bh, ludwig
priority: bug
status: unread
title: The semicolon cannot be used as mail address seperator anymore by default.
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3634>
___________________________________________________


From kolab-issues at intevation.de  Fri May 22 14:27:33 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Fri, 22 May 2009 12:27:33 +0000
Subject: [Kolab-devel] [issue3635] A member of a distribution list without a
	full name gets lost
Message-ID: <1242995253.25.0.153217909593.issue3635@intevation.de>


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

enterprise4 windows tag 20090515.968370

Test:
1. Switch to the contacts plugin.
2. Create a new contact with an email address only
3. Start to create a local distribution list and add the mail-only contact.
4. Sync.
5. Open the test local dist list again.
=> the mail-only contact is gone from the dist list.
I expect for this contact to stay in the dist list.

----------
assignedto: allen
messages: 20358
nosy: allen, bh, ludwig
priority: urgent
status: unread
title: A member of a distribution list without a full name gets lost
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3635>
___________________________________________________


From kolab-issues at intevation.de  Mon May 25 12:19:34 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Mon, 25 May 2009 10:19:34 +0000
Subject: [Kolab-devel] [issue3636] After updating kontact,
	a bugus empty imap cache directory is created.
Message-ID: <1243246774.81.0.866584938379.issue3636@intevation.de>


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

Update enterprise35 20090430.961755 to e35 20090508.965262

After the update, sometimes an empty folder with 3 subfolders(cur,new,..) is
created under .kde/share/apps/kmail/imap/

This folder stops kontact from working.

----------
assignedto: allen
messages: 20367
nosy: allen, bh, ludwig
priority: urgent
status: unread
title: After updating kontact, a bugus empty imap cache directory is created.
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3636>
___________________________________________________


From kolab-issues at intevation.de  Mon May 25 14:15:20 2009
From: kolab-issues at intevation.de (Martin Zapfl)
Date: Mon, 25 May 2009 12:15:20 +0000
Subject: [Kolab-devel] [issue3637] Patch for displaying user quota and last
	login in userlist
Message-ID: <1243253720.25.0.115946421021.issue3637@intevation.de>


New submission from Martin Zapfl <mailinglists at tbits.net>:

This patch enhances the user list of Kolab Webadmin. After applying you can see
users mailbox quota and usage (if set). Also the date of last login will be
shown. This feature also requires some modifications of SASL fill the openLDAP
attribute (which may later be coded and be available as an separate patch).

Please note:
This is still a beta release. Do not install it on production machines!!

----------
assignedto: martinzapfl
files: userlist-patch.tgz
messages: 20370
nosy: martin, martinzapfl, thomas, wilde, wrobel
priority: feature
status: chatting
title: Patch for displaying user quota and last login in userlist
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3637>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: userlist-patch.tgz
Type: application/x-tar
Size: 3776 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090525/17e62f27/userlist-patch.tar

From kolab-issues at intevation.de  Mon May 25 14:53:49 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Mon, 25 May 2009 12:53:49 +0000
Subject: [Kolab-devel] [issue3638] At the logoff from the windows account,
	kwalletd doesn't stop and needs to be killed manually.
Message-ID: <1243256029.81.0.7882653418.issue3638@intevation.de>


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

enterprise4 windows 20090515.968370

Test:
1. Log in into the windows account.
2. Start kontact.
3. Close Kontact.
4. Logoff the windows account.
=> A windows dialog opens and informs the user, that a k... process doesn't
stop and asks, if the user wants to stop the process.
I manually killed the remaining kde processes and after removing kwalletd,
logoff works again. So I think the problem is the kwalletd process.

----------
assignedto: allen
messages: 20371
nosy: allen, bh, ludwig
priority: bug
status: unread
title: At the logoff from the windows account, kwalletd doesn't stop and needs to be killed manually.
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3638>
___________________________________________________


From kolab-issues at intevation.de  Mon May 25 16:36:34 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Mon, 25 May 2009 14:36:34 +0000
Subject: [Kolab-devel] [issue3639] kwallet dialog is in English
Message-ID: <1243262194.1.0.570535725693.issue3639@intevation.de>


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

enterprise4 windows tag 20090515.968370

The kwallet dialog is in English, while I expect it to be in GErman, because
German is configured as language.

Test:
1. Start kolabwizard.
2. Configure an account and choose to save the passwords.
=> A English kwallet pops up.

----------
assignedto: allen
messages: 20378
nosy: allen, bh, ludwig
priority: bug
status: unread
title: kwallet dialog is in English
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3639>
___________________________________________________


From kolab-issues at intevation.de  Mon May 25 16:44:49 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Mon, 25 May 2009 14:44:49 +0000
Subject: [Kolab-devel] [issue3640] If kontact is started,
	before it is configured by the kolabwizard an undeletable empty
	identity is added
Message-ID: <1243262689.63.0.223793237298.issue3640@intevation.de>


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

enterprise4 windows 20090515.968370

Test:
1. Login on a fresh windows account.
2. Start and close kontact.
3. Start the kolabwizard and configure an account.
4. Start kontact.
5. Open the kmail configuration dialog.
=> In the identity tab is a empty identity.
6. Delete this empty id.
7. Restart kontact.
8. Open the kmail configuration dialog.
=> This empty id is back again.

----------
assignedto: allen
messages: 20380
nosy: allen, bh, ludwig
priority: bug
status: unread
title: If kontact is started, before it is configured by the kolabwizard an undeletable empty identity is added
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3640>
___________________________________________________


From kolab-issues at intevation.de  Mon May 25 17:01:09 2009
From: kolab-issues at intevation.de (Martin Zapfl)
Date: Mon, 25 May 2009 15:01:09 +0000
Subject: [Kolab-devel] [issue3641] Patch for setting quotas per domain in
	kolab webadmin
Message-ID: <1243263669.51.0.53050474516.issue3641@intevation.de>


New submission from Martin Zapfl <mailinglists at tbits.net>:

This patch adds new quota features that can be set per domain.
You may restrict the following quota values:
Domain Quota: Restrict the useable disk space in MBytes for this domain
Domain Default Quota: the default / maximum quota space for accounts in this domain
Number of allowed accounts: Restrict the number of accounts created for this domain

This values can also be set as default values for newly create domains under the
new settings section Domain Default settings.

Please note:
This is still a beta release. Do not install it on production machines!!

----------
assignedto: martinzapfl
files: domainsettings-patch.tgz
messages: 20381
nosy: martin, martinzapfl, thomas, wilde, wrobel
priority: feature
status: chatting
title: Patch for setting quotas per domain in kolab webadmin
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3641>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: domainsettings-patch.tgz
Type: application/x-tar
Size: 6893 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090525/6058762b/domainsettings-patch-0001.tar

From kolab-issues at intevation.de  Mon May 25 17:02:30 2009
From: kolab-issues at intevation.de (Shrenik)
Date: Mon, 25 May 2009 15:02:30 +0000
Subject: [Kolab-devel] [issue3642] webclient - headers+show all headers does
	not work
Message-ID: <1243263749.87.0.776598840031.issue3642@intevation.de>


New submission from Shrenik <shrenik.bhura at intelliant.net>:

Platform: opensuse 11.1
kolab Packages:
perl-kolab-2.2.2.90_cvs20090521-1.1
kolab-server-0.5.0-4.1
kolab-filter-0.1.5-3.1
cyrus-imapd-kolab-2.3.13-63.1
kolab-storage-0.4.0-3.7
imap-kolab-lib-2006c1_suse-71.3
kolab-format-1.0.1-2.5
kolab-freebusy-0.1.5-4.5
php5-imap-kolab-5.2.9-1.1
kolab-webadmin-2.2.0.99_cvs20090222-2.11
kolab-webclient-1.2-2.1
kolab-2.2.2-2.1

view a mail - click on Headers -> Show All Headers results in the following error:

Requested message not found. However "Message Source" works fine hence serving
the purpose.
This is what it throws up in /srv/www/htdocs/client/log/horde.log
May 25 20:21:51 HORDE [debug] [nag] Hook _horde_hook_share_init in application
horde not called. [pid 694 on line 1683 of "/srv/www/htdocs/client/lib/Horde.php"]
May 25 20:21:51 HORDE [debug] [nag] Hook _prefs_change_hook_display_tasklists in
application horde not called. [pid 694 on line 1683 of
"/srv/www/htdocs/client/lib/Horde.php"]
May 25 20:21:51 HORDE [debug] [mnemo] Hook _horde_hook_share_init in application
horde not called. [pid 694 on line 1683 of "/srv/www/htdocs/client/lib/Horde.php"]
May 25 20:21:51 HORDE [debug] [mnemo] Hook _prefs_change_hook_display_notepads
in application horde not called. [pid 694 on line 1683 of
"/srv/www/htdocs/client/lib/Horde.php"]
May 25 20:21:51 HORDE [debug] [imp] SQL query by Horde_Alarm_sql::_list():
SELECT alarm_id, alarm_uid, alarm_start, alarm_end, alarm_methods, alarm_params,
alarm_title, alarm_text, alarm_snooze, alarm_internal FROM horde_alarms WHERE
alarm_dismissed = 0 AND ((alarm_snooze IS NULL AND alarm_start <= ?) OR
alarm_snooze <= ?) AND (alarm_end IS NULL OR alarm_end >= ?) AND (alarm_uid = ?
OR alarm_uid = ?) ORDER BY alarm_start, alarm_end [pid 694 on line 148 of
"/srv/www/htdocs/client/lib/Horde/Alarm/sql.php"]
May 25 20:21:51 HORDE [debug] [imp] Max memory usage: 12058624 bytes [pid 694 on
line 339 of "/srv/www/htdocs/client/lib/Horde/Registry.php"]
May 25 20:21:51 HORDE [debug] [imp] IMAP errors: SECURITY PROBLEM: insecure
server advertised AUTH=PLAIN SECURITY PROBLEM: insecure server advertised
AUTH=PLAIN [pid 694 on line 175 of "/srv/www/htdocs/client/imp/lib/IMAP.php"]

Do let me know if any other info may be required to nail this minor bug.

----------
messages: 20383
nosy: sbhura
priority: bug
status: unread
title: webclient - headers+show all headers does not work
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3642>
___________________________________________________


From kolab-issues at intevation.de  Mon May 25 19:36:04 2009
From: kolab-issues at intevation.de (Shrenik)
Date: Mon, 25 May 2009 17:36:04 +0000
Subject: [Kolab-devel] [issue3643] Unable to add INBOX/Contacts: destination
	folder already exists
Message-ID: <1243272962.49.0.452508246832.issue3643@intevation.de>


New submission from Shrenik <shrenik.bhura at intelliant.net>:

Logging into web-client results in this in the logs:
May 25 01:36:52 HORDE [error] [turba] Unable to add INBOX/Contacts: destination
folder already exists [pid 22223 on line 442 of
"/srv/www/htdocs/client/turba/lib/Turba.php"] 

Though it seems harmless as it doesn't cause any detected damage in the
front-end but yet it would be better to take it to the cleaners.

----------
messages: 20388
nosy: sbhura
priority: minor bug
status: unread
title: Unable to add INBOX/Contacts: destination folder already exists
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3643>
___________________________________________________


From kolab-issues at intevation.de  Tue May 26 12:43:41 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 26 May 2009 10:43:41 +0000
Subject: [Kolab-devel] [issue3644] After completion of a recurring to-do,
	the event isn't set to the next date of this to-do.
Message-ID: <1243334620.96.0.0294534131203.issue3644@intevation.de>


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

enterprise4 windows tag 20090515.968370

Test:
1. Switch to the to-do part.
2. Create a new to-do with recurrance.
3. Press on the complet button of the to-do
=> The to-do is completed.
I expect the date of the to-do switch to the next date and the to-do to be 0%,
because after this completion of the to-do, it should change to the next part of
the to-do.

----------
assignedto: allen
messages: 20393
nosy: allen, bh, ludwig
priority: bug
status: unread
title: After completion of a recurring to-do, the event isn't set to the next date of this to-do.
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3644>
___________________________________________________


From kolab-issues at intevation.de  Tue May 26 13:00:59 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 26 May 2009 11:00:59 +0000
Subject: [Kolab-devel] [issue3645] Export Calendar as Web Page: Unix
	end-of-lines are used.
Message-ID: <1243335658.94.0.895615299476.issue3645@intevation.de>


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

tested with enterprise4 windows 20090515.968370

An as webpage exported calendar contains Unix end-of-lines. I expect that in
this case Windows eols are used.

----------
assignedto: allen
messages: 20394
nosy: allen, bh, ludwig
priority: minor bug
status: unread
title: Export Calendar as Web Page: Unix end-of-lines are used.
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3645>
___________________________________________________


From kolab-issues at intevation.de  Tue May 26 14:40:54 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 26 May 2009 12:40:54 +0000
Subject: [Kolab-devel] [issue3646] Calendar: Search needs better default
	dates.
Message-ID: <1243341654.6.0.060729184196.issue3646@intevation.de>


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

tested with enterprise4 windows 20090515.968370

Test:
1. Switch to the calendar.
2. Edit-YSearch
=> The default dates are from: 20060928 to: 20060928.
I expect as default the selected days.

----------
assignedto: allen
messages: 20395
nosy: allen, bh, ludwig
priority: wish
status: unread
title: Calendar: Search needs better default dates.
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3646>
___________________________________________________


From kolab-issues at intevation.de  Tue May 26 15:00:34 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 26 May 2009 13:00:34 +0000
Subject: [Kolab-devel] [issue3647] Cannot enter a new file into a open file
	dialog.
Message-ID: <1243342833.61.0.232509102867.issue3647@intevation.de>


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

tested with enterprise4 windows 20090515.968370

Test:
1. Switch to the calendar
2. File->Export->Export as Webpage...
=> A export dialog opens.
3. Open the file dialog and enter a new file.
4. Press open.
=> A warning appears: The new entered file doesn't exist.
This doesn't work like expected. Why cannot the enter a new file here?

----------
assignedto: allen
messages: 20396
nosy: allen, bh, ludwig
priority: bug
status: unread
title: Cannot enter a new file into a open file dialog.
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3647>
___________________________________________________


From kolab-issues at intevation.de  Tue May 26 16:24:49 2009
From: kolab-issues at intevation.de (Marc Mutz)
Date: Tue, 26 May 2009 14:24:49 +0000
Subject: [Kolab-devel] [issue3648] KMail blocks in dimap "Getting quota
	information"
Message-ID: <1243347889.09.0.562334449983.issue3648@intevation.de>


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

KMail blocks for a short time on dimap mail sync when "getting quota 
information". It does not block on any of the other stages, afaics.

Here's how to reproduce:
1. Have another window open besides KMail to "test KMail window refresh" with:)
2. Start a dimap sync (CTRL-L)
3. Observe:
 - when circling another window slowly atop KMail's window, KMail usually
   redraws almost immediately, but _not_
 - when in "getting quota information" state for each folder, at which point
   the UI blocks.

This is unnerving when trying to interact with KMail in any other way 
(composing messages, dnd'ing).

----------
assignedto: allen
messages: 20398
nosy: allen, bernhard, marc, till
status: unread
title: KMail blocks in dimap "Getting quota information"
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3648>
___________________________________________________


From ml at radoeka.nl  Tue May 26 21:25:37 2009
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 26 May 2009 21:25:37 +0200
Subject: [Kolab-devel] Is comment on line 181 in kolabd/Makefile.am
	still valid?
In-Reply-To: <200905161652.43460.ml@radoeka.nl>
References: <200905161652.43460.ml@radoeka.nl>
Message-ID: <200905262125.38093.ml@radoeka.nl>

Op zaterdag 16 mei 2009 16:52:43 schreef Richard Bos:
> Hi,
>
> in kolabd/Makefile.am, the following lines are present:
> 181 # Please update the perl-kolab, kolab-webadmin and
> kolab-resource-handlers 182 # Makefile.ams too when the underneath
> EXTRA_DIST assignment is altered 184         dist_conf/debian \
> 185         dist_conf/kolab \
> 186         dist_conf/kolabsrv \
> 187         dist_conf/mandriva \
> 188         dist_conf/suse
>
>
> Are the comment lines (181 and 182) still valid?  kolab-resource-handlers
> is gone, so that can be removed.  But what about perl-kolab, is that still
> using the values from the dist_conf files?  I believe, it doesn't, hence
> the comment lines should become (I think):
>
> 181 # Please update the kolab-webadmin
> 182 # Makefile.am too when the underneath EXTRA_DIST assignment is altered
>
> Is this assumption correct?

No one?

-- 
Richard


From kolab-issues at intevation.de  Wed May 27 10:37:00 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 27 May 2009 08:37:00 +0000
Subject: [Kolab-devel] [issue3649] LDAP search: shift+left mouse button just
	selects one contacts
Message-ID: <1243413420.2.0.251085302922.issue3649@intevation.de>


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

enterprise35 20090522.971351

Test:
1. Switch to the contacts
2. Click on LDAP search.
3. Create a search which finds more than one contact.
4. Try to select with shift+lmb
=> Only one contact is selected. I expect the normal shift selection way here.

----------
assignedto: allen
messages: 20401
nosy: allen, bh, ludwig
priority: minor bug
status: unread
title: LDAP search: shift+left mouse button just selects one contacts
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3649>
___________________________________________________


From kolab-issues at intevation.de  Wed May 27 17:10:39 2009
From: kolab-issues at intevation.de (=?utf-8?q?Daniel_Wr=C3=B3bel?=)
Date: Wed, 27 May 2009 15:10:39 +0000
Subject: [Kolab-devel] [issue3650] Emails don't appear in mailboxes.
Message-ID: <1243437039.4.0.697511974166.issue3650@intevation.de>


New submission from Daniel Wr?bel <daniel.wrobel at kopex.com.pl>:

Hello Guys,

I have Kolab 2.2.0 running on FreeBSD 7.1 Release i386. Users are complaining
that they they don't receive emails. I looked through logs postfix.log,
amavsid.log all looks fine, but in log /var/log/messages i can see:
kernel: pid 4049 (lmtpd), uid 19415: exited on signal 11
kernel: pid 4974 (imapd), uid 19415: exited on signal 11
kernel: pid 5083 (lmtpd), uid 19415: exited on signal 11
kernel: pid 5099 (lmtpd), uid 19415: exited on signal 11
kernel: pid 6281 (lmtpd), uid 19415: exited on signal 11
kernel: pid 6282 (lmtpd), uid 19415: exited on signal 11
kernel: pid 6396 (lmtpd), uid 19415: exited on signal 11
kernel: pid 6637 (lmtpd), uid 19415: exited on signal 11

I would be grateful if you could help me. I'm looking forward for your answer.

Regards,
 Sparrow

----------
messages: 20411
nosy: sparrow
status: unread
title: Emails don't appear in mailboxes.
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3650>
___________________________________________________


From kolab-issues at intevation.de  Thu May 28 13:01:02 2009
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Thu, 28 May 2009 11:01:02 +0000
Subject: [Kolab-devel] [issue3651] Forwarding as text (inline) misses
	attachment with encrypted email
Message-ID: <1243508461.98.0.0764683904079.issue3651@intevation.de>


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

Architecture: i386
Source: kdepim
Version: 4:3.5.10.enterprise.0.20090508.965262-kk1

I have a OpenPGP encrypted email here with attachment.
Using "forwarding as text" the attachement is missing.

Ludwig, please reproduce with current version and create an encrypted
email showing the problem with a publically available key.
Also check S/MIME, thanks.

----------
assignedto: ludwig
messages: 20418
nosy: allen, bernhard, ludwig
priority: bug
status: need-eg
title: Forwarding as text (inline) misses attachment with encrypted email
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3651>
___________________________________________________


From kolab-issues at intevation.de  Thu May 28 15:20:58 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 28 May 2009 13:20:58 +0000
Subject: [Kolab-devel] [issue3652] Contacts: Enter contacts to a
	distribution list is inconsistent
Message-ID: <1243516858.72.0.0706658844812.issue3652@intevation.de>


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

enterprise4 windows 20090515.968370

Test:
1. Start to create a dist list.
2. Enter different contacts and press Return
=> Normally the cursor jumps to the next blank field, but sometimes the dist
list editor just closes with okay.

----------
assignedto: allen
messages: 20419
nosy: allen, bh, ludwig
priority: bug
status: unread
title: Contacts: Enter contacts to a distribution list is inconsistent
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3652>
___________________________________________________


From kolab-issues at intevation.de  Thu May 28 15:33:56 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 28 May 2009 13:33:56 +0000
Subject: [Kolab-devel] [issue3653] contact: Click on a blue mail-address
	opens OL express
Message-ID: <1243517636.79.0.872650790237.issue3653@intevation.de>


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

enterprise4 windows 20090515.968370

Test:
1. Switch to contacts.
2. Look at the details of a contact with mail address.
3. Click on the mail address link.
=> OL Express starts.
I expect the composer to be used in this case.

----------
assignedto: allen
messages: 20421
nosy: allen, bh, ludwig
priority: bug
status: unread
title: contact: Click on a blue mail-address opens OL express
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3653>
___________________________________________________


From kolab-issues at intevation.de  Fri May 29 11:23:51 2009
From: kolab-issues at intevation.de (jean-pierre cartal)
Date: Fri, 29 May 2009 09:23:51 +0000
Subject: [Kolab-devel] [issue3654] vacation message problem
Message-ID: <1243589030.45.0.660652099701.issue3654@intevation.de>


New submission from jean-pierre cartal <jean-pierre.cartal at rld.fr>:

When creating a vacation message through web interface, Kolab automatically add
\ before all ' characters.
Clicking several times on the update button add several \.
E.g. :
initial entered text : jusqu'au
1st update click => jusqu\'au
2nd update click => jusqu\\\'au
...

Regards.

----------
messages: 20429
nosy: jpcartal
priority: urgent
status: unread
title: vacation message problem
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3654>
___________________________________________________


From kolab-issues at intevation.de  Fri May 29 12:17:53 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Fri, 29 May 2009 10:17:53 +0000
Subject: [Kolab-devel] [issue3655] LDAP search of the composer doesn't work
	with two servers.
Message-ID: <1243592273.26.0.53090516224.issue3655@intevation.de>


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

enterprise4 windows 20090515.968370

Test:
Req: Two different LDAP servers that provide contacts
1. Open Configure Contacts -> LDAP-search
2. Add both servers.
3. Switch to the mail parts.
4. Start to create a new mail.
5. Look for an address of each server.
=> It is not possible to find a address of the second server.
I expect mail addresses from both LDAP server to be searchable.

----------
assignedto: allen
messages: 20432
nosy: allen, bh, ludwig
priority: bug
status: unread
title: LDAP search of the composer doesn't work with two servers.
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3655>
___________________________________________________


From kolab-issues at intevation.de  Fri May 29 13:45:22 2009
From: kolab-issues at intevation.de (Smooph)
Date: Fri, 29 May 2009 11:45:22 +0000
Subject: [Kolab-devel] [issue3656] Unable to SyncML Calendar / PHP Fatal
	error compareDateTime()
Message-ID: <1243597522.41.0.980755251339.issue3656@intevation.de>


New submission from Smooph <webmaster at computational-chemistry.org>:

> > > >> Now I read on the mailing list that it should work. So I checked the
> > > >> logs for errors that only happen when I sync stuff. And this is the
> > > >> one I found in the /kolab/var/kolab/www/client/log/php-errors.log
> > > >>
> > > >> "PHP Fatal error :  Call to a member function compareDateTime() on a
> > > >> non- object in
> > > >> /kolab/var/kolab/www/client/kronolith/lib/Driver/kolab.php on line
> > > >> 1153"
> > > >
> > > > Same on my Side with Kolab 2.2.1 native on OpenSUSE-11.1.
> > > > My Client is a Blackberry 8300 Curve with actual Funambol-Plugin.
> > > >
> > >
> > > Not a real solution but according to the error I'd say that either
> > > $endDate or $startDate is not defined and not recognized as a date
> > > object. Maybe a null check should be sufficient?
> > >
> > >
> > > Carsten
> >
> > OK, thanks for the Tip.
> >
> > I have now made changes as follow on those lines:
> >
> > Line 1137
> > ---------------------------
> > if (is_null($startDate)) {
> > ----------------------------
> > to
> > ----------------------------
> > if (empty($startDate)) {
> > -----------------------------
> >
> > and Line 1140
> > -----------------------------
> > if (is_null($endDate)) {
> > ----------------------------
> > to
> > -----------------------------
> > if (empty($endDate)) {
> > -----------------------------
> >
> > and now it syncs without my stupid comment out of lines 1153 and 1154.
> >
> > But i do not now this is the right way to solve that problem.
> >
> > Thomas
>
> I have been testing this for the last couple of days and I didn't get an
> error. For me the issue is fixed, but of course it would be nice to have a
> developer or somebody who knows the code doublecheck everything and give
> some feedback.
>
> Is there a way to let the guys from Horde know about this issue? So they
> can fix it too.
>
>Regards Smooph

----------
messages: 20433
nosy: smooph
priority: bug
status: resolved
title: Unable to SyncML Calendar / PHP Fatal error compareDateTime()
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3656>
___________________________________________________


From kolab-issues at intevation.de  Fri May 29 13:48:59 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Fri, 29 May 2009 11:48:59 +0000
Subject: [Kolab-devel] [issue3657] Some English fields names in a create
	contact dialog.
Message-ID: <1243597739.22.0.473038034343.issue3657@intevation.de>


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

enterprise4 windows 20090516.968370

I have configured Kontact to use German, but in the "Create contact" dialog are
some fields not translated:
Role, Home/Work/Mobile in the phone field, Home/Work in the address field,
appointment categories, details->Title

----------
assignedto: allen
messages: 20434
nosy: allen, bh, ludwig
priority: bug
status: unread
title: Some English fields names in a create contact dialog.
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3657>
___________________________________________________


From kolab-issues at intevation.de  Fri May 29 14:13:13 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Fri, 29 May 2009 12:13:13 +0000
Subject: [Kolab-devel] [issue3658] Changing the name of a calendar
	subresource leads to crash
Message-ID: <1243599193.57.0.180581989294.issue3658@intevation.de>


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

enterprise4 windows 20090515.968370

----------
assignedto: allen
messages: 20435
nosy: allen, bh, ludwig
priority: urgent
status: unread
title: Changing the name of a calendar subresource leads to crash
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3658>
___________________________________________________


From kolab-issues at intevation.de  Fri May 29 14:26:23 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Fri, 29 May 2009 12:26:23 +0000
Subject: [Kolab-devel] [issue3659] Side-by-side view is not shown after the
	configuration of it.
Message-ID: <1243599983.86.0.267411685263.issue3659@intevation.de>


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

enterprise4 windows 20090515.968370

Test:
Req: 2 or more calendar resources
1. Switch to the calendar.
2. Configure in the dayview: side-by-side view.
3. Look at the calendar.
=> The display of the calendar hasn't changed. The user needs to switch to the
monthview and back to get the side-by-side view.
I expect after the configuration the change of the view.

----------
assignedto: allen
messages: 20437
nosy: allen, bh, ludwig
priority: bug
status: unread
title: Side-by-side view is not shown after the configuration of it.
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3659>
___________________________________________________


From kolab-issues at intevation.de  Fri May 29 21:29:25 2009
From: kolab-issues at intevation.de (John McMonagle)
Date: Fri, 29 May 2009 19:29:25 +0000
Subject: [Kolab-devel] [issue3660] only one url works for kolab.conf ldap_uri
Message-ID: <1243625365.24.0.279950071228.issue3660@intevation.de>


New submission from John McMonagle <johnm at advocap.org>:

If I put in this in kolab.conf
ldap_uri : ldap://127.0.0.1:389 ldaps://mstldap.advocap.org:636

It gets parsed wrong.

For example gives in apache.conf
AuthLDAPURL ldap://127.0.0.1 ldaps::389/dc=advocap,dc=org?mail
Pretty sure should be
AuthLDAPURL ldap://127.0.0.1:389
ldaps://mstldap.advocap.org:636/dc=advocap,dc=org?mail

For reference see 
http://httpd.apache.org/docs/2.0/mod/mod_auth_ldap.html#authldapurl

In my old mail server was set up that way.
for example in saslauthd.conf have
ldap_servers: ldapi:///var/run/ldapi ldaps://fonldap.advocap.org ldaps://mstlda
p.advocap.org

a postfix ldap map has:
server_host = ldap://127.0.0.1 ldap://mstldap.advocap.org ldap//fonldap.advocap.org

Not certain but suspect all ldap clients will accept multiple servers.

If one has more than one available ldap server things keep running even if a
ldap server fails for some reason.

My biggest concern is mail being bounced by postfix because of an ldap failure.

John

----------
messages: 20444
nosy: jmcmonagle
status: unread
title: only one url works for kolab.conf ldap_uri
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3660>
___________________________________________________


From martin.konold at erfrakon.de  Sat May 30 19:06:49 2009
From: martin.konold at erfrakon.de (Martin Konold)
Date: Sat, 30 May 2009 19:06:49 +0200
Subject: [Kolab-devel] handling of private events in kolab clients
In-Reply-To: <200905181014.43286.bernhard@intevation.de>
References: <20090511184740.54005x2xd8dk6u98@mail.das-netzwerkteam.de>
	<200905181014.43286.bernhard@intevation.de>
Message-ID: <200905301906.51135.martin.konold@erfrakon.de>

On Monday 18 May 2009 10:14:42 Bernhard Reiter wrote:

Hi Mike,
Hi Bernhard,

> On Monday 11 May 2009, Mike Gabriel wrote:
> > could there be an intermediate solution (hiding event details in the
> > Outlook GUI)?
>
> No, this wouldn't be secure.

Well, the current situation (since years!) is that Outlook users with a Kolab 
server can set the privacy flag in the UI but it is not honoured in the UI 
when the event is read by someone else.

This against the intuitive expectation of our users and a disadvantage of 
Kolab compared to MS Exchange.

> Data that needs to be kept secure from the client must not be
> transfered to the client in the first place.

This is not entirely true. It is sufficient of the client cannot decrypt the 
private data.

> Just hiding stuff in the user interface (like Outlook does  at least in
> some versions as far as I know) is not a real solution.

Well, it is better than nothing and helps to protect the privacy in a 
practical manner.

From a MS point of view there is a difference between a private and a 
confidential message.

I therefore asked the KONSEC developers to implement the privacy functionality 
with an Exchange compatible semantic in the KONSEC Konnektor in order to gain 
a real world feeling about the feasability of this task.

In the meantime they delivered a preview version of the KONSEC Konnektor which 
offers support for the privacy feature. 

KONSEC also plana to release this to the public in the future.

Anyone interested in having a look at the preview may write me a personal mail 
and I will provide you with a download URL.

Currently this version of the KONSEC Konnektor (which is a MAPI Storage 
Provider) denies Outlook access to the protected elements of a MAPI object 
according to:

- privacy flag
- IMAP administration rights which also represent effective control and 
ownership (ACL)
- IMAP read permission (ACL)
- IMAP write permission (ACL)

If the privacy flag is set and the user is lacking ownership the MAPI Storage 
Provider denies Outlook access to the private properties (texts etc.) while 
allowing access to public properties like begin and end datetime and also 
denies changing/copying/moving of the private object. (This is equivalent to 
how the privacy flag is handled by OL/EX)

As a next step I will come up with a proposal how to properly improve the 
current system using proper encryption.

The current implementation relies upon enforcement of the access control to 
private objects in the MAPI Storage Provider. From the point of view of 
Outlook this MAPI Storage Provide is a server but from a security point of 
view the MSP is still running in the context of the client workstation not of 
the Kolab server.

IMHO this simple Exchange compatible approach is already a big improvement 
compared to simply not addressing this issue. I expect a number of people are 
already fine with this implementation. (****)

In the future I want to have proper cryptographic methods used. Though this is 
not trivial to get right.

- Owners of a private object are all those Kolab users with adminstrative 
privileges on the corresponing folder.

- Only Owners can create, copy, move and delete private objects.

- If non-Owners with write permissions create such objects they effectivly 
either loose control (what MS Exchange does) or the flag is removed by the 
Connector/Konnektor when storing. The Middleware might decide to warn the user 
about this.

- Private properties within a private object are encrypted  and decrypted 
using a folder specific symmetric key.

- Only Kolab users with 

- The distribution/maintenance of this symmetric(***) key is non-trivial

- The basic idea is that the folder specific symmetric key is ONLY available 
to those users with administration priviledges on this folder. (I am currently 
not sure how this is implemented best) (*)

- Whenever someone is removed from the list of users with administrative 
priviledges from the folder ALL private objects need to be reencrypted with a 
newly created symmetric key. (**)

(*) I am wondering how this is to be implemented. 
The main point is that this is slowly changing folder specific information 
which shall only be available to users with adminstrative priviledges.
Does anyone have a great idea how this can be implemented?

(**) Due to the inherent incoherent nature of Kolab (offline clients etc.) we 
must beware of race conditions and provide a mechanism to avoid these. (This 
is solvable though!)

(***) Choosing a symmetric key method is simple but has some drawbacks. E.g. 
it does not protect from a malicious server/backup administrator. I consider 
this acceptable though as long as it is well documented.

(****) Of course the current implementation can trivially be subverted using a 
client which does not honour the privacy flag. As a first step I will 
therefore ask the KONSEC developers to encrypt all private properties using a 
single static key (no key management in the first step). This denies access to 
all non complying clients. Extraction of this hidden key from the proprietary 
Konnektor is possible though really not trivial.

I am looking forward to your feedback.

Yours,
-- martin

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

From mangoo at wpkg.org  Sun May 31 02:23:42 2009
From: mangoo at wpkg.org (Tomasz Chmielewski)
Date: Sun, 31 May 2009 02:23:42 +0200
Subject: [Kolab-devel] why not ship Kolab with Samba by default?
Message-ID: <4A21CE0E.8060307@wpkg.org>

Was shipping Samba with Kolab by default ever considered?

It would add great value to Kolab; right now, it's a bit painful to 
configure both to work together.

-- 
Tomasz Chmielewski
http://wpkg.org


From martin.konold at erfrakon.de  Sun May 31 11:34:22 2009
From: martin.konold at erfrakon.de (Martin Konold)
Date: Sun, 31 May 2009 11:34:22 +0200
Subject: [Kolab-devel] why not ship Kolab with Samba by default?
In-Reply-To: <4A21CE0E.8060307@wpkg.org>
References: <4A21CE0E.8060307@wpkg.org>
Message-ID: <200905311134.23171.martin.konold@erfrakon.de>

On Sunday 31 May 2009 02:23:42 Tomasz Chmielewski wrote:

Hi Tomasz,

> Was shipping Samba with Kolab by default ever considered?
>
> It would add great value to Kolab; right now, it's a bit painful to
> configure both to work together.

Well, I considered it several times. I came to the conclusion that we need a 
desperate use case within Kolab in order to justify the added complexity and 
loss of scope (we target for Groupware mainly).

On the other hand I am more than willing to support an infrastructure which 
makes it easier to integrate with Samba.

What was the biggest hurdle/pain when you tried to integrate Samba with Kolab?

Yours,
-- martin

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

From mangoo at wpkg.org  Sun May 31 12:21:22 2009
From: mangoo at wpkg.org (Tomasz Chmielewski)
Date: Sun, 31 May 2009 12:21:22 +0200
Subject: [Kolab-devel] why not ship Kolab with Samba by default?
In-Reply-To: <200905311134.23171.martin.konold@erfrakon.de>
References: <4A21CE0E.8060307@wpkg.org>
	<200905311134.23171.martin.konold@erfrakon.de>
Message-ID: <4A225A22.3030400@wpkg.org>

Martin Konold wrote:
> On Sunday 31 May 2009 02:23:42 Tomasz Chmielewski wrote:
> 
> Hi Tomasz,
> 
>  > Was shipping Samba with Kolab by default ever considered?
> 
>  >
> 
>  > It would add great value to Kolab; right now, it's a bit painful to
> 
>  > configure both to work together.
> 
> Well, I considered it several times. I came to the conclusion that we 
> need a desperate use case within Kolab in order to justify the added 
> complexity and loss of scope (we target for Groupware mainly).

Now with multi-domain support (well, even without it), Kolab could 
target some Exchange installations.
There are dozens of groupware solutions; there is no direct Exchange 
equivalent which would be easy to configure.


> On the other hand I am more than willing to support an infrastructure 
> which makes it easier to integrate with Samba.
> 
> What was the biggest hurdle/pain when you tried to integrate Samba with 
> Kolab?

There are some problems involved with it:

* Kolab's web interface is not compatible with Samba (i.e. it doesn't 
add some required LDAP attributes for Samba) - so you have to use a 
different webgui for adding users: LAM (LDAP Account Manager)

* current LAM release needs php-hash extension, which is not available 
with Kolab; I have no idea how one adds custom PHP extensions to Kolab 
(or perhaps, OpenPKG). Which leaves me two choices:
   - don't use Apache shipped with Kolab, but the one shipped with the 
distribution
   - use an old LAM release, which doesn't need hash extension

* overall, such process is overly complicated; would be great if one 
could, during Kolab bootstrapping, just choose to add Samba domain 
controller, and everything would work flawlessly from scratch


BTW, I committed a Kolab-Samba integration HOWTO a few years ago - 
http://wpkg.org/kolab - now slightly outdated for Kolab 2.2.x.


-- 
Tomasz Chmielewski


From ml at radoeka.nl  Sun May 31 12:29:59 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sun, 31 May 2009 12:29:59 +0200
Subject: [Kolab-devel] why not ship Kolab with Samba by default?
In-Reply-To: <4A225A22.3030400@wpkg.org>
References: <4A21CE0E.8060307@wpkg.org>
	<200905311134.23171.martin.konold@erfrakon.de>
	<4A225A22.3030400@wpkg.org>
Message-ID: <200905311229.59855.ml@radoeka.nl>

Op zondag 31 mei 2009 12:21:22 schreef Tomasz Chmielewski:
> BTW, I committed a Kolab-Samba integration HOWTO a few years ago -
> http://wpkg.org/kolab - now slightly outdated for Kolab 2.2.x.

All samba related efforts are collected on this wiki page:
http://wiki.kolab.org/index.php/Samba_PDC_and_Kolab_Server
As you can see there is also an issue for this.  Have a look at it, for the 
latest status information about support within kolab....

-- 
Richard


From mangoo at wpkg.org  Sun May 31 12:37:56 2009
From: mangoo at wpkg.org (Tomasz Chmielewski)
Date: Sun, 31 May 2009 12:37:56 +0200
Subject: [Kolab-devel] why not ship Kolab with Samba by default?
In-Reply-To: <200905311229.59855.ml@radoeka.nl>
References: <4A21CE0E.8060307@wpkg.org>
	<200905311134.23171.martin.konold@erfrakon.de>
	<4A225A22.3030400@wpkg.org> <200905311229.59855.ml@radoeka.nl>
Message-ID: <4A225E04.6060501@wpkg.org>

Richard Bos wrote:
> Op zondag 31 mei 2009 12:21:22 schreef Tomasz Chmielewski:
>> BTW, I committed a Kolab-Samba integration HOWTO a few years ago -
>> http://wpkg.org/kolab - now slightly outdated for Kolab 2.2.x.
> 
> All samba related efforts are collected on this wiki page:
> http://wiki.kolab.org/index.php/Samba_PDC_and_Kolab_Server
> As you can see there is also an issue for this.  Have a look at it, for the 
> latest status information about support within kolab....

Yes, I am able to add Samba support to Kolab myself, but many people aren't.

Having Samba support in Kolab by default could greatly increase Kolab's 
userbase, I think.


-- 
Tomasz Chmielewski
http://wpkg.org


From ml at radoeka.nl  Sun May 31 14:48:19 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sun, 31 May 2009 14:48:19 +0200
Subject: [Kolab-devel] why not ship Kolab with Samba by default?
In-Reply-To: <4A225E04.6060501@wpkg.org>
References: <4A21CE0E.8060307@wpkg.org> <200905311229.59855.ml@radoeka.nl>
	<4A225E04.6060501@wpkg.org>
Message-ID: <200905311448.21026.ml@radoeka.nl>

Op zondag 31 mei 2009 12:37:56 schreef Tomasz Chmielewski:
> Richard Bos wrote:
> > Op zondag 31 mei 2009 12:21:22 schreef Tomasz Chmielewski:
> >> BTW, I committed a Kolab-Samba integration HOWTO a few years ago -
> >> http://wpkg.org/kolab - now slightly outdated for Kolab 2.2.x.
> >
> > All samba related efforts are collected on this wiki page:
> > http://wiki.kolab.org/index.php/Samba_PDC_and_Kolab_Server
> > As you can see there is also an issue for this.  Have a look at it, for
> > the latest status information about support within kolab....
>
> Yes, I am able to add Samba support to Kolab myself, but many people
> aren't.
>
> Having Samba support in Kolab by default could greatly increase Kolab's
> userbase, I think.

I only wanted to tell that other people feel the same like you about samba 
support.  They opened an issue about and provided code, that can be included 
in kolab, but sofar that is about it.

-- 
Richard


From mangoo at wpkg.org  Sun May 31 15:11:41 2009
From: mangoo at wpkg.org (Tomasz Chmielewski)
Date: Sun, 31 May 2009 15:11:41 +0200
Subject: [Kolab-devel] why not ship Kolab with Samba by default?
In-Reply-To: <200905311448.21026.ml@radoeka.nl>
References: <4A21CE0E.8060307@wpkg.org> <200905311229.59855.ml@radoeka.nl>
	<4A225E04.6060501@wpkg.org> <200905311448.21026.ml@radoeka.nl>
Message-ID: <4A22820D.4040301@wpkg.org>

Richard Bos wrote:
> Op zondag 31 mei 2009 12:37:56 schreef Tomasz Chmielewski:
>> Richard Bos wrote:
>>> Op zondag 31 mei 2009 12:21:22 schreef Tomasz Chmielewski:
>>>> BTW, I committed a Kolab-Samba integration HOWTO a few years ago -
>>>> http://wpkg.org/kolab - now slightly outdated for Kolab 2.2.x.
>>> All samba related efforts are collected on this wiki page:
>>> http://wiki.kolab.org/index.php/Samba_PDC_and_Kolab_Server
>>> As you can see there is also an issue for this.  Have a look at it, for
>>> the latest status information about support within kolab....
>> Yes, I am able to add Samba support to Kolab myself, but many people
>> aren't.
>>
>> Having Samba support in Kolab by default could greatly increase Kolab's
>> userbase, I think.
> 
> I only wanted to tell that other people feel the same like you about samba 
> support.  They opened an issue about and provided code, that can be included 
> in kolab, but sofar that is about it.

Are there any technical arguments against it (besides additional 
maintenance burden)?

The changes are not intrusive, and Samba domain controller could be an 
option, not enabled by default (like Horde is now).

-- 
Tomasz Chmielewski
http://wpkg.org


From ml at radoeka.nl  Sun May 31 15:31:21 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sun, 31 May 2009 15:31:21 +0200
Subject: [Kolab-devel] why not ship Kolab with Samba by default?
In-Reply-To: <4A22820D.4040301@wpkg.org>
References: <4A21CE0E.8060307@wpkg.org> <200905311448.21026.ml@radoeka.nl>
	<4A22820D.4040301@wpkg.org>
Message-ID: <200905311531.23436.ml@radoeka.nl>

Op zondag 31 mei 2009 15:11:41 schreef Tomasz Chmielewski:
> Are there any technical arguments against it (besides additional
> maintenance burden)?

I believe that the maintenance burden is one reason, another one is testing 
for a release and that there is not yet a customer that requires this 
functionality.  Another thing is that I think that the kolab core developers 
would like this to be supported via a plugin architecture.  This isn't there 
yet and as such it needs to be developed.  When this feature is indeed 
supported via plugin architecture the maintenance burden and testing effort 
for a release are indeed no longer a part of the core developers 
responsibility.  Perhaps you can also read this in issue 2997 
https://www.intevation.de/roundup/kolab/issue2997

-- 
Richard


From martin.konold at erfrakon.de  Sun May 31 15:33:39 2009
From: martin.konold at erfrakon.de (Martin Konold)
Date: Sun, 31 May 2009 15:33:39 +0200
Subject: [Kolab-devel] why not ship Kolab with Samba by default?
In-Reply-To: <4A22820D.4040301@wpkg.org>
References: <4A21CE0E.8060307@wpkg.org> <200905311448.21026.ml@radoeka.nl>
	<4A22820D.4040301@wpkg.org>
Message-ID: <200905311533.40371.martin.konold@erfrakon.de>

On Sunday 31 May 2009 15:11:41 Tomasz Chmielewski wrote:

Hi Tomasz,

> >> Having Samba support in Kolab by default could greatly increase Kolab's
> >> userbase, I think.
> >
> > I only wanted to tell that other people feel the same like you about
> > samba support.  They opened an issue about and provided code, that can be
> > included in kolab, but sofar that is about it.
>
> Are there any technical arguments against it (besides additional
> maintenance burden)?
>
> The changes are not intrusive, and Samba domain controller could be an
> option, not enabled by default (like Horde is now).

I am afraid that people start to think that Kolab is the perfect Samba 
solution and therefore many Samba related support request(*) start popping up.

Yours,
-- martin
(*) As soon as you start using samba for non trivial purposes including PDC, 
BDC, printer driver, printing and ACLs things become hairy for the plain 
reason that Samba tries to offer a mapping between unix/posix and Windows with 
regards to these properties. 
It is simply IMPOSSIBLE to get such a mapping right in all corner cases. E.g. 
there is no sufficently good counterpart to SIDs. Windows ACLs are very 
different from POSIX ACLs,....

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

From mangoo at wpkg.org  Sun May 31 15:50:45 2009
From: mangoo at wpkg.org (Tomasz Chmielewski)
Date: Sun, 31 May 2009 15:50:45 +0200
Subject: [Kolab-devel] why not ship Kolab with Samba by default?
In-Reply-To: <200905311533.40371.martin.konold@erfrakon.de>
References: <4A21CE0E.8060307@wpkg.org> <200905311448.21026.ml@radoeka.nl>
	<4A22820D.4040301@wpkg.org>
	<200905311533.40371.martin.konold@erfrakon.de>
Message-ID: <4A228B35.6080507@wpkg.org>

Martin Konold wrote:

>  > option, not enabled by default (like Horde is now).
> 
> I am afraid that people start to think that Kolab is the perfect Samba 
> solution and therefore many Samba related support request(*) start 
> popping up.
> 
> Yours,
> 
> -- martin
> 
> (*) As soon as you start using samba for non trivial purposes including 
> PDC, BDC, printer driver, printing and ACLs things become hairy for the 
> plain reason that Samba tries to offer a mapping between unix/posix and 
> Windows with regards to these properties.
> 
> It is simply IMPOSSIBLE to get such a mapping right in all corner cases. 
> E.g. there is no sufficently good counterpart to SIDs. Windows ACLs are 
> very different from POSIX ACLs,....

There is a good list which deals with Samba: lists.samba.org. Just 
teach/tell users to use it.

And if you're talking about commercial support, it's a good opportunity 
to earn additional money.

Do you have many support questions regarding Apache, Postfix, OpenLDAP 
or Cyrus?

-- 
Tomasz Chmielewski
http://wpkg.org



From martin.konold at erfrakon.de  Sun May 31 16:46:41 2009
From: martin.konold at erfrakon.de (Martin Konold)
Date: Sun, 31 May 2009 16:46:41 +0200
Subject: [Kolab-devel] why not ship Kolab with Samba by default?
In-Reply-To: <4A228B35.6080507@wpkg.org>
References: <4A21CE0E.8060307@wpkg.org>
	<200905311533.40371.martin.konold@erfrakon.de>
	<4A228B35.6080507@wpkg.org>
Message-ID: <200905311646.41679.martin.konold@erfrakon.de>

On Sunday 31 May 2009 15:50:45 Tomasz Chmielewski wrote:

Hi,

> Do you have many support questions regarding 
> Apache,

rarely

> Postfix,

somtimes

> OpenLDAP

often

> or Cyrus?

often

Yours,
-- martin

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

From martin.konold at erfrakon.de  Sun May 31 16:49:24 2009
From: martin.konold at erfrakon.de (Martin Konold)
Date: Sun, 31 May 2009 16:49:24 +0200
Subject: [Kolab-devel] why not ship Kolab with Samba by default?
In-Reply-To: <4A225A22.3030400@wpkg.org>
References: <4A21CE0E.8060307@wpkg.org>
	<200905311134.23171.martin.konold@erfrakon.de>
	<4A225A22.3030400@wpkg.org>
Message-ID: <200905311649.25253.martin.konold@erfrakon.de>

On Sunday 31 May 2009 12:21:22 Tomasz Chmielewski wrote:

Hi,

> * Kolab's web interface is not compatible with Samba (i.e. it doesn't
> add some required LDAP attributes for Samba) - so you have to use a
> different webgui for adding users: LAM (LDAP Account Manager)

Is it incompatible or simple lacking to expose some attributes?
If it is the later we may consider to makeing them optionally available via 
the Kolab webadmin tool.

> * current LAM release needs php-hash extension, which is not available
> with Kolab; I have no idea how one adds custom PHP extensions to Kolab
> (or perhaps, OpenPKG). Which leaves me two choices:

If we can figure out the exect requirements (versions, options etc) I can 
imagine to add the PHP hash extension to the Kolab distribution.

> * overall, such process is overly complicated; would be great if one
> could, during Kolab bootstrapping, just choose to add Samba domain
> controller, and everything would work flawlessly from scratch

This would be best. Just how we currently deal with Horde.

Yours,
-- martin

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

From mangoo at wpkg.org  Sun May 31 17:02:05 2009
From: mangoo at wpkg.org (Tomasz Chmielewski)
Date: Sun, 31 May 2009 17:02:05 +0200
Subject: [Kolab-devel] why not ship Kolab with Samba by default?
In-Reply-To: <200905311649.25253.martin.konold@erfrakon.de>
References: <4A21CE0E.8060307@wpkg.org>	<200905311134.23171.martin.konold@erfrakon.de>	<4A225A22.3030400@wpkg.org>
	<200905311649.25253.martin.konold@erfrakon.de>
Message-ID: <4A229BED.1030601@wpkg.org>

Martin Konold wrote:
> On Sunday 31 May 2009 12:21:22 Tomasz Chmielewski wrote:
> 
> Hi,
> 
>  > * Kolab's web interface is not compatible with Samba (i.e. it doesn't
> 
>  > add some required LDAP attributes for Samba) - so you have to use a
> 
>  > different webgui for adding users: LAM (LDAP Account Manager)
> 
> Is it incompatible or simple lacking to expose some attributes?
> 
> If it is the later we may consider to makeing them optionally available 
> via the Kolab webadmin tool.

Isn't it the same? ;)

It would have to add some samba attributes (passwords) and keep track of 
user IDs (so that they are not duplicated).



-- 
Tomasz Chmielewski
http://wpkg.org


From martin.konold at erfrakon.de  Sun May 31 17:48:03 2009
From: martin.konold at erfrakon.de (Martin Konold)
Date: Sun, 31 May 2009 17:48:03 +0200
Subject: [Kolab-devel] why not ship Kolab with Samba by default?
In-Reply-To: <4A229BED.1030601@wpkg.org>
References: <4A21CE0E.8060307@wpkg.org>
	<200905311649.25253.martin.konold@erfrakon.de>
	<4A229BED.1030601@wpkg.org>
Message-ID: <200905311748.04648.martin.konold@erfrakon.de>

On Sunday 31 May 2009 17:02:05 Tomasz Chmielewski wrote:

Hi Tomasz,

Firstly you must decide what kind of Samba do you mean.
PDC, BDC, Fileserver, Printserver, Member of an existing AD Domain....

> Martin Konold wrote:
> > On Sunday 31 May 2009 12:21:22 Tomasz Chmielewski wrote:
> >
> > Hi,
> >
> >  > * Kolab's web interface is not compatible with Samba (i.e. it doesn't
> >  >
> >  > add some required LDAP attributes for Samba) - so you have to use a
> >  >
> >  > different webgui for adding users: LAM (LDAP Account Manager)
> >
> > Is it incompatible or simple lacking to expose some attributes?
> >
> > If it is the later we may consider to makeing them optionally available
> > via the Kolab webadmin tool.
>
> Isn't it the same? ;)

No. Incompatibility means that there is a conflict. E.g. either semantics or 
syntax dissallows simply extending on product in order to support the other.

> It would have to add some samba attributes (passwords)

Extra password attributes sound wrong and scary.

Please exlicitly list them somewhere so that I can have look and decide if 
they could be supported out of the box.

> and keep track of
> user IDs (so that they are not duplicated).

Yours,
-- martin

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

From martin.konold at erfrakon.de  Sun May 31 17:55:04 2009
From: martin.konold at erfrakon.de (Martin Konold)
Date: Sun, 31 May 2009 17:55:04 +0200
Subject: [Kolab-devel] why not ship Kolab with Samba by default?
In-Reply-To: <4A229BED.1030601@wpkg.org>
References: <4A21CE0E.8060307@wpkg.org>
	<200905311649.25253.martin.konold@erfrakon.de>
	<4A229BED.1030601@wpkg.org>
Message-ID: <200905311755.05182.martin.konold@erfrakon.de>

On Sunday 31 May 2009 17:02:05 Tomasz Chmielewski wrote:

Hi Tomasz,

> It would have to add some samba attributes (passwords) and keep track of
> user IDs (so that they are not duplicated).

Can you please test and comment on 

	http://www.mynetcologne.de/~nc-dreszal/kolab/Kolab-Ubuntu.html

I think this could be a starter for inclusion.

Yours,
-- martin

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

From kolab-issues at intevation.de  Sun May 31 20:22:55 2009
From: kolab-issues at intevation.de (Richard Bos)
Date: Sun, 31 May 2009 18:22:55 +0000
Subject: [Kolab-devel] [issue3661] Include pid in kolabfilter log file
Message-ID: <1243794175.13.0.751960586792.issue3661@intevation.de>


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

Include the pid in the filterlog file, without the pid the log file is
basically useless as multiple filters run in parallel.  Without pid the
logs of the different filters can not be separated.  I need a good log
to investigate issue3629 https://www.intevation.de/roundup/kolab/issue3629

As such I initially changed the filter log name:
$conf['log']['name'] = '/var/log/kolab/filter.'.getmypid();
This helped me tremendiously while debugging issue 3626.  As I assume that
kolab wants only 1 filter log file, I thing that the following change is
good enough:
$conf['log']['ident'] = 'Kolab Filter (pid='.getmypid().')';

If this change is okay, I can commit it to cvs.

An example of the change included below:
May 31 19:45:33 Kolab Filter (pid=5429) [debug] [horde] sleep 007 [on line 143
of "/usr/share/php5/PEAR/Horde/Kolab/Filter/Base.php"]                                                                                                                         
May 31 19:45:33 Kolab Filter (pid=5430) [debug] [horde] sleep 007 [on line 143
of "/usr/share/php5/PEAR/Horde/Kolab/Filter/Base.php"]                                                                                                                         
May 31 19:45:35 Kolab Filter (pid=5423) [debug] [horde] sleep 007 [on line 143
of "/usr/share/php5/PEAR/Horde/Kolab/Filter/Base

(the sleeps were added by me).  As you can see, the 3 lines are logged behing
each other, while they are from different processes.

----------
assignedto: wrobel
files: resmgr.conf.pid.patch
messages: 20451
nosy: rbos, thomas, wrobel
priority: bug
status: unread
title: Include pid in kolabfilter log file
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3661>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: resmgr.conf.pid.patch
Type: application/octet-stream
Size: 853 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090531/c2109c6c/resmgr.conf.pid.exe