From ml at radoeka.nl  Fri May  1 12:15:06 2009
From: ml at radoeka.nl (Richard Bos)
Date: Fri, 1 May 2009 12:15:06 +0200
Subject: kolab on openSUSE natively is a little bit back
In-Reply-To: <200904302141.23326.carsten@cburghardt.com>
References: <200902142107.48113.ml@radoeka.nl> <49F9546E.7000901@err.ee>
	<200904302141.23326.carsten@cburghardt.com>
Message-ID: <200905011215.07484.ml@radoeka.nl>

Op donderdag 30 april 2009 21:41:23 schreef Carsten Burghardt:
> > What version of perl-ldap to you have? I found this link
> > https://www.intevation.de/roundup/kolab/issue1755
>
> Well, the version is perl-ldap-0.39-5.2 from the kolab suse repository but
> it does not contain the fix. Thanks for spotting this. I assume the package
> is too old.

It's not.  I have the same and it is working fine.
kolab2:~ # rpm -q perl-ldap
perl-ldap-0.39-5.3

At the moment I can't think of a reason why you can't start ldap.  I believe I 
have seen the same thing, perhaps it is mentioned in issue1755.

-- 
Richard



From ml at radoeka.nl  Fri May  1 15:11:48 2009
From: ml at radoeka.nl (Richard Bos)
Date: Fri, 1 May 2009 15:11:48 +0200
Subject: kolab - opensuse 11.1
In-Reply-To: <200904302207.41151.carsten@cburghardt.com>
References: <200904021301.32465.ml@radoeka.nl>
	<200904302207.41151.carsten@cburghardt.com>
Message-ID: <200905011511.49777.ml@radoeka.nl>

Op donderdag 30 april 2009 22:07:41 schreef Carsten Burghardt:
> Am Donnerstag, 2. April 2009 13:01:32 schrieb Richard Bos:
> > Hello Steven,
> >
> > Op donderdag 02 april 2009 02:45:31 schreef u:
> > > I have been struggling with the install given on this page:
> > > http://en.opensuse.org/kolab
> > >
> > > I have tried the instructions with opensuse 11.0 and  11.1
> > >
> > > postfix is bouncing my mail with a php error:
> > >
> > >  83EE81AE1FA: to=<user1 at hd.net>, relay=kolabfilter, delay=0.21,
> > > delays=0.09/0/0/0.11, dsn=5.3.0, status=bounced (Command died with
> > > status 1: "/usr/bin/php5". Command output: Could not open input file:
> > > /usr/bin/kolabfilter )
> >
> > Does this file /usr/bin/kolabfilter exists?
> > # ls -l /usr/bin/kolabfilter
> >
> > What version of kolab do you have installed:
> > # rpm -q kolab kolab-filter
> >
> > > Apr  1 18:59:48 sft postfix/cleanup[7318]: B445B1AE1FD:
> > > message-id=<20090401225948.B445B1AE1FD at sft.hd.net>
> > > Apr  1 18:59:48 sft postfix/bounce[7321]: 83EE81AE1FA: sender
> > > non-delivery notification: B445B1AE1FD
> > > Apr  1 18:59:48 sft postfix/qmgr[7190]: B445B1AE1FD: from=<>,
> > > size=2243, nrcpt=1 (queue active)
> > > Apr  1 18:59:48 sft postfix/qmgr[7190]: 83EE81AE1FA: removed
> > > Apr  1 18:59:48 sft postfix/pipe[7323]: B445B1AE1FD: to=<sft at hd.net>,
> > > relay=kolabmailboxfilter, delay=0.11, delays=0.04/0.01/0/0.06,
> > > dsn=5.3.0, status=bounced (Command died with status 1:
> > > "/usr/bin/php5". Command output: Could not open input file:
> > > /usr/bin/kolabmailboxfilter )
> > > Apr  1 18:59:48 sft postfix/qmgr[7190]: B445B1AE1FD: removed
> > >
> > > What am I doing wrong?
> >
> > See questions as above, does the file exists
> > (/usr/bin/kolabmailboxfilter)
> >
> > # rpm -qf /usr/bin/kolabmailboxfilter
>
> Those files do not exist on my upgraded system (10.3). What package should
> include them?

On 10.3 I think it is:
/var/lib/kolab/kolab-filter/kolabmailboxfilter.php, but that is a big guess.  
If that is indeed the correct file, the package kolab-filter provides it.



-- 
Richard



From thomas at btspuhler.com  Sat May  2 03:14:08 2009
From: thomas at btspuhler.com (Thomas Spuhler)
Date: Fri, 1 May 2009 18:14:08 -0700
Subject: kolab on openSUSE natively is a little bit back
In-Reply-To: <200905011215.07484.ml@radoeka.nl>
References: <200902142107.48113.ml@radoeka.nl>
	<200904302141.23326.carsten@cburghardt.com>
	<200905011215.07484.ml@radoeka.nl>
Message-ID: <200905011814.08689.thomas@btspuhler.com>

On Friday 01 May 2009, Richard Bos wrote:
> Op donderdag 30 april 2009 21:41:23 schreef Carsten Burghardt:
> > > What version of perl-ldap to you have? I found this link
> > > https://www.intevation.de/roundup/kolab/issue1755
> >
> > Well, the version is perl-ldap-0.39-5.2 from the kolab suse repository
> > but it does not contain the fix. Thanks for spotting this. I assume the
> > package is too old.
>
> It's not.  I have the same and it is working fine.
> kolab2:~ # rpm -q perl-ldap
> perl-ldap-0.39-5.3
>
> At the moment I can't think of a reason why you can't start ldap.  I
> believe I have seen the same thing, perhaps it is mentioned in issue1755.

you have -5.3 vs. -5.2
different build but what else?

-- 
Thomas



From ml at radoeka.nl  Sat May  2 11:02:27 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sat, 2 May 2009 11:02:27 +0200
Subject: kolab on openSUSE natively is a little bit back
In-Reply-To: <200905011814.08689.thomas@btspuhler.com>
References: <200902142107.48113.ml@radoeka.nl>
	<200905011215.07484.ml@radoeka.nl>
	<200905011814.08689.thomas@btspuhler.com>
Message-ID: <200905021102.27738.ml@radoeka.nl>

Op zaterdag 02 mei 2009 03:14:08 schreef Thomas Spuhler:
> On Friday 01 May 2009, Richard Bos wrote:
> > Op donderdag 30 april 2009 21:41:23 schreef Carsten Burghardt:
> > > > What version of perl-ldap to you have? I found this link
> > > > https://www.intevation.de/roundup/kolab/issue1755
> > >
> > > Well, the version is perl-ldap-0.39-5.2 from the kolab suse repository
> > > but it does not contain the fix. Thanks for spotting this. I assume the
> > > package is too old.
> >
> > It's not.  I have the same and it is working fine.
> > kolab2:~ # rpm -q perl-ldap
> > perl-ldap-0.39-5.3
> >
> > At the moment I can't think of a reason why you can't start ldap.  I
> > believe I have seen the same thing, perhaps it is mentioned in issue1755.
>
> you have -5.3 vs. -5.2
> different build but what else?

That's a very minimal difference.  That number is added by the openSUSE build 
service, when a build is restarted.  This might be triggered by a package that 
is needed as build dependency for the perl-ldap package.

-- 
Richard



From carsten at cburghardt.com  Mon May  4 07:15:28 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Mon, 04 May 2009 07:15:28 +0200
Subject: kolab on openSUSE natively is a little bit back
In-Reply-To: <200905021102.27738.ml@radoeka.nl>
References: <200902142107.48113.ml@radoeka.nl>
	<200905011215.07484.ml@radoeka.nl>
	<200905011814.08689.thomas@btspuhler.com>
	<200905021102.27738.ml@radoeka.nl>
Message-ID: <20090504071528.98501fjvak0m2txc@www.inovox.de>

Quoting "Richard Bos" <ml at radoeka.nl>:

> Op zaterdag 02 mei 2009 03:14:08 schreef Thomas Spuhler:
>> On Friday 01 May 2009, Richard Bos wrote:
>> > Op donderdag 30 april 2009 21:41:23 schreef Carsten Burghardt:
>> > > > What version of perl-ldap to you have? I found this link
>> > > > https://www.intevation.de/roundup/kolab/issue1755
>> > >
>> > > Well, the version is perl-ldap-0.39-5.2 from the kolab suse repository
>> > > but it does not contain the fix. Thanks for spotting this. I assume the
>> > > package is too old.
>> >
>> > It's not.  I have the same and it is working fine.
>> > kolab2:~ # rpm -q perl-ldap
>> > perl-ldap-0.39-5.3
>> >
>> > At the moment I can't think of a reason why you can't start ldap.  I
>> > believe I have seen the same thing, perhaps it is mentioned in issue1755.
>>
>> you have -5.3 vs. -5.2
>> different build but what else?
>
> That's a very minimal difference.  That number is added by the openSUSE build
> service, when a build is restarted.  This might be triggered by a  
> package that
> is needed as build dependency for the perl-ldap package.

Well, I installed the package from the kolab suse repository and at  
least on my system the patch is not included. Once I patched it  
manually the cookie parsing problem was gone.


Carsten



From carsten at cburghardt.com  Mon May  4 09:30:45 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Mon, 04 May 2009 09:30:45 +0200
Subject: kolab - opensuse 11.1
In-Reply-To: <200905011511.49777.ml@radoeka.nl>
References: <200904021301.32465.ml@radoeka.nl>
	<200904302207.41151.carsten@cburghardt.com>
	<200905011511.49777.ml@radoeka.nl>
Message-ID: <20090504093045.18112egfqsgwsbms@www.inovox.de>

Quoting "Richard Bos" <ml at radoeka.nl>:

> Op donderdag 30 april 2009 22:07:41 schreef Carsten Burghardt:
>> Am Donnerstag, 2. April 2009 13:01:32 schrieb Richard Bos:
>> > Hello Steven,
>> >
>> > Op donderdag 02 april 2009 02:45:31 schreef u:
>> > > I have been struggling with the install given on this page:
>> > > http://en.opensuse.org/kolab
>> > >
>> > > I have tried the instructions with opensuse 11.0 and  11.1
>> > >
>> > > postfix is bouncing my mail with a php error:
>> > >
>> > >  83EE81AE1FA: to=<user1 at hd.net>, relay=kolabfilter, delay=0.21,
>> > > delays=0.09/0/0/0.11, dsn=5.3.0, status=bounced (Command died with
>> > > status 1: "/usr/bin/php5". Command output: Could not open input file:
>> > > /usr/bin/kolabfilter )
>> >
>> > Does this file /usr/bin/kolabfilter exists?
>> > # ls -l /usr/bin/kolabfilter
>> >
>> > What version of kolab do you have installed:
>> > # rpm -q kolab kolab-filter
>> >
>> > > Apr  1 18:59:48 sft postfix/cleanup[7318]: B445B1AE1FD:
>> > > message-id=<20090401225948.B445B1AE1FD at sft.hd.net>
>> > > Apr  1 18:59:48 sft postfix/bounce[7321]: 83EE81AE1FA: sender
>> > > non-delivery notification: B445B1AE1FD
>> > > Apr  1 18:59:48 sft postfix/qmgr[7190]: B445B1AE1FD: from=<>,
>> > > size=2243, nrcpt=1 (queue active)
>> > > Apr  1 18:59:48 sft postfix/qmgr[7190]: 83EE81AE1FA: removed
>> > > Apr  1 18:59:48 sft postfix/pipe[7323]: B445B1AE1FD: to=<sft at hd.net>,
>> > > relay=kolabmailboxfilter, delay=0.11, delays=0.04/0.01/0/0.06,
>> > > dsn=5.3.0, status=bounced (Command died with status 1:
>> > > "/usr/bin/php5". Command output: Could not open input file:
>> > > /usr/bin/kolabmailboxfilter )
>> > > Apr  1 18:59:48 sft postfix/qmgr[7190]: B445B1AE1FD: removed
>> > >
>> > > What am I doing wrong?
>> >
>> > See questions as above, does the file exists
>> > (/usr/bin/kolabmailboxfilter)
>> >
>> > # rpm -qf /usr/bin/kolabmailboxfilter
>>
>> Those files do not exist on my upgraded system (10.3). What package should
>> include them?
>
> On 10.3 I think it is:
> /var/lib/kolab/kolab-filter/kolabmailboxfilter.php, but that is a big guess.
> If that is indeed the correct file, the package kolab-filter provides it.

The file you mentioned exists but in the pipe command it looks for  
/usr/bin/kolabmailboxfilter. Should I create a link or change the  
command? I assume this should also be changed in the package then?


Carsten



From bernhard at intevation.de  Mon May  4 10:34:46 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 4 May 2009 10:34:46 +0200
Subject: Blackberry, Horde, Thunderbird, Outlook co-existence
In-Reply-To: <49E8B1B0.3010202@lancer-ins.com>
References: <49DB81CC.2050306@lancer-ins.com>
	<200904161846.05371.bernhard@intevation.de>
	<49E8B1B0.3010202@lancer-ins.com>
Message-ID: <200905041034.49715.bernhard@intevation.de>

Am Freitag, 17. April 2009 18:43:28 schrieb Tom Malone:
> Bernhard Reiter wrote:
> > On Tuesday 07 April 2009, Tom Malone wrote:
> >> The main problems we have with the current setup are the two Inbox
> >> folders in Horde and Thunderbird
> >
> > What exactely are the issues?
> > Note that with IMAP email can come in from almost any folder.
> > So having a folder called "Inbox" should be fine (in addition to the top
> > folder which could be displayed differently). We probably will change
> > Horde to behave in this respect.
>
> The issue is that Outlook with the Toltec connector would like mail to
> be deposited into the user INBOX folder.  It would then like to POP the
> mail out of that folder and sync it back to another folder INBOX/Inbox.
>
> In Outlook the user only has one Inbox where all mail is delivered.
> However, when the user then switches over to Horde the reality of the
> server is revealed.  The user will see two folders named Inbox.
>
> One Inbox has their mail from Outlook and the other Inbox has new mail
> that they have not seen.  This is VERY confusing to the user.

I think one important step is to point out the technical problem Outlook, 
Blackberry or other clients have here. With IMAP, any folder can contain 
fresh emails, any IMAP client must be ready to cope with it. However this is 
the mid and long term solution to switch to clients which are more IMAP 
ready. (E.g. Kontact on Windows.)

> In order to provide a view that is similar to Outlook the two Inbox
> folders would need to be combined in Horde.

Gunnar, we should plan for a configurable hack like this.
Even if this is only a short term solution as users will get confused if they 
are not ready to deal with incoming email in other folders, like one they 
have given from a functional account like sales at demo.kolab.org.

> This split Inbox also interferes with reading mail on a BlackBerry.
> BlackBerries are not full IMAP clients which means they are not able to
> see any folders other than an INBOX, Sent and Trash folder.  These
> folders also need to be at the same level on the IMAP server.  A
> BlackBerry is not able to address a folder INBOX/Inbox, INBOX/Sent or
> INBOX/Trash.
>
> Therefore, in order to user a BlackBerry with a Kolab server and the
> Toltec connector, in the standard configuration, a user would need to
> choose to either see new messages or their already seen messages.  The
> BlackBerries are my main reason for starting to go down the road of
> sub-folder mail delivery and altnamespace cyrus configurations.

Well client could be broken in several other aspects as well. This is sad, but 
it could lead to potentially unlimited things someone would need to provide.
Maybe a second account with a few only for the Blackberry would be an approach 
to hack around this.

> >> and email messages disappearing into
> >> Outlook, and out of the IMAP clients, only to reappear later when the
> >> connector syncs to the server.
> >
> > Once you know about the effect it should be okay, because as users you
> > are usually only using one client right now.
>
> Sadly, I must disagree with you on this point.  Users, at least in my
> experience, are more and more starting to read mail from different
> devices and programs in different locations.

I've meant that they are only using only client at a single spot in time.
So you are not having the blackberry on your left hand, the mouse for the web 
on your laptop in your right hand and the nose for typing outlook on the 
keyboard, which would consist of three clients being used simultaniously. ;)

Of course with shared folders, this might happen.

> Regrettably, my users see Exchange, BlackBerries and Outlook Web Access
> and are looking to me to provide an experience that approaches or
> exceeds Microsoft's.
>
> I am just trying to see if the collective wisdom of the group can give
> me any experience in this area.  It just might be that creative hacking
> can't get me around this problem and I will need to re-evaluate the
> configuration of a group of my users.

Yep, we try to help. 
Another idea: You could potentiall give the "mail.default" folder a different 
name. If you start up Outlook/Toltec in English, it will create a folder,
but if the folder is already created and has the right folder-type,
Toltec (and any other client) should honor it. Maybe this helps you with the 
modelling to not have INBOX/Inbox, but something else INBOX/abc to work with.

> On another note I have also been casually following the progress the
> OpenChange project has been making on their OpenChange MAPI server.  If
> their promises hold true I think that a Kolab server back end with an
> OpenChange server front end to Outlook could really make people stand up
> and take notice.

Maybe. My hope also is that a Free Software client like Kontact on Windows 
gets more users and a larger community. It can be controled much better. 
Accessing Outlook from outside (MAPI) or inside via plugin currently is a pain 
and probably will stay a pain as some things are fixed and cannot be changed
even when they are broken.



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-users/attachments/20090504/ddbe1ed0/attachment.bin

From ml at radoeka.nl  Mon May  4 22:41:04 2009
From: ml at radoeka.nl (Richard Bos)
Date: Mon, 4 May 2009 22:41:04 +0200
Subject: kolab on openSUSE natively is a little bit back
In-Reply-To: <20090504071528.98501fjvak0m2txc@www.inovox.de>
References: <200902142107.48113.ml@radoeka.nl>
	<200905021102.27738.ml@radoeka.nl>
	<20090504071528.98501fjvak0m2txc@www.inovox.de>
Message-ID: <200905042241.05035.ml@radoeka.nl>

Op maandag 04 mei 2009 07:15:28 schreef Carsten Burghardt:
> > Op zaterdag 02 mei 2009 03:14:08 schreef Thomas Spuhler:
> >> On Friday 01 May 2009, Richard Bos wrote:
> >> > Op donderdag 30 april 2009 21:41:23 schreef Carsten Burghardt:
> >> > > > What version of perl-ldap to you have? I found this link
> >> > > > https://www.intevation.de/roundup/kolab/issue1755
> >> > >
> >> > > Well, the version is perl-ldap-0.39-5.2 from the kolab suse
> >> > > repository but it does not contain the fix. Thanks for spotting
> >> > > this. I assume the package is too old.
> >> >
> >> > It's not.  I have the same and it is working fine.
> >> > kolab2:~ # rpm -q perl-ldap
> >> > perl-ldap-0.39-5.3
> >> >
> >> > At the moment I can't think of a reason why you can't start ldap.  I
> >> > believe I have seen the same thing, perhaps it is mentioned in
> >> > issue1755.
> >>
> >> you have -5.3 vs. -5.2
> >> different build but what else?
> >
> > That's a very minimal difference.  That number is added by the openSUSE
> > build service, when a build is restarted.  This might be triggered by a
> > package that
> > is needed as build dependency for the perl-ldap package.
>
> Well, I installed the package from the kolab suse repository and at  
> least on my system the patch is not included. Once I patched it  
> manually the cookie parsing problem was gone.

After investigating the package on the build service, it indeed misses the 
patch http://git.goingon.net/?p=perl-
ldap.git;a=blobdiff;f=lib/Net/LDAP/Control/SyncRequest.pm;h=d905d7bd1c7ee27c45a9609594fb89e3d9e8d63c;hp=95cd71634aa1c0704408d267a799bbc16915cda4;hb=3c5a803879e213ef146fad42f194e6f3568c6358;hpb=48fb4340597d60813f526a5a0217a36a04017d34
That one was created just after the 0.39 release.  I have updated the package 
on the build server, and is has been reported to work for openSUSE_10.3 in the 
meantime already.  Thanks Alar!

-- 
Richard



From ml at radoeka.nl  Mon May  4 22:44:44 2009
From: ml at radoeka.nl (Richard Bos)
Date: Mon, 4 May 2009 22:44:44 +0200
Subject: kolab - opensuse 11.1
In-Reply-To: <20090504093045.18112egfqsgwsbms@www.inovox.de>
References: <200904021301.32465.ml@radoeka.nl>
	<200905011511.49777.ml@radoeka.nl>
	<20090504093045.18112egfqsgwsbms@www.inovox.de>
Message-ID: <200905042244.44698.ml@radoeka.nl>

Hello Carsten,

Op maandag 04 mei 2009 09:30:45 schreef Carsten Burghardt:
> >> > > Apr  1 18:59:48 sft postfix/cleanup[7318]: B445B1AE1FD:
> >> > > message-id=<20090401225948.B445B1AE1FD at sft.hd.net>
> >> > > Apr  1 18:59:48 sft postfix/bounce[7321]: 83EE81AE1FA: sender
> >> > > non-delivery notification: B445B1AE1FD
> >> > > Apr  1 18:59:48 sft postfix/qmgr[7190]: B445B1AE1FD: from=<>,
> >> > > size=2243, nrcpt=1 (queue active)
> >> > > Apr  1 18:59:48 sft postfix/qmgr[7190]: 83EE81AE1FA: removed
> >> > > Apr  1 18:59:48 sft postfix/pipe[7323]: B445B1AE1FD:
> >> > > to=<sft at hd.net>, relay=kolabmailboxfilter, delay=0.11,
> >> > > delays=0.04/0.01/0/0.06, dsn=5.3.0, status=bounced (Command died
> >> > > with status 1:
> >> > > "/usr/bin/php5". Command output: Could not open input file:
> >> > > /usr/bin/kolabmailboxfilter )
> >> > > Apr  1 18:59:48 sft postfix/qmgr[7190]: B445B1AE1FD: removed
> >> > >
> >> > > What am I doing wrong?
> >> >
> >> > See questions as above, does the file exists
> >> > (/usr/bin/kolabmailboxfilter)
> >> >
> >> > # rpm -qf /usr/bin/kolabmailboxfilter
> >>
> >> Those files do not exist on my upgraded system (10.3). What package
> >> should include them?
> >
> > On 10.3 I think it is:
> > /var/lib/kolab/kolab-filter/kolabmailboxfilter.php, but that is a big
> > guess. If that is indeed the correct file, the package kolab-filter
> > provides it.
>
> The file you mentioned exists but in the pipe command it looks for  
> /usr/bin/kolabmailboxfilter. Should I create a link or change the  
> command? I assume this should also be changed in the package then?

Dunno, but it looks like you have to versions mixed.   If it is possible try 
to do a clean install of kolab.  AFAIK Alar has kolab-2.2.1 running 
successfully on openSUSE-10.3.

With Alar's help we have made very good progress and is now starting to work 
nicely on openSUSE.  There are still some things to be fixed, but the major 
components seem to be working fine and out of the box!

-- 
Richard



From ml at radoeka.nl  Mon May  4 22:49:46 2009
From: ml at radoeka.nl (Richard Bos)
Date: Mon, 4 May 2009 22:49:46 +0200
Subject: kolab on openSUSE natively is a little bit back
In-Reply-To: <200905042241.05035.ml@radoeka.nl>
References: <200902142107.48113.ml@radoeka.nl>
	<20090504071528.98501fjvak0m2txc@www.inovox.de>
	<200905042241.05035.ml@radoeka.nl>
Message-ID: <200905042249.46827.ml@radoeka.nl>

Op maandag 04 mei 2009 22:41:04 schreef Richard Bos:
> I have updated the package on the build server

You can find it in the devel:languages:perl repository:
http://download.opensuse.org/repositories/devel:/languages:/perl/openSUSE_10.3/repodata/
You need version 0.39-9.1 or higher!

-- 
Richard



From carsten at cburghardt.com  Tue May  5 00:21:40 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Tue, 5 May 2009 00:21:40 +0200
Subject: kolab - opensuse 11.1
In-Reply-To: <200905042244.44698.ml@radoeka.nl>
References: <200904021301.32465.ml@radoeka.nl>
	<20090504093045.18112egfqsgwsbms@www.inovox.de>
	<200905042244.44698.ml@radoeka.nl>
Message-ID: <200905050021.40442.carsten@cburghardt.com>

Am Montag, 4. Mai 2009 22:44:44 schrieben Sie:
> Hello Carsten,
>
> Op maandag 04 mei 2009 09:30:45 schreef Carsten Burghardt:
> > >> > > Apr  1 18:59:48 sft postfix/cleanup[7318]: B445B1AE1FD:
> > >> > > message-id=<20090401225948.B445B1AE1FD at sft.hd.net>
> > >> > > Apr  1 18:59:48 sft postfix/bounce[7321]: 83EE81AE1FA: sender
> > >> > > non-delivery notification: B445B1AE1FD
> > >> > > Apr  1 18:59:48 sft postfix/qmgr[7190]: B445B1AE1FD: from=<>,
> > >> > > size=2243, nrcpt=1 (queue active)
> > >> > > Apr  1 18:59:48 sft postfix/qmgr[7190]: 83EE81AE1FA: removed
> > >> > > Apr  1 18:59:48 sft postfix/pipe[7323]: B445B1AE1FD:
> > >> > > to=<sft at hd.net>, relay=kolabmailboxfilter, delay=0.11,
> > >> > > delays=0.04/0.01/0/0.06, dsn=5.3.0, status=bounced (Command died
> > >> > > with status 1:
> > >> > > "/usr/bin/php5". Command output: Could not open input file:
> > >> > > /usr/bin/kolabmailboxfilter )
> > >> > > Apr  1 18:59:48 sft postfix/qmgr[7190]: B445B1AE1FD: removed
> > >> > >
> > >> > > What am I doing wrong?
> > >> >
> > >> > See questions as above, does the file exists
> > >> > (/usr/bin/kolabmailboxfilter)
> > >> >
> > >> > # rpm -qf /usr/bin/kolabmailboxfilter
> > >>
> > >> Those files do not exist on my upgraded system (10.3). What package
> > >> should include them?
> > >
> > > On 10.3 I think it is:
> > > /var/lib/kolab/kolab-filter/kolabmailboxfilter.php, but that is a big
> > > guess. If that is indeed the correct file, the package kolab-filter
> > > provides it.
> >
> > The file you mentioned exists but in the pipe command it looks for
> > /usr/bin/kolabmailboxfilter. Should I create a link or change the
> > command? I assume this should also be changed in the package then?
>
> Dunno, but it looks like you have to versions mixed.   If it is possible
> try to do a clean install of kolab.  AFAIK Alar has kolab-2.2.1 running
> successfully on openSUSE-10.3.
>
> With Alar's help we have made very good progress and is now starting to
> work nicely on openSUSE.  There are still some things to be fixed, but the
> major components seem to be working fine and out of the box!

Kolab 2.2.0 had the following in the master.cf:
kolabfilter     unix  -       n       n       -       -       pipe user=kolab 
null_sender= argv=/usr/bin/php5
    -c /etc/php5/cli/php.ini
    -f /var/lib/kolab/kolab-filter/kolabfilter.php
    --
    -h @@@fqdnhostname@@@
    -s ${sender}
    -r ${recipient}
    -c ${client_address}
    -u ${sasl_username}

That was changed in 2.2.1 to:
kolabfilter     unix  -       n       n       -       -       pipe user=kolab 
null_sender= argv=/usr/bin/php5
    -c /etc/php5/cli/php.ini
    -f /usr/bin/kolabfilter
    --
    --host=@@@fqdnhostname@@@
    --sender=${sender}
    --recipient=${recipient}
    --client=${client_address}
    --user=${sasl_username}
    --config=/etc/kolab/filter/kolabfilter.conf

So I only need to know if I should change this back or enter something in the 
user profile. No big thing at all but seems to be a little missing piece.


Carsten




From carsten at cburghardt.com  Tue May  5 10:49:54 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Tue, 05 May 2009 10:49:54 +0200
Subject: Horde and Kolab on Suse
Message-ID: <20090505104954.393313pl3mbtlsqa@www.inovox.de>

Hi,

I am little bit confused by the packages and their dependencies for  
Horde together with Kolab 2.2.1 on my Suse (10.3) system. If I see  
this correct the "kolab-webclient" contains a complete Horde  
installation customized for Kolab. But the repository also contains a  
plain Horde installation. The strange thing is that some of the Kolab  
packages (e.g. filter or freebusy) depend on the Horde package so I  
also have to install this. But why? Isn't the kolab webclient enough?  
Thanks for any help.


Regards,

Carsten





From daniel.vergien at rrz.uni-hamburg.de  Tue May  5 16:18:22 2009
From: daniel.vergien at rrz.uni-hamburg.de (Daniel Vergien)
Date: Tue, 05 May 2009 16:18:22 +0200
Subject: Webclient SSL error
Message-ID: <4A004AAE.2050309@rrz.uni-hamburg.de>

Hi list,

when I try to access the webclient I get the following error message 
in Firefox:
ssl_error_rx_record_too_long - firefox 3.0.7 on windows xp
Data Transfer Interrupted - firefox 3.0.10 on solaris 10

The apache-error.log has the following entries:
Invalid method in request \x80O\x01\x03 - firefox from solaris
Invalid method in request \x16\x03\x01 - firefox from win xp

I had this problem once ago - I fixed it by deleting everything from 
/kolab/var/kolab/tmp/ but this time it doesn't help

Thanks in advance

Daniel



From ml at radoeka.nl  Tue May  5 22:31:07 2009
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 5 May 2009 22:31:07 +0200
Subject: kolab - opensuse 11.1
In-Reply-To: <200905050021.40442.carsten@cburghardt.com>
References: <200904021301.32465.ml@radoeka.nl>
	<200905042244.44698.ml@radoeka.nl>
	<200905050021.40442.carsten@cburghardt.com>
Message-ID: <200905052231.08716.ml@radoeka.nl>

Op dinsdag 05 mei 2009 00:21:40 schreef Carsten Burghardt:
> Kolab 2.2.0 had the following in the master.cf:
> kolabfilter     unix  -       n       n       -       -       pipe
> user=kolab null_sender= argv=/usr/bin/php5
>     -c /etc/php5/cli/php.ini
>     -f /var/lib/kolab/kolab-filter/kolabfilter.php
>     --
>     -h @@@fqdnhostname@@@
>     -s ${sender}
>     -r ${recipient}
>     -c ${client_address}
>     -u ${sasl_username}
>
> That was changed in 2.2.1 to:
> kolabfilter     unix  -       n       n       -       -       pipe
> user=kolab null_sender= argv=/usr/bin/php5
>     -c /etc/php5/cli/php.ini
>     -f /usr/bin/kolabfilter
>     --
>     --host=@@@fqdnhostname@@@
>     --sender=${sender}
>     --recipient=${recipient}
>     --client=${client_address}
>     --user=${sasl_username}
>     --config=/etc/kolab/filter/kolabfilter.conf
>
> So I only need to know if I should change this back or enter something in
> the user profile. No big thing at all but seems to be a little missing
> piece.


I have the same differences:

kolab2:/var/tmp # diff master.cf-2.2.0  /etc/postfix/master.cf-2.2.1
86c86                                                          
< kolabpolicy    unix  -       n       n       -       -       spawn user=kolab argv=/usr/share/kolab/scripts/kolab_smtpdpolicy 
---                                                                                                                             
> kolabpolicy    unix  -       n       n       -       -       spawn user=kolab argv=/usr/bin/kolab_smtpdpolicy                 
90c90                                                                                                                           
<     -f /var/lib/kolab/kolab-filter/kolabfilter.php                                                                            
---                                                                                                                             
>     -f /usr/bin/kolabfilter                                                                                                   

100c101
<     -f /var/lib/kolab/kolab-filter/kolabmailboxfilter.php
---
>     -f /usr/bin/kolabmailboxfilter


Both versions are working (email wise) for me.
Hope this helps.

-- 
Richard



From ml at radoeka.nl  Tue May  5 22:35:07 2009
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 5 May 2009 22:35:07 +0200
Subject: Horde and Kolab on Suse
In-Reply-To: <20090505104954.393313pl3mbtlsqa@www.inovox.de>
References: <20090505104954.393313pl3mbtlsqa@www.inovox.de>
Message-ID: <200905052235.08137.ml@radoeka.nl>

Hi Carsten,

Op dinsdag 05 mei 2009 10:49:54 schreef Carsten Burghardt:
> I am little bit confused by the packages and their dependencies for
> Horde together with Kolab 2.2.1 on my Suse (10.3) system. If I see
> this correct the "kolab-webclient" contains a complete Horde
> installation customized for Kolab. But the repository also contains a
> plain Horde installation. The strange thing is that some of the Kolab
> packages (e.g. filter or freebusy) depend on the Horde package so I
> also have to install this. But why? Isn't the kolab webclient enough?

That's indeed the way it is.  Kolab itself depends on the packages in 
/usr/share/php5/Horde and the webclient in /srv/www/htdocs/Horde.  That is 
because the way packaging horde has been setup.  We have to live with and the 
kolab developers and packagers have to deal with.  This is valid for horde3, 
horde4 that is being developed, will have better packaging support.
This is as far as I understand it, Alar, Gunnar, anybody else correct me if 
I'm wrong.

-- 
Richard



From LHendricks at austinent.com  Tue May  5 23:07:08 2009
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Tue, 5 May 2009 16:07:08 -0500 
Subject: migrating from exchange 5.5 to kolab 2.2.1 -- imapsync issue
Message-ID: <7907AE10BB50DD4F840E76527D27EF19029F63B6@entmail.domain.austinent.com>

I am now starting the transition from Exchange 5.5 to Kolab 2.2.1, and I
know imapsync is a 3rd party script, but hopefully someone has seen this or
can tell me if it just isn't going to work.

Per the kolab wiki I attempted to use imapsync with the suggested command
(substituting my user login and password information for each server):

imapsync --host1 exchange --noauthmd5 --user1 "$u1" --password1 "$p1" \
         --host2 kolab    --user2 "$u2" --password2 "$p2" \
         --regextrans2 's/INBOX.INBOX/INBOX/'

First it gives permission denied errors for all the folders not inside the
inbox which I understand.

Then it seems to be connecting to each server and finds emails to sync, but
when it begins to try and copy messages, the below errors occur:


From bernhard at intevation.de  Wed May  6 10:25:13 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 6 May 2009 10:25:13 +0200
Subject: Kontact Windows client - questions (url handler; spelling)
In-Reply-To: <20090312203931.GA553@sonic.net>
References: <20090312203931.GA553@sonic.net>
Message-ID: <200905061025.13570.bernhard@intevation.de>

Marc,

again thanks for giving our beta version a spin on windows 
and for reporting back.

Am Donnerstag, 12. M?rz 2009 21:39:34 schrieb kolab-marc at fieldinternet.com:
> I am using Kontact Version 1.3 (enterprise4 0.20090220.928360) Windows. ?I
> have two questions:

> 2. How to I set up spell checking for kmail? ?When I use Tools:Spelling in
> the compose window, it does not actually check anything. ?Also, I do not
> see the spelling settings that (I think) are present in kmail on Linux in
> the composer settings.

Our development team has "rebased" our enterprise branchto profit form the 
latest kde 4.2 improvements in the core libraries. Spell checking should work 
with the freshest development version.
(Note our pipeline of quality control may or may not release a version before 
this which currently is in testing.)

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-users/attachments/20090506/63cd8f95/attachment.bin

From bernhard at intevation.de  Wed May  6 10:31:50 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 6 May 2009 10:31:50 +0200
Subject: Webclient SSL error
In-Reply-To: <4A004AAE.2050309@rrz.uni-hamburg.de>
References: <4A004AAE.2050309@rrz.uni-hamburg.de>
Message-ID: <200905061031.51092.bernhard@intevation.de>

Am Dienstag, 5. Mai 2009 16:18:22 schrieb Daniel Vergien:
> when I try to access the webclient I get the following error message
> in Firefox:
> ssl_error_rx_record_too_long - firefox 3.0.7 on windows xp
> Data Transfer Interrupted - firefox 3.0.10 on solaris 10

Did you try other webbrowsers? Did you try the admin interface?
 I am asking because I wonder if this is a special or more general problem of 
your setup.

Which version of Kolab Server are you using precisely on which hardware 
platform?

> The apache-error.log has the following entries:
> Invalid method in request \x80O\x01\x03 - firefox from solaris
> Invalid method in request \x16\x03\x01 - firefox from win xp
>
> I had this problem once ago - I fixed it by deleting everything from
> /kolab/var/kolab/tmp/ but this time it doesn't help

 You could try searching for this on the internet, if this is a special 
openssl <-> apache <-> firefox problem on your platforms.

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-users/attachments/20090506/d86d8dee/attachment.bin

From daniel.vergien at rrz.uni-hamburg.de  Wed May  6 12:03:05 2009
From: daniel.vergien at rrz.uni-hamburg.de (Daniel Vergien)
Date: Wed, 06 May 2009 12:03:05 +0200
Subject: Webclient SSL error
In-Reply-To: <200905061031.51092.bernhard@intevation.de>
References: <4A004AAE.2050309@rrz.uni-hamburg.de>
	<200905061031.51092.bernhard@intevation.de>
Message-ID: <4A016059.4000306@rrz.uni-hamburg.de>

On 05/06/09 10:31 AM, Bernhard Reiter wrote:
 > Am Dienstag, 5. Mai 2009 16:18:22 schrieb Daniel Vergien:
 >> when I try to access the webclient I get the following error message
 >> in Firefox:
 >> ssl_error_rx_record_too_long - firefox 3.0.7 on windows xp
 >> Data Transfer Interrupted - firefox 3.0.10 on solaris 10
 >
 > Did you try other webbrowsers? Did you try the admin interface?
 >  I am asking because I wonder if this is a special or more general 
problem of
 > your setup.
 >
IE  7.0.5730.13 on XP-pro: "Die Webseite kann nicht angezeigt werden"
apache-error.log: Invalid method in request \x16\x03\x01

 > Which version of Kolab Server are you using precisely on which 
hardware
 > platform?

It's kolab 2.2.0 in a Solaris 10 zone on x86.

The point is: it worked up till I hard powered the machine off.

 >  You could try searching for this on the internet, if this is a 
special
 > openssl <-> apache <-> firefox problem on your platforms.

If done that: it always comes up to that there is something miss 
configured in the apache.conf - but I've not touched it. I also 
rebuilded it with kolabconf - but it does not help.

Daniel



From carsten at cburghardt.com  Thu May  7 10:48:34 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Thu, 07 May 2009 10:48:34 +0200
Subject: Upgrade on Suse 10.3 success
Message-ID: <20090507104834.17243gznb3z61eas@www.inovox.de>

Hi,

after a lot of tests on a virtual system I finally upgraded my  
productive Kolab server to 2.2.1 with the Suse packages.
Short description:
- Save ldap data according to readme (slapcat)
- rckolab stop
- add Kolab devel (see http://en.opensuse.org/Kolab) and Perl devel  
(http://download.opensuse.org/repositories/devel:/languages:/perl/openSUSE_10.3) installation  
sources
- update all Kolab, Horde, PHP and Perl packages with Yast
- restore .rpmnew files from /etc/kolab/templates (if you made changes)
- do the same for Horde if needed
- restore ldap data according to readme (slapadd)
- rcldap start
- kolabconf -n
- rckolab start
- change ownership of Horde config dirs and files to wwwrun

That's it. So far I tested email, calendar, tasks, contacts and syncml  
support, all work. I have not tested freebusy and shared calendars yet.

I am currently not able to save the Horde config as administrator  
because this replaces the __FILE__ macros with an actual path but that  
does not seem to work as Horde can not find the database anymore.


Regards

Carsten



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



From stive at polarnet.hu  Thu May  7 11:57:59 2009
From: stive at polarnet.hu (=?UTF-8?Q?G=C3=A1bor_Istv=C3=A1n?=)
Date: Thu, 07 May 2009 11:57:59 +0200
Subject: email cn is not uniq
Message-ID: <d4bebc2c843a27d2d04b4ef2b1f46918@polarnet.hu>

Hi!

I newbe in the kolab. Now I installing a server. 
But I have a problem. When I create a new user in the kolab webadmin
interface, then is the rdn the user's real name. But this is not unique id.
Because it can 2 people same name. So my question can I change that a
unique id for example primary email as the distribution list.

-- 
G?bor Istv?n
rendszergazda
Polarnet kft



From bernat at nan-tic.com  Thu May  7 12:46:59 2009
From: bernat at nan-tic.com (Bernat Brunet)
Date: Thu, 7 May 2009 12:46:59 +0200
Subject: kolab + mailman
Message-ID: <200905071246.59667.bernat@nan-tic.com>

Hi!

first of all sorry for my english.

I'm novice in the kolab. I have installed and running correctly. now I have 
installed the mailman and I would like to use it with the kolab, so I followed 
the instructions that are in the wiki 
(http://wiki.kolab.org/index.php/Kolab2_Integration_with_mailman) all seems go 
correctly, but when I try to enter in the mailman admin page it's return me an 
error:


Mailman CGI error!!!
The Mailman CGI wrapper encountered a fatal error. This entry is being stored 
in your syslog:

Group mismatch error.  Mailman expected the CGI
wrapper script to be executed as group "www-data", but
the system's web server executed the CGI script as
group "kolab-n".  Try tweaking the web server to run the
script as group "www-data", or re-run configure, 
providing the command line option `--with-cgi-gid=kolab-n'.


but in this case I don't know exactly why it appears, because I have made the 
compilation with the "cgi-gid" changed, and replaced the mailman bin, like the 
wiki explain.

any one know what may happen? would be better install the mailman throw the 
tar package? I have to restart something special?

well, I have the kolab 2.2.0 on a debian lenny. the kolab is installed throw 
the script, not the deb packages. the mail man is installed throw deb packages 
and is the 2.1.11 version. I have download the mailman tar 2.1.11 for the new 
configuration.

thanks for the help,

bernat



From aspineux at gmail.com  Thu May  7 13:34:45 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Thu, 7 May 2009 13:34:45 +0200
Subject: Kolab 2.2.1 : ERROR openpkg-20071227-20071227_kolab1.src.sh: No 
	such file or directory
In-Reply-To: <20090409080238.GA5149.thomas@intevation.de>
References: <71fe4e760904080918ga1ad281ubad77f0268f68a9b@mail.gmail.com>
	<20090409080238.GA5149.thomas@intevation.de>
Message-ID: <71fe4e760905070434j11fd2ae5wc5ecdbf6dfbb85b1@mail.gmail.com>

On Thu, Apr 9, 2009 at 10:02 AM, Thomas Arendsen Hein
<thomas at intevation.de> wrote:
> * Alain Spineux <aspineux at gmail.com> [20090408 18:18]:
>> I get an error trying to install new kolab 2.2.1,
>> But in fact, I got the same trying to reinstall old 2.2.0 that was
>> instaled previously !
>> Then this was not a probleme with the source but with the target :-)
>>
>> Received no instructions. Trying to determine required action...
>> sh: ./openpkg-20071227-20071227.src.sh
>> ./openpkg-20071227-20071227_kolab1.src.sh: No such file or directory
>
> I think you have both, openpkg-20071227-20071227.src.sh and
> ./openpkg-20071227-20071227_kolab1.src.sh, in the installation
> directory. Please delete the older one.

No, I dont, only openpkg-20071227-20071227.src.sh

Sorry for the long delay :-)

>
> 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
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



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



From aspineux at gmail.com  Thu May  7 13:56:59 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Thu, 7 May 2009 13:56:59 +0200
Subject: migrating from exchange 5.5 to kolab 2.2.1 -- imapsync issue
In-Reply-To: <7907AE10BB50DD4F840E76527D27EF19029F63B6@entmail.domain.austinent.com>
References: <7907AE10BB50DD4F840E76527D27EF19029F63B6@entmail.domain.austinent.com>
Message-ID: <71fe4e760905070456o44389675ha374f7ac9e6dd6bc@mail.gmail.com>

On Tue, May 5, 2009 at 11:07 PM, Lucas Hendricks
<LHendricks at austinent.com> wrote:
> I am now starting the transition from Exchange 5.5 to Kolab 2.2.1, and I
> know imapsync is a 3rd party script, but hopefully someone has seen this or
> can tell me if it just isn't going to work.
>
> Per the kolab wiki I attempted to use imapsync with the suggested command
> (substituting my user login and password information for each server):
>
> imapsync --host1 exchange --noauthmd5 --user1 "$u1" --password1 "$p1" \
> ? ? ? ? --host2 kolab ? ?--user2 "$u2" --password2 "$p2" \
> ? ? ? ? --regextrans2 's/INBOX.INBOX/INBOX/'
>
> First it gives permission denied errors for all the folders not inside the
> inbox which I understand.
>
> Then it seems to be connecting to each server and finds emails to sync, but
> when it begins to try and copy messages, the below errors occur:
>
> From Folder [INBOX]
> To ? Folder [INBOX]
> + NO msg #13626 [fEB0wcz6JEyY7+tHduu0ag:143468] in INBOX
> + Copying msg #13626:143468 to folder INBOX
> flags from : [\Seen][]
> Couldn't append msg #13626 (Subject:[RE: oops]) to folder INBOX: Error
> sending command '23 APPEND INBOX (\Seen) "" {143468}':

'23 APPEND INBOX (\Seen) "" {143468}':
dont look the be the correct syntax

I have more the use of something like
'23 APPEND INBOX {143468}'


> + NO msg #13636 [iQ0F+l7aXbj3Gv3I60msug:1279] in INBOX
> + Copying msg #13636:1279 to folder INBOX
> flags from : [\Seen][]
> Couldn't append msg #13636 (Subject:[RE: oops]) to folder INBOX: Error
> sending command '24 APPEND INBOX (\Seen) "" {1279}':
>

You could activate cyrus telemetry logging (search google for more,
and dont forget to chmod the directory :-)
and check the log for more info

>
> Thanks,
> Lucas Hendricks
> AENTC IT Support
>
> P.S. if this is fixable the next thing I'll be searching for is a way to do
> this without knowing all the individual user passwords.

On the cyrus side no probleme, use your "manager" credential, but on
the exchnage side, I dont know if Administrator credential will work.

> Something like an
> ldif I've read about, but if someone wants to toss me to a link with
> info/walkthroughs that they have sitting around that would be super helpful,
> thanks!
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



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



From ml at radoeka.nl  Thu May  7 17:35:57 2009
From: ml at radoeka.nl (Richard Bos)
Date: Thu, 7 May 2009 17:35:57 +0200
Subject: email cn is not uniq
In-Reply-To: <d4bebc2c843a27d2d04b4ef2b1f46918@polarnet.hu>
References: <d4bebc2c843a27d2d04b4ef2b1f46918@polarnet.hu>
Message-ID: <200905071735.58345.ml@radoeka.nl>

Hello G?bor,

Op donderdag 07 mei 2009 11:57:59 schreef G?bor Istv?n:
> But I have a problem. When I create a new user in the kolab webadmin
> interface, then is the rdn the user's real name. But this is not unique id.
> Because it can 2 people same name. 

This is a known issue, and it will probably addresses in the next major kolab 
upgrade (kolab-3).  You should search the wiki (http://wiki.kolab.org/) and/or 
the issue tracker https://www.intevation.de/roundup/kolab/ to find issues 
about this.

> So my question can I change that a
> unique id for example primary email as the distribution list.

The issue regarding this subject in the tracker (if you find it), may provide 
more information about this.

-- 
Richard



From lucidblue0 at gmail.com  Thu May  7 18:05:49 2009
From: lucidblue0 at gmail.com (Lucid Blue)
Date: Thu, 7 May 2009 09:05:49 -0700
Subject: Upgrade on Suse 10.3 success
In-Reply-To: <20090507104834.17243gznb3z61eas@www.inovox.de>
References: <20090507104834.17243gznb3z61eas@www.inovox.de>
Message-ID: <4cd66e520905070905u4f65adf0hd344eb62c3ad111f@mail.gmail.com>

On Thu, May 7, 2009 at 1:48 AM, Carsten Burghardt
<carsten at cburghardt.com> wrote:
> Hi,
>
> after a lot of tests on a virtual system I finally upgraded my
> productive Kolab server to 2.2.1 with the Suse packages.
> Short description:
> - Save ldap data according to readme (slapcat)
> - rckolab stop
> - add Kolab devel (see http://en.opensuse.org/Kolab) and Perl devel
> (http://download.opensuse.org/repositories/devel:/languages:/perl/openSUSE_10.3) installation
> sources
> - update all Kolab, Horde, PHP and Perl packages with Yast
> - restore .rpmnew files from /etc/kolab/templates (if you made changes)
> - do the same for Horde if needed
> - restore ldap data according to readme (slapadd)
> - rcldap start
> - kolabconf -n
> - rckolab start
> - change ownership of Horde config dirs and files to wwwrun
>
> That's it. So far I tested email, calendar, tasks, contacts and syncml
> support, all work. I have not tested freebusy and shared calendars yet.
>
> I am currently not able to save the Horde config as administrator
> because this replaces the __FILE__ macros with an actual path but that
> does not seem to work as Horde can not find the database anymore.
>
>
> Regards
>
> Carsten
>
>

I've VERY interested in this, I'd tried a few times, I'm using SUSE
10.2 and "versions" in the web interface gives me this output:

perl-kolab-5.8.7-30.8
kolab-2.1.0-31.1
kolab-resource-handlers-2.1.0-10.7
kolab-webadmin-2.1.0-5.7

I would love the "Long Description" if you have the time.  I haven't
had the time to mess with it in a while and currently it's working.  I
vaguely remember getting some annotations.db errors and I thought I'd
read that the DB format had changed, now I'm thinking that it's likely
I wasn't following the proper steps.

I have however successfully migrated the data and mail to a fresh 10.3
install, but a huge issue I have with that is that we are using Toltec
and per Joon, there is no way to 'copy' the Folder UID's, meaning that
any shared folders would come in as new or duplicate the messages
already contained within them on the outlook clients.

What clients are you using?

-- I'm new to mailing lists, I'm not sure the polite way to do this,
I've put my reply at the bottom and did a Reply All, please let me
know if I should be doing this differently...

Thanks,
-Skip



From LHendricks at austinent.com  Thu May  7 18:38:39 2009
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Thu, 7 May 2009 11:38:39 -0500 
Subject: migrating from exchange 5.5 to kolab 2.2.1 -- imapsync issue 
	(resolved)
Message-ID: <7907AE10BB50DD4F840E76527D27EF19029F6459@entmail.domain.austinent.com>

The below attempt was done with the latest Mail::IMAPClient module for perl.
The error persisted even when attempting to use imapsync from one Kolab
mailbox to another using imapsync 1.99 and Mail::IMAPClient 3.16.

I reverted to the version of Mail::IMAPClient required by the imapsync and
it began to sync emails great using imapsync 1.99 and Mail::IMAPClient
2.2.9.

I'll try to update the wiki once my email verification comes =).

Lucas

-----Original Message-----
From: Lucas Hendricks 
Sent: Tuesday, May 05, 2009 4:07 PM
To: Kolab Users List
Subject: migrating from exchange 5.5 to kolab 2.2.1 -- imapsync issue

I am now starting the transition from Exchange 5.5 to Kolab 2.2.1, and I
know imapsync is a 3rd party script, but hopefully someone has seen this or
can tell me if it just isn't going to work.

Per the kolab wiki I attempted to use imapsync with the suggested command
(substituting my user login and password information for each server):

imapsync --host1 exchange --noauthmd5 --user1 "$u1" --password1 "$p1" \
         --host2 kolab    --user2 "$u2" --password2 "$p2" \
         --regextrans2 's/INBOX.INBOX/INBOX/'

First it gives permission denied errors for all the folders not inside the
inbox which I understand.

Then it seems to be connecting to each server and finds emails to sync, but
when it begins to try and copy messages, the below errors occur:


From LHendricks at austinent.com  Thu May  7 20:03:54 2009
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Thu, 7 May 2009 13:03:54 -0500 
Subject: Kolab authenticating through Active Directory (Windows AD)
Message-ID: <7907AE10BB50DD4F840E76527D27EF19029F6466@entmail.domain.austinent.com>

I have been digging around for the next step in integrating our network with
Kolab which would be to have Kolab authenticate against our windows domain.
I have been digging in the wiki and around the web, but this is the closest
thing I've found from the list in 2004: 

http://www.kolab.org/pipermail/kolab-users/2004-April/000081.html

Given how old that message is, I was wondering if this has been
sophisticated since then, or if it's even still valid in Kolab 2.2.1.  It
was considered experimental and undocumented in April 2004.

I'll be glad to make a wiki page for it once I find out how to do it.  I'm
sure I can one way or another.  I don't necessarily need Kolab to
automatically create mailboxes, I just want it to authenticate the password
against the AD which seems like it should not be too complicated (it might
even be as simple as changing the ldap servers in the sasl.conf.template to
point to an AD server?

Thanks,
Lucas



From wrobel at pardus.de  Thu May  7 21:29:31 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 07 May 2009 21:29:31 +0200
Subject: Webclient SSL error
In-Reply-To: <4A016059.4000306@rrz.uni-hamburg.de>
References: <4A004AAE.2050309@rrz.uni-hamburg.de>
	<200905061031.51092.bernhard@intevation.de>
	<4A016059.4000306@rrz.uni-hamburg.de>
Message-ID: <20090507212931.178576vxy1utg5ss@webmail.pardus.de>

Quoting Daniel Vergien <daniel.vergien at rrz.uni-hamburg.de>:

> On 05/06/09 10:31 AM, Bernhard Reiter wrote:
>  > Am Dienstag, 5. Mai 2009 16:18:22 schrieb Daniel Vergien:
>  >> when I try to access the webclient I get the following error message
>  >> in Firefox:
>  >> ssl_error_rx_record_too_long - firefox 3.0.7 on windows xp
>  >> Data Transfer Interrupted - firefox 3.0.10 on solaris 10
>  >
>  > Did you try other webbrowsers? Did you try the admin interface?
>  >  I am asking because I wonder if this is a special or more general
> problem of
>  > your setup.
>  >
> IE  7.0.5730.13 on XP-pro: "Die Webseite kann nicht angezeigt werden"
> apache-error.log: Invalid method in request x16x03x01
>
>  > Which version of Kolab Server are you using precisely on which
> hardware
>  > platform?
>
> It's kolab 2.2.0 in a Solaris 10 zone on x86.
>
> The point is: it worked up till I hard powered the machine off.

There is nothing else listening on the kolab apache ports now?

http://bug.gd/search/details/69648/ssl_error_rx_record_too_long

hints at some possible problems in that area.

Cheers,

Gunnar

>
>  >  You could try searching for this on the internet, if this is a
> special
>  > openssl <-> apache <-> firefox problem on your platforms.
>
> If done that: it always comes up to that there is something miss
> configured in the apache.conf - but I've not touched it. I also
> rebuilded it with kolabconf - but it does not help.
>
> Daniel
>
> _______________________________________________
> 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 <<
--------------------------------------------------------------------


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

From wrobel at pardus.de  Thu May  7 21:43:23 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 07 May 2009 21:43:23 +0200
Subject: Horde and Kolab on Suse
In-Reply-To: <200905052235.08137.ml@radoeka.nl>
References: <20090505104954.393313pl3mbtlsqa@www.inovox.de>
	<200905052235.08137.ml@radoeka.nl>
Message-ID: <20090507214323.780172tec4gkt6fw@webmail.pardus.de>

Quoting Richard Bos <ml at radoeka.nl>:

> Hi Carsten,
>
> Op dinsdag 05 mei 2009 10:49:54 schreef Carsten Burghardt:
>> I am little bit confused by the packages and their dependencies for
>> Horde together with Kolab 2.2.1 on my Suse (10.3) system. If I see
>> this correct the "kolab-webclient" contains a complete Horde
>> installation customized for Kolab. But the repository also contains a
>> plain Horde installation. The strange thing is that some of the Kolab
>> packages (e.g. filter or freebusy) depend on the Horde package so I
>> also have to install this. But why? Isn't the kolab webclient enough?
>
> That's indeed the way it is.  Kolab itself depends on the packages in
> /usr/share/php5/Horde and the webclient in /srv/www/htdocs/Horde.  That is
> because the way packaging horde has been setup.  We have to live with and the
> kolab developers and packagers have to deal with.  This is valid for horde3,
> horde4 that is being developed, will have better packaging support.
> This is as far as I understand it, Alar, Gunnar, anybody else correct me if
> I'm wrong.

Yes, Horde 4 will be PEAR packages only. This means that you have most  
of the code in standard library locations (/usr/share/php or something  
like that) and probably not much more than a handfull of PHP scripts  
in the actual web area.

I recently packaged Koward this way and it worked great. Actually  
there is only one PHP file left in the document root  
(http://cvs.horde.org/co.php/koward/www/htdocs/koward/koward.php?rt=horde-hatchery&r=52e4832afedf0222dec06bf659d777ca49e9a8d1). All other stuff is static (css,  
images).

Cheers,

Gunnar

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



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

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


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

From ml at radoeka.nl  Thu May  7 21:48:48 2009
From: ml at radoeka.nl (Richard Bos)
Date: Thu, 7 May 2009 21:48:48 +0200
Subject: Upgrade on Suse 10.3 success
In-Reply-To: <20090507104834.17243gznb3z61eas@www.inovox.de>
References: <20090507104834.17243gznb3z61eas@www.inovox.de>
Message-ID: <200905072148.51890.ml@radoeka.nl>

Hi Carsten,

Op donderdag 07 mei 2009 10:48:34 schreef Carsten Burghardt:
> after a lot of tests on a virtual system I finally upgraded my  
> productive Kolab server to 2.2.1 with the Suse package

that's nice to read! :)

> That's it. So far I tested email, calendar, tasks, contacts and syncml  
> support, all work. I have not tested freebusy and shared calendars yet.
>
> I am currently not able to save the Horde config as administrator  
> because this replaces the __FILE__ macros with an actual path but that  
> does not seem to work as Horde can not find the database anymore.

Hopefully, you get this tested soon.  In case something is to be patched, 
please let us know!

-- 
Richard



From wrobel at pardus.de  Thu May  7 21:53:28 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 07 May 2009 21:53:28 +0200
Subject: trouble logging into horde
In-Reply-To: <200904140027.40133.sunil@khiatani.ath.cx>
References: <200904140027.40133.sunil@khiatani.ath.cx>
Message-ID: <20090507215328.29131wci9adgib0g@webmail.pardus.de>


Quoting Sunil Khiatani <sunil at khiatani.ath.cx>:

> Hi,
>
> I recently upgraded to horde 2.2.1, but i can no longer log
> into the horde webclient.  I'm not sure where to look for logs and what to do
> next.
>
> When I log in with the correct username and password, I get
> returned to the login page with no errors.

Do you have the correct cookie domain in the horde configuration?  
Maybe any old configuration files lying around in the horde  
configuration directory? Are the permissions on the log, tmp and  
storage directories in the horde installation set correctly (they must  
be owned by kolab-n)?

Cheers,

Gunnar

>
> I'm using a debian lenny server and installed the packages
> using openpkg.  I also do not  have libnss-db installed so there are  
> no conflicts
> with the libraries, and I am able to log into fbview's website fine too.
>
> Attached is my install log. Any help will be appreciated.

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

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

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

From wrobel at pardus.de  Thu May  7 22:02:08 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 07 May 2009 22:02:08 +0200
Subject: kolab + mailman
In-Reply-To: <200905071246.59667.bernat@nan-tic.com>
References: <200905071246.59667.bernat@nan-tic.com>
Message-ID: <20090507220208.2013745zo9qv75cs@webmail.pardus.de>

Quoting Bernat Brunet <bernat at nan-tic.com>:

> Hi!
>
> first of all sorry for my english.
>
> I'm novice in the kolab. I have installed and running correctly. now I have
> installed the mailman and I would like to use it with the kolab, so  
> I followed
> the instructions that are in the wiki
> (http://wiki.kolab.org/index.php/Kolab2_Integration_with_mailman)  
> all seems go
> correctly, but when I try to enter in the mailman admin page it's  
> return me an
> error:
>
>
> Mailman CGI error!!!
> The Mailman CGI wrapper encountered a fatal error. This entry is being stored
> in your syslog:
>
> Group mismatch error.  Mailman expected the CGI
> wrapper script to be executed as group "www-data", but
> the system's web server executed the CGI script as
> group "kolab-n".  Try tweaking the web server to run the
> script as group "www-data", or re-run configure,
> providing the command line option `--with-cgi-gid=kolab-n'.
>
>
> but in this case I don't know exactly why it appears, because I have made the
> compilation with the "cgi-gid" changed, and replaced the mailman  
> bin, like the
> wiki explain.

It definitely looks like the option --with-cgi-gid=kolab-n did not  
take any effect. Does the configure script give you anything related  
to this specific option?

Cheers,

Gunnar

>
> any one know what may happen? would be better install the mailman throw the
> tar package? I have to restart something special?
>
> well, I have the kolab 2.2.0 on a debian lenny. the kolab is installed throw
> the script, not the deb packages. the mail man is installed throw  
> deb packages
> and is the 2.1.11 version. I have download the mailman tar 2.1.11 for the new
> configuration.
>
> thanks for the help,
>
> bernat
>
> _______________________________________________
> 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 <<
--------------------------------------------------------------------


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

From daniel.vergien at rrz.uni-hamburg.de  Thu May  7 22:30:22 2009
From: daniel.vergien at rrz.uni-hamburg.de (Daniel Vergien)
Date: Thu, 07 May 2009 22:30:22 +0200
Subject: Webclient SSL error
In-Reply-To: <20090507212931.178576vxy1utg5ss@webmail.pardus.de>
References: <4A004AAE.2050309@rrz.uni-hamburg.de>	<200905061031.51092.bernhard@intevation.de>	<4A016059.4000306@rrz.uni-hamburg.de>
	<20090507212931.178576vxy1utg5ss@webmail.pardus.de>
Message-ID: <4A0344DE.7040206@rrz.uni-hamburg.de>

On 05/07/09 09:29 PM, Gunnar Wrobel wrote:

> There is nothing else listening on the kolab apache ports now?
> 
No

> http://bug.gd/search/details/69648/ssl_error_rx_record_too_long
> 
> hints at some possible problems in that area.

It's working again, but I don't know why. I changed _default_ to my 
FQDN to see if somethings changed - but no.
Then to reset the change I ran kolabconf - and this time it took 
longer time then before and everything works again. Too bad that I 
don't have a copy of the nonworking version, but next time i get a 
hard power off I will make a copy before trying this again.

Daniel



From carsten at cburghardt.com  Thu May  7 23:28:49 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Thu, 07 May 2009 23:28:49 +0200
Subject: Upgrade on Suse 10.3 success
In-Reply-To: <200905072148.51890.ml@radoeka.nl>
References: <20090507104834.17243gznb3z61eas@www.inovox.de>
	<200905072148.51890.ml@radoeka.nl>
Message-ID: <4A035291.9000106@cburghardt.com>

Richard Bos schrieb:
> Hi Carsten,
>
> Op donderdag 07 mei 2009 10:48:34 schreef Carsten Burghardt:
>   
>> after a lot of tests on a virtual system I finally upgraded my  
>> productive Kolab server to 2.2.1 with the Suse package
>>     
>
> that's nice to read! :)
>
>   
>> That's it. So far I tested email, calendar, tasks, contacts and syncml  
>> support, all work. I have not tested freebusy and shared calendars yet.
>>
>> I am currently not able to save the Horde config as administrator  
>> because this replaces the __FILE__ macros with an actual path but that  
>> does not seem to work as Horde can not find the database anymore.
>>     
>
> Hopefully, you get this tested soon.  In case something is to be patched, 
> please let us know!
>   
The reason for the error is rather simple. You have something like this 
in the Horde config:
$conf['tmpdir'] = dirname(__FILE__) . '/../tmp/';

If that is opened during runtime the dirname is replaced with the config 
directory so it works. But if you open the Horde configuration page and 
have a look at the setting the dirname is replaced with 
/srv/www/htdocs/client/lib/Horde/. I assume this is because the 
config.php is included. So the replaced path that shows up is 
/srv/www/htdocs/client/lib/Horde/../tmp/ and that is wrong. When you 
save the configuration the wrong path is include. Why don't you use the 
kolab functionality to insert the path to Horde here?


Carsten

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20090507/9d4af480/attachment.html

From aspineux at gmail.com  Fri May  8 01:21:01 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Fri, 8 May 2009 01:21:01 +0200
Subject: Kolab authenticating through Active Directory (Windows AD)
In-Reply-To: <7907AE10BB50DD4F840E76527D27EF19029F6466@entmail.domain.austinent.com>
References: <7907AE10BB50DD4F840E76527D27EF19029F6466@entmail.domain.austinent.com>
Message-ID: <71fe4e760905071621x3c036136i1f850016c4a8d0c9@mail.gmail.com>

On Thu, May 7, 2009 at 8:03 PM, Lucas Hendricks
<LHendricks at austinent.com> wrote:
> I have been digging around for the next step in integrating our network with
> Kolab which would be to have Kolab authenticate against our windows domain.
> I have been digging in the wiki and around the web, but this is the closest
> thing I've found from the list in 2004:
>
> http://www.kolab.org/pipermail/kolab-users/2004-April/000081.html

Another idea :

use pwdump to extract lanman password from your windows SAM.

http://www.openwall.com/passwords/microsoft-windows-nt-2000-xp-2003-vista

compile openldap to support lanman password
sync your window password into your ldap

I I did it for one user, it works ! But I have no scripts to automate
the job :-(






>
> Given how old that message is, I was wondering if this has been
> sophisticated since then, or if it's even still valid in Kolab 2.2.1. ?It
> was considered experimental and undocumented in April 2004.
>
> I'll be glad to make a wiki page for it once I find out how to do it. ?I'm
> sure I can one way or another. ?I don't necessarily need Kolab to
> automatically create mailboxes, I just want it to authenticate the password
> against the AD which seems like it should not be too complicated (it might
> even be as simple as changing the ldap servers in the sasl.conf.template to
> point to an AD server?
>
> Thanks,
> Lucas
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



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



From bernat at nan-tic.com  Fri May  8 08:04:17 2009
From: bernat at nan-tic.com (Bernat Brunet)
Date: Fri, 8 May 2009 08:04:17 +0200
Subject: kolab + mailman
In-Reply-To: <20090507220208.2013745zo9qv75cs@webmail.pardus.de>
References: <200905071246.59667.bernat@nan-tic.com>
	<20090507220208.2013745zo9qv75cs@webmail.pardus.de>
Message-ID: <200905080804.17349.bernat@nan-tic.com>

El Dijous, 7 de maig de 2009 22:02:08 Gunnar Wrobel va escriure:
> Quoting Bernat Brunet <bernat at nan-tic.com>:
> > Hi!
> >
> > first of all sorry for my english.
> >
> > I'm novice in the kolab. I have installed and running correctly. now I
> > have installed the mailman and I would like to use it with the kolab, so
> > I followed
> > the instructions that are in the wiki
> > (http://wiki.kolab.org/index.php/Kolab2_Integration_with_mailman)
> > all seems go
> > correctly, but when I try to enter in the mailman admin page it's
> > return me an
> > error:
> >
> >
> > Mailman CGI error!!!
> > The Mailman CGI wrapper encountered a fatal error. This entry is being
> > stored in your syslog:
> >
> > Group mismatch error.  Mailman expected the CGI
> > wrapper script to be executed as group "www-data", but
> > the system's web server executed the CGI script as
> > group "kolab-n".  Try tweaking the web server to run the
> > script as group "www-data", or re-run configure,
> > providing the command line option `--with-cgi-gid=kolab-n'.
> >
> >
> > but in this case I don't know exactly why it appears, because I have made
> > the compilation with the "cgi-gid" changed, and replaced the mailman bin,
> > like the
> > wiki explain.
>
> It definitely looks like the option --with-cgi-gid=kolab-n did not
> take any effect.

yes, it seems like that. but I have used the:

./configure --with-username=list --with-groupname=list --with-mail-gid=kolab-n --
without-permcheck --prefix=/var/lib/mailman --with-cgi-gid=kolab-n

in the output appear that:

[...]
checking permissions on /var/lib/mailman... skipped                                                                                                          
checking for mail wrapper group; i.e. --with-mail-gid... kolab-n                                                                                             
checking for CGI wrapper group; i.e. --with-cgi-gid... kolab-n                                                                                               
checking for CGI extensions... no
[...]

I don't know if that "no" in the CGI extensions is good or correct.  :)

> Does the configure script give you anything related
> to this specific option?

which configure script are you talking about?

thanks,

bernat

> Cheers,
>
> Gunnar
>
> > any one know what may happen? would be better install the mailman throw
> > the tar package? I have to restart something special?
> >
> > well, I have the kolab 2.2.0 on a debian lenny. the kolab is installed
> > throw the script, not the deb packages. the mail man is installed throw
> > deb packages
> > and is the 2.1.11 version. I have download the mailman tar 2.1.11 for the
> > new configuration.
> >
> > thanks for the help,
> >
> > bernat
> >
> > _______________________________________________
> > Kolab-users mailing list
> > Kolab-users at kolab.org
> > https://kolab.org/mailman/listinfo/kolab-users



From steuwer at univention.de  Fri May  8 09:21:09 2009
From: steuwer at univention.de (Ingo Steuwer)
Date: Fri, 8 May 2009 09:21:09 +0200
Subject: Kolab authenticating through Active Directory (Windows AD)
In-Reply-To: <71fe4e760905071621x3c036136i1f850016c4a8d0c9@mail.gmail.com>
References: <7907AE10BB50DD4F840E76527D27EF19029F6466@entmail.domain.austinent.com>
	<71fe4e760905071621x3c036136i1f850016c4a8d0c9@mail.gmail.com>
Message-ID: <200905080921.10666.steuwer@univention.de>

Hi,

Am Freitag, 8. Mai 2009 schrieb Alain Spineux:
> On Thu, May 7, 2009 at 8:03 PM, Lucas Hendricks
>
> <LHendricks at austinent.com> wrote:
> > I have been digging around for the next step in integrating our network
> > with Kolab which would be to have Kolab authenticate against our windows
> > domain. I have been digging in the wiki and around the web, but this is
> > the closest thing I've found from the list in 2004:
> >
> > http://www.kolab.org/pipermail/kolab-users/2004-April/000081.html

I didn't read the post, but you should find tons of informations about 
configuring PAM against AD, either by pam-ldap or by pam-kerberos (I'd prefer 
the first one). You need to do that for all user-related parts of Kolab, like 
cyrus, postfix and others. That will need very much testing.

> Another idea :
>
> use pwdump to extract lanman password from your windows SAM.
>
> http://www.openwall.com/passwords/microsoft-windows-nt-2000-xp-2003-vista
>
> compile openldap to support lanman password
> sync your window password into your ldap
>
> I I did it for one user, it works ! But I have no scripts to automate
> the job :-(

Our Active Directory Connector does it exactly that way and works very well 
with our kolab integration. It's open source software:
http://www.univention.de/fileadmin/download/dokumentation_2.2/ucs-ad-connector_en.pdf

You may download the deb-source here:
http://apt.univention.de/2.2/maintained/2.2-0/

Maybe the windows-part (password-service) is helpfull for you, the 
Linux-daemon makes heavy use of other parts of our product (Univention 
Directory Manager); they are also open source software but porting them to 
native kolab would be very much work.

Regards,
Ingo

-- 
Ingo Steuwer
Head of Professional Services

Univention GmbH
Linux for your business
Mary-Somerville-Str.1
28359 Bremen
Tel.: +49 421 22232-43
Fax : +49 421 22232-99
Mob : +49 173 2112971

steuwer at univention.de>
http://www.univention.de

Gesch?ftsf?hrer: Peter H. Ganten
HRB 20755 Amtsgericht Bremen
Steuer-Nr.: 71-597-02876 



From steuwer at univention.de  Fri May  8 09:29:40 2009
From: steuwer at univention.de (Ingo Steuwer)
Date: Fri, 8 May 2009 09:29:40 +0200
Subject: migrating from exchange 5.5 to kolab 2.2.1 -- imapsync issue
	(resolved)
In-Reply-To: <7907AE10BB50DD4F840E76527D27EF19029F6459@entmail.domain.austinent.com>
References: <7907AE10BB50DD4F840E76527D27EF19029F6459@entmail.domain.austinent.com>
Message-ID: <200905080929.41914.steuwer@univention.de>

Hi,

Am Donnerstag, 7. Mai 2009 schrieb Lucas Hendricks:
> The below attempt was done with the latest Mail::IMAPClient module for
> perl. The error persisted even when attempting to use imapsync from one
> Kolab mailbox to another using imapsync 1.99 and Mail::IMAPClient 3.16.
>
> I reverted to the version of Mail::IMAPClient required by the imapsync and
> it began to sync emails great using imapsync 1.99 and Mail::IMAPClient
> 2.2.9.
>
> I'll try to update the wiki once my email verification comes =).
>
> Lucas
[..]

you know about the migration tools provided by Toltec (Toltec Migration Tool) 
or Bynari (PST-Export, ask them/me for a Kolab-version) which sync not only 
mails but also appointments/contacts (everything Outlook saves on the 
server)?

Please note that both are non-free.

Regards,
Ingo

-- 
Ingo Steuwer
Head of Professional Services

Univention GmbH
Linux for your business
Mary-Somerville-Str.1
28359 Bremen
Tel.: +49 421 22232-43
Fax : +49 421 22232-99
Mob : +49 173 2112971

steuwer at univention.de>
http://www.univention.de

Gesch?ftsf?hrer: Peter H. Ganten
HRB 20755 Amtsgericht Bremen
Steuer-Nr.: 71-597-02876 



From carsten at cburghardt.com  Fri May  8 10:28:37 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Fri, 08 May 2009 10:28:37 +0200
Subject: Upgrade on Suse 10.3 success
In-Reply-To: <4cd66e520905070905u4f65adf0hd344eb62c3ad111f@mail.gmail.com>
References: <20090507104834.17243gznb3z61eas@www.inovox.de>
	<4cd66e520905070905u4f65adf0hd344eb62c3ad111f@mail.gmail.com>
Message-ID: <20090508102837.10856kkcwmn0vfok@www.inovox.de>

Hi Skip,


> On Thu, May 7, 2009 at 1:48 AM, Carsten Burghardt
> <carsten at cburghardt.com> wrote:
>> Hi,
>>
>> after a lot of tests on a virtual system I finally upgraded my
>> productive Kolab server to 2.2.1 with the Suse packages.
>> Short description:
>> - Save ldap data according to readme (slapcat)
>> - rckolab stop
>> - add Kolab devel (see http://en.opensuse.org/Kolab) and Perl devel
>> (http://download.opensuse.org/repositories/devel:/languages:/perl/openSUSE_10.3)  
>> installation
>> sources
>> - update all Kolab, Horde, PHP and Perl packages with Yast
>> - restore .rpmnew files from /etc/kolab/templates (if you made changes)
>> - do the same for Horde if needed
>> - restore ldap data according to readme (slapadd)
>> - rcldap start
>> - kolabconf -n
>> - rckolab start
>> - change ownership of Horde config dirs and files to wwwrun
>>
>> That's it. So far I tested email, calendar, tasks, contacts and syncml
>> support, all work. I have not tested freebusy and shared calendars yet.
>>
>> I am currently not able to save the Horde config as administrator
>> because this replaces the __FILE__ macros with an actual path but that
>> does not seem to work as Horde can not find the database anymore.
>>
>>
>> Regards
>>
>> Carsten
>>
>>
>
> I've VERY interested in this, I'd tried a few times, I'm using SUSE
> 10.2 and "versions" in the web interface gives me this output:
>
> perl-kolab-5.8.7-30.8
> kolab-2.1.0-31.1
> kolab-resource-handlers-2.1.0-10.7
> kolab-webadmin-2.1.0-5.7

There are no packages provided for 10.2 so you will need at least 10.3.

> I would love the "Long Description" if you have the time.  I haven't
> had the time to mess with it in a while and currently it's working.  I
> vaguely remember getting some annotations.db errors and I thought I'd
> read that the DB format had changed, now I'm thinking that it's likely
> I wasn't following the proper steps.

To be honest that is the long list. There were no other steps. All the  
experiments I had to do was to find the correct sequence and avoid  
problems along the way.

> I have however successfully migrated the data and mail to a fresh 10.3
> install, but a huge issue I have with that is that we are using Toltec
> and per Joon, there is no way to 'copy' the Folder UID's, meaning that
> any shared folders would come in as new or duplicate the messages
> already contained within them on the outlook clients.
>
> What clients are you using?

I am using Horde and Thunderbird.



Carsten



From carsten at cburghardt.com  Fri May  8 10:48:13 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Fri, 08 May 2009 10:48:13 +0200
Subject: i18n folders
Message-ID: <20090508104813.12806iz1j85mn1oo@www.inovox.de>

Hi,

this is more a Horde question but maybe somebody has seen this before.  
I have a "Sent" folder in my account and I have set this in Horde as  
sent folder. But Horde or Kolab (don't know) keeps on creating a  
"Gesendet" folder (German version) in my account. Any idea how I can  
disable this?
Kolab 2.2.1 from Suse packages, Horde 3.3.


Thanks!

Carsten





From johnm at advocap.org  Fri May  8 17:44:00 2009
From: johnm at advocap.org (John McMonagle)
Date: Fri, 8 May 2009 10:44:00 -0500
Subject: Problem sending via tsl with Kontact e35 packages?
In-Reply-To: <200904300851.32070.bernhard@intevation.de>
References: <200904231654.28717.johnm@advocap.org>
	<200904281437.11536.johnm@advocap.org>
	<200904300851.32070.bernhard@intevation.de>
Message-ID: <200905081044.00970.johnm@advocap.org>

On Thursday 30 April 2009 01:51:31 am Bernhard Reiter wrote:
> Am Dienstag, 28. April 2009 21:37:10 schrieb John McMonagle:
> > Any more ideas on ?what could break smtp via tls in kmail?
>
> Maybe it is a problem on the server or its configuration.
> You could enable all debugging in kdebugdialog for Kontact
> and check .xsession-errors or so for other messages.

Bernhard

Finally got back to it.

The openssl errors on .xsession-errors looks suspicious.

kio_imap: IMAP4::dispatch - command=77
kio_imap: IMAP4Protocol::special
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: 
undefined symbol: PKCS7_content_free
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: 
undefined symbol: OpenSSL_add_all_algorithms
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: 
undefined symbol: OPENSSL_add_all_algorithms
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8: 
undefined symbol: OpenSSL_add_all_algorithms_conf
kmail: KMMessage::replacePrefixes: bigRegExp=^(?:\s+|(?:Re\s*:)|
(?:Re\[\d+\]:)|(?:Re\d+:)|(?:Fwd:)|(?:FW:))+\s*
kmail: WARNING: FolderStorage::getMsg was asked for an invalid index. idx =1 
count()=1
kmail: [void KMSender::cleanup()]
kio_imap: IMAP4::dispatch - command=80

I did reinstall libssl0.9.8
Had no effect.

John



From LHendricks at austinent.com  Fri May  8 19:06:17 2009
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Fri, 8 May 2009 12:06:17 -0500 
Subject: Kolab authenticating through Active Directory (Windows AD)
Message-ID: <7907AE10BB50DD4F840E76527D27EF19029F64D4@entmail.domain.austinent.com>

OK thanks for that information.  It does say AD prohibits password queries
so the simple setup I was envisioning where Kolab simply queries AD for
authentication seems unlikely.  I played with the saslauthd.conf and got it
to bind but as expected the user logins failed.  That would just be icing on
the cake, I suppose anyway.

Now that I have imapsync working I think I can start pushing people onto
Kolab and make them use horde or outlook(imap)/horde until the production
release of kontact/win is out.  I'm very excited and I hope as I learn new
things I can contribute more to the wiki and maybe eventually the code of
the project (I have a lot of learning to do before that).

Lucas 

-----Original Message-----
From: Ingo Steuwer [mailto:steuwer at univention.de] 
Sent: Friday, May 08, 2009 2:21 AM
To: kolab-users at kolab.org
Subject: Re: Kolab authenticating through Active Directory (Windows AD)

Hi,

Am Freitag, 8. Mai 2009 schrieb Alain Spineux:
> On Thu, May 7, 2009 at 8:03 PM, Lucas Hendricks
>
> <LHendricks at austinent.com> wrote:
> > I have been digging around for the next step in integrating our network
> > with Kolab which would be to have Kolab authenticate against our windows
> > domain. I have been digging in the wiki and around the web, but this is
> > the closest thing I've found from the list in 2004:
> >
> > http://www.kolab.org/pipermail/kolab-users/2004-April/000081.html

I didn't read the post, but you should find tons of informations about 
configuring PAM against AD, either by pam-ldap or by pam-kerberos (I'd
prefer 
the first one). You need to do that for all user-related parts of Kolab,
like 
cyrus, postfix and others. That will need very much testing.

> Another idea :
>
> use pwdump to extract lanman password from your windows SAM.
>
> http://www.openwall.com/passwords/microsoft-windows-nt-2000-xp-2003-vista
>
> compile openldap to support lanman password
> sync your window password into your ldap
>
> I I did it for one user, it works ! But I have no scripts to automate
> the job :-(

Our Active Directory Connector does it exactly that way and works very well 
with our kolab integration. It's open source software:
http://www.univention.de/fileadmin/download/dokumentation_2.2/ucs-ad-connect
or_en.pdf

You may download the deb-source here:
http://apt.univention.de/2.2/maintained/2.2-0/

Maybe the windows-part (password-service) is helpfull for you, the 
Linux-daemon makes heavy use of other parts of our product (Univention 
Directory Manager); they are also open source software but porting them to 
native kolab would be very much work.

Regards,
Ingo

-- 
Ingo Steuwer
Head of Professional Services

Univention GmbH
Linux for your business
Mary-Somerville-Str.1
28359 Bremen
Tel.: +49 421 22232-43
Fax : +49 421 22232-99
Mob : +49 173 2112971

steuwer at univention.de>
http://www.univention.de

Gesch?ftsf?hrer: Peter H. Ganten
HRB 20755 Amtsgericht Bremen
Steuer-Nr.: 71-597-02876 

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



From carsten at cburghardt.com  Fri May  8 20:37:00 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Fri, 08 May 2009 20:37:00 +0200
Subject: syncml error
Message-ID: <20090508203700.18514y9w668w8bgg@www.inovox.de>

Hi,

I am trying to sync my Nokia mobile (5800) with the Horde version that  
is part of Kolab 2.2.1. When it tried it some days ago that worked but  
in the meantime the mobile was updated to a new firmware. And of  
course the sync does not work anymore: the mobile ends the connection  
with "connection error". I deleted the sync information and started  
with a fresh sync that should overwrite the server data.
The log:

DEBUG:  Backend of class SyncML_Backend_Horde created
DEBUG:  Started at 2009-05-08 20:28:56. Packet logged in  
/tmp/sync/client_608.wbxml
DEBUG:  New session created: fde5cece9a4179fdb181a7741690f9df
DEBUG:  Checking authentication for user carsten
DEBUG:  Authenticated: yes; version: 1.2; message ID: 1; source URI:  
IMEI:354183023337641; target URI:  
https://<myserver>:443/client/rpc.php; user: <myuser>; charset: UTF-8;  
wbxml: yes
DEBUG:  SQL Query by SyncML_Backend_Horde::readSyncAnchors(): SELECT  
syncml_clientanchor, syncml_serveranchor FROM horde_syncml_anchors  
WHERE syncml_syncpartner = ? AND syncml_db = ? AND syncml_uid = ?,  
values: IMEI:354183023337641, contacts, <myuser>
DEBUG:  No info about previous syncs found for device  
IMEI:354183023337641 and database ./contacts
DEBUG:  Creating SyncML_Sync object for database ./contacts; sync type 203
DEBUG:  SQL Query by SyncML_Backend_Horde::readSyncAnchors(): SELECT  
syncml_clientanchor, syncml_serveranchor FROM horde_syncml_anchors  
WHERE syncml_syncpartner = ? AND syncml_db = ? AND syncml_uid = ?,  
values: IMEI:354183023337641, calendar, <myuser>
DEBUG:  No info about previous syncs found for device  
IMEI:354183023337641 and database ./calendar
DEBUG:  Creating SyncML_Sync object for database ./calendar; sync type 203
DEBUG:  SQL Query by SyncML_Backend_Horde::readSyncAnchors(): SELECT  
syncml_clientanchor, syncml_serveranchor FROM horde_syncml_anchors  
WHERE syncml_syncpartner = ? AND syncml_db = ? AND syncml_uid = ?,  
values: IMEI:354183023337641, notes, <myuser>
DEBUG:  No info about previous syncs found for device  
IMEI:354183023337641 and database ./notes
DEBUG:  Creating SyncML_Sync object for database ./notes; sync type 203
DEBUG:  Received <Final> from client.
DEBUG:  Handle <Final> for state Init
DEBUG:  Handle <Final> for state Init
DEBUG:  Handle <Final> for state Init
DEBUG:  Sending <Final> to client
DEBUG:  Return message completed
DEBUG:  Finished at 2009-05-08 20:28:57. Packet logged in  
/tmp/sync/server_608.wbxml

Any idea what could cause this?

Regards

Carsten



From carsten at cburghardt.com  Fri May  8 20:38:33 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Fri, 08 May 2009 20:38:33 +0200
Subject: i18n folders
In-Reply-To: <20090508104813.12806iz1j85mn1oo@www.inovox.de>
References: <20090508104813.12806iz1j85mn1oo@www.inovox.de>
Message-ID: <20090508203833.96056hkald8qzx0c@www.inovox.de>


Zitat von Carsten Burghardt <carsten at cburghardt.com>:

> Hi,
>
> this is more a Horde question but maybe somebody has seen this before.
> I have a "Sent" folder in my account and I have set this in Horde as
> sent folder. But Horde or Kolab (don't know) keeps on creating a
> "Gesendet" folder (German version) in my account. Any idea how I can
> disable this?
> Kolab 2.2.1 from Suse packages, Horde 3.3.

To answer my own question: the problem was a separate identity that  
still had the old sent folder. And Horde created this folder everytime  
I sent an email using this identity.



From LHendricks at austinent.com  Fri May  8 23:22:23 2009
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Fri, 8 May 2009 16:22:23 -0500 
Subject: shared folders and calendars as of 2.2.1
Message-ID: <7907AE10BB50DD4F840E76527D27EF19029F64F2@entmail.domain.austinent.com>

New webclient and calendars:

1. I have tried to create several shared calendars and other folder types
and none of them show up anywhere in horde or kontact/win that I can see.  I
tried changing permissions for each of the shared folders to several
different variations (I only have a couple of test logins right now) and it
still never shows any shared calendars within either program for any of the
logins.

I can see the shared items in the admin login, but nowhere else.  Am I doing
something dumb?  I could have sworn in 2.2.0 I simply added the shared
folder with item type of events in the admin tool and it automatically
showed up in kontact/win and horde (or at least I could search for it easily
which does not work now).

2. The subscription URL for my calendar is not working in horde.  This
worked in 2.2.0, also.  When I try to use the correct url format according
to the horde site I get an empty ics file on a calendar that has events.

This is an install from the debian 4.0 binary distribution of Kolab 2.2.1.
It is a non-production test environment so I can take any destructive steps
necessary to make this work right if it is not a kolab bug.

Thanks,
Lucas



From LHendricks at austinent.com  Fri May  8 23:31:43 2009
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Fri, 8 May 2009 16:31:43 -0500 
Subject: shared folders and calendars as of 2.2.1
Message-ID: <7907AE10BB50DD4F840E76527D27EF19029F64F4@entmail.domain.austinent.com>

I should note that I got warnings when I attempted a clean install.  It also
mentions something about being unable to remove a pear channel.  Here is the
output from the install... I will be trying a reinstall of debian 4.0 and
then fresh install of kolab 2.2.1 since I am getting this stuff and finding
problems with the final install:

This will completely wipe your installation in /kolab!
Are you certain you want to do that (YES/NO)?
warning: /kolab/var/kolab/www/fbview/kronolith/config/kolab.php saved as
/kolab/
var/kolab/www/fbview/kronolith/config/kolab.php.rpmsave
warning: /kolab/var/kolab/www/fbview/config/kolab.php saved as
/kolab/var/kolab/
www/fbview/config/kolab.php.rpmsave
warning: /kolab/etc/spamassassin/local.cf saved as
/kolab/etc/spamassassin/local.cf.rpmsave
Channel "pear.horde.org" has installed packages, cannot delete
Could not delete channel pear.horde.org!
warning: /kolab/etc/postfix/virtual saved as
/kolab/etc/postfix/virtual.rpmsave
warning: /kolab/etc/postfix/transport saved as
/kolab/etc/postfix/transport.rpmsave
warning: /kolab/etc/postfix/relocated saved as
/kolab/etc/postfix/relocated.rpmsave
warning: /kolab/etc/postfix/master.cf saved as
/kolab/etc/postfix/master.cf.rpmsave
warning: /kolab/etc/postfix/main.cf saved as
/kolab/etc/postfix/main.cf.rpmsave
warning: /kolab/etc/postfix/canonical saved as
/kolab/etc/postfix/canonical.rpmsave
warning: /kolab/etc/postfix/access saved as
/kolab/etc/postfix/access.rpmsave
warning: /kolab/etc/openldap/slapd.conf saved as
/kolab/etc/openldap/slapd.conf.rpmsave
warning: /kolab/etc/openldap/ldap.conf saved as
/kolab/etc/openldap/ldap.conf.rpmsave
warning: /kolab/var/kolab/www/client/kronolith/config/kolab.php saved as
/kolab/var/kolab/www/client/kronolith/config/kolab.php.rpmsave
warning: /kolab/var/kolab/www/client/config/kolab.php saved as
/kolab/var/kolab/www/client/config/kolab.php.rpmsave
warning: /kolab/etc/amavisd/amavisd.conf saved as
/kolab/etc/amavisd/amavisd.conf.rpmsave
warning: /kolab/var/kolab/www/freebusy/config.php saved as
/kolab/var/kolab/www/freebusy/config.php.rpmsave
env: /kolab/bin/pear: No such file or directory
Could not delete channel pear.phpunit.de!
warning: /kolab/etc/clamav/freshclam.conf saved as
/kolab/etc/clamav/freshclam.conf.rpmsave
warning: /kolab/etc/clamav/clamd.conf saved as
/kolab/etc/clamav/clamd.conf.rpmsave
warning: /kolab/etc/imapd/imapd.conf saved as
/kolab/etc/imapd/imapd.conf.rpmsave
warning: /kolab/etc/imapd/cyrus.conf saved as
/kolab/etc/imapd/cyrus.conf.rpmsave
warning: /kolab/etc/apache/apache.conf saved as
/kolab/etc/apache/apache.conf.rpmsave
warning: /kolab/etc/sasl/saslauthd.conf saved as
/kolab/etc/sasl/saslauthd.conf.rpmsave
openpkg:WARNING: skipping deletion of OpenPKG super-user user root
openpkg:WARNING: (would remove system standard user)
openpkg:WARNING: skipping deletion of OpenPKG super-user group root
openpkg:WARNING: (would remove system standard group)
warning: /kolab/etc/rc.conf saved as /kolab/etc/rc.conf.rpmsave
Erased OpenPKG environment /kolab
-----Original Message-----
From: Lucas Hendricks [mailto:LHendricks at austinent.com] 
Sent: Friday, May 08, 2009 4:22 PM
To: kolab-users at kolab.org
Subject: shared folders and calendars as of 2.2.1

New webclient and calendars:

1. I have tried to create several shared calendars and other folder types
and none of them show up anywhere in horde or kontact/win that I can see.  I
tried changing permissions for each of the shared folders to several
different variations (I only have a couple of test logins right now) and it
still never shows any shared calendars within either program for any of the
logins.

I can see the shared items in the admin login, but nowhere else.  Am I doing
something dumb?  I could have sworn in 2.2.0 I simply added the shared
folder with item type of events in the admin tool and it automatically
showed up in kontact/win and horde (or at least I could search for it easily
which does not work now).

2. The subscription URL for my calendar is not working in horde.  This
worked in 2.2.0, also.  When I try to use the correct url format according
to the horde site I get an empty ics file on a calendar that has events.

This is an install from the debian 4.0 binary distribution of Kolab 2.2.1.
It is a non-production test environment so I can take any destructive steps
necessary to make this work right if it is not a kolab bug.

Thanks,
Lucas

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



From kolab at izsr.de  Sun May 10 10:17:32 2009
From: kolab at izsr.de (Tim Golz)
Date: Sun, 10 May 2009 10:17:32 +0200
Subject: Which MUA for the CLI?
Message-ID: <04E197D8-ECAD-4B99-9C31-D25094AEDE05@izsr.de>

Hi, folx,


on a Kolab 2.2.0 on a Debian Etch, which MUA could I use when I just  
want to send a testmail via the CLI?

Usually I prefer mailx, but though mailx is installed on my system I  
am not able to send a testmail from root on the CLI to another user.  
Mailx uses the sendmail-link from Exim (though I purged Exim ... ) and  
delivers all mails to /var/spool/exim4/msglog/, but it doesnt work  
with Kolab :-(

Thanx a lot in advance!


greetings


Tim Golz



From Nazeer at kryptonpcs.co.za  Sun May 10 12:04:18 2009
From: Nazeer at kryptonpcs.co.za (Nazeer)
Date: Sun, 10 May 2009 12:04:18 +0200
Subject: Cannot Delete Users in Kolab 2.2.1
Message-ID: <00ac01c9d156$ae967b60$0bc37220$@co.za>

Hi

 

I compiled Kolab 2.2.1 (latest version) on Ubuntu Dapper. Problem is that I
cannot delete users. It just keeps saying "User delete, awaiting cleanup). I
have restarted all Kolab services twice and still no luck. Used the
following command (/kolab/bin/openpkg rc all restart)

 

Any Suggestions?

 

Thanks

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20090510/e5d23c1f/attachment.html

From Nazeer at kryptonpcs.co.za  Sun May 10 12:08:08 2009
From: Nazeer at kryptonpcs.co.za (Nazeer)
Date: Sun, 10 May 2009 12:08:08 +0200
Subject: Kolab 2.2.1 with Hylafax
Message-ID: <00b101c9d157$3817bed0$a8473c70$@co.za>

H

 

What would be the procedure of installing Hylafax on a Kolab server using
Ubuntu 8.04 or 8.10? With Apt-get install hylafax, it keeps installing exim
which causes problems and when i try to remove exim on its own, it wants to
remove hylafax as well.

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20090510/41cd8473/attachment.html

From tom at tiri.li  Sun May 10 13:28:44 2009
From: tom at tiri.li (Thomas Baumann)
Date: Sun, 10 May 2009 13:28:44 +0200
Subject: Kolab 2.2.1 with Hylafax and exim4
In-Reply-To: <00b101c9d157$3817bed0$a8473c70$@co.za>
References: <00b101c9d157$3817bed0$a8473c70$@co.za>
Message-ID: <20090510132844.atu6dt6io0c88ckc@ox.thomasbaumann.com>

Hi Nazeer,

You can install exim and hylafax in debian from apt.
But it is necessary to keep exim stopped -- and configured on
another port (e.g. 20025) via /etc/exim4/exim4.conf.template
Then it will not interfere the kolab environment, and
mails will be accepted on kolab-postfix on port 25.

Greetings

Thomas.


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

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

Zitat von Nazeer <Nazeer at kryptonpcs.co.za>:

> H
>
>
>
> What would be the procedure of installing Hylafax on a Kolab server using
> Ubuntu 8.04 or 8.10? With Apt-get install hylafax, it keeps installing exim
> which causes problems and when i try to remove exim on its own, it wants to
> remove hylafax as well.
>
>
>
>
>
>
>
>
>
>




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



From tom at tiri.li  Sun May 10 14:33:03 2009
From: tom at tiri.li (Thomas Baumann)
Date: Sun, 10 May 2009 14:33:03 +0200
Subject: Kolab 2.2.1 with Hylafax and exim4
In-Reply-To: <00b901c9d164$f6501cf0$e2f056d0$@co.za>
References: <00b101c9d157$3817bed0$a8473c70$@co.za>
	<20090510132844.atu6dt6io0c88ckc@ox.thomasbaumann.com>
	<00b901c9d164$f6501cf0$e2f056d0$@co.za>
Message-ID: <20090510143303.4ljf8110ggkgwcg4@ox.thomasbaumann.com>

Disabling the init script would also work, but it is not
secure, sb could start the exim which would raise an error.
So you need to configure exim listening to another than the
kolab ports.

Greetings

Thomas.

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

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

Zitat von Nazeer <Nazeer at kryptonpcs.co.za>:

> Ok thanks, will try. Is there anything else I need edit to make hylafax work
> with kolab?
>
> Another option i was thinking about is maybe disabling exim from startup in
> /etc/init.d/
>
> Would that also work?
>
> -----Original Message-----
> From: Thomas Baumann [mailto:tom at tiri.li]
> Sent: 10 May 2009 01:29 PM
> To: Nazeer
> Cc: kolab-users at kolab.org
> Subject: Re: Kolab 2.2.1 with Hylafax and exim4
>
> Hi Nazeer,
>
> You can install exim and hylafax in debian from apt.
> But it is necessary to keep exim stopped -- and configured on
> another port (e.g. 20025) via /etc/exim4/exim4.conf.template
> Then it will not interfere the kolab environment, and
> mails will be accepted on kolab-postfix on port 25.
>
> Greetings
>
> Thomas.
>
>
> --
> tiri GmbH
> Lauenburger Str. 31a
> 21493 Schwarzenbek
> Tel. 04151 8674995
> Fax. 04151 8674996
> Net. http://www.tiri.li
>
> Gesch?ftsf?hrer: Anja Baumann, Thomas Baumann
> Sitz Schwarzenbek, Amtsgericht L?beck, HRB 8837 HL
>
> Zitat von Nazeer <Nazeer at kryptonpcs.co.za>:
>
>> H
>>
>>
>>
>> What would be the procedure of installing Hylafax on a Kolab server using
>> Ubuntu 8.04 or 8.10? With Apt-get install hylafax, it keeps installing
> exim
>> which causes problems and when i try to remove exim on its own, it wants
> to
>> remove hylafax as well.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
> __________ Information from ESET Smart Security, version of virus signature
> database 4036 (20090427) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>

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



From bernhard at intevation.de  Mon May 11 12:19:48 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 11 May 2009 12:19:48 +0200
Subject: Problem sending via tsl with Kontact e35 packages?
In-Reply-To: <200905081044.00970.johnm@advocap.org>
References: <200904231654.28717.johnm@advocap.org>
	<200904300851.32070.bernhard@intevation.de>
	<200905081044.00970.johnm@advocap.org>
Message-ID: <200905111219.52067.bernhard@intevation.de>

Am Freitag, 8. Mai 2009 17:44:00 schrieb John McMonagle:
> kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8:
> undefined symbol: OPENSSL_add_all_algorithms
> kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.8:
> undefined symbol: OpenSSL_add_all_algorithms_conf

I believe I've seen those warning and ignored them.
Are you absolutely sure that you have the right id and password in?
(If you were not tying the primary email address, as id, try it please.)

-- 
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-users/attachments/20090511/978f9bbb/attachment.bin

From bernhard at intevation.de  Mon May 11 12:30:27 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 11 May 2009 12:30:27 +0200
Subject: shared folders and calendars as of 2.2.1
In-Reply-To: <7907AE10BB50DD4F840E76527D27EF19029F64F2@entmail.domain.austinent.com>
References: <7907AE10BB50DD4F840E76527D27EF19029F64F2@entmail.domain.austinent.com>
Message-ID: <200905111230.37582.bernhard@intevation.de>

Am Freitag, 8. Mai 2009 23:22:23 schrieb Lucas Hendricks:
> 1. I have tried to create several shared calendars and other folder types
> and none of them show up anywhere in horde or kontact/win that I can see.

Check that they were created correctly by checking the IMAP server directly,
e.g. logging in with cyradm as user and listing all mailboxes.

Note the name clash: a shared folder usually is something that a user gets 
permission to. The web admin only can create accountless folders
and we do not recommend to use them. 

> 2. The subscription URL for my calendar is not working in horde. ?

There is one URL which is not supposed for work with Kolab Server and
its Webclient. I think we have a report to remove that missleading URL.
(And I guess that is what you are seeing.)

-- 
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-users/attachments/20090511/801d7138/attachment.bin

From bernhard at intevation.de  Mon May 11 12:33:10 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 11 May 2009 12:33:10 +0200
Subject: Which MUA for the CLI?
In-Reply-To: <04E197D8-ECAD-4B99-9C31-D25094AEDE05@izsr.de>
References: <04E197D8-ECAD-4B99-9C31-D25094AEDE05@izsr.de>
Message-ID: <200905111233.11069.bernhard@intevation.de>

Am Sonntag, 10. Mai 2009 10:17:32 schrieb Tim Golz:
> on a Kolab 2.2.0 on a Debian Etch, which MUA could I use when I just ?
> want to send a testmail via the CLI?

Any MUA will do for Kolab Server as Kolab Server installs a full MTA,
including postfix which has a sendmail compatibility binary.
Even easier is to install nullmailer and have it all transport to the 
localhost 25 where postfix listens.

> Usually I prefer mailx, but though mailx is installed on my system I ?
> am not able to send a testmail from root on the CLI to another user. ?
> Mailx uses the sendmail-link from Exim (though I purged Exim ... ) and ?
> delivers all mails to /var/spool/exim4/msglog/, but it doesnt work ?
> with Kolab :-(

mailx should work just as mutt or others.

apt-get install nullmailer 


-- 
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-users/attachments/20090511/978e6534/attachment.bin

From bernhard at intevation.de  Mon May 11 12:34:18 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 11 May 2009 12:34:18 +0200
Subject: Cannot Delete Users in Kolab 2.2.1
In-Reply-To: <00ac01c9d156$ae967b60$0bc37220$@co.za>
References: <00ac01c9d156$ae967b60$0bc37220$@co.za>
Message-ID: <200905111234.18646.bernhard@intevation.de>

Am Sonntag, 10. Mai 2009 12:04:18 schrieb Nazeer:
> I compiled Kolab 2.2.1 (latest version) on Ubuntu Dapper. Problem is that I
> cannot delete users. It just keeps saying "User delete, awaiting cleanup).
> I have restarted all Kolab services twice and still no luck. Used the
> following command (/kolab/bin/openpkg rc all restart)

Check the ldapout put to see if the kolabDelete attribute matches our
only hostname correctly. (E.g. with slapcat.)
-- 
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-users/attachments/20090511/1404517d/attachment.bin

From bernhard at intevation.de  Mon May 11 12:36:05 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 11 May 2009 12:36:05 +0200
Subject: Kolab 2.2.1 with Hylafax and exim4
In-Reply-To: <20090510132844.atu6dt6io0c88ckc@ox.thomasbaumann.com>
References: <00b101c9d157$3817bed0$a8473c70$@co.za>
	<20090510132844.atu6dt6io0c88ckc@ox.thomasbaumann.com>
Message-ID: <200905111236.05899.bernhard@intevation.de>

Am Sonntag, 10. Mai 2009 13:28:44 schrieb Thomas Baumann:
> But it is necessary to keep exim stopped -- and configured on
> another port (e.g. 20025)

Or install a different mail-transport-manager, e.g. nullmailer.


-- 
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-users/attachments/20090511/8cbfa9d2/attachment.bin

From aspineux at gmail.com  Mon May 11 13:38:03 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 11 May 2009 13:38:03 +0200
Subject: Which MUA for the CLI?
In-Reply-To: <04E197D8-ECAD-4B99-9C31-D25094AEDE05@izsr.de>
References: <04E197D8-ECAD-4B99-9C31-D25094AEDE05@izsr.de>
Message-ID: <71fe4e760905110438l668d9197g6b8ec795aa694432@mail.gmail.com>

On Sun, May 10, 2009 at 10:17 AM, Tim Golz <kolab at izsr.de> wrote:
> Hi, folx,
>
>
> on a Kolab 2.2.0 on a Debian Etch, which MUA could I use when I just
> want to send a testmail via the CLI?

Try replacing your sendmail binary by the kolab's one.

Try this :

mv /usr/sbin/sendmail /usr/sbin/sendmail.save
ln -sf /kolab/sbin/sendmail /usr/sbin/sendmail

Then try your mail or mailx utility


>
> Usually I prefer mailx, but though mailx is installed on my system I
> am not able to send a testmail from root on the CLI to another user.
> Mailx uses the sendmail-link from Exim (though I purged Exim ... ) and
> delivers all mails to /var/spool/exim4/msglog/, but it doesnt work
> with Kolab :-(
>
> Thanx a lot in advance!
>
>
> greetings
>
>
> Tim Golz
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



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



From LHendricks at austinent.com  Mon May 11 21:30:05 2009
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Mon, 11 May 2009 14:30:05 -0500
Subject: shared folders and calendars as of 2.2.1
Message-ID: <7907AE10BB50DD4F840E76527D27EF19029F6560@entmail.domain.austinent.com>

>Check that they were created correctly by checking the IMAP server
>directly,e.g. logging in with cyradm as user and listing all mailboxes.

>Note the name clash: a shared folder usually is something that a user gets 
>permission to. The web admin only can create accountless folders
>and we do not recommend to use them.

So using the shared folders feature of the webadmin is not recommended?  I
should just be creating the folders via horde/kontact and sharing them
through those programs, instead?

Lucas

-----Original Message-----
From: Bernhard Reiter [mailto:bernhard at intevation.de] 
Sent: Monday, May 11, 2009 5:30 AM
To: kolab-users at kolab.org
Subject: Re: shared folders and calendars as of 2.2.1

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



From LHendricks at austinent.com  Mon May 11 21:58:20 2009
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Mon, 11 May 2009 14:58:20 -0500
Subject: shared folders and calendars as of 2.2.1 (resolved)
Message-ID: <7907AE10BB50DD4F840E76527D27EF19029F6569@entmail.domain.austinent.com>

OK, I downloaded the latest rc8 iso for Debian 4.0, and did a clean
reinstall (Like I said it is a test environment, still).

Both problems are gone.  I've been working on this same install since
2.2-rc3 and had installed some pear tools for horde so I am thinking with
the errors I was getting that those tools were corrupting the install.

The subscription link works, and the shared folders now show up after I log
back into horde once they are created and is showing up in kontact.  Sorry
for rushing to the email list, I should have done that first.

Lucas

-----Original Message-----
From: Lucas Hendricks [mailto:LHendricks at austinent.com] 
Sent: Monday, May 11, 2009 2:30 PM
To: kolab-users at kolab.org
Subject: RE: shared folders and calendars as of 2.2.1

>Check that they were created correctly by checking the IMAP server
>directly,e.g. logging in with cyradm as user and listing all mailboxes.

>Note the name clash: a shared folder usually is something that a user gets 
>permission to. The web admin only can create accountless folders
>and we do not recommend to use them.

So using the shared folders feature of the webadmin is not recommended?  I
should just be creating the folders via horde/kontact and sharing them
through those programs, instead?

Lucas

-----Original Message-----
From: Bernhard Reiter [mailto:bernhard at intevation.de] 
Sent: Monday, May 11, 2009 5:30 AM
To: kolab-users at kolab.org
Subject: Re: shared folders and calendars as of 2.2.1

_______________________________________________
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



From tom at tiri.li  Mon May 11 22:12:37 2009
From: tom at tiri.li (Thomas Baumann)
Date: Mon, 11 May 2009 22:12:37 +0200
Subject: Kolab 2.2.1 with Hylafax and exim4
In-Reply-To: <010401c9d270$8181fe40$8485fac0$@co.za>
References: <00b101c9d157$3817bed0$a8473c70$@co.za>
	<20090510132844.atu6dt6io0c88ckc@ox.thomasbaumann.com>
	<00b901c9d164$f6501cf0$e2f056d0$@co.za>
	<20090510143303.4ljf8110ggkgwcg4@ox.thomasbaumann.com>
	<010401c9d270$8181fe40$8485fac0$@co.za>
Message-ID: <20090511221237.2arhkiwhs08gww88@ox.thomasbaumann.com>

No problem.
Just put in your exim4.conf.template

daemon_smtp_ports=10225

and run update-exim4.conf

Now exim4 should listen on port 10225 only.

Greetings -

Thomas.

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

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

Zitat von Nazeer <Nazeer at kryptonpcs.co.za>:

> Hi
>
> Thanks for your help but I cannot find anything is the conf file about port
> number. Do you by any chance know where?
>
> Thanks
>
> -----Original Message-----
> From: Thomas Baumann [mailto:tom at tiri.li]
> Sent: 10 May 2009 02:33 PM
> To: Nazeer
> Cc: kolab-users at kolab.org
> Subject: RE: Kolab 2.2.1 with Hylafax and exim4
>
> Disabling the init script would also work, but it is not
> secure, sb could start the exim which would raise an error.
> So you need to configure exim listening to another than the
> kolab ports.
>
> Greetings
>
> Thomas.
>
> --
> tiri GmbH
> Lauenburger Str. 31a
> 21493 Schwarzenbek
> Tel. 04151 8674995
> Fax. 04151 8674996
> Net. http://www.tiri.li
>
> Gesch?ftsf?hrer: Anja Baumann, Thomas Baumann
> Sitz Schwarzenbek, Amtsgericht L?beck, HRB 8837 HL
>
> Zitat von Nazeer <Nazeer at kryptonpcs.co.za>:
>
>> Ok thanks, will try. Is there anything else I need edit to make hylafax
> work
>> with kolab?
>>
>> Another option i was thinking about is maybe disabling exim from startup
> in
>> /etc/init.d/
>>
>> Would that also work?
>>
>> -----Original Message-----
>> From: Thomas Baumann [mailto:tom at tiri.li]
>> Sent: 10 May 2009 01:29 PM
>> To: Nazeer
>> Cc: kolab-users at kolab.org
>> Subject: Re: Kolab 2.2.1 with Hylafax and exim4
>>
>> Hi Nazeer,
>>
>> You can install exim and hylafax in debian from apt.
>> But it is necessary to keep exim stopped -- and configured on
>> another port (e.g. 20025) via /etc/exim4/exim4.conf.template
>> Then it will not interfere the kolab environment, and
>> mails will be accepted on kolab-postfix on port 25.
>>
>> Greetings
>>
>> Thomas.
>>
>>
>> --
>> tiri GmbH
>> Lauenburger Str. 31a
>> 21493 Schwarzenbek
>> Tel. 04151 8674995
>> Fax. 04151 8674996
>> Net. http://www.tiri.li
>>
>> Gesch?ftsf?hrer: Anja Baumann, Thomas Baumann
>> Sitz Schwarzenbek, Amtsgericht L?beck, HRB 8837 HL
>>
>> Zitat von Nazeer <Nazeer at kryptonpcs.co.za>:
>>
>>> H
>>>
>>>
>>>
>>> What would be the procedure of installing Hylafax on a Kolab server using
>>> Ubuntu 8.04 or 8.10? With Apt-get install hylafax, it keeps installing
>> exim
>>> which causes problems and when i try to remove exim on its own, it wants
>> to
>>> remove hylafax as well.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>>
>> __________ Information from ESET Smart Security, version of virus
> signature
>> database 4036 (20090427) __________
>>
>> The message was checked by ESET Smart Security.
>>
>> http://www.eset.com
>>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
> __________ Information from ESET Smart Security, version of virus signature
> database 4036 (20090427) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>
>
>





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



From tom at tiri.li  Mon May 11 22:41:04 2009
From: tom at tiri.li (Thomas Baumann)
Date: Mon, 11 May 2009 22:41:04 +0200
Subject: Kolab 2.2.1 with Hylafax and exim4
In-Reply-To: <012501c9d278$5b3be450$11b3acf0$@co.za>
References: <00b101c9d157$3817bed0$a8473c70$@co.za>
	<20090510132844.atu6dt6io0c88ckc@ox.thomasbaumann.com>
	<00b901c9d164$f6501cf0$e2f056d0$@co.za>
	<20090510143303.4ljf8110ggkgwcg4@ox.thomasbaumann.com>
	<010401c9d270$8181fe40$8485fac0$@co.za>
	<20090511221237.2arhkiwhs08gww88@ox.thomasbaumann.com>
	<012501c9d278$5b3be450$11b3acf0$@co.za>
Message-ID: <20090511224104.zgkwhoprks8g8gwk@ox.thomasbaumann.com>

netstat -nalp | grep :10225

(or

netstat -nalp | grep exim

)

Greetings

Thomas.


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

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

Zitat von Nazeer <Nazeer at kryptonpcs.co.za>:

> Thanks, will give it a try
>
> How would I check afterwards what port its running on?
>
> -----Original Message-----
> From: Thomas Baumann [mailto:tom at tiri.li]
> Sent: 11 May 2009 10:13 PM
> To: Nazeer
> Cc: kolab-users at kolab.org
> Subject: RE: Kolab 2.2.1 with Hylafax and exim4
>
> No problem.
> Just put in your exim4.conf.template
>
> daemon_smtp_ports=10225
>
> and run update-exim4.conf
>
> Now exim4 should listen on port 10225 only.
>
> Greetings -
>
> Thomas.
>
> --
> tiri GmbH
> Lauenburger Str. 31a
> 21493 Schwarzenbek
> Tel. 04151 8674995
> Fax. 04151 8674996
> Net. http://www.tiri.li
>
> Gesch?ftsf?hrer: Anja Baumann, Thomas Baumann
> Sitz Schwarzenbek, Amtsgericht L?beck, HRB 8837 HL
>
> Zitat von Nazeer <Nazeer at kryptonpcs.co.za>:
>
>> Hi
>>
>> Thanks for your help but I cannot find anything is the conf file about
> port
>> number. Do you by any chance know where?
>>
>> Thanks
>>
>> -----Original Message-----
>> From: Thomas Baumann [mailto:tom at tiri.li]
>> Sent: 10 May 2009 02:33 PM
>> To: Nazeer
>> Cc: kolab-users at kolab.org
>> Subject: RE: Kolab 2.2.1 with Hylafax and exim4
>>
>> Disabling the init script would also work, but it is not
>> secure, sb could start the exim which would raise an error.
>> So you need to configure exim listening to another than the
>> kolab ports.
>>
>> Greetings
>>
>> Thomas.
>>
>> --
>> tiri GmbH
>> Lauenburger Str. 31a
>> 21493 Schwarzenbek
>> Tel. 04151 8674995
>> Fax. 04151 8674996
>> Net. http://www.tiri.li
>>
>> Gesch?ftsf?hrer: Anja Baumann, Thomas Baumann
>> Sitz Schwarzenbek, Amtsgericht L?beck, HRB 8837 HL
>>
>> Zitat von Nazeer <Nazeer at kryptonpcs.co.za>:
>>
>>> Ok thanks, will try. Is there anything else I need edit to make hylafax
>> work
>>> with kolab?
>>>
>>> Another option i was thinking about is maybe disabling exim from startup
>> in
>>> /etc/init.d/
>>>
>>> Would that also work?
>>>
>>> -----Original Message-----
>>> From: Thomas Baumann [mailto:tom at tiri.li]
>>> Sent: 10 May 2009 01:29 PM
>>> To: Nazeer
>>> Cc: kolab-users at kolab.org
>>> Subject: Re: Kolab 2.2.1 with Hylafax and exim4
>>>
>>> Hi Nazeer,
>>>
>>> You can install exim and hylafax in debian from apt.
>>> But it is necessary to keep exim stopped -- and configured on
>>> another port (e.g. 20025) via /etc/exim4/exim4.conf.template
>>> Then it will not interfere the kolab environment, and
>>> mails will be accepted on kolab-postfix on port 25.
>>>
>>> Greetings
>>>
>>> Thomas.
>>>
>>>
>>> --
>>> tiri GmbH
>>> Lauenburger Str. 31a
>>> 21493 Schwarzenbek
>>> Tel. 04151 8674995
>>> Fax. 04151 8674996
>>> Net. http://www.tiri.li
>>>
>>> Gesch?ftsf?hrer: Anja Baumann, Thomas Baumann
>>> Sitz Schwarzenbek, Amtsgericht L?beck, HRB 8837 HL
>>>
>>> Zitat von Nazeer <Nazeer at kryptonpcs.co.za>:
>>>
>>>> H
>>>>
>>>>
>>>>
>>>> What would be the procedure of installing Hylafax on a Kolab server
> using
>>>> Ubuntu 8.04 or 8.10? With Apt-get install hylafax, it keeps installing
>>> exim
>>>> which causes problems and when i try to remove exim on its own, it wants
>>> to
>>>> remove hylafax as well.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> ----------------------------------------------------------------
>>> This message was sent using IMP, the Internet Messaging Program.
>>>
>>>
>>> __________ Information from ESET Smart Security, version of virus
>> signature
>>> database 4036 (20090427) __________
>>>
>>> The message was checked by ESET Smart Security.
>>>
>>> http://www.eset.com
>>>
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>>
>> __________ Information from ESET Smart Security, version of virus
> signature
>> database 4036 (20090427) __________
>>
>> The message was checked by ESET Smart Security.
>>
>> http://www.eset.com
>>
>>
>>
>>
>>
>
>
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
> __________ Information from ESET Smart Security, version of virus signature
> database 4036 (20090427) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>
>
>


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



From ml at radoeka.nl  Tue May 12 21:11:59 2009
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 12 May 2009 21:11:59 +0200
Subject: Upgrade on Suse 10.3 success
In-Reply-To: <4A035291.9000106@cburghardt.com>
References: <20090507104834.17243gznb3z61eas@www.inovox.de>
	<200905072148.51890.ml@radoeka.nl>
	<4A035291.9000106@cburghardt.com>
Message-ID: <200905122112.00202.ml@radoeka.nl>

Hi Carsten,

Op donderdag 07 mei 2009 23:28:49 schreef Carsten Burghardt:
> The reason for the error is rather simple. You have something like this
> in the Horde config:
> $conf['tmpdir'] = dirname(__FILE__) . '/../tmp/';
>
> If that is opened during runtime the dirname is replaced with the config
> directory so it works. But if you open the Horde configuration page and
> have a look at the setting the dirname is replaced with
> /srv/www/htdocs/client/lib/Horde/. I assume this is because the
> config.php is included. So the replaced path that shows up is
> /srv/www/htdocs/client/lib/Horde/../tmp/ and that is wrong. When you
> save the configuration the wrong path is include. Why don't you use the
> kolab functionality to insert the path to Horde here?

What do you mean with this?  To which kolab functionality are you referring?  
I have no idea what this is about, as it is Alar who did the packaging of the 
webclient.

-- 
Richard



From kolab at izsr.de  Wed May 13 00:11:54 2009
From: kolab at izsr.de (Tim Golz)
Date: Wed, 13 May 2009 00:11:54 +0200
Subject: Which MUA for the CLI?
In-Reply-To: <71fe4e760905110438l668d9197g6b8ec795aa694432@mail.gmail.com>
References: <04E197D8-ECAD-4B99-9C31-D25094AEDE05@izsr.de>
	<71fe4e760905110438l668d9197g6b8ec795aa694432@mail.gmail.com>
Message-ID: <6913EB1A-7020-4206-92E3-4563618ADBA0@izsr.de>

Hi Alain,


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


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


thanx, too, to Bernhard.


greetings


Tim



From carsten at cburghardt.com  Wed May 13 10:31:53 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Wed, 13 May 2009 10:31:53 +0200
Subject: Upgrade on Suse 10.3 success
In-Reply-To: <200905122112.00202.ml@radoeka.nl>
References: <20090507104834.17243gznb3z61eas@www.inovox.de>
	<200905072148.51890.ml@radoeka.nl> <4A035291.9000106@cburghardt.com>
	<200905122112.00202.ml@radoeka.nl>
Message-ID: <20090513103153.13911upplyseryio@www.inovox.de>


Zitat von Richard Bos <ml at radoeka.nl>:

> Hi Carsten,
>
> Op donderdag 07 mei 2009 23:28:49 schreef Carsten Burghardt:
>> The reason for the error is rather simple. You have something like this
>> in the Horde config:
>> $conf['tmpdir'] = dirname(__FILE__) . '/../tmp/';
>>
>> If that is opened during runtime the dirname is replaced with the config
>> directory so it works. But if you open the Horde configuration page and
>> have a look at the setting the dirname is replaced with
>> /srv/www/htdocs/client/lib/Horde/. I assume this is because the
>> config.php is included. So the replaced path that shows up is
>> /srv/www/htdocs/client/lib/Horde/../tmp/ and that is wrong. When you
>> save the configuration the wrong path is include. Why don't you use the
>> kolab functionality to insert the path to Horde here?
>
> What do you mean with this?  To which kolab functionality are you referring?
> I have no idea what this is about, as it is Alar who did the packaging of the
> webclient.

Well, the configuration files from Horde are generated by kolabconf  
and some variables are replaced so I would recommend to use that  
functionality to insert the path to Horde in that place and not to use  
that dirname(__FILE__) thingy. I don't know if Alar also reads this  
mailinglist.


Regards

Carsten



From johnm at advocap.org  Wed May 13 16:07:32 2009
From: johnm at advocap.org (John McMonagle)
Date: Wed, 13 May 2009 09:07:32 -0500
Subject: Problem with acls migrating from cyrus imap.
Message-ID: <200905130907.33120.johnm@advocap.org>

Working on migrating our debian sarge cyrus mail to kolab 2.2.1.

I'm having a problem getting the acls set.

This is what I'm doing:
Stop kolab
/etc/init.d/kolab stop
remove old mail spool
rm  -fr /kolab/var/imapd/spool/domain/a/advocap.org/*/user/*
rm /kolab/var/imapd/mailboxes.db
sudo -u kolab-r rsync -aHe ssh --exclude cyrus.*  
root at mail:/cyrus/spool/cyrus/mail/ /kolab/var/imapd/spool/domain/a/advocap.org

ssh root at mail "sudo -u cyrus /usr/sbin/ctl_mboxlist -d" > /tmp/mboxlist.txt

The next should be enhanced to get extra acls but  it should do it.

awk 'BEGIN { FS = "\t" } ;{print "advocap.org!" $1 "\t" $2 "\t" 
$3"@advocap.org" "\t" $4   }' /tmp/mboxlist.txt > /tmp/newmbox.txt

Sample from old dump mboxlist.txt
user.test       default test    lrswipcda       mailadm lrswipcda
user.test.Drafts        default test    lrswipcda       mailadm lrswipcda
user.test.Sent  default test    lrswipcda       mailadm lrswipcda
user.test.Trash default test    lrswipcda       mailadm lrswipcda

Sample from New newmbox.txt:
advocap.org!user.test   default test at advocap.org        lrswipcda
advocap.org!user.test.Drafts    default test at advocap.org        lrswipcda
advocap.org!user.test.Sent      default test at advocap.org        lrswipcda
advocap.org!user.test.Trash     default test at advocap.org        lrswipcda

sudo -u kolab-r /kolab/bin/ctl_mboxlist -u < newmbox.txt
ctl_mboxlis -d   looks OK after running

advocap.org!user.test   0 default test  lrswipcda
advocap.org!user.test.Drafts    0 default test  lrswipcda
advocap.org!user.test.Sent      0 default test  lrswipcda
advocap.org!user.test.Trash     0 default test  lrswipcda

Shouldn't matter but want to disclose everything.
sudo -u kolab-r rsync -aHe ssh  
root at mail://var/lib/cyrus/user/ /kolab/var/imapd/domain/a/advocap.org/user

find  /kolab/var/imapd/domain/a/advocap.org/user  -name "*.sub" -exec 
sed -i 's/user\.\w*/&@advocap.org/' {} \;

sudo  -u kolab-r /kolab/bin/mkimap

sudo  -u kolab-r /kolab/bin/cyrreconstruct
That does find all the mail boxes

in cyradm
lm user/test at advocap.org
user/test at advocap.org (\HasChildren)
lam user/test at advocap.org
.....Nothing...

If I add with sam it's ok.

Am I missing something?
Does ctl_mboxlist -u  not set acls?

Thanks

John







From carsten at cburghardt.com  Wed May 13 16:54:53 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Wed, 13 May 2009 16:54:53 +0200
Subject: 2.2.1/Horde: unable to save filter settings mor than once?
In-Reply-To: <20090417054814.87502ersg5cubr40@webmail.pardus.de>
References: <1239216672.5379.1@antares>
	<200904151121.17805.funke@hiskp.uni-bonn.de>
	<20090417054814.87502ersg5cubr40@webmail.pardus.de>
Message-ID: <20090513165453.631610j6yuv2kgn4@www.inovox.de>


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

> Quoting Christian Funke <funke at hiskp.uni-bonn.de>:
>
>> Hi Albert, hello List,
>>
>> the same happened to me just now. Saving filters was working fine
>> and now it suddenly stopped. I investigated it a little and can  
>> track it down
>> to the fact that the weblcient does not store the new filters in the
>> users.prefs file. The filter rules on the server are actually correctly
>> updated. Did you resolve your problem? If yes how?
>>
>> Gunnar if you are reading this, do you have any clues?
>
> I'm definitely reading this and will look into it :)
>
> Just a little bit busy at the moment so my response rates are  
> somewhat  slowed down. Hope to improve that soon again.

I experience the same problem, I created all my filter rules with  
Ingo, saved, the sieve script was generated fine. But the settings do  
not seem to be saved to the config so the configuration shown in Ingo  
does not list any of my custom filters anymore after logging out.


Carsten



From alar.sing at err.ee  Wed May 13 20:20:45 2009
From: alar.sing at err.ee (Alar Sing)
Date: Wed, 13 May 2009 21:20:45 +0300
Subject: Upgrade on Suse 10.3 success
In-Reply-To: <20090513103153.13911upplyseryio@www.inovox.de>
References: <20090507104834.17243gznb3z61eas@www.inovox.de>
	<200905072148.51890.ml@radoeka.nl> <4A035291.9000106@cburghardt.com>
	<200905122112.00202.ml@radoeka.nl>
	<20090513103153.13911upplyseryio@www.inovox.de>
Message-ID: <20090513212045.80145xdgao73j88w@mail.err.ee>


-- 
Lugupidamisega,
Alar Sing


Quoting Carsten Burghardt <carsten at cburghardt.com>:

>
> Zitat von Richard Bos <ml at radoeka.nl>:
>
>> Hi Carsten,
>>
>> Op donderdag 07 mei 2009 23:28:49 schreef Carsten Burghardt:
>>> The reason for the error is rather simple. You have something like this
>>> in the Horde config:
>>> $conf['tmpdir'] = dirname(__FILE__) . '/../tmp/';
>>>
>>> If that is opened during runtime the dirname is replaced with the config
>>> directory so it works. But if you open the Horde configuration page and
>>> have a look at the setting the dirname is replaced with
>>> /srv/www/htdocs/client/lib/Horde/. I assume this is because the
>>> config.php is included. So the replaced path that shows up is
>>> /srv/www/htdocs/client/lib/Horde/../tmp/ and that is wrong. When you
>>> save the configuration the wrong path is include. Why don't you use the
>>> kolab functionality to insert the path to Horde here?
>>
>> What do you mean with this?  To which kolab functionality are you referring?
>> I have no idea what this is about, as it is Alar who did the  
>> packaging of the
>> webclient.
>
> Well, the configuration files from Horde are generated by kolabconf
> and some variables are replaced so I would recommend to use that
> functionality to insert the path to Horde in that place and not to use
> that dirname(__FILE__) thingy. I don't know if Alar also reads this
> mailinglist.
>
Yes I read this list.
I found this threate  
http://lists.kde.org/?l=kroupware&m=123554768707814&w=2 that describes  
why you should not use horde admin interface.
That is why config directorys and config files of horde are not wwwrun  
writable also.



From ml at radoeka.nl  Wed May 13 23:47:12 2009
From: ml at radoeka.nl (Richard Bos)
Date: Wed, 13 May 2009 23:47:12 +0200
Subject: Upgrade on Suse 10.3 success
In-Reply-To: <20090513212045.80145xdgao73j88w@mail.err.ee>
References: <20090507104834.17243gznb3z61eas@www.inovox.de>
	<20090513103153.13911upplyseryio@www.inovox.de>
	<20090513212045.80145xdgao73j88w@mail.err.ee>
Message-ID: <200905132347.13345.ml@radoeka.nl>

Op woensdag 13 mei 2009 20:20:45 schreef Alar Sing:
> Quoting Carsten Burghardt <carsten at cburghardt.com>:
> > Zitat von Richard Bos <ml at radoeka.nl>:
> >> Hi Carsten,
> >>
> >> Op donderdag 07 mei 2009 23:28:49 schreef Carsten Burghardt:
> >>> The reason for the error is rather simple. You have something like this
> >>> in the Horde config:
> >>> $conf['tmpdir'] = dirname(__FILE__) . '/../tmp/';
> >>>
> >>> If that is opened during runtime the dirname is replaced with the
> >>> config directory so it works. But if you open the Horde configuration
> >>> page and have a look at the setting the dirname is replaced with
> >>> /srv/www/htdocs/client/lib/Horde/. I assume this is because the
> >>> config.php is included. So the replaced path that shows up is
> >>> /srv/www/htdocs/client/lib/Horde/../tmp/ and that is wrong. When you
> >>> save the configuration the wrong path is include. Why don't you use the
> >>> kolab functionality to insert the path to Horde here?
> >>
> >> What do you mean with this?  To which kolab functionality are you
> >> referring? I have no idea what this is about, as it is Alar who did the
> >> packaging of the
> >> webclient.
> >
> > Well, the configuration files from Horde are generated by kolabconf
> > and some variables are replaced so I would recommend to use that
> > functionality to insert the path to Horde in that place and not to use
> > that dirname(__FILE__) thingy. I don't know if Alar also reads this
> > mailinglist.
>
> Yes I read this list.
> I found this threate  
> http://lists.kde.org/?l=kroupware&m=123554768707814&w=2 that describes  
> why you should not use horde admin interface.
> That is why config directorys and config files of horde are not wwwrun  
> writable also.

Among many commits to cvs, I found those 2:
http://www.kolab.org/pipermail/kolab-commits/2009q2/009705.html
http://www.kolab.org/pipermail/kolab-commits/2009q2/009704.html
They are interesting as they change the horde config.php files, so they get 
controlled (it looks like) by kolabconf.  @Alar, do you apply the same 
treatment to the openSUSE version of the horde webclient?

-- 
Richard



From bud.golf4 at laposte.net  Thu May 14 11:28:11 2009
From: bud.golf4 at laposte.net (Benoit)
Date: Thu, 14 May 2009 11:28:11 +0200
Subject: problem with postfix.sum not updated
Message-ID: <4A0BE42B.7000901@laposte.net>

An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20090514/73a1df99/attachment.html

From albrecht.dress at lios-tech.com  Thu May 14 15:47:25 2009
From: albrecht.dress at lios-tech.com (Albrecht =?iso-8859-1?b?RHJl3w==?=)
Date: Thu, 14 May 2009 15:47:25 +0200
Subject: Kontact on Linux w/o kde
Message-ID: <1242308845.5203.0@pc-adr2>

Hi all,

I try to run Kontact on Ubuntu 9.04, but without a full kde  
installation, i.e. in a Gnome environment.  Ubuntu 9.04 comes  
withkontact 4:4.2.2-0ubuntu1.  Everything seems to run smoothly, with  
the following exceptions:

(1) clicking on a http uri in a mail results in a pop-up reading "Keine  
Verbindung zum Rechner xxx: Unknown error";
(2) Free/Busy lists simply don't work.  For each and every participant  
there is always a red bar.  The puzzling thing is that the Apache logs  
on the Kolab server say that kontact doesn't query the server.

I guess for (1) might be a config file/option which can be changed via  
the KDE control centre, but I don't want to install it.  Maybe someone  
can tell me how to create the file manually as to point to Firefox?

(2) could be a missing lib, or also something related to a uri handler?

Thanks in advance,
Albrecht.



From johnm at advocap.org  Thu May 14 16:02:35 2009
From: johnm at advocap.org (John McMonagle)
Date: Thu, 14 May 2009 09:02:35 -0500
Subject: Problem with acls migrating from cyrus imap.
In-Reply-To: <200905130907.33120.johnm@advocap.org>
References: <200905130907.33120.johnm@advocap.org>
Message-ID: <4A0C247B.6060505@advocap.org>

Did a simple test and it apears that the acls are defined in the 
cyrus.header files.

For example:
Cyrus mailbox header
"The best thing about this system was that it had lots of goals."
        --Jim Morris on Andrew
advocap.org!user.test   1513ee1e4424dbbc
Junk
test at advocap.org        lrswipcda       mailadm lrswipcda

I edited the last line and then ran cyrreconstruct.

Is this how to do it?
I doubt if I'm the first to migrate from a domain less cyrus installation.

John



John McMonagle wrote:
> Working on migrating our debian sarge cyrus mail to kolab 2.2.1.
>
> I'm having a problem getting the acls set.
>
> This is what I'm doing:
> Stop kolab
> /etc/init.d/kolab stop
> remove old mail spool
> rm  -fr /kolab/var/imapd/spool/domain/a/advocap.org/*/user/*
> rm /kolab/var/imapd/mailboxes.db
> sudo -u kolab-r rsync -aHe ssh --exclude cyrus.*  
> root at mail:/cyrus/spool/cyrus/mail/ /kolab/var/imapd/spool/domain/a/advocap.org
>
> ssh root at mail "sudo -u cyrus /usr/sbin/ctl_mboxlist -d" > /tmp/mboxlist.txt
>
> The next should be enhanced to get extra acls but  it should do it.
>
> awk 'BEGIN { FS = "\t" } ;{print "advocap.org!" $1 "\t" $2 "\t" 
> $3"@advocap.org" "\t" $4   }' /tmp/mboxlist.txt > /tmp/newmbox.txt
>
> Sample from old dump mboxlist.txt
> user.test       default test    lrswipcda       mailadm lrswipcda
> user.test.Drafts        default test    lrswipcda       mailadm lrswipcda
> user.test.Sent  default test    lrswipcda       mailadm lrswipcda
> user.test.Trash default test    lrswipcda       mailadm lrswipcda
>
> Sample from New newmbox.txt:
> advocap.org!user.test   default test at advocap.org        lrswipcda
> advocap.org!user.test.Drafts    default test at advocap.org        lrswipcda
> advocap.org!user.test.Sent      default test at advocap.org        lrswipcda
> advocap.org!user.test.Trash     default test at advocap.org        lrswipcda
>
> sudo -u kolab-r /kolab/bin/ctl_mboxlist -u < newmbox.txt
> ctl_mboxlis -d   looks OK after running
>
> advocap.org!user.test   0 default test  lrswipcda
> advocap.org!user.test.Drafts    0 default test  lrswipcda
> advocap.org!user.test.Sent      0 default test  lrswipcda
> advocap.org!user.test.Trash     0 default test  lrswipcda
>
> Shouldn't matter but want to disclose everything.
> sudo -u kolab-r rsync -aHe ssh  
> root at mail://var/lib/cyrus/user/ /kolab/var/imapd/domain/a/advocap.org/user
>
> find  /kolab/var/imapd/domain/a/advocap.org/user  -name "*.sub" -exec 
> sed -i 's/user\.\w*/&@advocap.org/' {} \;
>
> sudo  -u kolab-r /kolab/bin/mkimap
>
> sudo  -u kolab-r /kolab/bin/cyrreconstruct
> That does find all the mail boxes
>
> in cyradm
> lm user/test at advocap.org
> user/test at advocap.org (\HasChildren)
> lam user/test at advocap.org
> .....Nothing...
>
> If I add with sam it's ok.
>
> Am I missing something?
> Does ctl_mboxlist -u  not set acls?
>
> Thanks
>
> John
>
>
>
>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>   

-------------- next part --------------
A non-text attachment was scrubbed...
Name: johnm.vcf
Type: text/x-vcard
Size: 250 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20090514/cebd0858/johnm.bin

From liutauras.adomaitis at gmail.com  Thu May 14 22:49:43 2009
From: liutauras.adomaitis at gmail.com (Liutauras Adomaitis)
Date: Thu, 14 May 2009 23:49:43 +0300
Subject: Kolab installation problem with perl
Message-ID: <c1ec9ac0905141349s23d6266at221ad3df21a1b6e8@mail.gmail.com>

Hello,

I would like to report a problem with Kolab 2.2.1 installation.
- I met a problem, then openpkg was building perl package. The error was:

Making DynaLoader (static)
snip
opendir(./../../../../..): Permission denied at
../../lib/File/Spec/Unix.pm line 478
(sorry, full error message already lost in my browsing history, but I
can post it later if somebody is interested).

This error was solved, by applying patch (appended at the end of the
post). I could bypass this particular error by going to lib/Unix.pm
file and changing getcwd to cwd on the line 478, but then building
stops on the other file with the same error.
Is this a bug or something wrong with my installation?

One more thing - Kolab Wiki is referring to obmtool script, to edit it
by changing BUILDUSER variable to root if there is any permissions
problem, but there is no obmtool script. So probably wiki should be
updated.

Regards
Liutauras

--- lib/Cwd.pm  Tue Dec 18 10:47:07 2007
+++ lib/Cwd.pm.cwd      Thu Jan 24 12:33:29 2008
@@ -501,6 +501,11 @@
 sub _perl_abs_path
 {
     my $start = @_ ? shift : '.';
+
+    # this just returns a path down from /, without attempting to
+    # resolve .. or symlinks. It *may* be sufficient to build perl.
+    return $start =~ m!^/! ? $start : cwd() . '/' . $start;
+
     my($dotdots, $cwd, @pst, @cst, $dir, @tst);

     unless (@cst = stat( $start ))



From liutauras.adomaitis at gmail.com  Fri May 15 09:00:18 2009
From: liutauras.adomaitis at gmail.com (Liutauras Adomaitis)
Date: Fri, 15 May 2009 10:00:18 +0300
Subject: Compiling Kolab 2.2.1 and php problem
Message-ID: <c1ec9ac0905150000h6d500648k134818468ff0e5d6@mail.gmail.com>

Hi there,

after a long waiting of build process to finish I got an error:
/kolab/RPM/TMP/php-5.2.8/main/reentrancy.c: In function 'php_readdir_r':
/kolab/RPM/TMP/php-5.2.8/main/reentrancy.c:139: error: too few
arguments to function 'readdir_r'
make: *** [main/reentrancy.lo] Error 1
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.68015 (%build)
    Bad exit status from /kolab/RPM/TMP/rpm-tmp.68015 (%build)


RPM build errors:
Command exited with non-zero status 1


any ideas anyone?

Thanks
Liutauras



From aspineux at gmail.com  Fri May 15 12:58:29 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Fri, 15 May 2009 12:58:29 +0200
Subject: Compiling Kolab 2.2.1 and php problem
In-Reply-To: <c1ec9ac0905150000h6d500648k134818468ff0e5d6@mail.gmail.com>
References: <c1ec9ac0905150000h6d500648k134818468ff0e5d6@mail.gmail.com>
Message-ID: <71fe4e760905150358r5df408bbm62bf731be348df59@mail.gmail.com>

On Fri, May 15, 2009 at 9:00 AM, Liutauras Adomaitis
<liutauras.adomaitis at gmail.com> wrote:
> Hi there,
>
> after a long waiting of build process to finish I got an error:
> /kolab/RPM/TMP/php-5.2.8/main/reentrancy.c: In function 'php_readdir_r':
> /kolab/RPM/TMP/php-5.2.8/main/reentrancy.c:139: error: too few
> arguments to function 'readdir_r'
> make: *** [main/reentrancy.lo] Error 1
> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.68015 (%build)
> ? ?Bad exit status from /kolab/RPM/TMP/rpm-tmp.68015 (%build)
>
>
> RPM build errors:
> Command exited with non-zero status 1
>
>
> any ideas anyone?


This could help a lot to know your OS version and gcc !

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



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



From liutauras.adomaitis at gmail.com  Fri May 15 14:39:56 2009
From: liutauras.adomaitis at gmail.com (Liutauras Adomaitis)
Date: Fri, 15 May 2009 15:39:56 +0300
Subject: Compiling Kolab 2.2.1 and php problem
In-Reply-To: <71fe4e760905150358r5df408bbm62bf731be348df59@mail.gmail.com>
References: <c1ec9ac0905150000h6d500648k134818468ff0e5d6@mail.gmail.com>
	<71fe4e760905150358r5df408bbm62bf731be348df59@mail.gmail.com>
Message-ID: <c1ec9ac0905150539l50b8f67yd0509cc1a7683b0a@mail.gmail.com>

On Fri, May 15, 2009 at 1:58 PM, Alain Spineux <aspineux at gmail.com> wrote:
> On Fri, May 15, 2009 at 9:00 AM, Liutauras Adomaitis
> <liutauras.adomaitis at gmail.com> wrote:
>> Hi there,
>>
>> after a long waiting of build process to finish I got an error:
>> /kolab/RPM/TMP/php-5.2.8/main/reentrancy.c: In function 'php_readdir_r':
>> /kolab/RPM/TMP/php-5.2.8/main/reentrancy.c:139: error: too few
>> arguments to function 'readdir_r'
>> make: *** [main/reentrancy.lo] Error 1
>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.68015 (%build)
>> ? ?Bad exit status from /kolab/RPM/TMP/rpm-tmp.68015 (%build)
>>
>>
>> RPM build errors:
>> Command exited with non-zero status 1
>>
>>
>> any ideas anyone?
>
>
> This could help a lot to know your OS version and gcc !
>

Hi,

I'm not openpkg user, but I thought that everything is build with
openpkg packages and does depend on OS packages only for building
openpkg, then all the src rpms shipped with Kolab are build on openpkg

uname -a
Linux PBL-kolab 2.6.29.1-server-4mnb #1 SMP Mon Apr 20 20:10:24 EDT
2009 i686 Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz GNU/Linux

[root at PBL-kolab ~]# gcc --version
gcc (GCC) 4.3.2
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[root at PBL-kolab ~]# cat /etc/redhat-release
Mandriva Linux release 2009.1 (Official) for i586

This a PV guest on
Linux PBL-xendom0 2.6.18.8-xen-3.3.1-2mdv #1 SMP Wed Feb 4 08:51:02
EST 2009 x86_64 Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz
GNU/Linux

I have an impression, that my previous post about perl build and the
patch to solve it are from the same problem, because they both are
about accessing directories.

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



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

Hi!

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

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

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

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

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

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

You can check the integrity of the downloaded files with:

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

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

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

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

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

Regards,
Thomas Arendsen Hein

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

From thomas at intevation.de  Fri May 15 17:11:15 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 15 May 2009 17:11:15 +0200
Subject: problem with postfix.sum not updated
In-Reply-To: <4A0BE42B.7000901@laposte.net>
References: <4A0BE42B.7000901@laposte.net>
Message-ID: <20090515151115.GP31326.thomas@intevation.de>

* Benoit <bud.golf4 at laposte.net> [20090514 11:28]:
>    i have a problem since February, before i was reading sometimes the file postfix.sum to
>    see if all was working good, especially with dns blacklist. but since February the file
>    postfix.sum is not updated:
>    [root at mail log]# pwd
>    /kolab/var/postfix/log
>    [root at mail log]# ls -l
>    total 692112
>    -rw-r--r--  1 kolab kolab 695759104 mai 14 11:17 postfix.log
>    -rw-r--r--  1 kolab kolab   8560282 fév 10 00:41 postfix.log.0
>    -rw-r--r--  1 kolab kolab    128503 fév 10 00:00 postfix.log.1.bz2
>    -rw-r--r--  1 kolab kolab    397342 fév  9 00:00 postfix.log.2.bz2
>    -rw-r--r--  1 kolab kolab    396859 fév  7 00:00 postfix.log.3.bz2
>    -rw-r--r--  1 kolab kolab    389848 fév  6 00:00 postfix.log.4.bz2
>    -rw-r--r--  1 kolab kolab    415329 fév  5 00:00 postfix.log.5.bz2
>    -rw-r--r--  1 kolab kolab    460484 fév  4 00:00 postfix.log.6.bz2
>    -rw-r--r--  1 kolab kolab     96001 fév  3 00:00 postfix.log.7.bz2
>    -rw-r--r--  1 kolab kolab    418403 fév  1 00:00 postfix.log.8.bz2
>    -rw-r--r--  1 kolab kolab    436898 jan 31 00:00 postfix.log.9.bz2
>    -rw-r--r--  1 kolab kolab    222218 fév 10 00:00 postfix.sum
>    -rw-r--r--  1 kolab kolab     18554 fév 10 00:00 postfix.sum.0.bz2
>    -rw-r--r--  1 kolab kolab     21707 fév  9 00:00 postfix.sum.1.bz2
>    -rw-r--r--  1 kolab kolab     29375 fév  8 00:00 postfix.sum.2.bz2
>    -rw-r--r--  1 kolab kolab     25318 fév  7 00:00 postfix.sum.3.bz2
>    -rw-r--r--  1 kolab kolab     21458 fév  6 00:00 postfix.sum.4.bz2
>    -rw-r--r--  1 kolab kolab     24324 fév  5 00:00 postfix.sum.5.bz2
>    -rw-r--r--  1 kolab kolab     29712 fév  4 00:00 postfix.sum.6.bz2
>    -rw-r--r--  1 kolab kolab     15530 fév  3 00:00 postfix.sum.7.bz2
>    -rw-r--r--  1 kolab kolab     33684 fév  2 00:00 postfix.sum.8.bz2
>    -rw-r--r--  1 kolab kolab     27643 fév  1 00:00 postfix.sum.9.bz2
>    [root at mail log]#
>    did you know this problem??

I haven't seen this problem on other servers, additionally it seems
as if your postfix.log isn't rotated, too.

Check the %daily section of /kolab/etc/rc.d/rc.postfix

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

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

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

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

Happy hacking ;-)

Martin Zbo?il



From kloecker at kde.org  Fri May 15 22:52:40 2009
From: kloecker at kde.org (Ingo =?iso-8859-1?q?Kl=F6cker?=)
Date: Fri, 15 May 2009 22:52:40 +0200
Subject: Kontact on Linux w/o kde
In-Reply-To: <1242308845.5203.0@pc-adr2>
References: <1242308845.5203.0@pc-adr2>
Message-ID: <200905152252.45421@thufir.ingo-kloecker.de>

On Thursday 14 May 2009, Albrecht Dre? wrote:
> Hi all,
>
> I try to run Kontact on Ubuntu 9.04, but without a full kde
> installation, i.e. in a Gnome environment.  Ubuntu 9.04 comes
> withkontact 4:4.2.2-0ubuntu1.  Everything seems to run smoothly, with
> the following exceptions:
>
> (1) clicking on a http uri in a mail results in a pop-up reading
> "Keine Verbindung zum Rechner xxx: Unknown error";
> (2) Free/Busy lists simply don't work.  For each and every
> participant there is always a red bar.  The puzzling thing is that
> the Apache logs on the Kolab server say that kontact doesn't query
> the server.
>
> I guess for (1) might be a config file/option which can be changed
> via the KDE control centre, but I don't want to install it.  Maybe
> someone can tell me how to create the file manually as to point to
> Firefox?

Hmm. By default, KDE will choose the application best suitable for the 
type of file the URL points to. This decision is made based on the 
installed .desktop files. Maybe there's something wrong.

To use Firefox for all URLs add
BrowserApplication[$e]=!/usr/bin/firefox
to the [General] section of ~/.kde/share/config/kdeglobals


Regards,
Ingo
-------------- 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-users/attachments/20090515/7f172a39/attachment.bin

From aspineux at gmail.com  Fri May 15 23:00:42 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Fri, 15 May 2009 23:00:42 +0200
Subject: Compiling Kolab 2.2.1 and php problem
In-Reply-To: <c1ec9ac0905150539l50b8f67yd0509cc1a7683b0a@mail.gmail.com>
References: <c1ec9ac0905150000h6d500648k134818468ff0e5d6@mail.gmail.com>
	<71fe4e760905150358r5df408bbm62bf731be348df59@mail.gmail.com>
	<c1ec9ac0905150539l50b8f67yd0509cc1a7683b0a@mail.gmail.com>
Message-ID: <71fe4e760905151400h7eb74f17r81ca62f67b74873b@mail.gmail.com>

On Fri, May 15, 2009 at 2:39 PM, Liutauras Adomaitis
<liutauras.adomaitis at gmail.com> wrote:
> On Fri, May 15, 2009 at 1:58 PM, Alain Spineux <aspineux at gmail.com> wrote:
>> On Fri, May 15, 2009 at 9:00 AM, Liutauras Adomaitis
>> <liutauras.adomaitis at gmail.com> wrote:
>>> Hi there,
>>>
>>> after a long waiting of build process to finish I got an error:
>>> /kolab/RPM/TMP/php-5.2.8/main/reentrancy.c: In function 'php_readdir_r':
>>> /kolab/RPM/TMP/php-5.2.8/main/reentrancy.c:139: error: too few
>>> arguments to function 'readdir_r'
>>> make: *** [main/reentrancy.lo] Error 1
>>> error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.68015 (%build)
>>> ? ?Bad exit status from /kolab/RPM/TMP/rpm-tmp.68015 (%build)
>>>
>>>
>>> RPM build errors:
>>> Command exited with non-zero status 1
>>>
>>>
>>> any ideas anyone?
>>
>>
>> This could help a lot to know your OS version and gcc !
>>
>
> Hi,
>
> I'm not openpkg user, but I thought that everything is build with
> openpkg packages and does depend on OS packages only for building
> openpkg, then all the src rpms shipped with Kolab are build on openpkg
>
> uname -a
> Linux PBL-kolab 2.6.29.1-server-4mnb #1 SMP Mon Apr 20 20:10:24 EDT
> 2009 i686 Intel(R) Xeon(R) CPU ? ? ? ? ? E5405 ?@ 2.00GHz GNU/Linux
>
> [root at PBL-kolab ~]# gcc --version
> gcc (GCC) 4.3.2
> Copyright (C) 2008 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. ?There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> [root at PBL-kolab ~]# cat /etc/redhat-release
> Mandriva Linux release 2009.1 (Official) for i586
>
> This a PV guest on
> Linux PBL-xendom0 2.6.18.8-xen-3.3.1-2mdv #1 SMP Wed Feb 4 08:51:02
> EST 2009 x86_64 Intel(R) Xeon(R) CPU ? ? ? ? ? E5405 ?@ 2.00GHz
> GNU/Linux
>
> I have an impression, that my previous post about perl build and the
> patch to solve it are from the same problem, because they both are
> about accessing directories.

Read this

http://www.kolab.org/pipermail/kolab-users/2009-April/009678.html


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



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



From aspineux at gmail.com  Fri May 15 23:08:46 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Fri, 15 May 2009 23:08:46 +0200
Subject: Problem with acls migrating from cyrus imap.
In-Reply-To: <200905130907.33120.johnm@advocap.org>
References: <200905130907.33120.johnm@advocap.org>
Message-ID: <71fe4e760905151408t33bc1d4uff8ce5c549e33063@mail.gmail.com>

On Wed, May 13, 2009 at 4:07 PM, John McMonagle <johnm at advocap.org> wrote:
> Working on migrating our debian sarge cyrus mail to kolab 2.2.1.
>
> I'm having a problem getting the acls set.
>
> This is what I'm doing:
> Stop kolab
> /etc/init.d/kolab stop
> remove old mail spool
> rm ?-fr /kolab/var/imapd/spool/domain/a/advocap.org/*/user/*
> rm /kolab/var/imapd/mailboxes.db
> sudo -u kolab-r rsync -aHe ssh --exclude cyrus.*
> root at mail:/cyrus/spool/cyrus/mail/ /kolab/var/imapd/spool/domain/a/advocap.org
>
> ssh root at mail "sudo -u cyrus /usr/sbin/ctl_mboxlist -d" > /tmp/mboxlist.txt
>
> The next should be enhanced to get extra acls but ?it should do it.
>
> awk 'BEGIN { FS = "\t" } ;{print "advocap.org!" $1 "\t" $2 "\t"
> $3"@advocap.org" "\t" $4 ? }' /tmp/mboxlist.txt > /tmp/newmbox.txt
>
> Sample from old dump mboxlist.txt
> user.test ? ? ? default test ? ?lrswipcda ? ? ? mailadm lrswipcda
> user.test.Drafts ? ? ? ?default test ? ?lrswipcda ? ? ? mailadm lrswipcda
> user.test.Sent ?default test ? ?lrswipcda ? ? ? mailadm lrswipcda
> user.test.Trash default test ? ?lrswipcda ? ? ? mailadm lrswipcda
>
> Sample from New newmbox.txt:
> advocap.org!user.test ? default test at advocap.org ? ? ? ?lrswipcda
> advocap.org!user.test.Drafts ? ?default test at advocap.org ? ? ? ?lrswipcda
> advocap.org!user.test.Sent ? ? ?default test at advocap.org ? ? ? ?lrswipcda
> advocap.org!user.test.Trash ? ? default test at advocap.org ? ? ? ?lrswipcda
>
> sudo -u kolab-r /kolab/bin/ctl_mboxlist -u < newmbox.txt
> ctl_mboxlis -d ? looks OK after running
>
> advocap.org!user.test ? 0 default test ?lrswipcda
> advocap.org!user.test.Drafts ? ?0 default test ?lrswipcda
> advocap.org!user.test.Sent ? ? ?0 default test ?lrswipcda
> advocap.org!user.test.Trash ? ? 0 default test ?lrswipcda
>
> Shouldn't matter but want to disclose everything.
> sudo -u kolab-r rsync -aHe ssh
> root at mail://var/lib/cyrus/user/ /kolab/var/imapd/domain/a/advocap.org/user
>
> find ?/kolab/var/imapd/domain/a/advocap.org/user ?-name "*.sub" -exec
> sed -i 's/user\.\w*/&@advocap.org/' {} \;
>
> sudo ?-u kolab-r /kolab/bin/mkimap
>
> sudo ?-u kolab-r /kolab/bin/cyrreconstruct
> That does find all the mail boxes
>
> in cyradm
> lm user/test at advocap.org
> user/test at advocap.org (\HasChildren)
> lam user/test at advocap.org
> .....Nothing...
>
> If I add with sam it's ok.
>
> Am I missing something?
> Does ctl_mboxlist -u ?not set acls?

acl are stored in two places  I thing

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



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



From aspineux at gmail.com  Fri May 15 23:21:28 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Fri, 15 May 2009 23:21:28 +0200
Subject: Problem with acls migrating from cyrus imap.
In-Reply-To: <4A0C247B.6060505@advocap.org>
References: <200905130907.33120.johnm@advocap.org>
	<4A0C247B.6060505@advocap.org>
Message-ID: <71fe4e760905151421x43a3e30fy8e616cc27d615000@mail.gmail.com>

2009/5/14 John McMonagle <johnm at advocap.org>:
> Did a simple test and it apears that the acls are defined in the
> cyrus.header files.
>
> For example:
> Cyrus mailbox header
> "The best thing about this system was that it had lots of goals."
> ? ? ? --Jim Morris on Andrew
> advocap.org!user.test ? 1513ee1e4424dbbc
> Junk
> test at advocap.org ? ? ? ?lrswipcda ? ? ? mailadm lrswipcda
>
> I edited the last line and then ran cyrreconstruct.
>
> Is this how to do it?
> I doubt if I'm the first to migrate from a domain less cyrus installation.
>
> John

If you are not switching/restoring on an identical version/system then
you should use imapsync

Regards

>
>
>
> John McMonagle wrote:
>>
>> Working on migrating our debian sarge cyrus mail to kolab 2.2.1.
>>
>> I'm having a problem getting the acls set.
>>
>> This is what I'm doing:
>> Stop kolab
>> /etc/init.d/kolab stop
>> remove old mail spool
>> rm ?-fr /kolab/var/imapd/spool/domain/a/advocap.org/*/user/*
>> rm /kolab/var/imapd/mailboxes.db
>> sudo -u kolab-r rsync -aHe ssh --exclude cyrus.*
>> ?root at mail:/cyrus/spool/cyrus/mail/
>> /kolab/var/imapd/spool/domain/a/advocap.org
>>
>> ssh root at mail "sudo -u cyrus /usr/sbin/ctl_mboxlist -d" >
>> /tmp/mboxlist.txt
>>
>> The next should be enhanced to get extra acls but ?it should do it.
>>
>> awk 'BEGIN { FS = "\t" } ;{print "advocap.org!" $1 "\t" $2 "\t"
>> $3"@advocap.org" "\t" $4 ? }' /tmp/mboxlist.txt > /tmp/newmbox.txt
>>
>> Sample from old dump mboxlist.txt
>> user.test ? ? ? default test ? ?lrswipcda ? ? ? mailadm lrswipcda
>> user.test.Drafts ? ? ? ?default test ? ?lrswipcda ? ? ? mailadm lrswipcda
>> user.test.Sent ?default test ? ?lrswipcda ? ? ? mailadm lrswipcda
>> user.test.Trash default test ? ?lrswipcda ? ? ? mailadm lrswipcda
>>
>> Sample from New newmbox.txt:
>> advocap.org!user.test ? default test at advocap.org ? ? ? ?lrswipcda
>> advocap.org!user.test.Drafts ? ?default test at advocap.org ? ? ? ?lrswipcda
>> advocap.org!user.test.Sent ? ? ?default test at advocap.org ? ? ? ?lrswipcda
>> advocap.org!user.test.Trash ? ? default test at advocap.org ? ? ? ?lrswipcda
>>
>> sudo -u kolab-r /kolab/bin/ctl_mboxlist -u < newmbox.txt
>> ctl_mboxlis -d ? looks OK after running
>>
>> advocap.org!user.test ? 0 default test ?lrswipcda
>> advocap.org!user.test.Drafts ? ?0 default test ?lrswipcda
>> advocap.org!user.test.Sent ? ? ?0 default test ?lrswipcda
>> advocap.org!user.test.Trash ? ? 0 default test ?lrswipcda
>>
>> Shouldn't matter but want to disclose everything.
>> sudo -u kolab-r rsync -aHe ssh ?root at mail://var/lib/cyrus/user/
>> /kolab/var/imapd/domain/a/advocap.org/user
>>
>> find ?/kolab/var/imapd/domain/a/advocap.org/user ?-name "*.sub" -exec sed
>> -i 's/user\.\w*/&@advocap.org/' {} \;
>>
>> sudo ?-u kolab-r /kolab/bin/mkimap
>>
>> sudo ?-u kolab-r /kolab/bin/cyrreconstruct
>> That does find all the mail boxes
>>
>> in cyradm
>> lm user/test at advocap.org
>> user/test at advocap.org (\HasChildren)
>> lam user/test at advocap.org
>> .....Nothing...
>>
>> If I add with sam it's ok.
>>
>> Am I missing something?
>> Does ctl_mboxlist -u ?not set acls?
>>
>> Thanks
>>
>> John
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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
>
>



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



From Roessler at FuH-E.de  Mon May 18 11:10:51 2009
From: Roessler at FuH-E.de (=?ISO-8859-15?Q?Christian_R=F6=DFler?=)
Date: Mon, 18 May 2009 11:10:51 +0200
Subject: Update to 2.2.2: kolabd - failed dependencies
Message-ID: <4A11261B.2030304@FuH-E.de>

Good morning,

when updating to 2.2.2 I get the following result:

/tmp/install-kolab.5629.27893.232.29026/kolabd-2.2.2-20090514.src.rpm ::::
error: Failed dependencies:
        php::with_imap = yes is needed by kolabd-2.2.2-20090514
        php::with_ssl = yes is needed by kolabd-2.2.2-20090514
        php::with_zlib = yes is needed by kolabd-2.2.2-20090514
        php::with_imap_annotate = yes is needed by kolabd-2.2.2-20090514
        php::with_imap_myrights = yes is needed by kolabd-2.2.2-20090514
        php::with_spl = yes is needed by kolabd-2.2.2-20090514
        apache-php::with_imap = yes is needed by kolabd-2.2.2-20090514
        apache-php::with_ssl = yes is needed by kolabd-2.2.2-20090514
        apache-php::with_zlib = yes is needed by kolabd-2.2.2-20090514
        apache-php::with_imap_annotate = yes is needed by
kolabd-2.2.2-20090514
        apache-php::with_imap_myrights = yes is needed by
kolabd-2.2.2-20090514

...so I am just fishing for a quick hint. Well, anyone has a hint?

Best regards, Christian



From aspineux at gmail.com  Mon May 18 12:17:21 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 18 May 2009 12:17:21 +0200
Subject: Update to 2.2.2: kolabd - failed dependencies
In-Reply-To: <4A11261B.2030304@FuH-E.de>
References: <4A11261B.2030304@FuH-E.de>
Message-ID: <71fe4e760905180317x31b0c413p3d65dc5652836abb@mail.gmail.com>

On Mon, May 18, 2009 at 11:10 AM, Christian R??ler <Roessler at fuh-e.de> wrote:
> Good morning,
>
> when updating to 2.2.2 I get the following result:
>
> /tmp/install-kolab.5629.27893.232.29026/kolabd-2.2.2-20090514.src.rpm ::::
> error: Failed dependencies:
> ? ? ? ?php::with_imap = yes is needed by kolabd-2.2.2-20090514
> ? ? ? ?php::with_ssl = yes is needed by kolabd-2.2.2-20090514
> ? ? ? ?php::with_zlib = yes is needed by kolabd-2.2.2-20090514
> ? ? ? ?php::with_imap_annotate = yes is needed by kolabd-2.2.2-20090514
> ? ? ? ?php::with_imap_myrights = yes is needed by kolabd-2.2.2-20090514
> ? ? ? ?php::with_spl = yes is needed by kolabd-2.2.2-20090514
> ? ? ? ?apache-php::with_imap = yes is needed by kolabd-2.2.2-20090514
> ? ? ? ?apache-php::with_ssl = yes is needed by kolabd-2.2.2-20090514
> ? ? ? ?apache-php::with_zlib = yes is needed by kolabd-2.2.2-20090514
> ? ? ? ?apache-php::with_imap_annotate = yes is needed by
> kolabd-2.2.2-20090514
> ? ? ? ?apache-php::with_imap_myrights = yes is needed by
> kolabd-2.2.2-20090514
>
> ...so I am just fishing for a quick hint. Well, anyone has a hint?

When you build an rpm package, you can set some options  like this

/kolab/bin/openpkg rpm --rebuild youpackage --define "with_ssl yes"

The pakages where build without the options required by other pakages !


>
> Best regards, Christian
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



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



From Roessler at FuH-E.de  Mon May 18 12:25:50 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Mon, 18 May 2009 12:25:50 +0200
Subject: Kolab MySQL Integration
In-Reply-To: <200905171642.03771.bbuehler@bbm-bbmicro.ch>
References: <200904251500.40095.bbuehler@bbm-bbmicro.ch>	<200904301724.54907.bbuehler@bbm-bbmicro.ch>	<20090513090225.GA7927.thomas@intevation.de>
	<200905171642.03771.bbuehler@bbm-bbmicro.ch>
Message-ID: <4A1137AE.9040502@FuH-E.de>

Hallo an alle,

ich bin ja dem Ziel der MySQL-Integration ein gutes St?ck n?hergekommen;
ich h?nge nur noch daran, da? imap und imap-ssl nicht in php und
apache-php einkompiliert werden wollen.

Ich habe daher mal meine bisherige Vorgehensweise in einen Wiki-Artikel
eingeschrieben:
https://wiki.kolab.org/index.php/Kolab2_Integration_with_MySQL.
Vielleicht ist der n?tzlich? Ich bitte nat?rlich um Verbesserung; mit
diesem Wiki bin ich nicht so fit...


I came a bit closer to the target of a MySQL-integration; I just have
problems with compiling imap and imap-ssl into php and apache-php.

So I made a wiki article for that which reflects my approach until now:
https://wiki.kolab.org/index.php/Kolab2_Integration_with_MySQL - perhaps
others can use it. Please amend it.

Viele Gr??e / best regards,
Christian



From Roessler at FuH-E.de  Mon May 18 12:43:36 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Mon, 18 May 2009 12:43:36 +0200
Subject: Update to 2.2.2: kolabd - failed dependencies
In-Reply-To: <71fe4e760905180317x31b0c413p3d65dc5652836abb@mail.gmail.com>
References: <4A11261B.2030304@FuH-E.de>
	<71fe4e760905180317x31b0c413p3d65dc5652836abb@mail.gmail.com>
Message-ID: <4A113BD8.9090704@FuH-E.de>

Alain Spineux schrieb:

>> when updating to 2.2.2 I get the following result:
>> /tmp/install-kolab.5629.27893.232.29026/kolabd-2.2.2-20090514.src.rpm ::::
>> error: Failed dependencies:
>>        php::with_imap = yes is needed by kolabd-2.2.2-20090514
>>        [some more dependencies]
>> ...so I am just fishing for a quick hint. Well, anyone has a hint?
> When you build an rpm package, you can set some options  like this
> /kolab/bin/openpkg rpm --rebuild youpackage --define "with_ssl yes"
> The pakages where build without the options required by other pakages !

well, yes; but then I enter the option hell again (as i had massive
problems when compiling mysql into php and apache-php - while my options
were recognized, many other options 'fell beneath the table', and I
ended having to insert _every_ option the way you mentioned - not
knowing until now how to insert the options for imap and imap-ssl.

And, this being an update (from 2.2.1 to 2.2.2): Is this really
necessary? Would it not be a better way to mend the install script
and/or 00INDEX.rdf? In other words: Could it not be that this is *ahem*
an updating bug - am I the only one having this problem while updating?

Best regards, Christian

PS. Of course I will 'externally re-option' it if there is no other way.




From bernhard at intevation.de  Mon May 18 10:44:25 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 18 May 2009 10:44:25 +0200
Subject: shared folders and calendars as of 2.2.1
In-Reply-To: <7907AE10BB50DD4F840E76527D27EF19029F6560@entmail.domain.austinent.com>
References: <7907AE10BB50DD4F840E76527D27EF19029F6560@entmail.domain.austinent.com>
Message-ID: <200905181044.26575.bernhard@intevation.de>

On Monday 11 May 2009, Lucas Hendricks wrote:
> >Note the name clash: a shared folder usually is something that a user gets
> >permission to. The web admin only can create accountless folders
> >and we do not recommend to use them.
>
> So using the shared folders feature of the webadmin is not recommended?  I
> should just be creating the folders via horde/kontact and sharing them
> through those programs, instead?

Yes, that is what I recommend.
It also means you have a clear owner of the folder.

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

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

From bernhard at intevation.de  Mon May 18 10:47:25 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 18 May 2009 10:47:25 +0200
Subject: Kontact on Linux w/o kde
In-Reply-To: <1242308845.5203.0@pc-adr2>
References: <1242308845.5203.0@pc-adr2>
Message-ID: <200905181047.27295.bernhard@intevation.de>

On Thursday 14 May 2009, Albrecht Dre? wrote:
> Ubuntu 9.04 comes  
> withkontact 4:4.2.2-0ubuntu1.  Everything seems to run smoothly, with  
> the following exceptions:

> (2) Free/Busy lists simply don't work.  For each and every participant  
> there is always a red bar.  The puzzling thing is that the Apache logs  
> on the Kolab server say that kontact doesn't query the server.

> (2) could be a missing lib, or also something related to a uri handler?

Best would be to have a real enterprise4 package for Kontact on Ubuntu.
(Volunteers welcome, subscribe to kolab-devel@ and help. :) )


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

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

From aspineux at gmail.com  Mon May 18 14:57:51 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 18 May 2009 14:57:51 +0200
Subject: Update to 2.2.2: kolabd - failed dependencies
In-Reply-To: <4A113BD8.9090704@FuH-E.de>
References: <4A11261B.2030304@FuH-E.de>
	<71fe4e760905180317x31b0c413p3d65dc5652836abb@mail.gmail.com>
	<4A113BD8.9090704@FuH-E.de>
Message-ID: <71fe4e760905180557v70d737e3v3f8eb6f8c905a0fb@mail.gmail.com>

On Mon, May 18, 2009 at 12:43 PM, Christian R??ler <Roessler at fuh-e.de> wrote:
> Alain Spineux schrieb:
>
>>> when updating to 2.2.2 I get the following result:
>>> /tmp/install-kolab.5629.27893.232.29026/kolabd-2.2.2-20090514.src.rpm ::::
>>> error: Failed dependencies:
>>> ? ? ? ?php::with_imap = yes is needed by kolabd-2.2.2-20090514
>>> ? ? ? ?[some more dependencies]
>>> ...so I am just fishing for a quick hint. Well, anyone has a hint?
>> When you build an rpm package, you can set some options ?like this
>> /kolab/bin/openpkg rpm --rebuild youpackage --define "with_ssl yes"
>> The pakages where build without the options required by other pakages !
>
> well, yes; but then I enter the option hell again (as i had massive
> problems when compiling mysql into php and apache-php - while my options
> were recognized, many other options 'fell beneath the table', and I
> ended having to insert _every_ option the way you mentioned - not
> knowing until now how to insert the options for imap and imap-ssl.
>
> And, this being an update (from 2.2.1 to 2.2.2): Is this really
> necessary? Would it not be a better way to mend the install script
> and/or 00INDEX.rdf? In other words: Could it not be that this is *ahem*
> an updating bug - am I the only one having this problem while updating?
>

Did you follow the instruction in 1st.README ?

> Best regards, Christian
>
> PS. Of course I will 'externally re-option' it if there is no other way.
>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



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



From Roessler at FuH-E.de  Mon May 18 15:00:32 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Mon, 18 May 2009 15:00:32 +0200
Subject: Update to 2.2.2: kolabd - failed dependencies
In-Reply-To: <71fe4e760905180317x31b0c413p3d65dc5652836abb@mail.gmail.com>
References: <4A11261B.2030304@FuH-E.de>
	<71fe4e760905180317x31b0c413p3d65dc5652836abb@mail.gmail.com>
Message-ID: <4A115BF0.7010002@FuH-E.de>

Alain Spineux schrieb:

>> when updating to 2.2.2 I get the following result:
>> /tmp/install-kolab.5629.27893.232.29026/kolabd-2.2.2-20090514.src.rpm ::::
>> error: Failed dependencies:
>>        php::with_imap = yes is needed by kolabd-2.2.2-20090514
>>        [etc. usw. ff.]
>> ...so I am just fishing for a quick hint. Well, anyone has a hint?
> When you build an rpm package, you can set some options  like this
> /kolab/bin/openpkg rpm --rebuild youpackage --define "with_ssl yes"

Yes, as I feared this brings me into dependency declaration hell - if
rebuilt just with --define "with_xxx yes" (xxx=above mentioned missing
dependencies) many other will go amiss.

So, if others have the same problem: Using

--define "with_imap yes" --define "with_ssl yes" --define "with_zlib
yes" --define "with_imap_annotate yes" --define "with_imap_myrights yes"
--define "with_spl yes" --define "with_gettext yes" --define "with_dom
yes" --define "with_mcrypt yes" --define "with_iconv yes" --define
"with_mbstring yes" --define "with_mbregex yes" --define "with_gd yes"
--define "with_ctype yes" --define "with_openldap yes" --define
"with_mhash yes" --define "with_bdb yes" --define "with_pear yes"
--define "with_xml yes" --define "with_mm yes" --define "with_sqlite yes"

...or the equivalent...

--with imap --with ssl --with zlib --with imap_annotate --with imap_myrights
 --with spl --with gettext --with dom --with mcrypt --with iconv --with
mbstring
 --with mbregex --with gd --with ctype --with openldap --with mhash
--with bdb
 --with pear --with xml  --with mm --with sqlite

...will (hopefully:) do the trick.

Now once again into the breach^apache_php... I will post the needed
options for apache_php too, if wanted.

But I cannot cease to wonder whether a new update script should do this
by itself.

Best regards,
Christian



From Roessler at FuH-E.de  Mon May 18 15:05:04 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Mon, 18 May 2009 15:05:04 +0200
Subject: Update to 2.2.2: kolabd - failed dependencies
In-Reply-To: <71fe4e760905180557v70d737e3v3f8eb6f8c905a0fb@mail.gmail.com>
References: <4A11261B.2030304@FuH-E.de>	
	<71fe4e760905180317x31b0c413p3d65dc5652836abb@mail.gmail.com>	
	<4A113BD8.9090704@FuH-E.de>
	<71fe4e760905180557v70d737e3v3f8eb6f8c905a0fb@mail.gmail.com>
Message-ID: <4A115D00.7060109@FuH-E.de>

Alain Spineux schrieb:

> Did you follow the instruction in 1st.README ?

Yes, of course - even printed it:

| Upgrade from 2.2.1 to 2.2.2
| ---------------------------
| Nothing special has to be done for this upgrade.

(Found that a bit funny:) )

Did also the bit about generating 00INDEX.rdf.

Best regards, Christian



From albrecht.dress at lios-tech.com  Mon May 18 15:27:25 2009
From: albrecht.dress at lios-tech.com (Albrecht =?iso-8859-15?q?Dre=DF?=)
Date: Mon, 18 May 2009 15:27:25 +0200
Subject: Kontact on Linux w/o kde
In-Reply-To: <200905181047.27295.bernhard@intevation.de>
References: <1242308845.5203.0@pc-adr2>
	<200905181047.27295.bernhard@intevation.de>
Message-ID: <200905181527.26022.albrecht.dress@lios-tech.com>

Am Montag 18 Mai 2009 10:47:25 schrieb Bernhard Reiter:
> Best would be to have a real enterprise4 package for Kontact on Ubuntu. (Volunteers welcome, subscribe to kolab-devel@ and help. :) )

Umm, yes.  ;-)  I found the folder http://apt.intevation.org/dists/lenny/enterprise4-unstable/source, and will give it a try on Jaunty, stay tuned, please...

Cheers, Albrecht.



From Roessler at FuH-E.de  Mon May 18 15:51:42 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Mon, 18 May 2009 15:51:42 +0200
Subject: Update to 2.2.2: kolabd - failed dependencies
In-Reply-To: <4A115BF0.7010002@FuH-E.de>
References: <4A11261B.2030304@FuH-E.de>	<71fe4e760905180317x31b0c413p3d65dc5652836abb@mail.gmail.com>
	<4A115BF0.7010002@FuH-E.de>
Message-ID: <4A1167EE.6010606@FuH-E.de>

Christian R??ler schrieb:

> Now once again into the breach^apache_php... I will post the needed
> options for apache_php too, if wanted.

To fulfil that, one may see below. I post both series of options
together for easier searching. One may keep in mind that no carriage
return should be there:

For php:

--define "with_imap yes" --define "with_ssl yes" --define "with_zlib
yes" --define "with_imap_annotate yes" --define "with_imap_myrights yes"
--define "with_spl yes" --define "with_gettext yes" --define "with_dom
yes" --define "with_mcrypt yes" --define "with_iconv yes" --define
"with_mbstring yes" --define "with_mbregex yes" --define "with_gd yes"
--define "with_ctype yes" --define "with_openldap yes" --define
"with_mhash yes" --define "with_bdb yes" --define "with_pear yes"
--define "with_xml yes" --define "with_mm yes" --define "with_sqlite yes"

For apache_php:

--define "with_imap yes" --define "with_ssl yes" --define "with_zlib
yes" --define "with_imap_annotate yes" --define "with_imap_myrights yes"
--define "with_gettext yes" --define "with_dom yes" --define
"with_mcrypt yes" --define "with_iconv yes" --define "with_mbstring yes"
--define "with_mbregex yes" --define "with_gd yes" --define "with_ctype
yes" --define "with_openldap yes" --define "with_mhash yes" --define
"with_bdb yes" --define "with_pear yes" --define "with_xml yes" --define
"with_mm yes" --define "with_sqlite yes"

These have worked for me - at least as far as I can see now. Now unto
MySQL, again.

Best regards, Christian



From kcaesar at hotmail.com  Mon May 18 19:00:00 2009
From: kcaesar at hotmail.com (kiser Caesar)
Date: Mon, 18 May 2009 19:00:00 +0200
Subject: Question about upgrade from 2.2.0 to 2.2.2
Message-ID: <BLU122-W471AF207A53EC97DD4467A35A0@phx.gbl>


Hello the list !

I just saw that kolab 2.2.2 is avaible.
Well after a quick read of

http://files.kolab.org/server/release/kolab-server-2.2.2/sources/1st.README

I see that I need to make some steps before upgrading to 2.2.2.

Can you confirm that I understand well ???

I explain. To upgrade to 2.2.2 from 2.2.0 I must install

2.2.1-beta1 > 2.2.1-rc1 > 2.2.1 then finaly 2.2.2

It's true ? And the only way ?


I'm waiting for your feedback,


Best regards,

_________________________________________________________________
Vous voulez savoir ce que vous pouvez faire avec le nouveau Windows Live?? Lancez-vous !
http://www.microsoft.com/windows/windowslive/default.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20090518/0e866226/attachment.html

From albrecht.dress at lios-tech.com  Mon May 18 20:28:39 2009
From: albrecht.dress at lios-tech.com (Albrecht =?iso-8859-1?b?RHJl3w==?=)
Date: Mon, 18 May 2009 20:28:39 +0200
Subject: Compile problems [was: Kontact on Linux w/o kde]
In-Reply-To: <200905181527.26022.albrecht.dress@lios-tech.com> (from
	albrecht.dress@lios-tech.com on Mon May 18 15:27:25 2009)
Message-ID: <1242671319.3469.0@antares>

Am 18.05.09 15:27 schrieb(en) Albrecht Dre?:
> Umm, yes.  ;-)  I found the folder  
> http://apt.intevation.org/dists/lenny/enterprise4-unstable/source,  
> and will give it a try on Jaunty, stay tuned, please...

Do I need a specific g++ version to compile these packages?  For  
kde4libs-4.1.1.enterprise4.0.20081104.879654/kde3support/kdeui/k3popupmenu.cpp,  
the build ejects with

/home/adress/source/kde4libs-4.1.1.enterprise4.0.20081104.879654/kde3support/kdeui/k3popupmenu.cpp:  
In member function 'virtual void  
K3PopupMenu::mouseReleaseEvent(QMouseEvent*)':
/home/adress/source/kde4libs-4.1.1.enterprise4.0.20081104.879654/kde3support/kdeui/k3popupmenu.cpp:391:  
error: ISO C++ says that these are ambiguous, even though the worst  
conversion for the first is better than the worst conversion for the  
second:
/home/adress/source/kde4libs-4.1.1.enterprise4.0.20081104.879654/kde3support/kdeui/k3popupmenu.cpp:391:  
note: candidate 1: operator|(int, unsigned int) <built-in>
/usr/include/qt4/QtCore/qnamespace.h:1542: note: candidate 2:  
QIncompatibleFlag operator|(Qt::MouseButton, int)

Ubuntu Jaunty comes with gcc 4.3.3 and qt 4.5.0.  I'm not a c++  
programmer, so I don't have the slightest idea what that message  
means...

Second question:  Do I *really* need libfam for Kontact?  On jaunty, it  
conflicts with gamin which in turn is needed by some Gnome packages.   
Running "dpkg-buildpackage -d" succeeded without installing libfam,  
though (until it ejected due to the error above).

Cheers, Albrecht.



From johnm at advocap.org  Mon May 18 21:08:58 2009
From: johnm at advocap.org (John McMonagle)
Date: Mon, 18 May 2009 14:08:58 -0500
Subject: Compile problems [was: Kontact on Linux w/o kde]
In-Reply-To: <1242671319.3469.0@antares>
References: <1242671319.3469.0@antares>
Message-ID: <4A11B24A.1070509@advocap.org>

Albrecht Dre? wrote:
> Am 18.05.09 15:27 schrieb(en) Albrecht Dre?:
>   
>> Umm, yes.  ;-)  I found the folder  
>> http://apt.intevation.org/dists/lenny/enterprise4-unstable/source,  
>> and will give it a try on Jaunty, stay tuned, please...
>>     
>
> Do I need a specific g++ version to compile these packages?  For  
> kde4libs-4.1.1.enterprise4.0.20081104.879654/kde3support/kdeui/k3popupmenu.cpp,  
> the build ejects with
>
> /home/adress/source/kde4libs-4.1.1.enterprise4.0.20081104.879654/kde3support/kdeui/k3popupmenu.cpp:  
> In member function 'virtual void  
> K3PopupMenu::mouseReleaseEvent(QMouseEvent*)':
> /home/adress/source/kde4libs-4.1.1.enterprise4.0.20081104.879654/kde3support/kdeui/k3popupmenu.cpp:391:  
> error: ISO C++ says that these are ambiguous, even though the worst  
> conversion for the first is better than the worst conversion for the  
> second:
> /home/adress/source/kde4libs-4.1.1.enterprise4.0.20081104.879654/kde3support/kdeui/k3popupmenu.cpp:391:  
> note: candidate 1: operator|(int, unsigned int) <built-in>
> /usr/include/qt4/QtCore/qnamespace.h:1542: note: candidate 2:  
> QIncompatibleFlag operator|(Qt::MouseButton, int)
>
> Ubuntu Jaunty comes with gcc 4.3.3 and qt 4.5.0.  I'm not a c++  
> programmer, so I don't have the slightest idea what that message  
> means...
>
> Second question:  Do I *really* need libfam for Kontact?  On jaunty, it  
> conflicts with gamin which in turn is needed by some Gnome packages.   
> Running "dpkg-buildpackage -d" succeeded without installing libfam,  
> though (until it ejected due to the error above).
>
>   
As to fam and gamin.
Probably not a problem.
They both do the same thing using different kernel drivers.
What they do is notify when  files are changed.
Fam is considered less safe and has a limit on how many  files ( maybe 
directories) that can be monitored.
Gamin is better in almost all respects.
Both allows file managers etc to know when a file has changed without 
having to check for changes.
Gamin is designed to be mostly compatible with fam.

John
-------------- next part --------------
A non-text attachment was scrubbed...
Name: johnm.vcf
Type: text/x-vcard
Size: 250 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20090518/d9e34674/johnm.bin

From shrenik.bhura at intelliant.net  Tue May 19 07:25:25 2009
From: shrenik.bhura at intelliant.net (Shrenik Bhura)
Date: Tue, 19 May 2009 10:55:25 +0530
Subject: kolab - opensuse 11.1
Message-ID: <4A1242C5.2020104@intelliant.net>

Hi,

Following instructions at http://en.opensuse.org/kolab , I don't seem to
get a repo for 11.1 as it is also mentioned on the Talk/Discussions page.

Hence I proceeded with factory but that has landed me with the same
problem as Richard's.

I have the following kolab rpms installed:

# rpm -qa|grep -i kolab
cyrus-imapd-kolab-2.3.13-63.1
php5-pear-kolab_filter-2.2.0-5.67
kolab-webclient-1.2-2.1
perl-kolab-2.2.1.90_cvs20090503-1.3
php5-pear-kolab_freebusy-2.1.99-12.76
kolab-freebusy-2.1.99-17.35
kolab-2.2.1.90_cvs20090503-4.1
php5-imap-kolab-5.2.6-38.1
kolab-webadmin-2.2.0.99_cvs20090222-2.9
kolab-filter-2.1.99-18.12
imap-kolab-lib-2006c1_suse-133.30

There is definitely something wrong as there is no
/usr/bin/kolabmailboxfilter or kolabfilter

I have a few queries:
1. Is it advisable to go the 11.1 route or 10.3 on opensuse as of now?
If 10.3, then is this the right way -
http://www.kolab.org/pipermail/kolab-users/2009-May/009830.html ?
2. Have you managed to resolve your issue? If yes, could you please
share the same?

The wiki at http://en.opensuse.org/kolab needs some more cleanup.
Someone who has achieved complete/partial success, please  take the
initiative.
Or I shall definitely do it if I achieve it.

Thanks,
SB



From aspineux at gmail.com  Tue May 19 07:59:59 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Tue, 19 May 2009 07:59:59 +0200
Subject: Question about upgrade from 2.2.0 to 2.2.2
In-Reply-To: <BLU122-W471AF207A53EC97DD4467A35A0@phx.gbl>
References: <BLU122-W471AF207A53EC97DD4467A35A0@phx.gbl>
Message-ID: <71fe4e760905182259x26391b01g4baeeb0d438ad086@mail.gmail.com>

2009/5/18 kiser Caesar <kcaesar at hotmail.com>:
> Hello the list !
>
> I just saw that kolab 2.2.2 is avaible.
> Well after a quick read of
>
> http://files.kolab.org/server/release/kolab-server-2.2.2/sources/1st.README
>
> I see that I need to make some steps before upgrading to 2.2.2.
>
> Can you confirm that I understand well ???
>
> I explain. To upgrade to 2.2.2 from 2.2.0 I must install
>
> 2.2.1-beta1 > 2.2.1-rc1 > 2.2.1 then finaly 2.2.2
>
> It's true ? And the only way ?

No, itsn't ! Upgrade directly up to 2.2.2 but follow and compile/merge
all the instructions about the version in between.

Here this is mostly upgrade from 2.2.0 to 2.2.1-beta1

Regards


>
>
> I'm waiting for your feedback,
>
>
> Best regards,
>
> ________________________________
> Vous voulez savoir ce que vous pouvez faire avec le nouveau Windows Live??
> Lancez-vous !
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
>



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



From Roessler at FuH-E.de  Tue May 19 09:55:33 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Tue, 19 May 2009 09:55:33 +0200
Subject: Update to 2.2.2: kolabd - failed dependencies
In-Reply-To: <4A1167EE.6010606@FuH-E.de>
References: <4A11261B.2030304@FuH-E.de>	<71fe4e760905180317x31b0c413p3d65dc5652836abb@mail.gmail.com>	<4A115BF0.7010002@FuH-E.de>
	<4A1167EE.6010606@FuH-E.de>
Message-ID: <4A1265F5.7000009@FuH-E.de>

Christian R??ler schrieb:

>> I will post the needed options for apache_php too, if wanted.
> For php:
> --define "with_imap yes" --define "with_ssl yes" --define "with_zlib
> yes" --define "with_imap_annotate yes" --define "with_imap_myrights yes"
> --define "with_spl yes" --define "with_gettext yes" --define "with_dom
> yes" --define "with_mcrypt yes" --define "with_iconv yes" --define
> "with_mbstring yes" --define "with_mbregex yes" --define "with_gd yes"
> --define "with_ctype yes" --define "with_openldap yes" --define
> "with_mhash yes" --define "with_bdb yes" --define "with_pear yes"
> --define "with_xml yes" --define "with_mm yes" --define "with_sqlite yes"
> 
> For apache_php:
> --define "with_imap yes" --define "with_ssl yes" --define "with_zlib
> yes" --define "with_imap_annotate yes" --define "with_imap_myrights yes"
> --define "with_gettext yes" --define "with_dom yes" --define
> "with_mcrypt yes" --define "with_iconv yes" --define "with_mbstring yes"
> --define "with_mbregex yes" --define "with_gd yes" --define "with_ctype
> yes" --define "with_openldap yes" --define "with_mhash yes" --define
> "with_bdb yes" --define "with_pear yes" --define "with_xml yes" --define
> "with_mm yes" --define "with_sqlite yes"

Well, I noticed I forgot the part this all was about: To have
MySQL-support one has to append --define "with_mysql yes" to each option
line, of course.

Sorry, Christian



From kcaesar at hotmail.com  Tue May 19 13:13:36 2009
From: kcaesar at hotmail.com (kiser Caesar)
Date: Tue, 19 May 2009 13:13:36 +0200
Subject: SyncML in 2.2.2 ?
Message-ID: <BLU122-W9D1251D331A666E984FD7A35B0@phx.gbl>


Hello the list,


With the quick answer of Alain Spineux on my last question, I want to update kolab 2.2.0  to 2.2.2.
But before, I want to know if with the 2.2.2 I can connect my account (calendars, tasks) with my Blackberry ?

Best regards,

_________________________________________________________________
Vous voulez savoir ce que vous pouvez faire avec le nouveau Windows Live?? Lancez-vous !
http://www.microsoft.com/windows/windowslive/default.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20090519/3962c1d7/attachment.html

From Webmaster at computational-chemistry.org  Tue May 19 13:20:25 2009
From: Webmaster at computational-chemistry.org (Alexander =?utf-8?q?Schr=C3=B6ter?=)
Date: Tue, 19 May 2009 13:20:25 +0200
Subject: SyncML in 2.2.2 ?
In-Reply-To: <BLU122-W9D1251D331A666E984FD7A35B0@phx.gbl>
References: <BLU122-W9D1251D331A666E984FD7A35B0@phx.gbl>
Message-ID: <200905191320.26074.Webmaster@computational-chemistry.org>

On Tuesday 19 May 2009 01:13:36 pm kiser Caesar wrote:
> Hello the list,
>
>
> With the quick answer of Alain Spineux on my last question, I want to
> update kolab 2.2.0  to 2.2.2. But before, I want to know if with the 2.2.2
> I can connect my account (calendars, tasks) with my Blackberry ?

Hi I cannot really answer the question regarding "Your Blackberry" but I am 
using the Funambol Client for most of my not Unix Equipment. And the Syncing 
works in all Categories but the Calendar. I am not sure if I am the only one 
with this Problem or if others experienced the same.

Regards

> Best regards,
>
> _________________________________________________________________
> Vous voulez savoir ce que vous pouvez faire avec le nouveau Windows Live ?
> Lancez-vous ! http://www.microsoft.com/windows/windowslive/default.aspx



From johnm at advocap.org  Tue May 19 15:34:30 2009
From: johnm at advocap.org (John McMonagle)
Date: Tue, 19 May 2009 08:34:30 -0500
Subject: whitelist
Message-ID: <200905190834.31183.johnm@advocap.org>

I see there is a whitelist filter  in horde.
I am assuming that it is just  the sieve filter or does it also hook in to the 
spam controls?
It doesn't do much good to whitelist if it's been blocked before it gets to 
you :-(
If this is not the case is there a spam whitelist in kolab? 

Thanks

John



From shrenik.bhura at intelliant.net  Tue May 19 21:37:33 2009
From: shrenik.bhura at intelliant.net (Shrenik Bhura)
Date: Wed, 20 May 2009 01:07:33 +0530
Subject: trouble logging into horde
In-Reply-To: <20090507215328.29131wci9adgib0g@webmail.pardus.de>
References: <200904140027.40133.sunil@khiatani.ath.cx>
	<20090507215328.29131wci9adgib0g@webmail.pardus.de>
Message-ID: <4A130A7D.30707@intelliant.net>



Gunnar Wrobel wrote:
>
> Quoting Sunil Khiatani <sunil at khiatani.ath.cx>:
>
>> Hi,
>>
>> I recently upgraded to horde 2.2.1, but i can no longer log
>> into the horde webclient.  I'm not sure where to look for logs and
>> what to do
>> next.
>>
>> When I log in with the correct username and password, I get
>> returned to the login page with no errors.
I am now facing the same problem on opensuse 11.1 installation. The mail
delivery part is working fine though. Just can't log in into the horde
based web-client.

SB


PS: Something seems to be wrong with the mailing-list. Mails are not
going thru as of now.



From ml at radoeka.nl  Tue May 19 18:04:11 2009
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 19 May 2009 18:04:11 +0200
Subject: kolab - opensuse 11.1
In-Reply-To: <4A1242C5.2020104@intelliant.net>
References: <4A1242C5.2020104@intelliant.net>
Message-ID: <200905191804.12613.ml@radoeka.nl>

Hi shrenik,

Op dinsdag 19 mei 2009 07:25:25 schreef Shrenik Bhura:
> Following instructions at http://en.opensuse.org/kolab , I don't seem to
> get a repo for 11.1 as it is also mentioned on the Talk/Discussions page.

Ah, thanks for reporting this.  I don't look at the wiki talk/discussion page. 

I removed the links to the stable repository, as that is for kolab-2.1.0 (I 
believe or perhaps even prior 2.1.0).  One should now use the unstable 
repository.  Another thing for which I did not have the time to write, is that 
one must use perl-ldap from the devel:language:perl repository.

> Hence I proceeded with factory but that has landed me with the same
> problem as Richard's.

Factory as in openSUSE_Factory or unstable?

> I have the following kolab rpms installed:
>
> # rpm -qa|grep -i kolab
> cyrus-imapd-kolab-2.3.13-63.1
> php5-pear-kolab_filter-2.2.0-5.67
> kolab-webclient-1.2-2.1
> perl-kolab-2.2.1.90_cvs20090503-1.3
> php5-pear-kolab_freebusy-2.1.99-12.76
> kolab-freebusy-2.1.99-17.35
> kolab-2.2.1.90_cvs20090503-4.1
> php5-imap-kolab-5.2.6-38.1
> kolab-webadmin-2.2.0.99_cvs20090222-2.9
> kolab-filter-2.1.99-18.12
> imap-kolab-lib-2006c1_suse-133.30

If I do that I get:
kolab2:~ # rpm -qa | grep kolab
cyrus-imapd-kolab-2.3.13-63.1
kolab-filter-0.1.5-3.1
kolab-format-1.0.1-2.5
kolab-freebusy-0.1.5-4.5
kolab-2.2.2-0
php5-imap-kolab-5.2.9-1.1
kolab-storage-0.4.0-3.7
kolab-webadmin-2.2.0.99_cvs20090222-2.9
imap-kolab-lib-2006c1_suse-71.3
kolab-server-0.5.0-4.1
perl-kolab-2.2.1.90_cvs20090503-1.3

They come from the following repositories:
kolab2:~ # PKGS=$(rpm -qa | grep kolab)                           
kolab2:~ # rpm -q --qf "%{NAME}\t%{DISTRIBUTION}\n" $PKGS
kolab-format    server:php:applications / openSUSE_11.1
kolab-freebusy  server:php:applications / openSUSE_11.1
kolab   server:Kolab:UNSTABLE / openSUSE_11.1
php5-imap-kolab server:Kolab:UNSTABLE / openSUSE_11.1
kolab-storage   server:php:applications / openSUSE_11.1
kolab-filter    server:php:applications / openSUSE_11.1
kolab-webadmin  server:Kolab:UNSTABLE / openSUSE_11.1
cyrus-imapd-kolab       server:Kolab:UNSTABLE / openSUSE_11.1
imap-kolab-lib  server:Kolab:UNSTABLE / openSUSE_11.1
kolab-server    server:php:applications / openSUSE_11.1
perl-kolab      server:Kolab:UNSTABLE / openSUSE_11.1

You have packages with php5-pear-kolab-*, which is not good.

> There is definitely something wrong as there is no
> /usr/bin/kolabmailboxfilter or kolabfilter

What is the result of "locate kolabmailfilter"?

I have:
kolab2:~ # rpm -qf /usr/bin/kolabmailboxfilter
kolab-filter-0.1.5-3.1

kolab2:~ # rpm -ql kolab-filter | grep bin
/usr/bin/kolabfilter
/usr/bin/kolabmailboxfilter


> I have a few queries:
> 1. Is it advisable to go the 11.1 route or 10.3 on opensuse as of now?
> If 10.3, then is this the right way -
> http://www.kolab.org/pipermail/kolab-users/2009-May/009830.html ?

I test on and use 11.1, others test 10.3.  The packages are the same, as they 
are all build with exactly the same specfile.  I would opt for 11.1 if you 
have the possibility as that will last longer than 10.3.

> The wiki at http://en.opensuse.org/kolab needs some more cleanup.
> Someone who has achieved complete/partial success, please  take the
> initiative.
> Or I shall definitely do it if I achieve it.

I believe that the wiki is rather up to date.  The most important part that is 
missing, is an explanation to install perl-ldap from devel:language:perl

Verify that you have the right perl-ldap, by executing the following command:
kolab2:~ # grep -n "{cookie} || undef" 
/usr/lib/perl5/vendor_perl/5.10.0/Net/LDAP/Control/SyncRequest.pm

The result should be:
24:      cookie => $self->{cookie} || undef,

(24 is the line number).


-- 
Richard



From shrenik.bhura at intelliant.net  Tue May 19 20:29:28 2009
From: shrenik.bhura at intelliant.net (Shrenik Bhura)
Date: Tue, 19 May 2009 23:59:28 +0530
Subject: kolab - opensuse 11.1
In-Reply-To: <200905191804.12613.ml@radoeka.nl>
References: <4A1242C5.2020104@intelliant.net>
	<200905191804.12613.ml@radoeka.nl>
Message-ID: <4A12FA88.6050405@intelliant.net>

Brilliant Richard!! You couldn't have been more prompt and clear. :) Thanks.

Richard Bos wrote:
> Hi shrenik,
>
> Op dinsdag 19 mei 2009 07:25:25 schreef Shrenik Bhura:
>   
>> Following instructions at http://en.opensuse.org/kolab , I don't seem to
>> get a repo for 11.1 as it is also mentioned on the Talk/Discussions page.
>>     
>
> Ah, thanks for reporting this.  I don't look at the wiki talk/discussion page. 
>
> I removed the links to the stable repository, as that is for kolab-2.1.0 (I 
> believe or perhaps even prior 2.1.0).  One should now use the unstable 
> repository.  Another thing for which I did not have the time to write, is that 
> one must use perl-ldap from the devel:language:perl repository.
>   
Now I have the correct repositories added as well.
>> Hence I proceeded with factory but that has landed me with the same
>> problem as Richard's.
>> Factory as in openSUSE_Factory or unstable?
>>     
openSUSE_Factory

>> I have the following kolab rpms installed:
>>
>> # rpm -qa|grep -i kolab
>> cyrus-imapd-kolab-2.3.13-63.1
>> php5-pear-kolab_filter-2.2.0-5.67
>> kolab-webclient-1.2-2.1
>> perl-kolab-2.2.1.90_cvs20090503-1.3
>> php5-pear-kolab_freebusy-2.1.99-12.76
>> kolab-freebusy-2.1.99-17.35
>> kolab-2.2.1.90_cvs20090503-4.1
>> php5-imap-kolab-5.2.6-38.1
>> kolab-webadmin-2.2.0.99_cvs20090222-2.9
>> kolab-filter-2.1.99-18.12
>> imap-kolab-lib-2006c1_suse-133.30
>>     
>
> If I do that I get:
> kolab2:~ # rpm -qa | grep kolab
> cyrus-imapd-kolab-2.3.13-63.1
> kolab-filter-0.1.5-3.1
> kolab-format-1.0.1-2.5
> kolab-freebusy-0.1.5-4.5
> kolab-2.2.2-0
> php5-imap-kolab-5.2.9-1.1
> kolab-storage-0.4.0-3.7
> kolab-webadmin-2.2.0.99_cvs20090222-2.9
> imap-kolab-lib-2006c1_suse-71.3
> kolab-server-0.5.0-4.1
> perl-kolab-2.2.1.90_cvs20090503-1.3
>
> They come from the following repositories:
> kolab2:~ # PKGS=$(rpm -qa | grep kolab)                           
> kolab2:~ # rpm -q --qf "%{NAME}\t%{DISTRIBUTION}\n" $PKGS
> kolab-format    server:php:applications / openSUSE_11.1
> kolab-freebusy  server:php:applications / openSUSE_11.1
> kolab   server:Kolab:UNSTABLE / openSUSE_11.1
> php5-imap-kolab server:Kolab:UNSTABLE / openSUSE_11.1
> kolab-storage   server:php:applications / openSUSE_11.1
> kolab-filter    server:php:applications / openSUSE_11.1
> kolab-webadmin  server:Kolab:UNSTABLE / openSUSE_11.1
> cyrus-imapd-kolab       server:Kolab:UNSTABLE / openSUSE_11.1
> imap-kolab-lib  server:Kolab:UNSTABLE / openSUSE_11.1
> kolab-server    server:php:applications / openSUSE_11.1
> perl-kolab      server:Kolab:UNSTABLE / openSUSE_11.1
>
> You have packages with php5-pear-kolab-*, which is not good.
>   
The package details now installed are as follows:
 # rpm -qa |grep -i kolab
kolab-webadmin-2.2.0.99_cvs20090222-2.10
kolab-2.2.2-1.1
perl-kolab-2.2.1.90_cvs20090503-1.3
kolab-server-0.5.0-4.1
kolab-filter-0.1.5-3.1
cyrus-imapd-kolab-2.3.13-63.1
kolab-storage-0.4.0-3.7
imap-kolab-lib-2006c1_suse-71.3
kolab-format-1.0.1-2.5
kolab-freebusy-0.1.5-4.5
php5-imap-kolab-5.2.9-1.1

# PKGS=$(rpm -qa | grep kolab)
# rpm -q --qf "%{NAME}\t%{DISTRIBUTION}\n" $PKGS
kolab-webadmin  server:Kolab:UNSTABLE / openSUSE_11.1
kolab   server:Kolab:UNSTABLE / openSUSE_11.1
perl-kolab      server:Kolab:UNSTABLE / openSUSE_11.1
kolab-server    server:php:applications / openSUSE_11.1
kolab-filter    server:php:applications / openSUSE_11.1
cyrus-imapd-kolab       server:Kolab:UNSTABLE / openSUSE_11.1
kolab-storage   server:php:applications / openSUSE_11.1
imap-kolab-lib  server:Kolab:UNSTABLE / openSUSE_11.1
kolab-format    server:php:applications / openSUSE_11.1
kolab-freebusy  server:php:applications / openSUSE_11.1
php5-imap-kolab server:Kolab:UNSTABLE / openSUSE_11.1

>> There is definitely something wrong as there is no
>> /usr/bin/kolabmailboxfilter or kolabfilter
>>     
>
> What is the result of "locate kolabmailfilter"?
>
> I have:
> kolab2:~ # rpm -qf /usr/bin/kolabmailboxfilter
> kolab-filter-0.1.5-3.1
>
> kolab2:~ # rpm -ql kolab-filter | grep bin
> /usr/bin/kolabfilter
> /usr/bin/kolabmailboxfilter
>   
Now the files are there. :)
>> I have a few queries:
>> 1. Is it advisable to go the 11.1 route or 10.3 on opensuse as of now?
>> If 10.3, then is this the right way -
>> http://www.kolab.org/pipermail/kolab-users/2009-May/009830.html ?
>>     
>
> I test on and use 11.1, others test 10.3.  The packages are the same, as they 
> are all build with exactly the same specfile.  I would opt for 11.1 if you 
> have the possibility as that will last longer than 10.3.
>   
That's what I would have preferred.
>> The wiki at http://en.opensuse.org/kolab needs some more cleanup.
>> Someone who has achieved complete/partial success, please  take the
>> initiative.
>> Or I shall definitely do it if I achieve it.
>>     
>
> I believe that the wiki is rather up to date.  The most important part that is 
> missing, is an explanation to install perl-ldap from devel:language:perl
>   
It is now up-to-date indeed. You have done the remaining bit. Many thanks.
> Verify that you have the right perl-ldap, by executing the following command:
> kolab2:~ # grep -n "{cookie} || undef" 
> /usr/lib/perl5/vendor_perl/5.10.0/Net/LDAP/Control/SyncRequest.pm
>
> The result should be:
> 24:      cookie => $self->{cookie} || undef,
>
> (24 is the line number)
Got the same result but from different repository:
# rpm -q --qf "%{NAME}\t%{DISTRIBUTION}\n" perl-ldap
perl-ldap       server:Kolab:UNSTABLE / openSUSE_11.1

Mail received. :) Worked like a charm.
The only issue was this:
I only got this error while doing "# zypper in kolab" and it installed
all the other packages:
Installation of horde-form-0.0.2-4.16 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed:
Package "/var/lib/pear/Horde_Form.xml" is not valid
install failed
error: %post(horde-form-0.0.2-4.16.noarch) scriptlet failed, exit status 1

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

Regards,
SB



From johnm at advocap.org  Tue May 19 17:06:18 2009
From: johnm at advocap.org (John McMonagle)
Date: Tue, 19 May 2009 10:06:18 -0500
Subject: Problem with acls migrating from cyrus imap.
In-Reply-To: <71fe4e760905151421x43a3e30fy8e616cc27d615000@mail.gmail.com>
References: <200905130907.33120.johnm@advocap.org>
	<4A0C247B.6060505@advocap.org>
	<71fe4e760905151421x43a3e30fy8e616cc27d615000@mail.gmail.com>
Message-ID: <200905191006.19201.johnm@advocap.org>

On Friday 15 May 2009 04:21:28 pm Alain Spineux wrote:
> 2009/5/14 John McMonagle <johnm at advocap.org>:
> > Did a simple test and it apears that the acls are defined in the
> > cyrus.header files.
> >
> > For example:
> > Cyrus mailbox header
> > "The best thing about this system was that it had lots of goals."
> > ? ? ? --Jim Morris on Andrew
> > advocap.org!user.test ? 1513ee1e4424dbbc
> > Junk
> > test at advocap.org ? ? ? ?lrswipcda ? ? ? mailadm lrswipcda
> >
> > I edited the last line and then ran cyrreconstruct.
> >
> > Is this how to do it?
> > I doubt if I'm the first to migrate from a domain less cyrus
> > installation.
> >
> > John
>
> If you are not switching/restoring on an identical version/system then
> you should use imapsync
>

The problem with imapsync is that I still would have to manually fix all the 
acls for shared mailboxes.
I figure the switchover will be nasty enough without lots of manual 
configuration.

I made a sed script called by find to change the cyrus.header files.

I did a test run and it seems to work OK

Another method I considered was make a script to feed  cyradm  data from 
ctl_mboxlist.

Thanks

John



From LHendricks at austinent.com  Tue May 19 18:21:57 2009
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Tue, 19 May 2009 11:21:57 -0500
Subject: SyncML in 2.2.2 ?
Message-ID: <7907AE10BB50DD4F840E76527D27EF19029F684E@entmail.domain.austinent.com>

I cannot say for 2.2.2 yet.  But in 2.2.1 I was able to sync outlook via
funambol for all categories, including calendar (only default personal
calendar, though).  Theoretically that should not have changed for 2.2.2.

That said, this is depending on the webclient (horde) for its ability which
is a beta stage syncML support.  Here is a sync howto for many clients
including blackberry with horde:

http://wiki.horde.org/SyncHowTo

Lucas

-----Original Message-----
From: Alexander Schr?ter [mailto:Webmaster at computational-chemistry.org] 
Sent: Tuesday, May 19, 2009 6:20 AM
To: kolab-users at kolab.org
Subject: Re: SyncML in 2.2.2 ?

On Tuesday 19 May 2009 01:13:36 pm kiser Caesar wrote:
> Hello the list,
>
>
> With the quick answer of Alain Spineux on my last question, I want to
> update kolab 2.2.0  to 2.2.2. But before, I want to know if with the 2.2.2
> I can connect my account (calendars, tasks) with my Blackberry ?

Hi I cannot really answer the question regarding "Your Blackberry" but I am 
using the Funambol Client for most of my not Unix Equipment. And the Syncing

works in all Categories but the Calendar. I am not sure if I am the only one

with this Problem or if others experienced the same.

Regards

> Best regards,
>
> _________________________________________________________________
> Vous voulez savoir ce que vous pouvez faire avec le nouveau Windows Live ?
> Lancez-vous ! http://www.microsoft.com/windows/windowslive/default.aspx

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



From shrenik.bhura at intelliant.net  Tue May 19 20:29:28 2009
From: shrenik.bhura at intelliant.net (Shrenik Bhura)
Date: Tue, 19 May 2009 23:59:28 +0530
Subject: kolab - opensuse 11.1
In-Reply-To: <200905191804.12613.ml@radoeka.nl>
References: <4A1242C5.2020104@intelliant.net>
	<200905191804.12613.ml@radoeka.nl>
Message-ID: <4A12FA88.6050405@intelliant.net>

Brilliant Richard!! You couldn't have been more prompt and clear. :) Thanks.

Richard Bos wrote:
> Hi shrenik,
>
> Op dinsdag 19 mei 2009 07:25:25 schreef Shrenik Bhura:
>   
>> Following instructions at http://en.opensuse.org/kolab , I don't seem to
>> get a repo for 11.1 as it is also mentioned on the Talk/Discussions page.
>>     
>
> Ah, thanks for reporting this.  I don't look at the wiki talk/discussion page. 
>
> I removed the links to the stable repository, as that is for kolab-2.1.0 (I 
> believe or perhaps even prior 2.1.0).  One should now use the unstable 
> repository.  Another thing for which I did not have the time to write, is that 
> one must use perl-ldap from the devel:language:perl repository.
>   
Now I have the correct repositories added as well.
>> Hence I proceeded with factory but that has landed me with the same
>> problem as Richard's.
>> Factory as in openSUSE_Factory or unstable?
>>     
openSUSE_Factory

>> I have the following kolab rpms installed:
>>
>> # rpm -qa|grep -i kolab
>> cyrus-imapd-kolab-2.3.13-63.1
>> php5-pear-kolab_filter-2.2.0-5.67
>> kolab-webclient-1.2-2.1
>> perl-kolab-2.2.1.90_cvs20090503-1.3
>> php5-pear-kolab_freebusy-2.1.99-12.76
>> kolab-freebusy-2.1.99-17.35
>> kolab-2.2.1.90_cvs20090503-4.1
>> php5-imap-kolab-5.2.6-38.1
>> kolab-webadmin-2.2.0.99_cvs20090222-2.9
>> kolab-filter-2.1.99-18.12
>> imap-kolab-lib-2006c1_suse-133.30
>>     
>
> If I do that I get:
> kolab2:~ # rpm -qa | grep kolab
> cyrus-imapd-kolab-2.3.13-63.1
> kolab-filter-0.1.5-3.1
> kolab-format-1.0.1-2.5
> kolab-freebusy-0.1.5-4.5
> kolab-2.2.2-0
> php5-imap-kolab-5.2.9-1.1
> kolab-storage-0.4.0-3.7
> kolab-webadmin-2.2.0.99_cvs20090222-2.9
> imap-kolab-lib-2006c1_suse-71.3
> kolab-server-0.5.0-4.1
> perl-kolab-2.2.1.90_cvs20090503-1.3
>
> They come from the following repositories:
> kolab2:~ # PKGS=$(rpm -qa | grep kolab)                           
> kolab2:~ # rpm -q --qf "%{NAME}\t%{DISTRIBUTION}\n" $PKGS
> kolab-format    server:php:applications / openSUSE_11.1
> kolab-freebusy  server:php:applications / openSUSE_11.1
> kolab   server:Kolab:UNSTABLE / openSUSE_11.1
> php5-imap-kolab server:Kolab:UNSTABLE / openSUSE_11.1
> kolab-storage   server:php:applications / openSUSE_11.1
> kolab-filter    server:php:applications / openSUSE_11.1
> kolab-webadmin  server:Kolab:UNSTABLE / openSUSE_11.1
> cyrus-imapd-kolab       server:Kolab:UNSTABLE / openSUSE_11.1
> imap-kolab-lib  server:Kolab:UNSTABLE / openSUSE_11.1
> kolab-server    server:php:applications / openSUSE_11.1
> perl-kolab      server:Kolab:UNSTABLE / openSUSE_11.1
>
> You have packages with php5-pear-kolab-*, which is not good.
>   
The package details now installed are as follows:
 # rpm -qa |grep -i kolab
kolab-webadmin-2.2.0.99_cvs20090222-2.10
kolab-2.2.2-1.1
perl-kolab-2.2.1.90_cvs20090503-1.3
kolab-server-0.5.0-4.1
kolab-filter-0.1.5-3.1
cyrus-imapd-kolab-2.3.13-63.1
kolab-storage-0.4.0-3.7
imap-kolab-lib-2006c1_suse-71.3
kolab-format-1.0.1-2.5
kolab-freebusy-0.1.5-4.5
php5-imap-kolab-5.2.9-1.1

# PKGS=$(rpm -qa | grep kolab)
# rpm -q --qf "%{NAME}\t%{DISTRIBUTION}\n" $PKGS
kolab-webadmin  server:Kolab:UNSTABLE / openSUSE_11.1
kolab   server:Kolab:UNSTABLE / openSUSE_11.1
perl-kolab      server:Kolab:UNSTABLE / openSUSE_11.1
kolab-server    server:php:applications / openSUSE_11.1
kolab-filter    server:php:applications / openSUSE_11.1
cyrus-imapd-kolab       server:Kolab:UNSTABLE / openSUSE_11.1
kolab-storage   server:php:applications / openSUSE_11.1
imap-kolab-lib  server:Kolab:UNSTABLE / openSUSE_11.1
kolab-format    server:php:applications / openSUSE_11.1
kolab-freebusy  server:php:applications / openSUSE_11.1
php5-imap-kolab server:Kolab:UNSTABLE / openSUSE_11.1

>> There is definitely something wrong as there is no
>> /usr/bin/kolabmailboxfilter or kolabfilter
>>     
>
> What is the result of "locate kolabmailfilter"?
>
> I have:
> kolab2:~ # rpm -qf /usr/bin/kolabmailboxfilter
> kolab-filter-0.1.5-3.1
>
> kolab2:~ # rpm -ql kolab-filter | grep bin
> /usr/bin/kolabfilter
> /usr/bin/kolabmailboxfilter
>   
Now the files are there. :)
>> I have a few queries:
>> 1. Is it advisable to go the 11.1 route or 10.3 on opensuse as of now?
>> If 10.3, then is this the right way -
>> http://www.kolab.org/pipermail/kolab-users/2009-May/009830.html ?
>>     
>
> I test on and use 11.1, others test 10.3.  The packages are the same, as they 
> are all build with exactly the same specfile.  I would opt for 11.1 if you 
> have the possibility as that will last longer than 10.3.
>   
That's what I would have preferred.
>> The wiki at http://en.opensuse.org/kolab needs some more cleanup.
>> Someone who has achieved complete/partial success, please  take the
>> initiative.
>> Or I shall definitely do it if I achieve it.
>>     
>
> I believe that the wiki is rather up to date.  The most important part that is 
> missing, is an explanation to install perl-ldap from devel:language:perl
>   
It is now up-to-date indeed. You have done the remaining bit. Many thanks.
> Verify that you have the right perl-ldap, by executing the following command:
> kolab2:~ # grep -n "{cookie} || undef" 
> /usr/lib/perl5/vendor_perl/5.10.0/Net/LDAP/Control/SyncRequest.pm
>
> The result should be:
> 24:      cookie => $self->{cookie} || undef,
>
> (24 is the line number)
Got the same result but from different repository:
# rpm -q --qf "%{NAME}\t%{DISTRIBUTION}\n" perl-ldap
perl-ldap       server:Kolab:UNSTABLE / openSUSE_11.1

Mail received. :) Worked like a charm.
The only issue was this:
I only got this error while doing "# zypper in kolab" and it installed
all the other packages:
Installation of horde-form-0.0.2-4.16 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed:
Package "/var/lib/pear/Horde_Form.xml" is not valid
install failed
error: %post(horde-form-0.0.2-4.16.noarch) scriptlet failed, exit status 1

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

Regards,
SB




From ml at radoeka.nl  Tue May 19 22:56:02 2009
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 19 May 2009 22:56:02 +0200
Subject: kolab - opensuse 11.1
In-Reply-To: <4A12FA88.6050405@intelliant.net>
References: <4A1242C5.2020104@intelliant.net>
	<200905191804.12613.ml@radoeka.nl>
	<4A12FA88.6050405@intelliant.net>
Message-ID: <200905192256.03669.ml@radoeka.nl>

Hi Shrenik,

no need to Cc me, I'm subscribed to the list.

Op dinsdag 19 mei 2009 20:29:28 schreef Shrenik Bhura:
> >> Hence I proceeded with factory but that has landed me with the same
> >> problem as Richard's.
> >> Factory as in openSUSE_Factory or unstable?
> >>    
>
> openSUSE_Factory

Hmm, that is very much living on the bleeding edge, is it will take about 6 
months before Factory is stable and named 11.2.  If possible you better you 
11.1.

<removed quite a bit>

> > Verify that you have the right perl-ldap, by executing the following
> > command: kolab2:~ # grep -n "{cookie} || undef"
> > /usr/lib/perl5/vendor_perl/5.10.0/Net/LDAP/Control/SyncRequest.pm
> >
> > The result should be:
> > 24:      cookie => $self->{cookie} || undef,
> >
> > (24 is the line number)
>
> Got the same result but from different repository:
> # rpm -q --qf "%{NAME}\t%{DISTRIBUTION}\n" perl-ldap
> perl-ldap       server:Kolab:UNSTABLE / openSUSE_11.1

Don't know where that comes from.  As long as the test (with the grep command) 
is okay, than it does not matter to much where the package comes from.

> Mail received. :) Worked like a charm.
> The only issue was this:
> I only got this error while doing "# zypper in kolab" and it installed
> all the other packages:
> Installation of horde-form-0.0.2-4.16 failed:
> (with --nodeps --force) Error: Subprocess failed. Error: RPM failed:
> Package "/var/lib/pear/Horde_Form.xml" is not valid
> install failed
> error: %post(horde-form-0.0.2-4.16.noarch) scriptlet failed, exit status 1
>
> Abort, retry, ignore? [A/r/i]: i

Hmmm, there is an easy trick to make this warning harmless, which is already 
used in horde-token/horde-token.  The trick is the "|| echo"  piece.
pear install --nodeps --soft --force --register-only %{xmldir}/%{prj}.xml || 
echo > /dev/null
But I would like to know why the installation of the Horde_Form.xml file 
fails...  If this error always happen, please let us know.

-- 
Richard



From johnm at advocap.org  Tue May 19 22:55:58 2009
From: johnm at advocap.org (John McMonagle)
Date: Tue, 19 May 2009 15:55:58 -0500
Subject: ldap questions.
Message-ID: <200905191555.59009.johnm@advocap.org>

Have our ldap migrated over to kolab and it's looking good but have a couple 
questions.

I had to do a line by line merge of slapd.conf and mine were longer than 
kolabs so it took a while.

Really the only merge question is this really needed in slapd.conf?
allow           bind_v2
It seems to run fine without it.

Any chance one can put multiple servers for ldap_uri   in kolab.conf

For example in my current mail servers saslauthd.conf have:
ldap_servers: ldapi:///var/run/ldapi ldaps://fonldap.advocap.org 
ldaps://mstldap
.advocap.org
Sure that wrapped but have 3 servers.
Everywere else I use ldap do the same.

The neat thing  is if any go down for any reason ldap service is not lost.
For example while I working on the editing the schema on the current mail 
server    the ldap server failed a couple of times but I never lost ldap 
service.

Suppose I could try it and see what happens.

John

 



From liutauras.adomaitis at gmail.com  Tue May 19 22:58:47 2009
From: liutauras.adomaitis at gmail.com (Liutauras Adomaitis)
Date: Tue, 19 May 2009 23:58:47 +0300
Subject: Compiling Kolab 2.2.1 and php problem
In-Reply-To: <71fe4e760905151400h7eb74f17r81ca62f67b74873b@mail.gmail.com>
References: <c1ec9ac0905150000h6d500648k134818468ff0e5d6@mail.gmail.com>
	<71fe4e760905150358r5df408bbm62bf731be348df59@mail.gmail.com>
	<c1ec9ac0905150539l50b8f67yd0509cc1a7683b0a@mail.gmail.com>
	<71fe4e760905151400h7eb74f17r81ca62f67b74873b@mail.gmail.com>
Message-ID: <c1ec9ac0905191358u415ade68v10a0a53881e05f8a@mail.gmail.com>

>
> Read this
>
> http://www.kolab.org/pipermail/kolab-users/2009-April/009678.html
>

I read all those posts several times.
It seems to me, that Bernards patch is against tar problem in openpkg
compilation. Other people reported that downgrading to gcc-4.2 solves
problems.
In my situation I get different problems, in addition to problem
reported in this post, please read my post "Kolab installation problem
with perl".
I don't understand openpkg very well, but in my situation openpkg
compiles ok, because it starts to build src rpm packages for kolab and
fails on perl (as I understand) and after my patch it fails on build
php package.

I downgraded to gcc-4.2.3 (installed gcc4.2 package shiped with
Mandriva 2009.1).
I hope, that changing symlink for gcc should be enough.
[root at PBL-kolab src]# ll /etc/alternatives/
total 0
lrwxrwxrwx 1 root root 18 May 18 15:03 c++ -> /usr/bin/g++-4.3.2*
lrwxrwxrwx 1 root root 15 May 19 18:56 cpp -> /usr/bin/cpp4.2*
lrwxrwxrwx 1 root root  7 Apr 30 17:07 ex -> /bin/vi*
lrwxrwxrwx 1 root root 18 May 18 15:03 g++ -> /usr/bin/g++-4.3.2*
lrwxrwxrwx 1 root root 15 May 19 18:57 gcc -> /usr/bin/gcc4.2*
lrwxrwxrwx 1 root root 20 Apr 30 17:03 gconftool -> /usr/bin/gconftool-2*
lrwxrwxrwx 1 root root 12 May 18 15:13 gs -> /usr/bin/gsc*
lrwxrwxrwx 1 root root 18 May 14 13:49 lib_cpp -> /usr/bin/cpp-4.3.2*
lrwxrwxrwx 1 root root 25 May 18 15:17 qtconfig -> /usr/lib/qt3/bin/qtconfig*
lrwxrwxrwx 1 root root  7 Apr 30 17:07 rvi -> /bin/vi*
lrwxrwxrwx 1 root root  7 Apr 30 17:07 rview -> /bin/vi*
lrwxrwxrwx 1 root root  7 Apr 30 17:07 rvim -> /bin/vi*
lrwxrwxrwx 1 root root 16 Apr 30 17:07 uvi -> /bin/vim-minimal*
lrwxrwxrwx 1 root root 16 Apr 30 17:07 vi -> /bin/vim-minimal*
lrwxrwxrwx 1 root root  7 Apr 30 17:07 view -> /bin/vi*
lrwxrwxrwx 1 root root 16 Apr 30 17:07 vim -> /bin/vim-minimal*
lrwxrwxrwx 1 root root 19 May 15 11:01 yacc -> /usr/bin/yacc.bison*

Compiling kolab gives the same error as described in my previous post
"Kolab installation problem with perl". Patch I posted solves this
issue.
But I still have the same problem with compiling php.
/kolab/RPM/TMP/php-5.2.8/main/reentrancy.c: In function 'php_readdir_r':
/kolab/RPM/TMP/php-5.2.8/main/reentrancy.c:139: error: too few
arguments to function 'readdir_r'

I would like to note, that the same thing happens with kolab-2.2.1 and
kolab-2.2.2
I tried also on Mandriva 2009.0, totaly the same.

thaks for any hints

Liutauras



From Webmaster at computational-chemistry.org  Wed May 20 01:34:02 2009
From: Webmaster at computational-chemistry.org (Alexander =?iso-8859-1?q?Schr=F6ter?=)
Date: Wed, 20 May 2009 01:34:02 +0200
Subject: SyncML in 2.2.2 ?
In-Reply-To: <7907AE10BB50DD4F840E76527D27EF19029F684E@entmail.domain.austinent.com>
References: <7907AE10BB50DD4F840E76527D27EF19029F684E@entmail.domain.austinent.com>
Message-ID: <200905200134.02606.Webmaster@computational-chemistry.org>

Ohh really? I started out with 2.2.1 and it never worked with the Calendar. 
But I have found a hint in the php-error log of horde. Some function regarding 
the Time and Date is producing a Fatal error. Maybe I will open up a new topic 
to fix the problem.

On Tuesday 19 May 2009 06:21:57 pm Lucas Hendricks wrote:
> I cannot say for 2.2.2 yet.  But in 2.2.1 I was able to sync outlook via
> funambol for all categories, including calendar (only default personal
> calendar, though).  Theoretically that should not have changed for 2.2.2.
>
> That said, this is depending on the webclient (horde) for its ability which
> is a beta stage syncML support.  Here is a sync howto for many clients
> including blackberry with horde:
>
> http://wiki.horde.org/SyncHowTo
>
> Lucas
>
> -----Original Message-----
> From: Alexander Schr?ter [mailto:Webmaster at computational-chemistry.org]
> Sent: Tuesday, May 19, 2009 6:20 AM
> To: kolab-users at kolab.org
> Subject: Re: SyncML in 2.2.2 ?
>
> On Tuesday 19 May 2009 01:13:36 pm kiser Caesar wrote:
> > Hello the list,
> >
> >
> > With the quick answer of Alain Spineux on my last question, I want to
> > update kolab 2.2.0  to 2.2.2. But before, I want to know if with the
> > 2.2.2 I can connect my account (calendars, tasks) with my Blackberry ?
>
> Hi I cannot really answer the question regarding "Your Blackberry" but I am
> using the Funambol Client for most of my not Unix Equipment. And the
> Syncing
>
> works in all Categories but the Calendar. I am not sure if I am the only
> one
>
> with this Problem or if others experienced the same.
>
> Regards
>
> > Best regards,
> >
> > _________________________________________________________________
> > Vous voulez savoir ce que vous pouvez faire avec le nouveau Windows Live
> > ? Lancez-vous ! http://www.microsoft.com/windows/windowslive/default.aspx
>
> _______________________________________________
> 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




From kb at oe-s.de  Wed May 20 08:49:04 2009
From: kb at oe-s.de (Ulrich Oestreicher)
Date: Wed, 20 May 2009 08:49:04 +0200
Subject: SyncML in 2.2.2 ?
In-Reply-To: <200905200134.02606.Webmaster@computational-chemistry.org>
References: <7907AE10BB50DD4F840E76527D27EF19029F684E@entmail.domain.austinent.com>
	<200905200134.02606.Webmaster@computational-chemistry.org>
Message-ID: <20090520084904.206487lbqt4fshr4@oeit.de>

Hello,

I have the same problem.
Contacts and tasks works, but the calendar is not working.
I using the synthesis conector for iphone.

Have a nice day
Werner


Zitat von Alexander Schr?ter <Webmaster at computational-chemistry.org>:

> Ohh really? I started out with 2.2.1 and it never worked with the Calendar.
> But I have found a hint in the php-error log of horde. Some function  
> regarding
> the Time and Date is producing a Fatal error. Maybe I will open up a  
> new topic
> to fix the problem.
>
> On Tuesday 19 May 2009 06:21:57 pm Lucas Hendricks wrote:
>> I cannot say for 2.2.2 yet.  But in 2.2.1 I was able to sync outlook via
>> funambol for all categories, including calendar (only default personal
>> calendar, though).  Theoretically that should not have changed for 2.2.2.
>>
>> That said, this is depending on the webclient (horde) for its ability which
>> is a beta stage syncML support.  Here is a sync howto for many clients
>> including blackberry with horde:
>>
>> http://wiki.horde.org/SyncHowTo
>>
>> Lucas
>>
>> -----Original Message-----
>> From: Alexander Schr?ter [mailto:Webmaster at computational-chemistry.org]
>> Sent: Tuesday, May 19, 2009 6:20 AM
>> To: kolab-users at kolab.org
>> Subject: Re: SyncML in 2.2.2 ?
>>
>> On Tuesday 19 May 2009 01:13:36 pm kiser Caesar wrote:
>> > Hello the list,
>> >
>> >
>> > With the quick answer of Alain Spineux on my last question, I want to
>> > update kolab 2.2.0  to 2.2.2. But before, I want to know if with the
>> > 2.2.2 I can connect my account (calendars, tasks) with my Blackberry ?
>>
>> Hi I cannot really answer the question regarding "Your Blackberry" but I am
>> using the Funambol Client for most of my not Unix Equipment. And the
>> Syncing
>>
>> works in all Categories but the Calendar. I am not sure if I am the only
>> one
>>
>> with this Problem or if others experienced the same.
>>
>> Regards
>>
>> > Best regards,
>> >
>> > _________________________________________________________________
>> > Vous voulez savoir ce que vous pouvez faire avec le nouveau Windows Live
>> > ? Lancez-vous ! http://www.microsoft.com/windows/windowslive/default.aspx
>>
>> _______________________________________________
>> 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
>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



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



From shrenik.bhura at intelliant.net  Wed May 20 09:29:19 2009
From: shrenik.bhura at intelliant.net (Shrenik Bhura)
Date: Wed, 20 May 2009 12:59:19 +0530
Subject: kolab - opensuse 11.1
In-Reply-To: <200905192256.03669.ml@radoeka.nl>
References: <4A1242C5.2020104@intelliant.net>	<200905191804.12613.ml@radoeka.nl>	<4A12FA88.6050405@intelliant.net>
	<200905192256.03669.ml@radoeka.nl>
Message-ID: <4A13B14F.4060100@intelliant.net>



Richard Bos wrote:
-- snip --
>> Mail received. :) Worked like a charm.
>> The only issue was this:
>> I only got this error while doing "# zypper in kolab" and it installed
>> all the other packages:
>> Installation of horde-form-0.0.2-4.16 failed:
>> (with --nodeps --force) Error: Subprocess failed. Error: RPM failed:
>> Package "/var/lib/pear/Horde_Form.xml" is not valid
>> install failed
>> error: %post(horde-form-0.0.2-4.16.noarch) scriptlet failed, exit status 1
>>
>> Abort, retry, ignore? [A/r/i]: i
>>     
>
> Hmmm, there is an easy trick to make this warning harmless, which is already 
> used in horde-token/horde-token.  The trick is the "|| echo"  piece.
> pear install --nodeps --soft --force --register-only %{xmldir}/%{prj}.xml || 
> echo > /dev/null
> But I would like to know why the installation of the Horde_Form.xml file 
> fails...  If this error always happen, please let us know.
>  
Richard,

Do you want me to do this?

# pear install --nodeps --soft --force --register-only
horde-form/horde-form.xml || echo > /dev/null
Attempting to discover channel "horde-form"...
downloading ?url=horde-form%3A80%2Fchannel.xml ...
Starting to download ?url=horde-form%3A80%2Fchannel.xml (1,915 bytes)
....done: 1,915 bytes
Package "horde-form/horde-form.xml" is not valid
install failed

I will try this with one more installation in a test VM and revert with
the results.

I am also unable to log in into the webclient. It makes a log in attempt
and returns to the same page. Haven't found anything suspicious in the
apache or mail logs. Please do guide me where to look for any log.

Is there an IRC where you guys hang out? That may help speed up the
testing cycles.

Regards,
SB



From liutauras.adomaitis at gmail.com  Wed May 20 09:35:09 2009
From: liutauras.adomaitis at gmail.com (Liutauras Adomaitis)
Date: Wed, 20 May 2009 10:35:09 +0300
Subject: Compiling Kolab 2.2.1 and php problem
In-Reply-To: <c1ec9ac0905191358u415ade68v10a0a53881e05f8a@mail.gmail.com>
References: <c1ec9ac0905150000h6d500648k134818468ff0e5d6@mail.gmail.com>
	<71fe4e760905150358r5df408bbm62bf731be348df59@mail.gmail.com>
	<c1ec9ac0905150539l50b8f67yd0509cc1a7683b0a@mail.gmail.com>
	<71fe4e760905151400h7eb74f17r81ca62f67b74873b@mail.gmail.com>
	<c1ec9ac0905191358u415ade68v10a0a53881e05f8a@mail.gmail.com>
Message-ID: <c1ec9ac0905200035n3bda6c3cg92c39f22d87e5f54@mail.gmail.com>

On Tue, May 19, 2009 at 11:58 PM, Liutauras Adomaitis
<liutauras.adomaitis at gmail.com> wrote:
>>
>> Read this
>>
>> http://www.kolab.org/pipermail/kolab-users/2009-April/009678.html
>>
>
> I read all those posts several times.
> It seems to me, that Bernards patch is against tar problem in openpkg
> compilation. Other people reported that downgrading to gcc-4.2 solves
> problems.
> In my situation I get different problems, in addition to problem
> reported in this post, please read my post "Kolab installation problem
> with perl".
> I don't understand openpkg very well, but in my situation openpkg
> compiles ok, because it starts to build src rpm packages for kolab and
> fails on perl (as I understand) and after my patch it fails on build
> php package.
>
> I downgraded to gcc-4.2.3 (installed gcc4.2 package shiped with
> Mandriva 2009.1).
> I hope, that changing symlink for gcc should be enough.
> [root at PBL-kolab src]# ll /etc/alternatives/
> total 0
> lrwxrwxrwx 1 root root 18 May 18 15:03 c++ -> /usr/bin/g++-4.3.2*
> lrwxrwxrwx 1 root root 15 May 19 18:56 cpp -> /usr/bin/cpp4.2*
> lrwxrwxrwx 1 root root ?7 Apr 30 17:07 ex -> /bin/vi*
> lrwxrwxrwx 1 root root 18 May 18 15:03 g++ -> /usr/bin/g++-4.3.2*
> lrwxrwxrwx 1 root root 15 May 19 18:57 gcc -> /usr/bin/gcc4.2*
> lrwxrwxrwx 1 root root 20 Apr 30 17:03 gconftool -> /usr/bin/gconftool-2*
> lrwxrwxrwx 1 root root 12 May 18 15:13 gs -> /usr/bin/gsc*
> lrwxrwxrwx 1 root root 18 May 14 13:49 lib_cpp -> /usr/bin/cpp-4.3.2*
> lrwxrwxrwx 1 root root 25 May 18 15:17 qtconfig -> /usr/lib/qt3/bin/qtconfig*
> lrwxrwxrwx 1 root root ?7 Apr 30 17:07 rvi -> /bin/vi*
> lrwxrwxrwx 1 root root ?7 Apr 30 17:07 rview -> /bin/vi*
> lrwxrwxrwx 1 root root ?7 Apr 30 17:07 rvim -> /bin/vi*
> lrwxrwxrwx 1 root root 16 Apr 30 17:07 uvi -> /bin/vim-minimal*
> lrwxrwxrwx 1 root root 16 Apr 30 17:07 vi -> /bin/vim-minimal*
> lrwxrwxrwx 1 root root ?7 Apr 30 17:07 view -> /bin/vi*
> lrwxrwxrwx 1 root root 16 Apr 30 17:07 vim -> /bin/vim-minimal*
> lrwxrwxrwx 1 root root 19 May 15 11:01 yacc -> /usr/bin/yacc.bison*
>
> Compiling kolab gives the same error as described in my previous post
> "Kolab installation problem with perl". Patch I posted solves this
> issue.
> But I still have the same problem with compiling php.
> /kolab/RPM/TMP/php-5.2.8/main/reentrancy.c: In function 'php_readdir_r':
> /kolab/RPM/TMP/php-5.2.8/main/reentrancy.c:139: error: too few
> arguments to function 'readdir_r'
>
> I would like to note, that the same thing happens with kolab-2.2.1 and
> kolab-2.2.2
> I tried also on Mandriva 2009.0, totaly the same.
>

http://bugs.php.net/bug.php?id=11275 says it is a POSIX and OLD STYLE
readdir problem. This post is very old.
So the question: may it be the problem with openpkg and how to fix it?
Do i have to patch openpkg php or I should patch other packages to
make sure it works?

Thanks for your time
Liutauras



From bernhard at intevation.de  Wed May 20 10:02:02 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 20 May 2009 10:02:02 +0200
Subject: Problem with acls migrating from cyrus imap.
In-Reply-To: <200905191006.19201.johnm@advocap.org>
References: <200905130907.33120.johnm@advocap.org>
	<71fe4e760905151421x43a3e30fy8e616cc27d615000@mail.gmail.com>
	<200905191006.19201.johnm@advocap.org>
Message-ID: <200905201002.06905.bernhard@intevation.de>

Am Dienstag, 19. Mai 2009 17:06:18 schrieb John McMonagle:
> The problem with imapsync is that I still would have to manually fix all
> the acls for shared mailboxes.

Hmm if imapsync doesn not transfer the ACL settings, maybe we should come up 
with a script that does or enhance imapsync. From the technology point of 
view, the best solution is to do this via IMAP.
An alternative would be to script it on the server via IMAP, e.g. like
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/utils/admin/kolab-mailboxinfo.pl

-- 
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-users/attachments/20090520/c67384f8/attachment.bin

From bernhard at intevation.de  Wed May 20 10:05:46 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 20 May 2009 10:05:46 +0200
Subject: Compiling Kolab 2.2.1 and php problem
In-Reply-To: <c1ec9ac0905191358u415ade68v10a0a53881e05f8a@mail.gmail.com>
References: <c1ec9ac0905150000h6d500648k134818468ff0e5d6@mail.gmail.com>
	<71fe4e760905151400h7eb74f17r81ca62f67b74873b@mail.gmail.com>
	<c1ec9ac0905191358u415ade68v10a0a53881e05f8a@mail.gmail.com>
Message-ID: <200905201005.47091.bernhard@intevation.de>

Am Dienstag, 19. Mai 2009 22:58:47 schrieb Liutauras Adomaitis:
> > http://www.kolab.org/pipermail/kolab-users/2009-April/009678.html
>
> I read all those posts several times.
> It seems to me, that Bernards patch is against tar problem in openpkg
> compilation. Other people reported that downgrading to gcc-4.2 solves
> problems.

Yes, this is true and my fix was incorporated for the server 2.2.1 and 2.2.2 
releases, so the problem with gcc-4.2 and tar is gone. The whole server 
compiled for us and others with new gcc versions after the change.

> In my situation I get different problems, in addition to problem
> reported in this post, please read my post "Kolab installation problem
> with perl".
> I don't understand openpkg very well, but in my situation openpkg
> compiles ok

Reading your post I must admit, I've lost the overview a bit.
Best probably is to create an issue with all (relevant) information for each 
seperate problem you have with Kolab Server 2.2.2.

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-users/attachments/20090520/7b49e8f3/attachment.bin

From bernhard at intevation.de  Wed May 20 10:14:24 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 20 May 2009 10:14:24 +0200
Subject: SyncML in 2.2.2 ?
In-Reply-To: <20090520084904.206487lbqt4fshr4@oeit.de>
References: <7907AE10BB50DD4F840E76527D27EF19029F684E@entmail.domain.austinent.com>
	<200905200134.02606.Webmaster@computational-chemistry.org>
	<20090520084904.206487lbqt4fshr4@oeit.de>
Message-ID: <200905201014.25257.bernhard@intevation.de>

Alexander, Ulrich,

thanks for the reports and feedback we appreciate it.
Yes, calender sync should be working (though you might need to trigger two 
syncs sometimes). If it does not, opening a problem report with the tracker
is very good, if you can provide detailed information.

We face the problem that we do not have all the models of hardware and 
software available and testing many combinations is costly.
<advertisment>If you have funding for this, Kolab-Konsortium will be happy to 
buy your device, test and fix support for it, if possible.
</advertisment>

Am Mittwoch, 20. Mai 2009 08:49:04 schrieb Ulrich Oestreicher:
> I have the same problem.
> Contacts and tasks works, but the calendar is not working.
> I using the synthesis conector for iphone.

> Zitat von Alexander Schr?ter <Webmaster at computational-chemistry.org>:
> > Ohh really? I started out with 2.2.1 and it never worked with the
> > Calendar. But I have found a hint in the php-error log of horde. Some
> > function regarding
> > the Time and Date is producing a Fatal error. Maybe I will open up a ?
> > new topic
> > to fix the problem.

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-users/attachments/20090520/ce64627c/attachment.bin

From bernhard at intevation.de  Wed May 20 10:18:16 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 20 May 2009 10:18:16 +0200
Subject: whitelist
In-Reply-To: <200905190834.31183.johnm@advocap.org>
References: <200905190834.31183.johnm@advocap.org>
Message-ID: <200905201018.16717.bernhard@intevation.de>

Am Dienstag, 19. Mai 2009 15:34:30 schrieb John McMonagle:
>  see there is a whitelist filter ?in horde.
> I am assuming that it is just ?the sieve filter or does it also hook in to
> the spam controls?

The web client does not have credentials to change the system settings.
(A good thing giving our security architecture.) So it must mean a sieve
filter for the user. Note that I saw a number of problems with the web clients
sieve filter fly by, your milage might vary.

> It doesn't do much good to whitelist if it's been blocked before it gets to
> you :-(
> If this is not the case is there a spam whitelist in kolab?

Kolab Server uses amavisd new to trigger a number of check,
e.g. spamassasin and clamav. You can plug additional checks into it and also 
whitelisting. So yes, there is whitelisting and everything else that you can 
drive from amavisd new or postfix. ;)

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-users/attachments/20090520/41286795/attachment.bin

From bernhard at intevation.de  Wed May 20 10:21:59 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 20 May 2009 10:21:59 +0200
Subject: ldap questions.
In-Reply-To: <200905191555.59009.johnm@advocap.org>
References: <200905191555.59009.johnm@advocap.org>
Message-ID: <200905201022.00194.bernhard@intevation.de>

Am Dienstag, 19. Mai 2009 22:55:58 schrieb John McMonagle:
> Really the only merge question is this really needed in slapd.conf?
> allow           bind_v2
> It seems to run fine without it.

The manpage says:
     bind_v2  allows  acceptance  of  LDAPv2  bind requests.

I do not remember any case where this is necessary, so if you do not have any 
problems with it, I guess it can be removed. However testing has been done 
with this setting.

> Any chance one can put multiple servers for ldap_uri   in kolab.conf
>
> For example in my current mail servers saslauthd.conf have:
> ldap_servers: ldapi:///var/run/ldapi ldaps://fonldap.advocap.org
> ldaps://mstldap
> .advocap.org
> Sure that wrapped but have 3 servers.
> Everywere else I use ldap do the same.
>
> The neat thing  is if any go down for any reason ldap service is not lost.
> For example while I working on the editing the schema on the current mail
> server    the ldap server failed a couple of times but I never lost ldap
> service.
>
> Suppose I could try it and see what happens.

The chance is small I would guess as this is needed at a few code places and I 
am unsure if they all support a list of servers. You would need to try and 
check.


-- 
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-users/attachments/20090520/04e84865/attachment.bin

From carsten at cburghardt.com  Wed May 20 10:23:14 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Wed, 20 May 2009 10:23:14 +0200
Subject: SyncML in 2.2.2 ?
In-Reply-To: <200905201014.25257.bernhard@intevation.de>
References: <7907AE10BB50DD4F840E76527D27EF19029F684E@entmail.domain.austinent.com>
	<200905200134.02606.Webmaster@computational-chemistry.org>
	<20090520084904.206487lbqt4fshr4@oeit.de>
	<200905201014.25257.bernhard@intevation.de>
Message-ID: <20090520102314.639728tk8hjh4kkk@www.inovox.de>


Zitat von Bernhard Reiter <bernhard at intevation.de>:

> Alexander, Ulrich,
>
> thanks for the reports and feedback we appreciate it.
> Yes, calender sync should be working (though you might need to trigger two
> syncs sometimes). If it does not, opening a problem report with the tracker
> is very good, if you can provide detailed information.
>
> We face the problem that we do not have all the models of hardware and
> software available and testing many combinations is costly.
> <advertisment>If you have funding for this, Kolab-Konsortium will be happy to
> buy your device, test and fix support for it, if possible.
> </advertisment>

That said, did anybody successfully sync a Nokia mobile phone with the  
current version? I tried it with 5800 and the only thing that actually  
worked was to send all the contacts and calendar entries from the  
phone to Horde. As soon as you get updates from the server the phone  
produces errors. Apart from this the contacts are simply appended  
every time and not updated so they double with every sync.


Regards

Carsten



From benoit.mortier at opensides.be  Wed May 20 11:00:16 2009
From: benoit.mortier at opensides.be (Benoit Mortier)
Date: Wed, 20 May 2009 11:00:16 +0200
Subject: Problem with acls migrating from cyrus imap.
In-Reply-To: <200905201002.06905.bernhard@intevation.de>
References: <200905130907.33120.johnm@advocap.org>
	<200905191006.19201.johnm@advocap.org>
	<200905201002.06905.bernhard@intevation.de>
Message-ID: <200905201100.16743.benoit.mortier@opensides.be>

Le Wednesday 20 May 2009 10:02:02 Bernhard Reiter, vous avez ?crit?:
> Am Dienstag, 19. Mai 2009 17:06:18 schrieb John McMonagle:

Hello,

> > The problem with imapsync is that I still would have to manually fix
> > all the acls for shared mailboxes.
>
> Hmm if imapsync doesn not transfer the ACL settings, maybe we should
> come up with a script that does or enhance imapsync. From the

Enhancing imapsync is the way to go. it so usefull for imap migrations

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



From tim at timstone.com  Mon May 18 16:40:25 2009
From: tim at timstone.com (Tim)
Date: Mon, 18 May 2009 16:40:25 +0200
Subject: Kontact Windows 2009-02-20 - KMail "account types"
Message-ID: <0MKuxg-1M64163xvI-00011C@mrelayeu.kundenserver.de>

 

Hello,

I am trying to help a friend who has been given a pc with Mandriva on it.

It has Open Office and Kontact as an email program.

I am completely familiar with setting up mail accounts in both Outlook and
Outlook express but have never used Kontact.

I do have all the "Outlook" settings (server details, password, POP3 and
SMTP settings etc).

What is making it more difficult for me is that I have to do it all in
French which is not my native language!

If you can tell me if it is as simple as Outlook to add an account and what
Kontact calls accounts etc I should be able to figure it all out.

I hope you do not mind me asking you this, and thank you in anticipation of
any help you are able to give.

Best regards

Tim 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20090518/53aee1b1/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 5675 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20090518/53aee1b1/attachment.jpeg

From alain.abbas at libertech.Fr  Wed May 20 10:41:00 2009
From: alain.abbas at libertech.Fr (Alain Abbas)
Date: Wed, 20 May 2009 10:41:00 +0200
Subject: SyncML in 2.2.2 ?
Message-ID: <b9afd424.1c9d926.306f335.2e39@libertech.Fr>

hi 
normal for iphone Apple doesn t allow to access to calenar for an external application 
and the version 3 anounce the sync with caldav .... 

we are working on z-push and already done the sync of the calendar and contacts
work with kolab 2.2.1 and 2.2.2 
the state of our work :
for contacts :
-not all the fieds are synchronized and not the picture of the contact

for the calendar :
request meeting not implemented for the moment 

for mail :
Imap is better ..... 

if someone is interested .... 


-----Message d'origine-----
De?: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org] De la part de Bernhard Reiter
Envoy??: mercredi 20 mai 2009 10:14
??: kolab-users at kolab.org
Objet?: Re: SyncML in 2.2.2 ?

Alexander, Ulrich,

thanks for the reports and feedback we appreciate it.
Yes, calender sync should be working (though you might need to trigger two syncs sometimes). If it does not, opening a problem report with the tracker is very good, if you can provide detailed information.

We face the problem that we do not have all the models of hardware and software available and testing many combinations is costly.
<advertisment>If you have funding for this, Kolab-Konsortium will be happy to buy your device, test and fix support for it, if possible.
</advertisment>

Am Mittwoch, 20. Mai 2009 08:49:04 schrieb Ulrich Oestreicher:
> I have the same problem.
> Contacts and tasks works, but the calendar is not working.
> I using the synthesis conector for iphone.

> Zitat von Alexander Schr?ter <Webmaster at computational-chemistry.org>:
> > Ohh really? I started out with 2.2.1 and it never worked with the 
> > Calendar. But I have found a hint in the php-error log of horde. 
> > Some function regarding the Time and Date is producing a Fatal 
> > error. Maybe I will open up a new topic to fix the problem.

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



From liutauras.adomaitis at gmail.com  Wed May 20 12:02:59 2009
From: liutauras.adomaitis at gmail.com (Liutauras Adomaitis)
Date: Wed, 20 May 2009 13:02:59 +0300
Subject: Compiling Kolab 2.2.1 and php problem
In-Reply-To: <200905201005.47091.bernhard@intevation.de>
References: <c1ec9ac0905150000h6d500648k134818468ff0e5d6@mail.gmail.com>
	<71fe4e760905151400h7eb74f17r81ca62f67b74873b@mail.gmail.com>
	<c1ec9ac0905191358u415ade68v10a0a53881e05f8a@mail.gmail.com>
	<200905201005.47091.bernhard@intevation.de>
Message-ID: <c1ec9ac0905200302ybeb5eaepc121a07f94e4b5d1@mail.gmail.com>

Ok, I will submit a new post with all info.

2009/5/20 Bernhard Reiter <bernhard at intevation.de>:
> Am Dienstag, 19. Mai 2009 22:58:47 schrieb Liutauras Adomaitis:
>> > http://www.kolab.org/pipermail/kolab-users/2009-April/009678.html
>>
>> I read all those posts several times.
>> It seems to me, that Bernards patch is against tar problem in openpkg
>> compilation. Other people reported that downgrading to gcc-4.2 solves
>> problems.
>
> Yes, this is true and my fix was incorporated for the server 2.2.1 and 2.2.2
> releases, so the problem with gcc-4.2 and tar is gone. The whole server
> compiled for us and others with new gcc versions after the change.
>
>> In my situation I get different problems, in addition to problem
>> reported in this post, please read my post "Kolab installation problem
>> with perl".
>> I don't understand openpkg very well, but in my situation openpkg
>> compiles ok
>
> Reading your post I must admit, I've lost the overview a bit.
> Best probably is to create an issue with all (relevant) information for each
> seperate problem you have with Kolab Server 2.2.2.
>
> 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
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
>



From Webmaster at computational-chemistry.org  Wed May 20 13:02:47 2009
From: Webmaster at computational-chemistry.org (Alexander =?utf-8?q?Schr=C3=B6ter?=)
Date: Wed, 20 May 2009 13:02:47 +0200
Subject: Kontact Windows 2009-02-20 - KMail "account types"
In-Reply-To: <0MKuxg-1M64163xvI-00011C@mrelayeu.kundenserver.de>
References: <0MKuxg-1M64163xvI-00011C@mrelayeu.kundenserver.de>
Message-ID: <200905201302.47926.Webmaster@computational-chemistry.org>

Hi you should be able to setup a Kolab Account with by starting 
"groupwarewizard". And it is structured so simple you could probably do it in 
any language.

Good Luck.
Regards

On Monday 18 May 2009 04:40:25 pm Tim wrote:
> Hello,
>
> I am trying to help a friend who has been given a pc with Mandriva on it.
>
> It has Open Office and Kontact as an email program.
>
> I am completely familiar with setting up mail accounts in both Outlook and
> Outlook express but have never used Kontact.
>
> I do have all the "Outlook" settings (server details, password, POP3 and
> SMTP settings etc).
>
> What is making it more difficult for me is that I have to do it all in
> French which is not my native language!
>
> If you can tell me if it is as simple as Outlook to add an account and what
> Kontact calls accounts etc I should be able to figure it all out.
>
> I hope you do not mind me asking you this, and thank you in anticipation of
> any help you are able to give.
>
> Best regards
>
> Tim



From liutauras.adomaitis at gmail.com  Wed May 20 13:05:18 2009
From: liutauras.adomaitis at gmail.com (Liutauras Adomaitis)
Date: Wed, 20 May 2009 14:05:18 +0300
Subject: Kontact Windows 2009-02-20 - KMail "account types"
In-Reply-To: <0MKuxg-1M64163xvI-00011C@mrelayeu.kundenserver.de>
References: <0MKuxg-1M64163xvI-00011C@mrelayeu.kundenserver.de>
Message-ID: <c1ec9ac0905200405r1311d7dayb9c2ee94f15ef4f3@mail.gmail.com>

2009/5/18 Tim <tim at timstone.com>:
> Hello,
>
> I am trying to help a friend who has been given a pc with Mandriva on it.
>
> It has Open Office and Kontact as an email program.
>
> I am completely familiar with setting up mail accounts in both Outlook and
> Outlook express but have never used Kontact.
>
> I do have all the “Outlook” settings (server details, password, POP3 and
> SMTP settings etc).
>
> What is making it more difficult for me is that I have to do it all in
> French which is not my native language!
>
> If you can tell me if it is as simple as Outlook to add an account and what
> Kontact calls accounts etc I should be able to figure it all out.
>
> I hope you do not mind me asking you this, and thank you in anticipation of
> any help you are able to give.
>
> Best regards
>
> Tim
>

Did you tried:
urpmi kdepim4-wizards

Then launch KDE GroupWare wizard from Internet menu of KDE application
launcher.

Assuming you are using 2009.1 aor 2009.0

Liutauras



From johnm at advocap.org  Wed May 20 13:50:24 2009
From: johnm at advocap.org (John McMonagle)
Date: Wed, 20 May 2009 06:50:24 -0500
Subject: ldap questions.
In-Reply-To: <200905201022.00194.bernhard@intevation.de>
References: <200905191555.59009.johnm@advocap.org>
	<200905201022.00194.bernhard@intevation.de>
Message-ID: <200905200650.25421.johnm@advocap.org>

On Wednesday 20 May 2009 03:21:59 am Bernhard Reiter wrote:

>
> > Any chance one can put multiple servers for ldap_uri   in kolab.conf
> >
> > For example in my current mail servers saslauthd.conf have:
> > ldap_servers: ldapi:///var/run/ldapi ldaps://fonldap.advocap.org
> > ldaps://mstldap
> > .advocap.org
> > Sure that wrapped but have 3 servers.
> > Everywere else I use ldap do the same.
> >
> > The neat thing  is if any go down for any reason ldap service is not
> > lost. For example while I working on the editing the schema on the
> > current mail server    the ldap server failed a couple of times but I
> > never lost ldap service.
> >
> > Suppose I could try it and see what happens.
>
> The chance is small I would guess as this is needed at a few code places
> and I am unsure if they all support a list of servers. You would need to
> try and check.
I tried it.

Just one error:
 /kolab/sbin/kolabconf
OpenPKG: stop: sasl.
Syntax error on line 198 of /kolab/etc/apache/apache.conf:
Invalid LDAP connection mode setting: must be one of NONE, SSL, or 
TLS/STARTTLS
postfix/postfix-script: refreshing the Postfix mail system
OpenPKG: restart: imapd.

line is 
AuthLDAPURL ldap://127.0.0.1 ldaps::389/dc=advocap,dc=org?mail

Oh well it was worth a try :-)

John








From Webmaster at computational-chemistry.org  Wed May 20 13:53:46 2009
From: Webmaster at computational-chemistry.org (Alexander =?utf-8?q?Schr=C3=B6ter?=)
Date: Wed, 20 May 2009 13:53:46 +0200
Subject: Unable to Sync Calendar / PHP Fatal error compareDateTime()
Message-ID: <200905201353.46188.Webmaster@computational-chemistry.org>

Hello I am using Kolab since 2.2.1 and just updated to 2.2.2. System is a 
Debian Lenny with Kolab compiled from Source.

Since my first installation I am not able to sync my Calendar Data with with 
Outlook, Thunderbird etc. via the different Funambol Clients.

Here is what I did to make it work half way.

>Requirements: Running Kolab Server.
>1. Add the CA-Certificate and the Server-Certificate to the "Trusted 
Certificates" in Windows.
>2. Set up the Funambol Outlook Client with Correct settings:
>        Server-address: http(s)://yourdomain?/client/rpc.php
>        Username and Password
>3. The first time you must sync Tasks, Contacts, Notes one after another ... 
this could relate to my Error but I am not sure.

Now I read on the mailing list that it should work. So I checked the logs for 
errors that only happen when I sync stuff. And this is the one I found in the 
/kolab/var/kolab/www/client/log/php-errors.log

"PHP Fatal error :  Call to a member function compareDateTime() on a non-
object in /kolab/var/kolab/www/client/kronolith/lib/Driver/kolab.php on line 
1153"

Since I am anything but a good coder ... please can somebody help me fix this.

If there are people with the same problem can you please check if you might 
get the same error?

Regards Alexander



From johnm at advocap.org  Wed May 20 14:20:02 2009
From: johnm at advocap.org (John McMonagle)
Date: Wed, 20 May 2009 07:20:02 -0500
Subject: whitelist
In-Reply-To: <200905201018.16717.bernhard@intevation.de>
References: <200905190834.31183.johnm@advocap.org>
	<200905201018.16717.bernhard@intevation.de>
Message-ID: <200905200720.03403.johnm@advocap.org>

On Wednesday 20 May 2009 03:18:16 am Bernhard Reiter wrote:
> Am Dienstag, 19. Mai 2009 15:34:30 schrieb John McMonagle:
> >  see there is a whitelist filter ?in horde.
> > I am assuming that it is just ?the sieve filter or does it also hook in
> > to the spam controls?
>
> The web client does not have credentials to change the system settings.
> (A good thing giving our security architecture.) So it must mean a sieve
> filter for the user. Note that I saw a number of problems with the web
> clients sieve filter fly by, your milage might vary.
>
It would be nice if users could whitelist for them self.
If so would be only for that user and keep the virus checks.

> > It doesn't do much good to whitelist if it's been blocked before it gets
> > to you :-(
> > If this is not the case is there a spam whitelist in kolab?
>
> Kolab Server uses amavisd new to trigger a number of check,
> e.g. spamassasin and clamav. You can plug additional checks into it and
> also whitelisting. So yes, there is whitelisting and everything else that
> you can drive from amavisd new or postfix. ;)
>
> Bernhard

Bernard

Thanks for the quick answer
Wanted to make sure there was not something already in place.

More questions to come as I don't understand some of the postfix 
configuration.

John



From liutauras.adomaitis at gmail.com  Wed May 20 15:00:19 2009
From: liutauras.adomaitis at gmail.com (Liutauras Adomaitis)
Date: Wed, 20 May 2009 16:00:19 +0300
Subject: Kolab 2.2.1 and 2.2.2 does not install
Message-ID: <c1ec9ac0905200600y2a018aa9x2a86e8df998937ad@mail.gmail.com>

This is a post to summarize and make clear things posted by me in:

>from Liutauras Adomaitis <liutauras.adomaitis at gmail.com>
>to Kolab-users at kolab.org
>date Thu, May 14, 2009 at 11:49 PM
>subject Kolab installation problem with perl

and
>from Liutauras Adomaitis <liutauras.adomaitis at gmail.com>
>to kolab-users at kolab.org
>date Fri, May 15, 2009 at 10:00 AM
>subject Compiling Kolab 2.2.1 and php problem

The procedure i do:
1. #rsync -L -rtzvP
rsync://rsync.kolab.org/kolab/server/release/kolab-server-2.2.2/sources/
/usr/local/src/kolab-2.2.2
2. mount new partition to /kolab
3. run: #export TMPDIR=/tmp
4. run #sh install-kolab.sh 2>&1 | tee /root/kolab-install.log
after a while I get (pasting this to indicate that openpkg is installed):
______________________________________________
:::: /tmp/install-kolab.904.31271.10029.31393/openpkg-20071227-20071227_kolab1.src.rpm
::::
:::: /tmp/install-kolab.904.31271.10029.31393/openpkg-20071227-20071227_kolab1.src.rpm
= 0 ::::
:::: /tmp/install-kolab.904.31271.10029.31393/make-3.81-20080101.src.rpm
::::
Installing /tmp/install-kolab.904.31271.10029.31393/make-3.81-20080101.src.rpm
Executing(%prep): env -i /kolab/lib/openpkg/bash --norc --noprofile
--posix -e /kolab/RPM/TMP/rpm-tmp.10119
______________________________________________
.......
---- W A I T -----
.......
And get this
______________________________________________
opmini.c: In function 'Perl_fold_constants':
opmini.c:2340: warning: variable 'curop' might be clobbered by
'longjmp' or 'vfork'
/kolab/bin/gcc -L/kolab/lib -o miniperl \
? ? ? ? ? ?`echo ? gv.o toke.o perly.o op.o pad.o regcomp.o dump.o
util.o mg.o reentr.o mro.o hv.o av.o perl.o run.o pp_hot.o sv.o pp.o
scope.o pp_ctl.o pp_sys.o doop.o doio.o regexec.o utf8.o taint.o deb.o
universal.o xsutils.o globals.o perlio.o perlapi.o numeric.o mathoms.o
locale.o pp_pack.o pp_sort.o ?| sed 's/ op.o / /'` \
? ? ? ? ? ?miniperlmain.o opmini.o -lnsl -ldl -lm -lcrypt -lutil -lc
./miniperl -w -Ilib -MExporter -e '<?>' || /kolab/bin/make minitest
./miniperl -Ilib configpm
written lib/Config.pod
updated lib/Config.pm
updated lib/Config_heavy.pl
./miniperl -Ilib lib/lib_pm.PL
Extracting lib.pm (with variable substitutions)
? ? ? ?AutoSplitting perl library
./miniperl -Ilib -e 'use AutoSplit; \
? ? ? ? ? ? ? ?autosplit_lib_modules(@ARGV)' lib/*.pm
./miniperl -Ilib -e 'use AutoSplit; \
? ? ? ? ? ? ? ?autosplit_lib_modules(@ARGV)' lib/*/*.pm
/kolab/bin/make lib/re.pm
cp ext/re/re.pm lib/re.pm
./miniperl minimod.pl > lib/ExtUtils/Miniperl.pm
cd lib/unicore && ? ../../miniperl -I../../lib mktables -w
touch uni.data
`sh ?cflags "optimize='-O2 -pipe'" perlmain.o` ?perlmain.c
? ? ? ? ?CCCMD = ?/kolab/bin/gcc -DPERL_CORE -c -fno-strict-aliasing
-pipe -I/kolab/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-std=c89 -O2 -pipe -Wall -ansi ? -W -Wextra
-Wdeclaration-after-statement -Wendif-labels -Wc++-compat

? ? ? ?Making DynaLoader (static)
Processing hints file hints/linux.pl
opendir(./../../../../../../..): Permission denied at
../../lib/File/Spec/Unix.pm line 478
opendir(./../../../../../../..): Permission denied at
../../lib/File/Spec/Unix.pm line 478
opendir(./../../../../../../..): Permission denied at
../../lib/File/Spec/Unix.pm line 478
Writing Makefile for DynaLoader
/bin/sh: /miniperl: No such file or directory
make[1]: *** [../../lib/.exists] Error 127
/kolab/bin/make config failed, continuing anyway...
/bin/sh: /miniperl: No such file or directory
make[1]: *** [../../lib/.exists] Error 127
make: *** [DynaLoader.o] Error 2
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.39639 (%build)


RPM build errors:
? ?Bad exit status from /kolab/RPM/TMP/rpm-tmp.39639 (%build)
Command exited with non-zero status 1
__________________________________________________

Thats is were I should stop. So here should Kolab Guru tell us where
is a problem.
I did a research myself, and got a patch:
___________________________________
[root at PBL-kolab kolab-2.2.2]# cat /root/cwd.diff
--- lib/Cwd.pm ?Tue Dec 18 10:47:07 2007
+++ lib/Cwd.pm.cwd ? ? ?Thu Jan 24 12:33:29 2008
@@ -501,6 +501,11 @@
sub _perl_abs_path
{
? ? my $start = @_ ? shift : '.';
+
+ ? ?# this just returns a path down from /, without attempting to
+ ? ?# resolve .. or symlinks. It *may* be sufficient to build perl.
+ ? ?return $start =~ m!^/! ? $start : cwd() . '/' . $start;
+
? ? my($dotdots, $cwd, @pst, @cst, $dir, @tst);

? ? unless (@cst = stat( $start ))
_______________________________________

so my next steps:
5. run the same command as in step 4:  #sh install-kolab.sh 2>&1 | tee
/root/kolab-install.log
6. Wait while above command extracts perl and starts building process.
On the other terminal I do:
#cd /kolab/RPM/TMP/perl-5.10.0
#patch -p0 < /root/cwd.diff
This step helps me out to pass errors which I get at first attempt to
build kolab. Now it goes much further, until it starts compiling
apache-php for kolab. I get this:
________________________________________
/bin/sh /kolab/RPM/TMP/php-5.2.8/libtool --silent --preserve-dup-deps
--mode=compile /kolab/bin/cc  -Imain/ -I/kolab/RPM/TMP/php-5.2.8/main/
-DPHP_ATOM_INC -I/kolab/RPM/TMP/php-5.2.8/include
-I/kolab/RPM/TMP/php-5.2.8/main -I/kolab/RPM/TMP/php-5.2.8
-I/kolab/include/libxml2 -I/kolab/include
-I/kolab/RPM/TMP/php-5.2.8/ext/date/lib -I/kolab/include/imap
-I/kolab/RPM/TMP/php-5.2.8/ext/mbstring/oniguruma
-I/kolab/RPM/TMP/php-5.2.8/ext/mbstring/libmbfl
-I/kolab/RPM/TMP/php-5.2.8/ext/mbstring/libmbfl/mbfl
-I/kolab/RPM/TMP/php-5.2.8/TSRM -I/kolab/RPM/TMP/php-5.2.8/Zend
-I/kolab/include  -I/kolab/include -O2 -pipe  -prefer-non-pic -c
/kolab/RPM/TMP/php-5.2.8/main/reentrancy.c -o main/reentrancy.lo
/kolab/RPM/TMP/php-5.2.8/main/reentrancy.c: In function 'php_readdir_r':
/kolab/RPM/TMP/php-5.2.8/main/reentrancy.c:139: error: too few
arguments to function 'readdir_r'
make: *** [main/reentrancy.lo] Error 1
error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.44527 (%build)


RPM build errors:
    Bad exit status from /kolab/RPM/TMP/rpm-tmp.44527 (%build)
Command exited with non-zero status 1
________________________________________

Thats is it I'm here so far.
Any ideas?

My thoughts:

From johnm at advocap.org  Wed May 20 15:24:13 2009
From: johnm at advocap.org (John McMonagle)
Date: Wed, 20 May 2009 08:24:13 -0500
Subject: ldap questions.
In-Reply-To: <200905200650.25421.johnm@advocap.org>
References: <200905191555.59009.johnm@advocap.org>
	<200905201022.00194.bernhard@intevation.de>
	<200905200650.25421.johnm@advocap.org>
Message-ID: <200905200824.13700.johnm@advocap.org>

On Wednesday 20 May 2009 06:50:24 am John McMonagle wrote:
> On Wednesday 20 May 2009 03:21:59 am Bernhard Reiter wrote:
> > > Any chance one can put multiple servers for ldap_uri   in kolab.conf
> > >
> > > For example in my current mail servers saslauthd.conf have:
> > > ldap_servers: ldapi:///var/run/ldapi ldaps://fonldap.advocap.org
> > > ldaps://mstldap
> > > .advocap.org
> > > Sure that wrapped but have 3 servers.
> > > Everywere else I use ldap do the same.
> > >
> > > The neat thing  is if any go down for any reason ldap service is not
> > > lost. For example while I working on the editing the schema on the
> > > current mail server    the ldap server failed a couple of times but I
> > > never lost ldap service.
> > >
> > > Suppose I could try it and see what happens.
> >
> > The chance is small I would guess as this is needed at a few code places
> > and I am unsure if they all support a list of servers. You would need to
> > try and check.
>
> I tried it.
>
> Just one error:
>  /kolab/sbin/kolabconf
> OpenPKG: stop: sasl.
> Syntax error on line 198 of /kolab/etc/apache/apache.conf:
> Invalid LDAP connection mode setting: must be one of NONE, SSL, or
> TLS/STARTTLS
> postfix/postfix-script: refreshing the Postfix mail system
> OpenPKG: restart: imapd.
>
> line is
> AuthLDAPURL ldap://127.0.0.1 ldaps::389/dc=advocap,dc=org?mail
>
Need to read what I post :-)
Looks like kolabconf  messed up the second url.

I did a second try
in kolab.conf
ldap_uri : ldap://127.0.0.1:389 ldaps://mstldap.advocap.org:636

gives in apache.conf
AuthLDAPURL ldap://127.0.0.1 ldaps::389/dc=advocap,dc=org?mail

Should I do a bug report?

I just looked up the documeation at 

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

An example 
AuthLDAPURL "ldap://ldap1.airius.com ldap2.airius.com/ou=People, o=Airius"
Says it can take multiple servers.  

John



From alain.abbas at libertech.Fr  Wed May 20 18:05:00 2009
From: alain.abbas at libertech.Fr (Alain Abbas)
Date: Wed, 20 May 2009 18:05:00 +0200
Subject: z-push backend
Message-ID: <64ca4fd8.1c9d931.34cddc4.4d50@libertech.Fr>

hi 
you can find an alpha version (0.1) of the kolab backend for z-push at support.libertech.fr in the download
section with an installation note.

for the moment : 
-Calendar work on iphone and mobilePC (tested on HTC) 

-Contacts work on iphone an mobilePC 

-task not yet implemented 

be carefull read the note (the known issue, and todo list  ) , not for a production use  :-) 



-----Message d'origine-----
De?: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org] De la part de Alain Abbas
Envoy??: mercredi 20 mai 2009 10:41
??: 'Bernhard Reiter'
Cc?: 'kolab-users at kolab.org'
Objet?: RE: SyncML in 2.2.2 ?

hi 
normal for iphone Apple doesn t allow to access to calenar for an external application 
and the version 3 anounce the sync with caldav .... 

we are working on z-push and already done the sync of the calendar and contacts
work with kolab 2.2.1 and 2.2.2 
the state of our work :
for contacts :
-not all the fieds are synchronized and not the picture of the contact

for the calendar :
request meeting not implemented for the moment 

for mail :
Imap is better ..... 

if someone is interested .... 


-----Message d'origine-----
De?: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org] De la part de Bernhard Reiter
Envoy??: mercredi 20 mai 2009 10:14
??: kolab-users at kolab.org
Objet?: Re: SyncML in 2.2.2 ?

Alexander, Ulrich,

thanks for the reports and feedback we appreciate it.
Yes, calender sync should be working (though you might need to trigger two syncs sometimes). If it does not, opening a problem report with the tracker is very good, if you can provide detailed information.

We face the problem that we do not have all the models of hardware and software available and testing many combinations is costly.
<advertisment>If you have funding for this, Kolab-Konsortium will be happy to buy your device, test and fix support for it, if possible.
</advertisment>

Am Mittwoch, 20. Mai 2009 08:49:04 schrieb Ulrich Oestreicher:
> I have the same problem.
> Contacts and tasks works, but the calendar is not working.
> I using the synthesis conector for iphone.

> Zitat von Alexander Schr?ter <Webmaster at computational-chemistry.org>:
> > Ohh really? I started out with 2.2.1 and it never worked with the 
> > Calendar. But I have found a hint in the php-error log of horde. 
> > Some function regarding the Time and Date is producing a Fatal 
> > error. Maybe I will open up a new topic to fix the problem.

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

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




From steuwer at univention.de  Wed May 20 18:07:32 2009
From: steuwer at univention.de (Ingo Steuwer)
Date: Wed, 20 May 2009 18:07:32 +0200
Subject: SyncML in 2.2.2 ?
In-Reply-To: <b9afd424.1c9d926.306f335.2e39@libertech.Fr>
References: <b9afd424.1c9d926.306f335.2e39@libertech.Fr>
Message-ID: <200905201807.34208.steuwer@univention.de>

Hi,

Am Mittwoch, 20. Mai 2009 schrieb Alain Abbas:
> hi
> normal for iphone Apple doesn t allow to access to calenar for an external
> application and the version 3 anounce the sync with caldav ....
>
> we are working on z-push and already done the sync of the calendar and
> contacts work with kolab 2.2.1 and 2.2.2
> the state of our work :
> for contacts :
> -not all the fieds are synchronized and not the picture of the contact
>
> for the calendar :
> request meeting not implemented for the moment
>
> for mail :
> Imap is better .....
>
> if someone is interested ....
>
[..]

I'm interested on more informations about this. Would you like to summarize 
what you've done, patched etc. to get things running, maybe here in a mail or 
in the wiki?

Regards
Ingo

-- 
Ingo Steuwer
Head of Professional Services

Univention GmbH
Linux for your business
Mary-Somerville-Str.1
28359 Bremen
Tel.: +49 421 22232-43
Fax : +49 421 22232-99
Mob : +49 173 2112971

steuwer at univention.de>
http://www.univention.de

Gesch?ftsf?hrer: Peter H. Ganten
HRB 20755 Amtsgericht Bremen
Steuer-Nr.: 71-597-02876 



From alain.abbas at libertech.Fr  Wed May 20 18:26:00 2009
From: alain.abbas at libertech.Fr (Alain Abbas)
Date: Wed, 20 May 2009 18:26:00 +0200
Subject: z-push backend
Message-ID: <b95dd304.1c9d967.fbdfdb.29@libertech.Fr>

this is the readme that i provided with the download

Z-push is an emulation of Activesync protocol , you can with it connect your pda like if 
the server is an exchange 


1 Installation of Z-push (http://z-push.sourceforge.net/soswp/)

assuming that the root folder is /kolab

install folder z-push ( download it ) in  /kolab/var/kolab/www

in the file  /kolab/etc/kolab/templates/httpd.local.template  
add :
Alias /Microsoft-Server-ActiveSync /kolab/var/kolab/www/z-push/index.php
The right of the folder ./state must be 777 
create ./kolabindex/uid_id et ./kolabindex/id_uid
The right these  folders 777


copy  kolab.php in the folder ./bakend (download it for the moment at support.libertech.fr)
in the file ./config.php 

modify  
 // The data providers that we are using (see configuration below)
    $BACKEND_PROVIDER = "BackendKolab";
Add : 

 define('KOLAB_SERVER', '127.0.0.1');  
 define('KOLAB_IMAP_OPTIONS', '/notls/norsh');  
 define('KOLAB_IMAP_PORT', 143); 
 define('KOLAB_INDEX',"kolabindex");
 define('KOLAB_CONTACT_FOLDER',"inbox.contacts");
 define('KOLAB_DIARY_FOLDER',"inbox.calendrier");

on  Kolab <=2.2.1 or if there are an error : (debug file)
to have a debug file simply create with 666 rights debug.txt file on z-push directory 
 
05/19/09 10:59:43 [1851] /kolab/var/kolab/www/z-push/backend/kolab.php:26 requir
e_once(Horde/Kolab/Format.php) [<a href='function.require-once'>function.require
-once</a>]: failed to open stream: No such file or directory (2)
install: 
pear channel-discover pear.horde.org
pear install --force channel://pear.horde.org/Kolab_Format


Kown Issue: 

the Mail part is not tested yet because we use IMAP instead activesync for the mail , but the code is the code of the Imap backend. We saw some problems with it on the Iphone 
Task are not implemented yet

Calendar : 
-must fix the timeZone it is coded in hard for the moment
-must be find the mail off the user 
-problem with appointment who are full day and on more one day (on iphone)
-request meeting not implemented

Contacts :
-the contact's picture is not synchronized
-some supplementary fields are not synchronized like spouse, birthday ....




TODO :
fix the timezone 
fix the address mail 
implement more one kolab server ( ask to ldap who is the right server to open the imap connexion)
find a solution for the meeting request and accept or reject 
sync more than one folder (list per user)
more tracability 


-----Message d'origine-----
De?: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org] De la part de Alain Abbas
Envoy??: mercredi 20 mai 2009 18:05
??: 'kolab-users at kolab.org'
Objet?: z-push backend

hi 
you can find an alpha version (0.1) of the kolab backend for z-push at support.libertech.fr in the download
section with an installation note.

for the moment : 
-Calendar work on iphone and mobilePC (tested on HTC) 

-Contacts work on iphone an mobilePC 

-task not yet implemented 

be carefull read the note (the known issue, and todo list  ) , not for a production use  :-) 



-----Message d'origine-----
De?: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org] De la part de Alain Abbas
Envoy??: mercredi 20 mai 2009 10:41
??: 'Bernhard Reiter'
Cc?: 'kolab-users at kolab.org'
Objet?: RE: SyncML in 2.2.2 ?

hi 
normal for iphone Apple doesn t allow to access to calenar for an external application 
and the version 3 anounce the sync with caldav .... 

we are working on z-push and already done the sync of the calendar and contacts
work with kolab 2.2.1 and 2.2.2 
the state of our work :
for contacts :
-not all the fieds are synchronized and not the picture of the contact

for the calendar :
request meeting not implemented for the moment 

for mail :
Imap is better ..... 

if someone is interested .... 


-----Message d'origine-----
De?: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org] De la part de Bernhard Reiter
Envoy??: mercredi 20 mai 2009 10:14
??: kolab-users at kolab.org
Objet?: Re: SyncML in 2.2.2 ?

Alexander, Ulrich,

thanks for the reports and feedback we appreciate it.
Yes, calender sync should be working (though you might need to trigger two syncs sometimes). If it does not, opening a problem report with the tracker is very good, if you can provide detailed information.

We face the problem that we do not have all the models of hardware and software available and testing many combinations is costly.
<advertisment>If you have funding for this, Kolab-Konsortium will be happy to buy your device, test and fix support for it, if possible.
</advertisment>

Am Mittwoch, 20. Mai 2009 08:49:04 schrieb Ulrich Oestreicher:
> I have the same problem.
> Contacts and tasks works, but the calendar is not working.
> I using the synthesis conector for iphone.

> Zitat von Alexander Schr?ter <Webmaster at computational-chemistry.org>:
> > Ohh really? I started out with 2.2.1 and it never worked with the 
> > Calendar. But I have found a hint in the php-error log of horde. 
> > Some function regarding the Time and Date is producing a Fatal 
> > error. Maybe I will open up a new topic to fix the problem.

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

_______________________________________________
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



From t.nintemann at medial-networks.de  Wed May 20 20:19:16 2009
From: t.nintemann at medial-networks.de (Thomas Nintemann)
Date: Wed, 20 May 2009 20:19:16 +0200
Subject: Unable to Sync Calendar / PHP Fatal error compareDateTime()
In-Reply-To: <200905201353.46188.Webmaster@computational-chemistry.org>
References: <200905201353.46188.Webmaster@computational-chemistry.org>
Message-ID: <200905202019.16646.t.nintemann@medial-networks.de>


> Now I read on the mailing list that it should work. So I checked the logs
> for errors that only happen when I sync stuff. And this is the one I found
> in the /kolab/var/kolab/www/client/log/php-errors.log
>
> "PHP Fatal error :  Call to a member function compareDateTime() on a non-
> object in /kolab/var/kolab/www/client/kronolith/lib/Driver/kolab.php on
> line 1153"

Same on my Side with Kolab 2.2.1 native on OpenSUSE-11.1.
My Client is a Blackberry 8300 Curve with actual Funambol-Plugin.

For stupid test  i comment out the Line 1153 and 1154 as here:
/*if (!(($endDate->compareDateTime($event->start) < 0) ||
                  ($startDate->compareDateTime($event->end) > 0)))*/

and it sync's.
But i now this a bad idea.

Any better idea's?

Thomas



From kloecker at kde.org  Wed May 20 20:25:03 2009
From: kloecker at kde.org (Ingo =?iso-8859-15?q?Kl=F6cker?=)
Date: Wed, 20 May 2009 20:25:03 +0200
Subject: Kontact Windows 2009-02-20 - KMail "account types"
In-Reply-To: <0MKuxg-1M64163xvI-00011C@mrelayeu.kundenserver.de>
References: <0MKuxg-1M64163xvI-00011C@mrelayeu.kundenserver.de>
Message-ID: <200905202025.08562@thufir.ingo-kloecker.de>

On Monday 18 May 2009, Tim wrote:
> Hello,
>
> I am trying to help a friend who has been given a pc with Mandriva on
> it.
>
> It has Open Office and Kontact as an email program.
>
> I am completely familiar with setting up mail accounts in both
> Outlook and Outlook express but have never used Kontact.
>
> I do have all the "Outlook" settings (server details, password, POP3
> and SMTP settings etc).
>
> What is making it more difficult for me is that I have to do it all
> in French which is not my native language!

You could simply switch the language used by KDE temporarily to English. 
The English translation is built into all KDE applications.


Regards,
Ingo
-------------- 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-users/attachments/20090520/0e391385/attachment.bin

From ml at radoeka.nl  Wed May 20 21:12:42 2009
From: ml at radoeka.nl (Richard Bos)
Date: Wed, 20 May 2009 21:12:42 +0200
Subject: kolab - opensuse 11.1
In-Reply-To: <4A13B14F.4060100@intelliant.net>
References: <4A1242C5.2020104@intelliant.net>
	<200905192256.03669.ml@radoeka.nl>
	<4A13B14F.4060100@intelliant.net>
Message-ID: <200905202112.43333.ml@radoeka.nl>

Hi Shrenik,

Op woensdag 20 mei 2009 09:29:19 schreef Shrenik Bhura:
> Richard Bos wrote:
> -- snip --
>
> >> Mail received. :) Worked like a charm.
> >> The only issue was this:
> >> I only got this error while doing "# zypper in kolab" and it installed
> >> all the other packages:
> >> Installation of horde-form-0.0.2-4.16 failed:
> >> (with --nodeps --force) Error: Subprocess failed. Error: RPM failed:
> >> Package "/var/lib/pear/Horde_Form.xml" is not valid
> >> install failed
> >> error: %post(horde-form-0.0.2-4.16.noarch) scriptlet failed, exit status
> >> 1
> >>
> >> Abort, retry, ignore? [A/r/i]: i
> >
> > Hmmm, there is an easy trick to make this warning harmless, which is
> > already used in horde-token/horde-token.  The trick is the "|| echo" 
> > piece. pear install --nodeps --soft --force --register-only
> > %{xmldir}/%{prj}.xml || echo > /dev/null
> > But I would like to know why the installation of the Horde_Form.xml file
> > fails...  If this error always happen, please let us know.
>
> Richard,
>
> Do you want me to do this?

No, not really.  I just showed that it is possible to have the rpm install 
succesfully although the pear install command fails.  It's a trick, and it 
looks harmless to me, I hope the horde devs agree ;)

> # pear install --nodeps --soft --force --register-only
> horde-form/horde-form.xml || echo > /dev/null
> Attempting to discover channel "horde-form"...
> downloading ?url=horde-form%3A80%2Fchannel.xml ...
> Starting to download ?url=horde-form%3A80%2Fchannel.xml (1,915 bytes)
> ....done: 1,915 bytes
> Package "horde-form/horde-form.xml" is not valid
> install failed

The manual command should be:
# rpm -ql --scripts horde-form     
postinstall scriptlet (using /bin/sh):
pear install --nodeps --soft --force --register-only \ 
/var/lib/pear/Horde_Form.xml

> I will try this with one more installation in a test VM and revert with
> the results.
>
> I am also unable to log in into the webclient. It makes a log in attempt
> and returns to the same page. Haven't found anything suspicious in the
> apache or mail logs. Please do guide me where to look for any log.

I can't help you with this, sorry.

> Is there an IRC where you guys hang out? That may help speed up the
> testing cycles.

irc.freenode.org channel #kolab
I'm sometimes there, mostly only after a request via email.

-- 
Richard



From liutauras.adomaitis at gmail.com  Thu May 21 11:52:29 2009
From: liutauras.adomaitis at gmail.com (Liutauras Adomaitis)
Date: Thu, 21 May 2009 12:52:29 +0300
Subject: Kolab 2.2.1 and 2.2.2 does not install
In-Reply-To: <c1ec9ac0905200600y2a018aa9x2a86e8df998937ad@mail.gmail.com>
References: <c1ec9ac0905200600y2a018aa9x2a86e8df998937ad@mail.gmail.com>
Message-ID: <c1ec9ac0905210252g4c20b90ch5c13519f6aeb2ebc@mail.gmail.com>

UPDATE:

i got other patch:
__________________________________________________________
[root at PBL-kolab kolab-2.2.2]# cat /root/posix_php_config.h.diff
--- main/php_config.h   2009-05-20 15:32:30.000000000 +0300
+++ main/php_config.h.posix     2009-05-20 22:37:33.000000000 +0300
@@ -1150,10 +1150,10 @@
 /* #undef PHP_IRIX_TIME_R */

 /* whether you have POSIX readdir_r */
-/* #undef HAVE_POSIX_READDIR_R */
+#define HAVE_POSIX_READDIR_R 1

 /* whether you have old-style readdir_r */
-#define HAVE_OLD_READDIR_R 1
+/* #undef HAVE_OLD_READDIR_R 1 */

 /*   */
 /* #undef in_addr_t */
_________________________________________________________

This one helps to build apache-php and php. I had to apply it twice,
because Kolab install script is building php twice. It worked both
times. I applied it in the dirty manner i did with perl patch -
patched while php was build on the other terminal. It worked.
Now I have working kolab. Did not do extensive tests, but created
admin user account, created admin distribution lists, configured
settings (all of this was done via Kolab web interface), then tested
if pop3d and smtp services with ssl support is working by sending and
receiving test email for admin user. It works.

If somebody understand what they do, then maybe there is more elegant
way to make kolab install.

Can someone tell me how to test Kolab to make sure these patches does
not have any side effects? Probably there must be some files and
directory operations with Kolab, because these patches solved cwd and
readdir_r problems while build.

Liutauras



From Nicholas.Moore at tsr-i.com  Thu May 21 14:11:09 2009
From: Nicholas.Moore at tsr-i.com (Nicholas Moore)
Date: Thu, 21 May 2009 14:11:09 +0200
Subject: imap or dimap
Message-ID: <200905211411.10114.Nicholas.Moore@tsr-i.com>

Hi,

I am running Kolab (2.2.0-2.3-i586) on OpenSuse 11.1 in a small aapplication for 3 users.  

An imap mail server was my priority and that works fine. I now wish to try the groupware functions. Is it mandatory to create a disconnected imap in order to use groupware?

My experience is that with an ordinary imap the groupware folders do not get created and so are not available for configuration. In the Kmail>config>misc groupware tab the 'Resource folders are in account' field is blank.

Regards

Nicholas

-- 
Nicholas Moore
Lioges
France
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20090521/025dd2e7/attachment.html

From ml at radoeka.nl  Thu May 21 14:18:16 2009
From: ml at radoeka.nl (Richard Bos)
Date: Thu, 21 May 2009 14:18:16 +0200
Subject: imap or dimap
In-Reply-To: <200905211411.10114.Nicholas.Moore@tsr-i.com>
References: <200905211411.10114.Nicholas.Moore@tsr-i.com>
Message-ID: <200905211418.17988.ml@radoeka.nl>

Op donderdag 21 mei 2009 14:11:09 schreef Nicholas Moore:
> An imap mail server was my priority and that works fine. I now wish to try
> the groupware functions. Is it mandatory to create a disconnected imap in
> order to use groupware?

Yes.

-- 
Richard



From johnm at advocap.org  Thu May 21 21:57:00 2009
From: johnm at advocap.org (John McMonagle)
Date: Thu, 21 May 2009 14:57:00 -0500
Subject: postfix config questions.
Message-ID: <200905211457.01206.johnm@advocap.org>

Making a pass through main.conf before merging in my old configs.

I'm getting a bit lost trying to trace out kolabmailboxfilter and kolabfilter.
A little surprised to see php code.

As far as I can see
kolabmailboxfilter   handles delivering mail to imap.
kolabfilter       does amavisd etc.

Is that close enough?
Anything else I should know?

John



From shrenik.bhura at intelliant.net  Thu May 21 21:58:06 2009
From: shrenik.bhura at intelliant.net (Shrenik Bhura)
Date: Fri, 22 May 2009 01:28:06 +0530
Subject: trouble logging into horde
In-Reply-To: <4A130A7D.30707@intelliant.net>
References: <200904140027.40133.sunil@khiatani.ath.cx>	<20090507215328.29131wci9adgib0g@webmail.pardus.de>
	<4A130A7D.30707@intelliant.net>
Message-ID: <4A15B24E.5060804@intelliant.net>



Shrenik Bhura wrote:
> Gunnar Wrobel wrote:
>   
>> Quoting Sunil Khiatani <sunil at khiatani.ath.cx>:
>>
>>     
>>> Hi,
>>>
>>> I recently upgraded to horde 2.2.1, but i can no longer log
>>> into the horde webclient.  I'm not sure where to look for logs and
>>> what to do
>>> next.
>>>
>>> When I log in with the correct username and password, I get
>>> returned to the login page with no errors.
>>>       
> I am now facing the same problem on opensuse 11.1 installation. The mail
> delivery part is working fine though. Just can't log in into the horde
> based web-client.
>   
Hi Sunil,

Did you manage to solve this? What was it? Please share it in some detail.

Thanks,
SB



From shrenik.bhura at intelliant.net  Thu May 21 22:04:24 2009
From: shrenik.bhura at intelliant.net (Shrenik Bhura)
Date: Fri, 22 May 2009 01:34:24 +0530
Subject: trouble logging into horde
In-Reply-To: <4A130A7D.30707@intelliant.net>
References: <200904140027.40133.sunil@khiatani.ath.cx>	<20090507215328.29131wci9adgib0g@webmail.pardus.de>
	<4A130A7D.30707@intelliant.net>
Message-ID: <4A15B3C8.5020505@intelliant.net>



Shrenik Bhura wrote:
> Gunnar Wrobel wrote:
>   
>> Quoting Sunil Khiatani <sunil at khiatani.ath.cx>:
>>
>>     
>>> Hi,
>>>
>>> I recently upgraded to horde 2.2.1, but i can no longer log
>>> into the horde webclient.  I'm not sure where to look for logs and
>>> what to do
>>> next.
>>>
>>> When I log in with the correct username and password, I get
>>> returned to the login page with no errors.
>>>       
> I am now facing the same problem on opensuse 11.1 installation. The mail
> delivery part is working fine though. Just can't log in into the horde
> based web-client
Alar,

Could you please share the permissions you have on /srv/www/htdocs/horde
? It could possibly be that as I don't see any error/logs anywhere.

Cheers,
SB



From francesco at trimarchi.it  Fri May 22 17:12:23 2009
From: francesco at trimarchi.it (francesco trimarchi)
Date: Fri, 22 May 2009 17:12:23 +0200
Subject: trouble accessing webmail after upgrading from kolab 2.2.0 to 2.2.2
Message-ID: <000001c9daef$b8584000$2908c000$@it>

Hello to everybody!
Sorry for previous message in html format!

I've this problem: after upgrading form kolab 2.2.0 to 2.2.2, the webmail
not works.
When I try to login, after I insert the credentials, the login page reappair
without any error!
If I login with wrong credentials, a correct security warning is displayed.

The horde.log file displays the following lineson each try:

May 22 16:39:43 HORDE [debug] [imp] Hook _prefs_change_hook_last_login in
application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [notice] [imp] Login success for
administrator at domain.tld [172.17.16.150] to {groupware.domain.tld:143
[imap/notls/novalidate-cert]} [pid 4510 on line 304 of
"/kolab/var/kolab/www/client/imp/lib/Session.php"]
May 22 16:39:44 HORDE [debug] [imp] Hook _prefs_change_hook_last_maintenance
in application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] Max memory usage: 10223616 bytes [pid
4510 on line 339 of "/kolab/var/kolab/www/client/lib/Horde/Registry.php"]
May 22 16:39:44 HORDE [debug] [imp] IMAP errors: SECURITY PROBLEM: insecure
server advertised AUTH=PLAIN SECURITY PROBLEM: insecure server advertised
AUTH=PLAIN [pid 4510 on line 175 of
"/kolab/var/kolab/www/client/imp/lib/IMAP.php"]
May 22 16:39:44 HORDE [debug] [horde] Max memory usage: 4980736 bytes [pid
4510 on line 339 of "/kolab/var/kolab/www/client/lib/Horde/Registry.php"]
May 22 16:39:44 HORDE [debug] [horde] Max memory usage: 4980736 bytes [pid
4510 on line 339 of "/kolab/var/kolab/www/client/lib/Horde/Registry.php"]
May 22 16:39:44 HORDE [debug] [kronolith] Hook _horde_hook_share_init in
application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [error] [kronolith] Errore IMAP. Server:
groupware.domain.tld. Errore: IMAP Authentication cancelled [pid 4510 on
line 1330 of "/kolab/var/kolab/www/client/kronolith/lib/Kronolith.php"]
May 22 16:39:44 HORDE [debug] [kronolith] Hook
_prefs_change_hook_display_remote_cals in application horde not called. [pid
4510 on line 1683 of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [kronolith] Guest user does not have READ
permission for turba [pid 4510 on line 814 of
"/kolab/var/kolab/www/client/lib/Horde/Registry.php"]
May 22 16:39:44 HORDE [debug] [kronolith] Guest user does not have READ
permission for nag [pid 4510 on line 814 of
"/kolab/var/kolab/www/client/lib/Horde/Registry.php"]
May 22 16:39:44 HORDE [debug] [kronolith] Hook
_prefs_change_hook_display_external_cals in application horde not called.
[pid 4510 on line 1683 of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [kronolith] Hook
_prefs_change_hook_display_cals in application horde not called. [pid 4510
on line 1683 of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [nag] Hook _horde_hook_share_init in
application horde not called. [pid 4510 on line 1683 of
"/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [error] [nag] Errore IMAP. Server:
groupware.domain.tld. Errore: IMAP Authentication cancelled [pid 4510 on
line 281 of "/kolab/var/kolab/www/client/nag/lib/Nag.php"]
May 22 16:39:44 HORDE [error] [nag] Errore IMAP. Server:
groupware.domain.tld. Errore: IMAP Authentication cancelled [pid 4510 on
line 281 of "/kolab/var/kolab/www/client/nag/lib/Nag.php"]
May 22 16:39:44 HORDE [debug] [nag] Hook
_prefs_change_hook_display_tasklists in application horde not called. [pid
4510 on line 1683 of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 22 16:39:44 HORDE [debug] [imp] SQL query by Horde_Alarm_sql::_list():
SELECT alarm_id, alarm_uid, alarm_start, alarm_end, alarm_methods,
alarm_params, alarm_title, alarm_text, alarm_snooze, alarm_internal FROM
horde_alarms WHERE alarm_dismissed = 0 AND ((alarm_snooze IS NULL AND
alarm_start <= ?) OR alarm_snooze <= ?) AND (alarm_end IS NULL OR alarm_end
>= ?) AND (alarm_uid = ? OR alarm_uid = ?) ORDER BY alarm_start, alarm_end
[pid 4510 on line 148 of
"/kolab/var/kolab/www/client/lib/Horde/Alarm/sql.php"]
May 22 16:39:44 HORDE [debug] [imp] Max memory usage: 11534336 bytes [pid
4510 on line 339 of "/kolab/var/kolab/www/client/lib/Horde/Registry.php"]



Someone can help me?


Best regards

Francesco






From dvadell at linuxclusters.com.ar  Fri May 22 17:28:25 2009
From: dvadell at linuxclusters.com.ar (Diego M. Vadell)
Date: Fri, 22 May 2009 14:28:25 -0100
Subject: Unable to Sync Calendar / PHP Fatal error compareDateTime()
In-Reply-To: <200905202019.16646.t.nintemann@medial-networks.de>
References: <200905201353.46188.Webmaster@computational-chemistry.org>
	<200905202019.16646.t.nintemann@medial-networks.de>
Message-ID: <200905221428.26905.dvadell@linuxclusters.com.ar>

Hi,

  I'm in the dark here, not knowing at all the guts of Horde, but a quick 
google search led me to putting "$this" in front of the objects. The code 
looks like this:

            /* check if event period intersects with given period */
            // if (!(($endDate->compareDateTime($event->start) < 0) ||
            //       ($startDate->compareDateTime($event->end) > 0))) {

            if (!(($this->endDate->compareDateTime($event->start) < 0) ||
                  ($this->startDate->compareDateTime($event->end) > 0))) {
                $keep_event = true;
            }

Please if you try it, know that I'm just guessing.
I will continue testing Kolab 2.2.2 and report if I get any error with this. 

Cheers,
 -- Diego.

On Wednesday 20 May 2009 17:19:16 Thomas Nintemann wrote:
> > Now I read on the mailing list that it should work. So I checked the logs
> > for errors that only happen when I sync stuff. And this is the one I
> > found in the /kolab/var/kolab/www/client/log/php-errors.log
> >
> > "PHP Fatal error :  Call to a member function compareDateTime() on a non-
> > object in /kolab/var/kolab/www/client/kronolith/lib/Driver/kolab.php on
> > line 1153"
>
> Same on my Side with Kolab 2.2.1 native on OpenSUSE-11.1.
> My Client is a Blackberry 8300 Curve with actual Funambol-Plugin.
>
> For stupid test  i comment out the Line 1153 and 1154 as here:
> /*if (!(($endDate->compareDateTime($event->start) < 0) ||
>                   ($startDate->compareDateTime($event->end) > 0)))*/
>
> and it sync's.
> But i now this a bad idea.
>
> Any better idea's?
>
> Thomas
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users




From dvadell at linuxclusters.com.ar  Fri May 22 17:36:35 2009
From: dvadell at linuxclusters.com.ar (Diego M. Vadell)
Date: Fri, 22 May 2009 14:36:35 -0100
Subject: Unable to Sync Calendar / PHP Fatal error compareDateTime() -
	SORRY!
In-Reply-To: <200905221428.26905.dvadell@linuxclusters.com.ar>
References: <200905201353.46188.Webmaster@computational-chemistry.org>
	<200905202019.16646.t.nintemann@medial-networks.de>
	<200905221428.26905.dvadell@linuxclusters.com.ar>
Message-ID: <200905221436.35957.dvadell@linuxclusters.com.ar>

Hi,

   I wrote this last mail too early. This modification breaks Horde, so please 
don't do anything!

 Sorry for the noise,

 -- Diego

On Friday 22 May 2009 14:28:25 Diego M. Vadell wrote:
> Hi,
>
>   I'm in the dark here, not knowing at all the guts of Horde, but a quick
> google search led me to putting "$this" in front of the objects. The code
> looks like this:
>
>             /* check if event period intersects with given period */
>             // if (!(($endDate->compareDateTime($event->start) < 0) ||
>             //       ($startDate->compareDateTime($event->end) > 0))) {
>
>             if (!(($this->endDate->compareDateTime($event->start) < 0) ||
>                   ($this->startDate->compareDateTime($event->end) > 0))) {
>                 $keep_event = true;
>             }
>
> Please if you try it, know that I'm just guessing.
> I will continue testing Kolab 2.2.2 and report if I get any error with
> this.
>
> Cheers,
>  -- Diego.
>
> On Wednesday 20 May 2009 17:19:16 Thomas Nintemann wrote:
> > > Now I read on the mailing list that it should work. So I checked the
> > > logs for errors that only happen when I sync stuff. And this is the one
> > > I found in the /kolab/var/kolab/www/client/log/php-errors.log
> > >
> > > "PHP Fatal error :  Call to a member function compareDateTime() on a
> > > non- object in
> > > /kolab/var/kolab/www/client/kronolith/lib/Driver/kolab.php on line
> > > 1153"
> >
> > Same on my Side with Kolab 2.2.1 native on OpenSUSE-11.1.
> > My Client is a Blackberry 8300 Curve with actual Funambol-Plugin.
> >
> > For stupid test  i comment out the Line 1153 and 1154 as here:
> > /*if (!(($endDate->compareDateTime($event->start) < 0) ||
> >                   ($startDate->compareDateTime($event->end) > 0)))*/
> >
> > and it sync's.
> > But i now this a bad idea.
> >
> > Any better idea's?
> >
> > Thomas
> >
> > _______________________________________________
> > 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




From shrenik.bhura at intelliant.net  Fri May 22 20:18:08 2009
From: shrenik.bhura at intelliant.net (Shrenik Bhura)
Date: Fri, 22 May 2009 23:48:08 +0530
Subject: R: trouble logging into horde
In-Reply-To: <003901c9dacd$d5a37520$80ea5f60$@it>
References: <200904140027.40133.sunil@khiatani.ath.cx>	<20090507215328.29131wci9adgib0g@webmail.pardus.de>	<4A130A7D.30707@intelliant.net>
	<4A15B3C8.5020505@intelliant.net>
	<003901c9dacd$d5a37520$80ea5f60$@it>
Message-ID: <4A16EC60.3030703@intelliant.net>

Francesco,

Haven't got a clue as yet. Will be working on this late next week. Shall keep the list updated in case of any progress is made.

SB

PS: Please mail to the list and not to me individually. It shall be helpful for all. :)




francesco trimarchi wrote:
> I have the same problem after upgrade from 2.2.0 to 2.2.2
>
> In this case I found something wrong in the /kolab/var/imapd/log/imad.log
> file:
>
> May 22 13:04:33 groupware.domain.tld <debug> imap[5200]: SQUAT failed to
> open index file
> May 22 13:04:33 groupware.domain.tld <debug> imap[5200]: SQUAT failed
>
>
> Can you help me?
>
> Francesco
>
>
>
>
> -----Messaggio originale-----
> Da: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org] Per
> conto di Shrenik Bhura
> Inviato: gioved? 21 maggio 2009 22.04
> A: shrenik.bhura at intelliant.net
> Cc: Gunnar Wrobel; Richard Bos; kolab-users at kolab.org
> Oggetto: Re: trouble logging into horde
>
>
>
> Shrenik Bhura wrote:
>   
>> Gunnar Wrobel wrote:
>>   
>>     
>>> Quoting Sunil Khiatani <sunil at khiatani.ath.cx>:
>>>
>>>     
>>>       
>>>> Hi,
>>>>
>>>> I recently upgraded to horde 2.2.1, but i can no longer log
>>>> into the horde webclient.  I'm not sure where to look for logs and
>>>> what to do
>>>> next.
>>>>
>>>> When I log in with the correct username and password, I get
>>>> returned to the login page with no errors.
>>>>       
>>>>         
>> I am now facing the same problem on opensuse 11.1 installation. The mail
>> delivery part is working fine though. Just can't log in into the horde
>> based web-client
>>     
> Alar,
>
> Could you please share the permissions you have on /srv/www/htdocs/horde
> ? It could possibly be that as I don't see any error/logs anywhere.
>
> Cheers,
> SB
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users



From shrenik.bhura at intelliant.net  Sun May 24 22:36:10 2009
From: shrenik.bhura at intelliant.net (Shrenik Bhura)
Date: Mon, 25 May 2009 02:06:10 +0530
Subject: trouble accessing webmail after upgrading from kolab 2.2.0 to
	2.2.2
In-Reply-To: <000001c9daef$b8584000$2908c000$@it>
References: <000001c9daef$b8584000$2908c000$@it>
Message-ID: <4A19AFBA.8010001@intelliant.net>



francesco trimarchi wrote:
> Hello to everybody!
> Sorry for previous message in html format!
>
> I've this problem: after upgrading form kolab 2.2.0 to 2.2.2, the webmail
> not works.
> When I try to login, after I insert the credentials, the login page reappair
> without any error!
> If I login with wrong credentials, a correct security warning is displayed.
>
> The horde.log file displays the following lineson each try:
>
> May 22 16:39:43 HORDE [debug] [imp] Hook _prefs_change_hook_last_login in
> application horde not called. [pid 4510 on line 1683 of
> "/kolab/var/kolab/www/client/lib/Horde.php"
-- snip --

> line 281 of "/kolab/var/kolab/www/client/nag/lib/Nag.php"]
> May 22 16:39:44 HORDE [debug] [nag] Hook
> _prefs_change_hook_display_tasklists in application horde not called. [pid
> 4510 on line 1683 of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 22 16:39:44 HORDE [debug] [imp] SQL query by Horde_Alarm_sql::_list():
> SELECT alarm_id, alarm_uid, alarm_start, alarm_end, alarm_methods,
> alarm_params, alarm_title, alarm_text, alarm_snooze, alarm_internal FROM
> horde_alarms WHERE alarm_dismissed = 0 AND ((alarm_snooze IS NULL AND
> alarm_start <= ?) OR alarm_snooze <= ?) AND (alarm_end IS NULL OR alarm_end
>   
>> = ?) AND (alarm_uid = ? OR alarm_uid = ?) ORDER BY alarm_start, alarm_end
>>     
> [pid 4510 on line 148 of
> "/kolab/var/kolab/www/client/lib/Horde/Alarm/sql.php"]
> May 22 16:39:44 HORDE [debug] [imp] Max memory usage: 11534336 bytes [pid
> 4510 on line 339 of "/kolab/var/kolab/www/client/lib/Horde/Registry.php"]
I too was facing this issue but got resolved when I used the
kolab_bootstrap server host name to access webclient. Earlier I was
using the IP address.
Hoping it helps.

SB



From shrenik.bhura at intelliant.net  Mon May 25 10:22:06 2009
From: shrenik.bhura at intelliant.net (Shrenik Bhura)
Date: Mon, 25 May 2009 13:52:06 +0530
Subject: openSUSE 11.1 LDAP dynamic config back-end + kolab
Message-ID: <4A1A552E.3050806@intelliant.net>

Hello,

Is it safe to use yast ldap-server once we have configured kolab?

# yast ldap-server

I am getting this warning :

Your system is currently configured to use the configuration
file /etc/openldap/slapd.conf. This YaST module only supports the dynamic
configuration database of OpenLDAP (back-config). Do you want to migrate
your
existing configuration to the configuration database?
(x) Migrate existing configuration
( ) Create a new configuration from scratch
 
Hoping that migrating existing config would not break things for kolab.

Any suggestions?

SB



From shrenik.bhura at intelliant.net  Mon May 25 10:37:44 2009
From: shrenik.bhura at intelliant.net (Shrenik Bhura)
Date: Mon, 25 May 2009 14:07:44 +0530
Subject: openSUSE 11.1 LDAP dynamic config back-end + kolab
In-Reply-To: <4A1A552E.3050806@intelliant.net>
References: <4A1A552E.3050806@intelliant.net>
Message-ID: <4A1A58D8.5090601@intelliant.net>



Shrenik Bhura wrote:
> Hello,
>
> Is it safe to use yast ldap-server once we have configured kolab?
>
> # yast ldap-server
>
> I am getting this warning :
>
> Your system is currently configured to use the configuration
> file /etc/openldap/slapd.conf. This YaST module only supports the dynamic
> configuration database of OpenLDAP (back-config). Do you want to migrate
> your
> existing configuration to the configuration database?
> (x) Migrate existing configuration
> ( ) Create a new configuration from scratch
>  
> Hoping that migrating existing config would not break things for kolab.
>
> Any suggestions?

Sorry forgot to mention that I would like to use the same LDAP for
system user auth as well. Does anyone see any issues with it?

The only earlier instance I have found w.r.t. kolab for such application
has been
http://www.nexedi.org/workspaces/project/dls/usage_of_ldap_in_nex . Any
suggestions on this as well?

Hoping to get some valuable insight before I burn my fingers ;)

SB



From shrenik.bhura at intelliant.net  Mon May 25 13:26:34 2009
From: shrenik.bhura at intelliant.net (Shrenik Bhura)
Date: Mon, 25 May 2009 16:56:34 +0530
Subject: openSUSE 11.1 LDAP dynamic config back-end + kolab
In-Reply-To: <4A1A58D8.5090601@intelliant.net>
References: <4A1A552E.3050806@intelliant.net> <4A1A58D8.5090601@intelliant.net>
Message-ID: <4A1A806A.8080400@intelliant.net>



Shrenik Bhura wrote:
> Shrenik Bhura wrote:
>   
>> Hello,
>>
>> Is it safe to use yast ldap-server once we have configured kolab?
>>
>> # yast ldap-server
>>
>> I am getting this warning :
>>
>> Your system is currently configured to use the configuration
>> file /etc/openldap/slapd.conf. This YaST module only supports the dynamic
>> configuration database of OpenLDAP (back-config). Do you want to migrate
>> your
>> existing configuration to the configuration database?
>> (x) Migrate existing configuration
>> ( ) Create a new configuration from scratch
>>  
>> Hoping that migrating existing config would not break things for kolab.
>>
>> Any suggestions?
>>     
>
> Sorry forgot to mention that I would like to use the same LDAP for
> system user auth as well. Does anyone see any issues with it?
>
> The only earlier instance I have found w.r.t. kolab for such application
> has been
> http://www.nexedi.org/workspaces/project/dls/usage_of_ldap_in_nex . Any
> suggestions on this as well?
>
> Hoping to get some valuable insight before I burn my fingers ;)
Fingers burnt :)

First few side effects noticed.

 # slapcat
str2entry: invalid value for attributeType objectClass #0 (syntax
1.3.6.1.4.1.1466.115.121.1.38)
root_dse_read_file: could not parse entry
(file="/etc/kolab/rootDSE.ldif" line=3)
olcRootDSE: value #0: <olcRootDSE> could not read file
/etc/kolab/rootDSE.ldif
config error processing cn=config: <olcRootDSE> could not read file
slapcat: bad configuration file!

Though all the normal functions(sending receiving mails / accessing
webadmin / modifying accounts) seem to be going smooth.
Could it be an ACL issue as #yast ldap-server ACL section for the Kolab
db seems to return this:
"The selected Database contains Access Control Rules that are currently
not supported by this YaST Module. The Access Control Dialog will be
disabled."

SB
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: messages
Url: http://kolab.org/pipermail/kolab-users/attachments/20090525/eeb3627c/messages.txt

From carsten at cburghardt.com  Mon May 25 15:47:00 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Mon, 25 May 2009 15:47:00 +0200
Subject: R: trouble logging into horde
In-Reply-To: <4A16EC60.3030703@intelliant.net>
References: <200904140027.40133.sunil@khiatani.ath.cx>
	<20090507215328.29131wci9adgib0g@webmail.pardus.de>
	<4A130A7D.30707@intelliant.net> <4A15B3C8.5020505@intelliant.net>
	<003901c9dacd$d5a37520$80ea5f60$@it> <4A16EC60.3030703@intelliant.net>
Message-ID: <20090525154700.12293cgrnq34rb6s@www.inovox.de>


Zitat von Shrenik Bhura <shrenik.bhura at intelliant.net>:

> Francesco,
>
> Haven't got a clue as yet. Will be working on this late next week.  
> Shall keep the list updated in case of any progress is made.
>
> SB
>
> PS: Please mail to the list and not to me individually. It shall be  
> helpful for all. :)

I had the same problem and the reason was that the domain for the  
cookie was not correct. Therefore Horde did not recognize the Cookie  
and did not let me in. It was obvious from the logfile that the login  
itself was successfull.

>
>
>
> francesco trimarchi wrote:
>> I have the same problem after upgrade from 2.2.0 to 2.2.2
>>
>> In this case I found something wrong in the /kolab/var/imapd/log/imad.log
>> file:
>>
>> May 22 13:04:33 groupware.domain.tld <debug> imap[5200]: SQUAT failed to
>> open index file
>> May 22 13:04:33 groupware.domain.tld <debug> imap[5200]: SQUAT failed
>>
>>
>> Can you help me?
>>
>> Francesco
>>
>>
>>
>>
>> -----Messaggio originale-----
>> Da: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org] Per
>> conto di Shrenik Bhura
>> Inviato: gioved? 21 maggio 2009 22.04
>> A: shrenik.bhura at intelliant.net
>> Cc: Gunnar Wrobel; Richard Bos; kolab-users at kolab.org
>> Oggetto: Re: trouble logging into horde
>>
>>
>>
>> Shrenik Bhura wrote:
>>
>>> Gunnar Wrobel wrote:
>>>
>>>
>>>> Quoting Sunil Khiatani <sunil at khiatani.ath.cx>:
>>>>
>>>>
>>>>
>>>>> Hi,
>>>>>
>>>>> I recently upgraded to horde 2.2.1, but i can no longer log
>>>>> into the horde webclient.  I'm not sure where to look for logs and
>>>>> what to do
>>>>> next.
>>>>>
>>>>> When I log in with the correct username and password, I get
>>>>> returned to the login page with no errors.
>>>>>
>>>>>
>>> I am now facing the same problem on opensuse 11.1 installation. The mail
>>> delivery part is working fine though. Just can't log in into the horde
>>> based web-client
>>>
>> Alar,
>>
>> Could you please share the permissions you have on /srv/www/htdocs/horde
>> ? It could possibly be that as I don't see any error/logs anywhere.
>>
>> Cheers,
>> SB
>>
>> _______________________________________________
>> 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
>




From carsten at cburghardt.com  Mon May 25 17:33:37 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Mon, 25 May 2009 17:33:37 +0200
Subject: Unable to Sync Calendar / PHP Fatal error compareDateTime()
In-Reply-To: <200905202019.16646.t.nintemann@medial-networks.de>
References: <200905201353.46188.Webmaster@computational-chemistry.org>
	<200905202019.16646.t.nintemann@medial-networks.de>
Message-ID: <20090525173337.10416yjgxczm4yo0@www.inovox.de>


Zitat von Thomas Nintemann <t.nintemann at medial-networks.de>:

>
>> Now I read on the mailing list that it should work. So I checked the logs
>> for errors that only happen when I sync stuff. And this is the one I found
>> in the /kolab/var/kolab/www/client/log/php-errors.log
>>
>> "PHP Fatal error :  Call to a member function compareDateTime() on a non-
>> object in /kolab/var/kolab/www/client/kronolith/lib/Driver/kolab.php on
>> line 1153"
>
> Same on my Side with Kolab 2.2.1 native on OpenSUSE-11.1.
> My Client is a Blackberry 8300 Curve with actual Funambol-Plugin.
>
> For stupid test  i comment out the Line 1153 and 1154 as here:
> /*if (!(($endDate->compareDateTime($event->start) < 0) ||
>                   ($startDate->compareDateTime($event->end) > 0)))*/
>
> and it sync's.
> But i now this a bad idea.
>
> Any better idea's?

Not a real solution but according to the error I'd say that either  
$endDate or $startDate is not defined and not recognized as a date  
object. Maybe a null check should be sufficient?


Carsten



From t.nintemann at medial-networks.de  Mon May 25 19:31:04 2009
From: t.nintemann at medial-networks.de (Thomas Nintemann)
Date: Mon, 25 May 2009 19:31:04 +0200
Subject: Unable to Sync Calendar / PHP Fatal error compareDateTime()
In-Reply-To: <20090525173337.10416yjgxczm4yo0@www.inovox.de>
References: <200905201353.46188.Webmaster@computational-chemistry.org>
	<200905202019.16646.t.nintemann@medial-networks.de>
	<20090525173337.10416yjgxczm4yo0@www.inovox.de>
Message-ID: <200905251931.05020.t.nintemann@medial-networks.de>

Am Monday 25 May 2009 17:33:37 schrieb Carsten Burghardt:
> Zitat von Thomas Nintemann <t.nintemann at medial-networks.de>:
> >> Now I read on the mailing list that it should work. So I checked the
> >> logs for errors that only happen when I sync stuff. And this is the one
> >> I found in the /kolab/var/kolab/www/client/log/php-errors.log
> >>
> >> "PHP Fatal error :  Call to a member function compareDateTime() on a
> >> non- object in
> >> /kolab/var/kolab/www/client/kronolith/lib/Driver/kolab.php on line 1153"
> >
> > Same on my Side with Kolab 2.2.1 native on OpenSUSE-11.1.
> > My Client is a Blackberry 8300 Curve with actual Funambol-Plugin.
> >
> > For stupid test  i comment out the Line 1153 and 1154 as here:
> > /*if (!(($endDate->compareDateTime($event->start) < 0) ||
> >                   ($startDate->compareDateTime($event->end) > 0)))*/
> >
> > and it sync's.
> > But i now this a bad idea.
> >
> > Any better idea's?
>
> Not a real solution but according to the error I'd say that either
> $endDate or $startDate is not defined and not recognized as a date
> object. Maybe a null check should be sufficient?
>
>
> Carsten

OK, thanks for the Tip.

I have now made changes as follow on those lines:

Line 1137 
---------------------------
if (is_null($startDate)) {
----------------------------
to 
----------------------------
if (empty($startDate)) {
-----------------------------

and Line 1140
-----------------------------
if (is_null($endDate)) {
----------------------------
to
-----------------------------
if (empty($endDate)) {
-----------------------------

and now it syncs without my stupid comment out of lines 1153 and 1154.

But i do not now this is the right way to solve that problem.

Thomas

--------------------
Medial-Networks
Thomas Nintemann
Landsbergstra?e 45
26871 Papenburg
Phone:+494961916744
Fax: +494961669546
---------------------



From johnm at advocap.org  Mon May 25 21:07:18 2009
From: johnm at advocap.org (John McMonagle)
Date: Mon, 25 May 2009 14:07:18 -0500
Subject: Error upgrading  kolab  from 2.2.1 to 2.2.2
Message-ID: <200905251407.19546.johnm@advocap.org>

It's my first try at an upgrade.

Downloaded the debian 5 binary packages.

Verified the packages  and ran from the download directory.


 sh install-kolab.sh 2>&1 | tee /root/kolab-update.log
Changing to temporary working 
directory /tmp/install-kolab.17450.31912.7999.7035 ...

Kolab installation tag (TAG):       kolab
Kolab installation prefix (PREFIX): /kolab
Kolab version (KOLAB_VERSION):      2.2.2
Kolab user name (USER):             kolab
Kolab user base UID (KID):          19414
Kolab restricted UID (KID):         19415
Kolab non-priviledged UID (KID):    19416
Exclude following Kolab packages:

Received no instructions. Trying to determine required action...
Found an OpenPKG environment. Assuming upgrade...
----------- SETUP COMPLETED -----------

 Now running:

   /kolab/bin/openpkg 
build -kKBuZ -r "/tmp/install-kolab.17450.31912.7999.7035" -p "ix86-debian4.0-         
kolab" -D openldap::with_pth=no -D sasl::with_ldap -D sasl::with_login -D 
sasl::with_ntlm -D postfix         ::with_sasl -D postfix::with_ssl -D 
postfix::with_ldap -D imapd::with_kolab_nocaps
            -Dkolabd::kolab_version=2.2.2
            -Dkolab-webadmin::kolab_version=2.2.2
          openpkg-tools openldap postfix kolabd kolab-webadmin kolab-fbview 
kolab-webclient | sh

---------------------------------------
:::: /tmp/install-kolab.17450.31912.7999.7035/openpkg-20071227-20071227_kolab1.src.rpm ::::
error: cannot 
open /tmp/install-kolab.17450.31912.7999.7035/openpkg-20071227-20071227_kolab1.src.rpm         : 
No such file or directory
............................................
it ends there.

I was using the etch packages. Installed on lenny host.

John



From ml at radoeka.nl  Mon May 25 22:56:16 2009
From: ml at radoeka.nl (Richard Bos)
Date: Mon, 25 May 2009 22:56:16 +0200
Subject: openSUSE 11.1 LDAP dynamic config back-end + kolab
In-Reply-To: <4A1A552E.3050806@intelliant.net>
References: <4A1A552E.3050806@intelliant.net>
Message-ID: <200905252256.17749.ml@radoeka.nl>

Op maandag 25 mei 2009 10:22:06 schreef Shrenik Bhura:
> Hello,
>
> Is it safe to use yast ldap-server once we have configured kolab?
>
> # yast ldap-server

This is probably asking for trouble.  Yast and kolab are not aware of each 
other, so both think that they control the configuration file.  This does not 
look good....

> I am getting this warning :
>
> Your system is currently configured to use the configuration
> file /etc/openldap/slapd.conf. This YaST module only supports the dynamic
> configuration database of OpenLDAP (back-config). Do you want to migrate
> your existing configuration to the configuration database?
> (x) Migrate existing configuration
> ( ) Create a new configuration from scratch
>
> Hoping that migrating existing config would not break things for kolab.

Don't use yast :)

What is a dynamic configuration database....?  If it is the new openldap-2.4 
of storing the configuration, it is not supported by kolab....  As such you 
better not migrate.

> Sorry forgot to mention that I would like to use the same LDAP for
> system user auth as well. Does anyone see any issues with it?

What about this:
http://wiki.kolab.org/index.php/Samba_PDC_and_Kolab_Server
http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy
http://wiki.kolab.org/index.php/Special:Search?search=samba&go=Go
Is that perhaps what you're looking for?

http://wpkg.org/kolab/
http://wiki.kolab.org/index.php/Administrators_Overview#Extensions

Well that's about it :)

-- 
Richard



From aspineux at gmail.com  Tue May 26 08:42:15 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Tue, 26 May 2009 08:42:15 +0200
Subject: Problem with acls migrating from cyrus imap.
In-Reply-To: <200905201100.16743.benoit.mortier@opensides.be>
References: <200905130907.33120.johnm@advocap.org>
	<200905191006.19201.johnm@advocap.org>
	<200905201002.06905.bernhard@intevation.de>
	<200905201100.16743.benoit.mortier@opensides.be>
Message-ID: <71fe4e760905252342p468826c5l4ec13161479c5168@mail.gmail.com>

On Wed, May 20, 2009 at 11:00 AM, Benoit Mortier
<benoit.mortier at opensides.be> wrote:
> Le Wednesday 20 May 2009 10:02:02 Bernhard Reiter, vous avez ?crit?:
>> Am Dienstag, 19. Mai 2009 17:06:18 schrieb John McMonagle:
>
> Hello,
>
>> > The problem with imapsync is that I still would have to manually fix
>> > all the acls for shared mailboxes.
>>
>> Hmm if imapsync doesn not transfer the ACL settings, maybe we should
>> come up with a script that does or enhance imapsync. From the
>
> Enhancing imapsync is the way to go. it so usefull for imap migrations

I agree, but this is Perl and I don't speech this language.

>
> Cheers
> --
> Benoit Mortier
> CEO
> OpenSides "logiciels libres pour entreprises" : http://www.opensides.be/
> Contributor to Gosa Project : http://gosa-project.org/
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



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



From shrenik.bhura at intelliant.net  Tue May 26 10:08:56 2009
From: shrenik.bhura at intelliant.net (Shrenik Bhura)
Date: Tue, 26 May 2009 13:38:56 +0530
Subject: openSUSE 11.1 LDAP dynamic config back-end + kolab
In-Reply-To: <200905252256.17749.ml@radoeka.nl>
References: <4A1A552E.3050806@intelliant.net>
	<200905252256.17749.ml@radoeka.nl>
Message-ID: <4A1BA398.8000201@intelliant.net>

Hi Richard,

Richard Bos wrote:
> Op maandag 25 mei 2009 10:22:06 schreef Shrenik Bhura:
>   
>> Hello,
>>
>> Is it safe to use yast ldap-server once we have configured kolab?
>>
>> # yast ldap-server
>>     
>
> This is probably asking for trouble.  Yast and kolab are not aware of each 
> other, so both think that they control the configuration file.  This does not 
> look good....
>   
Yeah I asked for it and have got it.:) But now I observe something very
interesting. All seems to be working fine except slapcat.
>> I am getting this warning :
>>
>> Your system is currently configured to use the configuration
>> file /etc/openldap/slapd.conf. This YaST module only supports the dynamic
>> configuration database of OpenLDAP (back-config). Do you want to migrate
>> your existing configuration to the configuration database?
>> (x) Migrate existing configuration
>> ( ) Create a new configuration from scratch
>>
>> Hoping that migrating existing config would not break things for kolab.
>>     
>
> Don't use yast :)
>   
Any idea how I may revert to the old setup.
Tried kolab_bootstrap -b but the root DSE error remains as is.
I removed kolab, kolab-webclient and openldap2 and reinstalled the same
but yet no luck. The error remains.
I was under the impression that kolab on os 11.1 had been ported to
support the openldap 2.4

Any advice?
> What is a dynamic configuration database....?  If it is the new openldap-2.4 
> of storing the configuration, it is not supported by kolab....  As such you 
> better not migrate
Yeah it is openldap-2.4 that i am referring to.
openldap2-client-2.4.12-5.3
openldap2-2.4.12-5.4

SB



From Roessler at FuH-E.de  Tue May 26 11:17:05 2009
From: Roessler at FuH-E.de (=?ISO-8859-15?Q?Christian_R=F6=DFler?=)
Date: Tue, 26 May 2009 11:17:05 +0200
Subject: Mail archiving: Has anyone gotten OMA (open mail archive) to work
	with kolab?
Message-ID: <4A1BB391.3040607@FuH-E.de>

Hallo,

I have, some time ago, decided to give the per specification and
relative light-weight good-looking OMA (open mail archive,
<http://www.octant.org/en/content/open-mail-archiver-oma>) a try.

But I ran in one last difficulty I seemingly cannot overcome: After
successful MySQL-Integration in kolab-php (and apache-php) and
installing OMA I cannot get the OMA daemon omad.php to start.

If I start it it will log:
| PHP Notice:  Use of undefined constant AF_UNIX - assumed 'AF_UNIX' in
| /kolab/local/oma/lib/Socket.class.php on line 51

So I assumed AF_UNIX would be a file socket, which perhaps is not
compiled into the kolab-php. But phpinfo says:

| Registered PHP Streams => php, file, data, http, ftp, compress.zlib,
| https, ftps
| Registered Stream Socket Transports => tcp, udp, unix, udg, ssl,
| sslv3, sslv2, tls
Does that not say file sockets are implemented?

I have made many tries to 'rpm --rebuild ...' php with options like
"--define with_sockets' etc. pp. These brought me to nowhere; there is
also nothing about socket(s) in the rpm.spec. Does php5 this by default?

So: Has anyone here implemented OMA together with kolab? If so, how?

I would also appreciate, generally speaking, tips about these AF_UNIX
file sockets in general under a kolab system.

Best regards,
Christian



From ml at radoeka.nl  Tue May 26 12:07:45 2009
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 26 May 2009 12:07:45 +0200
Subject: openSUSE 11.1 LDAP dynamic config back-end + kolab
In-Reply-To: <4A1BA398.8000201@intelliant.net>
References: <4A1A552E.3050806@intelliant.net>
	<200905252256.17749.ml@radoeka.nl>
	<4A1BA398.8000201@intelliant.net>
Message-ID: <20090526100745.GA1149@xs4all.nl>

On Tue, May 26, 2009 at 01:38:56PM +0530, Shrenik Bhura wrote:
> >> configuration database of OpenLDAP (back-config). Do you want to migrate
> >> your existing configuration to the configuration database?
> >> (x) Migrate existing configuration
> >> ( ) Create a new configuration from scratch
> >>
> >> Hoping that migrating existing config would not break things for kolab.
> >>     
> >
> > Don't use yast :)
> >   
> Any idea how I may revert to the old setup.
> Tried kolab_bootstrap -b but the root DSE error remains as is.
> I removed kolab, kolab-webclient and openldap2 and reinstalled the same
> but yet no luck. The error remains.
> I was under the impression that kolab on os 11.1 had been ported to
> support the openldap 2.4
> 
> Any advice?
> > What is a dynamic configuration database....?  If it is the new openldap-2.4 
> > of storing the configuration, it is not supported by kolab....  As such you 
> > better not migrate
> Yeah it is openldap-2.4 that i am referring to.
> openldap2-client-2.4.12-5.3
> openldap2-2.4.12-5.4

Have a look at this issue:
https://www.intevation.de/roundup/kolab/issue3000
Hopefully it has enough pointers for you to get going.
I think that you should remove the openldap pkg annd
also remove the directories:
/etc/openldap and /var/lib/ldap.
Now re-install the openldap package and run kolab_bootstrap.
Of course this results in loss of data.....

-- 
Richard



From ronald at kovoks.nl  Tue May 26 12:19:59 2009
From: ronald at kovoks.nl (RonaldvE)
Date: Tue, 26 May 2009 10:19:59 +0000 (UTC)
Subject: Sync Kolab with Thunderbird
References: <0268B6D5-435C-4DA0-B3BC-E920667FADA2@izsr.de>
Message-ID: <loom.20090526T101518-147@post.gmane.org>

Tim Golz <kolab <at> izsr.de> writes:

> 
> Hi, folx,
> 
> been an administrator now for nearly 10 years with some experience in  
> Linux, Mac and Windows, I must admit that I dunno understand nothing  
> when I try to sync thunderbirdclients to Kolab.
> 
> I have just installed Kolab 2.2.0 from Sources on a Debian Etch-box,  
> works fine as far as i can see: i can administer the Kolab  
> webinterface, create users, external adresses, I can connect from  
> varios mailclients to the Kolabimapserver, sending and receiving  
> mails, adresses get completed from the kolab-lda-adressbook, I can do  
> an ldapsearch from a client to kolab - no probs.
> 
> but i am to stupid to get Thunderbird Adressbook, Calendar and Tasks  
> working with Kolab. I tried different setups now with the SyncKolab- 
> Plugin and Lightning, I created Folders in Kolab and on the  
> Thunderbird-client, I googled for hours - no chance. the HowTos on the  
> Kolabsite (i.e. the Kolabwiki) explains nothing (to me), nor does the  
> Synckolab-site.
> 
> Is there a Step-by-Step-HowTo for Fools like me (who are able to  
> administer two dozens of mal-, samba- and ldapservers and writing  
> bashscripts and so on, but to stupid to understand the teamwork of  
> Kolab and Thunderbird/SyncKolab)?
> 
> Thanx a lot in advance ...
> 

Per user, make extra imap or mailbox directories where contacts, tasks, and
agenda can reside.
now in the connector settings, choose these directories for corresponding names,
so agenda in agenda etc, now after you sync the contacts must also stay in these
earlier made directories. If you use the webmail, now these contacts, agenda etc
are there too. 

it's not hard, if you know ;)

good luck Tim.

> greetnings
> 
> Tim Golz
> 






From johnm at advocap.org  Tue May 26 17:52:32 2009
From: johnm at advocap.org (John McMonagle)
Date: Tue, 26 May 2009 10:52:32 -0500
Subject: Error upgrading  kolab  from 2.2.1 to 2.2.2
In-Reply-To: <200905251407.19546.johnm@advocap.org>
References: <200905251407.19546.johnm@advocap.org>
Message-ID: <4A1C1040.1020504@advocap.org>

John McMonagle wrote:
> It's my first try at an upgrade.
>
> Downloaded the debian 5 binary packages.
>
> Verified the packages  and ran from the download directory.
>
>
>  sh install-kolab.sh 2>&1 | tee /root/kolab-update.log
> Changing to temporary working 
> directory /tmp/install-kolab.17450.31912.7999.7035 ...
>
> Kolab installation tag (TAG):       kolab
> Kolab installation prefix (PREFIX): /kolab
> Kolab version (KOLAB_VERSION):      2.2.2
> Kolab user name (USER):             kolab
> Kolab user base UID (KID):          19414
> Kolab restricted UID (KID):         19415
> Kolab non-priviledged UID (KID):    19416
> Exclude following Kolab packages:
>
> Received no instructions. Trying to determine required action...
> Found an OpenPKG environment. Assuming upgrade...
> ----------- SETUP COMPLETED -----------
>
>  Now running:
>
>    /kolab/bin/openpkg 
> build -kKBuZ -r "/tmp/install-kolab.17450.31912.7999.7035" -p "ix86-debian4.0-         
> kolab" -D openldap::with_pth=no -D sasl::with_ldap -D sasl::with_login -D 
> sasl::with_ntlm -D postfix         ::with_sasl -D postfix::with_ssl -D 
> postfix::with_ldap -D imapd::with_kolab_nocaps
>             -Dkolabd::kolab_version=2.2.2
>             -Dkolab-webadmin::kolab_version=2.2.2
>           openpkg-tools openldap postfix kolabd kolab-webadmin kolab-fbview 
> kolab-webclient | sh
>
> ---------------------------------------
> :::: /tmp/install-kolab.17450.31912.7999.7035/openpkg-20071227-20071227_kolab1.src.rpm ::::
> error: cannot 
> open /tmp/install-kolab.17450.31912.7999.7035/openpkg-20071227-20071227_kolab1.src.rpm         : 
> No such file or directory
> ............................................
> it ends there.
>
> I was using the etch packages. Installed on lenny host.
>
> John
>
>   
As it's not in production yet  took some chances :-)

I saw the parameter -p "ix86-debian4.0-kolab".
Figure that did not look correct added -p "ix86-debian5.0-kolab" to  
install-kolab.sh.
it then at least did more but did error out.
Sorry did not save message.
Then ran without  -p "ix86-debian5.0-kolab" and it worked.
As a simple check all of /kolab/bin and sbin are new.

Any chance the the .rpmorig files that mess up startup could be removed 
by the startup script?
Not much point in preserving them as they are all created by templates.


John
-------------- next part --------------
A non-text attachment was scrubbed...
Name: johnm.vcf
Type: text/x-vcard
Size: 250 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20090526/dc3ea456/johnm.bin

From shrenik.bhura at intelliant.net  Wed May 27 05:29:58 2009
From: shrenik.bhura at intelliant.net (Shrenik Bhura)
Date: Wed, 27 May 2009 08:59:58 +0530
Subject: openSUSE 11.1 LDAP dynamic config back-end + kolab
In-Reply-To: <20090526100745.GA1149@xs4all.nl>
References: <4A1A552E.3050806@intelliant.net>
	<200905252256.17749.ml@radoeka.nl>
	<4A1BA398.8000201@intelliant.net> <20090526100745.GA1149@xs4all.nl>
Message-ID: <4A1CB3B6.1020203@intelliant.net>



Richard Bos wrote:
> On Tue, May 26, 2009 at 01:38:56PM +0530, Shrenik Bhura wrote:
>   
>>>> configuration database of OpenLDAP (back-config). Do you want to migrate
>>>> your existing configuration to the configuration database?
>>>> (x) Migrate existing configuration
>>>> ( ) Create a new configuration from scratch
>>>>
>>>> Hoping that migrating existing config would not break things for kolab.
>>>>     
>>>>         
>>> Don't use yast :)
>>>   
>>>       
>> Any idea how I may revert to the old setup.
>> Tried kolab_bootstrap -b but the root DSE error remains as is.
>> I removed kolab, kolab-webclient and openldap2 and reinstalled the same
>> but yet no luck. The error remains.
>> I was under the impression that kolab on os 11.1 had been ported to
>> support the openldap 2.4
>>
>> Any advice?
>>     
>>> What is a dynamic configuration database....?  If it is the new openldap-2.4 
>>> of storing the configuration, it is not supported by kolab....  As such you 
>>> better not migrate
>>>       
>> Yeah it is openldap-2.4 that i am referring to.
>> openldap2-client-2.4.12-5.3
>> openldap2-2.4.12-5.4
>>     
>
> Have a look at this issue:
> https://www.intevation.de/roundup/kolab/issue3000
> Hopefully it has enough pointers for you to get going.
> I think that you should remove the openldap pkg annd
> also remove the directories:
> /etc/openldap and /var/lib/ldap.
> Now re-install the openldap package and run kolab_bootstrap.
> Of course this results in loss of data.....
Woah! That was really interesting stuff but where do we go from there?
Can't we move ahead from there to ensure the migration happens smoothly
and maintain the same?
The issue seems to have been open for quite sometime now.

SB



From cristian at livadaru.net  Wed May 27 16:46:24 2009
From: cristian at livadaru.net (Cristian Livadaru)
Date: Wed, 27 May 2009 16:46:24 +0200
Subject: Amavis quarantine cleanup
Message-ID: <C8EF7E28-563A-4947-A872-B402E7F7F629@livadaru.net>

Hi everyone.

just noticed I have quite a lot of mails in the amavis quarantine  
directory.
Is there any Kolab way of doing a cleanup? Or should I just write my  
own script to delete old mails.

Or has anybody done thtat already? Couldn't really find anything.

Regards, Cristian



From andre.mathibe at mortgage-services.de  Wed May 27 16:58:39 2009
From: andre.mathibe at mortgage-services.de (Andre Mathibe)
Date: Wed, 27 May 2009 16:58:39 +0200
Subject: Amavis quarantine cleanup
In-Reply-To: <C8EF7E28-563A-4947-A872-B402E7F7F629@livadaru.net>
References: <C8EF7E28-563A-4947-A872-B402E7F7F629@livadaru.net>
Message-ID: <200905271658.44172.andre.mathibe@mortgage-services.de>

Am Mittwoch, 27. Mai 2009 schrieb Cristian Livadaru:
> Hi everyone.
>
> just noticed I have quite a lot of mails in the amavis quarantine
> directory.
> Is there any Kolab way of doing a cleanup? Or should I just write my
> own script to delete old mails.
>
> Or has anybody done thtat already? Couldn't really find anything.
>
> Regards, Cristian
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users


i used this in my crontab ....  quick and not soooooooo dirty,...

#### delete qurantained Virus-eMails older than 30 days ####
10 2 * * * find /var/spool/amavis/tmp/ -mtime +31 -exec rm -r {} \;
15 2 * * * find /var/spool/amavis/virusmails/ -mtime +31 -exec rm {} \;


-- 
Andre Mathibe
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090527/a92ee9af/attachment.bin

From akopciuch at bddf.ca  Wed May 27 17:35:50 2009
From: akopciuch at bddf.ca (Andrew J. Kopciuch)
Date: Wed, 27 May 2009 09:35:50 -0600
Subject: Amavis quarantine cleanup
In-Reply-To: <200905271658.44172.andre.mathibe@mortgage-services.de>
References: <C8EF7E28-563A-4947-A872-B402E7F7F629@livadaru.net>
	<200905271658.44172.andre.mathibe@mortgage-services.de>
Message-ID: <200905270935.51193.akopciuch@bddf.ca>

On May 27, 2009, Andre Mathibe wrote:
> 10 2 * * * find /var/spool/amavis/tmp/ -mtime +31 -exec rm -r {} \;
> 15 2 * * * find /var/spool/amavis/virusmails/ -mtime +31 -exec rm {} \;


+1




Andy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090527/f2aec787/attachment.bin

From dvadell at linuxclusters.com.ar  Thu May 28 03:44:01 2009
From: dvadell at linuxclusters.com.ar (Diego M. Vadell)
Date: Wed, 27 May 2009 22:44:01 -0300
Subject: Problem with calendar via HTTP.
Message-ID: <200905272244.02063.dvadell@linuxclusters.com.ar>

Hi,

   I'm having a problem with making calendar and using them via HTTP. 

* I can suscribe myself to my personal calendar in 
https://gluster1.pampa.linuxclusters.com.ar/client/rpc.php/kronolith/dvadell at pampa.linuxclusters.com.ar/dvadell at pampa.linuxclusters.com.ar.ics . 
I can use it in thunderbird, kontact and if I browse to that URL I get a ics 
file.

* I then created a new calendar, called "Compartido", via Horde. The URL that 
Horde gave me is
https://gluster1.pampa.linuxclusters.com.ar/client/rpc.php/kronolith/dvadell at pampa.linuxclusters.com.ar/INBOX/Compartido.ics

* I created one event.

* The IMAP folder is there. It has a mail with an attachment. It looks like 
the event I just created.

* I configure Kontact to use the calendar and get: The file or folder 
https://gluster1.pampa.linuxclusters.com.ar/client/rpc.php/kronolith/dvadell at pampa.linuxclusters.com.ar/INBOX/Compartido.ics 
does not exist.

* I configure thunderbird to use the calendar. The calendar gets added but the 
event does not appear. When I try to add an event, I get an error:

An error occurred when writing to the calendar Compartido! Error number: 
Modification_failed .

* If I try to GET the calendar's URL with wget, I get: HTTP request sent, 
awaiting response... 404 File Not Found

* If I try to GET the calendar's URL with firefox I get a blank page. 
Completely blank. In horde.log (inside client/log) I get all this.

May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders 
in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders 
in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders 
in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders 
in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders 
in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders 
in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders 
in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders 
in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders 
in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders 
in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders 
in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [notice] [imp] Login success for dvadell [10.200.200.7] 
to {gluster1.pampa.linuxclusters.com.ar:143 [imap/notls/novalidate-cert]} 
[pid 17092 on line 304 of "/kolab/var/kolab/www/client/imp/lib/Session.php"]
May 28 21:49:36 HORDE [debug] [kronolith] Hook _horde_hook_share_init in 
application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [kronolith] Hook 
_prefs_change_hook_display_remote_cals in application horde not called. [pid 
17092 on line 1683 of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [kronolith] Hook 
_prefs_change_hook_display_external_cals in application horde not called. 
[pid 17092 on line 1683 of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [kronolith] Hook _prefs_change_hook_display_cals 
in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [horde] Max memory usage: 11534336 bytes [pid 
17092 on line 339 of "/kolab/var/kolab/www/client/lib/Horde/Registry.php"]
May 28 21:49:36 HORDE [debug] [horde] IMAP errors: SECURITY PROBLEM: insecure 
server advertised AUTH=PLAIN [pid 17092 on line 175 
of "/kolab/var/kolab/www/client/imp/lib/IMAP.php"]

The last line looks like a warning only. Then "[notice]" line says that it 
could login as my user (dvadell) into this test server. 

I looked for something similar in the bug tracker, but nothing ringed any 
bell. Does anyone knows how I can futher debug this?

TIA
 -- Diego



From webmaster at computational-chemistry.org  Thu May 28 11:50:07 2009
From: webmaster at computational-chemistry.org (Alexander =?iso-8859-1?q?Schr=F6ter?=)
Date: Thu, 28 May 2009 11:50:07 +0200
Subject: [Solved] Re: Unable to Sync Calendar / PHP Fatal error
	compareDateTime()
In-Reply-To: <200905251931.05020.t.nintemann@medial-networks.de>
References: <200905201353.46188.Webmaster@computational-chemistry.org>
	<20090525173337.10416yjgxczm4yo0@www.inovox.de>
	<200905251931.05020.t.nintemann@medial-networks.de>
Message-ID: <200905281150.07404.webmaster@computational-chemistry.org>

On Monday 25 May 2009 07:31:04 pm Thomas Nintemann wrote:
> Am Monday 25 May 2009 17:33:37 schrieb Carsten Burghardt:
> > Zitat von Thomas Nintemann <t.nintemann at medial-networks.de>:
> > >> Now I read on the mailing list that it should work. So I checked the
> > >> logs for errors that only happen when I sync stuff. And this is the
> > >> one I found in the /kolab/var/kolab/www/client/log/php-errors.log
> > >>
> > >> "PHP Fatal error :  Call to a member function compareDateTime() on a
> > >> non- object in
> > >> /kolab/var/kolab/www/client/kronolith/lib/Driver/kolab.php on line
> > >> 1153"
> > >
> > > Same on my Side with Kolab 2.2.1 native on OpenSUSE-11.1.
> > > My Client is a Blackberry 8300 Curve with actual Funambol-Plugin.
> > >
> > > For stupid test  i comment out the Line 1153 and 1154 as here:
> > > /*if (!(($endDate->compareDateTime($event->start) < 0) ||
> > >                   ($startDate->compareDateTime($event->end) > 0)))*/
> > >
> > > and it sync's.
> > > But i now this a bad idea.
> > >
> > > Any better idea's?
> >
> > Not a real solution but according to the error I'd say that either
> > $endDate or $startDate is not defined and not recognized as a date
> > object. Maybe a null check should be sufficient?
> >
> >
> > Carsten
>
> OK, thanks for the Tip.
>
> I have now made changes as follow on those lines:
>
> Line 1137
> ---------------------------
> if (is_null($startDate)) {
> ----------------------------
> to
> ----------------------------
> if (empty($startDate)) {
> -----------------------------
>
> and Line 1140
> -----------------------------
> if (is_null($endDate)) {
> ----------------------------
> to
> -----------------------------
> if (empty($endDate)) {
> -----------------------------
>
> and now it syncs without my stupid comment out of lines 1153 and 1154.
>
> But i do not now this is the right way to solve that problem.
>
> Thomas

I have been testing this for the last couple of days and I didn't get an 
error. For me the issue is fixed, but of course it would be nice to have a 
developer or somebody who knows the code doublecheck everything and give some 
feedback.

Is there a way to let the guys from Horde know about this issue? So they can 
fix it too.

Regards Alexander



From Nicholas.Moore at tsr-i.com  Thu May 28 12:23:43 2009
From: Nicholas.Moore at tsr-i.com (Nicholas Moore)
Date: Thu, 28 May 2009 12:23:43 +0200
Subject: to-dos and journal entries
Message-ID: <200905281223.43959.Nicholas.Moore@tsr-i.com>

I have Kolab Kolab (2.2.0-2.3-i586) running happily on OpenSuse 11.1.

The only snag is that (in Kontact) completed to-do items do not get added to the journal. Explicitly created journal entries are fine. Is this the right forum to get help on that, or might it be a KDE issue?
-- 

Nicholas Moore
Limoges
France
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20090528/8fbc681b/attachment.html

From cristian at livadaru.net  Thu May 28 13:45:52 2009
From: cristian at livadaru.net (Cristian Livadaru)
Date: Thu, 28 May 2009 13:45:52 +0200
Subject: Amavis quarantine cleanup
In-Reply-To: <200905271658.44172.andre.mathibe@mortgage-services.de>
References: <C8EF7E28-563A-4947-A872-B402E7F7F629@livadaru.net>
	<200905271658.44172.andre.mathibe@mortgage-services.de>
Message-ID: <1F73A86D-EA4C-4E18-A477-2E9E42D20E8F@livadaru.net>


On 27. May 2009, at 16:58 , Andre Mathibe wrote:

> Am Mittwoch, 27. Mai 2009 schrieb Cristian Livadaru:
>> Hi everyone.
>>
>> just noticed I have quite a lot of mails in the amavis quarantine
>> directory.
>> Is there any Kolab way of doing a cleanup? Or should I just write my
>> own script to delete old mails.
>>
>> Or has anybody done thtat already? Couldn't really find anything.
>>
>> Regards, Cristian
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>
>
> i used this in my crontab ....  quick and not soooooooo dirty,...
>
> #### delete qurantained Virus-eMails older than 30 days ####
> 10 2 * * * find /var/spool/amavis/tmp/ -mtime +31 -exec rm -r {} \;
> 15 2 * * * find /var/spool/amavis/virusmails/ -mtime +31 -exec rm {}  
> \;
>
>

thanks, just added this to my crontab

Cris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
Url : http://kolab.org/pipermail/kolab-users/attachments/20090528/9058f569/PGP.bin

From LHendricks at austinent.com  Thu May 28 18:00:49 2009
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Thu, 28 May 2009 11:00:49 -0500
Subject: Problem with calendar via HTTP.
Message-ID: <7907AE10BB50DD4F840E76527D27EF19029F6AF7@entmail.domain.austinent.com>

I have this same issue on Horde with Kolab 2.2.2.  Calendars made by kolab
admin interface (default calendar and public event folders) work fine with
the icalendar subscription, but any calendars made with client
programs(horde and kontact/win) end up with the below issue. 

On internet explorer the URL doesn't even correctly parse and gives this at
the end: /INBOX%2FTestKontactCalendar.ics
Instead of /INBOX/TestKontactCalendar.ics

Lucas

-----Original Message-----
From: Diego M. Vadell [mailto:dvadell at linuxclusters.com.ar] 
Sent: Wednesday, May 27, 2009 8:44 PM
To: kolab-users at kolab.org
Subject: Problem with calendar via HTTP.

Hi,

   I'm having a problem with making calendar and using them via HTTP. 

* I can suscribe myself to my personal calendar in 
https://gluster1.pampa.linuxclusters.com.ar/client/rpc.php/kronolith/dvadell
@pampa.linuxclusters.com.ar/dvadell at pampa.linuxclusters.com.ar.ics . 
I can use it in thunderbird, kontact and if I browse to that URL I get a ics

file.

* I then created a new calendar, called "Compartido", via Horde. The URL
that 
Horde gave me is
https://gluster1.pampa.linuxclusters.com.ar/client/rpc.php/kronolith/dvadell
@pampa.linuxclusters.com.ar/INBOX/Compartido.ics

* I created one event.

* The IMAP folder is there. It has a mail with an attachment. It looks like 
the event I just created.

* I configure Kontact to use the calendar and get: The file or folder 
https://gluster1.pampa.linuxclusters.com.ar/client/rpc.php/kronolith/dvadell
@pampa.linuxclusters.com.ar/INBOX/Compartido.ics 
does not exist.

* I configure thunderbird to use the calendar. The calendar gets added but
the 
event does not appear. When I try to add an event, I get an error:

An error occurred when writing to the calendar Compartido! Error number: 
Modification_failed .

* If I try to GET the calendar's URL with wget, I get: HTTP request sent, 
awaiting response... 404 File Not Found

* If I try to GET the calendar's URL with firefox I get a blank page. 
Completely blank. In horde.log (inside client/log) I get all this.

May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders

in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders

in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders

in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders

in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders

in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders

in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders

in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders

in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders

in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders

in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [imp] Hook _prefs_change_hook_expanded_folders

in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [notice] [imp] Login success for dvadell
[10.200.200.7] 
to {gluster1.pampa.linuxclusters.com.ar:143 [imap/notls/novalidate-cert]} 
[pid 17092 on line 304 of "/kolab/var/kolab/www/client/imp/lib/Session.php"]
May 28 21:49:36 HORDE [debug] [kronolith] Hook _horde_hook_share_init in 
application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [kronolith] Hook 
_prefs_change_hook_display_remote_cals in application horde not called. [pid

17092 on line 1683 of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [kronolith] Hook 
_prefs_change_hook_display_external_cals in application horde not called. 
[pid 17092 on line 1683 of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [kronolith] Hook
_prefs_change_hook_display_cals 
in application horde not called. [pid 17092 on line 1683 
of "/kolab/var/kolab/www/client/lib/Horde.php"]
May 28 21:49:36 HORDE [debug] [horde] Max memory usage: 11534336 bytes [pid 
17092 on line 339 of "/kolab/var/kolab/www/client/lib/Horde/Registry.php"]
May 28 21:49:36 HORDE [debug] [horde] IMAP errors: SECURITY PROBLEM:
insecure 
server advertised AUTH=PLAIN [pid 17092 on line 175 
of "/kolab/var/kolab/www/client/imp/lib/IMAP.php"]

The last line looks like a warning only. Then "[notice]" line says that it 
could login as my user (dvadell) into this test server. 

I looked for something similar in the bug tracker, but nothing ringed any 
bell. Does anyone knows how I can futher debug this?

TIA
 -- Diego

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



From bernhard at intevation.de  Thu May 28 21:25:48 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 28 May 2009 21:25:48 +0200
Subject: ldap questions.
In-Reply-To: <200905200824.13700.johnm@advocap.org>
References: <200905191555.59009.johnm@advocap.org>
	<200905200650.25421.johnm@advocap.org>
	<200905200824.13700.johnm@advocap.org>
Message-ID: <200905282125.49489.bernhard@intevation.de>

Am Mittwoch, 20. Mai 2009 15:24:13 schrieb John McMonagle:
> I did a second try
> in kolab.conf
> ldap_uri : ldap://127.0.0.1:389 ldaps://mstldap.advocap.org:636
>
> gives in apache.conf
> AuthLDAPURL ldap://127.0.0.1 ldaps::389/dc=advocap,dc=org?mail
>
> Should I do a bug report?

Yes, please report the defect.


-- 
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-users/attachments/20090528/fe68fd27/attachment.bin

From bernhard at intevation.de  Thu May 28 21:29:08 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 28 May 2009 21:29:08 +0200
Subject: to-dos and journal entries
In-Reply-To: <200905281223.43959.Nicholas.Moore@tsr-i.com>
References: <200905281223.43959.Nicholas.Moore@tsr-i.com>
Message-ID: <200905282129.09075.bernhard@intevation.de>

Am Donnerstag, 28. Mai 2009 12:23:43 schrieb Nicholas Moore:
> I have Kolab Kolab (2.2.0-2.3-i586) running happily on OpenSuse 11.1.
>
> The only snag is that (in Kontact) completed to-do items do not get added
> to the journal. Explicitly created journal entries are fine. Is this the
> right forum to get help on that, or might it be a KDE issue?

Kolab is a groupware concept which naturally includes the clients.
Yes quite a few KDE Kolab Client users do read here. :)

This sounds like a defect, what is your version of Kontact?
(The next step is to create a good testcase for a problem report.)

-- 
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-users/attachments/20090528/c2b34cb3/attachment.bin

From bernhard at intevation.de  Thu May 28 21:30:26 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 28 May 2009 21:30:26 +0200
Subject: Amavis quarantine cleanup
In-Reply-To: <1F73A86D-EA4C-4E18-A477-2E9E42D20E8F@livadaru.net>
References: <C8EF7E28-563A-4947-A872-B402E7F7F629@livadaru.net>
	<200905271658.44172.andre.mathibe@mortgage-services.de>
	<1F73A86D-EA4C-4E18-A477-2E9E42D20E8F@livadaru.net>
Message-ID: <200905282130.27034.bernhard@intevation.de>

Am Donnerstag, 28. Mai 2009 13:45:52 schrieb Cristian Livadaru:
> > i used this in my crontab .... ?quick and not soooooooo dirty,...
> >
> > #### delete qurantained Virus-eMails older than 30 days ####
> > 10 2 * * * find /var/spool/amavis/tmp/ -mtime +31 -exec rm -r {} \;
> > 15 2 * * * find /var/spool/amavis/virusmails/ -mtime +31 -exec rm {} ?
> > \;
>
> thanks, just added this to my crontab

Please also add nice hints to the wiki. ;)


-- 
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-users/attachments/20090528/5ff2ca2e/attachment.bin

From bernhard at intevation.de  Thu May 28 21:32:09 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 28 May 2009 21:32:09 +0200
Subject: Mail archiving: Has anyone gotten OMA (open mail archive) to work
	with kolab?
In-Reply-To: <4A1BB391.3040607@FuH-E.de>
References: <4A1BB391.3040607@FuH-E.de>
Message-ID: <200905282132.10188.bernhard@intevation.de>

Am Dienstag, 26. Mai 2009 11:17:05 schrieb Christian R??ler:
> | PHP Notice: ?Use of undefined constant AF_UNIX - assumed 'AF_UNIX' in
> | /kolab/local/oma/lib/Socket.class.php on line 51

Check the specific php version requirements for OMA.
Otherwise it would be interested where AF_UNIX is usally defined in an php 
installation, maybe you can find it and just transfer that definition?

-- 
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-users/attachments/20090528/507511ba/attachment.bin

From bernhard at intevation.de  Thu May 28 21:33:44 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 28 May 2009 21:33:44 +0200
Subject: Error upgrading  kolab  from 2.2.1 to 2.2.2
In-Reply-To: <4A1C1040.1020504@advocap.org>
References: <200905251407.19546.johnm@advocap.org>
	<4A1C1040.1020504@advocap.org>
Message-ID: <200905282133.44705.bernhard@intevation.de>

Am Dienstag, 26. Mai 2009 17:52:32 schrieb John McMonagle:
> Then ran without ?-p "ix86-debian5.0-kolab" and it worked.
> As a simple check all of /kolab/bin and sbin are new.
>
> Any chance the the .rpmorig files that mess up startup could be removed
> by the startup script?
> Not much point in preserving them as they are all created by templates.

The problem is that there could be some that are not created by templates,
but if somebody codes a script deleting those, it would be helpful I think.


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

From Nicholas.Moore at tsr-i.com  Thu May 28 21:42:06 2009
From: Nicholas.Moore at tsr-i.com (Nicholas Moore)
Date: Thu, 28 May 2009 21:42:06 +0200
Subject: to-dos and journal entries
Message-ID: <200905282142.06802.Nicholas.Moore@tsr-i.com>

Kontact 1.3 on KDE 4.1.3 - 

Solved - it is necessary to manually click on the check box next to the item in the to-do list  - even though it appears to be automatically selected by declaring and then saving the event as 100% complete.


On Thursday 28 May 2009 12:23:43 Nicholas Moore wrote:
> I have Kolab Kolab (2.2.0-2.3-i586) running happily on OpenSuse 11.1.
> 
> The only snag is that (in Kontact) completed to-do items do not get added to the journal. Explicitly created journal entries are fine. Is this the right forum to get help on that, or might it be a KDE issue?

-- 

Nicholas Moore
Limoges
France
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20090528/98c36792/attachment.html

From ml at radoeka.nl  Thu May 28 22:23:34 2009
From: ml at radoeka.nl (Richard Bos)
Date: Thu, 28 May 2009 22:23:34 +0200
Subject: Problem with calendar via HTTP.
In-Reply-To: <7907AE10BB50DD4F840E76527D27EF19029F6AF7@entmail.domain.austinent.com>
References: <7907AE10BB50DD4F840E76527D27EF19029F6AF7@entmail.domain.austinent.com>
Message-ID: <200905282223.38492.ml@radoeka.nl>

Hi,

Op donderdag 28 mei 2009 18:00:49 schreef Lucas Hendricks:
> I have this same issue on Horde with Kolab 2.2.2.  Calendars made by kolab
> admin interface (default calendar and public event folders) work fine with
> the icalendar subscription, but any calendars made with client
> programs(horde and kontact/win) end up with the below issue.
>
> On internet explorer the URL doesn't even correctly parse and gives this at
> the end: /INBOX%2FTestKontactCalendar.ics
> Instead of /INBOX/TestKontactCalendar.ics
>
> Lucas

Open an issue in the kolab's problem tracker, please:
https://intevation.de/roundup/kolab/

The change of having problems fixed without an issue in the tracker is very 
very small!


> -----Original Message-----
> From: Diego M. Vadell [mailto:dvadell at linuxclusters.com.ar]
> Sent: Wednesday, May 27, 2009 8:44 PM
> To: kolab-users at kolab.org
> Subject: Problem with calendar via HTTP.
>
> Hi,
>
>    I'm having a problem with making calendar and using them via HTTP.
>
> * I can suscribe myself to my personal calendar in
> https://gluster1.pampa.linuxclusters.com.ar/client/rpc.php/kronolith/dvadel
>l @pampa.linuxclusters.com.ar/dvadell at pampa.linuxclusters.com.ar.ics . I can
> use it in thunderbird, kontact and if I browse to that URL I get a ics
>
> file.
>
> * I then created a new calendar, called "Compartido", via Horde. The URL
> that
> Horde gave me is
> https://gluster1.pampa.linuxclusters.com.ar/client/rpc.php/kronolith/dvadel
>l @pampa.linuxclusters.com.ar/INBOX/Compartido.ics
>
> * I created one event.
>
> * The IMAP folder is there. It has a mail with an attachment. It looks like
> the event I just created.
>
> * I configure Kontact to use the calendar and get: The file or folder
> https://gluster1.pampa.linuxclusters.com.ar/client/rpc.php/kronolith/dvadel
>l @pampa.linuxclusters.com.ar/INBOX/Compartido.ics
> does not exist.
>
> * I configure thunderbird to use the calendar. The calendar gets added but
> the
> event does not appear. When I try to add an event, I get an error:
>
> An error occurred when writing to the calendar Compartido! Error number:
> Modification_failed .
>
> * If I try to GET the calendar's URL with wget, I get: HTTP request sent,
> awaiting response... 404 File Not Found
>
> * If I try to GET the calendar's URL with firefox I get a blank page.
> Completely blank. In horde.log (inside client/log) I get all this.
>
> May 28 21:49:36 HORDE [debug] [imp] Hook
> _prefs_change_hook_expanded_folders
>
> in application horde not called. [pid 17092 on line 1683
> of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 28 21:49:36 HORDE [debug] [imp] Hook
> _prefs_change_hook_expanded_folders
>
> in application horde not called. [pid 17092 on line 1683
> of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 28 21:49:36 HORDE [debug] [imp] Hook
> _prefs_change_hook_expanded_folders
>
> in application horde not called. [pid 17092 on line 1683
> of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 28 21:49:36 HORDE [debug] [imp] Hook
> _prefs_change_hook_expanded_folders
>
> in application horde not called. [pid 17092 on line 1683
> of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 28 21:49:36 HORDE [debug] [imp] Hook
> _prefs_change_hook_expanded_folders
>
> in application horde not called. [pid 17092 on line 1683
> of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 28 21:49:36 HORDE [debug] [imp] Hook
> _prefs_change_hook_expanded_folders
>
> in application horde not called. [pid 17092 on line 1683
> of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 28 21:49:36 HORDE [debug] [imp] Hook
> _prefs_change_hook_expanded_folders
>
> in application horde not called. [pid 17092 on line 1683
> of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 28 21:49:36 HORDE [debug] [imp] Hook
> _prefs_change_hook_expanded_folders
>
> in application horde not called. [pid 17092 on line 1683
> of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 28 21:49:36 HORDE [debug] [imp] Hook
> _prefs_change_hook_expanded_folders
>
> in application horde not called. [pid 17092 on line 1683
> of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 28 21:49:36 HORDE [debug] [imp] Hook
> _prefs_change_hook_expanded_folders
>
> in application horde not called. [pid 17092 on line 1683
> of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 28 21:49:36 HORDE [debug] [imp] Hook
> _prefs_change_hook_expanded_folders
>
> in application horde not called. [pid 17092 on line 1683
> of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 28 21:49:36 HORDE [notice] [imp] Login success for dvadell
> [10.200.200.7]
> to {gluster1.pampa.linuxclusters.com.ar:143 [imap/notls/novalidate-cert]}
> [pid 17092 on line 304 of
> "/kolab/var/kolab/www/client/imp/lib/Session.php"] May 28 21:49:36 HORDE
> [debug] [kronolith] Hook _horde_hook_share_init in application horde not
> called. [pid 17092 on line 1683
> of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 28 21:49:36 HORDE [debug] [kronolith] Hook
> _prefs_change_hook_display_remote_cals in application horde not called.
> [pid
>
> 17092 on line 1683 of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 28 21:49:36 HORDE [debug] [kronolith] Hook
> _prefs_change_hook_display_external_cals in application horde not called.
> [pid 17092 on line 1683 of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 28 21:49:36 HORDE [debug] [kronolith] Hook
> _prefs_change_hook_display_cals
> in application horde not called. [pid 17092 on line 1683
> of "/kolab/var/kolab/www/client/lib/Horde.php"]
> May 28 21:49:36 HORDE [debug] [horde] Max memory usage: 11534336 bytes [pid
> 17092 on line 339 of "/kolab/var/kolab/www/client/lib/Horde/Registry.php"]
> May 28 21:49:36 HORDE [debug] [horde] IMAP errors: SECURITY PROBLEM:
> insecure
> server advertised AUTH=PLAIN [pid 17092 on line 175
> of "/kolab/var/kolab/www/client/imp/lib/IMAP.php"]
>
> The last line looks like a warning only. Then "[notice]" line says that it
> could login as my user (dvadell) into this test server.
>
> I looked for something similar in the bug tracker, but nothing ringed any
> bell. Does anyone knows how I can futher debug this?
>
> TIA
>  -- Diego
>
> _______________________________________________
> 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

-- 
Richard



From ml at radoeka.nl  Thu May 28 23:00:13 2009
From: ml at radoeka.nl (Richard Bos)
Date: Thu, 28 May 2009 23:00:13 +0200
Subject: [Solved] Unable to Sync Calendar / PHP Fatal error
	compareDateTime()
In-Reply-To: <200905281150.07404.webmaster@computational-chemistry.org>
References: <200905201353.46188.Webmaster@computational-chemistry.org>
	<200905251931.05020.t.nintemann@medial-networks.de>
	<200905281150.07404.webmaster@computational-chemistry.org>
Message-ID: <200905282300.13608.ml@radoeka.nl>

Hi,

Op donderdag 28 mei 2009 11:50:07 schreef Alexander Schr?ter:
> On Monday 25 May 2009 07:31:04 pm Thomas Nintemann wrote:
> > Am Monday 25 May 2009 17:33:37 schrieb Carsten Burghardt:
> > > Zitat von Thomas Nintemann <t.nintemann at medial-networks.de>:
> > > >> Now I read on the mailing list that it should work. So I checked the
> > > >> logs for errors that only happen when I sync stuff. And this is the
> > > >> one I found in the /kolab/var/kolab/www/client/log/php-errors.log
> > > >>
> > > >> "PHP Fatal error :  Call to a member function compareDateTime() on a
> > > >> non- object in
> > > >> /kolab/var/kolab/www/client/kronolith/lib/Driver/kolab.php on line
> > > >> 1153"
> > > >
> > > > Same on my Side with Kolab 2.2.1 native on OpenSUSE-11.1.
> > > > My Client is a Blackberry 8300 Curve with actual Funambol-Plugin.
> > > >
> > > > For stupid test  i comment out the Line 1153 and 1154 as here:
> > > > /*if (!(($endDate->compareDateTime($event->start) < 0) ||
> > > >                   ($startDate->compareDateTime($event->end) > 0)))*/
> > > >
> > > > and it sync's.
> > > > But i now this a bad idea.
> > > >
> > > > Any better idea's?
> > >
> > > Not a real solution but according to the error I'd say that either
> > > $endDate or $startDate is not defined and not recognized as a date
> > > object. Maybe a null check should be sufficient?
> > >
> > >
> > > Carsten
> >
> > OK, thanks for the Tip.
> >
> > I have now made changes as follow on those lines:
> >
> > Line 1137
> > ---------------------------
> > if (is_null($startDate)) {
> > ----------------------------
> > to
> > ----------------------------
> > if (empty($startDate)) {
> > -----------------------------
> >
> > and Line 1140
> > -----------------------------
> > if (is_null($endDate)) {
> > ----------------------------
> > to
> > -----------------------------
> > if (empty($endDate)) {
> > -----------------------------
> >
> > and now it syncs without my stupid comment out of lines 1153 and 1154.
> >
> > But i do not now this is the right way to solve that problem.
> >
> > Thomas
>
> I have been testing this for the last couple of days and I didn't get an
> error. For me the issue is fixed, but of course it would be nice to have a
> developer or somebody who knows the code doublecheck everything and give
> some feedback.
>
> Is there a way to let the guys from Horde know about this issue? So they
> can fix it too.
>
> Regards Alexander

Open an issue in the kolab's problem tracker, please:
https://intevation.de/roundup/kolab/

The chance of having problems fixed without an issue in the tracker is very 
very small!


-- 
Richard



From jens at homejm.de  Thu May 28 23:50:54 2009
From: jens at homejm.de (Jens Mohr)
Date: Thu, 28 May 2009 23:50:54 +0200
Subject: Problem after restore kolab v2.2.0
Message-ID: <200905282350.54393.jens@homejm.de>

Hi all,

in my Company we use kolab 2.2.0. Now i have a little trouble.

Our System runs on Fedora 7 over one year perfect. Now i will change the operatingsystem. Therefor I setup a VM with CentOS 5.3 & have compile  the kolab 2.2.0 new. Then i have restore our backup and all runs perfect.

But now we must find out our Server (x336) runs not with CentOS 5.3. I think no problem! He ist certified for RH4 then i can use CentOS 4.7.

The Server is running gcc-3.4.6-10 also no problem. Kolab compile fine!

But after restore i can not login! He say user or password isn't correct!

Now my question: is my procedure in backup and restore the problem?

My kolab_backup.sh:
-----------------------------------------------------------------------------------------------------
#!/bin/bash
# Script by Micha Kersloot (micha at kovoks.nl) under the GPLv2 licence
# Script changed by Jens Mohr jens at homejm.de

BACKDIR="/backup"
KOLABDIR="/kolab"

ROTATEDIR=`date +%Y-%m-%d_%H-%M`
DESTDIR=$BACKDIR/$ROTATEDIR

mkdir -p $DESTDIR

#Stop Kolab
/kolab/bin/openpkg rc all stop

#Cyrus backup
su - kolab-r -c "$KOLABDIR/bin/ctl_mboxlist -d" > $KOLABDIR/var/imapd/mailboxlist.txt
tar -zpcf $DESTDIR/var_imapd.tgz $KOLABDIR/var/imapd

#OpenLDAP backup
$KOLABDIR/sbin/slapcat > $DESTDIR/ldap_db.ldif
tar -zpcf $DESTDIR/ldap_conf.tgz $KOLABDIR/var/openldap/openldap-data/DB_CONFIG $KOLABDIR/etc/openldap/slapd.conf $KOLABDIR/etc/openldap/slapd.access

#Kolab backup
tar -zpcf $DESTDIR/kolab_conf.tgz $KOLABDIR/etc

#Spamassassin backups
mkdir $DESTDIR/spam
/kolab/bin/sa-learn --backup > $DESTDIR/spam/spamassassin-bck.txt
cp $KOLABDIR/spam-learn.sh $DESTDIR/spam/
cp /var/spool/cron/kolab-r $DESTDIR/spam/

#Start Kolab
#/kolab/bin/openpkg rc all start
-----------------------------------------------------------------------------------------------------

my kolab_restore.sh
-----------------------------------------------------------------------------------------------------
#!/bin/bash

BACKDIR="/backup"
KOLABDIR="/kolab"

ROTATEDIR=$1
SOURCEDIR=$BACKDIR/$ROTATEDIR

/kolab/bin/openpkg rc all stop
cd /
tar -zpxvf $SOURCEDIR/kolab_conf.tgz
tar -zpxvf $SOURCEDIR/ldap_conf.tgz
tar -zpxvf $SOURCEDIR/var_imapd.tgz

cp -p $SOURCEDIR/spam/spam-learn.sh /kolab
cp -p $SOURCEDIR/spam/kolab-r /var/spool/cron/
chown kolab-r $KOLABDIR/spam-learn.sh
chown kolab-r /var/spool/cron/kolab-r

su - kolab-r -c "/kolab/bin/ctl_mboxlist -u" < $KOLABDIR/var/imapd/mailboxlist.txt

cp $KOLABDIR/var/openldap/openldap-data/DB_CONFIG /tmp/
rm -rf $KOLABDIR/var/openldap/openldap-data/*
cp /tmp/DB_CONFIG $KOLABDIR/var/openldap/openldap-data/
/kolab/sbin/slapadd -l $SOURCEDIR/ldap_db.ldif
chown -R kolab:kolab $KOLABDIR/var/openldap/openldap-data

/kolab/bin/sa-learn --restore $SOURCEDIR/spam/spamassassin-bck.txt

/kolab/bin/openpkg rc all start

/kolab/sbin/kolabconf -n
-----------------------------------------------------------------------------------------------------

I restore for testing the same backup in CentOS 5.3 all is running
in 4.7 i have a problem!

Thanks for help!

Jens



From Roessler at FuH-E.de  Fri May 29 15:46:57 2009
From: Roessler at FuH-E.de (=?ISO-8859-15?Q?Christian_R=F6=DFler?=)
Date: Fri, 29 May 2009 15:46:57 +0200
Subject: Organization of incoming mails?
Message-ID: <4A1FE751.9050207@FuH-E.de>

Hallo everyone,

while this question is technically not related to Kolab in a narrow
sense, I would like to pose it anyway as it is intertwined to Kolab for
me here.

The question is about the organization of incoming mail. I would think
that most admins organize incoming mail for their company in an
(imap-)tree structure. So I would like to know:

- Does anyone use an alternative to that tree, and if, which one?

But perhaps more important: How gets your incoming mail sorted into that
tree? As usual per sieve scripts?

And maybe most important, for me: Can anyone suggest a 'sorting'
solution which could be better maintained than a sieve script? If so, which?

Best regard, and a nice weekend to everyone,
Christian



From johnm at advocap.org  Sat May 30 00:10:54 2009
From: johnm at advocap.org (John McMonagle)
Date: Fri, 29 May 2009 17:10:54 -0500
Subject: mail box creation
Message-ID: <200905291710.54945.johnm@advocap.org>

I noticed that new user mail boxes are not being created.

I am not using kolab's ldap server.
I sort of recall something about kolabd using slurpd to know about changes.

If I restart  kolabd the mail boxes get created.
Is the lack of slurpd my problem?
Anything I can do other than manually creating mail boxes or restarting 
kolabd?

Thanks

John



From hjkim at bynari.net  Fri May 29 19:52:00 2009
From: hjkim at bynari.net (Hyun Kim)
Date: Fri, 29 May 2009 12:52:00 -0500
Subject: new Bynari Beta Insight Connector 4.0 available 
Message-ID: <4d3c6354.1c9e086.b712a84.43c7@bynari.net>

Kolab users, 
I wanted to let you know that the new Beta for Insight Connector 4.0 is available for testing!
 
Our goal is to provide you with a Connector that exceeds your expectations.  We would really appreciate any feedback that you can provide through icbeta at bynari.net.  
 
Here is the link to the product:
https://beyond.bynari.net/files/connector/ic4beta/Bynari-InsightConnector-iCal-Kolab-4.0.0-0528516-INI.zip
Release note:
http://www.bynari.net/release_notes/insight_connector_release_notes/insight_connector_4.0.0_beta_release_notes.html
Installation Guide:
http://www.bynari.net/images/documentation/connector/insight_connector_40_quick_installation_guide.pdf
 
Thank you for your assistance!
Hyun 

Mrs. Hyun Kim
President
Bynari, Inc.
2639 Electronic Lane, Suite 110
Dallas, Tx  75220
www.bynari.net
(214) 350-5772 X59
(214) 789-8674 cell
(214) 352-3530 fax
 
"Sharing made easy...leading the way for Universal Collaboration."
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20090529/f31ce52e/attachment.html

From hermann at qwer.tk  Sun May 31 16:29:51 2009
From: hermann at qwer.tk (Hermann Himmelbauer)
Date: Sun, 31 May 2009 16:29:51 +0200
Subject: Status of Kolab - possible production usage?
Message-ID: <200905311629.52042.hermann@qwer.tk>

Hi,
I'm currently looking for a Linux-based groupware for me and my clients. After 
searching a lot (and not wanting to use Exchange), I came across Kolab, which 
looks very promising to me, as it uses technologies, which I like and which I 
currently use in various installations (postfix, cyrus, spamassassin, 
clamav...).

In specific, I am looking for the following:

- Decent webclient (horde)
- Groupware functionality
- MS Outlook integration 
- KDE (Kontact) integration
- Syncing with mobile phones (SyncML)

So I downloaded the latest Kolab version (2.2.2) and installed it on my Debian 
5.0 server. On my client, I currently use KDE-3.5.9 (distributed with suSE 
11.0). The server install was very smooth, user creation too.

But the client install is a mess - tried it with kolabwizard first, but 
Kontact (kmail) keeps crashing, found out that this had to do with Sieve, 
which I now disabled. Then I tried to transfer some of my contacts from my 
local to the kolab resources via cut & paste -> kaddressbook crashed.

Ok, I then tried to look at Horde to see, if the transfer actually worked, but 
there are no contacts, no calendar entries. However, when I enter a calendar 
entry directly in Horde, it's invisible in Horde, but visible in Kontact. For 
the addresses, I'm unsure if they are acutally synced to the server, as they 
are, too, invisible on Horde. (But I can see them in the IMAP folders).

Next I tried syncing my SonyEricsson K750i with Horde, which also failed due 
to some unknown reason - I tried that before with funambol, which did work, 
but there seems to be no interface between Kolab/Horde <-> funambol.

After that many struggles, I'm asking myself if Kolab is ready for production 
use or if I should give it some time to stabilize and switch to something 
else in the meantime.

What are your experiences? Perhaps I had bad luck? Am I better off with the 
latest KDE release instead of 3.5.9?

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 ml at radoeka.nl  Sun May 31 22:14:37 2009
From: ml at radoeka.nl (Richard Bos)
Date: Sun, 31 May 2009 22:14:37 +0200
Subject: Status of Kolab - possible production usage?
In-Reply-To: <200905311629.52042.hermann@qwer.tk>
References: <200905311629.52042.hermann@qwer.tk>
Message-ID: <200905312214.39692.ml@radoeka.nl>

Hello Hermann,

Op zondag 31 mei 2009 16:29:51 schreef Hermann Himmelbauer:
> Next I tried syncing my SonyEricsson K750i with Horde, which also failed
> due to some unknown reason - I tried that before with funambol, which did
> work, but there seems to be no interface between Kolab/Horde <-> funambol.

Syncing is still in its infancy.  Syncing was provided for the 1st with 
kolab-2.2.2.  So, there are probably still problems, and if you look back at 
the email list of may (2009), you'll see that there indeed are some problems.

> After that many struggles, I'm asking myself if Kolab is ready for
> production use or if I should give it some time to stabilize and switch to
> something else in the meantime.

Kolab is definately ready for production use.  It is used in production.  I 
have no numbers about how many sites, but I think it is quite a lot.

> What are your experiences? Perhaps I had bad luck? Am I better off with the
> latest KDE release instead of 3.5.9?

You had definitely bad luck.  Many people are happily using kolab.  Give it 
another try.  For production use you might want to use the enterprise version 
of kontact as described here http://www.kolab.org/about-kolab-clients.html

-- 
Richard



From alain.abbas at libertech.Fr  Wed May 20 11:57:37 2009
From: alain.abbas at libertech.Fr (Alain Abbas)
Date: Wed, 20 May 2009 09:57:37 -0000
Subject: z-push backend
Message-ID: <64ca4fd8.1c9d931.34cddc4.4d50@libertech.Fr>

hi 
you can find an alpha version (0.1) of the kolab backend for z-push at support.libertech.fr in te download
section with an installation note.

for the moment : 
-Calendar work on iphone and mobilePC (tested on HTC) 

-Contacts work on iphone an mobilePC 

-task not yet implemented 

be carefull read the note (the known issue, and todo list  ) , not for a production use  :-) 



-----Message d'origine-----
De?: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org] De la part de Alain Abbas
Envoy??: mercredi 20 mai 2009 10:41
??: 'Bernhard Reiter'
Cc?: 'kolab-users at kolab.org'
Objet?: RE: SyncML in 2.2.2 ?

hi 
normal for iphone Apple doesn t allow to access to calenar for an external application 
and the version 3 anounce the sync with caldav .... 

we are working on z-push and already done the sync of the calendar and contacts
work with kolab 2.2.1 and 2.2.2 
the state of our work :
for contacts :
-not all the fieds are synchronized and not the picture of the contact

for the calendar :
request meeting not implemented for the moment 

for mail :
Imap is better ..... 

if someone is interested .... 


-----Message d'origine-----
De?: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org] De la part de Bernhard Reiter
Envoy??: mercredi 20 mai 2009 10:14
??: kolab-users at kolab.org
Objet?: Re: SyncML in 2.2.2 ?

Alexander, Ulrich,

thanks for the reports and feedback we appreciate it.
Yes, calender sync should be working (though you might need to trigger two syncs sometimes). If it does not, opening a problem report with the tracker is very good, if you can provide detailed information.

We face the problem that we do not have all the models of hardware and software available and testing many combinations is costly.
<advertisment>If you have funding for this, Kolab-Konsortium will be happy to buy your device, test and fix support for it, if possible.
</advertisment>

Am Mittwoch, 20. Mai 2009 08:49:04 schrieb Ulrich Oestreicher:
> I have the same problem.
> Contacts and tasks works, but the calendar is not working.
> I using the synthesis conector for iphone.

> Zitat von Alexander Schr?ter <Webmaster at computational-chemistry.org>:
> > Ohh really? I started out with 2.2.1 and it never worked with the 
> > Calendar. But I have found a hint in the php-error log of horde. 
> > Some function regarding the Time and Date is producing a Fatal 
> > error. Maybe I will open up a new topic to fix the problem.

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

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



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

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

Hi Mike,
Hi Bernhard,

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

- Only Kolab users with 

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

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

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

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

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

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

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

I am looking forward to your feedback.

Yours,
-- martin

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