From benoit.mortier at opensides.be  Mon Jun  1 12:07:01 2009
From: benoit.mortier at opensides.be (Benoit Mortier)
Date: Mon, 1 Jun 2009 12:07:01 +0200
Subject: [Kolab-devel] French slides for the Kolab project
Message-ID: <200906011207.04962.benoit.mortier@opensides.be>

Hello,

I just published the translation of the official Kolab slides in french to 
the kolab wiki

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

Cheers
-- 
Benoit Mortier
CEO 
OpenSides "logiciels libres pour entreprises" : http://www.opensides.be/
Contributor to Gosa Project : http://gosa-project.org/


From kolab-issues at intevation.de  Mon Jun  1 15:56:55 2009
From: kolab-issues at intevation.de (Alan Miller)
Date: Mon, 01 Jun 2009 13:56:55 +0000
Subject: [Kolab-devel] [issue3662] Kolab website download link for 2.2.2
	goes to 2.2.1 directory
Message-ID: <1243864615.04.0.820144266112.issue3662@intevation.de>


New submission from Alan Miller <kolab-bugs at fencepost.net>:

On http://kolab.org/download.html, the link for kolab-server-2.2.2 actually
points to 2.2.1.

----------
messages: 20459
nosy: fencepost
priority: bug
status: unread
title: Kolab website download link for 2.2.2 goes to 2.2.1 directory
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3662>
___________________________________________________


From m.gabriel at das-netzwerkteam.de  Tue Jun  2 08:28:30 2009
From: m.gabriel at das-netzwerkteam.de (Mike Gabriel)
Date: Tue, 02 Jun 2009 08:28:30 +0200
Subject: [Kolab-devel] handling of private events in kolab clients
In-Reply-To: <200905301906.51135.martin.konold@erfrakon.de>
References: <20090511184740.54005x2xd8dk6u98@mail.das-netzwerkteam.de>
	<200905181014.43286.bernhard@intevation.de>
	<200905301906.51135.martin.konold@erfrakon.de>
Message-ID: <20090602082830.14247htaon3m57da@mail.das-netzwerkteam.de>

hi martin,

this is indeed very good news!!! i must admit i haven't had a spot on  
the konsec connector yet.

please provide me with a preview download URL, so i can catch up on this...

best and thanks for your initiative,
mike

On Sa 30 Mai 2009 19:06:49 CEST Martin Konold wrote:

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



-- 

DAS-NETZWERKTEAM
mike gabriel, dorfstr. 27, 24245 barmissen
fon: +49 (4302) 281418, fax: +49 (4302) 281419

eMail-LeseSchreibStunde: wochentags 8h-10h
mail: m.gabriel at das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 19650 bytes
Desc: =?utf-8?b?w5ZmZmVudGxpY2hlciA=?=
 =?utf-8?b?UEdQLVNjaGzDvHNzZWw=?=
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090602/439d3c9b/attachment-0001.bin

From kolab-issues at intevation.de  Tue Jun  2 12:13:03 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 02 Jun 2009 10:13:03 +0000
Subject: [Kolab-devel] [issue3663] After creation of a distribution list the
	user is asked to choose a resource twice.
Message-ID: <1243937583.43.0.402214892868.issue3663@intevation.de>


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

enterprise4 windows 20090515.968370

Test:
Req: An account with two contact resources,
1. Start to create a distribution list.
2. Enter twice contacts from the LDAP server.
3. Press okay.
=> The user is asked three times to choose a resource.
For the user the reason is not clear.

----------
assignedto: allen
messages: 20461
nosy: allen, bh, ludwig
priority: bug
status: unread
title: After creation of a distribution list the user is asked to choose  a resource twice.
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3663>
___________________________________________________


From kolab-issues at intevation.de  Tue Jun  2 12:30:04 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 02 Jun 2009 10:30:04 +0000
Subject: [Kolab-devel] [issue3664] After entering a appointment update mail
	into the calendar no mail is selected.
Message-ID: <1243938603.95.0.347903620599.issue3664@intevation.de>


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

enterprise4 windows 20090515.968370

Test:
Req: Accounts A and B.
1. A sends two invitations to B.
2. B accepts both.
=> A gets two update mails.
3. A looks at the first update mail and chooses: Enter into the calendar.
=> No mail is selected.
I expect that the next unread mail is selected.

----------
assignedto: allen
messages: 20462
nosy: allen, bh, ludwig
priority: minor bug
status: unread
title: After entering a appointment update mail into the calendar no mail is selected.
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3664>
___________________________________________________


From kolab-issues at intevation.de  Tue Jun  2 14:16:51 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 02 Jun 2009 12:16:51 +0000
Subject: [Kolab-devel] [issue3665] Not possible to accept a counter proposal
	from OL/toltec
Message-ID: <1243945010.93.0.306980425134.issue3665@intevation.de>


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

enterprise35 20090522.971351
OL 2003 with toltec 2.3.2 beta 9

Test:
Req: A: kontact user B: OL/toltec user
1. A invites B to an event.
2. B makes a counter proposal. 1h later.
3. A enters the update mail into the calendar.
=> A is not asked to accept the counter proposal.
I think this could be a problem as the user expect kontact to ask if he wants to
accept a counter proposal.

----------
assignedto: allen
messages: 20463
nosy: allen, bh, joonradley, ludwig
priority: bug
status: unread
title: Not possible to accept a counter proposal from OL/toltec
topic: enterprise35, kde client, toltec
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3665>
___________________________________________________


From martin.konold at erfrakon.de  Tue Jun  2 14:17:45 2009
From: martin.konold at erfrakon.de (Martin Konold)
Date: Tue, 2 Jun 2009 14:17:45 +0200
Subject: [Kolab-devel] handling of private events in kolab clients
In-Reply-To: <20090602082830.14247htaon3m57da@mail.das-netzwerkteam.de>
References: <20090511184740.54005x2xd8dk6u98@mail.das-netzwerkteam.de>
	<200905301906.51135.martin.konold@erfrakon.de>
	<20090602082830.14247htaon3m57da@mail.das-netzwerkteam.de>
Message-ID: <200906021417.46948.martin.konold@erfrakon.de>

On Tuesday 02 June 2009 08:28:30 Mike Gabriel wrote:

Hi Mike,

> this is indeed very good news!!! i must admit i haven't had a spot on
> the konsec connector yet.
>
> please provide me with a preview download URL, so i can catch up on this...

http://download.konsec.com/beta/KONSEC_Konnektor_2_3_0_16_de_ALPHA.zip

Please  note that this version ist not officially released and does not 
encrypt the private data. It only denies Outlook access to the private 
properties.



> > 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/20090602/13cee0db/attachment-0001.html

From kolab-issues at intevation.de  Tue Jun  2 14:27:30 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 02 Jun 2009 12:27:30 +0000
Subject: [Kolab-devel] [issue3666] textsnippets groups are closed in a new
	composer.
Message-ID: <1243945650.46.0.151209338557.issue3666@intevation.de>


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

enterprise 35 kdepim 20090522.971351

Test:
1. Create a new mail.
2. Configure text snippets and add a group with a snippet.
3. Open this group.
4. Send the mail.
5. Start to create another mail.
=> The snippet is not displayed, because the group is closed/folded together.

----------
assignedto: allen
messages: 20464
nosy: allen, bh, ludwig
priority: minor bug
status: unread
title: textsnippets groups are closed in a new composer.
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3666>
___________________________________________________


From kolab-issues at intevation.de  Tue Jun  2 16:49:07 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 02 Jun 2009 14:49:07 +0000
Subject: [Kolab-devel] [issue3667] Attachment icon is missing in use with
	OL/toltec
Message-ID: <1243954146.93.0.41108249304.issue3667@intevation.de>


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

enterprise35 kdepim 20090522.971351
OL 2003 toltec 2.3.2 beta9

Test:
Req A: kontact e35 user B: toltec user
1. A shares a folder with write rights with B.
2. A copies a mail with zip attachment to the shared folder.
3. B moves the mail to a different folder etc.
4. B moves the mail back in the shared folder.
5. A looks at the mail.
=> kontact doesn't display the attachment icon. (there is a kind of toltec.dat 
attachment at this mail.)
I expect the attachment icon to be displayed, as the mail has an attachment.

----------
assignedto: allen
messages: 20473
nosy: allen, bh, joonradley, ludwig
priority: bug
status: unread
title: Attachment icon is missing in use with OL/toltec
topic: enterprise35, kde client, kkc, toltec
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3667>
___________________________________________________


From kolab-issues at intevation.de  Tue Jun  2 18:43:01 2009
From: kolab-issues at intevation.de (Shrenik)
Date: Tue, 02 Jun 2009 16:43:01 +0000
Subject: [Kolab-devel] [issue3668] Installation of horde-form-0.0.2-4.16
	failed
Message-ID: <1243960981.05.0.0644760536492.issue3668@intevation.de>


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

While installing kolab on opensuse 11.1, it always stops with this error until
we choose to ignore it:

# zypper install kolab
...
...
Installation of horde-form-0.0.2-4.16 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed:
Package "/var/lib/pear/Horde_Form.xml" is not valid
install failed
error: %post(horde-form-0.0.2-4.16.noarch) scriptlet failed, exit status 1

Abort, retry, ignore? [A/r/i]: i

A workaround as suggested by Richard Bos to execute the script:

# rpm -ql --scripts horde-form
postinstall scriptlet (using /bin/sh):
pear install --nodeps --soft --force --register-only /var/lib/pear/Horde_Form.xml
postuninstall scriptlet (using /bin/sh):
if [ "$1" -eq "0" ]; then
  pear uninstall --nodeps --ignore-errors --register-only pear.horde.org/Horde_Form
fi
/usr/share/php5/PEAR/Horde/Form
/usr/share/php5/PEAR/Horde/Form.php
/usr/share/php5/PEAR/Horde/Form/Action
/usr/share/php5/PEAR/Horde/Form/Action.php
/usr/share/php5/PEAR/Horde/Form/Action/conditional_enable.php
/usr/share/php5/PEAR/Horde/Form/Action/conditional_setvalue.php
/usr/share/php5/PEAR/Horde/Form/Action/reload.php
/usr/share/php5/PEAR/Horde/Form/Action/submit.php
/usr/share/php5/PEAR/Horde/Form/Action/sum_fields.php
/usr/share/php5/PEAR/Horde/Form/Action/updatefield.php
/usr/share/php5/PEAR/Horde/Form/Renderer.php
/usr/share/php5/PEAR/Horde/Form/Type
/usr/share/php5/PEAR/Horde/Form/Type/tableset.php
/var/lib/pear/Horde_Form.xml

This bug is urgent as it results in the installation process being stalled.
Apart from that there doesn't seem to be any related failure.

----------
messages: 20476
nosy: sbhura
priority: urgent
status: unread
title: Installation of horde-form-0.0.2-4.16 failed
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3668>
___________________________________________________


From kolab-issues at intevation.de  Tue Jun  2 19:38:09 2009
From: kolab-issues at intevation.de (Shrenik)
Date: Tue, 02 Jun 2009 17:38:09 +0000
Subject: [Kolab-devel] [issue3669] setting kolabd to start automatically
	results in dependency error
Message-ID: <1243964289.76.0.784384159994.issue3669@intevation.de>


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

Setting kolabd to start automatically(through yast on opensuse 11.1) results in
dependency error for slurpd. It seems to be an incorrect dependency as ldap is
successfully added and also started with kolab.

----------
messages: 20478
nosy: sbhura
priority: minor bug
status: unread
title: setting kolabd to start automatically results in dependency error
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3669>
___________________________________________________


From kolab-issues at intevation.de  Wed Jun  3 11:02:09 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 03 Jun 2009 09:02:09 +0000
Subject: [Kolab-devel] [issue3670] Kontact hangs when 500 contacts are
	selected and a file resource is activated.
Message-ID: <1244019729.1.0.732070770584.issue3670@intevation.de>


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

enterprise4 windows 20090515.968370

Test:
Req:* more than 500 contacts in the Kolab contact resource.
    * a deactivated empty contact file resource.
1. In the contacts part: Select all 500 contacts (Ctrl+a)
2. Activate the test file resource.
=> kontact hangs/needs a long time to answer.

----------
assignedto: allen
messages: 20483
nosy: allen, bh, ludwig
priority: minor bug
status: unread
title: Kontact hangs when 500 contacts are selected and a file resource is activated.
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3670>
___________________________________________________


From kolab-issues at intevation.de  Wed Jun  3 11:34:53 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 03 Jun 2009 09:34:53 +0000
Subject: [Kolab-devel] [issue3671] Calendar: To Today button doesn't display
	a workweek right.
Message-ID: <1244021693.54.0.632167438438.issue3671@intevation.de>


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

enterprise35 kdepim 20090522.971351

Test:
1. Switch to the calendar part.
2. Activate workweek or week.
=> The workweek or week is displayed in the dayview.
3. Click on Next.
=> The next (work)week is selected.
4. Click on To Today.
=> Today is selected as first day and then three or five days follows.
This is a wrong behavior. I expect that the (work)week is displayed starting
with the first day of this week and not with today, if it is not Monday.

----------
assignedto: allen
messages: 20485
nosy: allen, bh, ludwig
priority: bug
status: unread
title: Calendar: To Today button doesn't display a workweek right.
topic: enterprise35, kde client, kkc
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3671>
___________________________________________________


From kolab-issues at intevation.de  Wed Jun  3 14:38:41 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 03 Jun 2009 12:38:41 +0000
Subject: [Kolab-devel] [issue3672] In a new appointment the "no time set"
	checkbox should be nearer to the time selection boxes
Message-ID: <1244032721.27.0.618252406222.issue3672@intevation.de>


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

enterprise4 windows 20090515.968370

Test:
1. Switch to the calendar part.
2. Start to create a new appointment.
=> The time select boxes and the "no time set" checkbox are a bit away.
It would be nice, if the checkbox is nearer to the time select boxes.

----------
assignedto: allen
messages: 20486
nosy: allen, bh, ludwig
priority: wish
status: unread
title: In a new appointment the "no time set" checkbox should be nearer to the time selection boxes
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3672>
___________________________________________________


From kolab-issues at intevation.de  Wed Jun  3 15:01:33 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 03 Jun 2009 13:01:33 +0000
Subject: [Kolab-devel] [issue3673] If "look into the calendar" is choosen in
	an invitation, the calendar window should be in the foreground
Message-ID: <1244034093.62.0.692185342815.issue3673@intevation.de>


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

enterprise4 windows 20090515.968370

Test:
Req: The user got invited to an appointment.
1. Switch to the Mail part.
2. Double click on the invitation.
=> A mail window with the invitation appears in the foreground.
3. Click on "Look into the calendar" 
=> Nothing visible happens. (In the background kontact switchs to the calendar.)
I expect that the main windows should be moved to the foreground in this case.

----------
assignedto: allen
messages: 20487
nosy: allen, bh, ludwig
priority: bug
status: unread
title: If "look into the calendar" is choosen in an invitation, the calendar window should be in the foreground
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3673>
___________________________________________________


From kolab-issues at intevation.de  Wed Jun  3 16:02:22 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 03 Jun 2009 14:02:22 +0000
Subject: [Kolab-devel] [issue3674] Deletion of an appointment or contact
	doesn't remove the mail from the resource folder
Message-ID: <1244037742.53.0.23238793356.issue3674@intevation.de>


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

enterprise35 kdepim 20090522.971351-kk2 (With patches for issue3636 and issue3648)

After some smoke tests I encounter following situation:
1. I have some mails in my resource folders contacts and calendar.
2. Neither the contacts part or the calendar part shows anything.
I think something with the index is wrong.
In the identity I have configured the name "Test, Smoke1".

----------
assignedto: allen
messages: 20488
nosy: allen, bh, ludwig
priority: critical
status: unread
title: Deletion of an appointment or contact doesn't remove the mail from the resource folder
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3674>
___________________________________________________


From ml at radoeka.nl  Wed Jun  3 23:21:28 2009
From: ml at radoeka.nl (Richard Bos)
Date: Wed, 3 Jun 2009 23:21:28 +0200
Subject: [Kolab-devel] annotations patch in c-client what is the status?
Message-ID: <200906032321.30110.ml@radoeka.nl>

Hi,

I'm wondering about the current status of the annotations support in the uw c-
client library.  The related draft RFC http://ietfreport.isoc.org/all-
ids/draft-daboo-imap-annotatemore-17.txt  is stated to expire on June 14, 
2009.  Which is about 2 weeks from now.  What does it mean that the draft RFC 
expires, will it be succeeded with another draft, or will it become the 
official one?

What about the c-client itself, a new version has been released last week:
Updated 28 May 2009:

Changes in Panda IMAP from UW IMAP 2007b that are in UW IMAP 2007e:

    * Fix rare crash in SMTP sending. [UW IMAP 2007c]
    * Fix security bug in tmail and dmail. [UW IMAP 2007d].
    * Mailbox compression ("burping") can now occur during IMAP IDLE.
      [UW IMAP 2007e].
    * Fix crash when using -I in tmail. [UW IMAP 2007e].
    * Fix crash in RFC822 output routines (CVE 2008-5514). [UW IMAP 2007e].

But from where can it be downloaded?  I do not find a download link on 
http://www.panda.com/imap/ what is the new home of the uw c-client library.

It would be good to have the RFC finally finalized, and have a c-client 
library that supports the RFC.  It's quite a hassle to build applications that 
depend on this library (php-imap e.g.).

This patch is tracked with https://www.intevation.de/roundup/kolab/merge10.

/me just curious.

-- 
Richard


From math.parent at gmail.com  Wed Jun  3 23:40:25 2009
From: math.parent at gmail.com (Mathieu Parent)
Date: Wed, 3 Jun 2009 23:40:25 +0200
Subject: [Kolab-devel] annotations patch in c-client what is the status?
In-Reply-To: <200906032321.30110.ml@radoeka.nl>
References: <200906032321.30110.ml@radoeka.nl>
Message-ID: <960738410906031440s43bb7dd6p542e713e7b82a4d4@mail.gmail.com>

Hi,
Mathieu Parent



On Wed, Jun 3, 2009 at 11:21 PM, Richard Bos <ml at radoeka.nl> wrote:
> Hi,
>
> I'm wondering about the current status of the annotations support in the uw c-
> client library. ?The related draft RFC http://ietfreport.isoc.org/all-
> ids/draft-daboo-imap-annotatemore-17.txt ?is stated to expire on June 14,
> 2009. ?Which is about 2 weeks from now. ?What does it mean that the draft RFC
> expires, will it be succeeded with another draft, or will it become the
> official one?

It is now approved (as shown in
http://wiki.kolab.org/index.php/Kolab-major-app-patches):
http://www.ietf.org/rfc/rfc5464.txt



> What about the c-client itself, a new version has been released last week:
> (...)
>
> But from where can it be downloaded? ?I do not find a download link on
> http://www.panda.com/imap/ what is the new home of the uw c-client library.
Probably ftp://ftp.cac.washington.edu/imap/

> It would be good to have the RFC finally finalized, and have a c-client
> library that supports the RFC. ?It's quite a hassle to build applications that
> depend on this library (php-imap e.g.).

Agree. I don't know how to push the patch upstream.

> This patch is tracked with https://www.intevation.de/roundup/kolab/merge10.
>
> /me just curious.
>
> --
> Richard
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>


From ml at radoeka.nl  Wed Jun  3 23:54:44 2009
From: ml at radoeka.nl (Richard Bos)
Date: Wed, 3 Jun 2009 23:54:44 +0200
Subject: [Kolab-devel] annotations patch in c-client what is the status?
In-Reply-To: <960738410906031440s43bb7dd6p542e713e7b82a4d4@mail.gmail.com>
References: <200906032321.30110.ml@radoeka.nl>
	<960738410906031440s43bb7dd6p542e713e7b82a4d4@mail.gmail.com>
Message-ID: <200906032354.45331.ml@radoeka.nl>

Hi Mathieu,

thanks for your fast reply :)

Op woensdag 03 juni 2009 23:40:25 schreef Mathieu Parent:
>  I'm wondering about the current status of the annotations support in the
> uw c-
>
> > client library.  The related draft RFC http://ietfreport.isoc.org/all-
> > ids/draft-daboo-imap-annotatemore-17.txt  is stated to expire on June 14,
> > 2009.  Which is about 2 weeks from now.  What does it mean that the draft
> > RFC expires, will it be succeeded with another draft, or will it become
> > the official one?
>
> It is now approved (as shown in
> http://wiki.kolab.org/index.php/Kolab-major-app-patches):
> http://www.ietf.org/rfc/rfc5464.txt

Oh, I did not realize it's now an official standard as the text on the wiki 
states "This is now a proposed standard: RFC 5464......"

> > What about the c-client itself, a new version has been released last
> > week: (...)
> >
> > But from where can it be downloaded?  I do not find a download link on
> > http://www.panda.com/imap/ what is the new home of the uw c-client
> > library.
>
> Probably ftp://ftp.cac.washington.edu/imap/

Nope it's not there :(

-- 
Richard


From alar.sing at err.ee  Thu Jun  4 07:24:21 2009
From: alar.sing at err.ee (Alar Sing)
Date: Thu, 04 Jun 2009 08:24:21 +0300
Subject: [Kolab-devel] annotations patch in c-client what is the status?
In-Reply-To: <200906032321.30110.ml@radoeka.nl>
References: <200906032321.30110.ml@radoeka.nl>
Message-ID: <4A275A85.9020703@err.ee>



Richard Bos wrote:
> Hi,
> 
> What about the c-client itself, a new version has been released last week:
> Updated 28 May 2009:
> 
> Changes in Panda IMAP from UW IMAP 2007b that are in UW IMAP 2007e:
> 
>     * Fix rare crash in SMTP sending. [UW IMAP 2007c]
>     * Fix security bug in tmail and dmail. [UW IMAP 2007d].
>     * Mailbox compression ("burping") can now occur during IMAP IDLE.
>       [UW IMAP 2007e].
>     * Fix crash when using -I in tmail. [UW IMAP 2007e].
>     * Fix crash in RFC822 output routines (CVE 2008-5514). [UW IMAP 2007e].
> 
> But from where can it be downloaded?  I do not find a download link on 
> http://www.panda.com/imap/ what is the new home of the uw c-client library.
>
Hello,

I looked at that web there was:
Panda Programming has forked the IMAP toolkit from the final University 
of Washington version (imap-2007b) for internal use.

Maybe they do not release their  imap libary.


From kolab-issues at intevation.de  Thu Jun  4 14:01:41 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 04 Jun 2009 12:01:41 +0000
Subject: [Kolab-devel] [issue3675] The anniversary day for a contact cannot
	be entered with the keyboard
Message-ID: <1244116901.45.0.191821019931.issue3675@intevation.de>


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

enterprise4 windows 20090515.968370

Test:
1. Switch to the contacts part.
2. Create a new contacts.
3. Look at the details and try to enter a anniversary day.
=> You need to use the date selection dialog. 
I expect that is possible to enter this day with the keyboard.

----------
assignedto: allen
messages: 20499
nosy: allen, bh, ludwig
priority: minor bug
status: unread
title: The anniversary day for a contact cannot be entered with the keyboard
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3675>
___________________________________________________


From kolab-issues at intevation.de  Thu Jun  4 14:09:28 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 04 Jun 2009 12:09:28 +0000
Subject: [Kolab-devel] [issue3676] Set "show mail size" in the
	mail->view->maillist dialog doesn't have an effect.
Message-ID: <1244117368.33.0.184303330148.issue3676@intevation.de>


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

enterprise4 windows 20090515.968370

Test:
In the mail list are shown the foldername and the folder total.
1. Open the mail configuration dialog.
2. Set View->Maillist->Show size
3. Press okay.
=> But the mail size isn't displayed in the maillist.

----------
assignedto: allen
messages: 20500
nosy: allen, bh, ludwig
priority: minor bug
status: unread
title: Set "show mail size" in the mail->view->maillist dialog doesn't have an effect.
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3676>
___________________________________________________


From kolab-issues at intevation.de  Thu Jun  4 14:18:33 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 04 Jun 2009 12:18:33 +0000
Subject: [Kolab-devel] [issue3677] In the calendar side-by-side view columns
	header aren't above their columns
Message-ID: <1244117913.82.0.228791173608.issue3677@intevation.de>


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

enterprise4 windows 20090515.968370

Test:
1. Switch to the calendar part.
2. Set Configuration->View->day view->side-by-side view.
3. Click on month view and on day view.
4. Select work week view.
=> The header of the columns are not above their columns.
See:sidebyside-20090604.png

----------
assignedto: allen
files: sidebyside-20090604.png
messages: 20501
nosy: allen, bh, ludwig
priority: bug
status: unread
title: In the calendar side-by-side view columns header aren't above their columns
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3677>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sidebyside-20090604.png
Type: image/png
Size: 38881 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090604/6aff412b/sidebyside-20090604-0001.png

From kolab-issues at intevation.de  Thu Jun  4 15:20:34 2009
From: kolab-issues at intevation.de (Bernhard Herzog)
Date: Thu, 04 Jun 2009 13:20:34 +0000
Subject: [Kolab-devel] [issue3678] Displaying a long inline pgp encrypted
	message takes very long
Message-ID: <1244121634.18.0.515780391387.issue3678@intevation.de>


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

When displaying an *inline* pgp encrypted message, kontact can take very long
(up to several minutes) to show the messages.  How long it takes depends on the
length of the message, but also on the content.  E.g. about 3MiB of normal
natural language text take about 20 seconds and a testmail where I encrypted
3MiB of base64 encoded data took more than two minutes.  While kontact is trying
to display the message, it is completely blocked and uses 100% CPU.

This also happens when Kontact cannot decrypt the message because of missing
private keys.  OTOH, when kontact cannot decrypt the message because it cannot
execute gpg 1.4 (because of unsupported config settings as in kolab/issue3319)
it only takes a few seconds.

Even a few seconds are a bit much, though.  Gnus for instance doesn't take more
than 1s to decrypt display the same messages.

Observed with kdepim enterprise branch in various versions, including
20090508.965262.

----------
assignedto: allen
messages: 20508
nosy: allen, bh
priority: bug
status: unread
title: Displaying a long inline pgp encrypted message takes very long
topic: enterprise35, kde client, kkc
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3678>
___________________________________________________


From kolab-issues at intevation.de  Thu Jun  4 15:26:04 2009
From: kolab-issues at intevation.de (Bernhard Herzog)
Date: Thu, 04 Jun 2009 13:26:04 +0000
Subject: [Kolab-devel] [issue3679] kontact composer: inserting large file
	takes very long
Message-ID: <1244121964.67.0.442084629479.issue3679@intevation.de>


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

Observed while testing kolab/issue3678: The Composer windows allows the user to
insert the contents of a file into the mail body with "Message"/"Insert
file...".  For large files, e.g. about 3MiB, this takes very long.  With one
file, I killed Kontact after about 30 minutes.  Interestingly, using copy&paste
from another X program is much faster but still at least several seconds which
is still too long.

This is with kontact from enterprise 3.5 branch version 20090508.965262.  I've
observed this with other enterprise 35 version too, though.

----------
assignedto: allen
messages: 20509
nosy: allen, bh
priority: bug
status: unread
title: kontact composer: inserting large file takes very long
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3679>
___________________________________________________


From kolab-issues at intevation.de  Thu Jun  4 15:38:35 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 04 Jun 2009 13:38:35 +0000
Subject: [Kolab-devel] [issue3680] Kontact throws "password wrong" error
	message after configure a new account without kwallet but
	saved passwords.
Message-ID: <1244122715.67.0.993136880149.issue3680@intevation.de>


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

enterprise35 kdepim 20090522.971351

Test:
1. Create a new account on the server.
2. Configure a user with kolabwizard, save passwords, but without kwallet.
3. Start kontact and sync.
=> An error message appears: "wrong password".
I expect the sync to work, because I have entered the password with the 
kolabwizard.

----------
assignedto: allen
messages: 20510
nosy: allen, bh, ludwig
priority: bug
status: unread
title: Kontact throws "password wrong" error message after configure a new account without kwallet but saved passwords.
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3680>
___________________________________________________


From kolab-issues at intevation.de  Thu Jun  4 16:57:58 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 04 Jun 2009 14:57:58 +0000
Subject: [Kolab-devel] [issue3681] Kontact asked for the free busy password,
	after every restart
Message-ID: <1244127478.43.0.17060568654.issue3681@intevation.de>


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

enterprise35 kdepim 20090522.971351

Test:
1. Create a new user with PW "123!123" on the server.
2. Use kolabwizard to configure this account, with saved passwords and without
  kwallet.
3. Start kontact and sync.
4. Switch to the calendar part.
5. Start to create a new appointment.
6. Look at the attendees.
=> A freebusy auth dialog pops up and asks for the password.
7. Enter the right password and save the password.
8. Restart kontact and do step 4.-6. again.
=> The freebusy auth dialog appears again.
I expect that the freebusy auth dialog doesn't appear the first time, because I
entered the password in kwallet. Anyway it shouldn't appear the second time, too.

----------
assignedto: allen
messages: 20517
nosy: allen, bh, ludwig
priority: urgent
status: unread
title: Kontact asked for the free busy password, after every restart
topic: enterprise35, kde client, kkc
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3681>
___________________________________________________


From kolab-issues at intevation.de  Thu Jun  4 18:34:03 2009
From: kolab-issues at intevation.de (Bernhard Herzog)
Date: Thu, 04 Jun 2009 16:34:03 +0000
Subject: [Kolab-devel] [issue3682] Kontact crashes when displaying certain
	S/MIME messages
Message-ID: <1244133243.2.0.320168085163.issue3682@intevation.de>


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

Kontact enterprise 3.5 (all recent versions) crashes when displaying certain
S/MIME mails.  Backtrace is attached (kontact.20090602-1.kcrash).
I haven't been able to reproduce it yet.  The backtrace was provided by a customer.

----------
assignedto: allen
files: kontact.20090602-1.kcrash
messages: 20518
nosy: allen, bernhard, bh, ludwig, osterfeld, till, vkrause
priority: bug
status: unread
title: Kontact crashes when displaying certain S/MIME messages
topic: enterprise35, kde client, kkc
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3682>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kontact.20090602-1.kcrash
Type: application/octet-stream
Size: 2850 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090604/81bb9b25/kontact.20090602-1.exe

From martin.konold at erfrakon.de  Thu Jun  4 19:04:19 2009
From: martin.konold at erfrakon.de (Martin Konold)
Date: Thu, 4 Jun 2009 19:04:19 +0200
Subject: [Kolab-devel] annotations patch in c-client what is the status?
In-Reply-To: <200906032321.30110.ml@radoeka.nl>
References: <200906032321.30110.ml@radoeka.nl>
Message-ID: <200906041904.20540.martin.konold@erfrakon.de>

On Wednesday 03 June 2009 23:21:28 Richard Bos wrote:

Hi Richard,

thank you very much for bringing our attention once more towards dealing with 
upstream project.

> I'm wondering about the current status of the annotations support in the uw
> c- client library.  The related draft RFC http://ietfreport.isoc.org/all-
> ids/draft-daboo-imap-annotatemore-17.txt  is stated to expire on June 14,
> 2009.  Which is about 2 weeks from now.  What does it mean that the draft
> RFC expires, will it be succeeded with another draft, or will it become the
> official one?

draft-daboo-imap-annotatemore-17.txt, was published as a Proposed Standard, 
RFC 5464, on 2009-2-9.

see also http://www.ietf.org/rfc/rfc5464.txt

> But from where can it be downloaded?  

Dunno.

> I do not find a download link on
> http://www.panda.com/imap/ what is the new home of the uw c-client library.
>
> It would be good to have the RFC finally finalized

This already happened. The fact that we were using it in the field for years 
helped with this.

> , and have a c-client
> library that supports the RFC. 

They used to claim that they are willing to incorporate this patch as soon as 
it became a RFC.

> It's quite a hassle to build applications
> that depend on this library (php-imap e.g.).

I tend to agree.

> This patch is tracked with https://www.intevation.de/roundup/kolab/merge10.

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/20090604/0ab16d77/attachment-0001.html

From ml at radoeka.nl  Thu Jun  4 21:27:40 2009
From: ml at radoeka.nl (Richard Bos)
Date: Thu, 4 Jun 2009 21:27:40 +0200
Subject: [Kolab-devel] annotations patch in c-client what is the status?
In-Reply-To: <4A275A85.9020703@err.ee>
References: <200906032321.30110.ml@radoeka.nl> <4A275A85.9020703@err.ee>
Message-ID: <200906042127.42237.ml@radoeka.nl>

Hi Alar,

Op donderdag 04 juni 2009 07:24:21 schreef Alar Sing:
> > But from where can it be downloaded?  I do not find a download link on
> > http://www.panda.com/imap/ what is the new home of the uw c-client
> > library.
>
> I looked at that web there was:
> Panda Programming has forked the IMAP toolkit from the final University
> of Washington version (imap-2007b) for internal use.
>
> Maybe they do not release their  imap libary.

Good point, that's also a reason why I asked about the status of this library.  
As the c-client is an important piece of software it must be available 
publicly.  The kolab project can not deal with c-client that is kept in house.
Therefor the following statement on the the same website is interesting: "We 
are still working on a funding model for Panda IMAP that will permit an public 
open source distribution. Future development will depend upon internal needs 
and cost recovery."

Which brings me to the following thought (thinking out load): does panda.com 
accept external funds or resources [1]?  If so, is the kolab project (actually 
the companies behind the project) willing to provide funding for the c-client 
library?

[1] Would it be sufficient to provide resources (and no financials?) e.g. the 
developers to develop and maintain the code, the code management system, the 
bug tracker, the source tarbals, the emaillists and everything else that is 
needed to run a successful project on kolab.org?  This is just thinking out 
load, I really don't know what funding panda.com is looking for!  But the 
current situation does not look good in my eyes.

-- 
Richard


From martin.konold at erfrakon.de  Thu Jun  4 22:26:27 2009
From: martin.konold at erfrakon.de (Martin Konold)
Date: Thu, 4 Jun 2009 22:26:27 +0200
Subject: [Kolab-devel] annotations patch in c-client what is the status?
In-Reply-To: <200906042127.42237.ml@radoeka.nl>
References: <200906032321.30110.ml@radoeka.nl> <4A275A85.9020703@err.ee>
	<200906042127.42237.ml@radoeka.nl>
Message-ID: <200906042226.27608.martin.konold@erfrakon.de>

On Thursday 04 June 2009 21:27:40 Richard Bos wrote:

Hi Richard,

> ?If so, is the kolab project (actually
> the companies behind the project) willing to provide funding for the
> c-client library?

I see no point in helping panda in any way beyond providing patches. They seem 
to try to blackmail their users. IMHO a very bad strategy I am not going to 
suppport. The dynamics in the c-client library was simply not there during the 
last years.

I popose to make another fork of the original c-client library and maintain it 
within kolab.org publically.

In the long run the c-client library will not survive anyway.

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/20090604/b39cef16/attachment.html

From ml at radoeka.nl  Fri Jun  5 00:09:02 2009
From: ml at radoeka.nl (Richard Bos)
Date: Fri, 5 Jun 2009 00:09:02 +0200
Subject: [Kolab-devel] annotations patch in c-client what is the status?
In-Reply-To: <200906042226.27608.martin.konold@erfrakon.de>
References: <200906032321.30110.ml@radoeka.nl>
	<200906042127.42237.ml@radoeka.nl>
	<200906042226.27608.martin.konold@erfrakon.de>
Message-ID: <200906050009.02763.ml@radoeka.nl>

Op donderdag 04 juni 2009 22:26:27 schreef Martin Konold:
> On Thursday 04 June 2009 21:27:40 Richard Bos wrote:
>
> Hi Richard,
>
> >  If so, is the kolab project (actually
> > the companies behind the project) willing to provide funding for the
> > c-client library?
>
> I see no point in helping panda in any way beyond providing patches. They
> seem to try to blackmail their users. IMHO a very bad strategy I am not
> going to suppport. The dynamics in the c-client library was simply not
> there during the last years.
>
> I popose to make another fork of the original c-client library and maintain
> it within kolab.org publically.

But how do you convince distributions to use this fork?  If the distributions 
will stick to the original one, the situation is not improved on the contrary 
it will be confusing.

> In the long run the c-client library will not survive anyway.

Can you elaborate on this a bit more?  How long is your run, if that will take 
years, it is not a good situation either.  Is it not possible to deliver this 
solution faster, so it can be used now?


-- 
Richard


From martin.konold at erfrakon.de  Fri Jun  5 07:02:34 2009
From: martin.konold at erfrakon.de (Martin Konold)
Date: Fri, 5 Jun 2009 07:02:34 +0200
Subject: [Kolab-devel] annotations patch in c-client what is the status?
In-Reply-To: <200906050009.02763.ml@radoeka.nl>
References: <200906032321.30110.ml@radoeka.nl>
	<200906042226.27608.martin.konold@erfrakon.de>
	<200906050009.02763.ml@radoeka.nl>
Message-ID: <200906050702.35151.martin.konold@erfrakon.de>

On Friday 05 June 2009 00:09:02 Richard Bos wrote:

Hi Richard,

> Op donderdag 04 juni 2009 22:26:27 schreef Martin Konold:
> > On Thursday 04 June 2009 21:27:40 Richard Bos wrote:
> >
> > Hi Richard,
> >
> > >  If so, is the kolab project (actually
> > > the companies behind the project) willing to provide funding for the
> > > c-client library?
> >
> > I see no point in helping panda in any way beyond providing patches. They
> > seem to try to blackmail their users. IMHO a very bad strategy I am not
> > going to suppport. The dynamics in the c-client library was simply not
> > there during the last years.
> >
> > I popose to make another fork of the original c-client library and
> > maintain it within kolab.org publically.
>
> But how do you convince distributions to use this fork?  If the
> distributions will stick to the original one, the situation is not improved
> on the contrary it will be confusing.

Firstly they must know about the existance of the fork.

Secondly they must know that there is NO risk involved in taking our version 
of the c-client library. (Our versions only extents the original version, is 
extremly well tested and is maintained without blackmailing so actually the 
risks are decreasing)

Thirdls they must be made aware of the differences:

 - maintained versus unmainained
 - freely available versus blackmail
 - rfc compliant features versus lack of features
 - security fixes versus blackmail

> > In the long run the c-client library will not survive anyway.
>
> Can you elaborate on this a bit more?

The codebase was stagnant for many years and is outdated. It lacks imap 
features and nobody is investing heavily in implementing the most recent IMAP 
rfcs (e.g. condstore....)

> How long is your run, if that will take years, it is not a good situation
> either.  

You mean the time until c-client dies? This will definetely take years.

> Is it not possible to
> deliver this solution faster, so it can be used now?

The fast solution is to fork now and make it widely know.

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/20090605/5e5e7b59/attachment-0001.html

From ml at radoeka.nl  Fri Jun  5 08:39:16 2009
From: ml at radoeka.nl (Richard Bos)
Date: Fri, 5 Jun 2009 08:39:16 +0200
Subject: [Kolab-devel] annotations patch in c-client what is the status?
In-Reply-To: <200906050702.35151.martin.konold@erfrakon.de>
References: <200906032321.30110.ml@radoeka.nl>
	<200906042226.27608.martin.konold@erfrakon.de>
	<200906050009.02763.ml@radoeka.nl>
	<200906050702.35151.martin.konold@erfrakon.de>
Message-ID: <20090605063916.GB93069@xs4all.nl>

Hi Martin,

On Fri, Jun 05, 2009 at 07:02:34AM +0200, Martin Konold wrote:
> > > I see no point in helping panda in any way beyond providing patches. They
> > > seem to try to blackmail their users. IMHO a very bad strategy I am not
> > > going to suppport. The dynamics in the c-client library was simply not
> > > there during the last years.
> > >
> > > I popose to make another fork of the original c-client library and
> > > maintain it within kolab.org publically.
> >
> > But how do you convince distributions to use this fork?  If the
> > distributions will stick to the original one, the situation is not improved
> > on the contrary it will be confusing.
> 
> Firstly they must know about the existance of the fork.
> 
> Secondly they must know that there is NO risk involved in taking our version 
> of the c-client library. (Our versions only extents the original version, is 
> extremly well tested and is maintained without blackmailing so actually the 
> risks are decreasing)
> 
> Thirdls they must be made aware of the differences:
> 
>  - maintained versus unmainained
>  - freely available versus blackmail
>  - rfc compliant features versus lack of features
>  - security fixes versus blackmail

Indeed, but have a look at this page: http://panda.com/imap/
and see the number of fixes that have been made to the
c-client already.  Would a fork be able to provide the same
number of fixes?



> > > In the long run the c-client library will not survive anyway.
> >
> > Can you elaborate on this a bit more?
> 
> The codebase was stagnant for many years and is outdated. It lacks imap 
> features and nobody is investing heavily in implementing the most recent IMAP 
> rfcs (e.g. condstore....)
> 
> > How long is your run, if that will take years, it is not a good situation
> > either.  
> 
> You mean the time until c-client dies? This will definetely take years.

No I in other email (earlier in this thread) you said that their might
be another solution for the c-client.  So I actually hoped that you 
could tell something about that (what solution and when available).
 
> > Is it not possible to
> > deliver this solution faster, so it can be used now?
> 
> The fast solution is to fork now and make it widely know.

So, who should do this (btw not me!)???

-- 
Richard


From martin.konold at erfrakon.de  Fri Jun  5 12:03:43 2009
From: martin.konold at erfrakon.de (Martin Konold)
Date: Fri, 5 Jun 2009 12:03:43 +0200
Subject: [Kolab-devel] annotations patch in c-client what is the status?
In-Reply-To: <20090605063916.GB93069@xs4all.nl>
References: <200906032321.30110.ml@radoeka.nl>
	<200906050702.35151.martin.konold@erfrakon.de>
	<20090605063916.GB93069@xs4all.nl>
Message-ID: <200906051203.44372.martin.konold@erfrakon.de>

On Friday 05 June 2009 08:39:16 Richard Bos wrote:

Hi Richard,

> > ?- security fixes versus blackmail
>
> Indeed, but have a look at this page: http://panda.com/imap/
> and see the number of fixes that have been made to the
> c-client already. ?Would a fork be able to provide the same
> number of fixes?

Claiming to have fixed a security problem without disclosure is simply 
blackmailing. I am not interested in dealing with these people. 

Maybe it is better to invest either in a fork or in another solution.

Regards,
-- martin

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

From ml at radoeka.nl  Fri Jun  5 14:27:26 2009
From: ml at radoeka.nl (Richard Bos)
Date: Fri, 5 Jun 2009 14:27:26 +0200
Subject: [Kolab-devel] annotations patch in c-client what is the status?
In-Reply-To: <200906051203.44372.martin.konold@erfrakon.de>
References: <200906032321.30110.ml@radoeka.nl>
	<20090605063916.GB93069@xs4all.nl>
	<200906051203.44372.martin.konold@erfrakon.de>
Message-ID: <200906051427.27293.ml@radoeka.nl>

Hi,

Op vrijdag 05 juni 2009 12:03:43 schreef Martin Konold:
> On Friday 05 June 2009 08:39:16 Richard Bos wrote:
>
> Hi Richard,
>
> > >  - security fixes versus blackmail
> >
> > Indeed, but have a look at this page: http://panda.com/imap/
> > and see the number of fixes that have been made to the
> > c-client already.  Would a fork be able to provide the same
> > number of fixes?
>
> Claiming to have fixed a security problem without disclosure is simply
> blackmailing. I am not interested in dealing with these people.
>
> Maybe it is better to invest either in a fork or in another solution.

What about the other solution?  In another e-mail you wrote:
In addition I noticed that Horde is moving away to c-client (due to lackof 
features)

http://cvs.horde.org/co.php/imp/docs/RFCS?rt=horde-hatchery

(Some of these RFCs are not supported by c-client)

What it be possible to replace the c-client functionality completely with 
horde libraries?  I believe I have read on this list that the c-client is 
needed because of speed.  A pure php implementation would be too slow.   But 
perhaps better a slow implementation that is maintained, than one that is fast 
and not maintained.  As the current c-client is shareware and no longer open 
source, the claim on kolab's home page is unfortunately not correct:
"The implementations offered by us are Free Software (Open Source)" :(

In case a full horde implementation would be used, would that imply that the 
patches get/set annotation and my_rights would be no longer needed?  (the 
patches are described as: PHP uses the c-client library and requires patches 
to use the annotation features that are provided within the c-client library 
of a Kolab server)

Looking forward to a good solution for this!  Shall I open a prio urgent issue 
for it?


-- 
Richard


From kolab-issues at intevation.de  Fri Jun  5 14:39:58 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Fri, 05 Jun 2009 12:39:58 +0000
Subject: [Kolab-devel] [issue3683] Calendar "Export->Export as web page"
	doesn't show the right events.
Message-ID: <1244205597.98.0.145678435955.issue3683@intevation.de>


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

enterprise35 kdepim 20090522.971351

There a some cases in which Export as web page doesn't show the right events:
* Date Range 2009-06-05 to 2009-06-05 and "Export in month view" is set.
  => The whole 2009-06 month is displayed in the html page.
  So in this case the Date Range is not used.
* Date Range 2009-06-05 to 2009-06-05 and "Export in month view" is _not_ set.
  => No calender is displayed in the html page.
  I expect the events (which existed) of the 2009-06-05 to be displayed in 
  the web page.
* Date Range 2009-05-01 to 2009-06-05 and "Export in month view" is not set.
  => No clendar is displayed in the html page.  

Test:
1. Switch to the calendar part.
2. Create events at the 20090605 and some test events at 20090610 and at 20090602
3. File->Export->Export as Web Page.
4. Enter the Dates as above and set/unset "Export in month view" option.
5. Look at the html page with a browser.

----------
assignedto: allen
messages: 20531
nosy: allen, bh, ludwig
priority: bug
status: unread
title: Calendar "Export->Export as web page" doesn't show the right events.
topic: enterprise35, kde client, kkc
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3683>
___________________________________________________


From thomas at intevation.de  Fri Jun  5 18:02:08 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 5 Jun 2009 18:02:08 +0200
Subject: [Kolab-devel] Is comment on line 181 in kolabd/Makefile.am
	still valid?
In-Reply-To: <200905262125.38093.ml@radoeka.nl>
References: <200905161652.43460.ml@radoeka.nl>
	<200905262125.38093.ml@radoeka.nl>
Message-ID: <20090605160208.GF22155.thomas@intevation.de>

* Richard Bos <ml at radoeka.nl> [20090526 21:25]:
> 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?

Back from vacation ...

Gunnar repackaged everything besides kolabd and kolab-webadmin, so I
think your assumption is correct, please change it in CVS.

Thomas

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


From kolab-issues at intevation.de  Mon Jun  8 12:27:33 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Mon, 08 Jun 2009 10:27:33 +0000
Subject: [Kolab-devel] [issue3685] Calendar: It isn't possible to enter the
	update mail of an moved event into the calendar.
Message-ID: <1244456853.09.0.180353629284.issue3685@intevation.de>


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

enterprise35 20090605.977802

Test:
Req: Two kontact user A and B.
1. A invites B to a new appointment.
2. B accepts the appointment.
3. A enters the update mail into his calendar.
4. A. A moves the appointment to a different time.
5. B looks at the update mail and wants to enter it into his calendar.
   But this is not possible.
I expect that user B can enter the updated appointment into his calender.

This is a regression.

----------
assignedto: allen
messages: 20542
nosy: allen, bh, ludwig
priority: critical
status: unread
title: Calendar: It isn't possible to enter the update mail of an moved event into the calendar.
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3685>
___________________________________________________


From kolab-issues at intevation.de  Mon Jun  8 17:01:10 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Mon, 08 Jun 2009 15:01:10 +0000
Subject: [Kolab-devel] [issue3686] Calendar: A delegator gets a wrong update
	mail.
Message-ID: <1244473270.2.0.143379923834.issue3686@intevation.de>


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

enterprise35 kdepim 20090605.977802

Test:
Req: Three kontact users (A, B, C) 
1. A invites B to an appointment.
2. B delegates the appointment to C.
3. C accepts.
4. A accepts C.
5. B syncs.
=> B has two update mails in his inbox.
One from C and one from A, telling B that A accepted C for the appointment.
B gets can accept/cond accept.. in this update mail, but he cannot enter this 
event into his calendar.

----------
assignedto: allen
messages: 20553
nosy: allen, bh, ludwig
priority: urgent
status: unread
title: Calendar: A delegator gets a wrong update mail.
topic: kde client, prokde35
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3686>
___________________________________________________


From kolab-issues at intevation.de  Tue Jun  9 12:38:42 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 09 Jun 2009 10:38:42 +0000
Subject: [Kolab-devel] [issue3687] calendar: print should show the place of
	an event like in e4
Message-ID: <1244543922.32.0.204385273037.issue3687@intevation.de>


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

enterprise35 20090605.977802

Test:
1. Switch to the calendar component.
2. Create a appointment with a place.
3. File->Print. and print this day to a file.
=> The printed appointment doesn't contain information about the place.
In e4 the appointment is printed with a place information.

I would be nice, if e35 does also show place of the appointment in the different 
ways of printing appointments.

----------
assignedto: allen
messages: 20562
nosy: allen, bh, ludwig
priority: wish
status: unread
title: calendar: print should show the place of an event like in e4
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3687>
___________________________________________________


From kolab-issues at intevation.de  Tue Jun  9 14:11:39 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 09 Jun 2009 12:11:39 +0000
Subject: [Kolab-devel] [issue3688] D'n'D a mail attachment from a mail
	window to the Desktop: wrong rights/Link broken
Message-ID: <1244549498.9.0.219110531336.issue3688@intevation.de>


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

enterprise35 20090605.977802

Test:
Req: In a KDE environment.
1. Send a mail with attachment (e.g. a pdf file) to yourself.
2. Sync and look at the mail.
3. D'n'D the attachment to the desktop.
=> A dialog pops up to choose copy to/move to/create link
4. Choose Copy to
=> The attachment is copied to the desktop, but the file has wrong rights.
The file is just read-only for the user (-r-------)
I expect that the user has write rights to his own file.

Test (cont.):
1-3. as above.
4. Choose Create Link.
5. Select a different mail and back again.
=>The link is broken, because the link was created against a tmp file, which is
 deleted after selection of a different mail.

----------
assignedto: allen
messages: 20563
nosy: allen, bh, ludwig
priority: bug
status: unread
title: D'n'D a mail attachment from a mail window to the Desktop: wrong rights/Link broken
topic: enterprise35, kde client, kkc
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3688>
___________________________________________________


From kolab-issues at intevation.de  Wed Jun 10 11:41:36 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 10 Jun 2009 09:41:36 +0000
Subject: [Kolab-devel] [issue3689] D'n''D a mail to the desktop: Preselect
	subject as filename
Message-ID: <1244626896.74.0.370514539493.issue3689@intevation.de>


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

enterprise35 20090605.979060

Test:
In a KDE environment.
1. Switch to KMail.
2. Select a mail.
3. RMB -> Save mail.
=> A save file dialog appears with the subject of the mail as filename.
  Okay.
4. D'n'D a mail to the desktop.
=> A different save file dialog appears without filename.
I expect that the dialog has preselected as filename the subject of the mail.
Is this possible?

----------
assignedto: allen
messages: 20569
nosy: allen, bh, ludwig
priority: wish
status: unread
title: D'n''D a mail to the desktop: Preselect subject as filename
topic: enterprise35, kde client, kkc
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3689>
___________________________________________________


From kolab-issues at intevation.de  Wed Jun 10 12:38:53 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 10 Jun 2009 10:38:53 +0000
Subject: [Kolab-devel] [issue3690] Calendar: Text "delegated to" right from
	the attendee combobox doesn't disappear,
	if another attendee is selected.
Message-ID: <1244630333.62.0.743297981182.issue3690@intevation.de>


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

enterprise35 20090605.979060

Test:
1. A invites B to an event.
2. B delegates the event to C.
3. C accepts the event.
4. A accepts C.
5. A edit the event and switch to the attendee tab.
6. A clicks on himself.
=> No "Delegates to" is displayed right from the attendee status combobox.
7. A clicks on the delegator and back on himself.
=> Now a "Delegates to ..." is displayed right from the combobox.
Wrong.

----------
assignedto: allen
messages: 20570
nosy: allen, bh, ludwig
priority: minor bug
status: unread
title: Calendar: Text "delegated to" right from the attendee combobox doesn't disappear, if another attendee is selected.
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3690>
___________________________________________________


From kolab-issues at intevation.de  Wed Jun 10 14:39:57 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 10 Jun 2009 12:39:57 +0000
Subject: [Kolab-devel] [issue3691] Calendar: event in a group account shows
	wrong attendee status
Message-ID: <1244637597.42.0.869734326675.issue3691@intevation.de>


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

enterprise35 20090605.979060

Test:
G group account, B kontact user
group account G shares its calendar with B (all rights)
G should out accept all invitations.
1. B invites G to an appointment.
2. B syncs.
3. Enter the update mail into the calendar.
4. B edits the appointment from G's calendar.
=> The appointment described, that the user hasn't responed to the invitation
yet. But G auto accepts every invitation.
This confuses the users who looks at this appointment.

----------
assignedto: allen
messages: 20571
nosy: allen, bh, ludwig
priority: bug
status: unread
title: Calendar: event in a group account shows wrong attendee status
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3691>
___________________________________________________


From kolab-issues at intevation.de  Wed Jun 10 15:16:08 2009
From: kolab-issues at intevation.de (Bernhard Herzog)
Date: Wed, 10 Jun 2009 13:16:08 +0000
Subject: [Kolab-devel] [issue3692] segfault when displaying signed S/MIME
	mail in separate window
Message-ID: <1244639768.09.0.873733813775.issue3692@intevation.de>


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

Tested with kontact from enterprise35 branch rev. 979060:

Kontact's mail layout is configured not to show the message preview pane, so a
double click is required to show messages.  Double click on a signed but not
encrypted S/MIME message.  With the new feature of non-blocking crypto
operations the message is shown immediately but the signature has not been
verified yet.  Now, before the signature has been verified, close the window.  A
while later this leads to a crash with the attached backtrace.

----------
assignedto: allen
files: nonblocking-smime-display-backtrace.txt
messages: 20572
nosy: allen, bh, ludwig, marc, osterfeld, till, vkrause
priority: critical
status: unread
title: segfault when displaying signed S/MIME mail  in separate window
topic: crypto, enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3692>
___________________________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: nonblocking-smime-display-backtrace.txt
Url: http://kolab.org/pipermail/kolab-devel/attachments/20090610/2df1d6d6/nonblocking-smime-display-backtrace.txt

From kolab-issues at intevation.de  Wed Jun 10 15:30:08 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 10 Jun 2009 13:30:08 +0000
Subject: [Kolab-devel] [issue3693] kontact with Online IMAP doesn't
	recognize shared calendar folder
Message-ID: <1244640608.62.0.608822218875.issue3693@intevation.de>


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

enterprise35 20090605.979060

Test:
Req: A and B.
1. A shares his calendar folder with B.
2. B deletes his .kde folder.
3. B configures his account with OnlineIMAP with the kolabwizard.
4. B starts kontact and syncs many times.
=> The folder user/A/calendar is a mail folder and not a calendar folder.
and the events of A's calendar  are not displayed in the calendar.

----------
assignedto: allen
messages: 20573
nosy: allen, bh, ludwig
priority: bug
status: unread
title: kontact with Online IMAP doesn't recognize shared calendar folder
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3693>
___________________________________________________


From kolab-issues at intevation.de  Wed Jun 10 16:00:05 2009
From: kolab-issues at intevation.de (Bernhard Herzog)
Date: Wed, 10 Jun 2009 14:00:05 +0000
Subject: [Kolab-devel] [issue3694] segfault when displaying invitation reply
Message-ID: <1244642405.7.0.566596110127.issue3694@intevation.de>


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

observed with Kontact from enterprise35 branch rev. 979060:

When trying to display a reply to an invititation, Kontact segfaults with the
attached backtrace.  It doesn't crash when displaying an invitation.  Also, it
doesn't matter whether the event to which the reply applies is still present in
the calendar or not.

----------
assignedto: allen
files: invitation-reply-formatting-traceback.txt
messages: 20574
nosy: allen, bh, ludwig, marc, osterfeld, till, vkrause
priority: urgent
status: unread
title: segfault when displaying invitation reply
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3694>
___________________________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: invitation-reply-formatting-traceback.txt
Url: http://kolab.org/pipermail/kolab-devel/attachments/20090610/39a90bbe/invitation-reply-formatting-traceback.txt

From kolab-issues at intevation.de  Thu Jun 11 13:18:54 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 11 Jun 2009 11:18:54 +0000
Subject: [Kolab-devel] [issue3695] kontact crashs while sending a OpenPGP
	enc and sign mail
Message-ID: <1244719134.23.0.281479474833.issue3695@intevation.de>


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

enteprise4 windows 20090522.971344

Test:
1. Configured kontact with kolab wizard.
2. Add the OpenPGP keys to the identity.
3. Send a OpenPGP encrypted and signed mail to another user.
  (It was the first mail send with this configuration.)
4. Wait a moment.
=> Kontact crashs.

----------
assignedto: allen
messages: 20583
nosy: allen, bh, ludwig
priority: urgent
status: unread
title: kontact crashs while sending a OpenPGP enc and sign mail
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3695>
___________________________________________________


From kolab-issues at intevation.de  Thu Jun 11 14:43:04 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 11 Jun 2009 12:43:04 +0000
Subject: [Kolab-devel] [issue3696] Contacts: Remove  phone number field,
	buttton is disabled.
Message-ID: <1244724184.76.0.0185899259014.issue3696@intevation.de>


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

enterprise4 windows tag 20090522.971344

Test:
1. Create a new contacts with 4 phone numbers.
2. Press okay.
3. Edit this contact. 
=> The Remove button under the phone numbers block is disabled.
But there are 4 numbers.
I except the button to be enabled in this case.

----------
assignedto: allen
messages: 20585
nosy: allen, bh, ludwig
priority: minor bug
status: unread
title: Contacts: Remove  phone number field, buttton is disabled.
topic: enterprise4, kde client, windows
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3696>
___________________________________________________


From kolab-issues at intevation.de  Fri Jun 12 19:02:57 2009
From: kolab-issues at intevation.de (charles cunningham)
Date: Fri, 12 Jun 2009 17:02:57 +0000
Subject: [Kolab-devel] [issue3697] Debian packages are .rpm not .deb
Message-ID: <1244826177.65.0.112382271624.issue3697@intevation.de>


New submission from charles cunningham <cc at surreysystems.co.uk>:

The packages for installation on debian linux systems in the
/server/release/kolab-server-2.2.2/ix86-debian5.0 directory are all .rpm files
and not .deb files.

For installation on debian systems they shouid be .deb files and the archive
should be apt compliant.

----------
messages: 20599
nosy: surreysystems
priority: urgent
status: unread
title: Debian packages are .rpm not .deb
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3697>
___________________________________________________


From delonly at gmail.com  Sun Jun 14 23:56:26 2009
From: delonly at gmail.com (Del)
Date: Sun, 14 Jun 2009 23:56:26 +0200
Subject: [Kolab-devel] Adjustment of message-size-limit should be in
	admin-interface
Message-ID: <4A35720A.5040307@gmail.com>

I assume the default 20MB is typically a setting many would like to be 
able to change at will. As such it is important to include it in the 
administrative web-interface.

Cheers,
Del


From kolab-issues at intevation.de  Mon Jun 15 15:56:52 2009
From: kolab-issues at intevation.de (Sascha Wilde)
Date: Mon, 15 Jun 2009 13:56:52 +0000
Subject: [Kolab-devel] [issue3698] S/MIME support in Kolab Web Client
Message-ID: <1245074211.55.0.88200444561.issue3698@intevation.de>


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

Having OpenPGP support in the web client it would be great if we could add
support for S/MIME, too.  This should be done using the new gpg2 stuff which has
full S/MIME support.

Things to consider:

- No end to end encryption.  It might be considerable to inform the
  user about the implications (maybe on the first configuration of the
  feature).

- Revocation lists must be used and updated regularly.

- Server security: with private keys of the users on the server it is
  absolutely vital to ensure that the keys are held as save as
  possible, that means that they have to be at least password
  protected.  This holds true for the OpenPGP feature, too but I don't
  know if and how much auditing was done on this by now...

- surely many more...

----------
assignedto: wrobel
messages: 20607
nosy: martin, thomas, wilde, wrobel
priority: feature
status: unread
title: S/MIME support in Kolab Web Client
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3698>
___________________________________________________


From ml at radoeka.nl  Mon Jun 15 19:10:41 2009
From: ml at radoeka.nl (Richard Bos)
Date: Mon, 15 Jun 2009 19:10:41 +0200
Subject: [Kolab-devel] Adjustment of message-size-limit should be in
	admin-interface
In-Reply-To: <4A35720A.5040307@gmail.com>
References: <4A35720A.5040307@gmail.com>
Message-ID: <200906151910.41947.ml@radoeka.nl>

Op zondag 14 juni 2009 23:56:26 schreef Del:
> I assume the default 20MB is typically a setting many would like to be
> able to change at will. As such it is important to include it in the
> administrative web-interface.

please open an issue in the kolab issue tracker at:
https://intevation.de/roundup/kolab/

-- 
Richard


From kolab-issues at intevation.de  Mon Jun 15 19:14:50 2009
From: kolab-issues at intevation.de (Shrenik)
Date: Mon, 15 Jun 2009 17:14:50 +0000
Subject: [Kolab-devel] [issue3699] Mails forwarded as attachments not
	visible in webclient
Message-ID: <1245086090.72.0.617877836465.issue3699@intevation.de>


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

Tested with Mozilla Thunderbird:

1. Forwarded mails (as attachments) show up as mere .eml attachments
which don't render correctly when clicked upon. Only the
attachment/forwarded mail's header is rendered correctly at the bottom
of the current mail's body depending upon your settings in Options ->
Message Viewing Options.

2. Forwarded mails (html, as inline) show up as mere unnamed html
attachments which open in a new tab/window in the default browser when
clicked upon. This is despite any combination of settings in the Options
-> Message Viewing Options.

3. Forwarded mails (text, as in-line) show up as desired and expected.

4. HTML mails when forwarded as attachments in plain text mails are
rendered incorrectly from the source itself but show up with full header
and garbled message as sent from source.

So point 1 & 2 are the real show stopper issues. Can anyone else as well test
and confirm the same?

----------
messages: 20609
nosy: sbhura
priority: critical
status: unread
title: Mails forwarded as attachments not visible in webclient
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3699>
___________________________________________________


From kolab-issues at intevation.de  Mon Jun 15 21:35:06 2009
From: kolab-issues at intevation.de (Richard Bos)
Date: Mon, 15 Jun 2009 19:35:06 +0000
Subject: [Kolab-devel] [issue3700] A replacement for c-client is needed
Message-ID: <1245094506.69.0.114020639213.issue3700@intevation.de>


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

The development of c-client stopped in july 2008 as open source application. 
Since it is a shareware application.  For details see the discussion on
kolab-devel: http://www.kolab.org/pipermail/kolab-devel/2009-June/010547.html

Now that the c-client is no longer open-source, but shareware, the claim on
kolab homepage "The implementations offered by us are Free Software (Open
Source)" is no longer true.

I add some information from the c-client later to this issue, but the overall is
(I think) that a replacement needs to found.  The replacement can either be a
fork of the project (with all its complications), or perhaps using libraries
from the horde project.

----------
assignedto: thomas
messages: 20610
nosy: bernhard, martin, rbos, thomas, wilde, wrobel
priority: critical
status: unread
title: A replacement for c-client is needed
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3700>
___________________________________________________


From kolab-issues at intevation.de  Tue Jun 16 10:12:20 2009
From: kolab-issues at intevation.de (Christian Funke)
Date: Tue, 16 Jun 2009 08:12:20 +0000
Subject: [Kolab-devel] [issue3701] The 1st.Readme should state that the
	webclient assumes convert and gpg to be installed
Message-ID: <1245139940.32.0.701734838516.issue3701@intevation.de>


New submission from Christian Funke <funke at cip.physik.uni-bonn.de>:

While browsing my logs i noticed many calls to /usr/bin/convert by the weblcient
which failed (since I had not installed it). As fa as I can tell the webclient uses

/usr/bin/gpg
/usr/bin/convert
/etc/mime.types (which it uses for mime detection though i am not sure this is
the correct file according to conf.xml it should be the file magic database,
which at least on my system located in /usr/share/magic)

I think the 1st.readme shoud state these "hidden" dependencies

Greets, Christian

----------
messages: 20612
nosy: eknuf
priority: bug
status: unread
title: The 1st.Readme should state that the webclient assumes convert and gpg to be installed
topic: docs
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3701>
___________________________________________________


From kolab-issues at intevation.de  Tue Jun 16 12:04:28 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 16 Jun 2009 10:04:28 +0000
Subject: [Kolab-devel] [issue3702] Strange things happens with the new dbus.
Message-ID: <1245146667.85.0.670929709499.issue3702@intevation.de>


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

observed with enterprise4 windows 20090605.977848

I observered some strange effects while using e4 with dbus4win-src.
I haven't found a way to reproduce it, yet. 
While using two kontacts on one machine I found:
* One time I created a new appointment and two appointments were entered into
the calendar.
* After closing one kontact user and syncing the other user's account the
calendar mails got doubled.
* After closing one kontact user and restarting the kontact of the other user,
the mail component shows wrong mail counts in the inbox and clicking on the
inbox shows no mail in the mail view.

I will continue to test.

----------
assignedto: ludwig
messages: 20614
nosy: allen, bh, ludwig
priority: critical
status: unread
title: Strange things happens with the new dbus.
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3702>
___________________________________________________


From kolab-issues at intevation.de  Wed Jun 17 16:37:45 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 17 Jun 2009 14:37:45 +0000
Subject: [Kolab-devel] [issue3703] basic calendar operations lead to crashs
Message-ID: <1245249465.64.0.121743411769.issue3703@intevation.de>


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

observed with Kontact enterprise4 windows of tag 20090605.977848 built on 20090616
Kontact-Installer-20090605-2.exe

Test:
1. A invites B to an appointment.
2. B syncs.
3. B accepts the appointment.
4. A syncs and enters the update mail into his calendar.
5. A changes the time of the appointment to an hour later.
6. B syncs and tries to enter the update mail.
7. A deletes the appointment.
8. B syncs and removes the appointment from his calendar.

I did this test three times, with a bit different setting.
(Both windows accounts logged in, Only one account logged in)
But at every test I observed crashs of B's Kontact.

----------
assignedto: allen
messages: 20621
nosy: allen, bernhard, bh, ludwig
priority: critical
status: unread
title: basic calendar operations lead to crashs
topic: kde client, kowi
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3703>
___________________________________________________


From kolab-issues at intevation.de  Thu Jun 18 12:20:53 2009
From: kolab-issues at intevation.de (Philipp Zerelles)
Date: Thu, 18 Jun 2009 10:20:53 +0000
Subject: [Kolab-devel] [issue3704] Email Aliases not saved when changed by
	Domain Maintainer
Message-ID: <1245320453.49.0.714324841102.issue3704@intevation.de>


New submission from Philipp Zerelles <pz at matrix-computer.com>:

When changing the Email Aliases of a user as Domain Maintainer, submitting
indicates success but the Email Aliases are not saved.

Doing the same as Manager works.

----------
messages: 20636
nosy: philipp
priority: bug
status: unread
title: Email Aliases not saved when changed by Domain Maintainer
topic: web admin
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3704>
___________________________________________________


From kolab-issues at intevation.de  Fri Jun 19 21:29:00 2009
From: kolab-issues at intevation.de (Richard Bos)
Date: Fri, 19 Jun 2009 19:29:00 +0000
Subject: [Kolab-devel] [issue3705] Last update to kolab2.schema prevents
	openldap to start
Message-ID: <1245439740.69.0.774842655595.issue3705@intevation.de>


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

When using kolab2.schema from cvs (version 1.36) slapd stops with the following
output:

line 341 (attributetype ( 1.3.6.1.4.1.19414.1.1.1.19  NAME 'kolabSalutation' 
DESC 'Salutation like Mr., Mrs, Herr, Frau)'  EQUALITY caseIgnoreMatch  SUBSTR
caseIgnoreSubstringsMatch  SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{64} ))
/etc/openldap/schema/kolab2.schema: line 341 attributetype: Inconsistent
duplicate attributeType: "1.3.6.1.4.1.19414.1.1.1.19"
/etc/openldap/slapd.conf: line 18: <include> handler exited with 1!

Looking for that OID reveals:
kolab2:/etc/openldap/schema # grep 1.3.6.1.4.1.19414.1.1.1.
/etc/openldap/schema/kolab2.schema
......
attributetype ( 1.3.6.1.4.1.19414.1.1.1.18
attributetype ( 1.3.6.1.4.1.19414.1.1.1.19
attributetype ( 1.3.6.1.4.1.19414.1.1.1.19
attributetype ( 1.3.6.1.4.1.19414.1.1.1.20


When assigning kolabSalutation OID 1.3.6.1.4.1.19414.1.1.1.44, the output
becomes:
/etc/openldap/schema/kolab2.schema: line 925 objectclass: AttributeType not
found: "dateOfBirth"
/etc/openldap/slapd.conf: line 18: <include> handler exited with 1!

I stopped here and went back to cvs version 1.35, which works.

I made this bug critical, because as soon as an rpm is made of the current
sources kolab will not start!

This is the cvs change:
http://kolab.org/cgi-bin/viewcvs-

----------
assignedto: martin
messages: 20642
nosy: martin, rbos, thomas, wilde, wrobel
priority: critical
status: unread
title: Last update to kolab2.schema prevents openldap to start
topic: server
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3705>
___________________________________________________


From ml at radoeka.nl  Mon Jun 22 23:15:01 2009
From: ml at radoeka.nl (Richard Bos)
Date: Mon, 22 Jun 2009 23:15:01 +0200
Subject: [Kolab-devel] martin: server/kolabd/kolabd kolab2.schema, 1.36,
	1.37
In-Reply-To: <20090622131844.850B9600839@lists.intevation.de>
References: <20090622131844.850B9600839@lists.intevation.de>
Message-ID: <200906222315.01407.ml@radoeka.nl>

Hi Martin,

what about this:
https://www.intevation.de/roundup/kolab/issue3705
 (Last update to kolab2.schema prevents openldap to start)??


Op maandag 22 juni 2009 15:18:44 schreef cvs at kolab.org:
> Author: martin
>
> Update of /kolabrepository/server/kolabd/kolabd
> In directory doto:/tmp/cvs-serv4267
>
> Modified Files:
> 	kolab2.schema
> Log Message:
> Martin Konold: Added new attribute which contains a comma separated list of
> secure ciphers. (Required for SSL/TLS)
>
>
> Index: kolab2.schema
> ===================================================================
> RCS file: /kolabrepository/server/kolabd/kolabd/kolab2.schema,v
> retrieving revision 1.36
> retrieving revision 1.37
> diff -u -d -r1.36 -r1.37
> --- kolab2.schema	5 Jun 2009 14:14:05 -0000	1.36
> +++ kolab2.schema	22 Jun 2009 13:18:42 -0000	1.37
> @@ -1,7 +1,7 @@
>  # $Id$
> -# (c) 2003, 2004 Tassilo Erlewein <tassilo.erlewein at erfrakon.de>
> -# (c) 2003-2009  Martin Konold <martin.konold at erfrakon.de>
> -# (c) 2003 Achim Frank <achim.frank at erfrakon.de>
> +# (c) 2003-2004 Tassilo Erlewein <tassilo.erlewein at erfrakon.de>
> +# (c) 2003-2009 Martin Konold <martin.konold at erfrakon.de>
> +# (c) 2003      Achim Frank <achim.frank at erfrakon.de>
>  #
>  # Redistribution and use in source and binary forms, with or without
>  # modification, are permitted provided that the following conditions are
> met: @@ -705,6 +705,17 @@
>    EQUALITY booleanMatch
>    SYNTAX 1.3.6.1.4.1.1466.115.121.1.7 )
>
> +# Configurable list of ciphers considered to be secure enough for our
> purposes. +# E.g. TLS 1.0 and SSL 3.0
> +attributetype ( 1.3.6.1.4.1.19414.2.1.801
> +  NAME 'kolabSecureCiphers'
> +  DESC 'comma separated list of ciphers considered to be secure'
> +  EQUALITY caseIgnoreIA5Match
> +  SUBSTR caseIgnoreIA5SubstringsMatch
> +  SINGLE-VALUE
> +  SYNTAX 1.3.6.1.4.1.1466.115.121.1.26{256} )
> +
> +
>  ######################################################
>  # proftpd attributes (unused since Kolab Server 2.2) #
>  ######################################################
> @@ -840,6 +851,7 @@
>          kolabfilter-allow-sender-header $
>          kolabfilter-reject-forged-from-header $
>          kolabPolicyDaemon $
> +        kolabSecureCiphers $
>          proftpd-ftp $
>          proftpd-defaultquota $
>          kolabFreeBusyFuture $
>
>
> _______________________________________________
> Kolab-commits mailing list
> Kolab-commits at kolab.org
> https://kolab.org/mailman/listinfo/kolab-commits

-- 
Richard


From math.parent at gmail.com  Mon Jun 22 23:58:26 2009
From: math.parent at gmail.com (Mathieu Parent)
Date: Mon, 22 Jun 2009 23:58:26 +0200
Subject: [Kolab-devel] martin: server/kolabd/kolabd kolab2.schema, 1.36,
	1.37
In-Reply-To: <200906222315.01407.ml@radoeka.nl>
References: <20090622131844.850B9600839@lists.intevation.de>
	<200906222315.01407.ml@radoeka.nl>
Message-ID: <960738410906221458l56954630veb2b2998f9de4208@mail.gmail.com>

Hi,


On Mon, Jun 22, 2009 at 11:15 PM, Richard Bos<ml at radoeka.nl> wrote:
> Hi Martin,
>
> (...)
>> @@ -1,7 +1,7 @@
>> ?# $Id$
>> -# (c) 2003, 2004 Tassilo Erlewein <tassilo.erlewein at erfrakon.de>
>> -# (c) 2003-2009 ?Martin Konold <martin.konold at erfrakon.de>
>> -# (c) 2003 Achim Frank <achim.frank at erfrakon.de>
>> +# (c) 2003-2004 Tassilo Erlewein <tassilo.erlewein at erfrakon.de>
>> +# (c) 2003-2009 Martin Konold <martin.konold at erfrakon.de>
>> +# (c) 2003 ? ? ?Achim Frank <achim.frank at erfrakon.de>

Those kind of files (functional interface specification) are not
copyrightable under the US law (Don't know under the german law). This
is probably better to remove those copyright statements (approved by
the authors) and replace it with an authors list (public domain?).

The "(c)" doesn't have any power, it should be replaced by "Copyright" or "?".

>> (...)

Regards

Mathieu Parent


From kolab-issues at intevation.de  Wed Jun 24 10:53:32 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 24 Jun 2009 08:53:32 +0000
Subject: [Kolab-devel] [issue3706] copy+ paste of appointments in the
	monthview creates the appointment at a wrong time.
Message-ID: <1245833612.19.0.368958508134.issue3706@intevation.de>


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

observed with Kontact enterprise34 20090522.971351-kk2 on Debian Etch

In the month view copy a day event and paste it at a different day creates the
new event at the current day and not at the selected day.

Test:
1. Switch to the calendar of Kontact.
2. Aktivate the monthview.
3. Create a new day event.
4. RMB->Copy on the event.
5. Select a day (different than the current day) and RMB->Paste.
=> The pasted day is shown at the current day and there is no event at the
selected day.

----------
assignedto: allen
messages: 20655
nosy: allen, bh, ludwig
priority: bug
status: unread
title: copy+ paste of appointments in the monthview creates the appointment at a wrong time.
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3706>
___________________________________________________


From kolab-issues at intevation.de  Wed Jun 24 15:38:17 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Wed, 24 Jun 2009 13:38:17 +0000
Subject: [Kolab-devel] [issue3707] A sent UTF-16 mail is missing the
	Content-Type
Message-ID: <1245850697.8.0.437287875518.issue3707@intevation.de>


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

observed with Kontact enterprise4 windows 20090605.977848 -7

A sent mail, which text encoding is changed to UTF-16, is sent. The mail doesn't
contain a Content-Type with charset.

An example is:
From: Kowi1 Test <kowi1test at test.hq>
X-KMail-Fcc: sent-mail
To: Kowi Testnutzer2 <kowi2test at test.hq>
Subject: Testmail UTF-16 C
Date: Wed, 24 Jun 2009 15:29:33 +0200
User-Agent: KMail/1.10.1 (enterprise4 0.20090605.977848) (Windows/5.1;
KDE/4.2.2; i686; svn-985608; 2009-06-11)
X-KMail-Transport: Kolab-Server
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
Message-Id: <200906241529.33773.kowi1test at test.hq>
Status: RO
X-Status: RS
X-KMail-EncryptionState:  
X-KMail-SignatureState:  
X-KMail-MDN-Sent:  

//78APYA5AD8APYA5AD8APYA5AAKAAo=

----------
assignedto: allen
messages: 20657
nosy: allen, bh, ludwig
priority: bug
status: unread
title: A sent UTF-16 mail is missing the Content-Type
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3707>
___________________________________________________


From kolab-issues at intevation.de  Thu Jun 25 11:08:17 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 25 Jun 2009 09:08:17 +0000
Subject: [Kolab-devel] [issue3708] To-dos: Field descriptons of category and
	click here are cut.
Message-ID: <1245920897.46.0.956272790341.issue3708@intevation.de>


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

observed with Kontact enterprise4 windows 20090605.977848-7

In the todos plugin "click here to create new todo" and "categories" description
texts are cut.

See screenshot.

I think it is a regression of the merge of the fix of the KDE bug 191225

----------
assignedto: allen
files: to-dos-descriptions-20090625.png
messages: 20659
nosy: allen, bh, ludwig
priority: minor bug
status: unread
title: To-dos: Field descriptons of category and click here are cut.
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3708>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: to-dos-descriptions-20090625.png
Type: image/png
Size: 30124 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090625/9629d63c/to-dos-descriptions-20090625-0001.png

From kolab-issues at intevation.de  Thu Jun 25 11:25:34 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 25 Jun 2009 09:25:34 +0000
Subject: [Kolab-devel] [issue3709] After changing the sending account,
	you need to reenter the SMTPS Password.
Message-ID: <1245921934.49.0.351434918338.issue3709@intevation.de>


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

observed with Kontact enterprise4 windows 20090605.977848-7

Test:
1. Switch to the  mail plugin.
2. Configure Mail->Accounts.->Sending->double click on account.
3. Change the name of the sending account.
4. Send a mail.
=> A password dialogs pops up again.
Why is the password forgotten?

----------
assignedto: allen
messages: 20660
nosy: allen, bh, ludwig
priority: minor bug
status: unread
title: After changing the sending account, you need to reenter the SMTPS Password.
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3709>
___________________________________________________


From kolab-issues at intevation.de  Thu Jun 25 12:33:43 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 25 Jun 2009 10:33:43 +0000
Subject: [Kolab-devel] [issue3710] The calendar reply actions aren't
	translated to German.
Message-ID: <1245926023.31.0.35877778906.issue3710@intevation.de>


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

observed with Kontact enterprise4 windows 20090605.977848-7

Test:
1. User A sends an invitation to B.
2. B syncs and looks at the invitations.
=> Accept,.. are in English. This is wrong, because the user B choosed German as
language.

----------
assignedto: allen
messages: 20664
nosy: allen, bh, ludwig
priority: bug
status: unread
title: The calendar reply actions aren't translated to German.
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3710>
___________________________________________________


From kolab-issues at intevation.de  Thu Jun 25 13:19:37 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Thu, 25 Jun 2009 11:19:37 +0000
Subject: [Kolab-devel] [issue3711] dictionary name isn't translated to German
Message-ID: <1245928777.11.0.711116446967.issue3711@intevation.de>


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

observed with Kontact enterprise4 windows 20090605.977848-7

The dictonary composer field is in English, even when the language of the
Kontact German is. So it is not translated.

Test:
1.Switch to the mail plugin.
2. Open a composer.
3. Activate View->Dictionary.
=> The dictionary text field which appears is in English.

----------
assignedto: allen
messages: 20666
nosy: allen, bh, ludwig
priority: minor bug
status: unread
title: dictionary name isn't translated to German
topic: enterprise4, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3711>
___________________________________________________


From kolab-issues at intevation.de  Thu Jun 25 15:28:29 2009
From: kolab-issues at intevation.de (Karl-Heinz Ruskowski)
Date: Thu, 25 Jun 2009 13:28:29 +0000
Subject: [Kolab-devel] [issue3712] Bulding Pear Head requires CVS passwort
Message-ID: <1245936509.16.0.441949836928.issue3712@intevation.de>


New submission from Karl-Heinz Ruskowski <khruskowski at intevation.de>:

I just tried building Kolab HEAD (PEAR) and the build process ask me for an
interactive password entry. Which is bad because automated build processes will
not work any more.

----------
assignedto: wrobel
messages: 20668
nosy: khruskowski, martin, thomas, wilde, wrobel
priority: critical
status: unread
title: Bulding Pear Head requires CVS passwort
topic: server, web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3712>
___________________________________________________


From kolab-issues at intevation.de  Fri Jun 26 17:30:17 2009
From: kolab-issues at intevation.de (Martin Zapfl)
Date: Fri, 26 Jun 2009 15:30:17 +0000
Subject: [Kolab-devel] [issue3713] Horde login denied for user after
	creating new maintainer
Message-ID: <1246030217.72.0.542506186393.issue3713@intevation.de>


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

A user cannot login to horde after a e.g. a maintainer is created that matches
the users e-Mail address. This is because LDAP search returns 2 rows when doing
SASL authentication. Log file will report "Size limit exceeded"

How to reproduce:
Create a new user with e-Mail Address newuser at domain.tld
User is able to login to horde
Then create maintainer with uid newuser
Now the user cannot login to horde getting error "username or password does not
match"

This error occurs because the SASL filter matches the keyword newuser when
searching %u (in this case newuser) for attributes mail and uid.

----------
assignedto: martinzapfl
messages: 20676
nosy: martinzapfl
status: unread
title: Horde login denied for user after creating new maintainer
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3713>
___________________________________________________


From kolab-issues at intevation.de  Fri Jun 26 17:30:41 2009
From: kolab-issues at intevation.de (Martin Zapfl)
Date: Fri, 26 Jun 2009 15:30:41 +0000
Subject: [Kolab-devel] [issue3714] Horde login denied for user after
	creating new maintainer
Message-ID: <1246030241.81.0.572158094287.issue3714@intevation.de>


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

A user cannot login to horde after a e.g. a maintainer is created that matches
the users e-Mail address. This is because LDAP search returns 2 rows when doing
SASL authentication. Log file will report "Size limit exceeded"

How to reproduce:
Create a new user with e-Mail Address newuser at domain.tld
User is able to login to horde
Then create maintainer with uid newuser
Now the user cannot login to horde getting error "username or password does not
match"

This error occurs because the SASL filter matches the keyword newuser when
searching %u (in this case newuser) for attributes mail and uid.

----------
assignedto: martinzapfl
messages: 20677
nosy: martinzapfl
status: unread
title: Horde login denied for user after creating new maintainer
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3714>
___________________________________________________


From kolab-issues at intevation.de  Fri Jun 26 17:36:26 2009
From: kolab-issues at intevation.de (Martin Zapfl)
Date: Fri, 26 Jun 2009 15:36:26 +0000
Subject: [Kolab-devel] [issue3715] Horde login denied for user after
	creating new maintainer
Message-ID: <1246030586.45.0.0222598898363.issue3715@intevation.de>


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

A user cannot login to horde after a e.g. a maintainer is created that matches
the users e-Mail address. This is because LDAP search returns 2 rows when doing
SASL authentication. Log file will report "Size limit exceeded"

How to reproduce:
Create a new user with e-Mail Address newuser at domain.tld
User is able to login to horde
Then create maintainer with uid newuser
Now the user cannot login to horde getting error "username or password does not
match"

This error occurs because the SASL filter matches the keyword newuser when
searching %u (in this case newuser) for attributes mail and uid.

----------
assignedto: martinzapfl
messages: 20678
nosy: martinzapfl
status: unread
title: Horde login denied for user after creating new maintainer
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3715>
___________________________________________________


From kolab-issues at intevation.de  Fri Jun 26 17:36:52 2009
From: kolab-issues at intevation.de (Martin Zapfl)
Date: Fri, 26 Jun 2009 15:36:52 +0000
Subject: [Kolab-devel] [issue3716] Horde login denied for user after
	creating new maintainer
Message-ID: <1246030611.95.0.199187512949.issue3716@intevation.de>


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

A user cannot login to horde after a e.g. a maintainer is created that matches
the users e-Mail address. This is because LDAP search returns 2 rows when doing
SASL authentication. Log file will report "Size limit exceeded"

How to reproduce:
Create a new user with e-Mail Address newuser at domain.tld
User is able to login to horde
Then create maintainer with uid newuser
Now the user cannot login to horde getting error "username or password does not
match"

This error occurs because the SASL filter matches the keyword newuser when
searching %u (in this case newuser) for attributes mail and uid.

----------
messages: 20679
nosy: martinzapfl
status: chatting
title: Horde login denied for user after creating new maintainer
topic: web client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3716>
___________________________________________________


From kolab-issues at intevation.de  Mon Jun 29 14:58:13 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Mon, 29 Jun 2009 12:58:13 +0000
Subject: [Kolab-devel] [issue3717] Invitation with description and
	attachment loses its attachment.
Message-ID: <1246280293.17.0.784878646307.issue3717@intevation.de>


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

observed with Kontact enterprise35 20090626.987805

Test:
1. A invites B to an appointment with description and attachment.
2. B syncs and looks at the invitation.
=> The invitation doesn't contain an attachment.

----------
assignedto: allen
messages: 20693
nosy: allen, bh, ludwig
priority: urgent
status: unread
title: Invitation with description and attachment loses its attachment.
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3717>
___________________________________________________


From kolab-issues at intevation.de  Mon Jun 29 15:26:45 2009
From: kolab-issues at intevation.de (=?utf-8?q?Emanuel_Sch=C3=BCtze?=)
Date: Mon, 29 Jun 2009 13:26:45 +0000
Subject: [Kolab-devel] [issue3718] No warning ("number of reciepients >5")
	for invitation email
Message-ID: <1246282005.05.0.671358176698.issue3718@intevation.de>


New submission from Emanuel Sch?tze <emanuel at intevation.de>:

Create a new event. 
Add more than 5 attendees and send an invitation email.
-> The user should _not_ see the warning "number of reciepients >5" (enabled in
kmail settings) for invitation emails. The email should be sent without this
warning.

----------
assignedto: allen
messages: 20695
nosy: allen, bh, emanuel, ludwig
status: unread
title: No warning ("number of reciepients >5") for invitation email
topic: enterprise35, kde client, kkc
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3718>
___________________________________________________


From kolab-issues at intevation.de  Mon Jun 29 15:41:06 2009
From: kolab-issues at intevation.de (=?utf-8?q?Emanuel_Sch=C3=BCtze?=)
Date: Mon, 29 Jun 2009 13:41:06 +0000
Subject: [Kolab-devel] [issue3719] Missing linebreaks in description of
	invitation messages
Message-ID: <1246282866.57.0.435077261.issue3719@intevation.de>


New submission from Emanuel Sch?tze <emanuel at intevation.de>:

Create new appointment. Add long description text with linebreaks/paragraphs.
Invite attendees.
Look at the description in the invitation message:
 a) in e35: no linebreaks
 b) in e4 (Windows): linebreaks with visible "<p>" Tags.
    [e4 (Mac) is ok]

----------
assignedto: allen
messages: 20696
nosy: allen, emanuel, ludwig
priority: bug
status: unread
title: Missing linebreaks in description of invitation messages
topic: enterprise35, kde client, kkc
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3719>
___________________________________________________


From kolab-issues at intevation.de  Tue Jun 30 14:29:14 2009
From: kolab-issues at intevation.de (Bernhard Reiter)
Date: Tue, 30 Jun 2009 12:29:14 +0000
Subject: [Kolab-devel] [issue3720] Online imap hang in select of
	KIO::SlaveBase::dispatchLoop under certain network conditions
Message-ID: <1246364954.07.0.349077477317.issue3720@intevation.de>


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

Online IMAP Account can hang on email check
then it does not display the contents of the INBOX folder anymore
even if the kio_imap4 slave is killed.
See 20090630-kontact-hang-1.png which has the progress bar that does not
go away anymore.

Architecture: i386
Source: kdepim
Version: 4:3.5.10.enterprise.0.20090522.971351-kk2

1 S uxr      12205 32520  0  80   0 - 14864 -      01:35 ?        00:00:16 
kio_imap4 [kdeinit] 
imaps /tmp/ksocket-uxr/klauncherJpnNLa.slave-socket /tmp/ksocket-uxr/kontact7Vnlkc.slave-socket

strace gives me only one line:
select(6, [5], NULL, NULL, NULL <unfinished ...>

Killing 12205 does not help to get the view of emails back, stopping and 
restarting Kontact does.

gdb) bt
#0  0xb7d36cd7 in select () from /lib/tls/libc.so.6
#1  0xb7ab3bbb in KIO::SlaveBase::dispatchLoop (this=0x808b898) 
at /build/buildd/kdelibs-3.5.5a.dfsg.1/./kio/kio/slavebase.cpp:282
#2  0xb663fc3c in kdemain (argc=4, argv=0x805b538) at imap4.cc:135
#3  0x0804e457 in launch (argc=4, _name=0x8079a74 "kio_imap4", 
args=0x8079add "", cwd=0x0, envc=0, envs=0x8079ae2 "", reset_env=false, 
tty=0x0, avoid_loops=false,
    startup_id_str=0x8050d2e "0") 
at /build/buildd/kdelibs-3.5.5a.dfsg.1/./kinit/kinit.cpp:673
        #4  0x0804ecf9 in handle_launcher_request (sock=11) 
at /build/buildd/kdelibs-3.5.5a.dfsg.1/./kinit/kinit.cpp:1240
        #5  0x0804f092 in handle_requests (waitForPid=0) 
at /build/buildd/kdelibs-3.5.5a.dfsg.1/./kinit/kinit.cpp:1443
        #6  0x080502b1 in main (argc=5, argv=0xbfc3c054, envp=0xbfc3c06c) 
at /build/buildd/kdelibs-3.5.5a.dfsg.1/./kinit/kinit.cpp:1909
        #7  0xb7c86ea8 in __libc_start_main () from /lib/tls/libc.so.6
        #8  0x0804b911 in _start () at ../sysdeps/i386/elf/start.S:119

It seems there is a code path where there is no timeout on the used select().

----------
assignedto: allen
files: 20090630-kontact-hang-1.png
messages: 20712
nosy: allen, bernhard, ludwig, till
priority: bug
status: unread
title: Online imap hang in select of KIO::SlaveBase::dispatchLoop under certain network conditions
topic: enterprise35, kde client
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3720>
___________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 20090630-kontact-hang-1.png
Type: image/png
Size: 21477 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20090630/bf58dc5f/20090630-kontact-hang-1-0001.png

From kolab-issues at intevation.de  Tue Jun 30 14:54:44 2009
From: kolab-issues at intevation.de (Ludwig Reiter)
Date: Tue, 30 Jun 2009 12:54:44 +0000
Subject: [Kolab-devel] [issue3721] Calendar: The German name of the
	Import->Import from UNIX ical tool is problematic
Message-ID: <1246366484.15.0.0568944543445.issue3721@intevation.de>


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

observed with Kontact enterprise35 20090626.987805

Test:
Use German as language.
1. Switch to the calendar plugin.
2. Click on Import and look at menu.
=> The German translation is "Aus UNIX Ical importieren". This can lead to
misunderstanding. It should be: "Aus UNIX Ical Werkzeug importieren".

----------
assignedto: allen
messages: 20713
nosy: allen, bh, ludwig
priority: bug
status: unread
title: Calendar: The German name of the Import->Import from UNIX ical tool is problematic
topic: enterprise35, kde client, kkc
___________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://www.intevation.de/roundup/kolab/issue3721>
___________________________________________________