From issues at kolab.org  Thu Oct  1 10:40:13 2009
From: issues at kolab.org (Arvid Requate)
Date: Thu, 01 Oct 2009 08:40:13 +0000
Subject: [Kolab-devel] [issue3884] No Event Invitation sent to Attendees
	with role	"resource".
In-Reply-To: <1254386413.98.0.612082262377.issue3884@kolab.org>
Message-ID: <1254386413.98.0.612082262377.issue3884@kolab.org>


New submission from Arvid Requate <requate at univention.de>:

Affected: horde-webmailer 1.2.0 with kolab-webclient patches

1. Create an event with attendees. Selecting "Attendance" as "None" creates an
event where the attendee is marked as a "resource":
   "<attendee>[...]<role>resource</role></attendee>"
2. Selecting "Send invitations to all attendees?" sends invitations to all
attendees except the ones with role "resource".

One could regard this as two issues, the second beeing the focus of this report:
1. The "Attendance" would maybe better be called "Resource" instead of "None".
2. "all attendees" certainly should include the "resource" roles.


kolab-webclient patches applied:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolab-webclient/

----------
assignedto: wrobel
keyword: web client
messages: 21878
nosy: martin, requate, schwardt, thomas, wilde, wrobel
priority: bug
status: unread
title: No Event Invitation sent to Attendees with role "resource".

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


From issues at kolab.org  Thu Oct  1 11:52:28 2009
From: issues at kolab.org (Arvid Requate)
Date: Thu, 01 Oct 2009 09:52:28 +0000
Subject: [Kolab-devel] [issue3885] Modifying start date of recurring events
	does not update	recurrance dates
In-Reply-To: <1254390748.99.0.802333413902.issue3885@kolab.org>
Message-ID: <1254390748.99.0.802333413902.issue3885@kolab.org>


New submission from Arvid Requate <requate at univention.de>:

Affected: horde-webmailer 1.2.0 with kolab-webclient patches

1. Create an event with recurrance (e.g. cycle=monthly, type=weekday), Save it.
2. Open it and change the "Time Span">Start On date to one day later (or
earlier). Save it.
3. Open the Calender e.g. in day view (using 'Goto') on the new start date.
4. Goto to the same weekday in the following month, where the recurrance would
be expected.

The observed bug is, that only the first incident of the event series is shown
on the new date, while all other incidents are not shown on the new weekday. In
the server side Kolab data only the <start-date> is modified, but the details in
the <recurrence> node are unchanged. In the particular 'weekday' test, the
attibute <day>sunday</day> was unchanged, but the general effect was also
reproducable with other recurrance types and cycles.

kolab-webclient patches applied:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolab-webclient/

----------
assignedto: wrobel
keyword: web client
messages: 21879
nosy: martin, requate, schwardt, thomas, wilde, wrobel
priority: bug
status: unread
title: Modifying start date of recurring events does not update recurrance dates

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


From issues at kolab.org  Thu Oct  1 12:03:31 2009
From: issues at kolab.org (Arvid Requate)
Date: Thu, 01 Oct 2009 10:03:31 +0000
Subject: [Kolab-devel] [issue3886] Recurring Events of type yearday are not
	interpreted as	recurring events
In-Reply-To: <1254391411.3.0.415144047862.issue3886@kolab.org>
Message-ID: <1254391411.3.0.415144047862.issue3886@kolab.org>


New submission from Arvid Requate <requate at univention.de>:

Affected: horde-webmailer 1.2.0 with kolab-webclient patches

1. Create a recurring event with "Yearly: Recurs every 1 year(s) on the same day
of the year".
2. Look at the Calendar on the same yearday the next year.
3. Look at the Calendar on the start date (this/first year)
4. Open the Event

The observed effect is, that the Event is not shown in the following year and
that it is not marked with the recurring icon on the start date (this/first
year). In the edit dialog it looks as if no recurrence had been selected at all.

kolab-webclient patches applied:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolab-webclient/

----------
assignedto: wrobel
keyword: web client
messages: 21880
nosy: martin, requate, schwardt, thomas, wilde, wrobel
status: unread
title: Recurring Events of type yearday are not interpreted as recurring events

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


From issues at kolab.org  Thu Oct  1 12:13:47 2009
From: issues at kolab.org (Arvid Requate)
Date: Thu, 01 Oct 2009 10:13:47 +0000
Subject: [Kolab-devel] [issue3887] Recurring "all day" events spanning two
	days are only	shown on each first day
In-Reply-To: <1254392027.76.0.583414379274.issue3887@kolab.org>
Message-ID: <1254392027.76.0.583414379274.issue3887@kolab.org>


New submission from Arvid Requate <requate at univention.de>:

1. Create a recurring "all day" event spanning two days, i.e. with "Time
Span">End On date one day later than the "Time Span">Start On date. Select some
recurrence (e.g. cycle=monthly). Save it.
2. Open the Calendar in day view on the date entered as "Time Span">End On date.

The observed effect was, that the "all day" event is not shown on the second
day, (i.e. the "End On" date).

Affected: horde-webmailer 1.2.0 with kolab-webclient patches
kolab-webclient patches applied:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolab-webclient/

----------
assignedto: wrobel
keyword: web client
messages: 21881
nosy: martin, requate, schwardt, thomas, wilde, wrobel
status: unread
title: Recurring "all day" events spanning two days are only shown on each first day

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


From issues at kolab.org  Thu Oct  1 12:23:05 2009
From: issues at kolab.org (Arvid Requate)
Date: Thu, 01 Oct 2009 10:23:05 +0000
Subject: [Kolab-devel] [issue3888] Organizer field not saved in Tasks
	written by	kolab-webclient
In-Reply-To: <1254392585.02.0.451935093698.issue3888@kolab.org>
Message-ID: <1254392585.02.0.451935093698.issue3888@kolab.org>


New submission from Arvid Requate <requate at univention.de>:

1. The display-name and smtp-address of the organizer are left empty in tasks
created by kolab-webclient. The Organizer field shown is empty.
2. A task created e.g. by the Kontact groupware client shows the proper
Organizer but editing the event, changing some detail and saving it removes the
organizer field.

Affected: horde-webmailer 1.2.0 with kolab-webclient patches
kolab-webclient patches applied:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolab-webclient/

----------
assignedto: wrobel
keyword: web client
messages: 21882
nosy: martin, requate, schwardt, thomas, wilde, wrobel
status: unread
title: Organizer field not saved in Tasks written by kolab-webclient

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


From issues at kolab.org  Thu Oct  1 13:33:49 2009
From: issues at kolab.org (Arvid Requate)
Date: Thu, 01 Oct 2009 11:33:49 +0000
Subject: [Kolab-devel] [issue3890] kolabHomeServer not selected for freebusy
	due to logic	error in Kolab Patch
In-Reply-To: <1254396829.56.0.597538682212.issue3890@kolab.org>
Message-ID: <1254396829.56.0.597538682212.issue3890@kolab.org>


New submission from Arvid Requate <requate at univention.de>:

The call $user_object->getServer('freebusy') call in
horde-webmail/lib/Horde/Kolab/Session.php returns 'https://localhost/freebusy'
neglecting the users kolabHomeServer attribute, leading to a false free-busy
trigger URL.

This is due to an intervted-logic error in
horde-webmail/lib/Horde/Kolab/Server/Object/user.php, which was introduced by
the Kolab patch

KOLAB/t_framework_HK_GW_Kolab__Server_RewriteExtend.diff

The attached diff shows the patch necessary to fix this issue.

Affected: horde-webmailer 1.2.0 with kolab-webclient patches
kolab-webclient patches applied:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolab-webclient/

----------
assignedto: wrobel
files: t_framework_UV_patch_for_KOLAB_t_framework_HK_GW_Kolab__Server_RewriteExtend.diff
keyword: web client
messages: 21884
nosy: martin, requate, schwardt, thomas, wilde, wrobel
status: unread
title: kolabHomeServer not selected for freebusy due to logic error in Kolab Patch

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3890>
______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: t_framework_UV_patch_for_KOLAB_t_framework_HK_GW_Kolab__Server_RewriteExtend.diff
Type: text/x-diff
Size: 631 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091001/2e098fec/t_framework_UV_patch_for_KOLAB_t_framework_HK_GW_Kolab__Server_RewriteExtend.bin

From issues at kolab.org  Thu Oct  1 13:49:35 2009
From: issues at kolab.org (Arvid Requate)
Date: Thu, 01 Oct 2009 11:49:35 +0000
Subject: [Kolab-devel] [issue3891] Undefined variable: suid_ts ,
	Kolab SyncML patch update needed
In-Reply-To: <1254397775.11.0.905770494107.issue3891@kolab.org>
Message-ID: <1254397775.11.0.905770494107.issue3891@kolab.org>


New submission from Arvid Requate <requate at univention.de>:

Apache2 error logs show the PHP error "Undefined variable: suid_ts in
/usr/share/horde3/lib/SyncML/Backend/Horde.php on line 212".

This seems to be introduced by a code change in the Horde SyncML implementation,
calling for an adjustment of the Kolab patch t_SyncML_HK_GW_CombinedFixes.diff.

The proposed changes are shown in the attached diff. If this patch leaves SyncML
in a funtional state is still unconfirmed, but it did not seem to cause adverse
effects. Indeed the time needed for synchronization reduced quite a bit after
application of this patch (without reducing the number of entries transmitted).

Affected: horde-webmailer 1.2.0 with kolab-webclient patches
kolab-webclient patches applied:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolab-webclient/

----------
assignedto: wrobel
files: t_SyncML_UV_patch_for_KOLAB_t_SyncML_HK_GW_CombinedFixes.diff
keyword: web client
messages: 21886
nosy: martin, requate, schwardt, thomas, wilde, wrobel
status: unread
title: Undefined variable: suid_ts , Kolab SyncML patch update needed

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3891>
______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: t_SyncML_UV_patch_for_KOLAB_t_SyncML_HK_GW_CombinedFixes.diff
Type: text/x-diff
Size: 1178 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091001/5e46c5ef/t_SyncML_UV_patch_for_KOLAB_t_SyncML_HK_GW_CombinedFixes.bin

From issues at kolab.org  Thu Oct  1 14:02:10 2009
From: issues at kolab.org (Arvid Requate)
Date: Thu, 01 Oct 2009 12:02:10 +0000
Subject: [Kolab-devel] [issue3892] Patch enabling SyncML support for the SE
	P1i mobile phone
In-Reply-To: <1254398530.6.0.139191386073.issue3892@kolab.org>
Message-ID: <1254398530.6.0.139191386073.issue3892@kolab.org>


New submission from Arvid Requate <requate at univention.de>:

The attached patch was necessary to make the SE P1i mobile phone work with SyncML.

----------
assignedto: thomas
files: t_SyncML_UV_message_size_p1i.diff
keyword: server
messages: 21887
nosy: martin, requate, schwardt, thomas, wilde, wrobel
priority: feature
status: unread
title: Patch enabling SyncML support for the SE P1i mobile phone

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3892>
______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: t_SyncML_UV_message_size_p1i.diff
Type: text/x-diff
Size: 859 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091001/3a88973d/t_SyncML_UV_message_size_p1i.bin

From issues at kolab.org  Thu Oct  1 15:32:56 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Thu, 01 Oct 2009 13:32:56 +0000
Subject: [Kolab-devel] [issue3893] Printing an event with more than 50 lines
	in the details	cuts the details
In-Reply-To: <1254403976.98.0.917796505145.issue3893@kolab.org>
Message-ID: <1254403976.98.0.917796505145.issue3893@kolab.org>


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

observed with Kontact e35 20090925.1027940-kk1

Test:
1. Create a new event with 50 lines details.
2. Print this event and send the output to a file.
3. Look at the file.
=> the details of the event are cut at line 34. Lines 35-50 are lost in the print.

----------
assignedto: allen
keyword: enterprise35, kde client
messages: 21892
nosy: allen, ludwig
priority: bug
status: unread
title: Printing an event with more than 50 lines in the details cuts the details

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


From issues at kolab.org  Thu Oct  1 15:45:28 2009
From: issues at kolab.org (Arvid Requate)
Date: Thu, 01 Oct 2009 13:45:28 +0000
Subject: [Kolab-devel] [issue3894] SyncML code sends some event data
	non-conformant to vCal	(1.0) standard
In-Reply-To: <1254404728.8.0.798237124075.issue3894@kolab.org>
Message-ID: <1254404728.8.0.798237124075.issue3894@kolab.org>


New submission from Arvid Requate <requate at univention.de>:

The attached patch fixes two Bugs in the SyncML code that affect the same
function. The Patch for A) only changes one line.

A) SyncML sends end dates not as DateTime, causing BB SyncJE to drop events

1. Create a recurring event with end date (e.g. weekly on days TH and FR).
2. Syncronize to BB/SyncJE client.

The event does not show up in the BB calendar.

Horde seems to send the following recurrence info in the vCal data:
       W1 TH FR 20090502
The vCal-Standard (1.0) mentions the following example:
-------------------------------------------------------
"  Every other week on Monday Wednesday and Friday until 12/24/94:
       W2 MO WE FR 19941224T000000Z"
-------------------------------------------------------

The attached patch changes _exportDate into _exportDateTime, causing BB/SyncJE
to accept the events.

B) For recurring events SyncML sends number of incedences in vCal duration
instead of the number of weeks.

1. Create an event recurring e.g. twice weekly (e.g. TH and FR) with a "Recur
Until" setting of "4 recurrences". [ Note: with the patch for kolab/issue3846
Kronolith shows this as 4 incidents. (i.e. <range type="number">4</range>
according to the kolab format standard v2.0rc7) ]
2. Syncronize to BB/SyncJE client.

The vCal data Horde SyncML sends for this event shows:
 W1 TH FR #4
i.e. Horde sends the number of incidences as "duration". The vCal-Standard (1.0)
expects the number of weeks instead.

The vCal-Standard (1.0) mentions the following examples:
-------------------------------------------------------
"Below is the form of a typical rule. This example causes events to be generated
every other week on Tuesday and Thursday, for 8 occurrences: 
W2 TU TH #4
Where, W is the Frequency, 2 is the Interval, TU and TH are the optional
Frequency Modifiers, and #4 is the Duration."

and

"Weekly on Tuesday and Thursday for 5 weeks:
    W1 TU TH #5"
-------------------------------------------------------

The attached patch fixes the encoding of the "duration" to weeks instead of
incidences. There still might be room for improvement, in partiticular for
events with recurrence incident numbers that are not simply a multiple of the
number of incidences per week. Maybe in this case it might be better to use
"ceil" instead for "floor" rounding and specify the end-date. The patch shows
the necessary point of adjustment.


Affected: horde-webmailer 1.2.0 with kolab-webclient patches
kolab-webclient patches applied:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolab-webclient/

----------
assignedto: thomas
files: t_SyncML_UV_recurring_events_week_count.diff
keyword: patch, server
messages: 21893
nosy: martin, requate, schwardt, thomas, wilde, wrobel
status: unread
title: SyncML code sends some event data non-conformant to vCal (1.0) standard

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3894>
______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: t_SyncML_UV_recurring_events_week_count.diff
Type: text/x-diff
Size: 1327 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091001/40ead0b8/t_SyncML_UV_recurring_events_week_count-0001.bin

From ml at radoeka.nl  Thu Oct  1 17:55:23 2009
From: ml at radoeka.nl (Richard Bos)
Date: Thu, 1 Oct 2009 17:55:23 +0200
Subject: [Kolab-devel] annotations patch in c-client what is the status?
In-Reply-To: <200909020949.53616.bernhard@intevation.de>
References: <200906032321.30110.ml@radoeka.nl>
	<200907240923.58654.martin.konold@erfrakon.de>
	<200909020949.53616.bernhard@intevation.de>
Message-ID: <200910011755.23690.ml@radoeka.nl>

Op woensdag 02 september 2009 09:49:47 schreef Bernhard Reiter:
> > > BH (in cc) will post later where to find the library.
> >
> > I did not see the relevant post.
>
> Sorry for the delay, we are planning to have a techbase wiki page but this
> did not happen as fast as I was hoping for.

Any news on this?  In the meantime BH dropped from the Cc:

-- 
Richard


From issues at kolab.org  Fri Oct  2 10:39:21 2009
From: issues at kolab.org (Christian Funke)
Date: Fri, 02 Oct 2009 08:39:21 +0000
Subject: [Kolab-devel] [issue3895] Openldap: loglevel should be set to none
	in slapd.conf
In-Reply-To: <1254472761.84.0.0878203774114.issue3895@kolab.org>
Message-ID: <1254472761.84.0.0878203774114.issue3895@kolab.org>


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

The current slapd.conf sets the loglevel to 0 supressing all logging. Setting the 
loglevel to none will only log errors. Imho this is very useful information for 
system administrators and a sensible choice for the default loglevel (logs dont 
get flooded but important information is available).

Christian

----------
messages: 21900
nosy: eknuf
priority: minor bug
status: unread
title: Openldap: loglevel should be set to none in slapd.conf

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


From issues at kolab.org  Fri Oct  2 10:57:41 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Fri, 02 Oct 2009 08:57:41 +0000
Subject: [Kolab-devel] [issue3896] Sync buttons are missing
In-Reply-To: <1254473861.61.0.560683599596.issue3896@kolab.org>
Message-ID: <1254473861.61.0.560683599596.issue3896@kolab.org>


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

observed with Kontact e4 windows 20090925-1

The sync buttons in tasks, contacts and calendar plugins are missing.

----------
assignedto: allen
keyword: enterprise4, kde client
messages: 21901
nosy: allen, ludwig
priority: urgent
status: unread
title: Sync buttons are missing

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


From issues at kolab.org  Fri Oct  2 11:06:15 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Fri, 02 Oct 2009 09:06:15 +0000
Subject: [Kolab-devel] [issue3897] kolabwizard sometimes crashs
In-Reply-To: <1254474375.24.0.217705726123.issue3897@kolab.org>
Message-ID: <1254474375.24.0.217705726123.issue3897@kolab.org>


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

observed with Kontact e4 windows 20090925-1

Sometimes the kolabwizard crashes in a multi-user environment.
Windows user A configures Kolab with the wizard and kontact ok.
Change without logoff to user B.
Try to configure the account with the wizard, but after configuring of the
password and enter it into the kwallet pw dialog, the kolabwizard crash.
This should not happen.

----------
assignedto: allen
keyword: enterprise4, kde client, windows
messages: 21902
nosy: allen, ludwig
priority: bug
status: unread
title: kolabwizard sometimes crashs

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


From thomas at intevation.de  Fri Oct  2 12:53:26 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 2 Oct 2009 12:53:26 +0200
Subject: [Kolab-devel] Kolab Security Issue 24 20091002 (imapd)
Message-ID: <20091002125229.493864048.thomas@intevation.de>

Kolab Security Issue 24 20091002
================================

Package:              Kolab Server, Cyrus IMAP Server
Vulnerability:        various
Kolab Specific:       no
Dependent Packages:   none


Summary
~~~~~~~

The Cyrus IMAP mail server supports the SIEVE mail filtering language. Cyrus
IMAP versions 2.2 through 2.3.14 contain a buffer overflow vulnerability that
may be triggered by a specially crafted SIEVE script. To install this type of
script, the attacker would need to have direct access to a mail account on the
server.


Affected Versions
~~~~~~~~~~~~~~~~~

This affects versions of Cyrus IMAP Server up to version 2.3.14
Kolab Server 2.2.2 and previous releases are affected.


Fix
~~~

Upgrade Cyrus IMAP Server to imapd-2.3.13-20081020_kolab3, which
includes a patch to fix the problem.

OpenPKG packages for Kolab Server 2.2.2 are available from
http://files.kolab.org/server/security-updates/20091002/
or from the mirrors listed on http://kolab.org/mirrors.html

A binary RPM for Kolab Server 2.2.2 (ix86 Debian GNU/Linux Lenny)
is available as imapd-2.3.13-20081020_kolab3.ix86-debian5.0-kolab.rpm

A binary RPM for Kolab Server 2.2.2 (ix86 Debian GNU/Linux Etch)
is available as imapd-2.3.13-20081020_kolab3.ix86-debian4.0-kolab.rpm

Above source and binary packages have been verified to work with Kolab
Server 2.2.0, so you can upgrade the imapd package without doing a full
upgrade.

All other server versions: Please upgrade to Kolab Server 2.2.x and install
the updated imapd package.


You can check the integrity of the downloaded files with:

$ gpg --keyserver keys.gnupg.net --recv-key 5816791A
  or import the key from https://www.intevation.de/~thomas/gpg_pub_key.asc
$ gpg --verify SHA1SUMS.sig
$ sha1sum -c SHA1SUMS


The source package can be compiled and installed on your Kolab Server with:

# su - kolab
$ openpkg rpm --rebuild --define 'with_fsl yes' --define 'with_group yes' \
  --define 'with_group_igncase yes' --define 'with_atvdom yes' \
  --define 'with_ldap yes' --define 'with_annotate yes' \
  --define 'with_morelogging yes' --define 'with_kolab yes' \
  --define 'with_kolab_nocaps yes' \
  ...path/to.../imapd-2.3.13-20081020_kolab3.src.rpm
$ openpkg rpm \
  -Uvh /kolab/RPM/PKG/imapd-2.3.13-20081020_kolab3.<ARCH>-<OS>-kolab.rpm

To install a binary package, just skip the rebuild step:

# su - kolab
$ openpkg rpm \
  -Uvh ...path/to.../imapd-2.3.13-20081020_kolab3.<ARCH>-<OS>-kolab.rpm

Alternatively you can copy or symlink all source and binary rpms and
install-kolab.sh of your current installation and the source rpm of this
security advisory into a new directory and follow the instructions below
"Generating your own 00INDEX.rdf for installations or upgrades" in
1st.README to generate a new installer which can be used to compile and
install the new package without having to specify the "--define" options.


Details
~~~~~~~

http://lists.andrew.cmu.edu/pipermail/cyrus-announce/2009-September/000068.html
	Cyrus IMAPd 2.2.13p1 & 2.3.15 Released

https://lists.andrew.cmu.edu/pipermail/cyrus-cvs/2009-September/001253.html
https://bugzilla.andrew.cmu.edu/cgi-bin/cvsweb.cgi/src/sieve/script.c.diff?r1=1.67&r2=1.68
	Upstream patch for src/sieve/script.c by Bron Gondwana

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2632
	CVE-2009-2632


Timeline
~~~~~~~~
    20090909 Cyrus IMAPd 2.2.13p1 & 2.3.15 released.
    20090922 Fix available via Kolab CVS, started testing.
    20091002 Kolab Server security advisory published.

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

From issues at kolab.org  Thu Oct  1 12:56:58 2009
From: issues at kolab.org (issues@kolab.org)
Date: Thu, 01 Oct 2009 10:56:58 +0000
Subject: [Kolab-devel] [issue3889] Kontact crahes if opening/changing
	calendar view (rt#5868)
In-Reply-To: <1254394618.78.0.104441072387.issue3889@kolab.org>
Message-ID: <1254394618.78.0.104441072387.issue3889@kolab.org>


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

First observations:
Some Kontact clients (e35 20090918.1025271) crashes often if the user...
* switch to calender view
* scroll through calender weeks/days (with mouse wheel) 
* close Kontact window in calender view and reopen Kontact
* ...

All users use the side-by-side calender view with shared calenders.

It's currently difficult to reproduce this crash. Only crash logs of some
crashed Kontacts are available (see attachments).

----------
assignedto: till
files: crash-dialog.png
keyword: enterprise35, kde client, kkc
messages: 21883
nosy: allen, emanuel, till
priority: critical
status: unread
title: Kontact crahes if opening/changing calendar view (rt#5868)

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3889>
______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: crash-dialog.png
Type: image/png
Size: 79730 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091001/cc66162f/crash-dialog-0001.png

From ml at radoeka.nl  Fri Oct  2 18:40:35 2009
From: ml at radoeka.nl (Richard Bos)
Date: Fri, 2 Oct 2009 18:40:35 +0200
Subject: [Kolab-devel] patches for cyrus?
Message-ID: <200910021840.36046.ml@radoeka.nl>

Hi,

where can I find the patches for cyrus.  I expected them here:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/patches/cyrus-imapd/cyrus-imapd-2.3.13/
but that directory is clearly empty.  I'm actually looking for the 2.3.14 and 2.3.15
patches.  The ones for 2.3.13 I already have.

-- 
Richard


From issues at kolab.org  Mon Oct  5 11:30:35 2009
From: issues at kolab.org (Thomas Arendsen Hein)
Date: Mon, 05 Oct 2009 09:30:35 +0000
Subject: [Kolab-devel] [issue3898] Mailman "moderator request(s) waiting"
	mail could not be	delivered
In-Reply-To: <1254735035.66.0.363536854696.issue3898@kolab.org>
Message-ID: <1254735035.66.0.363536854696.issue3898@kolab.org>


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

Mailman wants to send a mail "470 (listname) moderator request(s) waiting" to
the list moderators, but kolabmailboxfilter of Kolab Server 2.2.2 does not
want to deliver it.

The mail contains 470 lines starting with "From:" in the body, maybe
kolabfilter chokes on this? I'll verify this.

Here are the logs:

/kolab/var/postfix/log/postfix.log:

Oct 05 10:59:41 kolab <info> postfix/qmgr[30257]: E5D1994D143:
from=<mailman-bounces at example.com>, size=79552, nrcpt=2 (queue active)
Oct 05 10:59:41 kolab <info> postfix/pipe[14792]: E5D1994D143:
to=<user1 at example.com>, relay=kolabmailboxfilter, delay=97165,
delays=97165/0/0/0.36, dsn=4.3.0, status=deferred (temporary failure. Command
output: Invalid response code received from server, original code )
Oct 05 10:59:41 kolab <info> postfix/pipe[14799]: E5D1994D143:
to=<user2 at example.com>, relay=kolabmailboxfilter, delay=97165,
delays=97165/0.01/0/0.36, dsn=4.3.0, status=deferred (temporary failure. Command
output: Invalid response code received from server, original code )


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

Oct 05 10:59:41 Kolab Filter [debug] [horde] Arguments: Horde_Argv_Values Object
(
    [sender] => mailman-bounces at example.com
    [recipient] => Array
        (
            [0] => user1 at example.com
        )

    [host] => kolab.example.com
    [client] => 127.0.0.1
    [user] => 
    [config] => /kolab/etc/kolab/kolabfilter.conf
)
 [on line 244 of "/kolab/lib/php/Horde/Kolab/Filter/Base.php"]
Oct 05 10:59:41 Kolab Filter [debug] [horde] Arguments: Horde_Argv_Values Object
(
    [sender] => mailman-bounces at example.com
    [recipient] => Array
        (
            [0] => user2 at example.com
        )

    [host] => kolab.example.com
    [client] => 127.0.0.1
    [user] => 
    [config] => /kolab/etc/kolab/kolabfilter.conf
)
 [on line 244 of "/kolab/lib/php/Horde/Kolab/Filter/Base.php"]
Oct 05 10:59:41 Kolab Filter [error] [horde] Invalid response code received from
server, original code ; Code: 459 [on line 266 of
"/kolab/lib/php/Horde/Kolab/Filter/Transport.php"]
Oct 05 10:59:41 Kolab Filter [error] [horde] Invalid response code received from
server, original code ; Code: 459 [on line 266 of
"/kolab/lib/php/Horde/Kolab/Filter/Transport.php"]


/kolab/var/imapd/log/lmtpd.log:

Oct 05 10:59:41 kolab <debug> lmtp[14595]: accepted connection
Oct 05 10:59:41 kolab <debug> lmtp[14595]: connection from localhost.localdomain
[127.0.0.1] preauth'd as postman
Oct 05 10:59:41 kolab <debug> lmtp[14806]: executed
Oct 05 10:59:41 kolab <debug> lmtp[14806]: accepted connection
Oct 05 10:59:41 kolab <debug> lmtp[14806]: connection from localhost.localdomain
[127.0.0.1] preauth'd as postman

----------
assignedto: wrobel
keyword: filter, release, server
messages: 21920
nosy: martin, thomas, wilde, wrobel
priority: urgent
status: unread
title: Mailman "moderator request(s) waiting" mail could not be delivered

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


From ml at radoeka.nl  Mon Oct  5 23:22:34 2009
From: ml at radoeka.nl (Richard Bos)
Date: Mon, 5 Oct 2009 23:22:34 +0200
Subject: [Kolab-devel] patches for cyrus?
In-Reply-To: <200910021840.36046.ml@radoeka.nl>
References: <200910021840.36046.ml@radoeka.nl>
Message-ID: <200910052322.34863.ml@radoeka.nl>

Op vrijdag 02 oktober 2009 18:40:35 schreef Richard Bos:
> Hi,
>
> where can I find the patches for cyrus.  I expected them here:
> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/patches/cyrus-imapd/cyrus
>-imapd-2.3.13/ but that directory is clearly empty.  I'm actually looking
> for the 2.3.14 and 2.3.15 patches.  The ones for 2.3.13 I already have.

No one?

-- 
Richard


From thomas at intevation.de  Tue Oct  6 11:01:38 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Tue, 6 Oct 2009 11:01:38 +0200
Subject: [Kolab-devel] patches for cyrus?
In-Reply-To: <200910021840.36046.ml@radoeka.nl>
References: <200910021840.36046.ml@radoeka.nl>
Message-ID: <20091006105131.063306008.thomas@intevation.de>

* Richard Bos <ml at radoeka.nl> [20091002 18:40]:
> where can I find the patches for cyrus.  I expected them here:
> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/patches/cyrus-imapd/cyrus-imapd-2.3.13/
> but that directory is clearly empty.  I'm actually looking for the 2.3.14 and 2.3.15
> patches.  The ones for 2.3.13 I already have.

The patches got moved below the imapd directory in HEAD, viewcvs
does not show this in a useful manner.

in kolab_2_2_branch the patches are still here:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/patches/cyrus-imapd/cyrus-imapd-2.3.13/?only_with_tag=kolab_2_2_branch

In HEAD you'll find the patched for 2.3.14 here:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/imapd/patches/cyrus-imapd-2.3.14/

There are no specific patches for 2.3.15 yet, but the generic
patches in
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/imapd/patches/
might still apply.

Regards,
Thomas Arendsen Hein

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


From issues at kolab.org  Tue Oct  6 12:00:44 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Tue, 06 Oct 2009 10:00:44 +0000
Subject: [Kolab-devel] [issue3899] Selecting of an event and try to print
	the day of the	event leads to crash
In-Reply-To: <1254823244.66.0.0484760552638.issue3899@kolab.org>
Message-ID: <1254823244.66.0.0484760552638.issue3899@kolab.org>


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

observed with Kontact e35 lenny 20091002.1030466-kk1
         and Kontact e35 20090907.1024959-kk8

Test:
1. Switch to the calendar.
2. Select an event.
3. RMB->Print
4. Change the radiobutton to print day or print week.
5. Press print.
=> Printer dialog appears.
6. Press print.
=> Crash.

See backtrace: print-20091006.kcrash

----------
assignedto: allen
files: print-20091006.kcrash
keyword: enterprise35, kde client
messages: 21929
nosy: allen, ludwig
priority: urgent
status: unread
title: Selecting of an event and try to print the day of the event leads to crash

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3899>
______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: print-20091006.kcrash
Type: application/octet-stream
Size: 3089 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091006/165abcbe/print-20091006.exe

From ml at radoeka.nl  Tue Oct  6 23:19:53 2009
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 6 Oct 2009 23:19:53 +0200
Subject: [Kolab-devel] patches for cyrus?
In-Reply-To: <20091006105131.063306008.thomas@intevation.de>
References: <200910021840.36046.ml@radoeka.nl>
	<20091006105131.063306008.thomas@intevation.de>
Message-ID: <200910062319.54489.ml@radoeka.nl>

Op dinsdag 06 oktober 2009 11:01:38 schreef Thomas Arendsen Hein:
> * Richard Bos <ml at radoeka.nl> [20091002 18:40]:
> > where can I find the patches for cyrus.  I expected them here:
> > http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/patches/cyrus-imapd/cyr
> >us-imapd-2.3.13/ but that directory is clearly empty.  I'm actually
> > looking for the 2.3.14 and 2.3.15 patches.  The ones for 2.3.13 I already
> > have.
>
> The patches got moved below the imapd directory in HEAD, viewcvs
> does not show this in a useful manner.
>
> in kolab_2_2_branch the patches are still here:
> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/patches/cyrus-imapd/cyrus
>-imapd-2.3.13/?only_with_tag=kolab_2_2_branch
>
> In HEAD you'll find the patched for 2.3.14 here:
> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/imapd/patches/cyrus-imapd
>-2.3.14/

Thanks Thomas.  Why is this patch 
KOLAB_cyrus-imapd-2.3.13_UID_configure_in.patch no longer provided.  
configure.in did not change between 2.3.13 and 2.3.14

Contents of the patch:
--- b/configure.in      2008-10-09 01:28:58.000000000 +0200
+++ a/configure.in      2008-11-12 08:38:08.000000000 +0100
@@ -1253,7 +1253,7 @@ for flag in ${ldflags} ${default_ldflags
 done

 IMAP_COM_ERR_LIBS="${COM_ERR_LIBS}"
-IMAP_LIBS="${LIB_SASL} ${LIBS} ${SQL_LIBS}"
+IMAP_LIBS="${LIB_SASL} -lldap -llber ${LIBS} ${SQL_LIBS}"

 AC_SUBST(LIB_RT)
 AC_SUBST(IMAP_COM_ERR_LIBS)


Now I have to admit the patch is also not present in the current patch 
location:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/imapd/patches/cyrus-
imapd-2.3.13/
So one decided that it is nolonger needed?  Is that because a special 
configure argument is used, to active the -lldap and -llber?  If I call 
configure with the --with-ldap=%{_libdir} argument, the compilation stops with 
global.c:(.text+0xc4f): undefined reference to `ldap_.............'

What would be the correct argument to give to configure, to get ldap support 
compiled?


-- 
Richard


From ml at radoeka.nl  Tue Oct  6 23:28:21 2009
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 6 Oct 2009 23:28:21 +0200
Subject: [Kolab-devel] patches for cyrus?
In-Reply-To: <200910062319.54489.ml@radoeka.nl>
References: <200910021840.36046.ml@radoeka.nl>
	<20091006105131.063306008.thomas@intevation.de>
	<200910062319.54489.ml@radoeka.nl>
Message-ID: <200910062328.21989.ml@radoeka.nl>

Op dinsdag 06 oktober 2009 23:19:53 schreef Richard Bos:
> If I call
> configure with the --with-ldap=%{_libdir} argument, the compilation stops
> with global.c:(.text+0xc4f): undefined reference to `ldap_.............'
>
> What would be the correct argument to give to configure, to get ldap
> support compiled?

Tried --with-ldap=/usr/include as well, but this didn't result in rpms either 
:(

-- 
Richard


From thomas at intevation.de  Wed Oct  7 09:22:59 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Wed, 7 Oct 2009 09:22:59 +0200
Subject: [Kolab-devel] patches for cyrus?
In-Reply-To: <200910062328.21989.ml@radoeka.nl>
References: <200910021840.36046.ml@radoeka.nl>
	<20091006105131.063306008.thomas@intevation.de>
	<200910062319.54489.ml@radoeka.nl>
	<200910062328.21989.ml@radoeka.nl>
Message-ID: <20091007092150.648269561.thomas@intevation.de>

* Richard Bos <ml at radoeka.nl> [20091006 23:28]:
> Op dinsdag 06 oktober 2009 23:19:53 schreef Richard Bos:
> > If I call
> > configure with the --with-ldap=%{_libdir} argument, the compilation stops
> > with global.c:(.text+0xc4f): undefined reference to `ldap_.............'
> >
> > What would be the correct argument to give to configure, to get ldap
> > support compiled?
> 
> Tried --with-ldap=/usr/include as well, but this didn't result in rpms either 

The OpenPKG imapd.spec file contains this:

%if "%{with_ldap}" == "yes"
    %{l_shtool} subst -e 's;\(IMAP_LIBS="${LIB_SASL}\) \(.*"\);\1 -lldap -llber \2;g' configure
%endif

So it just patches the configure file on demand.

Regards,
Thomas

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


From ml at radoeka.nl  Wed Oct  7 20:35:59 2009
From: ml at radoeka.nl (Richard Bos)
Date: Wed, 7 Oct 2009 20:35:59 +0200
Subject: [Kolab-devel] patches for cyrus?
In-Reply-To: <200910062319.54489.ml@radoeka.nl>
References: <200910021840.36046.ml@radoeka.nl>
	<20091006105131.063306008.thomas@intevation.de>
	<200910062319.54489.ml@radoeka.nl>
Message-ID: <200910072035.59996.ml@radoeka.nl>

Hello Thomas,

Op dinsdag 07 oktober 200909:22:59  schreef Thomas Arendsen Hein:
> The OpenPKG imapd.spec file contains this:
>
> %if "%{with_ldap}" == "yes"
>     %{l_shtool} subst -e 's;\(IMAP_LIBS="${LIB_SASL}\) \(.*"\);\1 -lldap -
llber \2;g' configure
> %endif
>
> So it just patches the configure file on demand.

that's helps a lot.  I get a cyrus package this way as well :)

Now when I leave the configure arguments "--with-ldap=%{_includedir}" with the 
configure command line, I get the following RPMLINT check error
(the error is on the bottom of the following output):

cyrus-imapd> cat RPMLINT_ERROR
..........
Wrote: /usr/src/packages/SRPMS/cyrus-imapd-kolab-2.3.14-7.src.rpm                                                                                    
Wrote: /usr/src/packages/RPMS/i586/cyrus-imapd-kolab-2.3.14-7.i586.rpm                                                                               
Wrote: /usr/src/packages/RPMS/i586/perl-Cyrus-IMAP-2.3.14-7.i586.rpm
Wrote: /usr/src/packages/RPMS/i586/perl-Cyrus-SIEVE-
managesieve-2.3.14-7.i586.rpm
Wrote: /usr/src/packages/RPMS/i586/cyrus-imapd-kolab-devel-2.3.14-7.i586.rpm
... checking for files with abuild user/group
... running 00-check-install-rpms
... installing all built rpms
error: failed to stat /sys/kernel/debug: No such file or directory
Preparing packages for installation...
perl-Cyrus-IMAP-2.3.14-7
perl-Cyrus-SIEVE-managesieve-2.3.14-7
cyrus-imapd-kolab-devel-2.3.14-7
cyrus-imapd-kolab-2.3.14-7
... running 01-check-debuginfo
... testing for empty debuginfo packages
... running 02-check-gcc-output
... testing for serious compiler warnings
    (using /usr/lib/build/checks-data/check_gcc_output)
    (using /var/tmp/build-root-openSUSE_11.1-i586/.build.log)

I: Program returns random data in a function
E: cyrus-imapd-kolab no-return-in-nonvoid-function afskrb.c:549


I solved it by using this patch:
--- ./cyrus-imapd-2.3.14/ptclient/afskrb.c      2008-03-24 19:34:22.000000000 
+0100
+++ ./cyrus-imapd-2.3.14.new/ptclient/afskrb.c  2009-10-07 20:00:07.000000000 
+0200
@@ -546,6 +546,7 @@
     int *dsize __attribute__((unused)))
 {
        fatal("PTS module (afskrb) not compiled in", EC_CONFIG);
+       return 0;
 }

 #endif /* HAVE_AFSKRB */


Just wondering if that is the correct way to solve that RPMLINT error (cyrus-
imapd-kolab no-return-in-nonvoid-function afskrb.c:549).

For clarity, I'm not going to use the --with-ldap argument in the configure 
line, I just came across it (the error).  It also shows that the --with-ldap 
leaves out, part of the code.  Don't know if that is desired.....


-- 
Richard


From issues at kolab.org  Thu Oct  8 11:22:11 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Thu, 08 Oct 2009 09:22:11 +0000
Subject: [Kolab-devel] [issue3900] confirm dialog will be empty,
	if a contact without email address is added from the lookup.
In-Reply-To: <1254993731.56.0.38127184432.issue3900@kolab.org>
Message-ID: <1254993731.56.0.38127184432.issue3900@kolab.org>


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

observed with Kontact e35 lenny 20090918.1030082-kk5

Test:
1. Switch to contacts
2. Configure the LDAP lookup server x500.bund.de
3. Click on lookup search.
4. Select an entry without email address.
5. Add to contacts list.
=> An empty confirm dialog pops up.
Notice: After pressing ok, the contact is in the resource.

----------
assignedto: allen
keyword: enterprise35, kde client
messages: 21945
nosy: allen, ludwig
priority: minor bug
status: unread
title: confirm dialog will be empty, if a contact without email address is added from the lookup.

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


From thomas at intevation.de  Thu Oct  8 12:37:19 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Thu, 8 Oct 2009 12:37:19 +0200
Subject: [Kolab-devel] patches for cyrus?
In-Reply-To: <200910072035.59996.ml@radoeka.nl>
References: <200910021840.36046.ml@radoeka.nl>
	<20091006105131.063306008.thomas@intevation.de>
	<200910062319.54489.ml@radoeka.nl>
	<200910072035.59996.ml@radoeka.nl>
Message-ID: <20091008123504.652514716.thomas@intevation.de>

* Richard Bos <ml at radoeka.nl> [20091007 20:36]:
> I solved it by using this patch:
> --- ./cyrus-imapd-2.3.14/ptclient/afskrb.c      2008-03-24 19:34:22.000000000 
> +0100
> +++ ./cyrus-imapd-2.3.14.new/ptclient/afskrb.c  2009-10-07 20:00:07.000000000 
> +0200
> @@ -546,6 +546,7 @@
>      int *dsize __attribute__((unused)))
>  {
>         fatal("PTS module (afskrb) not compiled in", EC_CONFIG);
> +       return 0;
>  }
> 
>  #endif /* HAVE_AFSKRB */

Please report this bug to the OpenLDAP people, unless it is already
fixed in a newer version.

And you should use 2.3.15 (or the patch from kolab_2_2_branch)
anyway to close a security issue with sieve scripts.

Regards,
Thomas

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


From ml at radoeka.nl  Thu Oct  8 17:49:31 2009
From: ml at radoeka.nl (Richard Bos)
Date: Thu, 8 Oct 2009 17:49:31 +0200
Subject: [Kolab-devel] patches for cyrus?
In-Reply-To: <20091008123504.652514716.thomas@intevation.de>
References: <200910021840.36046.ml@radoeka.nl>
	<200910072035.59996.ml@radoeka.nl>
	<20091008123504.652514716.thomas@intevation.de>
Message-ID: <200910081749.31800.ml@radoeka.nl>

Hi Thomas,

Op donderdag 08 oktober 2009 12:37:19 schreef Thomas Arendsen Hein:
> * Richard Bos <ml at radoeka.nl> [20091007 20:36]:
> > I solved it by using this patch:
> > --- ./cyrus-imapd-2.3.14/ptclient/afskrb.c      2008-03-24
> > 19:34:22.000000000 +0100
> > +++ ./cyrus-imapd-2.3.14.new/ptclient/afskrb.c  2009-10-07
> > 20:00:07.000000000 +0200
> > @@ -546,6 +546,7 @@
> >      int *dsize __attribute__((unused)))
> >  {
> >         fatal("PTS module (afskrb) not compiled in", EC_CONFIG);
> > +       return 0;
> >  }
> >
> >  #endif /* HAVE_AFSKRB */
>
> Please report this bug to the OpenLDAP people, unless it is already
> fixed in a newer version.

Do you really mean openLDAP  or do you mean cyrus?


> And you should use 2.3.15 (or the patch from kolab_2_2_branch)
> anyway to close a security issue with sieve scripts.

I'll upgrade to 2.3.15 as soon as possible.  Do you have a url to the patch 
from kolab_2_2_branch, or a pointer to the repository / directory that 
contains the patch?


-- 
Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-devel/attachments/20091008/6bddcc70/attachment.html

From thomas at intevation.de  Fri Oct  9 11:38:27 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 9 Oct 2009 11:38:27 +0200
Subject: [Kolab-devel] patches for cyrus?
In-Reply-To: <200910081749.31800.ml@radoeka.nl>
References: <200910021840.36046.ml@radoeka.nl>
	<200910072035.59996.ml@radoeka.nl>
	<20091008123504.652514716.thomas@intevation.de>
	<200910081749.31800.ml@radoeka.nl>
Message-ID: <20091009113553.136118441.thomas@intevation.de>

* Richard Bos <ml at radoeka.nl> [20091008 17:49]:
> Op donderdag 08 oktober 2009 12:37:19 schreef Thomas Arendsen Hein:
> > * Richard Bos <ml at radoeka.nl> [20091007 20:36]:
> > > I solved it by using this patch:
> > > --- ./cyrus-imapd-2.3.14/ptclient/afskrb.c      2008-03-24
> > > 19:34:22.000000000 +0100
> > > +++ ./cyrus-imapd-2.3.14.new/ptclient/afskrb.c  2009-10-07
> > > 20:00:07.000000000 +0200
> > > @@ -546,6 +546,7 @@
> > >      int *dsize __attribute__((unused)))
> > >  {
> > >         fatal("PTS module (afskrb) not compiled in", EC_CONFIG);
> > > +       return 0;
> > >  }
> > >
> > >  #endif /* HAVE_AFSKRB */
> >
> > Please report this bug to the OpenLDAP people, unless it is already
> > fixed in a newer version.
> 
> Do you really mean openLDAP  or do you mean cyrus?

Of course, my brain is just playing tricks on me due to a cold.

> > And you should use 2.3.15 (or the patch from kolab_2_2_branch)
> > anyway to close a security issue with sieve scripts.
> 
> I'll upgrade to 2.3.15 as soon as possible.  Do you have a url to the patch 
> from kolab_2_2_branch, or a pointer to the repository / directory that 
> contains the patch?

http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/imapd/Attic/CVE-2009-2632.patch?only_with_tag=kolab_2_2_branch

Regards,
Thomas

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


From ml at radoeka.nl  Fri Oct  9 22:37:06 2009
From: ml at radoeka.nl (Richard Bos)
Date: Fri, 9 Oct 2009 22:37:06 +0200
Subject: [Kolab-devel] patches for cyrus?
In-Reply-To: <20091009113553.136118441.thomas@intevation.de>
References: <200910021840.36046.ml@radoeka.nl>
	<200910081749.31800.ml@radoeka.nl>
	<20091009113553.136118441.thomas@intevation.de>
Message-ID: <200910092237.07584.ml@radoeka.nl>

Op vrijdag 09 oktober 2009 11:38:27 schreef Thomas Arendsen Hein:
> * Richard Bos <ml at radoeka.nl> [20091008 17:49]:
> > Op donderdag 08 oktober 2009 12:37:19 schreef Thomas Arendsen Hein:
> > > * Richard Bos <ml at radoeka.nl> [20091007 20:36]:
> > > > I solved it by using this patch:
> > > > --- ./cyrus-imapd-2.3.14/ptclient/afskrb.c      2008-03-24
> > > > 19:34:22.000000000 +0100
> > > > +++ ./cyrus-imapd-2.3.14.new/ptclient/afskrb.c  2009-10-07
> > > > 20:00:07.000000000 +0200
> > > > @@ -546,6 +546,7 @@
> > > >      int *dsize __attribute__((unused)))
> > > >  {
> > > >         fatal("PTS module (afskrb) not compiled in", EC_CONFIG);
> > > > +       return 0;
> > > >  }
> > > >
> > > >  #endif /* HAVE_AFSKRB */
> > >
> > > Please report this bug to the OpenLDAP people, unless it is already
> > > fixed in a newer version.
> >
> > Do you really mean openLDAP  or do you mean cyrus?
>
> Of course, my brain is just playing tricks on me due to a cold.

Don't worry, as long as it is a lively discussion mistakes like this are 
correctly quickly :)

> > > And you should use 2.3.15 (or the patch from kolab_2_2_branch)
> > > anyway to close a security issue with sieve scripts.
> >
> > I'll upgrade to 2.3.15 as soon as possible.  Do you have a url to the
> > patch from kolab_2_2_branch, or a pointer to the repository / directory
> > that contains the patch?
>
> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/imapd/Attic/CVE-2009-2632
>.patch?only_with_tag=kolab_2_2_branch

Ah!  I'm in the comfortable position of using openSUSE's native cyrus spec 
file (that contains a switch to enable kolab).  This native package is already 
equipped with the patch that you refer to above :)  Even without me knowing 
it, the security patch was already there!

-- 
Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-devel/attachments/20091009/f304f964/attachment.html

From dusty at qwer.tk  Sat Oct 10 11:07:07 2009
From: dusty at qwer.tk (Hermann Himmelbauer)
Date: Sat, 10 Oct 2009 11:07:07 +0200
Subject: [Kolab-devel] Konsec Connector - any experiences?
Message-ID: <200910101107.07745.dusty@qwer.tk>

Hi,
I'm considering buying and using the Konsec connector for my windows clients 
along with my Kolab 2.2.2 installation.

Before I do so, I'd like to know if you have any experiences with that setup - 
is that stable? Does this work with recent releases of Outlook? What are the 
drawbacks/shortcomings?

Best Regards,
Hermann Himmelbauer

-- 
hermann at qwer.tk
GPG key ID: 299893C7 (on keyservers)
FP: 0124 2584 8809 EF2A DBF9  4902 64B4 D16B 2998 93C7


From issues at kolab.org  Mon Oct 12 15:53:09 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Mon, 12 Oct 2009 13:53:09 +0000
Subject: [Kolab-devel] [issue3902] Delete a folder while syncing leads to
	crash
In-Reply-To: <1255355589.39.0.879977570327.issue3902@kolab.org>
Message-ID: <1255355589.39.0.879977570327.issue3902@kolab.org>


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

observed with Kontact e35 lenny 20091010.1033370-kk1

Test:
Req: x1 has a lot of mails
1. Create new mail folder x2
2. Copy x1 mails to x2
3. Sync and while syncing delete folder x1.
=> Crash.

Backtrace:delete-folder-while-sync-20091012.kcrash
Output before the crash:
ASSERT: "!transferInProgress( serNum )" in messageproperty.cpp (167)
*** KMail got signal 11 (Crashing)

----------
assignedto: allen
files: delete-folder-while-sync-20091012.kcrash
keyword: kde client, prokde35
messages: 21968
nosy: allen, ludwig
priority: critical
status: unread
title: Delete a folder while syncing leads to crash

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3902>
______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: delete-folder-while-sync-20091012.kcrash
Type: application/octet-stream
Size: 6019 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091012/7f2baf52/delete-folder-while-sync-20091012.exe

From bernhard at intevation.de  Tue Oct 13 12:12:14 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 13 Oct 2009 12:12:14 +0200
Subject: [Kolab-devel] Konsec Connector - any experiences?
In-Reply-To: <200910101107.07745.dusty@qwer.tk>
References: <200910101107.07745.dusty@qwer.tk>
Message-ID: <200910131212.18271.bernhard@intevation.de>

Am Samstag, 10. Oktober 2009 11:07:07 schrieb Hermann Himmelbauer:
> I'm considering buying and using the Konsec connector for my windows
> clients along with my Kolab 2.2.2 installation.
>
> Before I do so, I'd like to know if you have any experiences with that
> setup - is that stable? Does this work with recent releases of Outlook?
> What are the drawbacks/shortcomings?

Best is to ask this kind of question on the user lists. 
(What I've heard and some pasts experiences Konsec 
is stable with Kolab Server. Of course, there are pros and cons for each 
connector.)

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

From bernhard at intevation.de  Tue Oct 13 12:16:27 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 13 Oct 2009 12:16:27 +0200
Subject: [Kolab-devel] kimap (imap library) Re: annotations patch in
	c-client what is the status?
In-Reply-To: <200910011755.23690.ml@radoeka.nl>
References: <200906032321.30110.ml@radoeka.nl>
	<200909020949.53616.bernhard@intevation.de>
	<200910011755.23690.ml@radoeka.nl>
Message-ID: <200910131216.27932.bernhard@intevation.de>

Am Donnerstag, 1. Oktober 2009 17:55:23 schrieb Richard Bos:
> Op woensdag 02 september 2009 09:49:47 schreef Bernhard Reiter:

> > Sorry for the delay, we are planning to have a techbase wiki page but
> > this did not happen as fast as I was hoping for. 
>
> Any news on this? 

Not yet as far as I know.
(I think Kevin or Till might directly drop an email to kolab-devel@ once the 
initial page is there..)



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

From bernhard at intevation.de  Tue Oct 13 12:25:13 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 13 Oct 2009 12:25:13 +0200
Subject: [Kolab-devel] Pseudo Push over IMAP (discussion)
Message-ID: <200910131225.13424.bernhard@intevation.de>

Just a tiny bit for reference:
There are a few comments in the following LWN thread about the IMAP protocol
and "pseudo-push" for several mailboxfolders (aka mailboxes in the IMAP 
slang):

http://lwn.net/Articles/355757/

Links mentioned:
http://mswatch.sourceforge.net/  (the "why" section)

Mark Crispin, does not see this capability [multi-
 mailbox IDLE] as belonging in IMAP:
http://www.webservertalk.com/message1459531-1.html#post4034387

There is a Lemonade working group:
http://www.ietf.org/html.charters/lemonade-charter.html
http://tools.ietf.org/html/draft-ietf-lemonade-imap-notify-07

In 2006 and 2007 Martin also made a suggestion how to fix this problem:
 http://www.erfrakon.de/konold/draft-konold-imap-idleplus-05.txt

For Kolab-Clients this is interesting as we want to solve the problem
of pseudo-push at some time of course.
Of used IMAP server and Kolab Clients must implement one of
the proposed solutions. :)


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

From issues at kolab.org  Mon Oct 12 14:19:46 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Mon, 12 Oct 2009 12:19:46 +0000
Subject: [Kolab-devel] [issue3901] Result of printing a day seems to be
	broken
In-Reply-To: <1255349986.58.0.0716093183596.issue3901@kolab.org>
Message-ID: <1255349986.58.0.0716093183596.issue3901@kolab.org>


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

observed with Kontact e35 lenny 20091010.1033370-kk1

Test:
1. Select a day with 2 events in the calendar component.
2. File->Print.
3. Print day into a file.
The print result sems to be broken.
Look at the example file.

----------
assignedto: allen
files: print.ps
keyword: enterprise35, kde client
messages: 21961
nosy: allen, ludwig
priority: bug
status: unread
title: Result of printing a day seems to be broken

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3901>
______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: print.ps
Type: application/postscript
Size: 45930 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091012/339fba17/print-0001.ps

From issues at kolab.org  Wed Oct 14 12:15:45 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Wed, 14 Oct 2009 10:15:45 +0000
Subject: [Kolab-devel] [issue3904] LDAP search: try to import a contact
	without email	address import the contact many times.
In-Reply-To: <1255515345.98.0.107891407466.issue3904@kolab.org>
Message-ID: <1255515345.98.0.107891407466.issue3904@kolab.org>


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

Kontact e4 windows 20091002-2

If I try to import a contact without email address to the addressbook, the confirm
dialog is empty and the contact is imported many times (in my case 18 times).

Test:
1. Configure LDAP search server x500.bund.de
2. Switch to contact part
3. Select LDAP search
4. Select an entry without email address
5. Add the selected entry to the addressbook.
=> a confirm dialog pops up, which is empty.
6. Press Ok.
=> The contact is imported many times.
I expect the entry to be imported once.

----------
assignedto: allen
keyword: enterprise4, kde client
messages: 21989
nosy: allen, ludwig
priority: bug
status: unread
title: LDAP search: try to import a contact without email address import the contact many times.

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


From issues at kolab.org  Wed Oct 14 10:24:08 2009
From: issues at kolab.org (issues@kolab.org)
Date: Wed, 14 Oct 2009 08:24:08 +0000
Subject: [Kolab-devel] [issue3903] Kontact hangs when switching to calendar
	view
In-Reply-To: <1255508648.84.0.0837883463887.issue3903@kolab.org>
Message-ID: <1255508648.84.0.0837883463887.issue3903@kolab.org>


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

enterprise35 20090918-kk5

Switch to calendar view. -> Kontact uses 99% CPU. See attached log with gdb
debug output. 

Maybe associated with this problem: 
After restart of Kontact: Sync -> Mark new mail as read. -> Sync -> Mail was set
to unread automatically. (index problem?)

Difficult to reproduce. Critical issue of our customer.

----------
assignedto: allen
files: konact-kalender-loop.log
keyword: enterprise35, kde client, kkc
messages: 21986
nosy: allen, bernhard, emanuel, ludwig, till
priority: critical
status: unread
title: Kontact hangs when switching to calendar view

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3903>
______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: konact-kalender-loop.log
Type: text/x-log
Size: 45133 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091014/ca303842/konact-kalender-loop-0001.bin

From issues at kolab.org  Wed Oct 14 13:31:54 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Wed, 14 Oct 2009 11:31:54 +0000
Subject: [Kolab-devel] [issue3906] Runtime Error after configuration of a
	new account with	checking security setting.
In-Reply-To: <1255519914.08.0.43892833148.issue3906@kolab.org>
Message-ID: <1255519914.08.0.43892833148.issue3906@kolab.org>


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

observed with Kontact e4 windows 20091002-2

Test:
1. Start kontact
2. Configure a new receiving account and check the security possiblities of the
server.
3. Sync.
=> Runtime Error.

----------
assignedto: allen
keyword: enterprise4, kde client
messages: 21992
nosy: allen, ludwig
priority: critical
status: unread
title: Runtime Error after configuration of a new account with checking security setting.

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


From issues at kolab.org  Wed Oct 14 15:06:16 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Wed, 14 Oct 2009 13:06:16 +0000
Subject: [Kolab-devel] [issue3907] Navigator toolbar and different
	components.
In-Reply-To: <1255525576.9.0.302398700841.issue3907@kolab.org>
Message-ID: <1255525576.9.0.302398700841.issue3907@kolab.org>


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

observed with Kontact e4 20091002-2 of tag 20091002.1030459

Test:
1. Start kontact
2. Switch to the mail part.
3. Set Settings->toolbar->navigator toolbar.
=> navigator toolbar is shown.
4. Switch to Kaddressbook.
=> no navigator toolbar is shown.

----------
assignedto: allen
keyword: enterprise4, kde client
messages: 21997
nosy: allen, ludwig
priority: bug
status: unread
title: Navigator toolbar and different components.

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


From issues at kolab.org  Wed Oct 14 16:35:18 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Wed, 14 Oct 2009 14:35:18 +0000
Subject: [Kolab-devel] [issue3909] Kontact allows to send a mail to a
	recipient which	address ends with an dot
In-Reply-To: <1255530918.25.0.0577528713925.issue3909@kolab.org>
Message-ID: <1255530918.25.0.0577528713925.issue3909@kolab.org>


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

tested with Kontact e4 windows 20091002-2 of tag 20091002.1030459

Try to send a mail to "test at test.". Kontact allows it.
In the NewsLog stands that this is not allowed.

----------
assignedto: allen
keyword: enterprise4, kde client
messages: 22003
nosy: allen, ludwig
priority: minor bug
status: unread
title: Kontact allows to send a mail to a recipient which address ends with an dot

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


From issues at kolab.org  Thu Oct 15 11:09:49 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Thu, 15 Oct 2009 09:09:49 +0000
Subject: [Kolab-devel] [issue3911] mail enterprise header: cannot mail to
	the second to	address.
In-Reply-To: <1255597789.17.0.00497133556597.issue3911@kolab.org>
Message-ID: <1255597789.17.0.00497133556597.issue3911@kolab.org>


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

observed with Kontact e4 windows 20091002-2

Test:
1. Send a mail to to:A and cc:B
2. A selects enterprise header for viewing mails.
3. A looks at the test mail.
There is an To: field with A's and part of B's addresses.
4. Try to click on B's address. Not possible, but it is possible to select 
A's address. Inconsistent.

----------
assignedto: allen
keyword: enterprise4, kde client
messages: 22009
nosy: allen, ludwig
priority: minor bug
status: unread
title: mail enterprise header: cannot mail to the second to address.

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


From issues at kolab.org  Thu Oct 15 12:55:39 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Thu, 15 Oct 2009 10:55:39 +0000
Subject: [Kolab-devel] [issue3912] Send an invitation with categories:
	categories are	seperated by \, 
In-Reply-To: <1255604139.5.0.764636448166.issue3912@kolab.org>
Message-ID: <1255604139.5.0.764636448166.issue3912@kolab.org>


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

observed with Kontact e4 windows 20091002-2

Test:
1. Start to create a new event.
2. Add 3 categories to the event.
3. Add an attendee.
4. Press ok and send the mail.
5. Look at the details of the send mail with "V".
=>The iCal mail contains the 
CATEGOIES: A\,B\,C
line.
I expect it to be:
CATEGORIES: A,B,C

----------
assignedto: allen
keyword: enterprise4, kde client
messages: 22013
nosy: allen, ludwig
priority: minor bug
status: unread
title: Send an invitation with categories: categories are seperated by \,

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


From issues at kolab.org  Thu Oct 15 15:09:03 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Thu, 15 Oct 2009 13:09:03 +0000
Subject: [Kolab-devel] [issue3913] German attachment deleted text is broken
In-Reply-To: <1255612143.83.0.758635042348.issue3913@kolab.org>
Message-ID: <1255612143.83.0.758635042348.issue3913@kolab.org>


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

observed with kontact e4 windows 20091002-2

Test:
1. Look at a mail with attachment.
2. Delete the attachment.
3. Look at the mail again.
The German attachment deleted text is broken by the umlauts.

----------
assignedto: allen
keyword: enterprise4, kde client
messages: 22016
nosy: allen, ludwig
priority: minor bug
status: unread
title: German attachment deleted text is broken

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


From issues at kolab.org  Wed Oct 14 15:28:59 2009
From: issues at kolab.org (issues@kolab.org)
Date: Wed, 14 Oct 2009 13:28:59 +0000
Subject: [Kolab-devel] [issue3908] Mail view and print layout problem if
	description of	attachment is to long (#5872)
In-Reply-To: <1255526939.1.0.781355488637.issue3908@kolab.org>
Message-ID: <1255526939.1.0.781355488637.issue3908@kolab.org>


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

enterprise35 20091010.1034811:

- Create a new mail.
- add an attachment
- right mouse click of attachment -> properties: add long description text
- send mail.
- receive mail
- view mail with mail header view "dekorativ" (german)
=> long attachment description breaks mail header view (see attached testmail) 

- print mail in preview
=> preview doesn't show the mail (see testmail1) or show the mail in very small
font only (see testmail2)

=> Long describtions don't have to break out; automatical linebreaks required.

----------
assignedto: allen
files: testmail1.mbox
keyword: enterprise35, kde client, kkc
messages: 22000
nosy: allen, bernhard, emanuel, ludwig
priority: urgent
status: unread
title: Mail view and print layout problem if description of attachment is to long (#5872)

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3908>
______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: testmail1.mbox
Type: application/octet-stream
Size: 2544 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091014/d9e4ec34/testmail1.exe

From issues at kolab.org  Wed Oct 14 17:22:42 2009
From: issues at kolab.org (issues@kolab.org)
Date: Wed, 14 Oct 2009 15:22:42 +0000
Subject: [Kolab-devel] [issue3910] German translation missing: select input
	method
In-Reply-To: <1255533762.11.0.104655100251.issue3910@kolab.org>
Message-ID: <1255533762.11.0.104655100251.issue3910@kolab.org>


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

There are 3 menu items which are not translated into German (see screenshot).
Please translate.
Thanks.

----------
assignedto: tmcguire
files: select-input-method.png
keyword: enterprise35, kde client, kkc
messages: 22006
nosy: allen, emanuel, tmcguire
priority: bug
status: unread
title: German translation missing: select input method

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3910>
______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: select-input-method.png
Type: image/png
Size: 71490 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091014/4554a766/select-input-method-0001.png

From issues at kolab.org  Fri Oct 16 10:42:58 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Fri, 16 Oct 2009 08:42:58 +0000
Subject: [Kolab-devel] [issue3914] Crash after looking at a forwarded mail
In-Reply-To: <1255682578.68.0.262429393824.issue3914@kolab.org>
Message-ID: <1255682578.68.0.262429393824.issue3914@kolab.org>


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

observed with Kontact e4 windows 20091002-2

A user received a mail containing:
X-Content-Disposition: inline;
	filename*=
This leads to a crash/RuntimeError of Kontact
See testmail 1074.

----------
assignedto: allen
files: 1074.
keyword: enterprise4, kde client
messages: 22023
nosy: allen, ludwig
priority: urgent
status: unread
title: Crash after looking at a forwarded mail

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3914>
______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1074.
Type: application/octet-stream
Size: 3430 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091016/da5fcfa3/1074.exe

From issues at kolab.org  Fri Oct 16 11:15:20 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Fri, 16 Oct 2009 09:15:20 +0000
Subject: [Kolab-devel] [issue3916] Dayview doesn't display events
In-Reply-To: <1255684520.92.0.34498924789.issue3916@kolab.org>
Message-ID: <1255684520.92.0.34498924789.issue3916@kolab.org>


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

observed with Kontact e4 windows 20091002-2 of tag 20091002.1030459

Test:
1. Select a week in the calender.
2. Create a new event in this week.
=> The event is shown in the week.
3. Select the day of the event.
=> The event is *not* displayed at this day.
I expect the event to be displayed. This is critical, because a main calendar
function is not working.

----------
assignedto: allen
keyword: enterprise4, kde client
messages: 22025
nosy: allen, ludwig
priority: critical
status: unread
title: Dayview doesn't display events

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


From issues at kolab.org  Fri Oct 16 12:23:08 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Fri, 16 Oct 2009 10:23:08 +0000
Subject: [Kolab-devel] [issue3918] Recreation of a mail index changes the
	last mail to	unread.
In-Reply-To: <1255688588.8.0.514525913983.issue3918@kolab.org>
Message-ID: <1255688588.8.0.514525913983.issue3918@kolab.org>


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

observed with Kontact e4 windows 20091002-2

Test:
In the inbox of the account are just 10 read mails.
1. Start Kontact/ Switch to mail part.
2. Sync.
3. RMB->IMAP troubleshooting->Recreate index of current folder.
=> The last mail changes to unread.
I expect that all mails stay read.

----------
assignedto: allen
keyword: enterprise4, kde client
messages: 22028
nosy: allen, ludwig
priority: bug
status: unread
title: Recreation of a mail index changes the last mail to unread.

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


From ml at radoeka.nl  Fri Oct 16 13:17:50 2009
From: ml at radoeka.nl (Richard Bos)
Date: Fri, 16 Oct 2009 13:17:50 +0200
Subject: [Kolab-devel] How to get my korganizer on MS windows alive again
Message-ID: <200910161317.50832.ml@radoeka.nl>

Hi,

I have a korganizer on MS windows that does not want to get started anymore, 
after I configured a remote calendar.  I made a kde bug report for it:
https://bugs.kde.org/show_bug.cgi?id=210656

Anybody on this ML who can help, to get my korganizer on MS windows alive 
again?

(I'm aware that this email would be more appropriate for the kolab-users list, 
but as it is a kde problem on MS windows I believe that this list is better).

-- 
Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-devel/attachments/20091016/7ed4ca0e/attachment.html

From issues at kolab.org  Fri Oct 16 15:01:23 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Fri, 16 Oct 2009 13:01:23 +0000
Subject: [Kolab-devel] [issue3919] After recreation of the mail cache,
	deleted tasks reappear.
In-Reply-To: <1255698083.18.0.799072668337.issue3919@kolab.org>
Message-ID: <1255698083.18.0.799072668337.issue3919@kolab.org>


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

observed with Kontact e4 windows 20091002-2

Test:
1. Start Kontact /Switch to todos
2. Create three tasks.
3. Sync.
4. Delete the three test tasks.
=> todos list is empty.
5. Sync.
6. Switch to mail part
7. IMAP troubleshooting-> Recreate cache.
8. Switch back to the tasks.
=> Some tasks reappears.

----------
assignedto: allen
keyword: enterprise4, kde client
messages: 22030
nosy: allen, ludwig
priority: urgent
status: unread
title: After recreation of the mail cache, deleted tasks reappear.

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


From issues at kolab.org  Fri Oct 16 15:30:16 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Fri, 16 Oct 2009 13:30:16 +0000
Subject: [Kolab-devel] [issue3920] After vertical zoom daytime scale and
	calendar scale	don't fit anymore.
In-Reply-To: <1255699816.87.0.117187983684.issue3920@kolab.org>
Message-ID: <1255699816.87.0.117187983684.issue3920@kolab.org>


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

observed with Kontact e4 windows 20091002-2

Test:
1. Switch to calendar.
2. View->Zoom-> increase vertically 
=> the day time scale and the calendar scale don't fit anymore.

----------
assignedto: allen
keyword: enterprise4, kde client
messages: 22034
nosy: allen, ludwig
priority: minor bug
status: unread
title: After vertical zoom daytime scale and calendar scale don't fit anymore.

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


From issues at kolab.org  Fri Oct 16 11:07:27 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Fri, 16 Oct 2009 09:07:27 +0000
Subject: [Kolab-devel] [issue3915] Sometimes events are not displayed in the
	monthview
In-Reply-To: <1255684047.76.0.487228611864.issue3915@kolab.org>
Message-ID: <1255684047.76.0.487228611864.issue3915@kolab.org>


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

observed with Kontact e4 windows 20091002-2

Test:
1. Create some events at the 16th of OCT.
2. Switch to monthview.
=> The events are not displayed.
3. Press on next week.
=> The events are now displayed.

The attachments shows the same Kontact, just a few clicks away.

----------
assignedto: allen
files: monthview-20091016.zip
keyword: enterprise4, kde client
messages: 22024
nosy: allen, ludwig
priority: urgent
status: unread
title: Sometimes events are not displayed in the monthview

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3915>
______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: monthview-20091016.zip
Type: application/zip
Size: 95627 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091016/ccaf2c4b/monthview-20091016-0001.zip

From issues at kolab.org  Fri Oct 16 11:27:28 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Fri, 16 Oct 2009 09:27:28 +0000
Subject: [Kolab-devel] [issue3917] Sometimes favorite folder and inbox
	display different	uncrad mails count.
In-Reply-To: <1255685248.5.0.650487625293.issue3917@kolab.org>
Message-ID: <1255685248.5.0.650487625293.issue3917@kolab.org>


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

observed with Kontact enterprise4 windows 20091002-2

Sometimes after some testing I observe that the favorite folders and the inbox
of a server has different unread mail count.

----------
assignedto: allen
files: unread-count-20091016.png
keyword: enterprise4, kde client
messages: 22027
nosy: allen, ludwig
priority: urgent
status: unread
title: Sometimes favorite folder and inbox display different uncrad mails count.

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3917>
______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: unread-count-20091016.png
Type: image/png
Size: 69784 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091016/4d24ad98/unread-count-20091016-0001.png

From bernhard at intevation.de  Mon Oct 19 14:54:13 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 19 Oct 2009 14:54:13 +0200
Subject: [Kolab-devel] How to get my korganizer on MS windows alive again
In-Reply-To: <200910161317.50832.ml@radoeka.nl>
References: <200910161317.50832.ml@radoeka.nl>
Message-ID: <200910191454.14156.bernhard@intevation.de>

Am Freitag, 16. Oktober 2009 13:17:50 schrieb Richard Bos:
> I have a korganizer on MS windows that does not want to get started
> anymore, after I configured a remote calendar. ?I made a kde bug report for
> it: https://bugs.kde.org/show_bug.cgi?id=210656
>
> Anybody on this ML who can help, to get my korganizer on MS windows alive
> again?

I've commented in the kde issue.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091019/ef63bff5/attachment.bin

From issues at kolab.org  Tue Oct 20 11:02:18 2009
From: issues at kolab.org (Bernhard Reiter)
Date: Tue, 20 Oct 2009 09:02:18 +0000
Subject: [Kolab-devel] [issue3921] Crash when canceling decryption of an
	non-mime deprecated	OpenPGP email,
	if different email is selected inbetween
In-Reply-To: <1256029338.99.0.356072326819.issue3921@kolab.org>
Message-ID: <1256029338.99.0.356072326819.issue3921@kolab.org>


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

I can reproduce a crash in a special condition:
If the questions for GPG-retry comes up and I select a different email
before canceling it, I get a crash.
(The priority would be minor, but the crash makes it "normal".)

Reproduced on Etch with
a)
Architecture: i386
Source: kdepim
Version: 4:3.5.10.enterprise.0.20091010.1033370-kk1

b) Version: 4:3.5.10.enterprise.0.20090918.1030082-kk5

I am attaching a typical crash from a).
Once I've got a crash from a) like:
[KCrash handler]
#5  DwString::data (this=0x37) at ../mimelib/mimelib/string.h:625
#6  0xf49b3069 in DwHeaders::FindField (this=0x88a9b50,
    aFieldName=0x8eb99b8 "Message-Id") at headers.cpp:289
#7  0xf4c6e081 in KMMessage::headerField (this=0x99b46c0, aName=@0xff8d5840)
    at kmmessage.cpp:2290
#8  0xf4c6ee3f in KMMessage::msgId (this=0x99b46c0) at kmmessage.cpp:2180
#9  0xf4d59bd6 in KMReaderWin::parseMsg (this=0x82b2788, aMsg=0x99b46c0)
    at kmreaderwin.cpp:1623
#10 0xf4d528f4 in KMReaderWin::displayMessage (this=0x82b2788)
    at kmreaderwin.cpp:1452
#11 0xf4d52ad6 in KMReaderWin::updateReaderWin (this=0x82b2788)
    at kmreaderwin.cpp:1387
#12 0xf4d5587d in KMReaderWin::qt_invoke (this=0x82b2788, _id=48,
    _o=0xff8d5d8c) at kmreaderwin.moc:308

----------
assignedto: marc
files: kontact-e35-crash-20091020-3.txt
keyword: enterprise35, kde client
messages: 22039
nosy: allen, bernhard, ludwig, marc, till
priority: bug
status: unread
title: Crash when canceling decryption of an non-mime deprecated OpenPGP email, if different email is selected inbetween

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3921>
______________________________________
-------------- next part --------------
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -169269568 (LWP 3628)]
[New Thread -219022416 (LWP 3632)]
[New Thread -210633808 (LWP 3631)]
[New Thread -202245200 (LWP 3630)]
[New Thread -193856592 (LWP 3629)]
[KCrash handler]
#5  0xf4d29b11 in KMReaderWin::parseMsg (this=0x8b4aa90, aMsg=0x8fb3b80)
    at kmreaderwin.cpp:1539
#6  0xf4d228f4 in KMReaderWin::displayMessage (this=0x8b4aa90)
    at kmreaderwin.cpp:1452
#7  0xf4d22ad6 in KMReaderWin::updateReaderWin (this=0x8b4aa90)
    at kmreaderwin.cpp:1387
#8  0xf4d2587d in KMReaderWin::qt_invoke (this=0x8b4aa90, _id=48, 
    _o=0xffb35ecc) at kmreaderwin.moc:308
#9  0xf6facd4f in QObject::activate_signal (this=0x8b4ab48, clist=0x8b6e948, 
    o=0xffb35ecc) at kernel/qobject.cpp:2356
#10 0xf6fad7e0 in QObject::activate_signal (this=0x8b4ab48, signal=2)
    at kernel/qobject.cpp:2325
#11 0xf7337c86 in QTimer::timeout (this=0x8b4ab48)
    at .moc/debug-shared-mt/moc_qtimer.cpp:82
#12 0xf6fd4603 in QTimer::event (this=0x8b4ab48, e=0xffb36218)
    at kernel/qtimer.cpp:219
#13 0xf6f44c26 in QApplication::internalNotify (this=0xffb364ac, 
    receiver=0x8b4ab48, e=0xffb36218) at kernel/qapplication.cpp:2635
#14 0xf6f46a43 in QApplication::notify (this=0xffb364ac, receiver=0x8b4ab48, 
    e=0xffb36218) at kernel/qapplication.cpp:2358
#15 0xf766ce0e in KApplication::notify (this=0xffb364ac, receiver=0x8b4ab48, 
    event=0xffb36218)
    at /chroots/etch-chroot/home/white/kdelibs/new/kdelibs-3.5.5a.dfsg.1/./kdecore/kapplication.cpp:550
#16 0xf6ed8421 in QApplication::sendEvent (receiver=0x8b4ab48, 
    event=0xffb36218) at ../include/qapplication.h:520
#17 0xf6f37623 in QEventLoop::activateTimers (this=0x80b16f8)
    at kernel/qeventloop_unix.cpp:556
#18 0xf6eec76f in QEventLoop::processEvents (this=0x80b16f8, flags=4)
    at kernel/qeventloop_x11.cpp:389
#19 0xf6f5f179 in QEventLoop::enterLoop (this=0x80b16f8)
    at kernel/qeventloop.cpp:198
#20 0xf6f5ef9a in QEventLoop::exec (this=0x80b16f8)
    at kernel/qeventloop.cpp:145
#21 0xf6f467bf in QApplication::exec (this=0xffb364ac)
    at kernel/qapplication.cpp:2758
#22 0x0805e324 in main (argc=0, argv=0x48) at main.cpp:191
#23 0xf7702ea8 in __libc_start_main () from /lib/tls/libc.so.6
#24 0x0805dc41 in _start () at ../sysdeps/i386/elf/start.S:119

From issues at kolab.org  Tue Oct 20 11:28:58 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Tue, 20 Oct 2009 09:28:58 +0000
Subject: [Kolab-devel] [issue3922] Decline an updated declined event throws
	error message
In-Reply-To: <1256030938.76.0.463744524886.issue3922@kolab.org>
Message-ID: <1256030938.76.0.463744524886.issue3922@kolab.org>


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

observed with Kontact e35 20091010.1035632-kk5

Test:
1. A sends an invitation to B.
2. B syncs and declines.
3. A syncs and enters B's update mail into his calendar.
4. A resizes the event.
5. B syncs.
=> B gets an invitation to this event again with the request to react.
6. B declines again.
=> He gets an error msg that the event was not in the calendar.
B should not get an error msg in this case.

----------
assignedto: allen
keyword: enterprise35, kde client
messages: 22041
nosy: allen, ludwig
priority: bug
status: unread
title: Decline an updated declined event throws error message

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


From issues at kolab.org  Tue Oct 20 11:40:25 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Tue, 20 Oct 2009 09:40:25 +0000
Subject: [Kolab-devel] [issue3923] Save as of an attachment of an invitation
	doesn't work
In-Reply-To: <1256031625.45.0.126701509783.issue3923@kolab.org>
Message-ID: <1256031625.45.0.126701509783.issue3923@kolab.org>


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

observed with Kontact e35 20091010.1035632-kk5

Test:
1. A sends B an invitation with text attachment.
2. B syncs.
3. B tries to save the attachment with RMB->Save Link as...
=> a file dialog without preselected filename appears.
4. Enter a name and press save.
=> No file is saved.

----------
assignedto: allen
keyword: enterprise35, kde client
messages: 22043
nosy: allen, ludwig
priority: bug
status: unread
title: Save as of an attachment of an invitation doesn't work

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


From thomas at intevation.de  Tue Oct 20 17:34:01 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Tue, 20 Oct 2009 17:34:01 +0200
Subject: [Kolab-devel] List of issues for Kolab Server 2.2.3
Message-ID: <20091020172924.577027525.thomas@intevation.de>

Hi!

Here is a preliminary list of issues we want to address in Kolab
Server 2.2.3, we aim to make the release in December:

Thomas:
  switch imapd databases back from berkeley to skiplist
    (skiplist has proven to cause less performance and stability issues)
  kolab/issue3513 (Clamav - new upstream version 0.95.2)
  kolab/issue3838 (no logging for pop3)
  kolab/issue3751 (Empty page in Firefox instead of login screen)
    (caused by a broken event or contact)
  kolab/issue3138 (problems with server upgrade from sarge to etch)
    (we have done this a couple of times from sarge or etch to lenny now)
  kolab/issue1340 (RFC: restrict users to sending mail only to internal recipients)
    (new feature, but requested by customers)
  kolab/issue1448 (Users might add an account on the nonHome Server and write emails in there.)
  kolab/issue3895 (Openldap: loglevel should be set to none in slapd.conf)
    (small change, big benefit)
  improve build process:
  - Makefile target for 2.2.2 -> 2.2.3
  - SHA1 checksums for things downloaded during build process

Gunnar:
  kolab/issue3610 (Mail to unknown at something.example.com gets accepted and yields kolabmailboxfilter exit 38)
  kolab/issue3856 (IMP/DIMP folder navigator does not allow creating/deleting/... mail folders)
  kolab/issue919  (kolab server has problems with some characters in passwords)
    (people wanting to use more secure passwords should not be punished)
  kolab/issue3890 (kolabHomeServer not selected for freebusy due to logic error in Kolab Patch)
    (patch available)
  SyncML issues

maybe:
  kolab/issue3499 (creating/modifying users with special characters in name confuses web admin)
  kolab/issue3654 (Special character issue in Kolab web interface (e.g. vacation message))
  kolab/issue2991 (The Kolab web client is always in the privileged networks)
  kolab/issue2919 (domain maintainer can't edit quota of his users)
  kolab/issue3445 (web client does not work with Konqueror)
  kolab/issue3567 (Migrate Horde prefs 2.2.0 -> 2.2.1, 2.2.2)
    (requested by many people, though not customers)
  kolab/issue3846 (fix recurring events that are counted per week and not per incident)
    (patch available)
  kolab/issue973 (Rewritten from shown inconveniently in kontact)
  kolab/issue3768 (Kolab server 2.2.2 resmgr doesn't copy attendee status (rt#5801))

And as usual, many of the issues which were fixed recently need testing,
e.g.:
  kolab/issue2982 (OpenLDAP segmentation fault on 64bit)
  kolab/issue3555 (unable to save filter settings more than once)
  kolab/issue3868 (Resmgr eats up all memory and dies on some recuring events)

Link for all server and web client issues on testing:
https://issues.kolab.org/issue?:columns=title,id,keyword&:group=priority&:filter=keyword,status&status=6&keyword=1,19

Regards,
Thomas Arendsen Hein

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

From math.parent at gmail.com  Tue Oct 20 18:14:15 2009
From: math.parent at gmail.com (Mathieu Parent)
Date: Tue, 20 Oct 2009 18:14:15 +0200
Subject: [Kolab-devel] List of issues for Kolab Server 2.2.3
In-Reply-To: <20091020172924.577027525.thomas@intevation.de>
References: <20091020172924.577027525.thomas@intevation.de>
Message-ID: <960738410910200914p20c9ed10v73319a41a1977c26@mail.gmail.com>

Hi,

On Tue, Oct 20, 2009 at 5:34 PM, Thomas Arendsen Hein
<thomas at intevation.de> wrote:
> Hi!
>
> Here is a preliminary list of issues we want to address in Kolab
> Server 2.2.3, we aim to make the release in December:
> ...

Will this release comes from the kolab_2_2_branch? (probably...)
Current roadmap says "It is planned to have further improvements in a
release 2.3.0 in the second half of 2009. ", when will be the 2.3.0
pre-release ?

Also as the team is probably too small to manage feature-based
releases, wouldn't it be preferable to do time-based releases ?
I am currently preparing a testsuite for the whole kolab server
([testsuite]) that will ease the development process (I hope).
The script currently does the following :
- bootstrap a Debian chroot (it is possible to bootstrap other
systems, see [xen-create-image]) for one master and several slaves
- launch those virtual machines with VirtualBox or xen (kvm or others
can be added)
- create an ssh key to easily controll the vms
To be done :
- install Kolab server using native Kolab packages or openPKG
- run phpunit tests (Kolab_* packages)
- run other tests : suggestions and patches welcomed!

Regards

Mathieu Parent

[testsuite]: http://svn.debian.org/wsvn/pkg-kolab/pkg-kolab_testsuite/testsuite
[xen-create-image]:
http://manpages.debian.net/cgi-bin/man.cgi?query=xen-create-image
INSTALLATION METHODS


From wilde at intevation.de  Tue Oct 20 18:33:34 2009
From: wilde at intevation.de (Sascha Wilde)
Date: Tue, 20 Oct 2009 18:33:34 +0200
Subject: [Kolab-devel] New features in the Kolab Server 2.2 branch
Message-ID: <s7w3a5eja8x.fsf@intevation.de>

Hi *,

I recently merged all improvements from the suc-branch (which was created
for work we did for an paying customer) to the regular 2.2 branch.

This includes some minor improvements to the Web Client (mainly ui
stuff) but also two new features:

- It is now possible to allow anonymous (read unauthorized) ICS export of
  selected calendars.
and even more fancy:
- One can include event summaries generated on the fly from one or more
  calendars in arbitrary web pages.

Both features work by creating a so called "proxy user" which can be
given read/list ACLs for calendar folders.  These calendars are then
world-wide anonymous accessible via ICS export or web-calendar.

Short Howtos for both new features can be found here:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/doc/raw-howtos/web-calendar.txt?rev=HEAD
and here
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/doc/raw-howtos/anonymous-ics-export.txt?rev=HEAD

Next step is to bring the changes to HEAD, Gunnar is already working on
this.

cheers
sascha
-- 
Sascha Wilde                                          OpenPGP key: 4BB86568
http://www.intevation.de/~wilde/                  http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabr?ck; AG Osnabr?ck, HR B 18998
Gesch?ftsf?hrer:   Frank Koormann,  Bernhard Reiter,  Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091020/7bede8c6/attachment.bin

From dusty at qwer.tk  Wed Oct 21 09:04:40 2009
From: dusty at qwer.tk (Hermann Himmelbauer)
Date: Wed, 21 Oct 2009 09:04:40 +0200
Subject: [Kolab-devel] List of issues for Kolab Server 2.2.3
In-Reply-To: <20091020172924.577027525.thomas@intevation.de>
References: <20091020172924.577027525.thomas@intevation.de>
Message-ID: <200910210904.40593.dusty@qwer.tk>

Am Dienstag 20 Oktober 2009 17:34:01 schrieb Thomas Arendsen Hein:
> Hi!
>
> Here is a preliminary list of issues we want to address in Kolab
> Server 2.2.3, we aim to make the release in December:

I wonder if you will upgrade the Horde webclient to the lastest version? The 
reason for this is that I'm hoping that the mobile synchronization may work 
better with the latest Horde release.

Best Regards,
Hermann

-- 
hermann at qwer.tk
GPG key ID: 299893C7 (on keyservers)
FP: 0124 2584 8809 EF2A DBF9  4902 64B4 D16B 2998 93C7


From bernhard at intevation.de  Wed Oct 21 10:13:32 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 21 Oct 2009 10:13:32 +0200
Subject: [Kolab-devel] List of issues for Kolab Server 2.2.3
In-Reply-To: <960738410910200914p20c9ed10v73319a41a1977c26@mail.gmail.com>
References: <20091020172924.577027525.thomas@intevation.de>
	<960738410910200914p20c9ed10v73319a41a1977c26@mail.gmail.com>
Message-ID: <200910211013.33318.bernhard@intevation.de>

Mathieu,

Am Dienstag, 20. Oktober 2009 18:14:15 schrieb Mathieu Parent:
> > Here is a preliminary list of issues we want to address in Kolab
> > Server 2.2.3, we aim to make the release in December:
> > ...
>
> Will this release comes from the kolab_2_2_branch? (probably...)

yes. 

> Current roadmap says "It is planned to have further improvements in a
> release 2.3.0 in the second half of 2009. ", when will be the 2.3.0
> pre-release ?

We might need to adjust the roadmap - I am not sure yet.
As always: What we are able to do depends on how much time, 
funding and help we have? 

> Also as the team is probably too small to manage feature-based
> releases, wouldn't it be preferable to do time-based releases ?

A good question. I haven't made up my mind about it.
To me the 2.2.3 is already time-based. We aim for a release before the end 
of the year and we try to plan the included features according to it.
So we might have less changes included, if the time runs out.

> I am currently preparing a testsuite for the whole kolab server
> ([testsuite]) that will ease the development process (I hope).

Most automatic tests promise help. Of course their maintenance and stepup must 
be less work intensive than doing the tests manually. :) 
(Seriously I have seen quite a few attempts at automatic testing that did not 
meet that criteria, we even have some partly finished things for Kolab 
Server.)

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

From bernhard at intevation.de  Wed Oct 21 10:15:58 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 21 Oct 2009 10:15:58 +0200
Subject: [Kolab-devel] List of issues for Kolab Server 2.2.3
In-Reply-To: <200910210904.40593.dusty@qwer.tk>
References: <20091020172924.577027525.thomas@intevation.de>
	<200910210904.40593.dusty@qwer.tk>
Message-ID: <200910211015.58793.bernhard@intevation.de>

Am Mittwoch, 21. Oktober 2009 09:04:40 schrieb Hermann Himmelbauer:
> > Here is a preliminary list of issues we want to address in Kolab
> > Server 2.2.3, we aim to make the release in December:
>
> I wonder if you will upgrade the Horde webclient to the lastest version?
> The reason for this is that I'm hoping that the mobile synchronization may
> work better with the latest Horde release.

That is a question for Gunnar. :)
We are looking into it. But what makes answering the question harder than 
usual is: What is the latest version of Horde? 3.x or 4, the one in Kolab 
Server or in UGS? 
The answer varies depending on the code parts you are looking at.
So it is not as easy as it could be, but we are working on it.
Our mid term goal is to have all our changes upstream and then use
a stable release or branch of upstream. This currently means Hord 3.x.

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

From issues at kolab.org  Wed Oct 21 11:27:13 2009
From: issues at kolab.org (Bernhard Reiter)
Date: Wed, 21 Oct 2009 09:27:13 +0000
Subject: [Kolab-devel] [issue3924] Side-by-side calender view: Unwanted
	extra scrollbar, even if there is enough space.
In-Reply-To: <1256117233.95.0.358584575658.issue3924@kolab.org>
Message-ID: <1256117233.95.0.358584575658.issue3924@kolab.org>


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

Even if there is enough space in the side-by-side view,
there is a scrollbar left. This is an artifact we should fix
(fast) as part of prokde35.

The effect can also be seen in the English language, but it is much more
troublesome in the German language. See the attached screenshot.

----------
assignedto: allen
files: kontact-e35-20091021-1.png
keyword: kde client, prokde35
messages: 22054
nosy: allen, bernhard, ludwig, till
priority: urgent
status: unread
title: Side-by-side calender view: Unwanted extra scrollbar, even if there is enough space.

______________________________________
Kolab issue tracker <issues at kolab.org>
<https://issues.kolab.org/issue3924>
______________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kontact-e35-20091021-1.png
Type: image/png
Size: 31242 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091021/1ded3887/kontact-e35-20091021-1-0001.png

From issues at kolab.org  Wed Oct 21 11:34:09 2009
From: issues at kolab.org (Bernhard Reiter)
Date: Wed, 21 Oct 2009 09:34:09 +0000
Subject: [Kolab-devel] [issue3925] Side-by-side calender view: Fit into
	available space	dynamically (rt5876)
In-Reply-To: <1256117649.03.0.701987636515.issue3925@kolab.org>
Message-ID: <1256117649.03.0.701987636515.issue3925@kolab.org>


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

To make the side by side view more usable it is
desireable to have a function that fits in the side-by-side calendar
view into the available space (horizontally).

Estimation of this feature is kkc.

Related to this wish is a defect even with the current behaviour, which should
be fixed in anyway: kolab/issue3924 (Side-by-side calender view: Unwanted extra 
scrollbar, even if there is enough space.)

As I consider it useful to sometimes get a scrollbar in the side-by-side view
I believe that we must make it configurable when this is the case.
My first idea is to add a minimum horizontal width. If we get blow the limit
the size is not made smaller and then the scrollbar appears.
Let me know if you have a better idea.

----------
assignedto: allen
keyword: enterprise35, kde client, kkc
messages: 22055
nosy: allen, bernhard, ludwig, till
priority: bug
status: unread
title: Side-by-side calender view: Fit into available space dynamically (rt5876)

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


From wrobel at pardus.de  Wed Oct 21 12:50:24 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 21 Oct 2009 12:50:24 +0200
Subject: [Kolab-devel] List of issues for Kolab Server 2.2.3
In-Reply-To: <200910210904.40593.dusty@qwer.tk>
References: <20091020172924.577027525.thomas@intevation.de>
	<200910210904.40593.dusty@qwer.tk>
Message-ID: <20091021125024.20424426vz1a6740@webmail.pardus.de>

Hi Hermann,

Quoting Hermann Himmelbauer <dusty at qwer.tk>:

> Am Dienstag 20 Oktober 2009 17:34:01 schrieb Thomas Arendsen Hein:
>> Hi!
>>
>> Here is a preliminary list of issues we want to address in Kolab
>> Server 2.2.3, we aim to make the release in December:
>
> I wonder if you will upgrade the Horde webclient to the lastest version?

No, this will happen with 2.3. I'm moving away from the monolithic  
package in 2.3 again so these type of updates in specific areas will  
be much easier (large parts have already been done in Kolab CVS HEAD).  
As this requires larger changes to the Kolab server we chose not to  
have this package split in 2.2.3.

Cheers,

Gunnar

> The reason for this is that I'm hoping that the mobile  
> synchronization may work better with the latest Horde release.
>
> Best Regards,
> Hermann
>
> --
> hermann at qwer.tk
> GPG key ID: 299893C7 (on keyservers)
> FP: 0124 2584 8809 EF2A DBF9  4902 64B4 D16B 2998 93C7
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



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

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091021/1dad653c/attachment.bin

From wrobel at pardus.de  Wed Oct 21 13:57:21 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 21 Oct 2009 13:57:21 +0200
Subject: [Kolab-devel] List of issues for Kolab Server 2.2.3
In-Reply-To: <960738410910200914p20c9ed10v73319a41a1977c26@mail.gmail.com>
References: <20091020172924.577027525.thomas@intevation.de>
	<960738410910200914p20c9ed10v73319a41a1977c26@mail.gmail.com>
Message-ID: <20091021135721.21444xbhapf2zcao@webmail.pardus.de>

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

> Hi,
>
> On Tue, Oct 20, 2009 at 5:34 PM, Thomas Arendsen Hein
> <thomas at intevation.de> wrote:
>> Hi!
>>
>> Here is a preliminary list of issues we want to address in Kolab
>> Server 2.2.3, we aim to make the release in December:
>> ...
>
> Will this release comes from the kolab_2_2_branch? (probably...)
> Current roadmap says "It is planned to have further improvements in a
> release 2.3.0 in the second half of 2009. ", when will be the 2.3.0
> pre-release ?
>
> Also as the team is probably too small to manage feature-based
> releases, wouldn't it be preferable to do time-based releases ?
> I am currently preparing a testsuite for the whole kolab server
> ([testsuite]) that will ease the development process (I hope).
> The script currently does the following :
> - bootstrap a Debian chroot (it is possible to bootstrap other
> systems, see [xen-create-image]) for one master and several slaves
> - launch those virtual machines with VirtualBox or xen (kvm or others
> can be added)
> - create an ssh key to easily controll the vms
> To be done :
> - install Kolab server using native Kolab packages or openPKG
> - run phpunit tests (Kolab_* packages)

The amount of these is going to increase (especially for the Horde 4  
versions of packages). At the same time the nature of these tests will  
slightly change. I had a tendency to write integration level  
(multi-component checks with many assertions) tests in the past. I'll  
keep it more to unit testing (one test - one assertion, for small  
chunks of code) in the future.

> - run other tests : suggestions and patches welcomed!

Nevertheless I also find it attractive to be able to run at least some  
integration level tests over the PHP code. And in principle it should  
not be hard to extend such tests to real world testing the Kolab  
server. On the other hand Bernhard is right: Tests for complex  
situations can be complex to maintain as they often need to be adapted  
with the code. So there is probably a limit there in terms of man  
power available.

If you have suggestions concerning the unit tests suites in the  
Kolab_* packages I'll definitely listen :)

Cheers,

Gunnar



>
> Regards
>
> Mathieu Parent
>
> [testsuite]:  
> http://svn.debian.org/wsvn/pkg-kolab/pkg-kolab_testsuite/testsuite
> [xen-create-image]:
> http://manpages.debian.net/cgi-bin/man.cgi?query=xen-create-image
> INSTALLATION METHODS
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



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

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091021/6df14f0c/attachment.bin

From kevin at kdab.net  Thu Oct 22 09:35:55 2009
From: kevin at kdab.net (Kevin Ottens)
Date: Thu, 22 Oct 2009 09:35:55 +0200
Subject: [Kolab-devel] kimap (imap library) Re: annotations patch in
	c-client what is the status?
In-Reply-To: <200910131216.27932.bernhard@intevation.de>
References: <200906032321.30110.ml@radoeka.nl>
	<200910011755.23690.ml@radoeka.nl>
	<200910131216.27932.bernhard@intevation.de>
Message-ID: <200910220936.04011.kevin@kdab.net>

On Tuesday 13 October 2009 12:16:27 Bernhard Reiter wrote:
> Am Donnerstag, 1. Oktober 2009 17:55:23 schrieb Richard Bos:
> > Op woensdag 02 september 2009 09:49:47 schreef Bernhard Reiter:
> > > Sorry for the delay, we are planning to have a techbase wiki page but
> > > this did not happen as fast as I was hoping for.
> >
> > Any news on this?
> 
> Not yet as far as I know.
> (I think Kevin or Till might directly drop an email to kolab-devel@ once
>  the initial page is there..)

Still not a techbase page, sorry, but I just pushed a blog post about how 
libkimap got created. That's hopefully a good place to start as I tried to 
provide insights on its design:
http://ervin.ipsquad.net/2009/10/22/libkimap-the-genesis/
 
Regards.
-- 
Kevin Ottens | kevin at kdab.net | KDE/Qt Software Engineer
Klar?lvdalens Datakonsult AB, a KDAB Group company
Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
KDAB - Qt Experts - Platform-independent software solutions
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091022/1cd2b15b/attachment.bin

From issues at kolab.org  Thu Oct 22 18:04:44 2009
From: issues at kolab.org (Bernhard Reiter)
Date: Thu, 22 Oct 2009 16:04:44 +0000
Subject: [Kolab-devel] [issue3926] Start khelpcenter instead of webbrowser
	help: from the	introduction/welcome screen (rt#5881)
In-Reply-To: <1256227484.86.0.894894130637.issue3926@kolab.org>
Message-ID: <1256227484.86.0.894894130637.issue3926@kolab.org>


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

Under the "help" menu there are two choices:

a) "Kontact Handbook" which opens the khelpcenter
b) "Kontact Introduction" which gets someone to the welcome screen
    were you can read: "Read Manual", which will open konqueror
    
What would be the effort to make Read Manual also open the khelpcenter?
Please estimate.

----------
assignedto: allen
keyword: enterprise35, kde client, kkc
messages: 22069
nosy: allen, bernhard, ludwig, till
priority: wish
status: unread
title: Start khelpcenter instead of webbrowser help: from the introduction/welcome screen (rt#5881)

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


From issues at kolab.org  Fri Oct 23 14:25:39 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Fri, 23 Oct 2009 12:25:39 +0000
Subject: [Kolab-devel] [issue3927] summary: completed event from today are
	displayed with	"in 623 hrs"
In-Reply-To: <1256300739.61.0.322189667554.issue3927@kolab.org>
Message-ID: <1256300739.61.0.322189667554.issue3927@kolab.org>


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

observed with Kontact e4 windows 20091010-1 of tag 20091010.1033359

Test: 
1. Create a event at today before the current time
   (e.g. at 9 o'clock, if it is 11 o'clock)
2. Look at the summary.
=> The event is displayed with "in 623 hrs". This is wrong because the event is
already completed.

----------
assignedto: allen
keyword: enterprise4, kde client
messages: 22073
nosy: allen, ludwig
priority: bug
status: unread
title: summary: completed event from today are displayed with "in 623 hrs"

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


From ml at radoeka.nl  Sun Oct 25 13:57:21 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sun, 25 Oct 2009 13:57:21 +0100
Subject: [Kolab-devel] kimap (imap library) Re: annotations patch in
	c-client what is the status?
In-Reply-To: <b756c91fbfb72929d5f269992f6968ab.squirrel@webmail.xs4all.nl>
References: <b756c91fbfb72929d5f269992f6968ab.squirrel@webmail.xs4all.nl>
Message-ID: <200910251357.22005.ml@radoeka.nl>

Op donderdag 22 oktober 2009 23:38:34 schreef u:
> On Tuesday 13 October 2009 12:16:27 Bernhard Reiter wrote:
> > Am Donnerstag, 1. Oktober 2009 17:55:23 schrieb Richard Bos:
> > > Op woensdag 02 september 2009 09:49:47 schreef Bernhard Reiter:
> > > > Sorry for the delay, we are planning to have a techbase wiki page but
> > > > this did not happen as fast as I was hoping for.
> > >
> > > Any news on this?
> >
> > Not yet as far as I know.
> > (I think Kevin or Till might directly drop an email to kolab-devel@ once
> >  the initial page is there..)
>
> Still not a techbase page, sorry, but I just pushed a blog post about how
> libkimap got created. That's hopefully a good place to start as I tried to
> provide insights on its design:
> http://ervin.ipsquad.net/2009/10/22/libkimap-the-genesis/

I stored the information here:
https://wiki.kolab.org/index.php/Server_component_UW_imap_c-client#C-
client_replacement_with_libkimap

An search on the wiki now results at least in something:
https://wiki.kolab.org/index.php/Special:Search?search=libkimap&go=Go

-- 
Richard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-devel/attachments/20091025/bdb27cfc/attachment.html

From issues at kolab.org  Tue Oct 27 12:11:57 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Tue, 27 Oct 2009 11:11:57 +0000
Subject: [Kolab-devel] [issue3928] Insert signature at cursor position: Two
	additional empty	lines added (rt#5880)
In-Reply-To: <1256641917.36.0.942994165032.issue3928@kolab.org>
Message-ID: <1256641917.36.0.942994165032.issue3928@kolab.org>


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

observed with Kontact e35 20091010.1035632-kk5

Test:
1. Open the mail configuration dialog and add a signature to the default ID.
2. Start to create a new mail.
3. Add two lines.
4. Set the cursor between this two test lines and use Edit->Insert signature at 
   cursor position.
=> The added signature contains two heading empty lines.
I expect that the signature is added without empty lines.

----------
assignedto: allen
keyword: enterprise35, kde client, kkc
messages: 22097
nosy: allen, ludwig
priority: bug
status: unread
title: Insert signature at cursor position: Two additional empty lines added (rt#5880)

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


From issues at kolab.org  Tue Oct 27 14:26:57 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Tue, 27 Oct 2009 13:26:57 +0000
Subject: [Kolab-devel] [issue3929] Contacts: The user can add a distribution
	list to itself
In-Reply-To: <1256650017.91.0.27828638597.issue3929@kolab.org>
Message-ID: <1256650017.91.0.27828638597.issue3929@kolab.org>


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

observed with Kontact e35 20091027.1040888-kk1

Test:
1. Switch to the contacts.
2. Create a new local distribution list.
3. Start to add a new contact to this list and try to add the list.
This is possible(!). It should not be possible to add the distlist to itself.

----------
assignedto: allen
keyword: enterprise35, kde client
messages: 22099
nosy: allen, ludwig
priority: bug
status: unread
title: Contacts: The user can add a distribution list to itself

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


From issues at kolab.org  Tue Oct 27 15:05:58 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Tue, 27 Oct 2009 14:05:58 +0000
Subject: [Kolab-devel] [issue3930] time on the Marcus Bains line doesn't
	change
In-Reply-To: <1256652358.86.0.514564761563.issue3930@kolab.org>
Message-ID: <1256652358.86.0.514564761563.issue3930@kolab.org>


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

observed with Kontact e35 20091027.1040888-kk1

The Marcus-Bain line time doesn't change. It stays on the same second.

output:
QObject::connect: Incompatible sender/receiver arguments
        QTimer::timeout() --> MarcusBains::updateLocation(bool)
QTime::setHMS Invalid time 24:00:00.000
QLayout "unnamed" added to QGroupBox "unnamed", which already has a layout

----------
assignedto: allen
keyword: enterprise35, kde client
messages: 22102
nosy: allen, ludwig
priority: urgent
status: unread
title: time on the Marcus Bains line doesn't change

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


From wrobel at pardus.de  Thu Oct 29 11:42:27 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 29 Oct 2009 11:42:27 +0100
Subject: [Kolab-devel] z-push Kolab backend
In-Reply-To: <4AE6EBA5.5000804@libertech.fr>
References: <200910222123.55612.phil@shellweb.homeip.net>
	<4AE631C7.5050708@libertech.fr>
	<20091027082719.20736z3ny1dyuckk@webmail.pardus.de>
	<4AE6B5B7.3010406@libertech.fr>
	<20091027110709.847418btmhgoguh8@webmail.pardus.de>
	<4AE6EBA5.5000804@libertech.fr>
Message-ID: <20091029114227.261434vnec1ixy8k@webmail.pardus.de>

Hi Alain,

considering the possible alternatives I guess placing the code on  
sourceforge for now is the best alternative.

So I started a new project at https://sourceforge.net/projects/kolabzpush
Can you give me your sourceforge id so that I can add you as admin there?

I checked in your v0.1 and the associated documentation in "trunk".

As I would like to package releases as a PEAR package named  
"Kolab_Zpush" it already has the basic structure with  
"Kolab_Zpush/lib" (for the code) and "Kolab_Zpush/doc" for the docs.

Once you have access can you commit your current code? Then we could  
continue from there.

I cc-ed kolab-devel at kolab.org and would like to continue discussions  
there so that people know what is happening concerning Kolab and  
Z-Push. One minor request: Can you use plain text mails for messages  
to the mailing lists? There are some people using mail readers that  
have difficulties with HTML-only mails.

Cheers,

Gunnar

Quoting Alain abbas <alain.abbas at libertech.fr>:

> we use SVN in internal and have some projets on sourceforge but i m
> open yes we are ok to contribute and to place the code in public.   
> Gunnar Wrobel a ?crit : Hi Alain,
>  if we work together on that it would be great to have a common
> workspace. Are you used to version control systems and if so do you
> have a specific preference? Would it be okay for Libertech to place
> the code in a public repository?
>  I personally have a preference for git at the moment and I tend to
> choose github.com as host for new projects. Sourceforge.net would
be
> a fine alternative. Another possibility might be the Horde
> repository. For that we'd be fixed to github.com (as I'd need to
> relay your commits from there to the Horde repository). It would
> have the advantage of getting feedback from the Horde community
> though and releasing the code as PEAR package for installations
> would be easier.
>  You can defintiely expect me to contribute in the area of
> Kolab_Storage integration, package structure and unit testing.
>  Cheers,
>  Gunnar
>
> Quoting Alain abbas
href=\"mailto:alain.abbas at libertech.fr\"><alain.abbas at libertech.fr>:
> Hi yes it would be great to integrate it at Kolab.  this  
> enchancement can resolve the moblity fonctionality  . a lot of  
> mobile have an
> Exchange connector builded on and the z-push-s code is really
great.
>
> The reason that we used imap directly is just a time dead line, i
> will look for to use the kolab_Storage in the next release .
>  Alain  Gunnar Wrobel a ?crit :
cite=\"mid:20091027082719.20736z3ny1dyuckk at webmail.pardus.de\"
> type=\"cite\">Hi Alain,  Quoting Alain abbas  class=\"moz-txt-link-rfc2396E\"
>
href=\"mailto:alain.abbas at libertech.fr\"><alain.abbas at libertech.fr>:
>
>  hi Phil Thanks to use our work  just disable the task in the  
> activesync setup on the phone because
> for now sync task is not implemented we will release a version 0.2  
> soon with these enchancements : - sync multi calendars and contacts  
> on the iphone - detection of  the contacts and calendars folders by  
> the
> annotation imap command - some correction of bug

This sounds really good. I looked at the code you used in 0.1 and was
wondering if you'd be willing to collaborate on getting this supported
directly in the Kolab server.

I noticed that you do the IMAP handling directly. Is there a specific
reason for that? You already use the Kolab_Format package for the XML
parsing and I think using Kolab_Storage for the IMAP handling would
make sense. Especially since you get caching of the Kolab objects that
way. Accessing an IMAP folder with thousands of events or contacts
should be significantly faster that way.

But other than that I think it would be worth trying to get this into
a package that can be distributed with the Kolab server. What do you
think?

Cheers,

Gunnar

> with have now arround 100 iphones, blackeberry ( with a third
> software) , windows mobile who sync with z-push and the kolab backend without
> major problems and with an easy setup ( Exchange setting on the  
> phone)   Phil Shelley a ?crit : I have the Kolab backend (version 0.1)
> working well with an i-phone 3G - Contacts (except for some missing  
> fields and photo), calendar and
> e-mail all working with a Kolab 2.2.2 server.  With Windows Mobile  
> 6.1 however, I can only get e-mail to work -
> Contacts and Calendar fail.  Does anyone know how to get contact and  
> calendar working with
> Windows Mobile 6.x?  Thanks for a superb piece of work.   
> _______________________________________________ Kolab-users mailing  
> list   href=\"mailto:Kolab-users at kolab.org\">Kolab-users at kolab.org
href=\"https://kolab.org/mailman/listinfo/kolab-users\">https://kolab.org/mailman/listinfo/kolab-users

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

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

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

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

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

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

-- 
______ http://kdab.com[1] _______________
http://kolab-konsortium.com[2] _

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

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


Links:
------
[1] http://kdab.com
[2] http://kolab-konsortium.com
[3] http://www.pardus.de
[4] http://gunnarwrobel.de

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091029/3246b400/attachment.bin

From wrobel at pardus.de  Thu Oct 29 11:49:12 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 29 Oct 2009 11:49:12 +0100
Subject: [Kolab-devel] z-push Kolab backend
In-Reply-To: <200910282054.47370.ml@radoeka.nl>
References: <200910222123.55612.phil@shellweb.homeip.net>
	<4AE631C7.5050708@libertech.fr>
	<20091027082719.20736z3ny1dyuckk@webmail.pardus.de>
	<200910282054.47370.ml@radoeka.nl>
Message-ID: <20091029114912.179750rol50rk8gs@webmail.pardus.de>

Hi Richard,

hope its okay to move this discussion to kolab-devel.

Quoting Richard Bos <ml at radoeka.nl>:

> Hi,
>
> Op dinsdag 27 oktober 2009 08:27:19 schreef Gunnar Wrobel:
> > > just disable the task in the activesync setup on the
> phone because for
> > > now sync task is not implemented
> > > we will release a version 0.2 soon with these
> enchancements :
> > > - sync multi calendars and contacts on the iphone
> > > - detection of  the contacts and calendars folders by the
> annotation
> > > imap command
> > > - some correction of bug
> >
> > This sounds really good. I looked at the code you used in 0.1
> and was  > wondering if you'd be willing to collaborate on getting this
> supported  > directly in the Kolab server.
>
> I made a wiki page for it on:
> http://wiki.kolab.org/index.php/Z_push#Z_push I  hope that it makes
> it easier for others to install the software.
>
> I have some questions / remarks about kolab-z-push, so please
> keep on reading this.
>
> I created 2 rpms for this, 1 that delivers z-push and the other
> the sole kolab.php to extend z-push for kolab.  The latter rpm
> (kolab-z-push) provides the following directories:# find z-push/
> -type d
> z-push/
> z-push/state
> z-push/kolabindex
> z-push/kolabindex/uid_id
> z-push/kolabindex/id_uid
> z-push/include
> z-push/backend
>
> Is this correct?  The directories state, kolabindex, uid_id and
> id_uid are writable  by the webserver user.
>
> When I browse to the url:
> https://<fqdn>/Microsoft-Server-ActiveSync it results in a
> popup window asking for a login and password, that seems to work
> well.  Is there a way to perform more testing?  Is it possible to
> test the kolab part of z-push (without device ;) )
>
> What about these defines:
> define('KOLAB_CONTACT_FOLDER',"inbox.contacts");
> define('KOLAB_DIARY_FOLDER',"inbox.calendrier");
> I have the following folders: Calendar and Contacts, should the
> KOLAB_CONTACT_FOLDER and KOLAB_DIARY_FOLDER be named inbox.Contacts
> and respectively inbox.Calendar?
>
> I created the rpms for openSUSE.  For openSUSE_11.1 they can be
> downloaded from:
>
http://download.opensuse.org/repositories/server:/php:/applications/openSUSE_11.1/noarch/
> other repositories exists for other openSUSE versions.
>
> Or search for the rpms with:
>
http://software.opensuse.org/search?baseproject=openSUSE:11.1&p=1&q=z-push

Cool, thanks! I'll download them and take a peek at the specs when I  
will create them for the Kolab server.

Cheers,

Gunnar

>
> -- 
> Richard
>
>

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

E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                         Bundesstrasse 29
Fax    : +49 721 1513 52322                        D-20146 Hamburg
--------------------------------------------------------------------
    >> Mail at ease - Rent a kolab groupware server at p at rdus <<
--------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091029/e0b3847b/attachment.bin

From wrobel at pardus.de  Thu Oct 29 11:56:24 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 29 Oct 2009 11:56:24 +0100
Subject: [Kolab-devel] z-push Kolab backend
In-Reply-To: <20091029114227.261434vnec1ixy8k@webmail.pardus.de>
References: <200910222123.55612.phil@shellweb.homeip.net>
	<4AE631C7.5050708@libertech.fr>
	<20091027082719.20736z3ny1dyuckk@webmail.pardus.de>
	<4AE6B5B7.3010406@libertech.fr>
	<20091027110709.847418btmhgoguh8@webmail.pardus.de>
	<4AE6EBA5.5000804@libertech.fr>
	<20091029114227.261434vnec1ixy8k@webmail.pardus.de>
Message-ID: <20091029115624.63272ijfmsealckk@webmail.pardus.de>

Quoting Gunnar Wrobel <wrobel at pardus.de>:

> Hi Alain,
>
> considering the possible alternatives I guess placing the code on   
> sourceforge for now is the best alternative.
>
> So I started a new project at https://sourceforge.net/projects/kolabzpush
> Can you give me your sourceforge id so that I can add you as admin there?
>
> I checked in your v0.1 and the associated documentation in "trunk".

I forgot to mention that I will mirror the code in the "zpush" branch  
in my horde playgrount on github  
(http://github.com/wrobel/horde/tree/zpush). The code    can be easily  
pushed to horde.org at a later timepoint then.

Cheers,

Gunnar

>
> As I would like to package releases as a PEAR package named   
> "Kolab_Zpush" it already has the basic structure with   
> "Kolab_Zpush/lib" (for the code) and "Kolab_Zpush/doc" for the docs.
>
> Once you have access can you commit your current code? Then we could  
>  continue from there.
>
> I cc-ed kolab-devel at kolab.org and would like to continue discussions  
>  there so that people know what is happening concerning Kolab and   
> Z-Push. One minor request: Can you use plain text mails for messages  
>  to the mailing lists? There are some people using mail readers that  
>  have difficulties with HTML-only mails.
>
> Cheers,
>
> Gunnar
>
> Quoting Alain abbas <alain.abbas at libertech.fr>:
>
>> we use SVN in internal and have some projets on sourceforge but i m
>> open yes we are ok to contribute and to place the code in public.    
>> Gunnar Wrobel a ?crit : Hi Alain,
>> if we work together on that it would be great to have a common
>> workspace. Are you used to version control systems and if so do you
>> have a specific preference? Would it be okay for Libertech to place
>> the code in a public repository?
>> I personally have a preference for git at the moment and I tend to
>> choose github.com as host for new projects. Sourceforge.net would
> be
>> a fine alternative. Another possibility might be the Horde
>> repository. For that we'd be fixed to github.com (as I'd need to
>> relay your commits from there to the Horde repository). It would
>> have the advantage of getting feedback from the Horde community
>> though and releasing the code as PEAR package for installations
>> would be easier.
>> You can defintiely expect me to contribute in the area of
>> Kolab_Storage integration, package structure and unit testing.
>> Cheers,
>> Gunnar
>>
>> Quoting Alain abbas
> href=\"mailto:alain.abbas at libertech.fr\"><alain.abbas at libertech.fr>:
>> Hi yes it would be great to integrate it at Kolab.  this   
>> enchancement can resolve the moblity fonctionality  . a lot of   
>> mobile have an
>> Exchange connector builded on and the z-push-s code is really
> great.
>>
>> The reason that we used imap directly is just a time dead line, i
>> will look for to use the kolab_Storage in the next release .
>> Alain  Gunnar Wrobel a ?crit :
> cite=\"mid:20091027082719.20736z3ny1dyuckk at webmail.pardus.de\"
>> type=\"cite\">Hi Alain,  Quoting Alain abbas   
>> class=\"moz-txt-link-rfc2396E\"
>>
> href=\"mailto:alain.abbas at libertech.fr\"><alain.abbas at libertech.fr>:
>>
>> hi Phil Thanks to use our work  just disable the task in the   
>> activesync setup on the phone because
>> for now sync task is not implemented we will release a version 0.2   
>> soon with these enchancements : - sync multi calendars and contacts  
>>  on the iphone - detection of  the contacts and calendars folders  
>> by  the
>> annotation imap command - some correction of bug
>
> This sounds really good. I looked at the code you used in 0.1 and was
> wondering if you'd be willing to collaborate on getting this supported
> directly in the Kolab server.
>
> I noticed that you do the IMAP handling directly. Is there a specific
> reason for that? You already use the Kolab_Format package for the XML
> parsing and I think using Kolab_Storage for the IMAP handling would
> make sense. Especially since you get caching of the Kolab objects that
> way. Accessing an IMAP folder with thousands of events or contacts
> should be significantly faster that way.
>
> But other than that I think it would be worth trying to get this into
> a package that can be distributed with the Kolab server. What do you
> think?
>
> Cheers,
>
> Gunnar
>
>> with have now arround 100 iphones, blackeberry ( with a third
>> software) , windows mobile who sync with z-push and the kolab  
>> backend without
>> major problems and with an easy setup ( Exchange setting on the   
>> phone)   Phil Shelley a ?crit : I have the Kolab backend (version  
>> 0.1)
>> working well with an i-phone 3G - Contacts (except for some missing  
>>  fields and photo), calendar and
>> e-mail all working with a Kolab 2.2.2 server.  With Windows Mobile   
>> 6.1 however, I can only get e-mail to work -
>> Contacts and Calendar fail.  Does anyone know how to get contact  
>> and  calendar working with
>> Windows Mobile 6.x?  Thanks for a superb piece of work.    
>> _______________________________________________ Kolab-users mailing  
>>  list   href=\"mailto:Kolab-users at kolab.org\">Kolab-users at kolab.org
> href=\"https://kolab.org/mailman/listinfo/kolab-users\">https://kolab.org/mailman/listinfo/kolab-users
>
> _______________________________________________
> Kolab-users mailing list
>  Kolab-users at kolab.org
>  https://kolab.org/mailman/listinfo/kolab-users
>
> -------------------------
> _______________________________________________ Kolab-users mailing
> list Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
> -- 
> ______ http://kdab.com _______________ http://kolab-konsortium.com _
>
> p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
>
> ____ http://www.pardus.de _________________ http://gunnarwrobel.de _
> E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
> Tel.   : +49 700 6245 0000                          Bundesstrasse 29
> Fax    : +49 721 1513 52322                          D-20146 Hamburg
> --------------------------------------------------------------------
>>> Mail at ease - Rent a kolab groupware server at p at rdus <<
> --------------------------------------------------------------------
>
> -------------------------
> _______________________________________________ Kolab-users mailing
> list Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
> -- 
> ______ http://kdab.com[1] _______________
> http://kolab-konsortium.com[2] _
>
> p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
>
> ____ http://www.pardus.de[3] _________________
> http://gunnarwrobel.de[4] _
> E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
> Tel.   : +49 700 6245 0000                          Bundesstrasse 29
> Fax    : +49 721 1513 52322                          D-20146 Hamburg
> --------------------------------------------------------------------
>    >> Mail at ease - Rent a kolab groupware server at p at rdus <<
> --------------------------------------------------------------------
>
>
> Links:
> ------
> [1] http://kdab.com
> [2] http://kolab-konsortium.com
> [3] http://www.pardus.de
> [4] http://gunnarwrobel.de
>
>



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

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

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091029/bcb6da7a/attachment.bin

From issues at kolab.org  Thu Oct 29 13:11:33 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Thu, 29 Oct 2009 12:11:33 +0000
Subject: [Kolab-devel] [issue3931] Automatic spellchecking doesn't work if
	action	tools->spellchecking is used(rt#5686)
In-Reply-To: <1256818293.84.0.514255319214.issue3931@kolab.org>
Message-ID: <1256818293.84.0.514255319214.issue3931@kolab.org>


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

observed with Kontact e35 20091027.1040888-kk1

A customer reported, that sometimes at long mails the automatic spellchecking
failed to work.

One case seem to be:
1. Start to create a new mail. (Composer)
2. Enter some test lines with some wrong spelled words.
3. Enter a wrong spelled word and use Tools-> spellchecking.
=> The cursor jumps to the earliest wrong word.
4. Scroll back to the last entered word.
=> It is still black.
I expect this word to be red, because it is wrong spelled.

----------
assignedto: allen
keyword: enterprise35, kde client
messages: 22126
nosy: allen, ludwig
priority: minor bug
status: unread
title: Automatic spellchecking doesn't work if action tools->spellchecking is used(rt#5686)

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


From alain.abbas at libertech.fr  Thu Oct 29 14:36:21 2009
From: alain.abbas at libertech.fr (Alain abbas)
Date: Thu, 29 Oct 2009 14:36:21 +0100
Subject: [Kolab-devel] z-push Kolab backend
In-Reply-To: <20091029114912.179750rol50rk8gs@webmail.pardus.de>
References: <200910222123.55612.phil@shellweb.homeip.net>	<4AE631C7.5050708@libertech.fr>	<20091027082719.20736z3ny1dyuckk@webmail.pardus.de>	<200910282054.47370.ml@radoeka.nl>
	<20091029114912.179750rol50rk8gs@webmail.pardus.de>
Message-ID: <4AE99A55.7020800@libertech.fr>

An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-devel/attachments/20091029/5e476238/attachment.html

From alain.abbas at libertech.fr  Thu Oct 29 14:38:54 2009
From: alain.abbas at libertech.fr (Alain abbas)
Date: Thu, 29 Oct 2009 14:38:54 +0100
Subject: [Kolab-devel] z-push Kolab backend
In-Reply-To: <20091029115624.63272ijfmsealckk@webmail.pardus.de>
References: <200910222123.55612.phil@shellweb.homeip.net>	<4AE631C7.5050708@libertech.fr>	<20091027082719.20736z3ny1dyuckk@webmail.pardus.de>	<4AE6B5B7.3010406@libertech.fr>	<20091027110709.847418btmhgoguh8@webmail.pardus.de>	<4AE6EBA5.5000804@libertech.fr>	<20091029114227.261434vnec1ixy8k@webmail.pardus.de>
	<20091029115624.63272ijfmsealckk@webmail.pardus.de>
Message-ID: <4AE99AEE.1000806@libertech.fr>

An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-devel/attachments/20091029/ba1f1fe4/attachment.html

From wrobel at pardus.de  Thu Oct 29 17:06:39 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 29 Oct 2009 17:06:39 +0100
Subject: [Kolab-devel] z-push Kolab backend
In-Reply-To: <4AE99AEE.1000806@libertech.fr>
References: <200910222123.55612.phil@shellweb.homeip.net>
	<4AE631C7.5050708@libertech.fr>
	<20091027082719.20736z3ny1dyuckk@webmail.pardus.de>
	<4AE6B5B7.3010406@libertech.fr>
	<20091027110709.847418btmhgoguh8@webmail.pardus.de>
	<4AE6EBA5.5000804@libertech.fr>
	<20091029114227.261434vnec1ixy8k@webmail.pardus.de>
	<20091029115624.63272ijfmsealckk@webmail.pardus.de>
	<4AE99AEE.1000806@libertech.fr>
Message-ID: <20091029170639.10831r2vifx65ack@webmail.pardus.de>

Hi Alain,

okay, I added "alain_abbas" but for "ghislain_ardyna" sourceforge  
tells me that the user does not exist.

Cheers,

Gunnar

Quoting Alain abbas <alain.abbas at libertech.fr>:

> oops Gunnar mde the same i cancel mine
> my sourceforge account is alain_abbas and you can add
> ghislain_ardyna  (Libertech's developper)
>  Gunnar Wrobel a ?crit :
cite=\"mid:20091029115624.63272ijfmsealckk at webmail.pardus.de\">Quoting
> Gunnar Wrobel <wrobel at pardus.de>[1]:  Hi Alain,  considering the  
> possible alternatives I guess placing the code on sourceforge for  
> now is the best alternative.  So I started a new project at
> https://sourceforge.net/projects/kolabzpush[2] Can you give me your  
> sourceforge id so that I can add you as admin
> there?  I checked in your v0.1 and the associated documentation in
> "trunk".

I forgot to mention that I will mirror the code in the "zpush" branch
in my horde playgrount on github
(http://github.com/wrobel/horde/tree/zpush[3]). The code    can be
easily pushed to horde.org at a later timepoint then.

Cheers,

Gunnar

> As I would like to package releases as a PEAR package named  
> "Kolab_Zpush" it already has the basic structure with  
> "Kolab_Zpush/lib" (for the code) and
> "Kolab_Zpush/doc" for the docs.  Once you have access can you commit  
> your current code? Then we
> could  continue from there.  I cc-ed kolab-devel at kolab.org[4] and  
> would like to continue
> discussions  there so that people know what is happening concerning
> Kolab and  Z-Push. One minor request: Can you use plain text mails
> for messages  to the mailing lists? There are some people using
mail
> readers that  have difficulties with HTML-only mails.  Cheers,   
> Gunnar  Quoting Alain abbas <alain.abbas at libertech.fr>[5]:  we use  
> SVN in internal and have some
> projets on sourceforge but i m open yes we are ok to contribute and  
> to place the code in public.  Gunnar Wrobel a ?crit : Hi Alain, if  
> we work together on that it would be great to have a common  
> workspace. Are you used to version control systems and if so do you
>
> have a specific preference? Would it be okay for Libertech to place
>
> the code in a public repository? I personally have a preference for  
> git at the moment and I tend to choose github.com as host for new  
> projects. Sourceforge.net would

  be

> a fine alternative. Another possibility might be the Horde  
> repository. For that we'd be fixed to github.com (as I'd need to  
> relay your commits from there to the Horde repository). It would  
> have the advantage of getting feedback from the Horde community  
> though and releasing the code as PEAR package for installations  
> would be easier. You can defintiely expect me to contribute in the  
> area of Kolab_Storage integration, package structure and unit  
> testing. Cheers, Gunnar  Quoting Alain abbas


href=\"mailto:alain.abbas at libertech.fr\"[6]><alain.abbas at libertech.fr>[7]:


> Hi yes it would be great to integrate it at Kolab.  this  
> enchancement can resolve the moblity fonctionality  . a lot of  
> mobile have an Exchange connector builded on and the z-push-s code  
> is really

  great.

> The reason that we used imap directly is just a time dead line, i  
> will look for to use the kolab_Storage in the next release . Alain   
> Gunnar Wrobel a ?crit :

  cite=\"mid:20091027082719.20736z3ny1dyuckk at webmail.pardus.de\"[8]

> type=\"cite\">Hi Alain,  Quoting Alain abbas class=\"moz-txt-link-rfc2396E\"


href=\"mailto:alain.abbas at libertech.fr\"[9]><alain.abbas at libertech.fr>[10]:


> hi Phil Thanks to use our work  just disable the task in the  
> activesync setup on the phone because for now sync task is not  
> implemented we will release a version 0.2 soon with these  
> enchancements : - sync multi calendars and contacts

> on the iphone - detection of  the contacts and calendars folders by

> the annotation imap command - some correction of bug

This sounds really good. I looked at the code you used in 0.1 and was

wondering if you'd be willing to collaborate on getting this
supported
directly in the Kolab server.

I noticed that you do the IMAP handling directly. Is there a specific

reason for that? You already use the Kolab_Format package for the XML

parsing and I think using Kolab_Storage for the IMAP handling would
make sense. Especially since you get caching of the Kolab objects
that
way. Accessing an IMAP folder with thousands of events or contacts
should be significantly faster that way.

But other than that I think it would be worth trying to get this into

a package that can be distributed with the Kolab server. What do you
think?

Cheers,

Gunnar

> with have now arround 100 iphones, blackeberry ( with a third  
> software) , windows mobile who sync with z-push and the kolab
> backend without major problems and with an easy setup ( Exchange  
> setting on the phone)   Phil Shelley a ?crit : I have the Kolab  
> backend (version
> 0.1) working well with an i-phone 3G - Contacts (except for some missing
>  fields and photo), calendar and e-mail all working with a Kolab  
> 2.2.2 server.  With Windows Mobile 6.1 however, I can only get  
> e-mail to work - Contacts and Calendar fail.  Does anyone know how  
> to get contact
> and  calendar working with Windows Mobile 6.x?  Thanks for a superb  
> piece of work.  _______________________________________________  
> Kolab-users mailing

> list  href=\"mailto:Kolab-users at kolab.org\"[11]>Kolab-users at kolab.org[12]


href=\"https://kolab.org/mailman/listinfo/kolab-users\"[13]>https://kolab.org/mailman/listinfo/kolab-users[14]


_______________________________________________
Kolab-users mailing list
  Kolab-users at kolab.org[15]
  https://kolab.org/mailman/listinfo/kolab-users[16]

-------------------------
_______________________________________________ Kolab-users mailing
list Kolab-users at kolab.org[17]
  https://kolab.org/mailman/listinfo/kolab-users[18]

-- 
______ http://kdab.com[19] _______________
http://kolab-konsortium.com[20] _

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

____ http://www.pardus.de[21] _________________
http://gunnarwrobel.de[22] _
E-mail : p at rdus.de[23]                                 Dr. Gunnar
Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
--------------------------------------------------------------------

> Mail at ease - Rent a kolab groupware
> server at p at rdus <<


--------------------------------------------------------------------

-------------------------
_______________________________________________ Kolab-users mailing
list Kolab-users at kolab.org[24]
  https://kolab.org/mailman/listinfo/kolab-users[25]

-- 
______ http://kdab.com[26][1] _______________
  http://kolab-konsortium.com[27][2] _

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

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

Links:
------
[1] http://kdab.com[31]
[2] http://kolab-konsortium.com[32]
[3] http://www.pardus.de[33]
[4] http://gunnarwrobel.de[34]

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

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

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

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

Links:
------
[1] mailto:wrobel at pardus.de
[2] https://sourceforge.net/projects/kolabzpush
[3] http://github.com/wrobel/horde/tree/zpush
[4] mailto:kolab-devel at kolab.org
[5] mailto:alain.abbas at libertech.fr
[6] mailto:alain.abbas at libertech.fr\
[7] mailto:alain.abbas at libertech.fr
[8] mailto:mid:20091027082719.20736z3ny1dyuckk at webmail.pardus.de\
[9] mailto:alain.abbas at libertech.fr\
[10] mailto:alain.abbas at libertech.fr
[11] mailto:Kolab-users at kolab.org\
[12] mailto:Kolab-users at kolab.org
[13] https://kolab.org/mailman/listinfo/kolab-users\
[14] https://kolab.org/mailman/listinfo/kolab-users
[15] mailto:Kolab-users at kolab.org
[16] https://kolab.org/mailman/listinfo/kolab-users
[17] mailto:Kolab-users at kolab.org
[18] https://kolab.org/mailman/listinfo/kolab-users
[19] http://kdab.com
[20] http://kolab-konsortium.com
[21] http://www.pardus.de
[22] http://gunnarwrobel.de
[23] mailto:p at rdus.de
[24] mailto:Kolab-users at kolab.org
[25] https://kolab.org/mailman/listinfo/kolab-users
[26] http://kdab.com
[27] http://kolab-konsortium.com
[28] http://www.pardus.de
[29] http://gunnarwrobel.de
[30] mailto:p at rdus.de
[31] http://kdab.com
[32] http://kolab-konsortium.com
[33] http://www.pardus.de
[34] http://gunnarwrobel.de

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091029/1365d48f/attachment-0001.bin

From issues at kolab.org  Fri Oct 30 14:54:20 2009
From: issues at kolab.org (Ludwig Reiter)
Date: Fri, 30 Oct 2009 13:54:20 +0000
Subject: [Kolab-devel] [issue3932] Kontact should show a warning,
	if a user tries to accept an invitation of a past event.
In-Reply-To: <1256910860.71.0.732386642864.issue3932@kolab.org>
Message-ID: <1256910860.71.0.732386642864.issue3932@kolab.org>


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

observed with Kontact e35 20091027.1040888-kk1

Test:
1. A invites B to a past event.
2. B syncs.
3. B accepts.

How can someone accept a past event? In this case a warning should be shown and
it should be possible to abort that he answered to a past event.

The estimation of this issue is kkc.
Please wait on an okay before start to implement.

----------
assignedto: allen
keyword: enterprise35, kde client, kkc
messages: 22142
nosy: allen, emanuel, ludwig
priority: wish
status: unread
title: Kontact should show a warning, if a user tries to accept an invitation of a past event.

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


From wrobel at pardus.de  Fri Oct 30 20:53:36 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Fri, 30 Oct 2009 20:53:36 +0100
Subject: [Kolab-devel] z-push Kolab backend
In-Reply-To: <4AE99AEE.1000806@libertech.fr>
References: <200910222123.55612.phil@shellweb.homeip.net>
	<4AE631C7.5050708@libertech.fr>
	<20091027082719.20736z3ny1dyuckk@webmail.pardus.de>
	<4AE6B5B7.3010406@libertech.fr>
	<20091027110709.847418btmhgoguh8@webmail.pardus.de>
	<4AE6EBA5.5000804@libertech.fr>
	<20091029114227.261434vnec1ixy8k@webmail.pardus.de>
	<20091029115624.63272ijfmsealckk@webmail.pardus.de>
	<4AE99AEE.1000806@libertech.fr>
Message-ID: <20091030205336.18196w5ug9quca4o@webmail.pardus.de>

Hi Alain,

Quoting Alain abbas <alain.abbas at libertech.fr>:

> oops Gunnar mde the same i cancel mine
> my sourceforge account is alain_abbas and you can add
> ghislain_ardyna  (Libertech's developper)

Both have been added now.

Is v0.1 you released the most up-to-date version or did you already  
continue development internally?

Once you give me a sign that the most current version is checked in  
I'd start trying to get this into Kolab packages and maybe start a  
test suite.

Cheers,

Gunnar

>  Gunnar Wrobel a ?crit :
cite=\"mid:20091029115624.63272ijfmsealckk at webmail.pardus.de\">Quoting
> Gunnar Wrobel <wrobel at pardus.de>[1]:  Hi Alain,  considering the  
> possible alternatives I guess placing the code on sourceforge for  
> now is the best alternative.  So I started a new project at
> https://sourceforge.net/projects/kolabzpush[2] Can you give me your  
> sourceforge id so that I can add you as admin
> there?  I checked in your v0.1 and the associated documentation in
> "trunk".

I forgot to mention that I will mirror the code in the "zpush" branch
in my horde playgrount on github
(http://github.com/wrobel/horde/tree/zpush[3]). The code    can be
easily pushed to horde.org at a later timepoint then.

Cheers,

Gunnar

> As I would like to package releases as a PEAR package named  
> "Kolab_Zpush" it already has the basic structure with  
> "Kolab_Zpush/lib" (for the code) and
> "Kolab_Zpush/doc" for the docs.  Once you have access can you commit  
> your current code? Then we
> could  continue from there.  I cc-ed kolab-devel at kolab.org[4] and  
> would like to continue
> discussions  there so that people know what is happening concerning
> Kolab and  Z-Push. One minor request: Can you use plain text mails
> for messages  to the mailing lists? There are some people using
mail
> readers that  have difficulties with HTML-only mails.  Cheers,   
> Gunnar  Quoting Alain abbas <alain.abbas at libertech.fr>[5]:  we use  
> SVN in internal and have some
> projets on sourceforge but i m open yes we are ok to contribute and  
> to place the code in public.  Gunnar Wrobel a ?crit : Hi Alain, if  
> we work together on that it would be great to have a common  
> workspace. Are you used to version control systems and if so do you
>
> have a specific preference? Would it be okay for Libertech to place
>
> the code in a public repository? I personally have a preference for  
> git at the moment and I tend to choose github.com as host for new  
> projects. Sourceforge.net would

  be

> a fine alternative. Another possibility might be the Horde  
> repository. For that we'd be fixed to github.com (as I'd need to  
> relay your commits from there to the Horde repository). It would  
> have the advantage of getting feedback from the Horde community  
> though and releasing the code as PEAR package for installations  
> would be easier. You can defintiely expect me to contribute in the  
> area of Kolab_Storage integration, package structure and unit  
> testing. Cheers, Gunnar  Quoting Alain abbas


href=\"mailto:alain.abbas at libertech.fr\"[6]><alain.abbas at libertech.fr>[7]:


> Hi yes it would be great to integrate it at Kolab.  this  
> enchancement can resolve the moblity fonctionality  . a lot of  
> mobile have an Exchange connector builded on and the z-push-s code  
> is really

  great.

> The reason that we used imap directly is just a time dead line, i  
> will look for to use the kolab_Storage in the next release . Alain   
> Gunnar Wrobel a ?crit :

  cite=\"mid:20091027082719.20736z3ny1dyuckk at webmail.pardus.de\"[8]

> type=\"cite\">Hi Alain,  Quoting Alain abbas class=\"moz-txt-link-rfc2396E\"


href=\"mailto:alain.abbas at libertech.fr\"[9]><alain.abbas at libertech.fr>[10]:


> hi Phil Thanks to use our work  just disable the task in the  
> activesync setup on the phone because for now sync task is not  
> implemented we will release a version 0.2 soon with these  
> enchancements : - sync multi calendars and contacts

> on the iphone - detection of  the contacts and calendars folders by

> the annotation imap command - some correction of bug

This sounds really good. I looked at the code you used in 0.1 and was

wondering if you'd be willing to collaborate on getting this
supported
directly in the Kolab server.

I noticed that you do the IMAP handling directly. Is there a specific

reason for that? You already use the Kolab_Format package for the XML

parsing and I think using Kolab_Storage for the IMAP handling would
make sense. Especially since you get caching of the Kolab objects
that
way. Accessing an IMAP folder with thousands of events or contacts
should be significantly faster that way.

But other than that I think it would be worth trying to get this into

a package that can be distributed with the Kolab server. What do you
think?

Cheers,

Gunnar

> with have now arround 100 iphones, blackeberry ( with a third  
> software) , windows mobile who sync with z-push and the kolab
> backend without major problems and with an easy setup ( Exchange  
> setting on the phone)   Phil Shelley a ?crit : I have the Kolab  
> backend (version
> 0.1) working well with an i-phone 3G - Contacts (except for some missing
>  fields and photo), calendar and e-mail all working with a Kolab  
> 2.2.2 server.  With Windows Mobile 6.1 however, I can only get  
> e-mail to work - Contacts and Calendar fail.  Does anyone know how  
> to get contact
> and  calendar working with Windows Mobile 6.x?  Thanks for a superb  
> piece of work.  _______________________________________________  
> Kolab-users mailing

> list  href=\"mailto:Kolab-users at kolab.org\"[11]>Kolab-users at kolab.org[12]


href=\"https://kolab.org/mailman/listinfo/kolab-users\"[13]>https://kolab.org/mailman/listinfo/kolab-users[14]


_______________________________________________
Kolab-users mailing list
  Kolab-users at kolab.org[15]
  https://kolab.org/mailman/listinfo/kolab-users[16]

-------------------------
_______________________________________________ Kolab-users mailing
list Kolab-users at kolab.org[17]
  https://kolab.org/mailman/listinfo/kolab-users[18]

-- 
______ http://kdab.com[19] _______________
http://kolab-konsortium.com[20] _

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

____ http://www.pardus.de[21] _________________
http://gunnarwrobel.de[22] _
E-mail : p at rdus.de[23]                                 Dr. Gunnar
Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
--------------------------------------------------------------------

> Mail at ease - Rent a kolab groupware
> server at p at rdus <<


--------------------------------------------------------------------

-------------------------
_______________________________________________ Kolab-users mailing
list Kolab-users at kolab.org[24]
  https://kolab.org/mailman/listinfo/kolab-users[25]

-- 
______ http://kdab.com[26][1] _______________
  http://kolab-konsortium.com[27][2] _

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

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

Links:
------
[1] http://kdab.com[31]
[2] http://kolab-konsortium.com[32]
[3] http://www.pardus.de[33]
[4] http://gunnarwrobel.de[34]

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

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

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

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

Links:
------
[1] mailto:wrobel at pardus.de
[2] https://sourceforge.net/projects/kolabzpush
[3] http://github.com/wrobel/horde/tree/zpush
[4] mailto:kolab-devel at kolab.org
[5] mailto:alain.abbas at libertech.fr
[6] mailto:alain.abbas at libertech.fr\
[7] mailto:alain.abbas at libertech.fr
[8] mailto:mid:20091027082719.20736z3ny1dyuckk at webmail.pardus.de\
[9] mailto:alain.abbas at libertech.fr\
[10] mailto:alain.abbas at libertech.fr
[11] mailto:Kolab-users at kolab.org\
[12] mailto:Kolab-users at kolab.org
[13] https://kolab.org/mailman/listinfo/kolab-users\
[14] https://kolab.org/mailman/listinfo/kolab-users
[15] mailto:Kolab-users at kolab.org
[16] https://kolab.org/mailman/listinfo/kolab-users
[17] mailto:Kolab-users at kolab.org
[18] https://kolab.org/mailman/listinfo/kolab-users
[19] http://kdab.com
[20] http://kolab-konsortium.com
[21] http://www.pardus.de
[22] http://gunnarwrobel.de
[23] mailto:p at rdus.de
[24] mailto:Kolab-users at kolab.org
[25] https://kolab.org/mailman/listinfo/kolab-users
[26] http://kdab.com
[27] http://kolab-konsortium.com
[28] http://www.pardus.de
[29] http://gunnarwrobel.de
[30] mailto:p at rdus.de
[31] http://kdab.com
[32] http://kolab-konsortium.com
[33] http://www.pardus.de
[34] http://gunnarwrobel.de

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
Url : http://kolab.org/pipermail/kolab-devel/attachments/20091030/e866df54/attachment.bin

From alain.abbas at libertech.fr  Sat Oct 31 00:08:55 2009
From: alain.abbas at libertech.fr (Alain abbas)
Date: Sat, 31 Oct 2009 00:08:55 +0100
Subject: [Kolab-devel] z-push Kolab backend
In-Reply-To: <20091030205336.18196w5ug9quca4o@webmail.pardus.de>
References: <200910222123.55612.phil@shellweb.homeip.net>	<4AE631C7.5050708@libertech.fr>	<20091027082719.20736z3ny1dyuckk@webmail.pardus.de>	<4AE6B5B7.3010406@libertech.fr>	<20091027110709.847418btmhgoguh8@webmail.pardus.de>	<4AE6EBA5.5000804@libertech.fr>	<20091029114227.261434vnec1ixy8k@webmail.pardus.de>	<20091029115624.63272ijfmsealckk@webmail.pardus.de>	<4AE99AEE.1000806@libertech.fr>
	<20091030205336.18196w5ug9quca4o@webmail.pardus.de>
Message-ID: <4AEB7207.6090801@libertech.fr>

hi Gunnar

I had iphone problems that i resolved today ( problem with folder by 
default when i wrote a contact  on the iphone  and when there are shared 
folders)
i will publish the code e in the trunk for the 0.2 thursday  im busy before)
this code a these features :
- Annotation detection for default Contacts folder and default Calendar 
( for the moment with the standard imap library  )
- Shared folders Contacts on the iphone
- for the moment annotation code is ugly but we will migrate on the 
Kolab_Storage Library

Must to test and not tested now :
-Mobile Windows ( i ve got just a HTC with an old Windows mobile Version)
- Blackbery with a third software for Exchange connexion

bugs that i noticed for the 0.2
- performance with shared Calendar ( due to the cutOffdate that is not 
implemented )
- display bug with users shared folders in Calendar and Contacts ( 
displayed the name of the user and not user/folder)



we have put the code on your production server this friday.

for the 0.3 i would migrate the imap library -> kolab_Storage like you 
adviced and work arround the cutOffDate that would be great
for performance when more than one Calendar would be pushed on the 
mobile (iphone)

Could you install  the trac bug and the feature request ? perhaps well , 
i let you decide you have got more experience than me .

Alain  Abbas
Regards and good week end 
Gunnar Wrobel a ?crit :
> Hi Alain,
>
> Quoting Alain abbas <alain.abbas at libertech.fr>:
>
>> oops Gunnar mde the same i cancel mine
>> my sourceforge account is alain_abbas and you can add
>> ghislain_ardyna  (Libertech's developper)
>
> Both have been added now.
>
> Is v0.1 you released the most up-to-date version or did you already 
> continue development internally?
>
> Once you give me a sign that the most current version is checked in 
> I'd start trying to get this into Kolab packages and maybe start a 
> test suite.
>
> Cheers,
>
> Gunnar
>
>>  Gunnar Wrobel a ?crit :
> cite=\"mid:20091029115624.63272ijfmsealckk at webmail.pardus.de\">Quoting
>> Gunnar Wrobel <wrobel at pardus.de>[1]:  Hi Alain,  considering the 
>> possible alternatives I guess placing the code on sourceforge for now 
>> is the best alternative.  So I started a new project at
>> https://sourceforge.net/projects/kolabzpush[2] Can you give me your 
>> sourceforge id so that I can add you as admin
>> there?  I checked in your v0.1 and the associated documentation in
>> "trunk".
>
> I forgot to mention that I will mirror the code in the "zpush" branch
> in my horde playgrount on github
> (http://github.com/wrobel/horde/tree/zpush[3]). The code    can be
> easily pushed to horde.org at a later timepoint then.
>
> Cheers,
>
> Gunnar
>
>> As I would like to package releases as a PEAR package named 
>> "Kolab_Zpush" it already has the basic structure with 
>> "Kolab_Zpush/lib" (for the code) and
>> "Kolab_Zpush/doc" for the docs.  Once you have access can you commit 
>> your current code? Then we
>> could  continue from there.  I cc-ed kolab-devel at kolab.org[4] and 
>> would like to continue
>> discussions  there so that people know what is happening concerning
>> Kolab and  Z-Push. One minor request: Can you use plain text mails
>> for messages  to the mailing lists? There are some people using
> mail
>> readers that  have difficulties with HTML-only mails.  Cheers,  
>> Gunnar  Quoting Alain abbas <alain.abbas at libertech.fr>[5]:  we use 
>> SVN in internal and have some
>> projets on sourceforge but i m open yes we are ok to contribute and 
>> to place the code in public.  Gunnar Wrobel a ?crit : Hi Alain, if we 
>> work together on that it would be great to have a common workspace. 
>> Are you used to version control systems and if so do you
>>
>> have a specific preference? Would it be okay for Libertech to place
>>
>> the code in a public repository? I personally have a preference for 
>> git at the moment and I tend to choose github.com as host for new 
>> projects. Sourceforge.net would
>
>  be
>
>> a fine alternative. Another possibility might be the Horde 
>> repository. For that we'd be fixed to github.com (as I'd need to 
>> relay your commits from there to the Horde repository). It would have 
>> the advantage of getting feedback from the Horde community though and 
>> releasing the code as PEAR package for installations would be easier. 
>> You can defintiely expect me to contribute in the area of 
>> Kolab_Storage integration, package structure and unit testing. 
>> Cheers, Gunnar  Quoting Alain abbas
>
>
> href=\"mailto:alain.abbas at libertech.fr\"[6]><alain.abbas at libertech.fr>[7]: 
>
>
>
>> Hi yes it would be great to integrate it at Kolab.  this enchancement 
>> can resolve the moblity fonctionality  . a lot of mobile have an 
>> Exchange connector builded on and the z-push-s code is really
>
>  great.
>
>> The reason that we used imap directly is just a time dead line, i 
>> will look for to use the kolab_Storage in the next release . Alain  
>> Gunnar Wrobel a ?crit :
>
>  cite=\"mid:20091027082719.20736z3ny1dyuckk at webmail.pardus.de\"[8]
>
>> type=\"cite\">Hi Alain,  Quoting Alain abbas 
>> class=\"moz-txt-link-rfc2396E\"
>
>
> href=\"mailto:alain.abbas at libertech.fr\"[9]><alain.abbas at libertech.fr>[10]: 
>
>
>
>> hi Phil Thanks to use our work  just disable the task in the 
>> activesync setup on the phone because for now sync task is not 
>> implemented we will release a version 0.2 soon with these 
>> enchancements : - sync multi calendars and contacts
>
>> on the iphone - detection of  the contacts and calendars folders by
>
>> the annotation imap command - some correction of bug
>
> This sounds really good. I looked at the code you used in 0.1 and was
>
> wondering if you'd be willing to collaborate on getting this
> supported
> directly in the Kolab server.
>
> I noticed that you do the IMAP handling directly. Is there a specific
>
> reason for that? You already use the Kolab_Format package for the XML
>
> parsing and I think using Kolab_Storage for the IMAP handling would
> make sense. Especially since you get caching of the Kolab objects
> that
> way. Accessing an IMAP folder with thousands of events or contacts
> should be significantly faster that way.
>
> But other than that I think it would be worth trying to get this into
>
> a package that can be distributed with the Kolab server. What do you
> think?
>
> Cheers,
>
> Gunnar
>
>> with have now arround 100 iphones, blackeberry ( with a third 
>> software) , windows mobile who sync with z-push and the kolab
>> backend without major problems and with an easy setup ( Exchange 
>> setting on the phone)   Phil Shelley a ?crit : I have the Kolab 
>> backend (version
>> 0.1) working well with an i-phone 3G - Contacts (except for some missing
>>  fields and photo), calendar and e-mail all working with a Kolab 
>> 2.2.2 server.  With Windows Mobile 6.1 however, I can only get e-mail 
>> to work - Contacts and Calendar fail.  Does anyone know how to get 
>> contact
>> and  calendar working with Windows Mobile 6.x?  Thanks for a superb 
>> piece of work.  _______________________________________________ 
>> Kolab-users mailing
>
>> list  
>> href=\"mailto:Kolab-users at kolab.org\"[11]>Kolab-users at kolab.org[12]
>
>
> href=\"https://kolab.org/mailman/listinfo/kolab-users\"[13]>https://kolab.org/mailman/listinfo/kolab-users[14] 
>
>
>
> _______________________________________________
> Kolab-users mailing list
>  Kolab-users at kolab.org[15]
>  https://kolab.org/mailman/listinfo/kolab-users[16]
>
> -------------------------
> _______________________________________________ Kolab-users mailing
> list Kolab-users at kolab.org[17]
>  https://kolab.org/mailman/listinfo/kolab-users[18]
>