From O.Stahl at lsw.uni-heidelberg.de  Thu Jan  1 10:18:33 2009
From: O.Stahl at lsw.uni-heidelberg.de (Otmar Stahl)
Date: Thu, 01 Jan 2009 10:18:33 +0100
Subject: SMTP SSL problem after upgrade from kolab 2.1 to 2.2.0
Message-ID: <495C8A69.3020003@lsw.uni-heidelberg.de>

Hello and happy new year,

After an upgrade from kolab 2.1 to 2.2.0 I have a problem with sending
mail via ssl from outside the kolab domain. This worked in kolab 2.1.

The error message I get with thunderbird is:

"An error occured while sending the mail.  The server reponded: 4.3.5
Server configuration problem. Please check the message recipients and
try again."

The corresponding lines in the postfix.log are the following:

"Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
connect from p5B0770BE.dip.t-dialin.net[91.7.112.190]
Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
setting up TLS connection from p5B0770BE.dip.t-dialin.net[91.7.112.190]
Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
TLS connection established from
p5B0770BE.dip.t-dialin.net[91.7.112.190]: TLSv1 with cipher
DHE-RSA-AES256-SHA (256/256 bits)
Jan 01 09:55:05 srv0.lsw.uni-heidelberg.de <warning>
postfix/spawn[4146]: warning: command /kolab/etc/kolab/kolab_smtpdpolicy
exit status 2
Jan 01 09:55:05 srv0.lsw.uni-heidelberg.de <warning>
postfix/smtpd[4143]: warning: premature end-of-input on
private/kolabpolicy while reading input attribute name
Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <warning>
postfix/spawn[4146]: warning: command /kolab/etc/kolab/kolab_smtpdpolicy
exit status 2
Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <warning>
postfix/smtpd[4143]: warning: premature end-of-input on
private/kolabpolicy while reading input attribute name
Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <warning>
postfix/smtpd[4143]: warning: problem talking to server
private/kolabpolicy: Connection reset by peer
Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
NOQUEUE: reject: RCPT from p5B0770BE.dip.t-dialin.net[91.7.112.190]: 451
4.3.5 Server configuration problem; from=<O.Stahl at lsw.uni-heidelberg.de>
to=<otmarstahl at web.de> proto=ESMTP helo=<[192.168.0.21]"

Any idea what could be causing this? How can I debug this issue?

Thank you in advance for your help,

Kind regards,
Otmar Stahl






From O.Stahl at lsw.uni-heidelberg.de  Thu Jan  1 13:41:38 2009
From: O.Stahl at lsw.uni-heidelberg.de (Otmar Stahl)
Date: Thu, 01 Jan 2009 13:41:38 +0100
Subject: SMTP SSL problem after upgrade from kolab 2.1 to 2.2.0
In-Reply-To: <495C8A69.3020003@lsw.uni-heidelberg.de>
References: <495C8A69.3020003@lsw.uni-heidelberg.de>
Message-ID: <495CBA02.4000501@lsw.uni-heidelberg.de>

Otmar Stahl schrieb:
> Hello and happy new year,
> 
> After an upgrade from kolab 2.1 to 2.2.0 I have a problem with sending
> mail via ssl from outside the kolab domain. This worked in kolab 2.1.
> 
> The error message I get with thunderbird is:
> 
> "An error occured while sending the mail.  The server reponded: 4.3.5
> Server configuration problem. Please check the message recipients and
> try again."
> 
> The corresponding lines in the postfix.log are the following:
> 
> "Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
> connect from p5B0770BE.dip.t-dialin.net[91.7.112.190]
> Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
> setting up TLS connection from p5B0770BE.dip.t-dialin.net[91.7.112.190]
> Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
> TLS connection established from
> p5B0770BE.dip.t-dialin.net[91.7.112.190]: TLSv1 with cipher
> DHE-RSA-AES256-SHA (256/256 bits)
> Jan 01 09:55:05 srv0.lsw.uni-heidelberg.de <warning>
> postfix/spawn[4146]: warning: command /kolab/etc/kolab/kolab_smtpdpolicy
> exit status 2
> Jan 01 09:55:05 srv0.lsw.uni-heidelberg.de <warning>
> postfix/smtpd[4143]: warning: premature end-of-input on
> private/kolabpolicy while reading input attribute name
> Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <warning>
> postfix/spawn[4146]: warning: command /kolab/etc/kolab/kolab_smtpdpolicy
> exit status 2
> Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <warning>
> postfix/smtpd[4143]: warning: premature end-of-input on
> private/kolabpolicy while reading input attribute name
> Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <warning>
> postfix/smtpd[4143]: warning: problem talking to server
> private/kolabpolicy: Connection reset by peer
> Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
> NOQUEUE: reject: RCPT from p5B0770BE.dip.t-dialin.net[91.7.112.190]: 451
> 4.3.5 Server configuration problem; from=<O.Stahl at lsw.uni-heidelberg.de>
> to=<otmarstahl at web.de> proto=ESMTP helo=<[192.168.0.21]"


I forgot to mention that this is on debian lenny and the kolab setup is
quite standard.

The mail client is thunderbird and I want to use "smtp auth".

I receive the password prompt and then the mail sending fails and the
error message appears. When I switch to unauthorized smtp, the same
error appears.

> Any idea what could be causing this? How can I debug this issue?
> 
> Thank you in advance for your help,
> 
> Kind regards,
> Otmar Stahl

Otmar Stahl


From aspineux at gmail.com  Fri Jan  2 11:58:48 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Fri, 2 Jan 2009 11:58:48 +0100
Subject: SMTP SSL problem after upgrade from kolab 2.1 to 2.2.0
In-Reply-To: <495C8A69.3020003@lsw.uni-heidelberg.de>
References: <495C8A69.3020003@lsw.uni-heidelberg.de>
Message-ID: <71fe4e760901020258r20bdaf2cuc067bd919aa64ce7@mail.gmail.com>

On Thu, Jan 1, 2009 at 10:18 AM, Otmar Stahl
<O.Stahl at lsw.uni-heidelberg.de> wrote:
> Hello and happy new year,
>
> After an upgrade from kolab 2.1 to 2.2.0 I have a problem with sending
> mail via ssl from outside the kolab domain. This worked in kolab 2.1.
>
> The error message I get with thunderbird is:
>
> "An error occured while sending the mail.  The server reponded: 4.3.5
> Server configuration problem. Please check the message recipients and
> try again."
>
> The corresponding lines in the postfix.log are the following:
>
> "Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
> connect from p5B0770BE.dip.t-dialin.net[91.7.112.190]
> Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
> setting up TLS connection from p5B0770BE.dip.t-dialin.net[91.7.112.190]
> Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
> TLS connection established from
> p5B0770BE.dip.t-dialin.net[91.7.112.190]: TLSv1 with cipher
> DHE-RSA-AES256-SHA (256/256 bits)
> Jan 01 09:55:05 srv0.lsw.uni-heidelberg.de <warning>
> postfix/spawn[4146]: warning: command /kolab/etc/kolab/kolab_smtpdpolicy
> exit status 2

Something wrong is happening her, please look into
/kolab/var/kolab-filter/log/filter.log
for more error

Regards

> Jan 01 09:55:05 srv0.lsw.uni-heidelberg.de <warning>
> postfix/smtpd[4143]: warning: premature end-of-input on
> private/kolabpolicy while reading input attribute name
> Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <warning>
> postfix/spawn[4146]: warning: command /kolab/etc/kolab/kolab_smtpdpolicy
> exit status 2
> Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <warning>
> postfix/smtpd[4143]: warning: premature end-of-input on
> private/kolabpolicy while reading input attribute name
> Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <warning>
> postfix/smtpd[4143]: warning: problem talking to server
> private/kolabpolicy: Connection reset by peer
> Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
> NOQUEUE: reject: RCPT from p5B0770BE.dip.t-dialin.net[91.7.112.190]: 451
> 4.3.5 Server configuration problem; from=<O.Stahl at lsw.uni-heidelberg.de>
> to=<otmarstahl at web.de> proto=ESMTP helo=<[192.168.0.21]"
>
> Any idea what could be causing this? How can I debug this issue?
>
> Thank you in advance for your help,
>
> Kind regards,
> Otmar Stahl
>
>
>
>
>
> _______________________________________________
> 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  Fri Jan  2 14:35:12 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Fri, 02 Jan 2009 14:35:12 +0100
Subject: Address book in Kolab admin webinterface: some entries not shown
Message-ID: <495E1810.3010701@FuH-E.de>

Hallo,

I have noticed some entries in the Kolab webinterface 
(https://my_kolabserver/admin/addressbook/) being not shown, e.g. the 
telephone an fax numbers, but are correctly stored in LDAP (and function 
perfectly eg. in Kontact). If I change one of these entries in the 
address book they will be correctly stored in LDAP; but also not shown 
in the web interface. The same happens when I make a complete, new 
adress entry using the web interface.

Looking into the php logfile (/kolab/var/log/apache/php/php-errors.log) 
I notice these entries:

[02-Jan-2009 14:01:37] PHP Notice:  Undefined index:  roomnumber in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 37
[02-Jan-2009 14:01:37] PHP Notice:  Undefined index:  roomnumber in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 38
[02-Jan-2009 14:01:37] PHP Notice:  Undefined index:  postofficebox in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 37
[02-Jan-2009 14:01:37] PHP Notice:  Undefined index:  postofficebox in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 38
[02-Jan-2009 14:01:37] PHP Notice:  Undefined index:  postalcode in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 37
[02-Jan-2009 14:01:37] PHP Notice:  Undefined index:  postalcode in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 38
[02-Jan-2009 14:01:37] PHP Notice:  Undefined index:  telephonenumber in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 37
[02-Jan-2009 14:01:37] PHP Notice:  Undefined index:  telephonenumber in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 38
[02-Jan-2009 14:01:37] PHP Notice:  Undefined index: 
facsimiletelephonenumber in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 37
[02-Jan-2009 14:01:37] PHP Notice:  Undefined index: 
facsimiletelephonenumber in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 38
[02-Jan-2009 14:01:37] PHP Notice:  Undefined index:  alias in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 41
[02-Jan-2009 14:01:37] PHP Notice:  Undefined index:  alias in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 46
[02-Jan-2009 14:01:44] PHP Notice:  Undefined offset:  1 in 
/kolab/var/kolab/php/admin/include/ldap.class.php on line 370
[02-Jan-2009 14:01:44] PHP Notice:  Undefined offset:  0 in 
/kolab/var/kolab/php/admin/include/ldap.class.php on line 392

...which matches the missing entries.

I have noticed this error after filling the ldap hierarchy under 
cn=external,dc=... fron another source, so I cannot say since when this 
error happens. Deleting these 'foreign' entries does not help.

Any hints, please?

Best regards,
Christian

PS. Btw, kolab 2.2.0


From aspineux at gmail.com  Sun Jan  4 11:59:14 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Sun, 4 Jan 2009 11:59:14 +0100
Subject: SMTP SSL problem after upgrade from kolab 2.1 to 2.2.0
In-Reply-To: <495E0F03.1000108@lsw.uni-heidelberg.de>
References: <495C8A69.3020003@lsw.uni-heidelberg.de>
	<71fe4e760901020258r20bdaf2cuc067bd919aa64ce7@mail.gmail.com>
	<495E0F03.1000108@lsw.uni-heidelberg.de>
Message-ID: <71fe4e760901040259t6d6608a8x5563eb50f1b35b43@mail.gmail.com>

On Fri, Jan 2, 2009 at 1:56 PM, Otmar Stahl
<O.Stahl at lsw.uni-heidelberg.de> wrote:
> Hello,
>
> Thank you for the mail.
>
> Alain Spineux wrote:
>>
>> On Thu, Jan 1, 2009 at 10:18 AM, Otmar Stahl
>> <O.Stahl at lsw.uni-heidelberg.de> wrote:
>>>
>>> Hello and happy new year,
>>>
>>> After an upgrade from kolab 2.1 to 2.2.0 I have a problem with sending
>>> mail via ssl from outside the kolab domain. This worked in kolab 2.1.
>>>
>>> The error message I get with thunderbird is:
>>>
>>> "An error occured while sending the mail.  The server reponded: 4.3.5
>>> Server configuration problem. Please check the message recipients and
>>> try again."
>>>
>>> The corresponding lines in the postfix.log are the following:
>>>
>>> "Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
>>> connect from p5B0770BE.dip.t-dialin.net[91.7.112.190]
>>> Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
>>> setting up TLS connection from p5B0770BE.dip.t-dialin.net[91.7.112.190]
>>> Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
>>> TLS connection established from
>>> p5B0770BE.dip.t-dialin.net[91.7.112.190]: TLSv1 with cipher
>>> DHE-RSA-AES256-SHA (256/256 bits)
>>> Jan 01 09:55:05 srv0.lsw.uni-heidelberg.de <warning>
>>> postfix/spawn[4146]: warning: command /kolab/etc/kolab/kolab_smtpdpolicy
>>> exit status 2
>>
>> Something wrong is happening her, please look into
>> /kolab/var/kolab-filter/log/filter.log
>> for more error
>
> Thank you for this hint. Unfortunately, there is absolutely nothing logged
> in this file at the corresponding date. The sending attempt seems to die
> before it can log anything in filter.log. All I have is the postfix log :-(
>
> Kind regards,
> Otmar
>

Sorry, The "policy" is a perl script, and log in the syslog, then you
should look into your /var/log/messages or /var/log/maillog or ...
depending your syslog configuration (the facility is "mail" and
priority is "info" )

You can increase the verbosity by adding a -v in your master.cf.
Dont forget to make the chnage in the template.

Regards.

>> Regards
>>
>>> Jan 01 09:55:05 srv0.lsw.uni-heidelberg.de <warning>
>>> postfix/smtpd[4143]: warning: premature end-of-input on
>>> private/kolabpolicy while reading input attribute name
>>> Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <warning>
>>> postfix/spawn[4146]: warning: command /kolab/etc/kolab/kolab_smtpdpolicy
>>> exit status 2
>>> Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <warning>
>>> postfix/smtpd[4143]: warning: premature end-of-input on
>>> private/kolabpolicy while reading input attribute name
>>> Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <warning>
>>> postfix/smtpd[4143]: warning: problem talking to server
>>> private/kolabpolicy: Connection reset by peer
>>> Jan 01 09:55:06 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
>>> NOQUEUE: reject: RCPT from p5B0770BE.dip.t-dialin.net[91.7.112.190]: 451
>>> 4.3.5 Server configuration problem; from=<O.Stahl at lsw.uni-heidelberg.de>
>>> to=<otmarstahl at web.de> proto=ESMTP helo=<[192.168.0.21]"
>>>
>>> Any idea what could be causing this? How can I debug this issue?
>>>
>>> Thank you in advance for your help,
>>>
>>> Kind regards,
>>> Otmar Stahl
>



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


From O.Stahl at lsw.uni-heidelberg.de  Sun Jan  4 13:13:57 2009
From: O.Stahl at lsw.uni-heidelberg.de (Otmar Stahl)
Date: Sun, 04 Jan 2009 13:13:57 +0100
Subject: SMTP SSL problem after upgrade from kolab 2.1 to 2.2.0
In-Reply-To: <71fe4e760901040259t6d6608a8x5563eb50f1b35b43@mail.gmail.com>
References: <495C8A69.3020003@lsw.uni-heidelberg.de>
	<71fe4e760901020258r20bdaf2cuc067bd919aa64ce7@mail.gmail.com>
	<495E0F03.1000108@lsw.uni-heidelberg.de>
	<71fe4e760901040259t6d6608a8x5563eb50f1b35b43@mail.gmail.com>
Message-ID: <20090104131357.55006vokctv3p8w8@srv0.lsw.uni-heidelberg.de>

Hello again,

Quoting Alain Spineux <aspineux at gmail.com>:

> On Fri, Jan 2, 2009 at 1:56 PM, Otmar Stahl
> <O.Stahl at lsw.uni-heidelberg.de> wrote:
>> Hello,
>>
>> Thank you for the mail.
>>
>> Alain Spineux wrote:
>>>
>>> On Thu, Jan 1, 2009 at 10:18 AM, Otmar Stahl
>>> <O.Stahl at lsw.uni-heidelberg.de> wrote:
>>>>
>>>> Hello and happy new year,
>>>>
>>>> After an upgrade from kolab 2.1 to 2.2.0 I have a problem with sending
>>>> mail via ssl from outside the kolab domain. This worked in kolab 2.1.
>>>>
>>>> The error message I get with thunderbird is:
>>>>
>>>> "An error occured while sending the mail.  The server reponded: 4.3.5
>>>> Server configuration problem. Please check the message recipients and
>>>> try again."
>>>>
>>>> The corresponding lines in the postfix.log are the following:
>>>>
>>>> "Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
>>>> connect from p5B0770BE.dip.t-dialin.net[91.7.112.190]
>>>> Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
>>>> setting up TLS connection from p5B0770BE.dip.t-dialin.net[91.7.112.190]
>>>> Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
>>>> TLS connection established from
>>>> p5B0770BE.dip.t-dialin.net[91.7.112.190]: TLSv1 with cipher
>>>> DHE-RSA-AES256-SHA (256/256 bits)
>>>> Jan 01 09:55:05 srv0.lsw.uni-heidelberg.de <warning>
>>>> postfix/spawn[4146]: warning: command /kolab/etc/kolab/kolab_smtpdpolicy
>>>> exit status 2
>>>
>>> Something wrong is happening her, please look into
>>> /kolab/var/kolab-filter/log/filter.log
>>> for more error
>>
>> Thank you for this hint. Unfortunately, there is absolutely nothing logged
>> in this file at the corresponding date. The sending attempt seems to die
>> before it can log anything in filter.log. All I have is the postfix log :-(
>>
>> Kind regards,
>> Otmar
>>
>
> Sorry, The "policy" is a perl script, and log in the syslog, then you
> should look into your /var/log/messages or /var/log/maillog or ...
> depending your syslog configuration (the facility is "mail" and
> priority is "info" )
>
> You can increase the verbosity by adding a -v in your master.cf.
> Dont forget to make the chnage in the template.

Thank you for the hints. I see errors only in postfix.log and adding  
-v to the policy script did not help. However I had a look at the  
policy script and tried to debug it by starting it from hand as  
suggested in the script. I get the following:

-------------------------------------------------------------------------
root at srv0:~#  su - kolab
kolab at srv0$  /kolab/etc/kolab/kolab_smtpdpolicy
IO object version 1.23_01 does not match bootstrap parameter 1.23 at  
/kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 226.
Compilation failed in require at  
/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/IO/Handle.pm line 263.
BEGIN failed--compilation aborted at  
/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/IO/Handle.pm line 263.
Compilation failed in require at  
/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/IO/Socket.pm line 11.
BEGIN failed--compilation aborted at  
/kolab/lib/perl/vendor_perl/5.10.0/i686-linux/IO/Socket.pm line 11.
Compilation failed in require at  
/kolab/lib/perl/vendor_perl/5.10.0/Net/LDAP.pm line 8.
BEGIN failed--compilation aborted at  
/kolab/lib/perl/vendor_perl/5.10.0/Net/LDAP.pm line 8.
Compilation failed in require at /kolab/etc/kolab/kolab_smtpdpolicy line 26.
BEGIN failed--compilation aborted at  
/kolab/etc/kolab/kolab_smtpdpolicy line 26.

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

So the script does not start at all and that should be a useful error  
message, but I still do not know what to do about it. Any hints how to  
fix this?

Kind regards,
Otmar



From aspineux at gmail.com  Sun Jan  4 16:04:47 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Sun, 4 Jan 2009 16:04:47 +0100
Subject: SMTP SSL problem after upgrade from kolab 2.1 to 2.2.0
In-Reply-To: <20090104131357.55006vokctv3p8w8@srv0.lsw.uni-heidelberg.de>
References: <495C8A69.3020003@lsw.uni-heidelberg.de>
	<71fe4e760901020258r20bdaf2cuc067bd919aa64ce7@mail.gmail.com>
	<495E0F03.1000108@lsw.uni-heidelberg.de>
	<71fe4e760901040259t6d6608a8x5563eb50f1b35b43@mail.gmail.com>
	<20090104131357.55006vokctv3p8w8@srv0.lsw.uni-heidelberg.de>
Message-ID: <71fe4e760901040704n332c2883k4a1f3090c1f60ea0@mail.gmail.com>

On Sun, Jan 4, 2009 at 1:13 PM, Otmar Stahl
<O.Stahl at lsw.uni-heidelberg.de> wrote:
> Hello again,
>
> Quoting Alain Spineux <aspineux at gmail.com>:
>
>> On Fri, Jan 2, 2009 at 1:56 PM, Otmar Stahl
>> <O.Stahl at lsw.uni-heidelberg.de> wrote:
>>> Hello,
>>>
>>> Thank you for the mail.
>>>
>>> Alain Spineux wrote:
>>>>
>>>> On Thu, Jan 1, 2009 at 10:18 AM, Otmar Stahl
>>>> <O.Stahl at lsw.uni-heidelberg.de> wrote:
>>>>>
>>>>> Hello and happy new year,
>>>>>
>>>>> After an upgrade from kolab 2.1 to 2.2.0 I have a problem with sending
>>>>> mail via ssl from outside the kolab domain. This worked in kolab 2.1.
>>>>>
>>>>> The error message I get with thunderbird is:
>>>>>
>>>>> "An error occured while sending the mail.  The server reponded: 4.3.5
>>>>> Server configuration problem. Please check the message recipients and
>>>>> try again."
>>>>>
>>>>> The corresponding lines in the postfix.log are the following:
>>>>>
>>>>> "Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
>>>>> connect from p5B0770BE.dip.t-dialin.net[91.7.112.190]
>>>>> Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
>>>>> setting up TLS connection from p5B0770BE.dip.t-dialin.net[91.7.112.190]
>>>>> Jan 01 09:55:04 srv0.lsw.uni-heidelberg.de <info> postfix/smtpd[4143]:
>>>>> TLS connection established from
>>>>> p5B0770BE.dip.t-dialin.net[91.7.112.190]: TLSv1 with cipher
>>>>> DHE-RSA-AES256-SHA (256/256 bits)
>>>>> Jan 01 09:55:05 srv0.lsw.uni-heidelberg.de <warning>
>>>>> postfix/spawn[4146]: warning: command /kolab/etc/kolab/kolab_smtpdpolicy
>>>>> exit status 2
>>>>
>>>> Something wrong is happening her, please look into
>>>> /kolab/var/kolab-filter/log/filter.log
>>>> for more error
>>>
>>> Thank you for this hint. Unfortunately, there is absolutely nothing logged
>>> in this file at the corresponding date. The sending attempt seems to die
>>> before it can log anything in filter.log. All I have is the postfix log :-(
>>>
>>> Kind regards,
>>> Otmar
>>>
>>
>> Sorry, The "policy" is a perl script, and log in the syslog, then you
>> should look into your /var/log/messages or /var/log/maillog or ...
>> depending your syslog configuration (the facility is "mail" and
>> priority is "info" )
>>
>> You can increase the verbosity by adding a -v in your master.cf.
>> Dont forget to make the chnage in the template.
>
> Thank you for the hints. I see errors only in postfix.log and adding
> -v to the policy script did not help. However I had a look at the
> policy script and tried to debug it by starting it from hand as
> suggested in the script. I get the following:
>
> -------------------------------------------------------------------------
> root at srv0:~#  su - kolab
> kolab at srv0$  /kolab/etc/kolab/kolab_smtpdpolicy
> IO object version 1.23_01 does not match bootstrap parameter 1.23 at

look like a probleme with perl installation.
Looks like something goes wrong during the upgrade.
Can you check the perl packages ?
Do they match the 2.2 version ?

Hope this help


> /kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 226.
> Compilation failed in require at
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/IO/Handle.pm line 263.
> BEGIN failed--compilation aborted at
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/IO/Handle.pm line 263.
> Compilation failed in require at
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/IO/Socket.pm line 11.
> BEGIN failed--compilation aborted at
> /kolab/lib/perl/vendor_perl/5.10.0/i686-linux/IO/Socket.pm line 11.
> Compilation failed in require at
> /kolab/lib/perl/vendor_perl/5.10.0/Net/LDAP.pm line 8.
> BEGIN failed--compilation aborted at
> /kolab/lib/perl/vendor_perl/5.10.0/Net/LDAP.pm line 8.
> Compilation failed in require at /kolab/etc/kolab/kolab_smtpdpolicy line 26.
> BEGIN failed--compilation aborted at
> /kolab/etc/kolab/kolab_smtpdpolicy line 26.
>
> --------------------------------------------------------------------------
>
> So the script does not start at all and that should be a useful error
> message, but I still do not know what to do about it. Any hints how to
> fix this?
>
> Kind regards,
> Otmar
>
>
> _______________________________________________
> 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 bernhard at intevation.de  Mon Jan  5 09:30:50 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 5 Jan 2009 09:30:50 +0100
Subject: kolab/issue2349 still present on 2.2.1 beta 1
In-Reply-To: <49513CDA.9040300@lascondes.cl>
References: <495112A9.10804@lascondes.cl> <49513CDA.9040300@lascondes.cl>
Message-ID: <200901050930.53940.bernhard@intevation.de>

Roberto,

On Dienstag, 23. Dezember 2008, Roberto de Iriarte wrote:
> I can confirm that the fix described in
> https://www.intevation.de/roundup/kolab/msg16342
> Allows to compile 2.2.1 beta on FreeBSD 7-Stable

thanks for the report, I've added your confirmation to 
kolab/issue2349 (imapd-2.3.11-20080101 fails to compile on FreeBSD)

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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090105/462820f8/attachment.bin

From bernhard.reiter at intevation.de  Mon Jan  5 09:36:54 2009
From: bernhard.reiter at intevation.de (Bernhard Reiter)
Date: Mon, 5 Jan 2009 09:36:54 +0100
Subject: [Kolab-devel] Multiple Kolab's php eat all the RAM
In-Reply-To: <20081227182825.16444p7ni4665b40@webmail.pardus.de>
References: <200812231807.41967.dvadell@linuxclusters.com.ar>
	<200812262113.52165.dvadell@linuxclusters.com.ar>
	<20081227182825.16444p7ni4665b40@webmail.pardus.de>
Message-ID: <200901050936.54654.bernhard.reiter@intevation.de>

On Samstag, 27. Dezember 2008, Gunnar Wrobel wrote:
> Quoting "Diego M. Vadell" <dvadell at linuxclusters.com.ar>:
> > On Wednesday 24 December 2008 04:55:09 Alain Spineux wrote:
> >> On Tue, Dec 23, 2008 at 10:59 PM, Diego M. Vadell
> >>
> >> <dvadell at linuxclusters.com.ar> wrote:

> >> > ? I think I found it: when I send an email to 30 people inside the
> >> > server (locals to the server) I get a lot of kolabmailfilter
> >> > processess. Is it the intended way of doing things?
> >>
> >> Unfortunately yes !

Not really.

The email transport system should be able to transport a single message
to several recipients as one message until the very end.
There have been several difficulties with this, so this ability
might be switched off until they are fixed.

> >> When you send to multiple recipients, one message is "cloned" by
> >> recipients ! This could be avoided by some more coding.
> >> This would reduce the CPU load and could reduce the space in the imap
> >> storage regarding
> >> the "singleinstancestore" in imapd.conf if handled
> >> appropriately.(divided by 3 with my own experience)

I do not recomment singleinstancestore on the imap backend,
as it might complicate backups and restores. Usually using group accounts
for account-less folders you can avoid too much double storage in the common 
cases. 


> > ? I mitigated (or solved?) the issue by editing master.cf.template and
> > changing this line:
> >
> > kolabmailboxfilter ? ? unix ?- ? ? ? n ? ? ? n ? ? ? - ? ? ?- ? ? ? ?pipe
> > user=kolab-n null_sender= argv=/kolab/bin/php
> >
> > to:
> >
> > kolabmailboxfilter ? ? unix ?- ? ? ? n ? ? ? n ? ? ? - ? ? ? 2 ? ? ? pipe
> > user=kolab-n null_sender= argv=/kolab/bin/php
> >
> >
> > Given that amavisd gets only 2 emails at a time, I thought 2 was a good
> > place to start.
>
> I believe that is a sensible safeguard.
>
> @thomas, bernhard: Should we add this as a default?

[the technical solution should be followed up on kolab-devel at .]
It would limit kolabmailboxfilter startup, right?
2 sounds too low to me for the general case.
We should also find out why it takes up so much time to complete
or how much memory is eaten.

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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090105/50279286/attachment.bin

From Roessler at FuH-E.de  Mon Jan  5 10:38:00 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Mon, 05 Jan 2009 10:38:00 +0100
Subject: Address book in Kolab admin webinterface: some entries not shown
In-Reply-To: <495E1810.3010701@FuH-E.de>
References: <495E1810.3010701@FuH-E.de>
Message-ID: <4961D4F8.4090305@FuH-E.de>

Christian R??ler schrieb:

> I have noticed some entries in the Kolab webinterface 
> (https://my_kolabserver/admin/addressbook/) being not shown, e.g. the 
> telephone an fax numbers, but are correctly stored in LDAP (and function 
> perfectly eg. in Kontact). If I change one of these entries in the 
> address book they will be correctly stored in LDAP; but also not shown 
> in the web interface. The same happens when I make a complete, new 
> adress entry using the web interface.

Well, sorry, I forgot to mention version numbers etc.:

It's a kolabd-2.2.0-20080709, compiled from the sources, under openpkg. 
OS: openSUSE 10.3 (i586). Complete versions:

kolab:~ # openpkg rpm -qa|grep kolab
apache-php-5.2.6-20080514_kolab
imapd-2.3.11-20080101_kolab4
kolabconf-2.2.0-20080709
kolabd-2.2.0-20080709
horde-framework-kolab-3.2_rc3-20080405
kolab-filter-2.2.0-20080709
horde-kolab-3.2_rc3-20080707
horde-turba-kolab-2.2_rc3-20080710
horde-nag-kolab-2.2_rc2-20080710
horde-kolab-client-0.99-20080405
postfix-2.4.6-20080101_kolab
php-5.2.6-20080514_kolab
perl-kolab-2.2.0-20080709
php-kolab-2.2.0-20080711
kolab-freebusy-2.2.0-20080709
kolab-webadmin-2.2.0-20080709
horde-kronolith-kolab-2.2_rc2-20080710
horde-mnemo-kolab-2.2_rc2-20080710
horde-passwd-kolab-3.0.1-20080710
horde-imp-kolab-4.2_rc3-20080710
horde-ingo-kolab-1.2_rc2-20080710

Best regards, Christian


From aspineux at gmail.com  Mon Jan  5 11:06:22 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 5 Jan 2009 11:06:22 +0100
Subject: [Kolab-devel] Multiple Kolab's php eat all the RAM
In-Reply-To: <200901050936.54654.bernhard.reiter@intevation.de>
References: <200812231807.41967.dvadell@linuxclusters.com.ar>
	<200812262113.52165.dvadell@linuxclusters.com.ar>
	<20081227182825.16444p7ni4665b40@webmail.pardus.de>
	<200901050936.54654.bernhard.reiter@intevation.de>
Message-ID: <71fe4e760901050206h7d4052e5w678ef79e951b0dee@mail.gmail.com>

On Mon, Jan 5, 2009 at 9:36 AM, Bernhard Reiter
<bernhard.reiter at intevation.de> wrote:
> On Samstag, 27. Dezember 2008, Gunnar Wrobel wrote:
>> Quoting "Diego M. Vadell" <dvadell at linuxclusters.com.ar>:
>> > On Wednesday 24 December 2008 04:55:09 Alain Spineux wrote:
>> >> On Tue, Dec 23, 2008 at 10:59 PM, Diego M. Vadell
>> >>
>> >> <dvadell at linuxclusters.com.ar> wrote:
>
>> >> >   I think I found it: when I send an email to 30 people inside the
>> >> > server (locals to the server) I get a lot of kolabmailfilter
>> >> > processess. Is it the intended way of doing things?
>> >>
>> >> Unfortunately yes !
>
> Not really.
>
> The email transport system should be able to transport a single message
> to several recipients as one message until the very end.
> There have been several difficulties with this, so this ability
> might be switched off until they are fixed.

And the "end" allso can keep the email alone.
This require some more LDAP queries inside the filter :-)

>
>> >> When you send to multiple recipients, one message is "cloned" by
>> >> recipients ! This could be avoided by some more coding.
>> >> This would reduce the CPU load and could reduce the space in the imap
>> >> storage regarding
>> >> the "singleinstancestore" in imapd.conf if handled
>> >> appropriately.(divided by 3 with my own experience)
>
> I do not recomment singleinstancestore on the imap backend,
> as it might complicate backups and restores. Usually using group accounts
> for account-less folders you can avoid too much double storage in the common
> cases.

This doesn't "complicate" the backup nor the restore,  except if you
want to keep this advantage during the backup and after the restore.

This reduce by 3 the space for my hosted domains.

This also require to use the good switch when using "du" :-)

>
>
>> >   I mitigated (or solved?) the issue by editing master.cf.template and
>> > changing this line:
>> >
>> > kolabmailboxfilter     unix  -       n       n       -      -        pipe
>> > user=kolab-n null_sender= argv=/kolab/bin/php
>> >
>> > to:
>> >
>> > kolabmailboxfilter     unix  -       n       n       -       2       pipe
>> > user=kolab-n null_sender= argv=/kolab/bin/php
>> >
>> >
>> > Given that amavisd gets only 2 emails at a time, I thought 2 was a good
>> > place to start.
>>
>> I believe that is a sensible safeguard.
>>
>> @thomas, bernhard: Should we add this as a default?
>
> [the technical solution should be followed up on kolab-devel at .]
> It would limit kolabmailboxfilter startup, right?
> 2 sounds too low to me for the general case.
> We should also find out why it takes up so much time to complete
> or how much memory is eaten.
>
> 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-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



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


From bernhard at intevation.de  Mon Jan  5 12:19:41 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 5 Jan 2009 12:19:41 +0100
Subject: Address book in Kolab admin webinterface: some entries not shown
In-Reply-To: <4961D4F8.4090305@FuH-E.de>
References: <495E1810.3010701@FuH-E.de> <4961D4F8.4090305@FuH-E.de>
Message-ID: <200901051219.41851.bernhard@intevation.de>

On Montag, 5. Januar 2009, Christian R??ler wrote:
> Christian R??ler schrieb:
> > I have noticed some entries in the Kolab webinterface
> > (https://my_kolabserver/admin/addressbook/) being not shown, e.g. the
> > telephone an fax numbers, but are correctly stored in LDAP (and function
> > perfectly eg. in Kontact). If I change one of these entries in the
> > address book they will be correctly stored in LDAP; but also not shown
> > in the web interface. The same happens when I make a complete, new
> > adress entry using the web interface.
>
> Well, sorry, I forgot to mention version numbers etc.:
>
> It's a kolabd-2.2.0-20080709, compiled from the sources, under openpkg.
> OS: openSUSE 10.3 (i586).

I've done a test with Kolab Server/OpenPKG 2.2-rc3 and 2.2.0
and could create and change entries with all settings, 
so fax number and room number and so on were displayed and changed correctly 
afterwards.

How did you fill the external tree?
Maybe there is some missmatch?
If you appen to have a staging system with the same system,
could you create a new LDAP addressbook entry and see if you get the same 
problem, if not, could you create the entries?

-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090105/7f6b7162/attachment.bin

From bernhard at intevation.de  Mon Jan  5 12:26:17 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 5 Jan 2009 12:26:17 +0100
Subject: export/import annotations.db
In-Reply-To: <71fe4e760812280525v14ed6591wccead6821e77c7c3@mail.gmail.com>
References: <002215046c8bb0eedb045f09edff@google.com>
	<71fe4e760812280525v14ed6591wccead6821e77c7c3@mail.gmail.com>
Message-ID: <200901051226.17662.bernhard@intevation.de>

On Sonntag, 28. Dezember 2008, Alain Spineux wrote:
> On Sat, Dec 27, 2008 at 5:42 PM, ?<Lucidblue0 at gmail.com> wrote:
> > Thanks, I'll look into this on monday or sooner if I get the chance. It
> > looks as if the backup/restore snippet is converting the annotations.db
> > to skiplist and then back again?
>
> Yes that's right. "flat" format could do the trick too (I suppose)

Note that the flat format had some significant drawbacks
I think it cannot deal with null byte entries or something like this.
(I did not recheck this for a while, see my surprise in
http://markmail.org/message/5rmjiaatmdw2l4rj )

-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090105/5e81f4b8/attachment.bin

From bernhard at intevation.de  Mon Jan  5 12:30:30 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 5 Jan 2009 12:30:30 +0100
Subject: user creation and deletion problems (was: Kolab-users Digest, Vol 58,
	Issue 18)
In-Reply-To: <BLU122-W13DDF2819317C4DED3A559A3E70@phx.gbl>
References: <mailman.3857.1229641475.2135.kolab-users@kolab.org>
	<BLU122-W13DDF2819317C4DED3A559A3E70@phx.gbl>
Message-ID: <200901051230.30904.bernhard@intevation.de>

On Dienstag, 30. Dezember 2008, kiser Caesar wrote:
> Since recently, I am having a weird problem. When I create a new user via
> the web GIU, kolab reports that the operation is successfull but it doesn't
> create a mailbox for the new user. When I try to delete the newly created
> user the the process hags showing "User Deleted, awaiting cleanup..." in
> the web interface. If I try to create an imap folder manually via cyradm
> it's working. Trying to delete the same folder via the kolab GUI still
> fails. So for some reason kolab is not able to perform any disk related
> operations. The permitions for /kolab/var/imapd/spool/domain/****/user/
> looks right. Any ideas?

Check
http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_Web_admin#After_deleting_an_user_the_message_User_deleted.2C_awaiting_cleanup_does_not_vanish

-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090105/627311df/attachment.bin

From Roessler at FuH-E.de  Mon Jan  5 15:52:19 2009
From: Roessler at FuH-E.de (=?ISO-8859-15?Q?Christian_R=F6=DFler?=)
Date: Mon, 05 Jan 2009 15:52:19 +0100
Subject: Address book in Kolab admin webinterface: some entries not shown
In-Reply-To: <200901051219.41851.bernhard@intevation.de>
References: <495E1810.3010701@FuH-E.de> <4961D4F8.4090305@FuH-E.de>
	<200901051219.41851.bernhard@intevation.de>
Message-ID: <49621EA3.3050805@FuH-E.de>

Bernhard Reiter schrieb:

> On Montag, 5. Januar 2009, Christian R??ler wrote:
>> Christian R??ler schrieb:
>>> I have noticed some entries in the Kolab webinterface
>>> (https://my_kolabserver/admin/addressbook/) being not shown, e.g. the
>>> telephone an fax numbers, but are correctly stored in LDAP (and function
>>> perfectly eg. in Kontact).
>> Well, sorry, I forgot to mention version numbers etc.:
>> It's a kolabd-2.2.0-20080709, compiled from the sources, under openpkg.
>> OS: openSUSE 10.3 (i586).
> I've done a test with Kolab Server/OpenPKG 2.2-rc3 and 2.2.0
> and could create and change entries with all settings, 
> so fax number and room number and so on were displayed and changed correctly 
> afterwards.

This behaviour I also remember, of course...

> How did you fill the external tree?

I generated ldif's by bash script, and inserted them per ldapadd.

> Maybe there is some missmatch?

Perhaps. I have deleted all entries under cn=external,... and used my 
script to generate a test entry. Here's the test ldif:
| dn: cn=testvor testnach,cn=external,dc=kolab,dc=fuhintern,dc=de
| objectClass: top
| objectClass: inetOrgPerson
| objectClass: kolabInetOrgPerson
| sn: testnach
| cn: testvor testnach
| givenName: testvor
| title: testtit
| mail: testtit at kolab.inv
| o: testorg
| ou: testorg-e
| roomNumber: 13
| street: Nirgendsstr. 13
| postOfficeBox: 12345
| postalCode: 79110
| l: Bleiburg
| c: DE
| telephoneNumber: 0761/12345678
| facsimileTelephoneNumber: 0761/87654321

...and this seems pretty standard to me, does it not?

This will be then be shown under 'Adressbuch verwalten', as it should. 
If I click on 'ver?ndern' (change?), I will get this (in php.lpg):
[05-Jan-2009 15:36:30] PHP Notice:  Undefined offset:  1 in 
/kolab/var/kolab/php/admin/include/ldap.class.php on line 370
[05-Jan-2009 15:36:30] PHP Notice:  Undefined offset:  0 in 
/kolab/var/kolab/php/admin/include/ldap.class.php on line 392
[05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  roomnumber in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 37
[05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  roomnumber in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 38
[05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  postofficebox in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 37
[05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  postofficebox in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 38
[05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  postalcode in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 37
[05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  postalcode in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 38
[05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  telephonenumber in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 37
[05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  telephonenumber in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 38
[05-Jan-2009 15:37:22] PHP Notice:  Undefined index: 
facsimiletelephonenumber in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 37
[05-Jan-2009 15:37:22] PHP Notice:  Undefined index: 
facsimiletelephonenumber in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 38
[05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  alias in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 41
[05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  alias in 
/kolab/var/kolab/www/admin/addressbook/addr.php on line 46

Please notice the first two lines with ldap.class.php...

If I, then, delete this entry per frontend, php.log says:
> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  roomnumber in /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  roomnumber in /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  postofficebox in /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  postofficebox in /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  postalcode in /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  postalcode in /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  telephonenumber in /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  telephonenumber in /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  facsimiletelephonenumber in /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  facsimiletelephonenumber in /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  alias in /kolab/var/kolab/www/admin/addressbook/addr.php on line 41
> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  alias in /kolab/var/kolab/www/admin/addressbook/addr.php on line 46
> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  roomnumber in /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  roomnumber in /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  postofficebox in /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  postofficebox in /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  postalcode in /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  postalcode in /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  telephonenumber in /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  telephonenumber in /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  facsimiletelephonenumber in /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  facsimiletelephonenumber in /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  alias in /kolab/var/kolab/www/admin/addressbook/addr.php on line 41
> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  alias in /kolab/var/kolab/www/admin/addressbook/addr.php on line 46
> [05-Jan-2009 15:40:43] PHP Notice:  Undefined variable: content in /kolab/var/kolab/www/admin/addressbook/addr.php on line 337

... and the entry stays, with "Eintrag gel?scht, warte auf 
Aufr?umaktion..." as long as I like. It inserts the
kolabDeleteflag: kolab.kolabserver-fqdn as it should. If I 'kill' the 
entry per ldapdelete (by hand) it vanishes, of course. kolabd etc. is 
running, by the way; ldap-slave also.

> If you appen to have a staging system with the same system,
> could you create a new LDAP addressbook entry and see if you get the same 
> problem, if not, could you create the entries?

Well, this one is the staging system, so to say:). If I create
exactly the same entry by web frontend, everything goes perfectly 'into' 
the LDAP, but all the other symptoms are the same.

Please let me know if I should give more info; I would gladly do so.

Thanks, and my best regards,
Christian


From s.kim at hia.rwth-aachen.de  Mon Jan  5 16:35:13 2009
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Mon, 05 Jan 2009 16:35:13 +0100
Subject: Update of event leads to doubled event
Message-ID: <496228B1.5000901@hia.rwth-aachen.de>

Hello,

new year new problems ;-)

One of my users has a problem with events that are doubled when updated 
-but only sporadically. Here is how it happens:

User A creates a new event with User B
User B automatically accepts the event
The event is entered into User B's calendar
User A shifts the event to a later time (overlap/no overlap doesn't make 
a difference)
User B has two events: the original one and a new one with the updated 
time + "updated:" in the event name

I checked the kolab-filter.log  and found several php error messages like:
Jan 05 11:31:40 Kolab Filter [error] [horde] PHP Error: Undefined 
index:  CN <ID: <alphanumericnumbers at computername>> [pid 10248 on line 
861 of "/ko
lab/lib/php/Kolab/Filter/Resource.php"]

Jan 05 11:31:51 Kolab Filter [error] [horde] PHP Error: Undefined 
index:  X-UID <ID: <alphanumericnumbers at computername>> [pid 9967 on line 
1342 of "
/kolab/lib/php/Kolab/Filter/Resource.php"]

Jan 05 11:31:51 Kolab Filter [error] [horde] PHP Error: Undefined 
index:  X-SID <ID: <alphanumericnumbers at computername>> [pid 9967 on line 
1342 of "
/kolab/lib/php/Kolab/Filter/Resource.php"]


Has anyone a hint on why the existing event is not detected?

Best regards,
Saim

-- 
--------------------------------------------------------------------------
Dipl.-Ing. Saim Kim
Lehrstuhl fuer Medizinische Informationstechnik
Helmholtz-Institut fuer Biomedizinische Technik
RWTH Aachen
Pauwelsstr. 20, D-52074 Aachen
---
Web:   http://www.medit.hia.rwth-aachen.de/
Tel:   +49-(0)241-80 23218
Fax:   +49-(0)241-80 82442
email: s.kim at hia.rwth-aachen.de
-------------------------------------------------------------------------- 


From bernhard at intevation.de  Tue Jan  6 09:50:57 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 6 Jan 2009 09:50:57 +0100
Subject: Address book in Kolab admin webinterface: some entries not shown
In-Reply-To: <49621EA3.3050805@FuH-E.de>
References: <495E1810.3010701@FuH-E.de>
	<200901051219.41851.bernhard@intevation.de>
	<49621EA3.3050805@FuH-E.de>
Message-ID: <200901060950.57852.bernhard@intevation.de>

On Montag, 5. Januar 2009, Christian R??ler wrote:
> Well, this one is the staging system, so to say:). If I create
> exactly the same entry by web frontend, everything goes perfectly 'into'
> the LDAP, but all the other symptoms are the same.
>
> Please let me know if I should give more info; I would gladly do so.

There must be a difference between a working system and yours.
Best would be if you had a similiar clean system right beside it so 
you can most easily compare.

Next I would probably compare the LDAP schemas to a healthy system.
Then turn on kolabd logging 
next try the debugging mode or openldap
then debug the php code in more detail.

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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090106/5ce378b9/attachment-0001.bin

From bernhard at intevation.de  Tue Jan  6 09:53:02 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 6 Jan 2009 09:53:02 +0100
Subject: Update of event leads to doubled event
In-Reply-To: <496228B1.5000901@hia.rwth-aachen.de>
References: <496228B1.5000901@hia.rwth-aachen.de>
Message-ID: <200901060953.03244.bernhard@intevation.de>

On Montag, 5. Januar 2009, Saim Kim wrote:
> One of my users has a problem with events that are doubled when updated
> -but only sporadically. Here is how it happens:
>
> User A creates a new event with User B
> User B automatically accepts the event
> The event is entered into User B's calendar
> User A shifts the event to a later time (overlap/no overlap doesn't make
> a difference)
> User B has two events: the original one and a new one with the updated
> time + "updated:" in the event name

Please always state server and client versions. :)


-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090106/d9546e50/attachment.bin

From bernhard at intevation.de  Tue Jan  6 09:56:59 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 6 Jan 2009 09:56:59 +0100
Subject: Cannot get freebusy to work in Kontact
In-Reply-To: <200812041111.56971.itsef-admin@brightsight.com>
References: <200810081024.43359.itsef-admin@brightsight.com>
	<200812041111.56971.itsef-admin@brightsight.com>
Message-ID: <200901060956.59612.bernhard@intevation.de>

On Donnerstag, 4. Dezember 2008, ITSEF Admin wrote:
> On Wednesday 8 October 2008 10:24:43 ITSEF Admin wrote:
> > I'm trying to get freebusy to work in my own Kontact (enterprise35) - so
> > far without luck.
>
> No ideas, anyone? I still can't use freebusy. I *think* it might have
> something to do with the interaction Kontact<->kwallet, but that's just a
> hunch. My Kontact simply does not send out the username/password needed to
> retrieve the freebusy information - and it does not ask for one, either, no
> matter what I do... I'll include the original description below for
> completeness.

My next step would be to check for more differences between the working and 
the none-working users.
E.g. kwallet settings or other kde settings.
Do I remember correctly that setting up the non-working users freshly again
with a new .kde will still give them the problems?

> Regards,
>
> Thomas
>
> > Here's what I see so far:
> >  > - We have several users for whom freebusy just works (same Kontact
>
> version
>
> > and no significant differences in korganizerrc, as far as I can see)
> > - For those users, the reqests I can see on the server (apache log)
> > include a login name
> > - If I use a browser to get the freebusy information "manually", I get
> > asked for a username and password. Once I supply them, I get the text.
> > Hence, freebusy does indeed work correctly on the server.
> > - In Settings -> Calendar -> Free/Busy -> Retrieve, I have set username
> > and password - however, none of those seems to get used by my client. The
> > username can be seen in korganizerrc, but it can never be seen in the
> > serverlogs.
> > - Restarting Kontact did not help
> >
> > Basically, it looks like "my" Kontact refuses to send the
> > username/password I have entered when trying to retrieve the freebusy
> > information. Unfortunately, I have absolutely no idea why, especially, as
> > it seems to work for other users with the same Kontact version.
> >
> > I have seen the Wiki article on the topic, but that does not seem to have
> > any clues. BTW: The Wiki article states that the URL for freebusy is
> > supposed to be "https://my-domain.de/freebusy/%EMAIL%.ifb". Is this still
> > correct for enterprise35? I'm asking 'cause all our users with working
> > freebusy have "https://my-domain.de/freebusy/" in there - which is the
> > way kolabwizard sets it.



-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090106/7971f385/attachment.bin

From bernhard at intevation.de  Tue Jan  6 10:06:47 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 6 Jan 2009 10:06:47 +0100
Subject: Duplication of appointments in shared calendar
In-Reply-To: <20081203095903.17115b7id9jg7gcg@webmail.pardus.de>
References: <1228211978l.3344l.2l@pc-adr2.lios-koeln.de>
	<20081203095903.17115b7id9jg7gcg@webmail.pardus.de>
Message-ID: <200901061006.48296.bernhard@intevation.de>

On Mittwoch, 3. Dezember 2008, Gunnar Wrobel wrote:
> > Is this a known problem? ?In Toltec or in Kolab? ?Any idea how I can
> > solve this bug? ?It is somewhat annoying to manually erase the
> > duplicates manually every day...
>
> Kolab itself has no feature that would do automatic writes in a shared ?
> calendar. 

There is the automatic invitation handling that Kolab Server can do,
but you can easily check if the calender user has access to any of these 
folders.

> If Toltec is the *only* client accessing the shared folder ? 
> I'd guess it is causing the problem.

Yes, this is the right conclusion.
There are occasional report for such duplications to happen 
with Toltec and many shared folder, but they are rare meaning
they have not been reproduced.

If you have a way to reliably reproduce, this would be cool.
Two potential causes for dublication are:
a) An old version of Toltec
b) A bad version of Toltec was used at some time, and the .pst 
was not unlinked and relink, which sometimes can help.

Here is a testing script which can help in some situations to 
detect some special duplicates (please only use if you fully understand it)
and assist in removing them.
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/utils/testing/remove_kolab_doubles.py

I also suspect that LDAP- service interruption could cause this condition.
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090106/86fde04b/attachment.bin

From bernhard at intevation.de  Tue Jan  6 10:13:33 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 6 Jan 2009 10:13:33 +0100
Subject: Why the use of SPF pointer is becoming more important
In-Reply-To: <71fe4e760812022052q1436049fgb015e9717f4f766f@mail.gmail.com>
References: <71fe4e760812022052q1436049fgb015e9717f4f766f@mail.gmail.com>
Message-ID: <200901061013.33585.bernhard@intevation.de>

On Mittwoch, 3. Dezember 2008, Alain Spineux wrote:
> Because SPF is used more and more, SPAMMER will become forced to choose
> unprotected SPF domain as sender of their spam!

Good question, I always thought that most of the spam is coming from cracked 
machines and accounts, SPF will not help with these I assume.

> Then the need of a kolab SPF aware will become more and more urgent !

I am not into the topic, but I've seen a lot of contoversy about SPF.
See http://en.wikipedia.org/wiki/Sender_Policy_Framework#Controversy,
the German page seem to have more criticism
http://de.wikipedia.org/wiki/Sender_Policy_Framework#Kritik

-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090106/60adec67/attachment.bin

From s.kim at hia.rwth-aachen.de  Tue Jan  6 13:14:02 2009
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Tue, 06 Jan 2009 13:14:02 +0100
Subject: Update of event leads to doubled event
In-Reply-To: <200901060953.03244.bernhard@intevation.de>
References: <496228B1.5000901@hia.rwth-aachen.de>
	<200901060953.03244.bernhard@intevation.de>
Message-ID: <49634B0A.4080600@hia.rwth-aachen.de>

Bernhard Reiter schrieb:
> On Montag, 5. Januar 2009, Saim Kim wrote:
>   
>> One of my users has a problem with events that are doubled when updated
>> -but only sporadically. Here is how it happens:
>>
>> User A creates a new event with User B
>> User B automatically accepts the event
>> The event is entered into User B's calendar
>> User A shifts the event to a later time (overlap/no overlap doesn't make
>> a difference)
>> User B has two events: the original one and a new one with the updated
>> time + "updated:" in the event name
>>     
>
> Please always state server and client versions. :)
>   
Sorry, my bad!

I'm using the kolab 2.2 release version with Outlook/Toltec Connector 2.3.

Best regards
Saim


>
>   


-- 
--------------------------------------------------------------------------
Dipl.-Ing. Saim Kim
Lehrstuhl fuer Medizinische Informationstechnik
Helmholtz-Institut fuer Biomedizinische Technik
RWTH Aachen
Pauwelsstr. 20, D-52074 Aachen
---
Web:   http://www.medit.hia.rwth-aachen.de/
Tel:   +49-(0)241-80 23218
Fax:   +49-(0)241-80 82442
email: s.kim at hia.rwth-aachen.de
-------------------------------------------------------------------------- 


From aspineux at gmail.com  Wed Jan  7 07:48:46 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Wed, 7 Jan 2009 07:48:46 +0100
Subject: Why the use of SPF pointer is becoming more important
In-Reply-To: <200901061013.33585.bernhard@intevation.de>
References: <71fe4e760812022052q1436049fgb015e9717f4f766f@mail.gmail.com>
	<200901061013.33585.bernhard@intevation.de>
Message-ID: <71fe4e760901062248t29b1cb82y658f142e0df6c221@mail.gmail.com>

On Tue, Jan 6, 2009 at 10:13 AM, Bernhard Reiter <bernhard at intevation.de> wrote:
> On Mittwoch, 3. Dezember 2008, Alain Spineux wrote:
>> Because SPF is used more and more, SPAMMER will become forced to choose
>> unprotected SPF domain as sender of their spam!
>
> Good question, I always thought that most of the spam is coming from cracked
> machines and accounts, SPF will not help with these I assume.

Any email should have a sender even SPAM, SPF allow to check if sender
machine match the sender domain.

>
>> Then the need of a kolab SPF aware will become more and more urgent !
>
> I am not into the topic, but I've seen a lot of contoversy about SPF.
> See http://en.wikipedia.org/wiki/Sender_Policy_Framework#Controversy,

This is not criticism about the SPF efficiency !

Some of the biggest mail provider" have registered SPF pointer :
# for d in hotmail.com gmail.com ; do dig +short $d TXT ; done

And kolab allow (and require !) sender to authenticate to send email !

Then, non of them apply !

> the German page seem to have more criticism
> http://de.wikipedia.org/wiki/Sender_Policy_Framework#Kritik

It looks like !

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



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


From bernhard at intevation.de  Wed Jan  7 12:44:23 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 7 Jan 2009 12:44:23 +0100
Subject: Update of event leads to doubled event
In-Reply-To: <49634B0A.4080600@hia.rwth-aachen.de>
References: <496228B1.5000901@hia.rwth-aachen.de>
	<200901060953.03244.bernhard@intevation.de>
	<49634B0A.4080600@hia.rwth-aachen.de>
Message-ID: <200901071244.24354.bernhard@intevation.de>

Am Dienstag, 6. Januar 2009 13:14:02 schrieb Saim Kim:
> > Please always state server and client versions. :)
> > ?
>
> Sorry, my bad!
>
> I'm using the kolab 2.2 release version with Outlook/Toltec Connector 2.3.

Toltec 2.3.1 is current as far as I know, what does the Toltec support say
to your problems?

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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090107/a4d592bd/attachment.bin

From wrobel at pardus.de  Wed Jan  7 13:21:11 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 07 Jan 2009 13:21:11 +0100
Subject: Update of event leads to doubled event
In-Reply-To: <49634B0A.4080600@hia.rwth-aachen.de>
References: <496228B1.5000901@hia.rwth-aachen.de>
	<200901060953.03244.bernhard@intevation.de>
	<49634B0A.4080600@hia.rwth-aachen.de>
Message-ID: <20090107132111.7035155tbec6zlmo@webmail.pardus.de>

Quoting Saim Kim <s.kim at hia.rwth-aachen.de>:

> Bernhard Reiter schrieb:
>> On Montag, 5. Januar 2009, Saim Kim wrote:
>>
>>> One of my users has a problem with events that are doubled when updated
>>> -but only sporadically. Here is how it happens:
>>>
>>> User A creates a new event with User B
>>> User B automatically accepts the event
>>> The event is entered into User B's calendar
>>> User A shifts the event to a later time (overlap/no overlap doesn't make
>>> a difference)
>>> User B has two events: the original one and a new one with the updated
>>> time + "updated:" in the event name
>>>
>>
>> Please always state server and client versions. :)
>>
> Sorry, my bad!
>
> I'm using the kolab 2.2 release version with Outlook/Toltec Connector 2.3.

Is it possible to test this with the code in the newer beta release?  
The error you mentioned should have been fixed there.

Cheers,

Gunnar

>
> Best regards
> Saim
>
>
>>
>>
>
>
> --
> --------------------------------------------------------------------------
> Dipl.-Ing. Saim Kim
> Lehrstuhl fuer Medizinische Informationstechnik
> Helmholtz-Institut fuer Biomedizinische Technik
> RWTH Aachen
> Pauwelsstr. 20, D-52074 Aachen
> ---
> Web:   http://www.medit.hia.rwth-aachen.de/
> Tel:   +49-(0)241-80 23218
> Fax:   +49-(0)241-80 82442
> email: s.kim at hia.rwth-aachen.de
> --------------------------------------------------------------------------
>
> _______________________________________________
> 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/20090107/0ebef04b/attachment.bin

From wrobel at pardus.de  Wed Jan  7 21:21:54 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 07 Jan 2009 21:21:54 +0100
Subject: kolab user for samba access
In-Reply-To: <d53357b70812311050o10128ce9g749fdd6d1ce1787f@mail.gmail.com>
References: <d53357b70812111228v494cff2aua40f7d3420e0677d@mail.gmail.com>
	<1229068001l.6902l.0l@pc-adr2.lios-koeln.de> <4945663C.40501@gmail.com>
	<d53357b70812142354y62dafb05yfa4839fcca8a6f27@mail.gmail.com>
	<d53357b70812300611v5edd751cj8d926326e1bc83aa@mail.gmail.com>
	<d53357b70812300807y4a8740dhd084c00b2d1a6c88@mail.gmail.com>
	<d53357b70812310933i20411ef7t8138768e48b25b25@mail.gmail.com>
	<d53357b70812311050o10128ce9g749fdd6d1ce1787f@mail.gmail.com>
Message-ID: <20090107212154.13246ifi9j4tsw84@webmail.pardus.de>

Quoting Antonio Straziota <devgioiatech at gmail.com>:

> hi again :)
>
> my problem now is in user.php...
> when i try to create a user (or modify existing one) i got an empty page...

Then you should find an error in your PHP log. That should help to debug it.

Cheers,

Gunnar

>
> thanks for the help and again HAPPY NEW YEAR.
>
> 2008/12/31 Antonio Straziota <devgioiatech at gmail.com>:
>> i've solved.
>> the problem was in smbldap_bind.conf
>>
>> i had
>> masterDN="cn=internal,cn=manager,dc=demo,dc=tst"
>>
>> instead of
>>
>> masterDN="cn=manager,cn=internal,dc=demo,dc=tst"
>>
>> bye!
>>
>> Happy new year! ;)
>>
>>
>>
>> 2008/12/30 Antonio Straziota <devgioiatech at gmail.com>:
>>> another issue:
>>> when i check smbd and nmbd status i get:
>>>
>>> smbd dead but pid file exists
>>> nmbd dead but pid file exists
>>>
>>>
>>> Do you know why?
>>> Thanks.
>>>
>>> 2008/12/30 Antonio Straziota <devgioiatech at gmail.com>:
>>>> Hi all,
>>>> i tried the solution proposed...
>>>>
>>>> I tried it on a single machine and the process goes forward without
>>>> any problem, but when i try it on two different server i've the
>>>> following error on
>>>>
>>>> # smbldap-populate -b guest -l 65534 -a myadmin
>>>>
>>>> on the samba server.
>>>>
>>>> It returns:
>>>>
>>>> Populating LDAP directory for domain DEMO-TST
>>>> (S-1-5-21-3554714494-4109302710-169134865)
>>>> (using builtin directory structure)
>>>>
>>>> Use of uninitialized value in concatenation (.) or string at
>>>> /usr/local/sbin/smbldap-populate line 173.
>>>> adding new entry: cn=internal,dc=demo,dc=tst
>>>> failed to add entry: objectclass: value #0 invalid per syntax at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 2.
>>>> entry dc=demo,dc=tst already exist.
>>>> adding new entry: ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>> failed to add entry: modifications require authentication at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 4.
>>>> adding new entry: ou=SmbComputers,cn=internal,dc=demo,dc=tst
>>>> failed to add entry: modifications require authentication at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 5.
>>>> adding new entry: ou=SmbIdmap,cn=internal,dc=demo,dc=tst
>>>> failed to add entry: modifications require authentication at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 6.
>>>> adding new entry: uid=myadmin,dc=demo,dc=tst
>>>> failed to add entry: modifications require authentication at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 7.
>>>> adding new entry: uid=guest,dc=demo,dc=tst
>>>> failed to add entry: modifications require authentication at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 8.
>>>> adding new entry: cn=Domain Admins,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>> failed to add entry: modifications require authentication at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 9.
>>>> adding new entry: cn=Domain Users,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>> failed to add entry: modifications require authentication at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 10.
>>>> adding new entry: cn=Domain Guests,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>> failed to add entry: modifications require authentication at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 11.
>>>> adding new entry: cn=Domain  
>>>> Computers,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>> failed to add entry: modifications require authentication at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 12.
>>>> adding new entry:  
>>>> cn=Administrators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>> failed to add entry: modifications require authentication at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 16.
>>>> adding new entry: cn=Account  
>>>> Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>> failed to add entry: modifications require authentication at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 18.
>>>> adding new entry: cn=Print  
>>>> Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>> failed to add entry: modifications require authentication at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 19.
>>>> adding new entry: cn=Backup  
>>>> Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>> failed to add entry: modifications require authentication at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 20.
>>>> adding new entry: cn=Replicators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>> failed to add entry: modifications require authentication at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 21.
>>>> adding new entry: sambaDomainName=DEMO-TST,cn=internal,dc=demo,dc=tst
>>>> failed to add entry: modifications require authentication at
>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 21.
>>>>
>>>> Please provide a password for the domain myadmin:
>>>> /usr/local/sbin/smbldap-passwd: user myadmin doesn't exist
>>>>
>>>> I use same user myadmin as administrator.
>>>>
>>>> Any idea?
>>>>
>>>> 2008/12/15 Antonio Straziota <devgioiatech at gmail.com>:
>>>>> I'm going to try it... ;)
>>>>>
>>>>> thanks to all for the link... i was searching for samba-openldap and i
>>>>> haven't found this tutorial.
>>>>> I'll give you a feedback asap.
>>>>>
>>>>> bye.
>>>>>
>>>>>
>>>>> 2008/12/14 schmerold1 at gmail.com <schmerold1 at gmail.com>:
>>>>>> Any feedback regarding following the Ubuntu directions on a Centos 5.2
>>>>>> box are appreciated.
>>>>>>
>>>>>> Ubuntu directions:
>>>>>> http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy
>>>>>>
>>>>>>
>>>>>> Albrecht Dre? wrote:
>>>>>>> Am 11.12.2008 21:28:50 schrieb(en) Antonio Straziota:
>>>>>>>
>>>>>>>> i need to make kolab user capable to access samba shares. I'm trying
>>>>>>>> to authenticate samba user against kolab openldap following some
>>>>>>>> tutorial found on the web, but any attempt fails.
>>>>>>>>
>>>>>>>
>>>>>>> Did you try
>>>>>>> <http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy>?
>>>>>>> Works nicely for me...
>>>>>>>
>>>>>>> Hth,
>>>>>>> Albrecht.
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>



-- 
______ 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/20090107/7e2d70e7/attachment.bin

From wrobel at pardus.de  Wed Jan  7 23:37:08 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 07 Jan 2009 23:37:08 +0100
Subject: Address book in Kolab admin webinterface: some entries not shown
In-Reply-To: <49621EA3.3050805@FuH-E.de>
References: <495E1810.3010701@FuH-E.de> <4961D4F8.4090305@FuH-E.de>
	<200901051219.41851.bernhard@intevation.de> <49621EA3.3050805@FuH-E.de>
Message-ID: <20090107233708.79814unk1oe386m8@webmail.pardus.de>

Quoting Christian R??ler <Roessler at FuH-E.de>:

> Bernhard Reiter schrieb:
>
>> On Montag, 5. Januar 2009, Christian R??ler wrote:
>>> Christian R??ler schrieb:
>>>> I have noticed some entries in the Kolab webinterface
>>>> (https://my_kolabserver/admin/addressbook/) being not shown, e.g. the
>>>> telephone an fax numbers, but are correctly stored in LDAP (and function
>>>> perfectly eg. in Kontact).
>>> Well, sorry, I forgot to mention version numbers etc.:
>>> It's a kolabd-2.2.0-20080709, compiled from the sources, under openpkg.
>>> OS: openSUSE 10.3 (i586).
>> I've done a test with Kolab Server/OpenPKG 2.2-rc3 and 2.2.0
>> and could create and change entries with all settings,
>> so fax number and room number and so on were displayed and changed correctly
>> afterwards.
>
> This behaviour I also remember, of course...
>
>> How did you fill the external tree?
>
> I generated ldif's by bash script, and inserted them per ldapadd.
>
>> Maybe there is some missmatch?
>
> Perhaps. I have deleted all entries under cn=external,... and used my
> script to generate a test entry. Here's the test ldif:
> | dn: cn=testvor testnach,cn=external,dc=kolab,dc=fuhintern,dc=de
> | objectClass: top
> | objectClass: inetOrgPerson
> | objectClass: kolabInetOrgPerson
> | sn: testnach
> | cn: testvor testnach
> | givenName: testvor
> | title: testtit
> | mail: testtit at kolab.inv
> | o: testorg
> | ou: testorg-e
> | roomNumber: 13
> | street: Nirgendsstr. 13
> | postOfficeBox: 12345
> | postalCode: 79110
> | l: Bleiburg
> | c: DE
> | telephoneNumber: 0761/12345678
> | facsimileTelephoneNumber: 0761/87654321
>
> ...and this seems pretty standard to me, does it not?

It might be that the "/" is not allowed. Can you test that?

Cheers,

Gunnar

>
> This will be then be shown under 'Adressbuch verwalten', as it should.
> If I click on 'ver?ndern' (change?), I will get this (in php.lpg):
> [05-Jan-2009 15:36:30] PHP Notice:  Undefined offset:  1 in
> /kolab/var/kolab/php/admin/include/ldap.class.php on line 370
> [05-Jan-2009 15:36:30] PHP Notice:  Undefined offset:  0 in
> /kolab/var/kolab/php/admin/include/ldap.class.php on line 392
> [05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  roomnumber in
> /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
> [05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  roomnumber in
> /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
> [05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  postofficebox in
> /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
> [05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  postofficebox in
> /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
> [05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  postalcode in
> /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
> [05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  postalcode in
> /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
> [05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  telephonenumber in
> /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
> [05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  telephonenumber in
> /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
> [05-Jan-2009 15:37:22] PHP Notice:  Undefined index:
> facsimiletelephonenumber in
> /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
> [05-Jan-2009 15:37:22] PHP Notice:  Undefined index:
> facsimiletelephonenumber in
> /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
> [05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  alias in
> /kolab/var/kolab/www/admin/addressbook/addr.php on line 41
> [05-Jan-2009 15:37:22] PHP Notice:  Undefined index:  alias in
> /kolab/var/kolab/www/admin/addressbook/addr.php on line 46
>
> Please notice the first two lines with ldap.class.php...
>
> If I, then, delete this entry per frontend, php.log says:
>> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  roomnumber in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
>> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  roomnumber in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
>> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  postofficebox  
>> in /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
>> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  postofficebox  
>> in /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
>> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  postalcode in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
>> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  postalcode in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
>> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:   
>> telephonenumber in /kolab/var/kolab/www/admin/addressbook/addr.php  
>> on line 37
>> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:   
>> telephonenumber in /kolab/var/kolab/www/admin/addressbook/addr.php  
>> on line 38
>> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:   
>> facsimiletelephonenumber in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
>> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:   
>> facsimiletelephonenumber in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
>> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  alias in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 41
>> [05-Jan-2009 15:39:12] PHP Notice:  Undefined index:  alias in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 46
>> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  roomnumber in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
>> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  roomnumber in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
>> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  postofficebox  
>> in /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
>> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  postofficebox  
>> in /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
>> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  postalcode in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
>> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  postalcode in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
>> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:   
>> telephonenumber in /kolab/var/kolab/www/admin/addressbook/addr.php  
>> on line 37
>> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:   
>> telephonenumber in /kolab/var/kolab/www/admin/addressbook/addr.php  
>> on line 38
>> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:   
>> facsimiletelephonenumber in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 37
>> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:   
>> facsimiletelephonenumber in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 38
>> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  alias in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 41
>> [05-Jan-2009 15:40:41] PHP Notice:  Undefined index:  alias in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 46
>> [05-Jan-2009 15:40:43] PHP Notice:  Undefined variable: content in  
>> /kolab/var/kolab/www/admin/addressbook/addr.php on line 337
>
> ... and the entry stays, with "Eintrag gel?scht, warte auf
> Aufr?umaktion..." as long as I like. It inserts the
> kolabDeleteflag: kolab.kolabserver-fqdn as it should. If I 'kill' the
> entry per ldapdelete (by hand) it vanishes, of course. kolabd etc. is
> running, by the way; ldap-slave also.
>
>> If you appen to have a staging system with the same system,
>> could you create a new LDAP addressbook entry and see if you get the same
>> problem, if not, could you create the entries?
>
> Well, this one is the staging system, so to say:). If I create
> exactly the same entry by web frontend, everything goes perfectly 'into'
> the LDAP, but all the other symptoms are the same.
>
> Please let me know if I should give more info; I would gladly do so.
>
> Thanks, and my best regards,
> Christian
>
> _______________________________________________
> 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/20090107/9e57e8b5/attachment-0001.bin

From info at erler-familie.de  Thu Jan  8 09:56:52 2009
From: info at erler-familie.de (Benjamin Erler)
Date: Thu, 08 Jan 2009 09:56:52 +0100
Subject: kolabquotawarn[NUMBER]: fatal: Can't read configuration, please make
	sure that kolabquotawarn runs with sufficient privileges
In-Reply-To: <mailman.22.1231403850.2112.kolab-users@kolab.org>
References: <mailman.22.1231403850.2112.kolab-users@kolab.org>
Message-ID: <4965BFD4.7050401@erler-familie.de>

Hallo,

I can't send and recive Mails. So I watched the /var/log/mail.log and
get this Message:

kolabquotawarn[10009]: fatal: Can't read configuration, please make sure
that kolabquotawarn runs with sufficient privileges

(The number 10009 is an example; there are many of that messages and
they all have different numbers)

My OS is a debian etch vserver under linux vServer

cat /proc/version says that:
Linux version 2.6.22.19-vs2.2.0.7 (root at hn2.weccos.de) (gcc version
4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Sun Dec 21
15:54:45 CET 2008

special is: I have no Loopback Davice - maybe that couse the problem?

I can't use quota on thes vserver, because I have no access on devices.
So maybe it's possible to deaktivate quota for kolab - maybe thats the
problem. But how can I do that?

My kolab versions (output from Kolab web interface > About Kolab >
Versions):
------------------------------------------------
Kolab2 Groupware Server Version

2.2.0

Kolab2 Groupware Server Component Versions

amavisd: 2.5.3-20080101
apache: 2.2.8-20080118
clamav: 0.93.3-20080708
imapd: 2.3.11-20080101_kolab4
kolab-filter: 2.2.0-20080709
kolab-freebusy: 2.2.0-20080709
kolab-webadmin: 2.2.0-20080709
kolabconf: 2.2.0-20080709
kolabd: 2.2.0-20080709
openldap: 2.3.41-20080424
perl-kolab: 2.2.0-20080709
php-kolab: 2.2.0-20080711
postfix: 2.4.6-20080101_kolab
spamassassin: 3.2.4-20080107

PEAR/Horde Versions

PEAR-Auth_SASL: 1.0.2-1
PEAR-Date: 1.4.7-1
PEAR-HTTP_Request: 1.4.1-1
PEAR-Log: 1.9.9-1
PEAR-Mail: 1.1.14-1
PEAR-Mail_Mime: 1.3.1-1
PEAR-Net_IMAP: 1.1.0beta1-1
PEAR-Net_LMTP: 1.0.1-1
PEAR-Net_SMTP: 1.2.10-1
PEAR-Net_Sieve: 1.1.5-1
PEAR-Net_Socket: 1.0.6-1
PEAR-Net_URL: 1.0.15-1
fbview-horde: 3.2_rc3-20080605
fbview-kronolith: 2.2_rc2-20080710
horde-framework-kolab: 3.2_rc3-20080405
horde-imp-kolab: 4.2_rc3-20080710
horde-ingo-kolab: 1.2_rc2-20080710
horde-kolab-client: 0.99-20080405
horde-kolab: 3.2_rc3-20080707
horde-kronolith-kolab: 2.2_rc2-20080710
horde-mnemo-kolab: 2.2_rc2-20080710
horde-nag-kolab: 2.2_rc2-20080710
horde-passwd-kolab: 3.0.1-20080710
horde-turba-kolab: 2.2_rc3-20080710
php-channel-horde: 1.0-1

Kolab2 Patched OpenPKG Package Versions

apache-php-5.2.6-20080514_kolab
imapd-2.3.11-20080101_kolab4
postfix-2.4.6-20080101_kolab
php-5.2.6-20080514_kolab

OpenPKG Version

openpkg-20071227-20071227
------------------------------------------------

Sorry for the long quote, thats my first post in that mailinglist and I
don't know what informations are important for help me.


From devgioiatech at gmail.com  Thu Jan  8 11:03:15 2009
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Thu, 8 Jan 2009 11:03:15 +0100
Subject: kolab user for samba access
In-Reply-To: <20090107212154.13246ifi9j4tsw84@webmail.pardus.de>
References: <d53357b70812111228v494cff2aua40f7d3420e0677d@mail.gmail.com>
	<1229068001l.6902l.0l@pc-adr2.lios-koeln.de>
	<4945663C.40501@gmail.com>
	<d53357b70812142354y62dafb05yfa4839fcca8a6f27@mail.gmail.com>
	<d53357b70812300611v5edd751cj8d926326e1bc83aa@mail.gmail.com>
	<d53357b70812300807y4a8740dhd084c00b2d1a6c88@mail.gmail.com>
	<d53357b70812310933i20411ef7t8138768e48b25b25@mail.gmail.com>
	<d53357b70812311050o10128ce9g749fdd6d1ce1787f@mail.gmail.com>
	<20090107212154.13246ifi9j4tsw84@webmail.pardus.de>
Message-ID: <d53357b70901080203l19742323l7bb1b7c3fa4efb17@mail.gmail.com>

i reversed the patch and re-applied it...
now goes fine.

All works perfectly also on CentOS 5.2


thanks.


2009/1/7 Gunnar Wrobel <wrobel at pardus.de>:
> Quoting Antonio Straziota <devgioiatech at gmail.com>:
>
>> hi again :)
>>
>> my problem now is in user.php...
>> when i try to create a user (or modify existing one) i got an empty
>> page...
>
> Then you should find an error in your PHP log. That should help to debug it.
>
> Cheers,
>
> Gunnar
>
>>
>> thanks for the help and again HAPPY NEW YEAR.
>>
>> 2008/12/31 Antonio Straziota <devgioiatech at gmail.com>:
>>>
>>> i've solved.
>>> the problem was in smbldap_bind.conf
>>>
>>> i had
>>> masterDN="cn=internal,cn=manager,dc=demo,dc=tst"
>>>
>>> instead of
>>>
>>> masterDN="cn=manager,cn=internal,dc=demo,dc=tst"
>>>
>>> bye!
>>>
>>> Happy new year! ;)
>>>
>>>
>>>
>>> 2008/12/30 Antonio Straziota <devgioiatech at gmail.com>:
>>>>
>>>> another issue:
>>>> when i check smbd and nmbd status i get:
>>>>
>>>> smbd dead but pid file exists
>>>> nmbd dead but pid file exists
>>>>
>>>>
>>>> Do you know why?
>>>> Thanks.
>>>>
>>>> 2008/12/30 Antonio Straziota <devgioiatech at gmail.com>:
>>>>>
>>>>> Hi all,
>>>>> i tried the solution proposed...
>>>>>
>>>>> I tried it on a single machine and the process goes forward without
>>>>> any problem, but when i try it on two different server i've the
>>>>> following error on
>>>>>
>>>>> # smbldap-populate -b guest -l 65534 -a myadmin
>>>>>
>>>>> on the samba server.
>>>>>
>>>>> It returns:
>>>>>
>>>>> Populating LDAP directory for domain DEMO-TST
>>>>> (S-1-5-21-3554714494-4109302710-169134865)
>>>>> (using builtin directory structure)
>>>>>
>>>>> Use of uninitialized value in concatenation (.) or string at
>>>>> /usr/local/sbin/smbldap-populate line 173.
>>>>> adding new entry: cn=internal,dc=demo,dc=tst
>>>>> failed to add entry: objectclass: value #0 invalid per syntax at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 2.
>>>>> entry dc=demo,dc=tst already exist.
>>>>> adding new entry: ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>>> failed to add entry: modifications require authentication at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 4.
>>>>> adding new entry: ou=SmbComputers,cn=internal,dc=demo,dc=tst
>>>>> failed to add entry: modifications require authentication at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 5.
>>>>> adding new entry: ou=SmbIdmap,cn=internal,dc=demo,dc=tst
>>>>> failed to add entry: modifications require authentication at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 6.
>>>>> adding new entry: uid=myadmin,dc=demo,dc=tst
>>>>> failed to add entry: modifications require authentication at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 7.
>>>>> adding new entry: uid=guest,dc=demo,dc=tst
>>>>> failed to add entry: modifications require authentication at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 8.
>>>>> adding new entry: cn=Domain
>>>>> Admins,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>>> failed to add entry: modifications require authentication at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 9.
>>>>> adding new entry: cn=Domain
>>>>> Users,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>>> failed to add entry: modifications require authentication at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 10.
>>>>> adding new entry: cn=Domain
>>>>> Guests,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>>> failed to add entry: modifications require authentication at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 11.
>>>>> adding new entry: cn=Domain
>>>>> Computers,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>>> failed to add entry: modifications require authentication at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 12.
>>>>> adding new entry:
>>>>> cn=Administrators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>>> failed to add entry: modifications require authentication at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 16.
>>>>> adding new entry: cn=Account
>>>>> Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>>> failed to add entry: modifications require authentication at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 18.
>>>>> adding new entry: cn=Print
>>>>> Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>>> failed to add entry: modifications require authentication at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 19.
>>>>> adding new entry: cn=Backup
>>>>> Operators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>>> failed to add entry: modifications require authentication at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 20.
>>>>> adding new entry:
>>>>> cn=Replicators,ou=SmbGroups,cn=internal,dc=demo,dc=tst
>>>>> failed to add entry: modifications require authentication at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 21.
>>>>> adding new entry: sambaDomainName=DEMO-TST,cn=internal,dc=demo,dc=tst
>>>>> failed to add entry: modifications require authentication at
>>>>> /usr/local/sbin/smbldap-populate line 498, <GEN1> line 21.
>>>>>
>>>>> Please provide a password for the domain myadmin:
>>>>> /usr/local/sbin/smbldap-passwd: user myadmin doesn't exist
>>>>>
>>>>> I use same user myadmin as administrator.
>>>>>
>>>>> Any idea?
>>>>>
>>>>> 2008/12/15 Antonio Straziota <devgioiatech at gmail.com>:
>>>>>>
>>>>>> I'm going to try it... ;)
>>>>>>
>>>>>> thanks to all for the link... i was searching for samba-openldap and i
>>>>>> haven't found this tutorial.
>>>>>> I'll give you a feedback asap.
>>>>>>
>>>>>> bye.
>>>>>>
>>>>>>
>>>>>> 2008/12/14 schmerold1 at gmail.com <schmerold1 at gmail.com>:
>>>>>>>
>>>>>>> Any feedback regarding following the Ubuntu directions on a Centos
>>>>>>> 5.2
>>>>>>> box are appreciated.
>>>>>>>
>>>>>>> Ubuntu directions:
>>>>>>> http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy
>>>>>>>
>>>>>>>
>>>>>>> Albrecht Dre? wrote:
>>>>>>>>
>>>>>>>> Am 11.12.2008 21:28:50 schrieb(en) Antonio Straziota:
>>>>>>>>
>>>>>>>>> i need to make kolab user capable to access samba shares. I'm
>>>>>>>>> trying
>>>>>>>>> to authenticate samba user against kolab openldap following some
>>>>>>>>> tutorial found on the web, but any attempt fails.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Did you try
>>>>>>>>
>>>>>>>> <http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy>?
>>>>>>>> Works nicely for me...
>>>>>>>>
>>>>>>>> Hth,
>>>>>>>> Albrecht.
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>
>
>
>
> --
> ______ 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.
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
>


From marko at mechtron.com.au  Thu Jan  8 12:51:54 2009
From: marko at mechtron.com.au (Mark Berndt)
Date: Thu, 8 Jan 2009 22:51:54 +1100
Subject: kolabquotawarn[NUMBER]: fatal: Can't read configuration,
	please make sure that kolabquotawarn runs with sufficient privileges
In-Reply-To: <4965BFD4.7050401@erler-familie.de>
References: <mailman.22.1231403850.2112.kolab-users@kolab.org>
	<4965BFD4.7050401@erler-familie.de>
Message-ID: <200901082251.54976.marko@mechtron.com.au>

Do you have a crashed kolab running in the background?  This will tie up local 
sockets and lead to kolabquotawarn not being able to run and sticking in 
memory.  

I saw something similar recently, the actual problem was the openldap daemon 
had died.  

hope that helps,

Marko


On Thu, 8 Jan 2009 07:56:52 pm Benjamin Erler wrote:
> Hallo,
>
> I can't send and recive Mails. So I watched the /var/log/mail.log and
> get this Message:
>
> kolabquotawarn[10009]: fatal: Can't read configuration, please make sure
> that kolabquotawarn runs with sufficient privileges
>
> (The number 10009 is an example; there are many of that messages and
> they all have different numbers)
>
> My OS is a debian etch vserver under linux vServer
>
> cat /proc/version says that:
> Linux version 2.6.22.19-vs2.2.0.7 (root at hn2.weccos.de) (gcc version
> 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Sun Dec 21
> 15:54:45 CET 2008
>
> special is: I have no Loopback Davice - maybe that couse the problem?
>
> I can't use quota on thes vserver, because I have no access on devices.
> So maybe it's possible to deaktivate quota for kolab - maybe thats the
> problem. But how can I do that?
>
> My kolab versions (output from Kolab web interface > About Kolab >
> Versions):
> ------------------------------------------------
> Kolab2 Groupware Server Version
>
> 2.2.0
>
> Kolab2 Groupware Server Component Versions
>
> amavisd: 2.5.3-20080101
> apache: 2.2.8-20080118
> clamav: 0.93.3-20080708
> imapd: 2.3.11-20080101_kolab4
> kolab-filter: 2.2.0-20080709
> kolab-freebusy: 2.2.0-20080709
> kolab-webadmin: 2.2.0-20080709
> kolabconf: 2.2.0-20080709
> kolabd: 2.2.0-20080709
> openldap: 2.3.41-20080424
> perl-kolab: 2.2.0-20080709
> php-kolab: 2.2.0-20080711
> postfix: 2.4.6-20080101_kolab
> spamassassin: 3.2.4-20080107
>
> PEAR/Horde Versions
>
> PEAR-Auth_SASL: 1.0.2-1
> PEAR-Date: 1.4.7-1
> PEAR-HTTP_Request: 1.4.1-1
> PEAR-Log: 1.9.9-1
> PEAR-Mail: 1.1.14-1
> PEAR-Mail_Mime: 1.3.1-1
> PEAR-Net_IMAP: 1.1.0beta1-1
> PEAR-Net_LMTP: 1.0.1-1
> PEAR-Net_SMTP: 1.2.10-1
> PEAR-Net_Sieve: 1.1.5-1
> PEAR-Net_Socket: 1.0.6-1
> PEAR-Net_URL: 1.0.15-1
> fbview-horde: 3.2_rc3-20080605
> fbview-kronolith: 2.2_rc2-20080710
> horde-framework-kolab: 3.2_rc3-20080405
> horde-imp-kolab: 4.2_rc3-20080710
> horde-ingo-kolab: 1.2_rc2-20080710
> horde-kolab-client: 0.99-20080405
> horde-kolab: 3.2_rc3-20080707
> horde-kronolith-kolab: 2.2_rc2-20080710
> horde-mnemo-kolab: 2.2_rc2-20080710
> horde-nag-kolab: 2.2_rc2-20080710
> horde-passwd-kolab: 3.0.1-20080710
> horde-turba-kolab: 2.2_rc3-20080710
> php-channel-horde: 1.0-1
>
> Kolab2 Patched OpenPKG Package Versions
>
> apache-php-5.2.6-20080514_kolab
> imapd-2.3.11-20080101_kolab4
> postfix-2.4.6-20080101_kolab
> php-5.2.6-20080514_kolab
>
> OpenPKG Version
>
> openpkg-20071227-20071227
> ------------------------------------------------
>
> Sorry for the long quote, thats my first post in that mailinglist and I
> don't know what informations are important for help me.



-- 
High performance computer, software and automation systems for demanding 
applications
 
Mechtron Systems
ABN: 52 149 788 293
329 Old Canobolas Road NASHDALE NSW 2800
mob 04-2860-1801 ph 02-6365-3568 fx 02-6365-3578 


From info at erler-familie.de  Thu Jan  8 17:40:56 2009
From: info at erler-familie.de (Benjamin Erler)
Date: Thu, 08 Jan 2009 17:40:56 +0100
Subject: install debian package kolabd without libsensors3
Message-ID: <49662C98.9040204@erler-familie.de>

Hallo,

I have a vserver and so I have no access to devices or filesystem. When
I try to install the package kolabd with the command 'aptitude install
kolabd' the package libsensors3 will be installed, too.

But during installation of libsensors3 i get the following Errors:

Setting up libsensors3 (2.10.1-3) ...
mknod: `i2c-0-': Operation not permitted
makedev i2c-0 c 89 0 root root 0600: failed
mknod: `i2c-1-': Operation not permitted
makedev i2c-1 c 89 1 root root 0600: failed
mknod: `i2c-2-': Operation not permitted
makedev i2c-2 c 89 2 root root 0600: failed
mknod: `i2c-3-': Operation not permitted
makedev i2c-3 c 89 3 root root 0600: failed
mknod: `i2c-4-': Operation not permitted
makedev i2c-4 c 89 4 root root 0600: failed
mknod: `i2c-5-': Operation not permitted
makedev i2c-5 c 89 5 root root 0600: failed
mknod: `i2c-6-': Operation not permitted
makedev i2c-6 c 89 6 root root 0600: failed
mknod: `i2c-7-': Operation not permitted
makedev i2c-7 c 89 7 root root 0600: failed

Is it possible to install kolabd without installing libsensors3?

Or is there an alternative to install libsensors3 without makedev commands?

My OS is debian sarge


From wrobel at pardus.de  Fri Jan  9 08:07:48 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Fri, 09 Jan 2009 08:07:48 +0100
Subject: kolabquotawarn[NUMBER]: fatal: Can't read configuration,
	please make sure that kolabquotawarn runs with sufficient privileges
In-Reply-To: <4965BFD4.7050401@erler-familie.de>
References: <mailman.22.1231403850.2112.kolab-users@kolab.org>
	<4965BFD4.7050401@erler-familie.de>
Message-ID: <20090109080748.19711nn0mn337lj4@webmail.pardus.de>

Quoting Benjamin Erler <info at erler-familie.de>:

> Hallo,
>
> I can't send and recive Mails. So I watched the /var/log/mail.log and
> get this Message:
>
> kolabquotawarn[10009]: fatal: Can't read configuration, please make sure
> that kolabquotawarn runs with sufficient privileges
>
> (The number 10009 is an example; there are many of that messages and
> they all have different numbers)

I don't think this specific error is connected to problems with  
sending and receiving mails.

Can you check for any errors in the postfix log  
(/kolab/var/postfix/log/postfix.log)?

Or maybe there are errors in the kolabfilter log  
(/kolab/var/kolabfilter/log/filter.log)?

>
> My OS is a debian etch vserver under linux vServer
>
> cat /proc/version says that:
> Linux version 2.6.22.19-vs2.2.0.7 (root at hn2.weccos.de) (gcc version
> 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Sun Dec 21
> 15:54:45 CET 2008
>
> special is: I have no Loopback Davice - maybe that couse the problem?
>
> I can't use quota on thes vserver, because I have no access on devices.
> So maybe it's possible to deaktivate quota for kolab - maybe thats the
> problem. But how can I do that?

This should not be connected. kolabquotawarn is responsible for Cyrus  
IMAP quotas and these have no connection to filesystem quotas.

Cheers,

Gunnar

>
> My kolab versions (output from Kolab web interface > About Kolab >
> Versions):
> ------------------------------------------------
> Kolab2 Groupware Server Version
>
> 2.2.0
>
> Kolab2 Groupware Server Component Versions
>
> amavisd: 2.5.3-20080101
> apache: 2.2.8-20080118
> clamav: 0.93.3-20080708
> imapd: 2.3.11-20080101_kolab4
> kolab-filter: 2.2.0-20080709
> kolab-freebusy: 2.2.0-20080709
> kolab-webadmin: 2.2.0-20080709
> kolabconf: 2.2.0-20080709
> kolabd: 2.2.0-20080709
> openldap: 2.3.41-20080424
> perl-kolab: 2.2.0-20080709
> php-kolab: 2.2.0-20080711
> postfix: 2.4.6-20080101_kolab
> spamassassin: 3.2.4-20080107
>
> PEAR/Horde Versions
>
> PEAR-Auth_SASL: 1.0.2-1
> PEAR-Date: 1.4.7-1
> PEAR-HTTP_Request: 1.4.1-1
> PEAR-Log: 1.9.9-1
> PEAR-Mail: 1.1.14-1
> PEAR-Mail_Mime: 1.3.1-1
> PEAR-Net_IMAP: 1.1.0beta1-1
> PEAR-Net_LMTP: 1.0.1-1
> PEAR-Net_SMTP: 1.2.10-1
> PEAR-Net_Sieve: 1.1.5-1
> PEAR-Net_Socket: 1.0.6-1
> PEAR-Net_URL: 1.0.15-1
> fbview-horde: 3.2_rc3-20080605
> fbview-kronolith: 2.2_rc2-20080710
> horde-framework-kolab: 3.2_rc3-20080405
> horde-imp-kolab: 4.2_rc3-20080710
> horde-ingo-kolab: 1.2_rc2-20080710
> horde-kolab-client: 0.99-20080405
> horde-kolab: 3.2_rc3-20080707
> horde-kronolith-kolab: 2.2_rc2-20080710
> horde-mnemo-kolab: 2.2_rc2-20080710
> horde-nag-kolab: 2.2_rc2-20080710
> horde-passwd-kolab: 3.0.1-20080710
> horde-turba-kolab: 2.2_rc3-20080710
> php-channel-horde: 1.0-1
>
> Kolab2 Patched OpenPKG Package Versions
>
> apache-php-5.2.6-20080514_kolab
> imapd-2.3.11-20080101_kolab4
> postfix-2.4.6-20080101_kolab
> php-5.2.6-20080514_kolab
>
> OpenPKG Version
>
> openpkg-20071227-20071227
> ------------------------------------------------
>
> Sorry for the long quote, thats my first post in that mailinglist and I
> don't know what informations are important for help me.
>
> _______________________________________________
> 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/20090109/c460df93/attachment.bin

From wrobel at pardus.de  Fri Jan  9 08:28:16 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Fri, 09 Jan 2009 08:28:16 +0100
Subject: kolabquotawarn[NUMBER]: fatal: Can't read configuration,
	please make sure that kolabquotawarn runs with sufficient privileges
In-Reply-To: <20090109080748.19711nn0mn337lj4@webmail.pardus.de>
References: <mailman.22.1231403850.2112.kolab-users@kolab.org>
	<4965BFD4.7050401@erler-familie.de>
	<20090109080748.19711nn0mn337lj4@webmail.pardus.de>
Message-ID: <20090109082816.192478u8id6bu2sk@webmail.pardus.de>

Quoting Gunnar Wrobel <wrobel at pardus.de>:

> Quoting Benjamin Erler <info at erler-familie.de>:
>
>> Hallo,
>>
>> I can't send and recive Mails. So I watched the /var/log/mail.log and
>> get this Message:
>>
>> kolabquotawarn[10009]: fatal: Can't read configuration, please make sure
>> that kolabquotawarn runs with sufficient privileges
>>
>> (The number 10009 is an example; there are many of that messages and
>> they all have different numbers)
>
> I don't think this specific error is connected to problems with   
> sending and receiving mails.
>
> Can you check for any errors in the postfix log   
> (/kolab/var/postfix/log/postfix.log)?
>
> Or maybe there are errors in the kolabfilter log   
> (/kolab/var/kolabfilter/log/filter.log)?

Sorry, I just realized from your other mail that you are using  
Kolab2/Debian. So my answer won't help, sorry.

Cheers,

Gunnar

>
>>
>> My OS is a debian etch vserver under linux vServer
>>
>> cat /proc/version says that:
>> Linux version 2.6.22.19-vs2.2.0.7 (root at hn2.weccos.de) (gcc version
>> 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Sun Dec 21
>> 15:54:45 CET 2008
>>
>> special is: I have no Loopback Davice - maybe that couse the problem?
>>
>> I can't use quota on thes vserver, because I have no access on devices.
>> So maybe it's possible to deaktivate quota for kolab - maybe thats the
>> problem. But how can I do that?
>
> This should not be connected. kolabquotawarn is responsible for  
> Cyrus  IMAP quotas and these have no connection to filesystem quotas.
>
> Cheers,
>
> Gunnar
>
>>
>> My kolab versions (output from Kolab web interface > About Kolab >
>> Versions):
>> ------------------------------------------------
>> Kolab2 Groupware Server Version
>>
>> 2.2.0
>>
>> Kolab2 Groupware Server Component Versions
>>
>> amavisd: 2.5.3-20080101
>> apache: 2.2.8-20080118
>> clamav: 0.93.3-20080708
>> imapd: 2.3.11-20080101_kolab4
>> kolab-filter: 2.2.0-20080709
>> kolab-freebusy: 2.2.0-20080709
>> kolab-webadmin: 2.2.0-20080709
>> kolabconf: 2.2.0-20080709
>> kolabd: 2.2.0-20080709
>> openldap: 2.3.41-20080424
>> perl-kolab: 2.2.0-20080709
>> php-kolab: 2.2.0-20080711
>> postfix: 2.4.6-20080101_kolab
>> spamassassin: 3.2.4-20080107
>>
>> PEAR/Horde Versions
>>
>> PEAR-Auth_SASL: 1.0.2-1
>> PEAR-Date: 1.4.7-1
>> PEAR-HTTP_Request: 1.4.1-1
>> PEAR-Log: 1.9.9-1
>> PEAR-Mail: 1.1.14-1
>> PEAR-Mail_Mime: 1.3.1-1
>> PEAR-Net_IMAP: 1.1.0beta1-1
>> PEAR-Net_LMTP: 1.0.1-1
>> PEAR-Net_SMTP: 1.2.10-1
>> PEAR-Net_Sieve: 1.1.5-1
>> PEAR-Net_Socket: 1.0.6-1
>> PEAR-Net_URL: 1.0.15-1
>> fbview-horde: 3.2_rc3-20080605
>> fbview-kronolith: 2.2_rc2-20080710
>> horde-framework-kolab: 3.2_rc3-20080405
>> horde-imp-kolab: 4.2_rc3-20080710
>> horde-ingo-kolab: 1.2_rc2-20080710
>> horde-kolab-client: 0.99-20080405
>> horde-kolab: 3.2_rc3-20080707
>> horde-kronolith-kolab: 2.2_rc2-20080710
>> horde-mnemo-kolab: 2.2_rc2-20080710
>> horde-nag-kolab: 2.2_rc2-20080710
>> horde-passwd-kolab: 3.0.1-20080710
>> horde-turba-kolab: 2.2_rc3-20080710
>> php-channel-horde: 1.0-1
>>
>> Kolab2 Patched OpenPKG Package Versions
>>
>> apache-php-5.2.6-20080514_kolab
>> imapd-2.3.11-20080101_kolab4
>> postfix-2.4.6-20080101_kolab
>> php-5.2.6-20080514_kolab
>>
>> OpenPKG Version
>>
>> openpkg-20071227-20071227
>> ------------------------------------------------
>>
>> Sorry for the long quote, thats my first post in that mailinglist and I
>> don't know what informations are important for help me.
>>
>> _______________________________________________
>> 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.
>



-- 
______ 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/20090109/23ffad9f/attachment.bin

From wrobel at pardus.de  Fri Jan  9 08:32:08 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Fri, 09 Jan 2009 08:32:08 +0100
Subject: install debian package kolabd without libsensors3
In-Reply-To: <49662C98.9040204@erler-familie.de>
References: <49662C98.9040204@erler-familie.de>
Message-ID: <20090109083208.61667bukqxleslgk@webmail.pardus.de>

Hi Benjamin,

Quoting Benjamin Erler <info at erler-familie.de>:

> Hallo,
>
> I have a vserver and so I have no access to devices or filesystem. When
> I try to install the package kolabd with the command 'aptitude install
> kolabd' the package libsensors3 will be installed, too.

This sounds like a debian problem, not a specific Kolab problem. So  
you will probably have more luck on their mailing lists.

By the way: Kolab2/Debian is a native port of the core Kolab2/OpenPKG  
system. Such native ports have far less stability (as they see less  
testing) than the OpenPKG-based server.

For people that are not an expert in mail server configurations we  
would always recommend to use the OpenPKG-based version as the benefit  
of having a working system is usually higher then the benefit of being  
able to use the system tools of your favourite distribution - and I  
know what I'm speaking of as I maintain the Kolab2/Gentoo port ;).

Cheers,

Gunnar

>
> But during installation of libsensors3 i get the following Errors:
>
> Setting up libsensors3 (2.10.1-3) ...
> mknod: `i2c-0-': Operation not permitted
> makedev i2c-0 c 89 0 root root 0600: failed
> mknod: `i2c-1-': Operation not permitted
> makedev i2c-1 c 89 1 root root 0600: failed
> mknod: `i2c-2-': Operation not permitted
> makedev i2c-2 c 89 2 root root 0600: failed
> mknod: `i2c-3-': Operation not permitted
> makedev i2c-3 c 89 3 root root 0600: failed
> mknod: `i2c-4-': Operation not permitted
> makedev i2c-4 c 89 4 root root 0600: failed
> mknod: `i2c-5-': Operation not permitted
> makedev i2c-5 c 89 5 root root 0600: failed
> mknod: `i2c-6-': Operation not permitted
> makedev i2c-6 c 89 6 root root 0600: failed
> mknod: `i2c-7-': Operation not permitted
> makedev i2c-7 c 89 7 root root 0600: failed
>
> Is it possible to install kolabd without installing libsensors3?
>
> Or is there an alternative to install libsensors3 without makedev commands?
>
> My OS is debian sarge
>
> _______________________________________________
> 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/20090109/44f537f7/attachment-0001.bin

From NPrice at gibb.co.za  Fri Jan  9 09:37:45 2009
From: NPrice at gibb.co.za (Price,Neil)
Date: Fri, 9 Jan 2009 10:37:45 +0200 
Subject: install debian package kolabd without libsensors3
Message-ID: <7B91BBC61758DD1183BE000C296D2CA7104F01@ct-exchange.wins.lawco.com>

On 08 January 2009 06:41 PM Benjamin Erler wrote

> Is it possible to install kolabd without installing libsensors3?
> 
> Or is there an alternative to install libsensors3 without 
> makedev commands?
> 
> My OS is debian sarge
> 
Are you using the Kolab 1.x packaged with Debian Sarge? If so its very old.

Or are you using the packages from Alioth as per
http://wiki.kolab.org/index.php/Debian_-_Administrators_-_Kolab_Installation
?

I'd be very surprised if that works with Sarge. You need to upgrade to Etch
or preferably Lenny.

The Alioth packages are very good (thanks to Mathieu Parent) but if you want
to stay with Sarge you should go with the openpkg version.


From jwhardeman at gmail.com  Sat Jan 10 03:36:50 2009
From: jwhardeman at gmail.com (Joseph Hardeman)
Date: Fri, 09 Jan 2009 21:36:50 -0500
Subject: Question About Kolab and Cyrus Mail Boxes
Message-ID: <496809C2.8080107@gmail.com>

Greetings everyone,

I have just finished setting up my first installation of Kolab and have 
two quick questions.

When I create a user, I do not see a Sent mail folder and a Drafts 
folder.  For instance see my lm after logging into cyradm:

user/testuser/Calendar at farkinga.com (\HasNoChildren)
user/testuser/Contacts at farkinga.com (\HasNoChildren)
user/testuser/Notes at farkinga.com (\HasNoChildren)
user/testuser/Tasks at farkinga.com (\HasNoChildren)
user/testuser at farkinga.com (\HasChildren)


I have been searching through the templates and other files but have not 
been able to find a way to have these folders autogenerated when I add 
an email user.  I can add them afterwards, but I want my users to be 
able to simply login and go.

My second question is, is there a template file where I can add multiple 
certs for my IMAP/POP authentication?  Or can someone send me a quick 
note on where I need to add them?  I want to be able to provide virtual 
domain support and when a user goes to add their mail.domain.com account 
to their client they won't get the wrong cert.

Thanks for everything.

Joseph


From lbf at dragonrising.com  Sun Jan 11 13:56:35 2009
From: lbf at dragonrising.com (Alex)
Date: Sun, 11 Jan 2009 12:56:35 +0000
Subject: Groups for shared folders
Message-ID: <4969EC83.8090201@dragonrising.com>

Hi,

I'm loving kolab, but need a few pointers giving a group of users access 
to a shared folder. I can at the moment give access to everyone, nobody 
or a specific person.

Having searched kolab-users, I've seen a post which seemed to indicate 
the following:

1) Create a new user of account type 'Group Account'

2) Add users to this group account by adding their UID to the 
'Email-Delegates' field of the group account.

3) Create a shared folder, giving the group accounts UID 'post' permissions.

My Mozilla Thunderbird client does not see the new shared folder.

Am I on the right lines here?

Thanks,

Alex Kent


From christian.tardif at servinfo.ca  Sun Jan 11 19:38:50 2009
From: christian.tardif at servinfo.ca (Christian Tardif)
Date: Sun, 11 Jan 2009 13:38:50 -0500
Subject: kolab 2.2.1b1 issue 3331
Message-ID: <496A3CBA.3060004@servinfo.ca>

Hi,

I just installed a new kolab 2.2.1b1, and lost some time to figure out 
why mail was not getting thru. I finally found out the answer to my 
problem on the Internet. The solution is documented in issue 3331 
(kolabfilter uses incorrect delivery backend).

Couldn't it be integrated in the source directly on the server ?   That 
would be very helpful not to have to fix it manually.

Regards,
-- 

*Christian Tardif*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20090111/dcc811a8/attachment.html

From Roessler at FuH-E.de  Mon Jan 12 11:53:34 2009
From: Roessler at FuH-E.de (=?ISO-8859-15?Q?Christian_R=F6=DFler?=)
Date: Mon, 12 Jan 2009 11:53:34 +0100
Subject: Address book in Kolab admin webinterface: some entries not shown
In-Reply-To: <200901060950.57852.bernhard@intevation.de>
References: <495E1810.3010701@FuH-E.de>	<200901051219.41851.bernhard@intevation.de>	<49621EA3.3050805@FuH-E.de>
	<200901060950.57852.bernhard@intevation.de>
Message-ID: <496B212E.4010209@FuH-E.de>

Bernhard Reiter schrieb:

> On Montag, 5. Januar 2009, Christian R??ler wrote:
>> Well, this one is the staging system, so to say:). If I create
>> exactly the same entry by web frontend, everything goes perfectly 'into'
>> the LDAP, but all the other symptoms are the same.
 >
> There must be a difference between a working system and yours.
> Best would be if you had a similiar clean system right beside it so 
> you can most easily compare.

I think you are quite right; I am setting up such a system, and then I 
will compare.

> Next I would probably compare the LDAP schemas to a healthy system.
> Then turn on kolabd logging 
> next try the debugging mode or openldap

Compiling right now; when finished I will try all that. And I will, of 
course, tell then what I find...

 > then debug the php code in more detail.

Ah well, that will be a problem - my php capabilities are quite small. 
But let's see.

Best regards,
Christian


From Roessler at FuH-E.de  Mon Jan 12 11:56:03 2009
From: Roessler at FuH-E.de (=?ISO-8859-15?Q?Christian_R=F6=DFler?=)
Date: Mon, 12 Jan 2009 11:56:03 +0100
Subject: Address book in Kolab admin webinterface: some entries not shown
In-Reply-To: <20090107233708.79814unk1oe386m8@webmail.pardus.de>
References: <495E1810.3010701@FuH-E.de>
	<4961D4F8.4090305@FuH-E.de>	<200901051219.41851.bernhard@intevation.de>
	<49621EA3.3050805@FuH-E.de>
	<20090107233708.79814unk1oe386m8@webmail.pardus.de>
Message-ID: <496B21C3.6010105@FuH-E.de>

Gunnar Wrobel schrieb:

> It might be that the "/" is not allowed. Can you test that?

Tested - that's not the cause, as it seems. As Bernhard mentioned, I 
will now setup a truly fresh Kolab server for comparing purpose.

Best regards,
Christian


From aspineux at gmail.com  Mon Jan 12 12:22:38 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 12 Jan 2009 12:22:38 +0100
Subject: Question About Kolab and Cyrus Mail Boxes
In-Reply-To: <496809C2.8080107@gmail.com>
References: <496809C2.8080107@gmail.com>
Message-ID: <71fe4e760901120322y6f7a53b1u5c1a4fd82314c61a@mail.gmail.com>

On Sat, Jan 10, 2009 at 3:36 AM, Joseph Hardeman <jwhardeman at gmail.com> wrote:
> Greetings everyone,
>
> I have just finished setting up my first installation of Kolab and have
> two quick questions.
>
> When I create a user, I do not see a Sent mail folder and a Drafts
> folder.  For instance see my lm after logging into cyradm:

I think Kolab let the MUA create theses folder itself at first user login,
because Sent, Draft and other are not standard names !
Depending  your Language, the name could change.


>
> user/testuser/Calendar at farkinga.com (\HasNoChildren)
> user/testuser/Contacts at farkinga.com (\HasNoChildren)
> user/testuser/Notes at farkinga.com (\HasNoChildren)
> user/testuser/Tasks at farkinga.com (\HasNoChildren)
> user/testuser at farkinga.com (\HasChildren)
>
>
> I have been searching through the templates and other files but have not
> been able to find a way to have these folders autogenerated when I add
> an email user.  I can add them afterwards, but I want my users to be
> able to simply login and go.

They are already able to simply login and go !

>
> My second question is, is there a template file where I can add multiple
> certs for my IMAP/POP authentication?  Or can someone send me a quick
> note on where I need to add them?  I want to be able to provide virtual
> domain support and when a user goes to add their mail.domain.com account
> to their client they won't get the wrong cert.

You can only attach ONE certificate to an (IP, port) couple !

anyway, you can ave multiple Alternate Name in one certificate.
For example you create a certificate using the

commonName =myserver.name.com

and add 2 alternate names

DNS.1=myserver.name.com   # this is a good idea to have ce commonName
in the list of alternate name
DNS.2=webmail.domain1.com
DNS.3=webmail.domain2.com

But this is mostly true if you generate your certificate yourself, because most
of the cheap certificate provider will not let you add multiple
alternate names !


>
> Thanks for everything.
>
> Joseph
>
> _______________________________________________
> 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 s.kim at hia.rwth-aachen.de  Mon Jan 12 13:08:03 2009
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Mon, 12 Jan 2009 13:08:03 +0100
Subject: Question About Kolab and Cyrus Mail Boxes
In-Reply-To: <496809C2.8080107@gmail.com>
References: <496809C2.8080107@gmail.com>
Message-ID: <496B32A3.1070702@hia.rwth-aachen.de>

Hello Jospeh,

>
> I have been searching through the templates and other files but have 
> not been able to find a way to have these folders autogenerated when I 
> add an email user.  I can add them afterwards, but I want my users to 
> be able to simply login and go.
AFAIK the user has to first log into his own account via a client (e.g. 
Horde) to trigger an automatic generation of the Inbox etc.

Best regards,
Saim

-- 
--------------------------------------------------------------------------
Dipl.-Ing. Saim Kim
Lehrstuhl fuer Medizinische Informationstechnik
Helmholtz-Institut fuer Biomedizinische Technik
RWTH Aachen
Pauwelsstr. 20, D-52074 Aachen
---
Web:   http://www.medit.hia.rwth-aachen.de/
Tel:   +49-(0)241-80 23218
Fax:   +49-(0)241-80 82442
email: s.kim at hia.rwth-aachen.de
-------------------------------------------------------------------------- 


From bernhard at intevation.de  Mon Jan 12 15:28:51 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 12 Jan 2009 15:28:51 +0100
Subject: Question About Kolab and Cyrus Mail Boxes
In-Reply-To: <496B32A3.1070702@hia.rwth-aachen.de>
References: <496809C2.8080107@gmail.com> <496B32A3.1070702@hia.rwth-aachen.de>
Message-ID: <200901121528.54289.bernhard@intevation.de>

On Montag, 12. Januar 2009, Saim Kim wrote:
> > I have been searching through the templates and other files but have
> > not been able to find a way to have these folders autogenerated when I
> > add an email user. ?I can add them afterwards, but I want my users to
> > be able to simply login and go.
>
> AFAIK the user has to first log into his own account via a client (e.g.
> Horde) to trigger an automatic generation of the Inbox etc.

On Montag, 12. Januar 2009, Alain Spineux wrote:
> I think Kolab let the MUA create theses folder itself at first user login,
> because Sent, Draft and other are not standard names !
> Depending  your Language, the name could change.

Alain and Saim, you are right!
The client shall create the folder structure.
(The resmngr counts as client for the special purposes if there is
no calender default.)

Developers discussed a possible addition to allow autocreation here:
kolab/issue2492 (Autocreate autosubscribe folders/subfolders patch)
But there currently is not funding for such a change.

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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090112/2fc0c065/attachment.bin

From bernhard at intevation.de  Mon Jan 12 15:32:56 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 12 Jan 2009 15:32:56 +0100
Subject: Groups for shared folders
In-Reply-To: <4969EC83.8090201@dragonrising.com>
References: <4969EC83.8090201@dragonrising.com>
Message-ID: <200901121532.56689.bernhard@intevation.de>

On Sonntag, 11. Januar 2009, Alex wrote:
> I'm loving kolab, but need a few pointers giving a group of users access
> to a shared folder. I can at the moment give access to everyone, nobody
> or a specific person.

You can use server distribution lists.
(Use the Webadmin for your Kolab Server go to "distribution list",
add one with all your users and then use "group:YOURLISTNAME"
as UID to give rights to for the folder.

> Having searched kolab-users, I've seen a post which seemed to indicate
> the following:
>
> 1) Create a new user of account type 'Group Account'
>
> 2) Add users to this group account by adding their UID to the
> 'Email-Delegates' field of the group account.

Email-Delegates _only_ is about who can use the From: adress
for the Account in question. So this does not help.

> 3) Create a shared folder, giving the group accounts UID 'post'
> permissions.

Post is about incoming emails, so wrong tree. :)

> My Mozilla Thunderbird client does not see the new shared folder.
> Am I on the right lines here?

You were'nt. ;)



-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090112/f9eb5673/attachment.bin

From bernhard at intevation.de  Mon Jan 12 15:37:06 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 12 Jan 2009 15:37:06 +0100
Subject: kolab 2.2.1b1 issue 3331
In-Reply-To: <496A3CBA.3060004@servinfo.ca>
References: <496A3CBA.3060004@servinfo.ca>
Message-ID: <200901121537.06488.bernhard@intevation.de>

On Sonntag, 11. Januar 2009, Christian Tardif wrote:
> I just installed a new kolab 2.2.1b1, and lost some time to figure out
> why mail was not getting thru. I finally found out the answer to my
> problem on the Internet. The solution is documented in issue 3331
> (kolabfilter uses incorrect delivery backend).

Hmm, you did not read the (updated) 1st.README.
Since two weeks or it has the hint, e.g.
http://ftp.belnet.be/packages/kolab/server/beta/kolab-server-2.2.1-beta-1/sources/1st.README
!!!!!!!!!!!!!!!
!! PLEASE NOTE:
!!!!!!!!!!!!!!!
Due to a configuration error within the Kolab-Server-2.2.1-beta-1 release 
you will have to correct a setting in the following file
in order to be able to reveive emails on the server!

    /kolab/etc/kolab/templates/resmgr.conf.template

Please change the 'LMTP' to 'lmtp' in line 53:
$conf['kolab']['filter']['delivery_backend'] = 'LMTP';
to
$conf['kolab']['filter']['delivery_backend'] = 'lmtp';
!!!!!!!!!!!!!!!

> Couldn't it be integrated in the source directly on the server ? ?

We will for the next revision. :)
If we'd changed it for 2.2.lb1 is would not be 2.2.1b1 anymore. 

Sorry for the inconvenience!
But: Please read 1st.README!
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090112/2382a624/attachment.bin

From jwhardeman at gmail.com  Mon Jan 12 16:24:17 2009
From: jwhardeman at gmail.com (Joseph Hardeman)
Date: Mon, 12 Jan 2009 10:24:17 -0500
Subject: Question About Kolab and Cyrus Mail Boxes
In-Reply-To: <71fe4e760901120322y6f7a53b1u5c1a4fd82314c61a@mail.gmail.com>
References: <496809C2.8080107@gmail.com>
	<71fe4e760901120322y6f7a53b1u5c1a4fd82314c61a@mail.gmail.com>
Message-ID: <496B60A1.8030905@gmail.com>

Alain,

Thank you for the response.  In my test account and another account, I 
used both Thunderbird, with IMAP, and Horde and after logging in on both 
the Drafts and Sent folders were not created, I had to manually create 
them in Horde and then Thunderbird saw them.

Do you know what files Kolab Admin uses to create the user?  I want to 
see if there is a way in those files to generate these folders.  I 
understand about the different languages, I just want to be able to 
handle it on my end for my domain users.

Thanks for the info about setting up a self generated cert for multiple 
domain names, I will research further on how to generate it. 

Thanks

Joseph

Alain Spineux wrote:
> On Sat, Jan 10, 2009 at 3:36 AM, Joseph Hardeman <jwhardeman at gmail.com> wrote:
>   
>> Greetings everyone,
>>
>> I have just finished setting up my first installation of Kolab and have
>> two quick questions.
>>
>> When I create a user, I do not see a Sent mail folder and a Drafts
>> folder.  For instance see my lm after logging into cyradm:
>>     
>
> I think Kolab let the MUA create theses folder itself at first user login,
> because Sent, Draft and other are not standard names !
> Depending  your Language, the name could change.
>
>
>   
>> user/testuser/Calendar at farkinga.com (\HasNoChildren)
>> user/testuser/Contacts at farkinga.com (\HasNoChildren)
>> user/testuser/Notes at farkinga.com (\HasNoChildren)
>> user/testuser/Tasks at farkinga.com (\HasNoChildren)
>> user/testuser at farkinga.com (\HasChildren)
>>
>>
>> I have been searching through the templates and other files but have not
>> been able to find a way to have these folders autogenerated when I add
>> an email user.  I can add them afterwards, but I want my users to be
>> able to simply login and go.
>>     
>
> They are already able to simply login and go !
>
>   
>> My second question is, is there a template file where I can add multiple
>> certs for my IMAP/POP authentication?  Or can someone send me a quick
>> note on where I need to add them?  I want to be able to provide virtual
>> domain support and when a user goes to add their mail.domain.com account
>> to their client they won't get the wrong cert.
>>     
>
> You can only attach ONE certificate to an (IP, port) couple !
>
> anyway, you can ave multiple Alternate Name in one certificate.
> For example you create a certificate using the
>
> commonName =myserver.name.com
>
> and add 2 alternate names
>
> DNS.1=myserver.name.com   # this is a good idea to have ce commonName
> in the list of alternate name
> DNS.2=webmail.domain1.com
> DNS.3=webmail.domain2.com
>
> But this is mostly true if you generate your certificate yourself, because most
> of the cheap certificate provider will not let you add multiple
> alternate names !
>
>
>   
>> Thanks for everything.
>>
>> Joseph
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>
>>     
>
>
>
>   


From jwhardeman at gmail.com  Mon Jan 12 16:26:06 2009
From: jwhardeman at gmail.com (Joseph Hardeman)
Date: Mon, 12 Jan 2009 10:26:06 -0500
Subject: Question About Kolab and Cyrus Mail Boxes
In-Reply-To: <496B32A3.1070702@hia.rwth-aachen.de>
References: <496809C2.8080107@gmail.com> <496B32A3.1070702@hia.rwth-aachen.de>
Message-ID: <496B610E.5050404@gmail.com>

Saim,

Thanks for the response, I did login via Horde and the Inbox was there, 
but the Sent items folder wasn't generated.  I just responded to another 
response asking if they knew the files that are used to generate the 
Inbox and other folders so that I can modify on my end to generate these 
folders I want.

Thanks

Joseph

Saim Kim wrote:
> Hello Jospeh,
>
>>
>> I have been searching through the templates and other files but have 
>> not been able to find a way to have these folders autogenerated when 
>> I add an email user.  I can add them afterwards, but I want my users 
>> to be able to simply login and go.
> AFAIK the user has to first log into his own account via a client 
> (e.g. Horde) to trigger an automatic generation of the Inbox etc.
>
> Best regards,
> Saim
>


From lbf at dragonrising.com  Mon Jan 12 16:58:02 2009
From: lbf at dragonrising.com (Alex)
Date: Mon, 12 Jan 2009 15:58:02 +0000
Subject: Groups for shared folders
In-Reply-To: <mailman.245.1231773956.2113.kolab-users@kolab.org>
References: <mailman.245.1231773956.2113.kolab-users@kolab.org>
Message-ID: <496B688A.2080802@dragonrising.com>

Hi Bernhard,

Thanks so much for the assistance, though I'm still getting stuck.

I've:

1) Gone to distribution lists and create new list:

List name: staff-group at mydomain.com
Members: alex.kent at mydomain.com
Hidden: unchecked

2) Created a shared folder:

Folder name: staff-shared at mydomain.com
Folder type: mails
Permission for UID/email/GID: "group:staff-group at mydomain.com" 
Permission='all'

This generates the error:

"No UID or GID group:staff-group at mydomain.com"

It does accept the UID if I drop "group:" eg:

Permission for UID/email/GID: "staff-group at mydomain.com" Permission='all'

But this doesn't seem to give me "alex.kent at mydomain.com" access to the 
folder.

Am I getting closer?

Best wishes,

Alex Kent




>
> ------------------------------------------------------------------------
>
> Subject:
> Re: Groups for shared folders
> From:
> Bernhard Reiter <bernhard at intevation.de>
> Date:
> Mon, 12 Jan 2009 15:32:56 +0100
> To:
> kolab-users at kolab.org
>
> To:
> kolab-users at kolab.org
>
>
> On Sonntag, 11. Januar 2009, Alex wrote:
>   
>> I'm loving kolab, but need a few pointers giving a group of users access
>> to a shared folder. I can at the moment give access to everyone, nobody
>> or a specific person.
>>     
>
> You can use server distribution lists.
> (Use the Webadmin for your Kolab Server go to "distribution list",
> add one with all your users and then use "group:YOURLISTNAME"
> as UID to give rights to for the folder.
>
>   
>> Having searched kolab-users, I've seen a post which seemed to indicate
>> the following:
>>
>> 1) Create a new user of account type 'Group Account'
>>
>> 2) Add users to this group account by adding their UID to the
>> 'Email-Delegates' field of the group account.
>>     
>
> Email-Delegates _only_ is about who can use the From: adress
> for the Account in question. So this does not help.
>
>   
>> 3) Create a shared folder, giving the group accounts UID 'post'
>> permissions.
>>     
>
> Post is about incoming emails, so wrong tree. :)
>
>   
>> My Mozilla Thunderbird client does not see the new shared folder.
>> Am I on the right lines here?
>>     
>
> You were'nt. ;)
>
>
>   


From bernhard at intevation.de  Tue Jan 13 08:44:07 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 13 Jan 2009 08:44:07 +0100
Subject: Groups for shared folders
In-Reply-To: <496B688A.2080802@dragonrising.com>
References: <mailman.245.1231773956.2113.kolab-users@kolab.org>
	<496B688A.2080802@dragonrising.com>
Message-ID: <200901130844.08259.bernhard@intevation.de>

On Montag, 12. Januar 2009, Alex wrote:
> Folder name: staff-shared at mydomain.com
> Folder type: mails
> Permission for UID/email/GID: "group:staff-group at mydomain.com"
> Permission='all'

Try "group:staff-group".


-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090113/d8ba2efa/attachment.bin

From lbf at dragonrising.com  Tue Jan 13 12:27:01 2009
From: lbf at dragonrising.com (Alex)
Date: Tue, 13 Jan 2009 11:27:01 +0000
Subject: Groups for shared folders
In-Reply-To: <mailman.10.1231844403.29861.kolab-users@kolab.org>
References: <mailman.10.1231844403.29861.kolab-users@kolab.org>
Message-ID: <496C7A85.6010504@dragonrising.com>

Hi Bernhard,

Thanks for the assistance, but I'm still getting "No UID or GID
group:staff-group". #

I've tried:

+ Restarting kolab

+ Created a new distribution list without hyphens, ie 'staffgroup' to
see if hyphens weren't being allowed.

+ Add a distribution list called 'group:staff-group at mydomain.com' and
then adding 'group:staff-group at mydomain.com' into the permissions of the
shared folder. It does save the UID without error, but doesn't give me
access to that folder.

I'm using kolab version 2.2.0.Would I have more luck by upgrading to the
latest beta that is out?

Thanks & best wishes,

Alex Kent

>
> Subject:
> Re: Groups for shared folders
> From:
> Bernhard Reiter <bernhard at intevation.de>
> Date:
> Tue, 13 Jan 2009 08:44:07 +0100
> To:
> kolab-users at kolab.org
>
> To:
> kolab-users at kolab.org
>
>
> On Montag, 12. Januar 2009, Alex wrote:
>   
>> Folder name: staff-shared at mydomain.com
>> Folder type: mails
>> Permission for UID/email/GID: "group:staff-group at mydomain.com"
>> Permission='all'
>>     
>
> Try "group:staff-group".
>   



From alex at DragonRising.com  Tue Jan 13 12:26:45 2009
From: alex at DragonRising.com (Alex Kent)
Date: Tue, 13 Jan 2009 11:26:45 +0000
Subject: Groups for shared folders
In-Reply-To: <mailman.10.1231844403.29861.kolab-users@kolab.org>
References: <mailman.10.1231844403.29861.kolab-users@kolab.org>
Message-ID: <496C7A75.2000109@DragonRising.com>

Hi Bernhard,

Thanks for the assistance, but I'm still getting "No UID or GID 
group:staff-group". #

I've tried:

+ Restarting kolab

+ Created a new distribution list without hyphens, ie 'staffgroup' to 
see if hyphens weren't being allowed.

+ Add a distribution list called 'group:staff-group at mydomain.com' and 
then adding 'group:staff-group at mydomain.com' into the permissions of the 
shared folder. It does save the UID without error, but doesn't give me 
access to that folder.

I'm using kolab version 2.2.0.Would I have more luck by upgrading to the 
latest beta that is out?

Thanks & best wishes,

Alex Kent

>
> Subject:
> Re: Groups for shared folders
> From:
> Bernhard Reiter <bernhard at intevation.de>
> Date:
> Tue, 13 Jan 2009 08:44:07 +0100
> To:
> kolab-users at kolab.org
>
> To:
> kolab-users at kolab.org
>
>
> On Montag, 12. Januar 2009, Alex wrote:
>   
>> Folder name: staff-shared at mydomain.com
>> Folder type: mails
>> Permission for UID/email/GID: "group:staff-group at mydomain.com"
>> Permission='all'
>>     
>
> Try "group:staff-group".
>   


From delonly at gmail.com  Tue Jan 13 14:53:21 2009
From: delonly at gmail.com (Del Only)
Date: Tue, 13 Jan 2009 14:53:21 +0100
Subject: Clients on Mac OSX, any experiences?
Message-ID: <2d303b680901130553m77d7bb1eu5a2c484e72e17b84@mail.gmail.com>

Hello all,

I am wondering if any of you can share experiences using clients on Macs. I
am especially interested in whether Kontact is in a usable state, it can be
downloaded here:
http://files.kolab.org/clients/kontact-enterprise4/

I am also interested in hearing about experience with
Thunderbird+Lightening+synckolab, although I expect scheduling and viewing
others calenders to still be missing.

Cheers,
Del
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20090113/76875bce/attachment.html

From akopciuch at bddf.ca  Tue Jan 13 16:26:54 2009
From: akopciuch at bddf.ca (Andrew J. Kopciuch)
Date: Tue, 13 Jan 2009 08:26:54 -0700
Subject: Groups for shared folders
In-Reply-To: <200901130844.08259.bernhard@intevation.de>
References: <mailman.245.1231773956.2113.kolab-users@kolab.org>
	<496B688A.2080802@dragonrising.com>
	<200901130844.08259.bernhard@intevation.de>
Message-ID: <200901130826.59026.akopciuch@bddf.ca>

On January 13, 2009, Bernhard Reiter wrote:
> On Montag, 12. Januar 2009, Alex wrote:
> > Folder name: staff-shared at mydomain.com
> > Folder type: mails
> > Permission for UID/email/GID: "group:staff-group at mydomain.com"
> > Permission='all'
>
> Try "group:staff-group".

I just tested, and I can not make a group address work either.

The syntax to enter a distribution list is the full email address.

list at domain.com

The PHP interface determines it as a distribution list, and prepends "group:" 
to the acl entry.

I dug a little bit into the PHP code to see what was going on, and I have 
verified that the admin interface seems to be doing it's job, as the acl is 
added in LDAP properly :

<ldif>
# testshare at domain.ca, domain.ca
dn: cn=testshare at domain.ca,dc=domain,dc=ca
kolabHomeServer: mail.domain.ca
objectClass: kolabSharedFolder
cn: testshare at domain.ca
acl: group:test at domain.ca all
</ldif>


However ...

With only the group: acl entry, the shared folder does not appear in my 
account's subscription list.  Not until I specify the individual user in an 
acl.  Only then do I have the option to subscribe to the folder.

I can verify that the group does exist in /kolab/etc/imapd/imapd.group as one 
would expect.

I did modify things to test the LDAP entry without the group: on the acl, and 
that definitely does not work.  I also just for my own humor : 

- added the user UID acl, 
- subscribed, 
- then added some messages, 
- removed the UID, and left the GID acl.
- tried something else on the folder.

All to no avail.   All I did was verify that Kontact acted properly, and told 
me I have no rights to a shared folder, and things had been moved into 
lost+found for safe keeping.  (Which is exactly what I would expect to 
happen.


It appears that cyrus imapd is not utilizing the group: acl properly.   That's 
out of my knowledge at the current moment on how to debug without a great 
deal of time.   I hope my comments, and information can help someone else 
debug this further.


BTW ...

Kolab version 2.2 (OpenPKG)
Kontact Version 1.2.9


HTH,


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/20090113/9244f115/attachment.bin

From dvadell at linuxclusters.com.ar  Tue Jan 13 16:47:15 2009
From: dvadell at linuxclusters.com.ar (Diego M. Vadell)
Date: Tue, 13 Jan 2009 13:47:15 -0200
Subject: Question About Kolab and Cyrus Mail Boxes
In-Reply-To: <496B610E.5050404@gmail.com>
References: <496809C2.8080107@gmail.com> <496B32A3.1070702@hia.rwth-aachen.de>
	<496B610E.5050404@gmail.com>
Message-ID: <200901131347.15973.dvadell@linuxclusters.com.ar>

Hi Joseph,

   I (kind of hackishly) solved it by changing 
/kolab/lib/perl/vendor_perl/5.10.0/Kolab/Cyrus.pm . In the createMailbox 
function, I added a line calling a perl script that would check that every 
user has Spam, Sent and Drafts folders.

    Looks like this:

sub createMailbox
{
[...]

        if (!$cyrus->create($cyruid)) {
            Kolab::log('Y', "Unable to create mailbox `$cyruid', Error = `" . 
$cyrus->error . "'", KOLAB_WARN);
        }
        # Revision: 20081021 - DMV
        system("/root/bin/fix_Spam_folder.pl");
    } else {
        Kolab::log('Y', "Skipping mailbox creation for $uid (curuid='$cyruid', 
mailbox='".join(',',@{$mailbox})."'", KOLAB_DEBUG);
    }
}

So if $cyrus->create($cyruid) does create the mailbox, perl runs 
/root/bin/fix_Spam_folder.pl . 

That script uses IMAP::Admin to log in as manager and check all the users.

HTH
 -- Diego


On Monday 12 January 2009 13:26:06 Joseph Hardeman wrote:
> Saim,
>
> Thanks for the response, I did login via Horde and the Inbox was there,
> but the Sent items folder wasn't generated.  I just responded to another
> response asking if they knew the files that are used to generate the
> Inbox and other folders so that I can modify on my end to generate these
> folders I want.
>
> Thanks
>
> Joseph
>
> Saim Kim wrote:
> > Hello Jospeh,
> >
> >> I have been searching through the templates and other files but have
> >> not been able to find a way to have these folders autogenerated when
> >> I add an email user.  I can add them afterwards, but I want my users
> >> to be able to simply login and go.
> >
> > AFAIK the user has to first log into his own account via a client
> > (e.g. Horde) to trigger an automatic generation of the Inbox etc.
> >
> > Best regards,
> > Saim
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users


From jwhardeman at gmail.com  Tue Jan 13 17:01:10 2009
From: jwhardeman at gmail.com (Joseph Hardeman)
Date: Tue, 13 Jan 2009 11:01:10 -0500
Subject: Question About Kolab and Cyrus Mail Boxes
In-Reply-To: <200901131347.15973.dvadell@linuxclusters.com.ar>
References: <496809C2.8080107@gmail.com> <496B32A3.1070702@hia.rwth-aachen.de>
	<496B610E.5050404@gmail.com>
	<200901131347.15973.dvadell@linuxclusters.com.ar>
Message-ID: <496CBAC6.8090109@gmail.com>

Hi Diego,

Very cool.  Was considering something like this myself.

Would you mind sharing your perl script? 

Thanks

Joseph

Diego M. Vadell wrote:
> Hi Joseph,
>
>    I (kind of hackishly) solved it by changing 
> /kolab/lib/perl/vendor_perl/5.10.0/Kolab/Cyrus.pm . In the createMailbox 
> function, I added a line calling a perl script that would check that every 
> user has Spam, Sent and Drafts folders.
>
>     Looks like this:
>
> sub createMailbox
> {
> [...]
>
>         if (!$cyrus->create($cyruid)) {
>             Kolab::log('Y', "Unable to create mailbox `$cyruid', Error = `" . 
> $cyrus->error . "'", KOLAB_WARN);
>         }
>         # Revision: 20081021 - DMV
>         system("/root/bin/fix_Spam_folder.pl");
>     } else {
>         Kolab::log('Y', "Skipping mailbox creation for $uid (curuid='$cyruid', 
> mailbox='".join(',',@{$mailbox})."'", KOLAB_DEBUG);
>     }
> }
>
> So if $cyrus->create($cyruid) does create the mailbox, perl runs 
> /root/bin/fix_Spam_folder.pl . 
>
> That script uses IMAP::Admin to log in as manager and check all the users.
>
> HTH
>  -- Diego
>
>
> On Monday 12 January 2009 13:26:06 Joseph Hardeman wrote:
>   
>> Saim,
>>
>> Thanks for the response, I did login via Horde and the Inbox was there,
>> but the Sent items folder wasn't generated.  I just responded to another
>> response asking if they knew the files that are used to generate the
>> Inbox and other folders so that I can modify on my end to generate these
>> folders I want.
>>
>> Thanks
>>
>> Joseph
>>
>> Saim Kim wrote:
>>     
>>> Hello Jospeh,
>>>
>>>       
>>>> I have been searching through the templates and other files but have
>>>> not been able to find a way to have these folders autogenerated when
>>>> I add an email user.  I can add them afterwards, but I want my users
>>>> to be able to simply login and go.
>>>>         
>>> AFAIK the user has to first log into his own account via a client
>>> (e.g. Horde) to trigger an automatic generation of the Inbox etc.
>>>
>>> Best regards,
>>> Saim
>>>       
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>     
>
>
>   


From bernhard at intevation.de  Tue Jan 13 17:40:06 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 13 Jan 2009 17:40:06 +0100
Subject: New native Windows and Mac OS Clients: first beta of Kontact
	Enterprise 4
Message-ID: <200901131740.09986.bernhard@intevation.de>

Hello Friends of the Kolab Groupware Solution,

as a christmas present the new server files.kolab.org was unveiled
on kolab-devel@ on the 19th of December and it already had
'beta-huge-debug' versions of Kontact Enterprise 4 for Windows and Mac OS X.

The available betas are huge, because they contain all debugging files,
everything and the kitchen sink. Still, why should we have waited longer? 
You know it is a beta and bad things might happen,
but you get to make the choice if you want to try it anyway.
In best tradition of early publication in Free Software development
you the Software now, despite some known problems. Go to

  https://wiki.kolab.org/index.php/Kontact_for_Windows_(beta-huge-debug)
  https://wiki.kolab.org/index.php/Kontact_for_MacOS_(beta-huge-debug)

We will polish the installation packages during the next months.
Feedback is highly appreciated, e.g. on the public mailinglists!

Best Regards,
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090113/7174303f/attachment-0001.bin

From florianbeckmann at gmx.net  Wed Jan 14 03:44:02 2009
From: florianbeckmann at gmx.net (Florian Beckmann)
Date: Wed, 14 Jan 2009 03:44:02 +0100
Subject: Help - virus/trojan/worm
Message-ID: <20090114024402.199020@gmx.net>

Hi all,

I have a problem with a virus/trojan/worm. Since only kolab-related files have
entries like

0208:03d9fda72723c1f79dfafefcfaf419bd:Trojan.Downloader-58153
382976:9e88346055a2baef59dc20fd0df1b880:Trojan.Agent-59155
313344:d257bcbdddccedb9bf6f02fd20f1f564:Trojan.Agent-59156
339968:23b593336ad2be91c00603fd221f37a4:Trojan.Agent-59157
126976:acb84f58d9f6a7a16c33fffd2e44b9e1:Trojan.Magania-7887
336896:0fa145272e152ea5785e04fd3209f524:Trojan.Agent-59158

I guess it's related to kolab (or at least postfix?)?

I wondered if someone here could help me to find out how this happens and what I should/can/have to  do now.

Related files are
/etc/kolab/filter/config.php

/etc/kolab/filter/config.php
/etc/kolab/filter/config.php.old
/etc/imapd.group
/etc/postfix/ldapdistlist.cf
/etc/postfix/ldaptransport.cf
/etc/postfix/main.cf
/etc/postfix/main.cf.old
/etc/postfix/relocated
/etc/ldap/slapd.replicas
/etc/postfix/sasl/smtpd.conf
/etc/postfix/transport

All files were last modified at 12. Jan 13:44

Debian Linux 2.6.26 with kolab 2.2.0-20080709.dfsg-2 0 from debian/unstable.

Thx in advance
Florian Beckmann

-- 
Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger


From aspineux at gmail.com  Wed Jan 14 08:17:05 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Wed, 14 Jan 2009 08:17:05 +0100
Subject: Question About Kolab and Cyrus Mail Boxes
In-Reply-To: <496CBAC6.8090109@gmail.com>
References: <496809C2.8080107@gmail.com> <496B32A3.1070702@hia.rwth-aachen.de>
	<496B610E.5050404@gmail.com>
	<200901131347.15973.dvadell@linuxclusters.com.ar>
	<496CBAC6.8090109@gmail.com>
Message-ID: <71fe4e760901132317oda3a98doae1d3c8380aed40d@mail.gmail.com>

On Tue, Jan 13, 2009 at 5:01 PM, Joseph Hardeman <jwhardeman at gmail.com> wrote:
> Hi Diego,
>
> Very cool.  Was considering something like this myself.
>
> Would you mind sharing your perl script?
>
> Thanks
>
> Joseph
>
> Diego M. Vadell wrote:
>> Hi Joseph,
>>
>>    I (kind of hackishly) solved it by changing
>> /kolab/lib/perl/vendor_perl/5.10.0/Kolab/Cyrus.pm . In the createMailbox
>> function, I added a line calling a perl script that would check that every
>> user has Spam, Sent and Drafts folders.
>>
>>     Looks like this:
>>
>> sub createMailbox
>> {
>> [...]
>>
>>         if (!$cyrus->create($cyruid)) {
>>             Kolab::log('Y', "Unable to create mailbox `$cyruid', Error = `" .
>> $cyrus->error . "'", KOLAB_WARN);
>>         }
>>         # Revision: 20081021 - DMV
>>         system("/root/bin/fix_Spam_folder.pl");
>>     } else {
>>         Kolab::log('Y', "Skipping mailbox creation for $uid (curuid='$cyruid',
>> mailbox='".join(',',@{$mailbox})."'", KOLAB_DEBUG);
>>     }
>> }
>>

This could become a new feature in kolab !
With a checkbox in the web admin for "Do you want kolab to create the
common folders in all new mailboxes ?"


>> So if $cyrus->create($cyruid) does create the mailbox, perl runs
>> /root/bin/fix_Spam_folder.pl .
>>
>> That script uses IMAP::Admin to log in as manager and check all the users.
>>
>> HTH
>>  -- Diego
>>
>>
>> On Monday 12 January 2009 13:26:06 Joseph Hardeman wrote:
>>
>>> Saim,
>>>
>>> Thanks for the response, I did login via Horde and the Inbox was there,
>>> but the Sent items folder wasn't generated.  I just responded to another
>>> response asking if they knew the files that are used to generate the
>>> Inbox and other folders so that I can modify on my end to generate these
>>> folders I want.
>>>
>>> Thanks
>>>
>>> Joseph
>>>
>>> Saim Kim wrote:
>>>
>>>> Hello Jospeh,
>>>>
>>>>
>>>>> I have been searching through the templates and other files but have
>>>>> not been able to find a way to have these folders autogenerated when
>>>>> I add an email user.  I can add them afterwards, but I want my users
>>>>> to be able to simply login and go.
>>>>>
>>>> AFAIK the user has to first log into his own account via a client
>>>> (e.g. Horde) to trigger an automatic generation of the Inbox etc.
>>>>
>>>> Best regards,
>>>> Saim
>>>>
>>> _______________________________________________
>>> 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 aspineux at gmail.com  Wed Jan 14 08:19:30 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Wed, 14 Jan 2009 08:19:30 +0100
Subject: Help - virus/trojan/worm
In-Reply-To: <20090114024402.199020@gmx.net>
References: <20090114024402.199020@gmx.net>
Message-ID: <71fe4e760901132319n4220fd66g181aa813ba850ea9@mail.gmail.com>

On Wed, Jan 14, 2009 at 3:44 AM, Florian Beckmann
<florianbeckmann at gmx.net> wrote:
> Hi all,
>
> I have a problem with a virus/trojan/worm. Since only kolab-related files have
> entries like

Hi

What is your problem ?

>
> 0208:03d9fda72723c1f79dfafefcfaf419bd:Trojan.Downloader-58153
> 382976:9e88346055a2baef59dc20fd0df1b880:Trojan.Agent-59155
> 313344:d257bcbdddccedb9bf6f02fd20f1f564:Trojan.Agent-59156
> 339968:23b593336ad2be91c00603fd221f37a4:Trojan.Agent-59157
> 126976:acb84f58d9f6a7a16c33fffd2e44b9e1:Trojan.Magania-7887
> 336896:0fa145272e152ea5785e04fd3209f524:Trojan.Agent-59158
>
> I guess it's related to kolab (or at least postfix?)?
>
> I wondered if someone here could help me to find out how this happens and what I should/can/have to  do now.
>
> Related files are
> /etc/kolab/filter/config.php
>
> /etc/kolab/filter/config.php
> /etc/kolab/filter/config.php.old
> /etc/imapd.group
> /etc/postfix/ldapdistlist.cf
> /etc/postfix/ldaptransport.cf
> /etc/postfix/main.cf
> /etc/postfix/main.cf.old
> /etc/postfix/relocated
> /etc/ldap/slapd.replicas
> /etc/postfix/sasl/smtpd.conf
> /etc/postfix/transport
>
> All files were last modified at 12. Jan 13:44
>
> Debian Linux 2.6.26 with kolab 2.2.0-20080709.dfsg-2 0 from debian/unstable.
>
> Thx in advance
> Florian Beckmann
>
> --
> Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
>
> _______________________________________________
> 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 bernhard at intevation.de  Wed Jan 14 10:42:36 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 14 Jan 2009 10:42:36 +0100
Subject: Question About Kolab and Cyrus Mail Boxes
In-Reply-To: <71fe4e760901132317oda3a98doae1d3c8380aed40d@mail.gmail.com>
References: <496809C2.8080107@gmail.com> <496CBAC6.8090109@gmail.com>
	<71fe4e760901132317oda3a98doae1d3c8380aed40d@mail.gmail.com>
Message-ID: <200901141042.36839.bernhard@intevation.de>

On Mittwoch, 14. Januar 2009, Alain Spineux wrote:
> This could become a new feature in kolab !
> With a checkbox in the web admin for "Do you want kolab to create the
> common folders in all new mailboxes ?"

See
| Developers discussed a possible addition to allow autocreation here:
| kolab/issue2492 (Autocreate autosubscribe folders/subfolders patch)

for some conceptual difficulties.
Also it would be good to refer to the script there in the issue.
Thanks,
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 --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20090114/7b2aa085/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090114/7b2aa085/attachment.bin

From itsef-admin at brightsight.com  Wed Jan 14 14:38:48 2009
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Wed, 14 Jan 2009 14:38:48 +0100
Subject: Massive loss of events in enterprise35 client
Message-ID: <200901141438.48428.itsef-admin@brightsight.com>

Hi all,

I'm Cc'ing this to both lists, as  I regard this as a major problem - "devel" 
to get some input from the developers and "users" just to see whether anybody 
else has seen things like this anywhere.

For the first time in enterprise35 (that I know of in our company), the old, 
ugly problem rears its head again: Massive loss of events from one's agenda. 
This time it has happened to myself - yesterday evening, several hundred 
events were deleted from my agenda, without my intervention. Here's the 
forensics:
- kontact --version
  Qt: 3.3.8b
  KDE: 3.5.10
  Kontact: 1.2.9 (enterprise35 20081202.891698)
  (Kubuntu 8.04)
- $HOME is on NFS
- Kontact was running, but I do not recall actually working with Kontact at 
the time, though I did start a new mail shortly afterwards
- According to the imap server logs (Kolab 2.1), the events in question were 
deleted - I can see hunderds of lines like this:
imapd.log.0:Jan 13 18:13:19 HOST <debug> imaps[3259]: mailbox_expunge: 
removing mail brightsight.com!user.USER.Calendar:18646
- Earlier that day, I had a crash - most likely due to connection problems 
with our mailserver (we had firewall problems), but I had already restarted 
Kontact
- I did not find anything suspicious in .xsession-errors, except for a bunch 
of SSL errors I could not place:
5594:error:140940E5:lib(20):func(148):reason(229):s3_pkt.c:990:
5594:error:14094415:lib(20):func(148):reason(1045):s3_pkt.c:1053:SSL alert 
number 45
- I am using four different calendars - my own, another "single user" 
calendar, one group calendar and a shared folder calendar. Only my own 
calendar was affected.
- Oddly enough, not all of the events in my calendar were deleted - 9 messages 
were left behind on the server, one of which was a real event from last 
October. The other eight were empty.


Another user also lost all events yesterday, however, in his case it happened 
with the Kontact instance that was still running during the connection 
problems with the mail server. His events were deleted (again, according to 
imapd.log) about three hours after the connection had been restored. He had 
not restarted Kontact since. His .xession-errors has already been 
overwritten, so no help there.


We have experienced problems like this rather frequently with proko2. 
enterprise35 is doing much better (in fact, I was lulled into the hope that 
the problem might have vanished) - but apparently, there's still something 
not quite right...

Any input - as always - welcome!

Regards,

Thomas


From wrobel at pardus.de  Wed Jan 14 16:20:14 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 14 Jan 2009 16:20:14 +0100
Subject: Help - virus/trojan/worm
In-Reply-To: <20090114024402.199020@gmx.net>
References: <20090114024402.199020@gmx.net>
Message-ID: <20090114162014.174847y85zmmmbqc@webmail.pardus.de>

Hi Florian,

Quoting Florian Beckmann <florianbeckmann at gmx.net>:

> Hi all,
>
> I have a problem with a virus/trojan/worm. Since only kolab-related  
> files have
> entries like
>
> 0208:03d9fda72723c1f79dfafefcfaf419bd:Trojan.Downloader-58153
> 382976:9e88346055a2baef59dc20fd0df1b880:Trojan.Agent-59155
> 313344:d257bcbdddccedb9bf6f02fd20f1f564:Trojan.Agent-59156
> 339968:23b593336ad2be91c00603fd221f37a4:Trojan.Agent-59157
> 126976:acb84f58d9f6a7a16c33fffd2e44b9e1:Trojan.Magania-7887
> 336896:0fa145272e152ea5785e04fd3209f524:Trojan.Agent-59158
>
> I guess it's related to kolab (or at least postfix?)?
>
> I wondered if someone here could help me to find out how this  
> happens and what I should/can/have to  do now.
>
> Related files are
> /etc/kolab/filter/config.php
>
> /etc/kolab/filter/config.php
> /etc/kolab/filter/config.php.old
> /etc/imapd.group
> /etc/postfix/ldapdistlist.cf
> /etc/postfix/ldaptransport.cf
> /etc/postfix/main.cf
> /etc/postfix/main.cf.old
> /etc/postfix/relocated
> /etc/ldap/slapd.replicas
> /etc/postfix/sasl/smtpd.conf
> /etc/postfix/transport
>
> All files were last modified at 12. Jan 13:44
>
> Debian Linux 2.6.26 with kolab 2.2.0-20080709.dfsg-2 0 from debian/unstable.

 From the problem report it is extremely hard to guess what is going  
on. What does the "Trojan.Agent-..." report mean and what kind of  
signature does it match to? If you see that signature in the config  
files written via kolabconf it is unclear why they are not reported in  
the templates for these files. And it is hard to imagine that someone  
modified kolabconf on your machine so that it includes malware into  
the files it writes.

Maybe you should also contact the Debian maintainers of your Kolab port.

Cheers,

Gunnar

>
> Thx in advance
> Florian Beckmann
>
> --
> Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit  
> allen: http://www.gmx.net/de/go/multimessenger
>
> _______________________________________________
> 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/20090114/0e7d8579/attachment.bin

From wrobel at pardus.de  Wed Jan 14 16:56:50 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 14 Jan 2009 16:56:50 +0100
Subject: Groups for shared folders
In-Reply-To: <496B688A.2080802@dragonrising.com>
References: <mailman.245.1231773956.2113.kolab-users@kolab.org>
	<496B688A.2080802@dragonrising.com>
Message-ID: <20090114165650.127449q2jw3upagw@webmail.pardus.de>

Quoting Alex <lbf at dragonrising.com>:

> Hi Bernhard,
>
> Thanks so much for the assistance, though I'm still getting stuck.
>
> I've:
>
> 1) Gone to distribution lists and create new list:
>
> List name: staff-group at mydomain.com
> Members: alex.kent at mydomain.com
> Hidden: unchecked
>
> 2) Created a shared folder:
>
> Folder name: staff-shared at mydomain.com
> Folder type: mails
> Permission for UID/email/GID: "group:staff-group at mydomain.com"
> Permission='all'
>
> This generates the error:
>
> "No UID or GID group:staff-group at mydomain.com"
>
> It does accept the UID if I drop "group:" eg:

Indeed, you don't need the "group:" prefix. The mail address is enough  
to identify that this is a group.

I tested that the whole procedure works fine on the recent  
Kolab-Server-2.2.1-beta-1 release but I believe it should also work on  
2.2.0 as I don't think we changed anything in that area.

Can you check if you see the right permissions on the shared folder  
when using the cyradm tool (/kolab/bin/cyradm).

This is the example session when I tested this:

/kolab/bin/cyradm -u manager localhost
Password:
example.com> lm
shared.shared at example.com (HasNoChildren)
user/1 at example.com (HasNoChildren)
user/2 at example.com (HasNoChildren)
example.com> lam shared.shared at eample.com
group:group at example.com lrswipteda
anyone lrswipteda
manager lrswipkxtecda

You see that here the permission is marked with  
"group:group at example.com lrswipteda". The "group:" prefix is cyrus  
specific. Both users (1 at example.com com and 2 at example.com" are members  
of "group at example.com". Both see the shared folder (tested via the  
Kolab web client).

If it still does not work for you I could test the same procedure on 2.2.0.

Cheers,

Gunnar

> Permission for UID/email/GID: "staff-group at mydomain.com" Permission='all'
>
> But this doesn't seem to give me "alex.kent at mydomain.com" access to the
> folder.
>
> Am I getting closer?
>
> Best wishes,
>
> Alex Kent
>
>
>
>
>>
>> ------------------------------------------------------------------------
>>
>> Subject:
>> Re: Groups for shared folders
>> From:
>> Bernhard Reiter <bernhard at intevation.de>
>> Date:
>> Mon, 12 Jan 2009 15:32:56 +0100
>> To:
>> kolab-users at kolab.org
>>
>> To:
>> kolab-users at kolab.org
>>
>>
>> On Sonntag, 11. Januar 2009, Alex wrote:
>>
>>> I'm loving kolab, but need a few pointers giving a group of users access
>>> to a shared folder. I can at the moment give access to everyone, nobody
>>> or a specific person.
>>>
>>
>> You can use server distribution lists.
>> (Use the Webadmin for your Kolab Server go to "distribution list",
>> add one with all your users and then use "group:YOURLISTNAME"
>> as UID to give rights to for the folder.
>>
>>
>>> Having searched kolab-users, I've seen a post which seemed to indicate
>>> the following:
>>>
>>> 1) Create a new user of account type 'Group Account'
>>>
>>> 2) Add users to this group account by adding their UID to the
>>> 'Email-Delegates' field of the group account.
>>>
>>
>> Email-Delegates _only_ is about who can use the From: adress
>> for the Account in question. So this does not help.
>>
>>
>>> 3) Create a shared folder, giving the group accounts UID 'post'
>>> permissions.
>>>
>>
>> Post is about incoming emails, so wrong tree. :)
>>
>>
>>> My Mozilla Thunderbird client does not see the new shared folder.
>>> Am I on the right lines here?
>>>
>>
>> You were'nt. ;)
>>
>>
>>
>
> _______________________________________________
> 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/20090114/4f13290f/attachment.bin

From wrobel at pardus.de  Wed Jan 14 17:11:29 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Wed, 14 Jan 2009 17:11:29 +0100
Subject: Question About Kolab and Cyrus Mail Boxes
In-Reply-To: <496B60A1.8030905@gmail.com>
References: <496809C2.8080107@gmail.com>
	<71fe4e760901120322y6f7a53b1u5c1a4fd82314c61a@mail.gmail.com>
	<496B60A1.8030905@gmail.com>
Message-ID: <20090114171129.18205t2z0d3bdtog@webmail.pardus.de>

Quoting Joseph Hardeman <jwhardeman at gmail.com>:

> Alain,
>
> Thank you for the response.  In my test account and another account, I
> used both Thunderbird, with IMAP, and Horde and after logging in on both
> the Drafts and Sent folders were not created, I had to manually create
> them in Horde and then Thunderbird saw them.
>
> Do you know what files Kolab Admin uses to create the user?  I want to
> see if there is a way in those files to generate these folders.  I
> understand about the different languages, I just want to be able to
> handle it on my end for my domain users.
>
> Thanks for the info about setting up a self generated cert for multiple
> domain names, I will research further on how to generate it.

This is what I consider one of the best explanations in that area:

http://wiki.cacert.org/wiki/VhostTaskForce

There should also be a script there that allows you to generate such  
certificates.

Cheers,

Gunnar
>
> Thanks
>
> Joseph
>
> Alain Spineux wrote:
>> On Sat, Jan 10, 2009 at 3:36 AM, Joseph Hardeman  
>> <jwhardeman at gmail.com> wrote:
>>
>>> Greetings everyone,
>>>
>>> I have just finished setting up my first installation of Kolab and have
>>> two quick questions.
>>>
>>> When I create a user, I do not see a Sent mail folder and a Drafts
>>> folder.  For instance see my lm after logging into cyradm:
>>>
>>
>> I think Kolab let the MUA create theses folder itself at first user login,
>> because Sent, Draft and other are not standard names !
>> Depending  your Language, the name could change.
>>
>>
>>
>>> user/testuser/Calendar at farkinga.com (\HasNoChildren)
>>> user/testuser/Contacts at farkinga.com (\HasNoChildren)
>>> user/testuser/Notes at farkinga.com (\HasNoChildren)
>>> user/testuser/Tasks at farkinga.com (\HasNoChildren)
>>> user/testuser at farkinga.com (\HasChildren)
>>>
>>>
>>> I have been searching through the templates and other files but have not
>>> been able to find a way to have these folders autogenerated when I add
>>> an email user.  I can add them afterwards, but I want my users to be
>>> able to simply login and go.
>>>
>>
>> They are already able to simply login and go !
>>
>>
>>> My second question is, is there a template file where I can add multiple
>>> certs for my IMAP/POP authentication?  Or can someone send me a quick
>>> note on where I need to add them?  I want to be able to provide virtual
>>> domain support and when a user goes to add their mail.domain.com account
>>> to their client they won't get the wrong cert.
>>>
>>
>> You can only attach ONE certificate to an (IP, port) couple !
>>
>> anyway, you can ave multiple Alternate Name in one certificate.
>> For example you create a certificate using the
>>
>> commonName =myserver.name.com
>>
>> and add 2 alternate names
>>
>> DNS.1=myserver.name.com   # this is a good idea to have ce commonName
>> in the list of alternate name
>> DNS.2=webmail.domain1.com
>> DNS.3=webmail.domain2.com
>>
>> But this is mostly true if you generate your certificate yourself,  
>> because most
>> of the cheap certificate provider will not let you add multiple
>> alternate names !
>>
>>
>>
>>> Thanks for everything.
>>>
>>> Joseph
>>>
>>> _______________________________________________
>>> Kolab-users mailing list
>>> Kolab-users at kolab.org
>>> https://kolab.org/mailman/listinfo/kolab-users
>>>
>>>
>>
>>
>>
>>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



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

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

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


----------------------------------------------------------------
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/20090114/97943191/attachment.bin

From florianbeckmann at gmx.net  Wed Jan 14 17:33:22 2009
From: florianbeckmann at gmx.net (Florian Beckmann)
Date: Wed, 14 Jan 2009 17:33:22 +0100
Subject: Help - virus/trojan/worm
In-Reply-To: <20090114162014.174847y85zmmmbqc@webmail.pardus.de>
References: <20090114024402.199020@gmx.net>
	<20090114162014.174847y85zmmmbqc@webmail.pardus.de>
Message-ID: <20090114163322.34400@gmx.net>

>  From the problem report it is extremely hard to guess what is going  
> on. What does the "Trojan.Agent-..." report mean and what kind of  
> signature does it match to? If you see that signature in the config  
> files written via kolabconf it is unclear why they are not reported in  
> the templates for these files. And it is hard to imagine that someone  
> modified kolabconf on your machine so that it includes malware into  
> the files it writes.
> Maybe you should also contact the Debian maintainers of your Kolab port.

I just found these kind of lines (only) in the config files and my problem is that since I didn't modify them I just wondered if the modification was caused by some kind of exploit/virus. But you're right about the malware thing and probably something weird happened while clamav scanned incoming mail. I will post my problem to the debian maintainers.

Thx a lot.

Cheers
Florian

-- 
Sensationsangebot verl?ngert: GMX FreeDSL - Telefonanschluss + DSL 
f?r nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K1308T4569a


From troy at carpenter.cx  Wed Jan 14 18:09:19 2009
From: troy at carpenter.cx (Troy Carpenter)
Date: Wed, 14 Jan 2009 12:09:19 -0500
Subject: New native Windows and Mac OS Clients: first beta of Kontact
	Enterprise 4
In-Reply-To: <200901131740.09986.bernhard@intevation.de>
References: <200901131740.09986.bernhard@intevation.de>
Message-ID: <200901141209.19735.troy@carpenter.cx>

On Tue January 13 2009 11:40:06 am Bernhard Reiter wrote:
> Hello Friends of the Kolab Groupware Solution,
>
> as a christmas present the new server files.kolab.org was unveiled
> on kolab-devel@ on the 19th of December and it already had
> 'beta-huge-debug' versions of Kontact Enterprise 4 for Windows and Mac OS
> X.
>
> The available betas are huge, because they contain all debugging files,
> everything and the kitchen sink. Still, why should we have waited longer?
> You know it is a beta and bad things might happen,
> but you get to make the choice if you want to try it anyway.
> In best tradition of early publication in Free Software development
> you the Software now, despite some known problems. Go to
>
>   https://wiki.kolab.org/index.php/Kontact_for_Windows_(beta-huge-debug)
>   https://wiki.kolab.org/index.php/Kontact_for_MacOS_(beta-huge-debug)
>
> We will polish the installation packages during the next months.
> Feedback is highly appreciated, e.g. on the public mailinglists!
>
> Best Regards,
> Bernhard


I just installed the packages.  Great job and finally I have an integrated 
solution for all my data (Synckolab is great, but this is ideal).

Here's my feedback so far:

Installation went great.  When I installed it asked if I wanted English, which 
didn't seem to have any effect...everything came out in German.

Kolab Wizard: Thank goodness for my vast German knowledge...just kidding.  
Having used this for all my other systems I knew what was going on...but 
someone else who doesn't know kolab or German may get lost there.

I managed to get most of the UI into English, but there is still quite a bit 
of German.  Again, familiarity with Kontact helps, but obviously this is an 
area that needs work.

Questions: 
1. How do I change other settings that are normally controlled via the KDE 
control panel, like date format?  The menu selection under Settings gives some 
QT warning (in German which I can't read).

2. I have KDE 4.2rc1 installed on Windows. Is this version Kontact eventually 
targeted for inclusion in the Windows port?

I will continue to play around with it.  I've had two unexplained crashes so 
far, but given the status of the software, I'm expecting crashes.

Troy

-------------- 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/20090114/98183eee/attachment.bin

From bernhard at intevation.de  Wed Jan 14 18:32:48 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 14 Jan 2009 18:32:48 +0100
Subject: Massive loss of events in enterprise35 client
In-Reply-To: <200901141438.48428.itsef-admin@brightsight.com>
References: <200901141438.48428.itsef-admin@brightsight.com>
Message-ID: <200901141832.50990.bernhard@intevation.de>

On Mittwoch, 14. Januar 2009, ITSEF Admin wrote:
> - $HOME is on NFS

Your analysis should try to exclude this as a cause.
Put the cache on a local disc if you can for this.


-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090114/c5efb557/attachment.bin

From lbf at dragonrising.com  Wed Jan 14 18:41:14 2009
From: lbf at dragonrising.com (Alex)
Date: Wed, 14 Jan 2009 17:41:14 +0000
Subject: Groups for shared folders
In-Reply-To: <mailman.292.1231950808.2113.kolab-users@kolab.org>
References: <mailman.292.1231950808.2113.kolab-users@kolab.org>
Message-ID: <496E23BA.7020305@dragonrising.com>

Hi Gunnar,

Thanks for your advice on using cyradm for seeing what was going on. I
have found a work-around on 2.2.0 so that I'm able to use groups
(distribution lists) to set permissions on shared folders.

As people have been stating, I didn't need to append 'group:' to the
front of the email address used. The system did that for me fine.

With the web admin panel configured to give permission for
UID/email/GID="staff-group at starfields.net" and  permissions='all':

localhost> lam shared.test at starfields.net
group:staff-group at starfields.net p
manager lrswipkxtecda

So clearly, the 'all' permissions weren't getting through to the imap
server.

So I played with adding permissions manually to the web admin folder:

staff-group at starfields.net = "read/post"
staff-group at starfields.net = "append"
staff-group at starfields.net = "write"

And this now results in:

localhost> lam shared.test at starfields.net
group:staff-group at starfields.net lrswipted
manager lrswipkxtecda

This allows me to subscribe to the shared mail folder using thunderbird,
and add mails to it. I'm guessing I should be able to assign a public
email address to it in the normal way.

Thanks for everyones help in finding this work-around without me having
to compile/upgrade anything!

Best wishes,

Alex

> ------------------------------------------------------------------------
>
> Subject:
> Re: Groups for shared folders
> From:
> Gunnar Wrobel <wrobel at pardus.de>
> Date:
> Wed, 14 Jan 2009 16:56:50 +0100
> To:
> kolab-users at kolab.org
>
> To:
> kolab-users at kolab.org
>
>
> Quoting Alex <lbf at dragonrising.com>:
>
>> Hi Bernhard,
>>
>> Thanks so much for the assistance, though I'm still getting stuck.
>>
>> I've:
>>
>> 1) Gone to distribution lists and create new list:
>>
>> List name: staff-group at mydomain.com
>> Members: alex.kent at mydomain.com
>> Hidden: unchecked
>>
>> 2) Created a shared folder:
>>
>> Folder name: staff-shared at mydomain.com
>> Folder type: mails
>> Permission for UID/email/GID: "group:staff-group at mydomain.com"
>> Permission='all'
>>
>> This generates the error:
>>
>> "No UID or GID group:staff-group at mydomain.com"
>>
>> It does accept the UID if I drop "group:" eg:
>
> Indeed, you don't need the "group:" prefix. The mail address is enough 
> to identify that this is a group.
>
> I tested that the whole procedure works fine on the recent 
> Kolab-Server-2.2.1-beta-1 release but I believe it should also work on 
> 2.2.0 as I don't think we changed anything in that area.
>
> Can you check if you see the right permissions on the shared folder 
> when using the cyradm tool (/kolab/bin/cyradm).
>
> This is the example session when I tested this:
>
> /kolab/bin/cyradm -u manager localhost
> Password:
> example.com> lm
> shared.shared at example.com (HasNoChildren)
> user/1 at example.com (HasNoChildren)
> user/2 at example.com (HasNoChildren)
> example.com> lam shared.shared at eample.com
> group:group at example.com lrswipteda
> anyone lrswipteda
> manager lrswipkxtecda
>
> You see that here the permission is marked with 
> "group:group at example.com lrswipteda". The "group:" prefix is cyrus 
> specific. Both users (1 at example.com com and 2 at example.com" are members 
> of "group at example.com". Both see the shared folder (tested via the 
> Kolab web client).
>
> If it still does not work for you I could test the same procedure on 
> 2.2.0.
>
> Cheers,
>
> Gunnar
>
>> Permission for UID/email/GID: "staff-group at mydomain.com" 
>> Permission='all'
>>
>> But this doesn't seem to give me "alex.kent at mydomain.com" access to the
>> folder.
>>
>> Am I getting closer?
>>
>> Best wishes,
>>
>> Alex Kent
>>
>>
>>
>>
>>>
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>> Subject:
>>> Re: Groups for shared folders
>>> From:
>>> Bernhard Reiter <bernhard at intevation.de>
>>> Date:
>>> Mon, 12 Jan 2009 15:32:56 +0100
>>> To:
>>> kolab-users at kolab.org
>>>
>>> To:
>>> kolab-users at kolab.org
>>>
>>>
>>> On Sonntag, 11. Januar 2009, Alex wrote:
>>>
>>>> I'm loving kolab, but need a few pointers giving a group of users 
>>>> access
>>>> to a shared folder. I can at the moment give access to everyone, 
>>>> nobody
>>>> or a specific person.
>>>>
>>>
>>> You can use server distribution lists.
>>> (Use the Webadmin for your Kolab Server go to "distribution list",
>>> add one with all your users and then use "group:YOURLISTNAME"
>>> as UID to give rights to for the folder.
>>>
>>>
>>>> Having searched kolab-users, I've seen a post which seemed to indicate
>>>> the following:
>>>>
>>>> 1) Create a new user of account type 'Group Account'
>>>>
>>>> 2) Add users to this group account by adding their UID to the
>>>> 'Email-Delegates' field of the group account.
>>>>
>>>
>>> Email-Delegates _only_ is about who can use the From: adress
>>> for the Account in question. So this does not help.
>>>
>>>
>>>> 3) Create a shared folder, giving the group accounts UID 'post'
>>>> permissions.
>>>>
>>>
>>> Post is about incoming emails, so wrong tree. :)
>>>
>>>
>>>> My Mozilla Thunderbird client does not see the new shared folder.
>>>> Am I on the right lines here?
>>>>
>>>
>>> You were'nt. ;)
>>>
>>>
>>>
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>


From troy at carpenter.cx  Wed Jan 14 19:12:20 2009
From: troy at carpenter.cx (Troy Carpenter)
Date: Wed, 14 Jan 2009 13:12:20 -0500
Subject: New native Windows and Mac OS Clients: first beta of Kontact
	Enterprise 4
In-Reply-To: <200901141209.19735.troy@carpenter.cx>
References: <200901131740.09986.bernhard@intevation.de>
	<200901141209.19735.troy@carpenter.cx>
Message-ID: <200901141312.20823.troy@carpenter.cx>

On Wed January 14 2009 12:09:19 pm Troy Carpenter wrote:
>
> 2. I have KDE 4.2rc1 installed on Windows. Is this version Kontact
> eventually targeted for inclusion in the Windows port?
>
> I will continue to play around with it.  I've had two unexplained crashes
> so far, but given the status of the software, I'm expecting crashes.
>

That screeching sound you now hear is the major clash between the Windows KDE 
install and this Kontact package.  This is because each one is essentially a 
KDE installation.  4.2rc1 is what you would expect.  From what I can tell, the 
Kontact package is a 4.1.2 install.

Windows does NOT handle multiple KDE installs like Linux does because there 
apparently can only be one KDEDIR variable pointing to one install.  Since 
just about all the libs have the same name between the installs, Windows is 
using the first library it finds.  In my case, that was the 4.2rc1 libs.

When I removed the 4.2rc1 install (which installed in C:\Program Files\KDE) 
and only used Kontact (in C:\Program Files\Kontact), then Kontact worked fine 
including all the date configuration settings.

So, since I want Kontact more than a current KDE install, I am going to try 
something out there to see how it works.  I am going to do a Windows install 
of KDE 4.1.2, then try to install Kontact into the same directory.  If that 
fails miserably, then I guess I'll just settle for Kontact only.

One other problem I'm finding is that Kontact's Calendar doesn't keep my 
timezone setting.  I've configured it for "Eastern Standard", but once I close 
the settings dialog and reopen it, I see that the timezone setting is not 
kept.  That's causing all my events to be displayed in UTC time instead of my 
local time.

-------------- 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/20090114/416fd09e/attachment.bin

From bernhard at intevation.de  Wed Jan 14 23:01:57 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 14 Jan 2009 23:01:57 +0100
Subject: Kontact on Windows feedback (was: New native Windows and Mac OS
	Clients: first beta of Kontact Enterprise 4)
In-Reply-To: <200901141209.19735.troy@carpenter.cx>
References: <200901131740.09986.bernhard@intevation.de>
	<200901141209.19735.troy@carpenter.cx>
Message-ID: <200901142302.06179.bernhard@intevation.de>

Troy,


On Mittwoch, 14. Januar 2009, Troy Carpenter wrote:
> I managed to get most of the UI into English, but there is still quite a
> bit of German. ?Again, familiarity with Kontact helps, but obviously this
> is an area that needs work.

you should be able to get everything in English see
https://wiki.kolab.org/index.php/Kontact_for_Windows_(beta-huge-debug)
 'kdeglobals' to: 
 Country=en
 Language=en_US


> Questions:
> 1. How do I change other settings that are normally controlled via the KDE
> control panel, like date format? ?The menu selection under Settings gives
> some QT warning (in German which I can't read).

We are still working on this, the menu selection currently is the best you 
have. :)

Thanks for trying our Kontact on Windows beta and for the feedback!
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090114/0f29364d/attachment.bin

From bernhard at intevation.de  Wed Jan 14 23:07:57 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 14 Jan 2009 23:07:57 +0100
Subject: New native Windows and Mac OS Clients: first beta of Kontact
	Enterprise 4
In-Reply-To: <200901141312.20823.troy@carpenter.cx>
References: <200901131740.09986.bernhard@intevation.de>
	<200901141209.19735.troy@carpenter.cx>
	<200901141312.20823.troy@carpenter.cx>
Message-ID: <200901142307.57760.bernhard@intevation.de>

On Mittwoch, 14. Januar 2009, Troy Carpenter wrote:
> On Wed January 14 2009 12:09:19 pm Troy Carpenter wrote:
> > 2. I have KDE 4.2rc1 installed on Windows. Is this version Kontact
> > eventually targeted for inclusion in the Windows port?

Eventually yes, all changes to Kontact enterprise are being merged back to KDE 
trunk and thus will get into the Kde installer. However it also depends on
the packagers of this installer on kde-windows at . We had to use the branch
to keep all packages fixed to be able to stablelise them for the beta release,
and we'll continue to do this. So the enterprise 4 branch will most likely 
have the more stable version of Kontact and the underlying libs.

> > I will continue to play around with it.  I've had two unexplained crashes
> > so far, but given the status of the software, I'm expecting crashes.

> That screeching sound you now hear is the major clash between the Windows
> KDE install and this Kontact package.  This is because each one is
> essentially a KDE installation.  4.2rc1 is what you would expect.  From
> what I can tell, the Kontact package is a 4.1.2 install.

Yes, for the above reasons.

> Windows does NOT handle multiple KDE installs like Linux does because there
> apparently can only be one KDEDIR variable pointing to one install.  Since
> just about all the libs have the same name between the installs, Windows is
> using the first library it finds.  In my case, that was the 4.2rc1 libs.

You can probably remove KDEDIR from the general system's path (and KDEHOME I 
guess) and set it for each .bat script to have several environments on one 
machine. I haven't tried it, but somehow it will be possible.

> When I removed the 4.2rc1 install (which installed in C:\Program Files\KDE)
> and only used Kontact (in C:\Program Files\Kontact), then Kontact worked
> fine including all the date configuration settings.

Were the crashes gone also?

> So, since I want Kontact more than a current KDE install, I am going to try
> something out there to see how it works.  I am going to do a Windows
> install of KDE 4.1.2, then try to install Kontact into the same directory. 
> If that fails miserably, then I guess I'll just settle for Kontact only.

It is bound to fail.

> One other problem I'm finding is that Kontact's Calendar doesn't keep my
> timezone setting.  I've configured it for "Eastern Standard", but once I
> close the settings dialog and reopen it, I see that the timezone setting is
> not kept.  That's causing all my events to be displayed in UTC time instead
> of my local time.

We still have know problems with the timezone settings

Again, thanks for the feedback!
Can you tell on which version of windows you have tried it?

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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090114/0947dea6/attachment-0001.bin

From troy at carpenter.cx  Wed Jan 14 23:32:44 2009
From: troy at carpenter.cx (Troy Carpenter)
Date: Wed, 14 Jan 2009 17:32:44 -0500
Subject: New native Windows and Mac OS Clients: first beta of Kontact
	Enterprise 4
In-Reply-To: <200901142307.57760.bernhard@intevation.de>
References: <200901131740.09986.bernhard@intevation.de>
	<200901141312.20823.troy@carpenter.cx>
	<200901142307.57760.bernhard@intevation.de>
Message-ID: <200901141732.44736.troy@carpenter.cx>

On Wed January 14 2009 05:07:57 pm Bernhard Reiter wrote:
> On Mittwoch, 14. Januar 2009, Troy Carpenter wrote:
> > On Wed January 14 2009 12:09:19 pm Troy Carpenter wrote:
> > > 2. I have KDE 4.2rc1 installed on Windows. Is this version Kontact
> > > eventually targeted for inclusion in the Windows port?
>
> Eventually yes, all changes to Kontact enterprise are being merged back to
> KDE trunk and thus will get into the Kde installer. However it also depends
> on the packagers of this installer on kde-windows at . We had to use the
> branch to keep all packages fixed to be able to stablelise them for the
> beta release, and we'll continue to do this. So the enterprise 4 branch
> will most likely have the more stable version of Kontact and the underlying
> libs.

Cool.  I did get the system to be all English once I got the other KDE install 
out of the way.  After that the Date/Time control panel came up and I could 
switch my Country to US and language to US English.

> > > I will continue to play around with it.  I've had two unexplained
> > > crashes so far, but given the status of the software, I'm expecting
> > > crashes.
> >
> > That screeching sound you now hear is the major clash between the Windows
> > KDE install and this Kontact package.  This is because each one is
> > essentially a KDE installation.  4.2rc1 is what you would expect.  From
> > what I can tell, the Kontact package is a 4.1.2 install.
>
> Yes, for the above reasons.
>
> > Windows does NOT handle multiple KDE installs like Linux does because
> > there apparently can only be one KDEDIR variable pointing to one install.
> >  Since just about all the libs have the same name between the installs,
> > Windows is using the first library it finds.  In my case, that was the
> > 4.2rc1 libs.
>
> You can probably remove KDEDIR from the general system's path (and KDEHOME
> I guess) and set it for each .bat script to have several environments on
> one machine. I haven't tried it, but somehow it will be possible.

I'm not going to go through that much trouble to get KDE and Kontact to work.  
I mainly want Kontact so I can use all my data (contacts, calendar, email) 
from a native application without any tricks like synckolab and Thunderbird.


> > When I removed the 4.2rc1 install (which installed in C:\Program
> > Files\KDE) and only used Kontact (in C:\Program Files\Kontact), then
> > Kontact worked fine including all the date configuration settings.
>
> Were the crashes gone also?

I haven't seen any lately, but the system is still syncing the emails.  I have 
many thousands of emails on the server and prefer disconnected IMAP for 
"external" PCs like my laptop and my desktop at work.

> > So, since I want Kontact more than a current KDE install, I am going to
> > try something out there to see how it works.  I am going to do a Windows
> > install of KDE 4.1.2, then try to install Kontact into the same
> > directory. If that fails miserably, then I guess I'll just settle for
> > Kontact only.
>
> It is bound to fail.

The main thing I couldn't get to work was the IMAP process.  I didn't try much 
else past that.  I reverted my Windows system to use the Kontact version only.

It was nice, though, that Kontact integrated very nicely into the KDE menu as 
if it was installed with the KDE installer.

>
> > One other problem I'm finding is that Kontact's Calendar doesn't keep my
> > timezone setting.  I've configured it for "Eastern Standard", but once I
> > close the settings dialog and reopen it, I see that the timezone setting
> > is not kept.  That's causing all my events to be displayed in UTC time
> > instead of my local time.
>
> We still have know problems with the timezone settings

Well, for the calendar entries, Korganizer is somewhat useless without the 
timezone settings since all the entries show up in the wrong timezone.  I'm 
also not seeing all the events in the grid for the week and workweek views.  
If I switch to the month view, then I see the events.  I think part of the 
problem is related to the timezone because Kontact thinks the event starts at 
11:00pm and goes until 1:30 the next morning.  In the month view that event 
stretches over Wednesday and Thursday.  In the week views it is not there at 
all.

> Again, thanks for the feedback!
> Can you tell on which version of windows you have tried it?

This is on Windows XP Pro.

Troy


-------------- 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/20090114/edaa2490/attachment.bin

From jwhardeman at gmail.com  Thu Jan 15 00:59:51 2009
From: jwhardeman at gmail.com (Joseph Hardeman)
Date: Wed, 14 Jan 2009 18:59:51 -0500
Subject: Question About Kolab and Cyrus Mail Boxes
In-Reply-To: <20090114171129.18205t2z0d3bdtog@webmail.pardus.de>
References: <496809C2.8080107@gmail.com>	<71fe4e760901120322y6f7a53b1u5c1a4fd82314c61a@mail.gmail.com>	<496B60A1.8030905@gmail.com>
	<20090114171129.18205t2z0d3bdtog@webmail.pardus.de>
Message-ID: <496E7C77.7010601@gmail.com>

Gunner,

Thanks for the link, I have book marked it and will go through and make 
a cert for my sites.  *S* 

Again, Thanks for the link and info.

Joseph

Gunnar Wrobel wrote:
> Quoting Joseph Hardeman <jwhardeman at gmail.com>:
>
>> Alain,
>>
>> Thank you for the response.  In my test account and another account, I
>> used both Thunderbird, with IMAP, and Horde and after logging in on both
>> the Drafts and Sent folders were not created, I had to manually create
>> them in Horde and then Thunderbird saw them.
>>
>> Do you know what files Kolab Admin uses to create the user?  I want to
>> see if there is a way in those files to generate these folders.  I
>> understand about the different languages, I just want to be able to
>> handle it on my end for my domain users.
>>
>> Thanks for the info about setting up a self generated cert for multiple
>> domain names, I will research further on how to generate it.
>
> This is what I consider one of the best explanations in that area:
>
> http://wiki.cacert.org/wiki/VhostTaskForce
>
> There should also be a script there that allows you to generate such 
> certificates.
>
> Cheers,
>
> Gunnar
>>
>> Thanks
>>
>> Joseph
>>
>> Alain Spineux wrote:
>>> On Sat, Jan 10, 2009 at 3:36 AM, Joseph Hardeman 
>>> <jwhardeman at gmail.com> wrote:
>>>
>>>> Greetings everyone,
>>>>
>>>> I have just finished setting up my first installation of Kolab and 
>>>> have
>>>> two quick questions.
>>>>
>>>> When I create a user, I do not see a Sent mail folder and a Drafts
>>>> folder.  For instance see my lm after logging into cyradm:
>>>>
>>>
>>> I think Kolab let the MUA create theses folder itself at first user 
>>> login,
>>> because Sent, Draft and other are not standard names !
>>> Depending  your Language, the name could change.
>>>
>>>
>>>
>>>> user/testuser/Calendar at farkinga.com (\HasNoChildren)
>>>> user/testuser/Contacts at farkinga.com (\HasNoChildren)
>>>> user/testuser/Notes at farkinga.com (\HasNoChildren)
>>>> user/testuser/Tasks at farkinga.com (\HasNoChildren)
>>>> user/testuser at farkinga.com (\HasChildren)
>>>>
>>>>
>>>> I have been searching through the templates and other files but 
>>>> have not
>>>> been able to find a way to have these folders autogenerated when I add
>>>> an email user.  I can add them afterwards, but I want my users to be
>>>> able to simply login and go.
>>>>
>>>
>>> They are already able to simply login and go !
>>>
>>>
>>>> My second question is, is there a template file where I can add 
>>>> multiple
>>>> certs for my IMAP/POP authentication?  Or can someone send me a quick
>>>> note on where I need to add them?  I want to be able to provide 
>>>> virtual
>>>> domain support and when a user goes to add their mail.domain.com 
>>>> account
>>>> to their client they won't get the wrong cert.
>>>>
>>>
>>> You can only attach ONE certificate to an (IP, port) couple !
>>>
>>> anyway, you can ave multiple Alternate Name in one certificate.
>>> For example you create a certificate using the
>>>
>>> commonName =myserver.name.com
>>>
>>> and add 2 alternate names
>>>
>>> DNS.1=myserver.name.com   # this is a good idea to have ce commonName
>>> in the list of alternate name
>>> DNS.2=webmail.domain1.com
>>> DNS.3=webmail.domain2.com
>>>
>>> But this is mostly true if you generate your certificate yourself, 
>>> because most
>>> of the cheap certificate provider will not let you add multiple
>>> alternate names !
>>>
>>>
>>>
>>>> Thanks for everything.
>>>>
>>>> Joseph
>>>>
>>>> _______________________________________________
>>>> 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 itsef-admin at brightsight.com  Thu Jan 15 09:07:11 2009
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Thu, 15 Jan 2009 09:07:11 +0100
Subject: Massive loss of events in enterprise35 client
In-Reply-To: <200901141832.50990.bernhard@intevation.de>
References: <200901141438.48428.itsef-admin@brightsight.com>
	<200901141832.50990.bernhard@intevation.de>
Message-ID: <200901150907.11972.itsef-admin@brightsight.com>

On Wednesday 14 January 2009 18:32:48 Bernhard Reiter wrote:
> On Mittwoch, 14. Januar 2009, ITSEF Admin wrote:
> > - $HOME is on NFS
>
> Your analysis should try to exclude this as a cause.
> Put the cache on a local disc if you can for this.

Would migrating to NFSv4 suffice? That's on the short term TODO list anyway...

BTW: The local cache did *not* help with proko2 - despite having the cache on 
the local hard drive (which causes all sorts of adminstrative headaches), 
we've seen spontaneous and large scale data losses in all DIMAP accounts 
(groupware and mail) every now and then.

Cheerio,

Thomas


From Roessler at FuH-E.de  Thu Jan 15 16:57:58 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Thu, 15 Jan 2009 16:57:58 +0100
Subject: Multiple instaces of kolabquotawarn - kolabquotawarn not terminating
Message-ID: <496F5D06.9060801@FuH-E.de>

Hallo everyone,

after setting up a new Kolab in an equally new openSuse 10.3 for testing 
I have noticed that kolabquotawarn will not terminate. So every 10 
minutes a new kolabquotawarninstance pops up:

(Snippet:)
| kolab    26409  0.0  4.9  14740 12728 ?        Ss   15:40   0:00
| /kolab/bin/perl /kolab/etc/kolab/kolabquotawarn
| kolab     7056  0.0  4.9  14744 12732 ?        Ss   15:50   0:00
| kolab/bin/perl /kolab/etc/kolab/kolabquotawarn
| kolab    20102  0.0  4.9  14744 12728 ?        Ss   16:00   0:00
| kolab/bin/perl /kolab/etc/kolab/kolabquotawarn
| kolab     1231  0.0  4.9  14744 12728 ?        Ss   16:10   0:00
| kolab/bin/perl /kolab/etc/kolab/kolabquotawarn
| kolab    14818  0.0  4.9  14740 12724 ?        Ss   16:20   0:00
| kolab/bin/perl /kolab/etc/kolab/kolabquotawarn
(etc. usw.).

I have increased the log level in kolab.globals to 10, but the messages 
do not really help me:
(from /var/log/messages:)
| Jan 15 16:40:01 kolab-test /usr/sbin/cron[9195]: (kolab) CMD
| /kolab/etc/kolab/kolabquotawarn)
| Jan 15 16:40:02 kolab-test kolabquotawarn: C: Reloading configuration
| Jan 15 16:40:03 kolab-test kolabquotawarn: C: Finished reloading
| configuration
| Jan 15 16:40:03 kolab-test kolabquotawarn: L: Starting up

Any hints, please? Kolab version is 2.2.0, yesterday from 
<http://ftp.gwdg.de/pub/linux/kolab/server/release/kolab-server-2.2.0/>.

Best regards, Christian


From troy at carpenter.cx  Thu Jan 15 20:56:53 2009
From: troy at carpenter.cx (Troy Carpenter)
Date: Thu, 15 Jan 2009 14:56:53 -0500
Subject: New native Windows and Mac OS Clients: first beta of Kontact
	Enterprise 4
In-Reply-To: <200901141732.44736.troy@carpenter.cx>
References: <200901131740.09986.bernhard@intevation.de>
	<200901142307.57760.bernhard@intevation.de>
	<200901141732.44736.troy@carpenter.cx>
Message-ID: <200901151456.53660.troy@carpenter.cx>

Overnight Kontact crashed.  When I re-ran the program, I noticed that most of 
my email was missing from the local store (using disconnected IMAP), and kmail 
started downloading all the emails again.  During that process I got the 
following error message:

Microsoft Visual C++ Runtime Library
Assertion Failed!
Program: C:\Program Files\Kontact\bin\kontact.exe
File: F:\kderoot-20081020\svn\branches...\kmfold...map.cpp
Line: 552

Expression: msg

abort, retry, ignore
--------------

Any of those selections causes Kontact to then crash.  If I click the debug 
button on the crash dialog, everything goes away.

The program will not work now.  I don't know if the data is corrupt, or if the 
program install has become messed up.

Troy
troy at carpenter.cx

-------------- 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/20090115/e5cbcfff/attachment.bin

From bernhard at intevation.de  Fri Jan 16 09:32:42 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 16 Jan 2009 09:32:42 +0100
Subject: New native Windows and Mac OS Clients: first beta of Kontact
	Enterprise 4
In-Reply-To: <200901141732.44736.troy@carpenter.cx>
References: <200901131740.09986.bernhard@intevation.de>
	<200901142307.57760.bernhard@intevation.de>
	<200901141732.44736.troy@carpenter.cx>
Message-ID: <200901160932.43301.bernhard@intevation.de>

Troy,

On Mittwoch, 14. Januar 2009, Troy Carpenter wrote:
> > > When I removed the 4.2rc1 install (which installed in C:\Program
> > > Files\KDE) and only used Kontact (in C:\Program Files\Kontact), then
> > > Kontact worked fine including all the date configuration settings.
> >
> > Were the crashes gone also?
>
> I haven't seen any lately, but the system is still syncing the emails. ?I
> have many thousands of emails on the server and prefer disconnected IMAP
> for "external" PCs like my laptop and my desktop at work.

let us know about crashes. If you are really cool, you could check the
problem tracker to see if we already have one like the one your are seeing.
I guess we should also publish short instructions how to get a gdb backtrace 
done in the wiki.kolab.org. Let me see about this. 

> > > One other problem I'm finding is that Kontact's Calendar doesn't keep
> > > my timezone setting. ?I've configured it for "Eastern Standard", but
> > > once I close the settings dialog and reopen it, I see that the timezone
> > > setting is not kept. ?That's causing all my events to be displayed in
> > > UTC time instead of my local time.
> >
> > We still have know problems with the timezone settings
>
> Well, for the calendar entries, Korganizer is somewhat useless without the
> timezone settings since all the entries show up in the wrong timezone. 

I've raised the priority of
kolab/issue2782 (timezones missing in Korganizer Settings for Time/Date)

> I'm 
> also not seeing all the events in the grid for the week and workweek views.
> ? If I switch to the month view, then I see the events. ?I think part of
> the problem is related to the timezone because Kontact thinks the event
> starts at 11:00pm and goes until 1:30 the next morning. ?In the month view
> that event stretches over Wednesday and Thursday. ?In the week views it is
> not there at all.

This seems like a different issue.
Ludwig will give this a spin!

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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090116/e546e17e/attachment.bin

From bernhard at intevation.de  Fri Jan 16 09:36:17 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 16 Jan 2009 09:36:17 +0100
Subject: New native Windows and Mac OS Clients: first beta of Kontact
	Enterprise 4
In-Reply-To: <200901151456.53660.troy@carpenter.cx>
References: <200901131740.09986.bernhard@intevation.de>
	<200901141732.44736.troy@carpenter.cx>
	<200901151456.53660.troy@carpenter.cx>
Message-ID: <200901160936.17916.bernhard@intevation.de>

Hi Troy,

On Donnerstag, 15. Januar 2009, Troy Carpenter wrote:
> Overnight Kontact crashed. ?When I re-ran the program, I noticed that most
> of my email was missing from the local store (using disconnected IMAP), and
> kmail started downloading all the emails again. 

arg, this sounds nasty. We had tried this for a large data store recently
and it worked with two attempts to sync it fully, so this is unexpected
and was running in our tests. Thanks for testing it and keeping up with the 
issues.

> During that process I got 
> the following error message:
>
> Microsoft Visual C++ Runtime Library
> Assertion Failed!
> Program: C:\Program Files\Kontact\bin\kontact.exe
> File: F:\kderoot-20081020\svn\branches...\kmfold...map.cpp
> Line: 552
>
> Expression: msg
>
> abort, retry, ignore
> --------------
>
> Any of those selections causes Kontact to then crash. ?If I click the debug
> button on the crash dialog, everything goes away.

You would need to run gdb before the crash and attach it to the process
to get a useful backtrace.
It is quite easy.

> The program will not work now. ?I don't know if the data is corrupt, or if
> the program install has become messed up.

What happens when you restart it?
Note that you can rebuild the index on folders if the index would come 
corrupted. Do a right click on the top folder and use the trouble shooting 
menu to rebuild the index. This sometimes helps.

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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090116/38894444/attachment.bin

From bernhard at intevation.de  Fri Jan 16 09:41:15 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 16 Jan 2009 09:41:15 +0100
Subject: Massive loss of events in enterprise35 client
In-Reply-To: <200901150907.11972.itsef-admin@brightsight.com>
References: <200901141438.48428.itsef-admin@brightsight.com>
	<200901141832.50990.bernhard@intevation.de>
	<200901150907.11972.itsef-admin@brightsight.com>
Message-ID: <200901160941.15819.bernhard@intevation.de>

On Donnerstag, 15. Januar 2009, ITSEF Admin wrote:
> On Wednesday 14 January 2009 18:32:48 Bernhard Reiter wrote:
> > On Mittwoch, 14. Januar 2009, ITSEF Admin wrote:
> > > - $HOME is on NFS
> >
> > Your analysis should try to exclude this as a cause.
> > Put the cache on a local disc if you can for this.
>
> Would migrating to NFSv4 suffice? 

No, as far as I can say. I suggest you put a few people on a local store 
for this analytic step to be completed. Also you could check your NFS 
performance and logs for general problems.

> BTW: The local cache did *not* help with proko2 - despite having the cache
> on the local hard drive (which causes all sorts of adminstrative
> headaches), we've seen spontaneous and large scale data losses in all DIMAP
> accounts (groupware and mail) every now and then.

I only have one clearly reported case of this with proko2 (over several years 
of usage). I do not quite remember, did you use the Debian packages build 
from KK? 

Note that with the fix of kolab/issue3196 (large number of appointments can 
lead to corrupt index and loss of events) we found a potential source of this
problem in all Kontact Kolab clients (proko2, enterprise35 and enterprise4).
We are very appy to frame any other issue that might remain, but again
with our experience proko2 has been very stable from that respect.
Enterprise35 is also running very nice since about 9 month.

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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090116/c8cf43c2/attachment.bin

From alex at DragonRising.com  Wed Jan 14 18:40:24 2009
From: alex at DragonRising.com (Alex Kent)
Date: Wed, 14 Jan 2009 17:40:24 +0000
Subject: Groups for shared folders
In-Reply-To: <mailman.292.1231950808.2113.kolab-users@kolab.org>
References: <mailman.292.1231950808.2113.kolab-users@kolab.org>
Message-ID: <496E2388.50701@DragonRising.com>

Hi Gunnar,

Thanks for your advice on using cyradm for seeing what was going on. I 
have found a work-around on 2.2.0 so that I'm able to use groups 
(distribution lists) to set permissions on shared folders.

As people have been stating, I didn't need to append 'group:' to the 
front of the email address used. The system did that for me fine.

With the web admin panel configured to give permission for 
UID/email/GID="staff-group at starfields.net" and  permissions='all':

localhost> lam shared.test at starfields.net
group:staff-group at starfields.net p
manager lrswipkxtecda

So clearly, the 'all' permissions weren't getting through to the imap 
server.

So I played with adding permissions manually to the web admin folder:

staff-group at starfields.net = "read/post"
staff-group at starfields.net = "append"
staff-group at starfields.net = "write"

And this now results in:

localhost> lam shared.test at starfields.net
group:staff-group at starfields.net lrswipted
manager lrswipkxtecda

This allows me to subscribe to the shared mail folder using thunderbird, 
and add mails to it. I'm guessing I should be able to assign a public 
email address to it in the normal way.

Thanks for everyones help in finding this work-around without me having 
to compile/upgrade anything!

Best wishes,

Alex

> ------------------------------------------------------------------------
>
> Subject:
> Re: Groups for shared folders
> From:
> Gunnar Wrobel <wrobel at pardus.de>
> Date:
> Wed, 14 Jan 2009 16:56:50 +0100
> To:
> kolab-users at kolab.org
>
> To:
> kolab-users at kolab.org
>
>
> Quoting Alex <lbf at dragonrising.com>:
>
>> Hi Bernhard,
>>
>> Thanks so much for the assistance, though I'm still getting stuck.
>>
>> I've:
>>
>> 1) Gone to distribution lists and create new list:
>>
>> List name: staff-group at mydomain.com
>> Members: alex.kent at mydomain.com
>> Hidden: unchecked
>>
>> 2) Created a shared folder:
>>
>> Folder name: staff-shared at mydomain.com
>> Folder type: mails
>> Permission for UID/email/GID: "group:staff-group at mydomain.com"
>> Permission='all'
>>
>> This generates the error:
>>
>> "No UID or GID group:staff-group at mydomain.com"
>>
>> It does accept the UID if I drop "group:" eg:
>
> Indeed, you don't need the "group:" prefix. The mail address is enough 
> to identify that this is a group.
>
> I tested that the whole procedure works fine on the recent 
> Kolab-Server-2.2.1-beta-1 release but I believe it should also work on 
> 2.2.0 as I don't think we changed anything in that area.
>
> Can you check if you see the right permissions on the shared folder 
> when using the cyradm tool (/kolab/bin/cyradm).
>
> This is the example session when I tested this:
>
> /kolab/bin/cyradm -u manager localhost
> Password:
> example.com> lm
> shared.shared at example.com (HasNoChildren)
> user/1 at example.com (HasNoChildren)
> user/2 at example.com (HasNoChildren)
> example.com> lam shared.shared at eample.com
> group:group at example.com lrswipteda
> anyone lrswipteda
> manager lrswipkxtecda
>
> You see that here the permission is marked with 
> "group:group at example.com lrswipteda". The "group:" prefix is cyrus 
> specific. Both users (1 at example.com com and 2 at example.com" are members 
> of "group at example.com". Both see the shared folder (tested via the 
> Kolab web client).
>
> If it still does not work for you I could test the same procedure on 
> 2.2.0.
>
> Cheers,
>
> Gunnar
>
>> Permission for UID/email/GID: "staff-group at mydomain.com" 
>> Permission='all'
>>
>> But this doesn't seem to give me "alex.kent at mydomain.com" access to the
>> folder.
>>
>> Am I getting closer?
>>
>> Best wishes,
>>
>> Alex Kent
>>
>>
>>
>>
>>>
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>> Subject:
>>> Re: Groups for shared folders
>>> From:
>>> Bernhard Reiter <bernhard at intevation.de>
>>> Date:
>>> Mon, 12 Jan 2009 15:32:56 +0100
>>> To:
>>> kolab-users at kolab.org
>>>
>>> To:
>>> kolab-users at kolab.org
>>>
>>>
>>> On Sonntag, 11. Januar 2009, Alex wrote:
>>>
>>>> I'm loving kolab, but need a few pointers giving a group of users 
>>>> access
>>>> to a shared folder. I can at the moment give access to everyone, 
>>>> nobody
>>>> or a specific person.
>>>>
>>>
>>> You can use server distribution lists.
>>> (Use the Webadmin for your Kolab Server go to "distribution list",
>>> add one with all your users and then use "group:YOURLISTNAME"
>>> as UID to give rights to for the folder.
>>>
>>>
>>>> Having searched kolab-users, I've seen a post which seemed to indicate
>>>> the following:
>>>>
>>>> 1) Create a new user of account type 'Group Account'
>>>>
>>>> 2) Add users to this group account by adding their UID to the
>>>> 'Email-Delegates' field of the group account.
>>>>
>>>
>>> Email-Delegates _only_ is about who can use the From: adress
>>> for the Account in question. So this does not help.
>>>
>>>
>>>> 3) Create a shared folder, giving the group accounts UID 'post'
>>>> permissions.
>>>>
>>>
>>> Post is about incoming emails, so wrong tree. :)
>>>
>>>
>>>> My Mozilla Thunderbird client does not see the new shared folder.
>>>> Am I on the right lines here?
>>>>
>>>
>>> You were'nt. ;)
>>>
>>>
>>>
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>


From funke at hiskp.uni-bonn.de  Fri Jan 16 09:59:46 2009
From: funke at hiskp.uni-bonn.de (Christian Funke)
Date: Fri, 16 Jan 2009 09:59:46 +0100
Subject: Weblient users default settings
Message-ID: <200901160959.47207.funke@hiskp.uni-bonn.de>


Hi all (and especially Gunnar),

does anyone know where the default settings for weblcient users are stored?
I want to disable the sidebar and set dimp as the default application for all 
users. What do I have to do to achieve this?

Greets

Christian Funke


From marko at mechtron.com.au  Fri Jan 16 11:01:24 2009
From: marko at mechtron.com.au (Mark Berndt)
Date: Fri, 16 Jan 2009 21:01:24 +1100
Subject: Multiple instaces of kolabquotawarn - kolabquotawarn not
	terminating
In-Reply-To: <496F5D06.9060801@FuH-E.de>
References: <496F5D06.9060801@FuH-E.de>
Message-ID: <200901162101.25017.marko@mechtron.com.au>

On Fri, 16 Jan 2009 02:57:58 am you wrote:
> Hallo everyone,
>
> after setting up a new Kolab in an equally new openSuse 10.3 for testing
> I have noticed that kolabquotawarn will not terminate. So every 10
> minutes a new kolabquotawarninstance pops up:
>
> (Snippet:)
>
> | kolab    26409  0.0  4.9  14740 12728 ?        Ss   15:40   0:00
> | /kolab/bin/perl /kolab/etc/kolab/kolabquotawarn
> | kolab     7056  0.0  4.9  14744 12732 ?        Ss   15:50   0:00
> | kolab/bin/perl /kolab/etc/kolab/kolabquotawarn
> | kolab    20102  0.0  4.9  14744 12728 ?        Ss   16:00   0:00
> | kolab/bin/perl /kolab/etc/kolab/kolabquotawarn
> | kolab     1231  0.0  4.9  14744 12728 ?        Ss   16:10   0:00
> | kolab/bin/perl /kolab/etc/kolab/kolabquotawarn
> | kolab    14818  0.0  4.9  14740 12724 ?        Ss   16:20   0:00
> | kolab/bin/perl /kolab/etc/kolab/kolabquotawarn
>
> (etc. usw.).
>
> I have increased the log level in kolab.globals to 10, but the messages
> do not really help me:
> (from /var/log/messages:)
>
> | Jan 15 16:40:01 kolab-test /usr/sbin/cron[9195]: (kolab) CMD
> | /kolab/etc/kolab/kolabquotawarn)
> | Jan 15 16:40:02 kolab-test kolabquotawarn: C: Reloading configuration
> | Jan 15 16:40:03 kolab-test kolabquotawarn: C: Finished reloading
> | configuration
> | Jan 15 16:40:03 kolab-test kolabquotawarn: L: Starting up
>
> Any hints, please? Kolab version is 2.2.0, yesterday from
> <http://ftp.gwdg.de/pub/linux/kolab/server/release/kolab-server-2.2.0/>.
>
> Best regards, Christian

I have seen this due to a crashed openldap.

I was running openpkg on debian and I got ldap error messages 
in /var/log/messages.

There was also a crashed instance of kolabd.

After stopping openpkg, I used ps -A and kill to remove kolabd, slapd and 
multiple kolabquotawarns.  

Restarting the openpkg system resumed normal operation.

-- 
High performance computer, software and automation systems for demanding 
applications
 
Mechtron Systems
ABN: 52 149 788 293
329 Old Canobolas Road NASHDALE NSW 2800
mob 04-2860-1801 ph 02-6365-3568 fx 02-6365-3578 


From Roessler at FuH-E.de  Fri Jan 16 12:57:51 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Fri, 16 Jan 2009 12:57:51 +0100
Subject: Multiple instaces of kolabquotawarn - kolabquotawarn
	not	terminating
In-Reply-To: <200901162101.25017.marko@mechtron.com.au>
References: <496F5D06.9060801@FuH-E.de>
	<200901162101.25017.marko@mechtron.com.au>
Message-ID: <4970763F.5050809@FuH-E.de>

Mark Berndt schrieb:

>> after setting up a new Kolab in an equally new openSuse 10.3 for testing
>> I have noticed that kolabquotawarn will not terminate. So every 10
>> minutes a new kolabquotawarninstance pops up:
>> Any hints, please? Kolab version is 2.2.0, yesterday from
>> <http://ftp.gwdg.de/pub/linux/kolab/server/release/kolab-server-2.2.0/>.
> I have seen this due to a crashed openldap.
> I was running openpkg on debian and I got ldap error messages 
> in /var/log/messages.
> [...] Restarting the openpkg system resumed normal operation.

Thanks for the hints! Anyway, I have started everything multiple times, 
without change. Then I noticed in the imap logs:

Jan 16 10:28:36 kolab-test <warning> imap[21482]: DBERROR db4: 
/kolab/var/imapd/mailboxes.db: unexpected file type or format
Jan 16 10:28:36 kolab-test <error> imap[21482]: DBERROR: opening 
/kolab/var/imapd/mailboxes.db: Invalid argument
Jan 16 10:28:36 kolab-test <error> imap[21482]: DBERROR: opening 
/kolab/var/imapd/mailboxes.db: cyrusdb error
Jan 16 10:28:36 kolab-test <error> imap[21482]: Fatal error: can't read 
mailboxes file
Jan 16 10:28:36 kolab-test <debug> imap[21488]: executed

Jan 16 10:30:12 kolab-test <debug> imap[29974]: executed
Jan 16 10:30:12 kolab-test <warning> imap[29974]: DBERROR db4: 
/kolab/var/imapd/annotations.db: unexpected file type or format
Jan 16 10:30:12 kolab-test <error> imap[29974]: DBERROR: opening 
/kolab/var/imapd/annotations.db: Invalid argument
Jan 16 10:30:12 kolab-test <error> imap[29974]: DBERROR: opening 
/kolab/var/imapd/annotations.db: cyrusdb error
Jan 16 10:30:12 kolab-test <error> imap[29974]: Fatal error: can't read 
annotations file

...got a bit agitated, and deleted /kolab/var/imapd/mailboxes.db and 
/kolab/var/imapd/mailboxes.db - as it was a very fresh install; surely 
not good for a working one.

Then I killed the kolabquotawarn instances manually, and (as it seems) 
the problem's gone.

But in any case I wonder why these two files got corrupted - as it was a 
very fresh install.

Best regards, Christian


From troy at carpenter.cx  Fri Jan 16 13:48:50 2009
From: troy at carpenter.cx (Troy Carpenter)
Date: Fri, 16 Jan 2009 07:48:50 -0500
Subject: New native Windows and Mac OS Clients: first beta of Kontact
	Enterprise 4
In-Reply-To: <200901160936.17916.bernhard@intevation.de>
References: <200901131740.09986.bernhard@intevation.de>
	<200901151456.53660.troy@carpenter.cx>
	<200901160936.17916.bernhard@intevation.de>
Message-ID: <200901160748.50802.troy@carpenter.cx>

On Friday 16 January 2009 03:36:17 am Bernhard Reiter wrote:
> Hi Troy,
>
> On Donnerstag, 15. Januar 2009, Troy Carpenter wrote:
> > Overnight Kontact crashed. ?When I re-ran the program, I noticed that
> > most of my email was missing from the local store (using disconnected
> > IMAP), and kmail started downloading all the emails again.
>
> arg, this sounds nasty. We had tried this for a large data store recently
> and it worked with two attempts to sync it fully, so this is unexpected
> and was running in our tests. Thanks for testing it and keeping up with the
> issues.

I have 1.2 gig over 80 folders in my IMAP account.  That's not counting shared 
folders.

> > During that process I got
> > the following error message:
> >
> > Microsoft Visual C++ Runtime Library
> > Assertion Failed!
> > Program: C:\Program Files\Kontact\bin\kontact.exe
> > File: F:\kderoot-20081020\svn\branches...\kmfold...map.cpp
> > Line: 552
> >
> > Expression: msg
> >
> > abort, retry, ignore
> > --------------
> >
> > Any of those selections causes Kontact to then crash. ?If I click the
> > debug button on the crash dialog, everything goes away.
>
> You would need to run gdb before the crash and attach it to the process
> to get a useful backtrace.
> It is quite easy.

I trust I can find instructions on how to do that somewhere.  It doesn't look 
like you've had time to post those instructions on the wiki page.

> > The program will not work now. ?I don't know if the data is corrupt, or
> > if the program install has become messed up.
>
> What happens when you restart it?
> Note that you can rebuild the index on folders if the index would come
> corrupted. Do a right click on the top folder and use the trouble shooting
> menu to rebuild the index. This sometimes helps.

Ok, that first statement was a bit overdone.  The program crashes when it 
starts the sync process with the IMAP server.  Since I stupidly set that to 
happen at startup, it crashes almost right away.  If I can stop the sync at 
startup, then I might be able to try rebuilding the index on the folders.

>
> Best,
> Bernhard

Thanks to you and everyone who is working on the windows port.  Although my 
main desktop machines at home and work run Kubuntu/KDE/Kontact in conjunction 
with my Kolab server, I still have a few laptops and users on Windows that 
have traditionally been cut off from the calendar & contact portions of my data 
without jumping though major hoops.

Troy

-------------- 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/20090116/fdd312ca/attachment.bin

From Roessler at FuH-E.de  Fri Jan 16 15:03:59 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Fri, 16 Jan 2009 15:03:59 +0100
Subject: Address book in Kolab admin webinterface: some entries not shown
In-Reply-To: <496B21C3.6010105@FuH-E.de>
References: <495E1810.3010701@FuH-E.de>	<4961D4F8.4090305@FuH-E.de>	<200901051219.41851.bernhard@intevation.de>	<49621EA3.3050805@FuH-E.de>	<20090107233708.79814unk1oe386m8@webmail.pardus.de>
	<496B21C3.6010105@FuH-E.de>
Message-ID: <497093CF.5010805@FuH-E.de>

Hallo everyone,

> Tested - that's not the cause, as it seems. As Bernhard mentioned, I 
> will now setup a truly fresh Kolab server for comparing purpose.

Well, I have done so, and the problem persists.

I have made a series of screen shots - anyway i fear these screenshots 
will not help much. apache/php-log has the same error messages.

<http://kartan.de/kolab/02_adressbuchverwaltung_noch_leer.png>
Here the empty adress book...

<http://kartan.de/kolab/03_adressbuchverwaltung_eintrag_vor_absenden.png>
Some data entered.

<http://kartan.de/kolab/04_adressbuchverwaltung_eintrag_erfolgreich_hinzu.png>
Directly after pressing the submit key...

<http://kartan.de/kolab/05_adressbuchverwaltung_eintrag_drin.png>
Entry accepted into (external) adress book...

<http://kartan.de/kolab/06_adressbuchverwaltung_keine_nummern.png>
Changing the entry, numbers missing.

Please let me know, if anybody can give me some hints. Of course I will 
give any needed information.

Best regards, Christian


From thomas at intevation.de  Fri Jan 16 16:57:38 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 16 Jan 2009 16:57:38 +0100
Subject: Kolab Server Hotfix 20090116
Message-ID: <20090116155738.GF10329.thomas@intevation.de>

This hotfix package fixes three issues in the groupware functions of
Kolab Server 2.2.0.  Users of 2.2 release candidates or beta versions
should upgrade to 2.2.0 first, users of Kolab Server 2.2.1-beta1 must
_not_ apply this hotfix since the issues are already fixed here.


kolab/issue3074 (Freebusy trigger fails for other users' calenders)
kolab/issue3236 (automatic acceptance, Attendee status email not
                 recognized by Outlook 2003)
kolab/issue3284 (Webclient or resmgr might send invitations that Outlook
                 2003 does not understand (unquoted CN with Umlauts))

Visit http://issues.kolab.org/ and enter the corresponding issue numbers
to view more details.


The hotfix is available from the Kolab download mirrors in the directory
server/release/kolab-server-2.2.0/hotfix-20090116
(see http://kolab.org/mirrors.html for a list of download mirrors)

While the mirrors are catching up, you can also get the hotfix files via rsync:
# rsync -tvP rsync://rsync.kolab.org/kolab/server/release/kolab-server-2.2.0/hotfix-20090116/iCalendar.php .
# rsync -tvP rsync://rsync.kolab.org/kolab/server/release/kolab-server-2.2.0/hotfix-20090116/kolab-issue3074.patch .

SHA1 sums:
5294eab5f874cfa4d76415a5e20a5122d5e86b3a  iCalendar.php
4eb16659513c07c38e4a7a7e5d1ed75d262ef3f6  kolab-issue3074.patch


The hotfix can be installed on your Kolab Server with the following
commands executed as user 'root' or 'kolab':

# cp iCalendar.php /kolab/lib/php/Horde/
# patch -s -p0 -d /kolab/lib/php < kolab-issue3074.patch

-- 
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: 206 bytes
Desc: not available
Url : http://kolab.org/pipermail/kolab-users/attachments/20090116/e767a289/attachment.bin

From albrecht.dress at lios-tech.com  Fri Jan 16 19:28:47 2009
From: albrecht.dress at lios-tech.com (Albrecht =?iso-8859-1?b?RHJl3w==?=)
Date: Fri, 16 Jan 2009 19:28:47 +0100
Subject: Kolab Server Hotfix 20090116
In-Reply-To: <20090116155738.GF10329.thomas@intevation.de> (from
	thomas@intevation.de on Fri Jan 16 16:57:38 2009)
Message-ID: <1232130527.6048.0@antares>

Hi Thomas:

Am 16.01.09 16:57 schrieb(en) Thomas Arendsen Hein:
> kolab/issue3074 (Freebusy trigger fails for other users' calenders)

Does it also fix issue #3208 which if I understand the comments in  
#3074 correctly might be somehow related?

Cheers, Albrecht.


P.S.: BTW, the GnuPG structure of the message you sent is broken.  It  
has the content-type

Content-Type: multipart/signed; micalg=SHA1;  
protocol="application/pgp-signature"; boundary="H8ygTp4AXg6deix2"

which violates RFC 3156, sect. 5 which states that

<quote>
    The "micalg" parameter for the "application/pgp-signature" protocol
    MUST contain exactly one hash-symbol of the format "pgp-<hash-
    identifier>", where <hash-identifier> identifies the Message
    Integrity Check (MIC) algorithm used to generate the signature.
    Hash-symbols are constructed from the text names registered in [1]  
or
    according to the mechanism defined in that document by converting  
the
    text name to lower case and prefixing it with the four characters
    "pgp-".

    Currently defined values are "pgp-md5", "pgp-sha1", "pgp-ripemd160",
    "pgp-md2", "pgp-tiger192", and "pgp-haval-5-160".
</quote>


From kloecker at kde.org  Fri Jan 16 20:54:28 2009
From: kloecker at kde.org (Ingo =?iso-8859-15?q?Kl=F6cker?=)
Date: Fri, 16 Jan 2009 20:54:28 +0100
Subject: New native Windows and Mac OS Clients: first beta of Kontact
	Enterprise 4
In-Reply-To: <200901160748.50802.troy@carpenter.cx>
References: <200901131740.09986.bernhard@intevation.de>
	<200901160936.17916.bernhard@intevation.de>
	<200901160748.50802.troy@carpenter.cx>
Message-ID: <200901162054.32263@thufir.ingo-kloecker.de>

On Friday 16 January 2009, Troy Carpenter wrote:
> On Friday 16 January 2009 03:36:17 am Bernhard Reiter wrote:
> > On Donnerstag, 15. Januar 2009, Troy Carpenter wrote:
> > > The program will not work now. ?I don't know if the data is
> > > corrupt, or if the program install has become messed up.
> >
> > What happens when you restart it?
> > Note that you can rebuild the index on folders if the index would
> > come corrupted. Do a right click on the top folder and use the
> > trouble shooting menu to rebuild the index. This sometimes helps.
>
> Ok, that first statement was a bit overdone.  The program crashes
> when it starts the sync process with the IMAP server.  Since I
> stupidly set that to happen at startup, it crashes almost right away.
>  If I can stop the sync at startup, then I might be able to try
> rebuilding the index on the folders.

Look for the file kmailrc and change the line
checkmail-startup=true
to
checkmail-startup=false


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/20090116/90442288/attachment.bin

From troy at carpenter.cx  Fri Jan 16 21:59:10 2009
From: troy at carpenter.cx (Troy Carpenter)
Date: Fri, 16 Jan 2009 15:59:10 -0500
Subject: New native Windows and Mac OS Clients: first beta of Kontact
	Enterprise 4
In-Reply-To: <200901162054.32263@thufir.ingo-kloecker.de>
References: <200901131740.09986.bernhard@intevation.de>
	<200901160748.50802.troy@carpenter.cx>
	<200901162054.32263@thufir.ingo-kloecker.de>
Message-ID: <200901161559.10972.troy@carpenter.cx>

I was going to reply to this on my Windows version of Kontact, but when I hit 
reply, the composer window was empty and didn't bring over any quoted text.  
So I had to move over to my Linux machine for the reply...is that a bug or 
have I missed some setting?

On Fri January 16 2009 02:54:28 pm Ingo Kl?cker wrote:
> On Friday 16 January 2009, Troy Carpenter wrote:
> > On Friday 16 January 2009 03:36:17 am Bernhard Reiter wrote:
> > > On Donnerstag, 15. Januar 2009, Troy Carpenter wrote:
> > > > The program will not work now. ?I don't know if the data is
> > > > corrupt, or if the program install has become messed up.
> > >
> > > What happens when you restart it?
> > > Note that you can rebuild the index on folders if the index would
> > > come corrupted. Do a right click on the top folder and use the
> > > trouble shooting menu to rebuild the index. This sometimes helps.
> >
> > Ok, that first statement was a bit overdone.  The program crashes
> > when it starts the sync process with the IMAP server.  Since I
> > stupidly set that to happen at startup, it crashes almost right away.
> >  If I can stop the sync at startup, then I might be able to try
> > rebuilding the index on the folders.
>
> Look for the file kmailrc and change the line
> checkmail-startup=true
> to
> checkmail-startup=false

Thanks.  I actually got Kontact to start and not crash this time...don't know 
if I really did anything.  In any case, I deleted my account and re-added it.  
I am currently syncing one folder at a time.  Every now and then the process 
seems to stall and I need to hit the minus sign in the status bar to jumpstart 
it again.

On to the tracker.  I've found the issue about the timezones (2782).  What 
should the settings be to create issues for the windows Kontact?  Is it the 
case that issues I'm finding exist in all versions?  I certainly don't see 
them in my KDE 4.2 install on Kubuntu (KMail 1.11.0).

Troy

-------------- 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/20090116/8abc4523/attachment-0001.bin

From LHendricks at austinent.com  Fri Jan 16 22:10:27 2009
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Fri, 16 Jan 2009 15:10:27 -0600
Subject: timezone issues kontact beta windows
Message-ID: <7907AE10BB50DD4F840E76527D27EF1902105113@entmail.domain.austinent.com>

OK I am using kontact for windows and having issues with timezone.  I
attempted to specify the timezone within the calendar setup and it lost my
kolab calendars and refused to save the timezone (when I close and then
reopen timezone is back to default which was actually showing GMT versions
of my appointments).

Thanks,
Lucas


From LHendricks at austinent.com  Fri Jan 16 22:19:34 2009
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Fri, 16 Jan 2009 15:19:34 -0600
Subject: nasty crash
Message-ID: <7907AE10BB50DD4F840E76527D27EF1902105114@entmail.domain.austinent.com>

Removing the kolab accounts from the configure kontact dialogue: kmail
accounts while running kontact connected to kolab 2 online imap causes an
error to pop up about too many files open which when you press OK just comes
right back.  I had to end task on the process to get kontact to shut down.

Lucas


From troy at carpenter.cx  Fri Jan 16 22:39:30 2009
From: troy at carpenter.cx (Troy Carpenter)
Date: Fri, 16 Jan 2009 16:39:30 -0500
Subject: timezone issues kontact beta windows
In-Reply-To: <7907AE10BB50DD4F840E76527D27EF1902105113@entmail.domain.austinent.com>
References: <7907AE10BB50DD4F840E76527D27EF1902105113@entmail.domain.austinent.com>
Message-ID: <200901161639.31125.troy@carpenter.cx>

On Fri January 16 2009 04:10:27 pm Lucas Hendricks wrote:
> OK I am using kontact for windows and having issues with timezone.  I
> attempted to specify the timezone within the calendar setup and it lost my
> kolab calendars and refused to save the timezone (when I close and then
> reopen timezone is back to default which was actually showing GMT versions
> of my appointments).
>
> Thanks,
> Lucas
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

We are talking about this already in the other thread, but the Kolab tracker 
url is: https://www.intevation.de/roundup/kolab/issue2782

It is currently an unresolved issue which makes the calendar useless for any 
timezone that is not UTC.

Troy

-------------- 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/20090116/ff51353c/attachment.bin

From thomas at intevation.de  Mon Jan 19 15:43:56 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Mon, 19 Jan 2009 15:43:56 +0100
Subject: Kolab Server Hotfix 20090116
In-Reply-To: <1232130527.6048.0@antares>
References: <20090116155738.GF10329.thomas@intevation.de>
	<1232130527.6048.0@antares>
Message-ID: <20090119144356.GC10616.thomas@intevation.de>

* Albrecht Dre? <albrecht.dress at lios-tech.com> [20090119 15:28]:
> Am 16.01.09 16:57 schrieb(en) Thomas Arendsen Hein:
> > kolab/issue3074 (Freebusy trigger fails for other users' calenders)
> 
> Does it also fix issue #3208 which if I understand the comments in  
> #3074 correctly might be somehow related?

They are related, but I do not think kolab/issue3208 is fixed with this.

> P.S.: BTW, the GnuPG structure of the message you sent is broken.  It  
> has the content-type
> 
> Content-Type: multipart/signed; micalg=SHA1;  
> protocol="application/pgp-signature"; boundary="H8ygTp4AXg6deix2"
> 
> which violates RFC 3156, sect. 5 which states that
> 
> <quote>
>     The "micalg" parameter for the "application/pgp-signature" protocol
...
>     Currently defined values are "pgp-md5", "pgp-sha1", "pgp-ripemd160",
>     "pgp-md2", "pgp-tiger192", and "pgp-haval-5-160".
> </quote>

You're right. This is fixed in a newer version of mutt, but I'm
still using an old mutt-ng with some patches I have to port to mutt
before switching back.

I did not notice problems with other clients yet, did you?

Regards,
Thomas Arendsen Hein

P.S.: Please answer to kolab-devel for issue3208 and in private mail
regarding the mutt-ng bug.

-- 
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 bernhard at intevation.de  Mon Jan 19 15:51:03 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 19 Jan 2009 15:51:03 +0100
Subject: backtraces for Kontact on Windows (was: New native Windows and Mac OS
	Clients: first beta of Kontact Enterprise 4)
In-Reply-To: <200901160748.50802.troy@carpenter.cx>
References: <200901131740.09986.bernhard@intevation.de>
	<200901160936.17916.bernhard@intevation.de>
	<200901160748.50802.troy@carpenter.cx>
Message-ID: <200901191551.06478.bernhard@intevation.de>

Troy,

On Freitag, 16. Januar 2009, Troy Carpenter wrote:
> > > Any of those selections causes Kontact to then crash. ?If I click the
> > > debug button on the crash dialog, everything goes away.
> >
> > You would need to run gdb before the crash and attach it to the process
> > to get a useful backtrace.
> > It is quite easy.
>
> I trust I can find instructions on how to do that somewhere. ?It doesn't
> look like you've had time to post those instructions on the wiki page.

I did not manage to put them up on Friday, but now I have added the following 
section to 
https://wiki.kolab.org/index.php/Kontact_for_Windows_(beta-huge-debug)#Hints :

 Backtrace for Crash reporting 
If you encounter crashes, a backtrace might help the developers to find the 
defect faster. There are some hints doing a backtrace with gdb on windows in 
https://techbase.kde.org/Development/Tutorials/Debugging/Debugging_on_MS_Windows#MinGW_debugging_hints

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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090119/30f1b2d4/attachment.bin

From ludwig.reiter at intevation.de  Mon Jan 19 16:27:40 2009
From: ludwig.reiter at intevation.de (Ludwig Reiter)
Date: Mon, 19 Jan 2009 16:27:40 +0100
Subject: nasty crash
In-Reply-To: <7907AE10BB50DD4F840E76527D27EF1902105114@entmail.domain.austinent.com>
References: <7907AE10BB50DD4F840E76527D27EF1902105114@entmail.domain.austinent.com>
Message-ID: <200901191627.41042.ludwig.reiter@intevation.de>



Am Freitag, 16. Januar 2009 22:19:34 schrieb Lucas Hendricks:
> Removing the kolab accounts from the configure kontact dialogue: kmail
> accounts while running kontact connected to kolab 2 online imap causes an
> error to pop up about too many files open which when you press OK just
> comes right back.  I had to end task on the process to get kontact to shut
> down.
I could reproduce this problem here and entered 
 kolab/issue3354 (Crash after deletion of an online account)
into the kolab  bugtracker.

https://www.intevation.de/roundup/kolab/issue3354

Ludwig
-- 
Intevation GmbH, Osnabr?ck
Firmensitz: Neuer Graben 17, 49074 Osnabr?ck
Registereintrag: Amtsgericht Osnabr?ck, HR B 18998
Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From alessio at skye.it  Mon Jan 19 18:18:36 2009
From: alessio at skye.it (Alessio Cecchi)
Date: Mon, 19 Jan 2009 18:18:36 +0100
Subject: rotate cyrmaster.log file
Message-ID: <200901191818.36412.alessio@skye.it>

Hi,

on my kolab server the cyrmaster.log is very very large:


mail:~# ls -lh /home/kolab/var/imapd/log/cyrmaster.log
-rw-rw-r-- 1 kolab-r kolab-r 6.2G Jan 19 
18:14 /home/kolab/var/imapd/log/cyrmaster.log

Why kolab/cyrus not rotate this file? Is a problem of my Kolab installation?

How can i disable debug on this file?

mail:~# tail -f /home/kolab/var/imapd/log/cyrmaster.log
Jan 19 18:05:27 mail <debug> master[13723]: about to exec /kolab/bin/pop3d
Jan 19 18:05:33 mail <debug> master[13724]: about to exec /kolab/bin/pop3d
Jan 19 18:05:46 mail <debug> master[9307]: process 12856 exited, status 0
Jan 19 18:06:02 mail <debug> master[13725]: about to exec /kolab/bin/imapd
Jan 19 18:08:23 mail <debug> master[9307]: process 13724 exited, status 0
Jan 19 18:10:04 mail <debug> master[13760]: about to exec /kolab/bin/lmtpd
Jan 19 18:12:10 mail <debug> master[9307]: process 13760 exited, status 0
Jan 19 18:12:13 mail <debug> master[13781]: about to exec /kolab/bin/lmtpd
Jan 19 18:14:30 mail <debug> master[9307]: process 13781 exited, status 0
Jan 19 18:14:42 mail <debug> master[13807]: about to exec /kolab/bin/lmtpd

Thanks
-- 
Alessio Cecchi is:
@ ILS -> http://www.linux.it/~alessice/
on LinkedIn -> http://www.linkedin.com/in/alessice
Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/
@ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it
@ LOLUG -> Socio http://www.lolug.net


From albrecht.dress at lios-tech.com  Mon Jan 19 19:52:52 2009
From: albrecht.dress at lios-tech.com (Albrecht =?iso-8859-1?b?RHJl3w==?=)
Date: Mon, 19 Jan 2009 19:52:52 +0100
Subject: Kolab Server Hotfix 20090116
In-Reply-To: <20090119144356.GC10616.thomas@intevation.de> (from
	thomas@intevation.de on Mon Jan 19 15:43:56 2009)
Message-ID: <1232391172.5236.1@antares>

Am 19.01.09 15:43 schrieb(en) Thomas Arendsen Hein:
> You're right. This is fixed in a newer version of mutt, but I'm still  
> using an old mutt-ng with some patches I have to port to mutt before  
> switching back.

The application seems to have more issues - it doesn't specify the  
charset of the text/plain part containing non-ascii chars...

> I did not notice problems with other clients yet, did you?

Yes, with balsa (see <http://balsa.gnome.org>) for which I wrote the  
encryption stuff (see  
<http://www.mynetcologne.de/~nc-dreszal/balsa/balsa23-secure-mail.html>,  
somewhat outdated) and which therefore is my favourite MUA.  I tried to  
follow rfc 3156, so I catch that broken header.

Cheers, Albrecht.


From aspineux at gmail.com  Mon Jan 19 22:11:22 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 19 Jan 2009 22:11:22 +0100
Subject: Multiple instaces of kolabquotawarn - kolabquotawarn not 
	terminating
In-Reply-To: <4970763F.5050809@FuH-E.de>
References: <496F5D06.9060801@FuH-E.de>
	<200901162101.25017.marko@mechtron.com.au> <4970763F.5050809@FuH-E.de>
Message-ID: <71fe4e760901191311j23560e87kec4ecd3e2e48c068@mail.gmail.com>

On Fri, Jan 16, 2009 at 12:57 PM, Christian R??ler <Roessler at fuh-e.de> wrote:
> Mark Berndt schrieb:
>
>>> after setting up a new Kolab in an equally new openSuse 10.3 for testing
>>> I have noticed that kolabquotawarn will not terminate. So every 10
>>> minutes a new kolabquotawarninstance pops up:
>>> Any hints, please? Kolab version is 2.2.0, yesterday from
>>> <http://ftp.gwdg.de/pub/linux/kolab/server/release/kolab-server-2.2.0/>.
>> I have seen this due to a crashed openldap.
>> I was running openpkg on debian and I got ldap error messages
>> in /var/log/messages.
>> [...] Restarting the openpkg system resumed normal operation.
>
> Thanks for the hints! Anyway, I have started everything multiple times,
> without change. Then I noticed in the imap logs:
>
> Jan 16 10:28:36 kolab-test <warning> imap[21482]: DBERROR db4:
> /kolab/var/imapd/mailboxes.db: unexpected file type or format

The message is "unexpected file type or format"

Did you restore mailboxes.db from another system ?
Or did you change anything in your imapd.conf in between ?


> Jan 16 10:28:36 kolab-test <error> imap[21482]: DBERROR: opening
> /kolab/var/imapd/mailboxes.db: Invalid argument
> Jan 16 10:28:36 kolab-test <error> imap[21482]: DBERROR: opening
> /kolab/var/imapd/mailboxes.db: cyrusdb error
> Jan 16 10:28:36 kolab-test <error> imap[21482]: Fatal error: can't read
> mailboxes file
> Jan 16 10:28:36 kolab-test <debug> imap[21488]: executed
>
> Jan 16 10:30:12 kolab-test <debug> imap[29974]: executed
> Jan 16 10:30:12 kolab-test <warning> imap[29974]: DBERROR db4:
> /kolab/var/imapd/annotations.db: unexpected file type or format
> Jan 16 10:30:12 kolab-test <error> imap[29974]: DBERROR: opening
> /kolab/var/imapd/annotations.db: Invalid argument
> Jan 16 10:30:12 kolab-test <error> imap[29974]: DBERROR: opening
> /kolab/var/imapd/annotations.db: cyrusdb error
> Jan 16 10:30:12 kolab-test <error> imap[29974]: Fatal error: can't read
> annotations file
>
> ...got a bit agitated, and deleted /kolab/var/imapd/mailboxes.db and
> /kolab/var/imapd/mailboxes.db - as it was a very fresh install; surely
> not good for a working one.
>
> Then I killed the kolabquotawarn instances manually, and (as it seems)
> the problem's gone.
>
> But in any case I wonder why these two files got corrupted - as it was a
> very fresh install.
>
> 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 aspineux at gmail.com  Mon Jan 19 22:41:55 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 19 Jan 2009 22:41:55 +0100
Subject: rotate cyrmaster.log file
In-Reply-To: <200901191818.36412.alessio@skye.it>
References: <200901191818.36412.alessio@skye.it>
Message-ID: <71fe4e760901191341i68e74f35l77d02ddc74850295@mail.gmail.com>

On Mon, Jan 19, 2009 at 6:18 PM, Alessio Cecchi <alessio at skye.it> wrote:
> Hi,
>
> on my kolab server the cyrmaster.log is very very large:
>
>
> mail:~# ls -lh /home/kolab/var/imapd/log/cyrmaster.log
> -rw-rw-r-- 1 kolab-r kolab-r 6.2G Jan 19
> 18:14 /home/kolab/var/imapd/log/cyrmaster.log
>
> Why kolab/cyrus not rotate this file? Is a problem of my Kolab installation?
>
> How can i disable debug on this file?
>
> mail:~# tail -f /home/kolab/var/imapd/log/cyrmaster.log
> Jan 19 18:05:27 mail <debug> master[13723]: about to exec /kolab/bin/pop3d
> Jan 19 18:05:33 mail <debug> master[13724]: about to exec /kolab/bin/pop3d
> Jan 19 18:05:46 mail <debug> master[9307]: process 12856 exited, status 0
> Jan 19 18:06:02 mail <debug> master[13725]: about to exec /kolab/bin/imapd
> Jan 19 18:08:23 mail <debug> master[9307]: process 13724 exited, status 0
> Jan 19 18:10:04 mail <debug> master[13760]: about to exec /kolab/bin/lmtpd
> Jan 19 18:12:10 mail <debug> master[9307]: process 13760 exited, status 0
> Jan 19 18:12:13 mail <debug> master[13781]: about to exec /kolab/bin/lmtpd
> Jan 19 18:14:30 mail <debug> master[9307]: process 13781 exited, status 0
> Jan 19 18:14:42 mail <debug> master[13807]: about to exec /kolab/bin/lmtpd
>

It should be rooled once a day. Are you sure it doesn't grow to 6Go in
only one day ?
What about  ?

# head /home/kolab/var/imapd/log/cyrmaster.log

look at /kolab/etc/rc.d/rc.imapd if everything looks fine.
Also look for older log files dates:

# ls -l  /home/kolab/var/imapd/log/cyrmaster.*

Regards

> Thanks
> --
> Alessio Cecchi is:
> @ ILS -> http://www.linux.it/~alessice/
> on LinkedIn -> http://www.linkedin.com/in/alessice
> Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/
> @ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it
> @ LOLUG -> Socio http://www.lolug.net
>
> _______________________________________________
> 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 Jan 20 09:38:01 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Tue, 20 Jan 2009 09:38:01 +0100
Subject: Multiple instaces of kolabquotawarn - kolabquotawarn not
	terminating
In-Reply-To: <71fe4e760901191311j23560e87kec4ecd3e2e48c068@mail.gmail.com>
References: <496F5D06.9060801@FuH-E.de>	
	<200901162101.25017.marko@mechtron.com.au>
	<4970763F.5050809@FuH-E.de>
	<71fe4e760901191311j23560e87kec4ecd3e2e48c068@mail.gmail.com>
Message-ID: <49758D69.80606@FuH-E.de>

Alain Spineux schrieb:

>> Jan 16 10:28:36 kolab-test <warning> imap[21482]: DBERROR db4:
>> /kolab/var/imapd/mailboxes.db: unexpected file type or format
> 
> The message is "unexpected file type or format"
> Did you restore mailboxes.db from another system ?
> Or did you change anything in your imapd.conf in between ?

No, it was a new, clean install for testing purposes. The only
noticeable thing could be that I ctrl-c'ed the bootstrap script once, as
I noticed I made a typo.

Best regards, Christian


From bernhard at intevation.de  Tue Jan 20 11:11:30 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 20 Jan 2009 11:11:30 +0100
Subject: Address book in Kolab admin webinterface: some entries not shown
In-Reply-To: <497093CF.5010805@FuH-E.de>
References: <495E1810.3010701@FuH-E.de> <496B21C3.6010105@FuH-E.de>
	<497093CF.5010805@FuH-E.de>
Message-ID: <200901201111.34351.bernhard@intevation.de>

On Freitag, 16. Januar 2009, Christian R??ler wrote:
> <http://kartan.de/kolab/06_adressbuchverwaltung_keine_nummern.png>
> Changing the entry, numbers missing.
>
> Please let me know, if anybody can give me some hints. Of course I will
> give any needed information.

I can reproduce it here with 2.2.0,
so we'll follow up on it.


-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090120/1bb2791b/attachment.bin

From Roessler at FuH-E.de  Tue Jan 20 11:51:05 2009
From: Roessler at FuH-E.de (=?ISO-8859-15?Q?Christian_R=F6=DFler?=)
Date: Tue, 20 Jan 2009 11:51:05 +0100
Subject: Address book in Kolab admin webinterface: some entries not shown
In-Reply-To: <200901201111.34351.bernhard@intevation.de>
References: <495E1810.3010701@FuH-E.de>
	<496B21C3.6010105@FuH-E.de>	<497093CF.5010805@FuH-E.de>
	<200901201111.34351.bernhard@intevation.de>
Message-ID: <4975AC99.7000404@FuH-E.de>

Bernhard Reiter schrieb:

> On Freitag, 16. Januar 2009, Christian R??ler wrote:
>> <http://kartan.de/kolab/06_adressbuchverwaltung_keine_nummern.png>
>> Changing the entry, numbers missing.
>
> I can reproduce it here with 2.2.0,
> so we'll follow up on it.

Many thanks! Please let me know if I can help in any way.

Best regards,
Christian


From alessio at skye.it  Tue Jan 20 12:50:13 2009
From: alessio at skye.it (Alessio Cecchi)
Date: Tue, 20 Jan 2009 12:50:13 +0100
Subject: rotate cyrmaster.log file
In-Reply-To: <71fe4e760901191341i68e74f35l77d02ddc74850295@mail.gmail.com>
References: <200901191818.36412.alessio@skye.it>
	<71fe4e760901191341i68e74f35l77d02ddc74850295@mail.gmail.com>
Message-ID: <4975BA75.20602@skye.it>

Alain Spineux ha scritto:
> On Mon, Jan 19, 2009 at 6:18 PM, Alessio Cecchi <alessio at skye.it> wrote:
>   
>> Hi,
>>
>> on my kolab server the cyrmaster.log is very very large:
>>
>>
>> mail:~# ls -lh /home/kolab/var/imapd/log/cyrmaster.log
>> -rw-rw-r-- 1 kolab-r kolab-r 6.2G Jan 19
>> 18:14 /home/kolab/var/imapd/log/cyrmaster.log
>>
>> Why kolab/cyrus not rotate this file? Is a problem of my Kolab installation?
>>
>> How can i disable debug on this file?
>>
>> mail:~# tail -f /home/kolab/var/imapd/log/cyrmaster.log
>> Jan 19 18:05:27 mail <debug> master[13723]: about to exec /kolab/bin/pop3d
>> Jan 19 18:05:33 mail <debug> master[13724]: about to exec /kolab/bin/pop3d
>> Jan 19 18:05:46 mail <debug> master[9307]: process 12856 exited, status 0
>> Jan 19 18:06:02 mail <debug> master[13725]: about to exec /kolab/bin/imapd
>> Jan 19 18:08:23 mail <debug> master[9307]: process 13724 exited, status 0
>> Jan 19 18:10:04 mail <debug> master[13760]: about to exec /kolab/bin/lmtpd
>> Jan 19 18:12:10 mail <debug> master[9307]: process 13760 exited, status 0
>> Jan 19 18:12:13 mail <debug> master[13781]: about to exec /kolab/bin/lmtpd
>> Jan 19 18:14:30 mail <debug> master[9307]: process 13781 exited, status 0
>> Jan 19 18:14:42 mail <debug> master[13807]: about to exec /kolab/bin/lmtpd
>>
>>     
>
> It should be rooled once a day. Are you sure it doesn't grow to 6Go in
> only one day ?
> What about  ?
>
> # head /home/kolab/var/imapd/log/cyrmaster.log
>
> look at /kolab/etc/rc.d/rc.imapd if everything looks fine.
> Also look for older log files dates:
>
> # ls -l  /home/kolab/var/imapd/log/cyrmaster.*
>
> Regards
>
>   
Hi Alain,

you have reason, the file is rotate every day:

mail:~# ls -lh /home/kolab/var/imapd/log/cyrmaster.log*
-rw-rw-r-- 1 kolab-r kolab-r  83K Jan 20 12:47 
/home/kolab/var/imapd/log/cyrmaster.log
-rw-rw-r-- 1 kolab-r kolab-r 6.2G Jan 20 00:00 
/home/kolab/var/imapd/log/cyrmaster.log.0
-rw-rw-r-- 1 kolab-r kolab-r  76K Jan 20 00:00 
/home/kolab/var/imapd/log/cyrmaster.log.1.bz2
-rw-rw-r-- 1 kolab-r kolab-r  94K Jan 16 00:00 
/home/kolab/var/imapd/log/cyrmaster.log.2.bz2
-rw-rw-r-- 1 kolab-r kolab-r  95K Jan  9 00:00 
/home/kolab/var/imapd/log/cyrmaster.log.3.bz2
-rw-rw-r-- 1 kolab-r kolab-r  81K Dec 29 00:00 
/home/kolab/var/imapd/log/cyrmaster.log.4.bz2
-rw-rw-r-- 1 kolab-r kolab-r  80K Dec 19 00:00 
/home/kolab/var/imapd/log/cyrmaster.log.5.bz2
-rw-rw-r-- 1 kolab-r kolab-r  78K Dec 13 00:00 
/home/kolab/var/imapd/log/cyrmaster.log.6.bz2
-rw-rw-r-- 1 kolab-r kolab-r  81K Dec  8 00:00 
/home/kolab/var/imapd/log/cyrmaster.log.7.bz2
-rw-rw-r-- 1 kolab-r kolab-r  91K Dec  3 00:00 
/home/kolab/var/imapd/log/cyrmaster.log.8.bz2
-rw-rw-r-- 1 kolab-r kolab-r  79K Nov 28 00:00 
/home/kolab/var/imapd/log/cyrmaster.log.9.bz2


6Gb was an only one day of logs.

Thanks


From s.kim at hia.rwth-aachen.de  Tue Jan 20 18:49:37 2009
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Tue, 20 Jan 2009 18:49:37 +0100
Subject: Groups for shared folders
In-Reply-To: <496E2388.50701@DragonRising.com>
References: <mailman.292.1231950808.2113.kolab-users@kolab.org>
	<496E2388.50701@DragonRising.com>
Message-ID: <49760EB1.5000907@hia.rwth-aachen.de>

Hi,

I was also looking for a solution for group access -but not to shared 
folders. Instead I would like to grant access to the calendar of 
ressource accounts. I'm still working on a Kolab 2.2.0 system (Debian 
Etch). When I try to enter the group or actually the distribution list 
on the fbview interface it is not added but it shows up in the cyradm 
interface with the "group:" prefix and seems to work right. Will this 
function be added to the fbview webinterface? Actually, there is an 
option to add groups but it is greyed out.

Best regards,
Saim





Alex Kent schrieb:
> <div class="moz-text-flowed" style="font-family: -moz-fixed">Hi Gunnar,
>
> Thanks for your advice on using cyradm for seeing what was going on. I 
> have found a work-around on 2.2.0 so that I'm able to use groups 
> (distribution lists) to set permissions on shared folders.
>
> As people have been stating, I didn't need to append 'group:' to the 
> front of the email address used. The system did that for me fine.
>
> With the web admin panel configured to give permission for 
> UID/email/GID="staff-group at starfields.net" and  permissions='all':
>
> localhost> lam shared.test at starfields.net
> group:staff-group at starfields.net p
> manager lrswipkxtecda
>
> So clearly, the 'all' permissions weren't getting through to the imap 
> server.
>
> So I played with adding permissions manually to the web admin folder:
>
> staff-group at starfields.net = "read/post"
> staff-group at starfields.net = "append"
> staff-group at starfields.net = "write"
>
> And this now results in:
>
> localhost> lam shared.test at starfields.net
> group:staff-group at starfields.net lrswipted
> manager lrswipkxtecda
>
> This allows me to subscribe to the shared mail folder using 
> thunderbird, and add mails to it. I'm guessing I should be able to 
> assign a public email address to it in the normal way.
>
> Thanks for everyones help in finding this work-around without me 
> having to compile/upgrade anything!
>
> Best wishes,
>
> Alex
>
>> ------------------------------------------------------------------------
>>
>> Subject:
>> Re: Groups for shared folders
>> From:
>> Gunnar Wrobel <wrobel at pardus.de>
>> Date:
>> Wed, 14 Jan 2009 16:56:50 +0100
>> To:
>> kolab-users at kolab.org
>>
>> To:
>> kolab-users at kolab.org
>>
>>
>> Quoting Alex <lbf at dragonrising.com>:
>>
>>> Hi Bernhard,
>>>
>>> Thanks so much for the assistance, though I'm still getting stuck.
>>>
>>> I've:
>>>
>>> 1) Gone to distribution lists and create new list:
>>>
>>> List name: staff-group at mydomain.com
>>> Members: alex.kent at mydomain.com
>>> Hidden: unchecked
>>>
>>> 2) Created a shared folder:
>>>
>>> Folder name: staff-shared at mydomain.com
>>> Folder type: mails
>>> Permission for UID/email/GID: "group:staff-group at mydomain.com"
>>> Permission='all'
>>>
>>> This generates the error:
>>>
>>> "No UID or GID group:staff-group at mydomain.com"
>>>
>>> It does accept the UID if I drop "group:" eg:
>>
>> Indeed, you don't need the "group:" prefix. The mail address is 
>> enough to identify that this is a group.
>>
>> I tested that the whole procedure works fine on the recent 
>> Kolab-Server-2.2.1-beta-1 release but I believe it should also work 
>> on 2.2.0 as I don't think we changed anything in that area.
>>
>> Can you check if you see the right permissions on the shared folder 
>> when using the cyradm tool (/kolab/bin/cyradm).
>>
>> This is the example session when I tested this:
>>
>> /kolab/bin/cyradm -u manager localhost
>> Password:
>> example.com> lm
>> shared.shared at example.com (HasNoChildren)
>> user/1 at example.com (HasNoChildren)
>> user/2 at example.com (HasNoChildren)
>> example.com> lam shared.shared at eample.com
>> group:group at example.com lrswipteda
>> anyone lrswipteda
>> manager lrswipkxtecda
>>
>> You see that here the permission is marked with 
>> "group:group at example.com lrswipteda". The "group:" prefix is cyrus 
>> specific. Both users (1 at example.com com and 2 at example.com" are 
>> members of "group at example.com". Both see the shared folder (tested 
>> via the Kolab web client).
>>
>> If it still does not work for you I could test the same procedure on 
>> 2.2.0.
>>
>> Cheers,
>>
>> Gunnar
>>
>>> Permission for UID/email/GID: "staff-group at mydomain.com" 
>>> Permission='all'
>>>
>>> But this doesn't seem to give me "alex.kent at mydomain.com" access to the
>>> folder.
>>>
>>> Am I getting closer?
>>>
>>> Best wishes,
>>>
>>> Alex Kent
>>>
>>>
>>>
>>>
>>>>
>>>> ------------------------------------------------------------------------ 
>>>>
>>>>
>>>> Subject:
>>>> Re: Groups for shared folders
>>>> From:
>>>> Bernhard Reiter <bernhard at intevation.de>
>>>> Date:
>>>> Mon, 12 Jan 2009 15:32:56 +0100
>>>> To:
>>>> kolab-users at kolab.org
>>>>
>>>> To:
>>>> kolab-users at kolab.org
>>>>
>>>>
>>>> On Sonntag, 11. Januar 2009, Alex wrote:
>>>>
>>>>> I'm loving kolab, but need a few pointers giving a group of users 
>>>>> access
>>>>> to a shared folder. I can at the moment give access to everyone, 
>>>>> nobody
>>>>> or a specific person.
>>>>>
>>>>
>>>> You can use server distribution lists.
>>>> (Use the Webadmin for your Kolab Server go to "distribution list",
>>>> add one with all your users and then use "group:YOURLISTNAME"
>>>> as UID to give rights to for the folder.
>>>>
>>>>
>>>>> Having searched kolab-users, I've seen a post which seemed to 
>>>>> indicate
>>>>> the following:
>>>>>
>>>>> 1) Create a new user of account type 'Group Account'
>>>>>
>>>>> 2) Add users to this group account by adding their UID to the
>>>>> 'Email-Delegates' field of the group account.
>>>>>
>>>>
>>>> Email-Delegates _only_ is about who can use the From: adress
>>>> for the Account in question. So this does not help.
>>>>
>>>>
>>>>> 3) Create a shared folder, giving the group accounts UID 'post'
>>>>> permissions.
>>>>>
>>>>
>>>> Post is about incoming emails, so wrong tree. :)
>>>>
>>>>
>>>>> My Mozilla Thunderbird client does not see the new shared folder.
>>>>> Am I on the right lines here?
>>>>>
>>>>
>>>> You were'nt. ;)
>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Kolab-users mailing list
>>> Kolab-users at kolab.org
>>> https://kolab.org/mailman/listinfo/kolab-users
>>>
>
>
> </div>
>


-- 
--------------------------------------------------------------------------
Dipl.-Ing. Saim Kim
Lehrstuhl fuer Medizinische Informationstechnik
Helmholtz-Institut fuer Biomedizinische Technik
RWTH Aachen
Pauwelsstr. 20, D-52074 Aachen
---
Web:   http://www.medit.hia.rwth-aachen.de/
Tel:   +49-(0)241-80 23218
Fax:   +49-(0)241-80 82442
email: s.kim at hia.rwth-aachen.de
-------------------------------------------------------------------------- 


From aspineux at gmail.com  Wed Jan 21 07:40:22 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Wed, 21 Jan 2009 07:40:22 +0100
Subject: Multiple instaces of kolabquotawarn - kolabquotawarn not 
	terminating
In-Reply-To: <49758D69.80606@FuH-E.de>
References: <496F5D06.9060801@FuH-E.de>
	<200901162101.25017.marko@mechtron.com.au> <4970763F.5050809@FuH-E.de>
	<71fe4e760901191311j23560e87kec4ecd3e2e48c068@mail.gmail.com>
	<49758D69.80606@FuH-E.de>
Message-ID: <71fe4e760901202240r10cb9d18h4528806cbaa38bbc@mail.gmail.com>

On Tue, Jan 20, 2009 at 9:38 AM, Christian R??ler <Roessler at fuh-e.de> wrote:
> Alain Spineux schrieb:
>
>>> Jan 16 10:28:36 kolab-test <warning> imap[21482]: DBERROR db4:
>>> /kolab/var/imapd/mailboxes.db: unexpected file type or format
>>
>> The message is "unexpected file type or format"
>> Did you restore mailboxes.db from another system ?
>> Or did you change anything in your imapd.conf in between ?
>
> No, it was a new, clean install for testing purposes. The only
> noticeable thing could be that I ctrl-c'ed the bootstrap script once, as
> I noticed I made a typo.

Here it'is !
The original openpkg config use skiplist instead of berkley !
Maybe imap started with th original config, and created the mailboxes.db file

Regards

>
> 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 aspineux at gmail.com  Wed Jan 21 07:50:02 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Wed, 21 Jan 2009 07:50:02 +0100
Subject: rotate cyrmaster.log file
In-Reply-To: <4975BA75.20602@skye.it>
References: <200901191818.36412.alessio@skye.it>
	<71fe4e760901191341i68e74f35l77d02ddc74850295@mail.gmail.com>
	<4975BA75.20602@skye.it>
Message-ID: <71fe4e760901202250h62f196cehca9c2941732290af@mail.gmail.com>

On Tue, Jan 20, 2009 at 12:50 PM, Alessio Cecchi <alessio at skye.it> wrote:
> Alain Spineux ha scritto:
>> On Mon, Jan 19, 2009 at 6:18 PM, Alessio Cecchi <alessio at skye.it> wrote:
>>
>>> Hi,
>>>
>>> on my kolab server the cyrmaster.log is very very large:
>>>
>>>
>>> mail:~# ls -lh /home/kolab/var/imapd/log/cyrmaster.log
>>> -rw-rw-r-- 1 kolab-r kolab-r 6.2G Jan 19
>>> 18:14 /home/kolab/var/imapd/log/cyrmaster.log
>>>
>>> Why kolab/cyrus not rotate this file? Is a problem of my Kolab installation?
>>>
>>> How can i disable debug on this file?
>>>
>>> mail:~# tail -f /home/kolab/var/imapd/log/cyrmaster.log
>>> Jan 19 18:05:27 mail <debug> master[13723]: about to exec /kolab/bin/pop3d
>>> Jan 19 18:05:33 mail <debug> master[13724]: about to exec /kolab/bin/pop3d
>>> Jan 19 18:05:46 mail <debug> master[9307]: process 12856 exited, status 0
>>> Jan 19 18:06:02 mail <debug> master[13725]: about to exec /kolab/bin/imapd
>>> Jan 19 18:08:23 mail <debug> master[9307]: process 13724 exited, status 0
>>> Jan 19 18:10:04 mail <debug> master[13760]: about to exec /kolab/bin/lmtpd
>>> Jan 19 18:12:10 mail <debug> master[9307]: process 13760 exited, status 0
>>> Jan 19 18:12:13 mail <debug> master[13781]: about to exec /kolab/bin/lmtpd
>>> Jan 19 18:14:30 mail <debug> master[9307]: process 13781 exited, status 0
>>> Jan 19 18:14:42 mail <debug> master[13807]: about to exec /kolab/bin/lmtpd
>>>
>>>
>>
>> It should be rooled once a day. Are you sure it doesn't grow to 6Go in
>> only one day ?
>> What about  ?
>>
>> # head /home/kolab/var/imapd/log/cyrmaster.log
>>
>> look at /kolab/etc/rc.d/rc.imapd if everything looks fine.
>> Also look for older log files dates:
>>
>> # ls -l  /home/kolab/var/imapd/log/cyrmaster.*
>>
>> Regards
>>
>>
> Hi Alain,
>
> you have reason, the file is rotate every day:
>
> mail:~# ls -lh /home/kolab/var/imapd/log/cyrmaster.log*
> -rw-rw-r-- 1 kolab-r kolab-r  83K Jan 20 12:47
> /home/kolab/var/imapd/log/cyrmaster.log
> -rw-rw-r-- 1 kolab-r kolab-r 6.2G Jan 20 00:00
> /home/kolab/var/imapd/log/cyrmaster.log.0
> -rw-rw-r-- 1 kolab-r kolab-r  76K Jan 20 00:00
> /home/kolab/var/imapd/log/cyrmaster.log.1.bz2
> -rw-rw-r-- 1 kolab-r kolab-r  94K Jan 16 00:00
> /home/kolab/var/imapd/log/cyrmaster.log.2.bz2
> -rw-rw-r-- 1 kolab-r kolab-r  95K Jan  9 00:00
> /home/kolab/var/imapd/log/cyrmaster.log.3.bz2
> -rw-rw-r-- 1 kolab-r kolab-r  81K Dec 29 00:00
> /home/kolab/var/imapd/log/cyrmaster.log.4.bz2
> -rw-rw-r-- 1 kolab-r kolab-r  80K Dec 19 00:00
> /home/kolab/var/imapd/log/cyrmaster.log.5.bz2
> -rw-rw-r-- 1 kolab-r kolab-r  78K Dec 13 00:00
> /home/kolab/var/imapd/log/cyrmaster.log.6.bz2
> -rw-rw-r-- 1 kolab-r kolab-r  81K Dec  8 00:00
> /home/kolab/var/imapd/log/cyrmaster.log.7.bz2
> -rw-rw-r-- 1 kolab-r kolab-r  91K Dec  3 00:00
> /home/kolab/var/imapd/log/cyrmaster.log.8.bz2
> -rw-rw-r-- 1 kolab-r kolab-r  79K Nov 28 00:00
> /home/kolab/var/imapd/log/cyrmaster.log.9.bz2
>
>
> 6Gb was an only one day of logs.


You should understand why, and fix it maybe.


>
> 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 bernhard at intevation.de  Wed Jan 21 09:46:16 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 21 Jan 2009 09:46:16 +0100
Subject: Groups for shared folders
In-Reply-To: <49760EB1.5000907@hia.rwth-aachen.de>
References: <mailman.292.1231950808.2113.kolab-users@kolab.org>
	<496E2388.50701@DragonRising.com>
	<49760EB1.5000907@hia.rwth-aachen.de>
Message-ID: <200901210946.16997.bernhard@intevation.de>

On Dienstag, 20. Januar 2009, Saim Kim wrote:
> I was also looking for a solution for group access -but not to shared
> folders. Instead I would like to grant access to the calendar of
> ressource accounts. I'm still working on a Kolab 2.2.0 system (Debian
> Etch). When I try to enter the group or actually the distribution list
> on the fbview interface it is not added but it shows up in the cyradm
> interface with the "group:" prefix and seems to work right.

Huh, die fbview interface should not change the directory contents,
nor anything else on the server. It should be "view only".

> Will this 
> function be added to the fbview webinterface? Actually, there is an
> option to add groups but it is greyed out.

A recommended model is to have a person be responsible for each resource 
account. (Means having the password as well).
This person shold use a regular client (Outlook with Connector, Kontact or the 
Webclient (currently in Beta)) to set the access permission on the folders
of the resource account.

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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090121/624da3d1/attachment.bin

From Roessler at FuH-E.de  Wed Jan 21 11:32:30 2009
From: Roessler at FuH-E.de (=?ISO-8859-15?Q?Christian_R=F6=DFler?=)
Date: Wed, 21 Jan 2009 11:32:30 +0100
Subject: Address book in Kolab admin webinterface: some entries not shown
In-Reply-To: <200901201111.34351.bernhard@intevation.de>
References: <495E1810.3010701@FuH-E.de>
	<496B21C3.6010105@FuH-E.de>	<497093CF.5010805@FuH-E.de>
	<200901201111.34351.bernhard@intevation.de>
Message-ID: <4976F9BE.7040802@FuH-E.de>

Bernhard Reiter schrieb:

> On Freitag, 16. Januar 2009, Christian R??ler wrote:
>> <http://kartan.de/kolab/06_adressbuchverwaltung_keine_nummern.png>
>> Changing the entry, numbers missing.
>> Please let me know, if anybody can give me some hints. Of course I will
>> give any needed information.
> I can reproduce it here with 2.2.0,
> so we'll follow up on it.

Thanks again for that; this is very reassuring, if i may say so.

I have noticed there is a bit of another issue, too. But for the 
possibility that these things are related I will mention it for the sake 
of completeness.

When importing entries from elsewhere I notice the last character from 
'Vorname' entry (How it's called: Christian name? First name?) missing - 
see appendes screen shots. (I know attachments are not well received; 
but I made them very small).

When looking into LDAP I notice in these entries that sn=cn:

| kolab:~ # ldapsearch  -LLL -b cn=external,dc=kolab,dc=lokal,dc=de
| cn="Alternate*" -h kolab
| dn: cn=ALTERNATE Computerversand
| GmbH,cn=external,dc=kolab,dc=lokal,dc=de
| objectClass: top
| objectClass: inetOrgPerson
| objectClass: kolabInetOrgPerson
| sn: ALTERNATE Computerversand GmbH
| cn: ALTERNATE Computerversand GmbH

If I make an entry with the kolab webfrontend this does not happen. 
Difference, notice givenName:

| kolab:~ # ldapsearch  -LLL -b cn=external,dc=kolab,dc=lokal,dc=de
| cn="Vorname*" -h kolab
| dn: cn=Vorname Nachname,cn=external,dc=kolab,dc=lokal,dc=de
| objectClass: top
| objectClass: inetOrgPerson
| objectClass: kolabInetOrgPerson
| sn: Nachname
| cn: Vorname Nachname
| givenName: Vorname

If I add an entry 'givenName' to the first example above, nothing 
changes. If I then enter the missing 'H' the entry shows correct; cn 
gets automatically doubled. Can anyone give me a hint how this behaviour 
can be circumvented? For example, if my data source just has a CN and a 
SN (which I cannot change), should I better enter sn->givenName and 
cn->sn, so Kolab constructs the cn?

Regards, Christian
-------------- n?chster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : 08_adressbuchverwaltung_Buchstabe_abgeschnitten_Liste.png
Dateityp    : image/png
Dateigr??e  : 3036 bytes
Beschreibung: nicht verf?gbar
URL         : http://kolab.org/pipermail/kolab-users/attachments/20090121/919134fe/08_adressbuchverwaltung_Buchstabe_abgeschnitten_Liste-0001.png
-------------- n?chster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : 09_adressbuchverwaltung_Buchstabe_abgeschnitten_Eintrag.png
Dateityp    : image/png
Dateigr??e  : 14367 bytes
Beschreibung: nicht verf?gbar
URL         : http://kolab.org/pipermail/kolab-users/attachments/20090121/919134fe/09_adressbuchverwaltung_Buchstabe_abgeschnitten_Eintrag-0001.png

From Roessler at FuH-E.de  Wed Jan 21 13:17:43 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Wed, 21 Jan 2009 13:17:43 +0100
Subject: Multiple instaces of kolabquotawarn - kolabquotawarn not
	terminating
In-Reply-To: <71fe4e760901202240r10cb9d18h4528806cbaa38bbc@mail.gmail.com>
References: <496F5D06.9060801@FuH-E.de>	
	<200901162101.25017.marko@mechtron.com.au>
	<4970763F.5050809@FuH-E.de>	
	<71fe4e760901191311j23560e87kec4ecd3e2e48c068@mail.gmail.com>	
	<49758D69.80606@FuH-E.de>
	<71fe4e760901202240r10cb9d18h4528806cbaa38bbc@mail.gmail.com>
Message-ID: <49771267.4040000@FuH-E.de>

Alain Spineux schrieb:

>>>> Jan 16 10:28:36 kolab-test <warning> imap[21482]: DBERROR db4:
>>>> /kolab/var/imapd/mailboxes.db: unexpected file type or format
>>> The message is "unexpected file type or format"
>>> Did you restore mailboxes.db from another system ?
>>> Or did you change anything in your imapd.conf in between ?
>> No, it was a new, clean install for testing purposes.
> The original openpkg config use skiplist instead of berkley !
> Maybe imap started with th original config, and created the mailboxes.db file

Yes, that seems plausible. Would that be something for the Kolab wiki?

Best regards,
Christian


From Roessler at FuH-E.de  Wed Jan 21 17:10:04 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Wed, 21 Jan 2009 17:10:04 +0100
Subject: Global sieve script possible?
Message-ID: <497748DC.1050501@FuH-E.de>

Good evening,

in the way of preparing a migration to Kolab I am wondering if it is
possible to use a global sieve script, which will be executed before
user's sieve scripts?

I was not able to find much in the net (eg. for example
<http://lists.andrew.cmu.edu/pipermail/cyrus-devel/2007-January/000239.html>) 

or in the Kolab documentation. So I would be thankful if anyone could
hint me whether this is possible, and if so, how.

Or would it suffice to put a (compiled, of course) sieve script into
/kolab/var/imapd/sieve/global?

Best regards,
Christian


From wrobel at pardus.de  Thu Jan 22 06:32:48 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 22 Jan 2009 06:32:48 +0100
Subject: Groups for shared folders
In-Reply-To: <496E2388.50701@DragonRising.com>
References: <mailman.292.1231950808.2113.kolab-users@kolab.org>
	<496E2388.50701@DragonRising.com>
Message-ID: <20090122063248.1384563hurznh4ow@webmail.pardus.de>

Quoting Alex Kent <alex at DragonRising.com>:

> Hi Gunnar,
>
> Thanks for your advice on using cyradm for seeing what was going on. I
> have found a work-around on 2.2.0 so that I'm able to use groups
> (distribution lists) to set permissions on shared folders.
>
> As people have been stating, I didn't need to append 'group:' to the
> front of the email address used. The system did that for me fine.
>
> With the web admin panel configured to give permission for
> UID/email/GID="staff-group at starfields.net" and  permissions='all':
>
> localhost> lam shared.test at starfields.net
> group:staff-group at starfields.net p
> manager lrswipkxtecda

The 'p' looks like only 'post' has been selected rather than 'all'. I  
fired up a 2.2.0 server now, checking the procedure again: Looks all  
fine.

Cheers,

Gunnar

>
> So clearly, the 'all' permissions weren't getting through to the imap
> server.
>
> So I played with adding permissions manually to the web admin folder:
>
> staff-group at starfields.net = "read/post"
> staff-group at starfields.net = "append"
> staff-group at starfields.net = "write"
>
> And this now results in:
>
> localhost> lam shared.test at starfields.net
> group:staff-group at starfields.net lrswipted
> manager lrswipkxtecda
>
> This allows me to subscribe to the shared mail folder using thunderbird,
> and add mails to it. I'm guessing I should be able to assign a public
> email address to it in the normal way.
>
> Thanks for everyones help in finding this work-around without me having
> to compile/upgrade anything!
>
> Best wishes,
>
> Alex
>
>> ------------------------------------------------------------------------
>>
>> Subject:
>> Re: Groups for shared folders
>> From:
>> Gunnar Wrobel <wrobel at pardus.de>
>> Date:
>> Wed, 14 Jan 2009 16:56:50 +0100
>> To:
>> kolab-users at kolab.org
>>
>> To:
>> kolab-users at kolab.org
>>
>>
>> Quoting Alex <lbf at dragonrising.com>:
>>
>>> Hi Bernhard,
>>>
>>> Thanks so much for the assistance, though I'm still getting stuck.
>>>
>>> I've:
>>>
>>> 1) Gone to distribution lists and create new list:
>>>
>>> List name: staff-group at mydomain.com
>>> Members: alex.kent at mydomain.com
>>> Hidden: unchecked
>>>
>>> 2) Created a shared folder:
>>>
>>> Folder name: staff-shared at mydomain.com
>>> Folder type: mails
>>> Permission for UID/email/GID: "group:staff-group at mydomain.com"
>>> Permission='all'
>>>
>>> This generates the error:
>>>
>>> "No UID or GID group:staff-group at mydomain.com"
>>>
>>> It does accept the UID if I drop "group:" eg:
>>
>> Indeed, you don't need the "group:" prefix. The mail address is enough
>> to identify that this is a group.
>>
>> I tested that the whole procedure works fine on the recent
>> Kolab-Server-2.2.1-beta-1 release but I believe it should also work on
>> 2.2.0 as I don't think we changed anything in that area.
>>
>> Can you check if you see the right permissions on the shared folder
>> when using the cyradm tool (/kolab/bin/cyradm).
>>
>> This is the example session when I tested this:
>>
>> /kolab/bin/cyradm -u manager localhost
>> Password:
>> example.com> lm
>> shared.shared at example.com (HasNoChildren)
>> user/1 at example.com (HasNoChildren)
>> user/2 at example.com (HasNoChildren)
>> example.com> lam shared.shared at eample.com
>> group:group at example.com lrswipteda
>> anyone lrswipteda
>> manager lrswipkxtecda
>>
>> You see that here the permission is marked with
>> "group:group at example.com lrswipteda". The "group:" prefix is cyrus
>> specific. Both users (1 at example.com com and 2 at example.com" are members
>> of "group at example.com". Both see the shared folder (tested via the
>> Kolab web client).
>>
>> If it still does not work for you I could test the same procedure on
>> 2.2.0.
>>
>> Cheers,
>>
>> Gunnar
>>
>>> Permission for UID/email/GID: "staff-group at mydomain.com"
>>> Permission='all'
>>>
>>> But this doesn't seem to give me "alex.kent at mydomain.com" access to the
>>> folder.
>>>
>>> Am I getting closer?
>>>
>>> Best wishes,
>>>
>>> Alex Kent
>>>
>>>
>>>
>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>> Subject:
>>>> Re: Groups for shared folders
>>>> From:
>>>> Bernhard Reiter <bernhard at intevation.de>
>>>> Date:
>>>> Mon, 12 Jan 2009 15:32:56 +0100
>>>> To:
>>>> kolab-users at kolab.org
>>>>
>>>> To:
>>>> kolab-users at kolab.org
>>>>
>>>>
>>>> On Sonntag, 11. Januar 2009, Alex wrote:
>>>>
>>>>> I'm loving kolab, but need a few pointers giving a group of users
>>>>> access
>>>>> to a shared folder. I can at the moment give access to everyone,
>>>>> nobody
>>>>> or a specific person.
>>>>>
>>>>
>>>> You can use server distribution lists.
>>>> (Use the Webadmin for your Kolab Server go to "distribution list",
>>>> add one with all your users and then use "group:YOURLISTNAME"
>>>> as UID to give rights to for the folder.
>>>>
>>>>
>>>>> Having searched kolab-users, I've seen a post which seemed to indicate
>>>>> the following:
>>>>>
>>>>> 1) Create a new user of account type 'Group Account'
>>>>>
>>>>> 2) Add users to this group account by adding their UID to the
>>>>> 'Email-Delegates' field of the group account.
>>>>>
>>>>
>>>> Email-Delegates _only_ is about who can use the From: adress
>>>> for the Account in question. So this does not help.
>>>>
>>>>
>>>>> 3) Create a shared folder, giving the group accounts UID 'post'
>>>>> permissions.
>>>>>
>>>>
>>>> Post is about incoming emails, so wrong tree. :)
>>>>
>>>>
>>>>> My Mozilla Thunderbird client does not see the new shared folder.
>>>>> Am I on the right lines here?
>>>>>
>>>>
>>>> You were'nt. ;)
>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Kolab-users mailing list
>>> Kolab-users at kolab.org
>>> https://kolab.org/mailman/listinfo/kolab-users
>>>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



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

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

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


----------------------------------------------------------------
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/20090122/b9a7150b/attachment.bin

From wrobel at pardus.de  Thu Jan 22 07:01:20 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 22 Jan 2009 07:01:20 +0100
Subject: Groups for shared folders
In-Reply-To: <49760EB1.5000907@hia.rwth-aachen.de>
References: <mailman.292.1231950808.2113.kolab-users@kolab.org>
	<496E2388.50701@DragonRising.com> <49760EB1.5000907@hia.rwth-aachen.de>
Message-ID: <20090122070120.1987265yokie04bo@webmail.pardus.de>

Quoting Saim Kim <s.kim at hia.rwth-aachen.de>:

> Hi,
>
> I was also looking for a solution for group access -but not to shared
> folders. Instead I would like to grant access to the calendar of
> ressource accounts. I'm still working on a Kolab 2.2.0 system (Debian
> Etch). When I try to enter the group or actually the distribution list
> on the fbview interface it is not added but it shows up in the cyradm
> interface with the "group:" prefix and seems to work right. Will this
> function be added to the fbview webinterface? Actually, there is an
> option to add groups but it is greyed out.

At the current state of planning this will be included. I just checked  
for Kolab-Server-2.2.1-beta-1 and the area is not greyed out anymore.  
But it does not work yet either. I'll have to check this:

https://www.intevation.de/roundup/kolab/issue3365

Cheers,

Gunna

>
> Best regards,
> Saim
>
>
>
>
>
> Alex Kent schrieb:
>> <div class="moz-text-flowed" style="font-family: -moz-fixed">Hi Gunnar,
>>
>> Thanks for your advice on using cyradm for seeing what was going on. I
>> have found a work-around on 2.2.0 so that I'm able to use groups
>> (distribution lists) to set permissions on shared folders.
>>
>> As people have been stating, I didn't need to append 'group:' to the
>> front of the email address used. The system did that for me fine.
>>
>> With the web admin panel configured to give permission for
>> UID/email/GID="staff-group at starfields.net" and  permissions='all':
>>
>> localhost> lam shared.test at starfields.net
>> group:staff-group at starfields.net p
>> manager lrswipkxtecda
>>
>> So clearly, the 'all' permissions weren't getting through to the imap
>> server.
>>
>> So I played with adding permissions manually to the web admin folder:
>>
>> staff-group at starfields.net = "read/post"
>> staff-group at starfields.net = "append"
>> staff-group at starfields.net = "write"
>>
>> And this now results in:
>>
>> localhost> lam shared.test at starfields.net
>> group:staff-group at starfields.net lrswipted
>> manager lrswipkxtecda
>>
>> This allows me to subscribe to the shared mail folder using
>> thunderbird, and add mails to it. I'm guessing I should be able to
>> assign a public email address to it in the normal way.
>>
>> Thanks for everyones help in finding this work-around without me
>> having to compile/upgrade anything!
>>
>> Best wishes,
>>
>> Alex
>>
>>> ------------------------------------------------------------------------
>>>
>>> Subject:
>>> Re: Groups for shared folders
>>> From:
>>> Gunnar Wrobel <wrobel at pardus.de>
>>> Date:
>>> Wed, 14 Jan 2009 16:56:50 +0100
>>> To:
>>> kolab-users at kolab.org
>>>
>>> To:
>>> kolab-users at kolab.org
>>>
>>>
>>> Quoting Alex <lbf at dragonrising.com>:
>>>
>>>> Hi Bernhard,
>>>>
>>>> Thanks so much for the assistance, though I'm still getting stuck.
>>>>
>>>> I've:
>>>>
>>>> 1) Gone to distribution lists and create new list:
>>>>
>>>> List name: staff-group at mydomain.com
>>>> Members: alex.kent at mydomain.com
>>>> Hidden: unchecked
>>>>
>>>> 2) Created a shared folder:
>>>>
>>>> Folder name: staff-shared at mydomain.com
>>>> Folder type: mails
>>>> Permission for UID/email/GID: "group:staff-group at mydomain.com"
>>>> Permission='all'
>>>>
>>>> This generates the error:
>>>>
>>>> "No UID or GID group:staff-group at mydomain.com"
>>>>
>>>> It does accept the UID if I drop "group:" eg:
>>>
>>> Indeed, you don't need the "group:" prefix. The mail address is
>>> enough to identify that this is a group.
>>>
>>> I tested that the whole procedure works fine on the recent
>>> Kolab-Server-2.2.1-beta-1 release but I believe it should also work
>>> on 2.2.0 as I don't think we changed anything in that area.
>>>
>>> Can you check if you see the right permissions on the shared folder
>>> when using the cyradm tool (/kolab/bin/cyradm).
>>>
>>> This is the example session when I tested this:
>>>
>>> /kolab/bin/cyradm -u manager localhost
>>> Password:
>>> example.com> lm
>>> shared.shared at example.com (HasNoChildren)
>>> user/1 at example.com (HasNoChildren)
>>> user/2 at example.com (HasNoChildren)
>>> example.com> lam shared.shared at eample.com
>>> group:group at example.com lrswipteda
>>> anyone lrswipteda
>>> manager lrswipkxtecda
>>>
>>> You see that here the permission is marked with
>>> "group:group at example.com lrswipteda". The "group:" prefix is cyrus
>>> specific. Both users (1 at example.com com and 2 at example.com" are
>>> members of "group at example.com". Both see the shared folder (tested
>>> via the Kolab web client).
>>>
>>> If it still does not work for you I could test the same procedure on
>>> 2.2.0.
>>>
>>> Cheers,
>>>
>>> Gunnar
>>>
>>>> Permission for UID/email/GID: "staff-group at mydomain.com"
>>>> Permission='all'
>>>>
>>>> But this doesn't seem to give me "alex.kent at mydomain.com" access to the
>>>> folder.
>>>>
>>>> Am I getting closer?
>>>>
>>>> Best wishes,
>>>>
>>>> Alex Kent
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> Subject:
>>>>> Re: Groups for shared folders
>>>>> From:
>>>>> Bernhard Reiter <bernhard at intevation.de>
>>>>> Date:
>>>>> Mon, 12 Jan 2009 15:32:56 +0100
>>>>> To:
>>>>> kolab-users at kolab.org
>>>>>
>>>>> To:
>>>>> kolab-users at kolab.org
>>>>>
>>>>>
>>>>> On Sonntag, 11. Januar 2009, Alex wrote:
>>>>>
>>>>>> I'm loving kolab, but need a few pointers giving a group of users
>>>>>> access
>>>>>> to a shared folder. I can at the moment give access to everyone,
>>>>>> nobody
>>>>>> or a specific person.
>>>>>>
>>>>>
>>>>> You can use server distribution lists.
>>>>> (Use the Webadmin for your Kolab Server go to "distribution list",
>>>>> add one with all your users and then use "group:YOURLISTNAME"
>>>>> as UID to give rights to for the folder.
>>>>>
>>>>>
>>>>>> Having searched kolab-users, I've seen a post which seemed to
>>>>>> indicate
>>>>>> the following:
>>>>>>
>>>>>> 1) Create a new user of account type 'Group Account'
>>>>>>
>>>>>> 2) Add users to this group account by adding their UID to the
>>>>>> 'Email-Delegates' field of the group account.
>>>>>>
>>>>>
>>>>> Email-Delegates _only_ is about who can use the From: adress
>>>>> for the Account in question. So this does not help.
>>>>>
>>>>>
>>>>>> 3) Create a shared folder, giving the group accounts UID 'post'
>>>>>> permissions.
>>>>>>
>>>>>
>>>>> Post is about incoming emails, so wrong tree. :)
>>>>>
>>>>>
>>>>>> My Mozilla Thunderbird client does not see the new shared folder.
>>>>>> Am I on the right lines here?
>>>>>>
>>>>>
>>>>> You were'nt. ;)
>>>>>
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Kolab-users mailing list
>>>> Kolab-users at kolab.org
>>>> https://kolab.org/mailman/listinfo/kolab-users
>>>>
>>
>>
>> </div>
>>
>
>
> --
> --------------------------------------------------------------------------
> Dipl.-Ing. Saim Kim
> Lehrstuhl fuer Medizinische Informationstechnik
> Helmholtz-Institut fuer Biomedizinische Technik
> RWTH Aachen
> Pauwelsstr. 20, D-52074 Aachen
> ---
> Web:   http://www.medit.hia.rwth-aachen.de/
> Tel:   +49-(0)241-80 23218
> Fax:   +49-(0)241-80 82442
> email: s.kim at hia.rwth-aachen.de
> --------------------------------------------------------------------------
>
> _______________________________________________
> 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/20090122/4ae3cdf5/attachment.bin

From wrobel at pardus.de  Thu Jan 22 07:08:40 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 22 Jan 2009 07:08:40 +0100
Subject: Groups for shared folders
In-Reply-To: <200901210946.16997.bernhard@intevation.de>
References: <mailman.292.1231950808.2113.kolab-users@kolab.org>
	<496E2388.50701@DragonRising.com> <49760EB1.5000907@hia.rwth-aachen.de>
	<200901210946.16997.bernhard@intevation.de>
Message-ID: <20090122070840.61866kcfk2qnwdwc@webmail.pardus.de>

Quoting Bernhard Reiter <bernhard at intevation.de>:

> On Dienstag, 20. Januar 2009, Saim Kim wrote:
>> I was also looking for a solution for group access -but not to shared
>> folders. Instead I would like to grant access to the calendar of
>> ressource accounts. I'm still working on a Kolab 2.2.0 system (Debian
>> Etch). When I try to enter the group or actually the distribution list
>> on the fbview interface it is not added but it shows up in the cyradm
>> interface with the "group:" prefix and seems to work right.
>
> Huh, die fbview interface should not change the directory contents,
> nor anything else on the server. It should be "view only".

This change has been requested with the implementation of the extended  
free/busy  concept. As we had only the Kolab web client supporting the  
required additional folder attributes we added the calendar management  
view from the client into fbview. If I remember it correctly you  
reasoned that not everybody would install/use the Kolab web client and  
so this functionality should be included in fbview as this was  
considered an integral part of the server.

Cheers,

Gunnar

>
>> Will this
>> function be added to the fbview webinterface? Actually, there is an
>> option to add groups but it is greyed out.
>
> A recommended model is to have a person be responsible for each resource
> account. (Means having the password as well).
> This person shold use a regular client (Outlook with Connector,  
> Kontact or the
> Webclient (currently in Beta)) to set the access permission on the folders
> of the resource account.
>
> 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
>



-- 
______ 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/20090122/d0d0714c/attachment-0001.bin

From wrobel at pardus.de  Thu Jan 22 07:35:03 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 22 Jan 2009 07:35:03 +0100
Subject: Address book in Kolab admin webinterface: some entries not shown
In-Reply-To: <4976F9BE.7040802@FuH-E.de>
References: <495E1810.3010701@FuH-E.de> <496B21C3.6010105@FuH-E.de>
	<497093CF.5010805@FuH-E.de> <200901201111.34351.bernhard@intevation.de>
	<4976F9BE.7040802@FuH-E.de>
Message-ID: <20090122073503.19054rpxzw0l2su8@webmail.pardus.de>

Quoting Christian R??ler <Roessler at FuH-E.de>:

> Bernhard Reiter schrieb:
>
>> On Freitag, 16. Januar 2009, Christian R??ler wrote:
>>> <http://kartan.de/kolab/06_adressbuchverwaltung_keine_nummern.png>
>>> Changing the entry, numbers missing.
>>> Please let me know, if anybody can give me some hints. Of course I will
>>> give any needed information.
>> I can reproduce it here with 2.2.0,
>> so we'll follow up on it.
>
> Thanks again for that; this is very reassuring, if i may say so.
>
> I have noticed there is a bit of another issue, too. But for the  
> possibility that these things are related I will mention it for the  
> sake of completeness.
>
> When importing entries from elsewhere I notice the last character  
> from 'Vorname' entry (How it's called: Christian name? First name?)  
> missing - see appendes screen shots. (I know attachments are not  
> well received; but I made them very small).
>
> When looking into LDAP I notice in these entries that sn=cn:
>
> | kolab:~ # ldapsearch  -LLL -b cn=external,dc=kolab,dc=lokal,dc=de
> | cn="Alternate*" -h kolab
> | dn: cn=ALTERNATE Computerversand
> | GmbH,cn=external,dc=kolab,dc=lokal,dc=de
> | objectClass: top
> | objectClass: inetOrgPerson
> | objectClass: kolabInetOrgPerson
> | sn: ALTERNATE Computerversand GmbH
> | cn: ALTERNATE Computerversand GmbH
>
> If I make an entry with the kolab webfrontend this does not happen.  
> Difference, notice givenName:
>
> | kolab:~ # ldapsearch  -LLL -b cn=external,dc=kolab,dc=lokal,dc=de
> | cn="Vorname*" -h kolab
> | dn: cn=Vorname Nachname,cn=external,dc=kolab,dc=lokal,dc=de
> | objectClass: top
> | objectClass: inetOrgPerson
> | objectClass: kolabInetOrgPerson
> | sn: Nachname
> | cn: Vorname Nachname
> | givenName: Vorname
>
> If I add an entry 'givenName' to the first example above, nothing  
> changes. If I then enter the missing 'H' the entry shows correct; cn  
> gets automatically doubled. Can anyone give me a hint how this  
> behaviour can be circumvented? For example, if my data source just  
> has a CN and a SN (which I cannot change), should I better enter  
> sn->givenName and cn->sn, so Kolab constructs the cn?

These are known issues:

https://www.intevation.de/roundup/kolab/issue752
https://www.intevation.de/roundup/kolab/issue1000

The kolab webadmin does parse the cn entry to generate the givenName.  
This it does by taking the cn from position 1 to the length of the cn  
minus the length of sn *minus 1* (for the space to be expected between  
givenName and sn). Not a very good solution and it needs fixing at  
some point.

Cheers,

Gunnar

>
> Regards, Christian
>



-- 
______ 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/20090122/2b1c128e/attachment.bin

From wrobel at pardus.de  Thu Jan 22 07:48:27 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 22 Jan 2009 07:48:27 +0100
Subject: Multiple instaces of kolabquotawarn - kolabquotawarn not
	terminating
In-Reply-To: <49771267.4040000@FuH-E.de>
References: <496F5D06.9060801@FuH-E.de>
	<200901162101.25017.marko@mechtron.com.au> <4970763F.5050809@FuH-E.de>
	<71fe4e760901191311j23560e87kec4ecd3e2e48c068@mail.gmail.com>
	<49758D69.80606@FuH-E.de>
	<71fe4e760901202240r10cb9d18h4528806cbaa38bbc@mail.gmail.com>
	<49771267.4040000@FuH-E.de>
Message-ID: <20090122074827.45334cgdl2dzuq4g@webmail.pardus.de>

Quoting Christian R??ler <Roessler at FuH-E.de>:

> Alain Spineux schrieb:
>
>>>>> Jan 16 10:28:36 kolab-test <warning> imap[21482]: DBERROR db4:
>>>>> /kolab/var/imapd/mailboxes.db: unexpected file type or format
>>>> The message is "unexpected file type or format"
>>>> Did you restore mailboxes.db from another system ?
>>>> Or did you change anything in your imapd.conf in between ?
>>> No, it was a new, clean install for testing purposes.
>> The original openpkg config use skiplist instead of berkley !
>> Maybe imap started with th original config, and created the  
>> mailboxes.db file
>
> Yes, that seems plausible. Would that be something for the Kolab wiki?

Certainly, but it is already in there and has been for a while already:

http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_IMAP#I_see_a_DBERROR_db4:_mailboxes.db:_unexpected_file_type_or_format_in_the_log_file

;)

Cheers,

Gunnar

>
> Best regards,
> Christian
>
> _______________________________________________
> 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/20090122/88964883/attachment.bin

From wrobel at pardus.de  Thu Jan 22 07:53:01 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 22 Jan 2009 07:53:01 +0100
Subject: Weblient users default settings
In-Reply-To: <200901160959.47207.funke@hiskp.uni-bonn.de>
References: <200901160959.47207.funke@hiskp.uni-bonn.de>
Message-ID: <20090122075301.15627fqc3n6d8pgc@webmail.pardus.de>

Quoting Christian Funke <funke at hiskp.uni-bonn.de>:

>
> Hi all (and especially Gunnar),
>
> does anyone know where the default settings for weblcient users are stored?
> I want to disable the sidebar and set dimp as the default application for all
> users. What do I have to do to achieve this?

The preferences for each application are stored within config/prefs.php.

So for base horde this would be:

/kolab/var/kolab/www/client/config/prefs.php (or  
/kolab/var/kolab/www/client/horde/prefs.php on systems < 2.2.1).

The system is quite versatile. You can set the default for all users  
and you can also lock the preference if you don't want your users to  
be able to change the default. If you need more advanced processing  
you can even have hook functions for each preference so that you can  
code the generation of default values.

I should definitely put this into the wiki soon.

Cheers,

Gunnar

>
> Greets
>
> Christian Funke
>
> _______________________________________________
> 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/20090122/db2f7b0d/attachment.bin

From wrobel at pardus.de  Thu Jan 22 07:59:19 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 22 Jan 2009 07:59:19 +0100
Subject: Global sieve script possible?
In-Reply-To: <497748DC.1050501@FuH-E.de>
References: <497748DC.1050501@FuH-E.de>
Message-ID: <20090122075919.98942iiy9i3hbnms@webmail.pardus.de>

Quoting Christian R??ler <Roessler at FuH-E.de>:

> Good evening,
>
> in the way of preparing a migration to Kolab I am wondering if it is
> possible to use a global sieve script, which will be executed before
> user's sieve scripts?
>
> I was not able to find much in the net (eg. for example
> <http://lists.andrew.cmu.edu/pipermail/cyrus-devel/2007-January/000239.html>)
>
> or in the Kolab documentation. So I would be thankful if anyone could
> hint me whether this is possible, and if so, how.
>
> Or would it suffice to put a (compiled, of course) sieve script into
> /kolab/var/imapd/sieve/global?

Hm, I had that question before and I think it does not work at the  
moment but it should be possible to get it to work. I currently lack  
the time to dig deeper into this. But could you try to generate the  
global sieve script as you described it and report your findings? It  
would be best to open an issue if it does not work. Then I have a  
reminder to look into this again.

Thanks!

Gunnar

>
> Best regards,
> Christian
>
> _______________________________________________
> 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/20090122/aa1f003b/attachment.bin

From bernhard at intevation.de  Thu Jan 22 09:27:49 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Thu, 22 Jan 2009 09:27:49 +0100
Subject: Groups for shared folders
In-Reply-To: <20090122070840.61866kcfk2qnwdwc@webmail.pardus.de>
References: <mailman.292.1231950808.2113.kolab-users@kolab.org>
	<200901210946.16997.bernhard@intevation.de>
	<20090122070840.61866kcfk2qnwdwc@webmail.pardus.de>
Message-ID: <200901220927.49938.bernhard@intevation.de>

On Donnerstag, 22. Januar 2009, Gunnar Wrobel wrote:
> Quoting Bernhard Reiter <bernhard at intevation.de>:
> > On Dienstag, 20. Januar 2009, Saim Kim wrote:
> >> I was also looking for a solution for group access -but not to shared
> >> folders. Instead I would like to grant access to the calendar of
> >> ressource accounts. I'm still working on a Kolab 2.2.0 system (Debian
> >> Etch). When I try to enter the group or actually the distribution list
> >> on the fbview interface it is not added but it shows up in the cyradm
> >> interface with the "group:" prefix and seems to work right.
> >
> > Huh, die fbview interface should not change the directory contents,
> > nor anything else on the server. It should be "view only".
>
> This change has been requested with the implementation of the extended ?
> free/busy ?concept. 

True, the pxfb-readable-for annotation should be writeable from fbview,
thanks for pointing this out.

But I think this issue is about setting the ACLs from fbview
which is not necessary and should be done from the client.

> As we had only the Kolab web client supporting the ? 
> required additional folder attributes we added the calendar management ?
> view from the client into fbview. 

Yes, for pxfb-readable-for only.

> If I remember it correctly you ? 
> reasoned that not everybody would install/use the Kolab web client and ?
> so this functionality should be included in fbview as this was ?
> considered an integral part of the server.

It is true, the current Outlook connectors cannot set pxfb-readable-for
as far as I know.

-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090122/692ed065/attachment.bin

From Roessler at FuH-E.de  Thu Jan 22 13:15:09 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Thu, 22 Jan 2009 13:15:09 +0100
Subject: Kolab Mail archiving - software, methods, experiences?
Message-ID: <4978634D.7000801@FuH-E.de>

Hallo everyone,

I am in need for mail archiving, that means that every incoming and 
outgoing mail has to be archived somewhere.

Now I am a bit overwhelmed with all the possibilities, and so I want to 
ask the list in which ways this has already been solved, which software 
(if so) is being used, and so on.

Several possibilities spring to my mind:

- postfix (main.cf) always_bcc=archiv at kolab.lokal.tld. Funny, but not 
unexpected (as each mail goes three times through postfix, if I am not 
mistaken) is that each mail goes threefold to the archive / gets 
tripled. Does anyone know an easy way around that?

- has anyone integrated Octant Opensources OMA Open Mail Archive 
<http://octant.org> into Kolab, and if so, which are the experiences?

- or perhaps Inovox-Mailarchivierungssoftware, 
<http://www.inovox.de/email-archivierung>, 
<http://sourceforge.net/projects/emailarchiving/>? Experiences?

- Or perhaps another way? Another software, proxy or more simple 
solution? In short, how is this solved elsewhere?

Best regards,
Christian


From harkin.as at gmail.com  Wed Jan 21 22:43:33 2009
From: harkin.as at gmail.com (Harkin Banks)
Date: Wed, 21 Jan 2009 16:43:33 -0500
Subject: Horde SyncML and Kolab 2.2.1 Beta 1
Message-ID: <6B1DF837B339408DA30400526954E9A7@mdmbxp>

I am having problems getting sync (via Horde) to work with every plugin I've 
tried, which means Funambol (in each case) for Outlook, iPhone, and 
BlackBerry.  One possible issue is that there is, according to a discussion 
we are having on the Horde sync mailing list, that there should be an option 
under Options  > Address Book that allows one to specify which Address Book 
is to be used for sync.  No such options appears.

Any thoughts are much appreciated.


From itsef-admin at brightsight.com  Thu Jan 22 16:30:28 2009
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Thu, 22 Jan 2009 16:30:28 +0100
Subject: Cannot get freebusy to work in Kontact
In-Reply-To: <200812101746.10487.itsef-admin@brightsight.com>
References: <200810081024.43359.itsef-admin@brightsight.com>
	<200812101714.32022.itsef-admin@brightsight.com>
	<200812101746.10487.itsef-admin@brightsight.com>
Message-ID: <200901221630.28459.itsef-admin@brightsight.com>

On Wednesday 10 December 2008 17:46:10 ITSEF Admin wrote:
> Ok, it's definitely some problem in the interaction with KWallet. If I
> enter username *and* password in the freebusy config dialog
> (Settings-.Configure Calendar->Freebusy->Retrieve), it works. I know for
> certain that I used to get a KWallet dialog the first time I tried, upon
> which I could add the password to KWallet and be happy. However, for some
> odd reasons, Kontact seems to ignore KWallet completely right now - no idea
> why.

I'm back to square one. Despite this "fix" above, it stopped working again. 
Like before, my kontact just fails to send out the username.

Upon closer study of the apache logs on our Kolab server, however, I noticed 
something else: With those accounts where freebusy actually works, I see 
this:

[...]
HOST1.DOM.AIN - - [22/Jan/2009:11:10:17 
+0100] "GET /freebusy/NAME%40DOM.AIN.ifb HTTP/1.1" 401 489
HOST1.DOM.AIN - CLIENTUSER at DOM.AIN [22/Jan/2009:11:10:18 
+0100] "GET /freebusy/NAME%40DOM.AIN.ifb HTTP/1.1" 200 10320
[...]

i.e. the client gets a "401" first ("Authentication required"), retries with 
the username (and I suppose password) supplied, which results in "200" 
("Success").

When *I* try it with my client/account, the exchange looks like this:

[...]
HOST2.DOM.AIN - - [22/Jan/2009:12:26:28 +0100] "GET /freebusy/NAME2.ifb 
HTTP/1.1" 403 770
[...]

i.e. the server sends a "403" ("Forbidden") right away - my client doesn't 
even get the "401" (which, in turn, I expect to be the reason why the user 
name is never sent). Does that maybe ring a bell with someone?

@Bernhard: I even thought about wiping .kde (or at least all kontact related 
rc's in config) and starting afresh with my account - but I'm using a lot of 
custom settings (folder icons, views, etc.pp.) for the three accounts I 
have - restoring this manually would be quite painful... :-/

Cheerio,

Thomas


From itsef-admin at brightsight.com  Thu Jan 22 16:46:08 2009
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Thu, 22 Jan 2009 16:46:08 +0100
Subject: SOLVED? Re: Cannot get freebusy to work in Kontact
In-Reply-To: <200901221630.28459.itsef-admin@brightsight.com>
References: <200810081024.43359.itsef-admin@brightsight.com>
	<200812101746.10487.itsef-admin@brightsight.com>
	<200901221630.28459.itsef-admin@brightsight.com>
Message-ID: <200901221646.08095.itsef-admin@brightsight.com>

On Thursday 22 January 2009 16:30:28 ITSEF Admin wrote:
[...]
> When *I* try it with my client/account, the exchange looks like this:
>
> [...]
> HOST2.DOM.AIN - - [22/Jan/2009:12:26:28 +0100] "GET /freebusy/NAME2.ifb
> HTTP/1.1" 403 770
> [...]
>
> i.e. the server sends a "403" ("Forbidden") right away - my client doesn't
> even get the "401" (which, in turn, I expect to be the reason why the user
> name is never sent). Does that maybe ring a bell with someone?
[...]

This finally ignited some dim bulb somewhere in my mind - I had been wondering 
about some password dialogues coming up asking for a password for some SSL 
certificate. Hence, I had a look at the "kssl*" files in 
~/.kde/share/config - and moved them out of the way, then restarted kontact.
Now freebusy works again... Apparently, some old cert had sneaked in there 
(we've been busy with SSL on our Kolab server some months back), causing the 
SSL connection to fail - resulting in the "403". Now, after I removed that 
stuff, my client gets a "401" initially, like all others.

I hope this is of help to anybody...

@Bernhard: Is it worthwhile to file a "wish" ticket with the request for 
better error reporting in cases like this? If kontact had reported something 
back about the error codes from the server, the bell might have started 
ringing earlier... :-}

Cheerio,

Thomas


From itsef-admin at brightsight.com  Thu Jan 22 17:33:43 2009
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Thu, 22 Jan 2009 17:33:43 +0100
Subject: Another free/busy odditiy - Kontact vs. DNS?
Message-ID: <200901221733.43555.itsef-admin@brightsight.com>

Hi all,

while I was resolving my own problem with Kontact and free/busy (see list 
archives... it was a problem with a SSL certificate), several other users 
came to me also with free/busy problems. Again, free/busy simply did not 
work - and I was not even able to find any requests from them in the server 
logs. After some experimenting I finally found the solution for this problem 
as well: Contrary to our other users (and myself), the users with the problem 
had their FreeBusyRetrieveUrl set to: "https://KOLABSERVER/freebusy/"
All other users have "https://KOLABSERVER.DOM.AIN/freebusy/". To my great 
surprise, only the second version (with the full domain) works. This is 
especially puzzling, as "host KOLABSERVER" yields the same result as "host 
KOLABSERVER.DOM.AIN" on the command line. Same with Konqueror - it does not 
matter whether I enter the domain or not, Konqueror does display the correct 
page on our Kolab server. Kontact seems to be the only exception.

Does anybody have an idea why this is? Should I file a bugreport?

Regards,

Thomas


From devgioiatech at gmail.com  Thu Jan 22 21:03:02 2009
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Thu, 22 Jan 2009 21:03:02 +0100
Subject: multiple kolab installation question :(
Message-ID: <d53357b70901221203q4b3c8ac3le80cf06b3bd7052@mail.gmail.com>

hi all,

i've multiple sites interconnected through a VPN and i have an
internet entry point only in site1

i've multiple kolab installation on site1 site2 site3 site4

on site1 i've Kolab Master, and two kolab slave

i want to one of this slave as webclient only for internet use for ALL
slave of that master.

For example:

MASTER is KOLAB-MASTER.demo.tst (on site1)

slave for webmail is webmail.demo.tst (on site1)

slave severs are: kolab.site1.demo.tst kolab.site2.demo.tst
kolab.site3.demo.tst kolab.site4.demo.tst

mail domains are: site1.demo.tst site2.demo.tst site3.demo.tst site4.demo.tst

can i access all mailbox for all slave server through webmail server?

Then, i need to setting up each slave with samba integration
(http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy)
so every openLDAP structure must be indipendent from each other . Is
it possible?


                 		         ---------------------------
                                 	| webmail.demo.tst | (on site1)
                 		         ---------------------------
		                                      |
                                                      |
             ---------------------------------------------------------------------------------------------------------------------------------------
            |                                        |
              |                            |
       |
            |                                        |
              |                            |
       |
 ----------------------------------------            |
              |                            |
       |
| KOLAB-MASTER.demo.tst |          |                               |
                         |                                  |
 ----------------------------------------            |
              |                            |
       |
    (on site1)                                   |
           |                            |
    |
                                    -------------------------------
--------------------------------   --------------------------------
--------------------------------
                                   | kolab.site1.demo.tst |  |
kolab.site2.demo.tst |  | kolab.site3.demo.tst |   |
kolab.site4.demo.tst |
                                    -------------------------------
--------------------------------    -------------------------------
 -------------------------------

If this way is not possible, is there a way to use a webmail client
for multiple indipendent kolab installation...

Thanks in advance.


From johnm at advocap.org  Thu Jan 22 23:15:37 2009
From: johnm at advocap.org (John McMonagle)
Date: Thu, 22 Jan 2009 16:15:37 -0600
Subject: kolab ldap migration questions.
Message-ID: <200901221615.38062.johnm@advocap.org>

Our current mail server is using debian sarge with postfix cyrus and openldap.

Most our servers are debian etch and am starting to switch to lenny.
Have many questions but for now will stick to my ldap concerns.
Currently have 1 master ldap server and 6 slaves at 5 sites.
Primarily using ldap account manager for management.
We are primarily linux but do run nt domain via samba, ldap and nitrobit.
Am using a combination slurp and sync replication.
Slowly switching to sync replication as I do upgrades.

After dealing with merging all the schemas and acls, was thinking I would 
import the base kolab records into our ldap.

Here is  one of our current records:
dn: uid=bradb,ou=People,dc=advocap,dc=org
uid: bradb
sambaSID: S-1-5-21-3708734655-3086812103-629500990-53054
cn: Brad Bingham
sambaLMPassword: xxxx
sambaNTPassword: xxxx
sambaPwdLastSet: 1159476966
sambaKickoffTime: 1893513600
sambaAcctFlags: [XU         ]
sambaHomeDrive: U:
sambaPrimaryGroupSID: S-1-5-21-3708734655-3086812103-629500990-5047
sambaDomainName: ADVOCAP
objectClass: sambaSamAccount
objectClass: shadowAccount
objectClass: posixAccount
objectClass: inetOrgPerson
shadowMin: 1
shadowMax: 99999
shadowWarning: 10
shadowInactive: 10
shadowExpire: 22278
shadowLastChange: 13419
uidNumber: 26027
gidNumber: 2023
homeDirectory: /home/bradb
loginShell: /bin/bash
givenName: Brad
mail: bradb at advocap.org
sn: Bingham
structuralObjectClass: inetOrgPerson
entryUUID: 838796c6-e37f-102a-9af5-ccd5da83767c
creatorsName: cn=Manager,dc=advocap,dc=org
createTimestamp: 20060928205610Z
userPassword:: xxxxxxx
entryCSN: 20061005160616Z#000001#00#000000
modifiersName: uid=bradb,ou=People,dc=advocap,dc=org
modifyTimestamp: 20061005160616Z

From kolab test:
dn: cn=Brad Bingham,dc=advocap,dc=org
objectClass: top
objectClass: inetOrgPerson
objectClass: kolabInetOrgPerson
sn: Bingham
cn: Brad Bingham
givenName: Brad
userPassword:: xxxxx
mail: bradb at advocap.org
uid: bradb at advocap.org
kolabHomeServer: mailtest.advocap.org
kolabInvitationPolicy: ACT_MANUAL
structuralObjectClass: inetOrgPerson
entryUUID: 3a1bc7f0-60cd-102d-966a-c14e19117a33
creatorsName: cn=manager,cn=internal,dc=advocap,dc=org
createTimestamp: 20081217212718Z
entryCSN: 20081217212718Z#000000#00#000000
modifiersName: cn=manager,cn=internal,dc=advocap,dc=org
modifyTimestamp: 20081217212718Z


One possible problem I see is in the People dn records.
Will kolab work with my People dn entries?

Will I have to add these for each user?
objectClass: kolabInetOrgPerson
kolabHomeServer: mailtest.advocap.org
kolabInvitationPolicy: ACT_MANUAL
I suspect yes.

Anyone have migration scripts?

I  prefer kolab to be a slave but either way that is a small issue.
I see kolab is  using slurp. Can I use sync replication instead?
I'm going to have to do a lot of editing to slapd.conf anyhow.

Looks like ldap account manager has provisions for kolab so I assume that will 
work for user administration. Any recommendation on anything else?

John 


From steuwer at univention.de  Fri Jan 23 08:20:44 2009
From: steuwer at univention.de (Ingo Steuwer)
Date: Fri, 23 Jan 2009 08:20:44 +0100
Subject: Another free/busy odditiy - Kontact vs. DNS?
In-Reply-To: <200901221733.43555.itsef-admin@brightsight.com>
References: <200901221733.43555.itsef-admin@brightsight.com>
Message-ID: <200901230820.46839.steuwer@univention.de>

Hello,

Am Donnerstag, 22. Januar 2009 schrieb ITSEF Admin:
> Hi all,
>
> while I was resolving my own problem with Kontact and free/busy (see list
> archives... it was a problem with a SSL certificate), several other users
> came to me also with free/busy problems. Again, free/busy simply did not
> work - and I was not even able to find any requests from them in the server
> logs. After some experimenting I finally found the solution for this
> problem as well: Contrary to our other users (and myself), the users with
> the problem had their FreeBusyRetrieveUrl set to:
> "https://KOLABSERVER/freebusy/" All other users have
> "https://KOLABSERVER.DOM.AIN/freebusy/". To my great surprise, only the
> second version (with the full domain) works. This is especially puzzling,
> as "host KOLABSERVER" yields the same result as "host KOLABSERVER.DOM.AIN"
> on the command line. Same with Konqueror - it does not matter whether I
> enter the domain or not, Konqueror does display the correct page on our
> Kolab server. Kontact seems to be the only exception.
>
> Does anybody have an idea why this is? Should I file a bugreport?
>
> Regards,
>
> Thomas

this might be connected to your SSL-Issue. SSL-certificates are only valid for 
the FQDN (KOLABSERVER.DOM.AIN) of your server, not for the IP or hostname 
(KOLABSERVER). If you'll open https://KOLABSERVER with your browser you'll 
see a warning also. Maybe it is similar to your latest issue that kontact 
doesn't show such a warning but simply "ignores" the server because of 
the "invalied" SSL certificate.

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 Jan 23 08:37:29 2009
From: steuwer at univention.de (Ingo Steuwer)
Date: Fri, 23 Jan 2009 08:37:29 +0100
Subject: multiple kolab installation question :(
In-Reply-To: <d53357b70901221203q4b3c8ac3le80cf06b3bd7052@mail.gmail.com>
References: <d53357b70901221203q4b3c8ac3le80cf06b3bd7052@mail.gmail.com>
Message-ID: <200901230837.30745.steuwer@univention.de>

Hello,

Am Donnerstag, 22. Januar 2009 schrieb Antonio Straziota:
> hi all,
>
> i've multiple sites interconnected through a VPN and i have an
> internet entry point only in site1
>
> i've multiple kolab installation on site1 site2 site3 site4
>
> on site1 i've Kolab Master, and two kolab slave
>
> i want to one of this slave as webclient only for internet use for ALL
> slave of that master.
>
> For example:
>
> MASTER is KOLAB-MASTER.demo.tst (on site1)
>
> slave for webmail is webmail.demo.tst (on site1)
>
> slave severs are: kolab.site1.demo.tst kolab.site2.demo.tst
> kolab.site3.demo.tst kolab.site4.demo.tst
>
> mail domains are: site1.demo.tst site2.demo.tst site3.demo.tst
> site4.demo.tst
>
> can i access all mailbox for all slave server through webmail server?

Horde should be able to connect to the users kolabHomeServer instead of 
localhost. I'm not sure how Horde is preconfigured in native kolab 
installations, but it is able to do that in general.

One drawback in your constellation are shared folders, which are shared on one 
server only. A user on server A can't share stuff with a user on server B. 
This can be avoided with "cyrus murder", a kind of cluster-enhancement for 
cyrus. It is a bit tricky in setup and certainly will need patches against 
kolabd.

> Then, i need to setting up each slave with samba integration
> (http://wiki.kolab.org/index.php/Kolab_2.2_and_Samba_on_Ubuntu_Hardy)
> so every openLDAP structure must be indipendent from each other . Is
> it possible?

Mhm, what are your goals? Centralized user management (Kolab) or decentralized 
user management (indipendet samba sites)?

Samba in combination with OpenLADP can be configured to use a local LDAP 
replicate for read access (authentication etc.) but a central master instance 
for write access (i.e. password changes). And even in such a scenario each 
site can have it's own samba PDC -- but you need to make sure that clients 
and servers can "see" only one samba PDC in broadcasts or netbios requests.

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 tobias.oed at octant.org  Fri Jan 23 09:16:25 2009
From: tobias.oed at octant.org (Tobias Oed)
Date: Fri, 23 Jan 2009 09:16:25 +0100
Subject: Kolab Mail archiving - software, methods, experiences?
In-Reply-To: <4978634D.7000801@FuH-E.de>
References: <4978634D.7000801@FuH-E.de>
Message-ID: <49797CD9.1070109@octant.org>

Christian R??ler wrote:
> Hallo everyone,
>
> I am in need for mail archiving, that means that every incoming and
> outgoing mail has to be archived somewhere.

Be aware of the privacy rights of your users! Not sure how legislation
goes where you're at but this is something you need to consider.
At a minimum, they must be fully informed.

> Now I am a bit overwhelmed with all the possibilities, and so I want to
> ask the list in which ways this has already been solved, which software
> (if so) is being used, and so on.
>
> Several possibilities spring to my mind:
>
> - postfix (main.cf) always_bcc=archiv at kolab.lokal.tld. Funny, but not
> unexpected (as each mail goes three times through postfix, if I am not
> mistaken) is that each mail goes threefold to the archive / gets
> tripled. Does anyone know an easy way around that?

put the always_bcc in master.cf as an option to the last postfix smtpd
in the chain
   -o always_bcc = archiver...
You're in for a nightmare though - I have a customer who does that and
it's hell.

> - has anyone integrated Octant Opensources OMA Open Mail Archive
> <http://octant.org> into Kolab, and if so, which are the experiences?

It works. The kolab modifications are minimal, even more so since the
archiving is done by a postfix content filter. There is a plugin to
authenticate users against the kolab ldap. If you need help, we (octant)
can help  :)

> - or perhaps Inovox-Mailarchivierungssoftware,
> <http://www.inovox.de/email-archivierung>,
> <http://sourceforge.net/projects/emailarchiving/>? Experiences?

I didn't know about this project, looks interesting especially their
import facilities.

> - Or perhaps another way? Another software, proxy or more simple
> solution? In short, how is this solved elsewhere?

Here it's obviously oma  :)

> Best regards,
> Christian

Regards
Tobias Oed
ps: Apologies for sending this privately yesturday Christian.

-- *Tobias Oed* - Octant Informatique <http://www.octant-fr.com>
tobias.oed at octant.org <mailto:tobias.oed at octant.org> - 04 76 50 82 38
*La R?gion Rh?ne Alpes soutient Octant dans le cadre de son projet
innovant... L'ERP OpenSource.*


From bernhard at intevation.de  Fri Jan 23 10:45:18 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 23 Jan 2009 10:45:18 +0100
Subject: Groups for shared folders
In-Reply-To: <200901220927.49938.bernhard@intevation.de>
References: <mailman.292.1231950808.2113.kolab-users@kolab.org>
	<20090122070840.61866kcfk2qnwdwc@webmail.pardus.de>
	<200901220927.49938.bernhard@intevation.de>
Message-ID: <200901231045.18864.bernhard@intevation.de>

On Donnerstag, 22. Januar 2009, Bernhard Reiter wrote:
> > As we had only the Kolab web client supporting the ?
> > required additional folder attributes we added the calendar management ?
> > view from the client into fbview.
>
> Yes, for pxfb-readable-for only.

Sorry, my bad of not remembering the change.
Gunnar remined me that we actually build in the full handling in fbview. 

-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090123/48a85902/attachment.bin

From bernhard at intevation.de  Fri Jan 23 10:56:24 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 23 Jan 2009 10:56:24 +0100
Subject: kolab ldap migration questions.
In-Reply-To: <200901221615.38062.johnm@advocap.org>
References: <200901221615.38062.johnm@advocap.org>
Message-ID: <200901231056.27402.bernhard@intevation.de>

On Donnerstag, 22. Januar 2009, John McMonagle wrote:
> Here is ?one of our current records:
> dn: uid=bradb,ou=People,dc=advocap,dc=org
> uid: bradb

> From kolab test:
> dn: cn=Brad Bingham,dc=advocap,dc=org

> One possible problem I see is in the People dn records.
> Will kolab work with my People dn entries?

I think it should (would need a through test).

> Will I have to add these for each user?
> objectClass: kolabInetOrgPerson
> kolabHomeServer: mailtest.advocap.org
> kolabInvitationPolicy: ACT_MANUAL
> I suspect yes.

Yes, I think so. As many LDAP searches will only go for kolabInetOrgPerson
it should not be necessary to set kolabInvitationPolicy:, it is a current 
defect in the server 2.2.1beta1.

> Anyone have migration scripts?

We've done a few migration scripts for directory management changes
in the past, so you might find examples, maybe
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/utils/admin/convert-ldif-21.py

> I ?prefer kolab to be a slave but either way that is a small issue.
> I see kolab is ?using slurp. Can I use sync replication instead?
> I'm going to have to do a lot of editing to slapd.conf anyhow.

I believe we have added syncrepl methods, but they are not default
and might miss more testing.

> Looks like ldap account manager has provisions for kolab so I assume that
> will work for user administration. Any recommendation on anything else?

Any directory management client that is able to deal with ldap should 
be usable in principle.

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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090123/bb22b3bc/attachment.bin

From Roessler at FuH-E.de  Fri Jan 23 12:19:26 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Fri, 23 Jan 2009 12:19:26 +0100
Subject: Kolab Mail archiving - software, methods, experiences?
In-Reply-To: <49797CD9.1070109@octant.org>
References: <4978634D.7000801@FuH-E.de> <49797CD9.1070109@octant.org>
Message-ID: <4979A7BE.9020201@FuH-E.de>

Tobias Oed schrieb:

>> I am in need for mail archiving, that means that every incoming and
>> outgoing mail has to be archived somewhere.
> Be aware of the privacy rights of your users! Not sure how legislation
> goes where you're at but this is something you need to consider.At a
 > minimum, they must be fully informed.

Thanks for mentioning, even if these things are already solved. Users 
are fully informed, and there is no private mail. If this was not so, I 
would not do this migration, as legislature here in germany is (as far 
as I know) pretty strict in this regard.

>> - postfix (main.cf) always_bcc=archiv at kolab.lokal.tld. [... ]each mail
 >> goes threefold to the archive / gets tripled. Does anyone know an
 >> easy way around that?
> put the always_bcc in master.cf as an option to the last postfix smtpd
> in the chain -o always_bcc = archiver... You're in for a nightmare though
 > - I have a customer who does that and it's hell.

Yes, I tend to think that too; if I do that I will have to 'sieve' until 
kingdom's coming (if I may say so). But besides that, why would you say 
'nightmare'?

>> - has anyone integrated Octant Opensources OMA Open Mail Archive
>> <http://octant.org> into Kolab, and if so, which are the experiences?
> It works. The kolab modifications are minimal, even more so since the
> archiving is done by a postfix content filter. There is a plugin to
> authenticate users against the kolab ldap. If you need help, we (octant)
> can help  :)

Thank you, and I must say this solution seems tasty to me. I will try it 
right now.

So here are my first questions (if I may): You wrote in 
<http://opensources.octant-fr.com/e107_plugins/forum/forum_viewtopic.php?39.post> 
about kolab integration. Where do I put that code snippet? 
/kolab/local/oma/lib/plugins/auth/ldap/ldap.php, obviously? (By the way, 
first line: "<;?php", shouldn't that be: "<?php"?)

Well, I got two fast questions. First one: I just got a blank screen 
when entering http://kolab.lokal.de/oma/ (kolab.lokal.de just used 
internally, here). But some source html is delivered; please see below 
[1], if that helps. I presume the demon does not start. If I start it 
'by hand' it says:
| kolab:/kolab/local/oma # /kolab/local/oma/bin/omad.php
| PHP Notice:  Use of undefined constant AF_UNIX - assumed 'AF_UNIX' in
| /kolab/local/oma/lib/Socket.class.php on line 51

Any hint, please?

> Here it's obviously oma  :)

Obviously :)

> ps: Apologies for sending this privately yesturday Christian.

No apology needed! To the contrary: I thank for your answer, and your 
help offer.

Best regards,
Christian


[1] Delivered source html:
<html>
<head>
<meta http-equiv='Pragma' content='no-cache'/>
<meta http-equiv='Cache-Control' content='no-cache'/>
<meta http-equiv='Content-Type' content='text/html; charset=utf-8'/>
<title>Open Mail Archiver</title>
<script type='text/javascript' 
src='http://kolab.lokal.de/oma/javascripts/oma.js'></script>
<link rel='StyleSheet' href='http://kolab.lokal.de/oma/style.css' 
media='screen' type='text/css'/>
 >link rel='stylesheet' type='text/css' media='all' 
href='http://kolab.lokal.de/oma/includes/jscalendar-1.0/calendar-blue.css' 
title='win2k-cold-1' />
<script type='text/javascript' 
src='http://kolab.lokal.de/oma/includes/jscalendar-1.0/calendar.js'></script>
<script type='text/javascript' 
src='http://kolab.lokal.de/oma/includes/jscalendar-1.0/lang/calendar-en.js'></script>
<script type='text/javascript' 
src='http://kolab.lokal.de/oma/includes/jscalendar-1.0/calendar-setup.js'></script>
</head>
<body>


From aspineux at gmail.com  Fri Jan 23 12:46:58 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Fri, 23 Jan 2009 12:46:58 +0100
Subject: Kolab Mail archiving - software, methods, experiences?
In-Reply-To: <4978634D.7000801@FuH-E.de>
References: <4978634D.7000801@FuH-E.de>
Message-ID: <71fe4e760901230346k149b0dd9j2593dae70a3c042c@mail.gmail.com>

On Thu, Jan 22, 2009 at 1:15 PM, Christian R??ler <Roessler at fuh-e.de> wrote:
> Hallo everyone,
>
> I am in need for mail archiving, that means that every incoming and
> outgoing mail has to be archived somewhere.
>
> Now I am a bit overwhelmed with all the possibilities, and so I want to
> ask the list in which ways this has already been solved, which software
> (if so) is being used, and so on.
>
> Several possibilities spring to my mind:
>
> - postfix (main.cf) always_bcc=archiv at kolab.lokal.tld. Funny, but not
> unexpected (as each mail goes three times through postfix, if I am not
> mistaken) is that each mail goes threefold to the archive / gets
> tripled. Does anyone know an easy way around that?

Instead of adding alway_bcc option in your main.cf, add it to your
master.cf  using a "-o always_bcc=archiv at kolab.lokal.tld" syntax.
Your 2 entry points should be :

@@@bind_addr@@@:smtp      inet  n       -       n       -       -       smtpd

and

@@@bind_addr@@@:465       inet  n       -       n       -       -
 smtpd -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes

Just update these 2 lines


I dont know about other archiving method.

Regards.

>
> - has anyone integrated Octant Opensources OMA Open Mail Archive
> <http://octant.org> into Kolab, and if so, which are the experiences?
>
> - or perhaps Inovox-Mailarchivierungssoftware,
> <http://www.inovox.de/email-archivierung>,
> <http://sourceforge.net/projects/emailarchiving/>? Experiences?
>
> - Or perhaps another way? Another software, proxy or more simple
> solution? In short, how is this solved elsewhere?
>
> 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  Fri Jan 23 13:00:06 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Fri, 23 Jan 2009 13:00:06 +0100
Subject: Kolab Mail archiving - software, methods, experiences?
In-Reply-To: <71fe4e760901230346k149b0dd9j2593dae70a3c042c@mail.gmail.com>
References: <4978634D.7000801@FuH-E.de>
	<71fe4e760901230346k149b0dd9j2593dae70a3c042c@mail.gmail.com>
Message-ID: <4979B146.2030008@FuH-E.de>

Alain Spineux schrieb:

>> - postfix (main.cf) always_bcc=archiv at kolab.lokal.tld.[...] each
 >> mail goes threefold to the archive / gets tripled. Does anyone
 >> know an easy way around that?
> Instead of adding alway_bcc option in your main.cf, add it to your
> master.cf  using a "-o always_bcc=archiv at kolab.lokal.tld" syntax.
> Your 2 entry points should be :
> @@@bind_addr@@@:smtp      inet  n       -       n       -       -       smtpd
> and
> @@@bind_addr@@@:465       inet  n       -       n       -       -
>  smtpd -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes

Thanks, Alain; I will do that at once as a fallback (if open mail 
archive will not work) with sieve-ing afterwards.


Best regards,
Christian


From devgioiatech at gmail.com  Fri Jan 23 13:15:22 2009
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Fri, 23 Jan 2009 13:15:22 +0100
Subject: multiple kolab installation question :(
In-Reply-To: <200901230837.30745.steuwer@univention.de>
References: <d53357b70901221203q4b3c8ac3le80cf06b3bd7052@mail.gmail.com>
	<200901230837.30745.steuwer@univention.de>
Message-ID: <d53357b70901230415t2780724dncd50d77040cf6d46@mail.gmail.com>

Thanks for reply...

> Horde should be able to connect to the users kolabHomeServer instead of
> localhost. I'm not sure how Horde is preconfigured in native kolab
> installations, but it is able to do that in general.

Ok ,so, from my "salve webmail" of the master i can access to mail box
on each other slave?
I'll try it :-)

> One drawback in your constellation are shared folders, which are shared on one
> server only. A user on server A can't share stuff with a user on server B.
> This can be avoided with "cyrus murder", a kind of cluster-enhancement for
> cyrus. It is a bit tricky in setup and certainly will need patches against
> kolabd.

At this time I don't need this... but i'll study it for future ;-)

> Mhm, what are your goals? Centralized user management (Kolab) or decentralized
> user management (indipendet samba sites)?

I need decentralized one: every site has kolab server and a file
server accessible from user of THAT site.

Really, my problem is that i've only one entry/exit point from/to internet.
I have to make all kolab accessible from internet from that point, but
all kolab server must be indipendent from the other.

Thanks again.
I'll try this architecture.


From s.kim at hia.rwth-aachen.de  Fri Jan 23 13:26:20 2009
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Fri, 23 Jan 2009 13:26:20 +0100
Subject: Groups for shared folders
In-Reply-To: <200901220927.49938.bernhard@intevation.de>
References: <mailman.292.1231950808.2113.kolab-users@kolab.org>
	<200901210946.16997.bernhard@intevation.de>
	<20090122070840.61866kcfk2qnwdwc@webmail.pardus.de>
	<200901220927.49938.bernhard@intevation.de>
Message-ID: <4979B76C.2090208@hia.rwth-aachen.de>

Hello,

Bernhard Reiter schrieb:
> On Donnerstag, 22. Januar 2009, Gunnar Wrobel wrote:
>   
>> Quoting Bernhard Reiter <bernhard at intevation.de>:
>>     
>>> On Dienstag, 20. Januar 2009, Saim Kim wrote:
>>>       
>>>> I was also looking for a solution for group access -but not to shared
>>>> folders. Instead I would like to grant access to the calendar of
>>>> ressource accounts. I'm still working on a Kolab 2.2.0 system (Debian
>>>> Etch). When I try to enter the group or actually the distribution list
>>>> on the fbview interface it is not added but it shows up in the cyradm
>>>> interface with the "group:" prefix and seems to work right.
>>>>         
>>> Huh, die fbview interface should not change the directory contents,
>>> nor anything else on the server. It should be "view only".
>>>       
>> This change has been requested with the implementation of the extended  
>> free/busy  concept. 
>>     
>
> True, the pxfb-readable-for annotation should be writeable from fbview,
> thanks for pointing this out.
>
> But I think this issue is about setting the ACLs from fbview
> which is not necessary and should be done from the client.
>   
That was the function I was looking for since we don't have an 
responsible person for each ressource. So a central interface to change 
the ACL's would be nice. I didn't even know it changes come annotations 
of a folder.

Best regards
Saim

-- 
--------------------------------------------------------------------------
Dipl.-Ing. Saim Kim
Lehrstuhl fuer Medizinische Informationstechnik
Helmholtz-Institut fuer Biomedizinische Technik
RWTH Aachen
Pauwelsstr. 20, D-52074 Aachen
---
Web:   http://www.medit.hia.rwth-aachen.de/
Tel:   +49-(0)241-80 23218
Fax:   +49-(0)241-80 82442
email: s.kim at hia.rwth-aachen.de
-------------------------------------------------------------------------- 


From Roessler at FuH-E.de  Fri Jan 23 15:33:02 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Fri, 23 Jan 2009 15:33:02 +0100
Subject: Kolab Mail archiving - software, methods, experiences?
In-Reply-To: <71fe4e760901230346k149b0dd9j2593dae70a3c042c@mail.gmail.com>
References: <4978634D.7000801@FuH-E.de>
	<71fe4e760901230346k149b0dd9j2593dae70a3c042c@mail.gmail.com>
Message-ID: <4979D51E.60500@FuH-E.de>

Alain Spineux schrieb:

> Instead of adding alway_bcc option in your main.cf, add it to your
> master.cf  using a "-o always_bcc=archiv at kolab.lokal.tld" syntax.
> Your 2 entry points should be :
> @@@bind_addr@@@:smtp      inet  n       -       n       -       -       smtpd
> @@@bind_addr@@@:465       inet  n       -       n       -       -
>  smtpd -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes

Just to verify: the two entries would be (without linefeeds, and of
course a kolabconf and postfix-reload after):

| @@@bind_addr@@@:smtp      inet  n       -       n       -       -
| smtpd -o always_bcc=archiv at kolab.lokal.de

| @@@bind_addr@@@:465       inet  n       -       n       -       -
| smtpd smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes
| -o always_bcc=archiv at kolab.lokal.de

... as i have difficulties to get it to work, and am wondering...

best regards,
Christian


From Roessler at FuH-E.de  Fri Jan 23 15:47:40 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Fri, 23 Jan 2009 15:47:40 +0100
Subject: Kolab Mail archiving - software, methods, experiences?
In-Reply-To: <71fe4e760901230346k149b0dd9j2593dae70a3c042c@mail.gmail.com>
References: <4978634D.7000801@FuH-E.de>
	<71fe4e760901230346k149b0dd9j2593dae70a3c042c@mail.gmail.com>
Message-ID: <4979D88C.8030407@FuH-E.de>

Alain Spineux schrieb:
> @@@bind_addr@@@:smtp      inet  n       -       n       -       -       smtpd
> @@@bind_addr@@@:465       inet  n       -       n       -       -
>  smtpd -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes

Well, it works if I put it in (one line)
| cleanup   unix  n       -       n       -       0       cleanup
| -o always_bcc=archiv at kolab.lokal.de

...but that's possible not a good place, is it not?

Best regrads,
Christian


From carsten at cburghardt.com  Fri Jan 23 16:15:35 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Fri, 23 Jan 2009 16:15:35 +0100
Subject: Kolab Mail archiving - software, methods, experiences?
In-Reply-To: <4978634D.7000801@FuH-E.de>
References: <4978634D.7000801@FuH-E.de>
Message-ID: <20090123161535.26992vty6pdl2o00@www.inovox.de>

Quoting "Christian R??ler" <Roessler at FuH-E.de>:

> Hallo everyone,
>
> I am in need for mail archiving, that means that every incoming and
> outgoing mail has to be archived somewhere.
>
> Now I am a bit overwhelmed with all the possibilities, and so I want to
> ask the list in which ways this has already been solved, which software
> (if so) is being used, and so on.
>
> Several possibilities spring to my mind:
>
> - postfix (main.cf) always_bcc=archiv at kolab.lokal.tld. Funny, but not
> unexpected (as each mail goes three times through postfix, if I am not
> mistaken) is that each mail goes threefold to the archive / gets
> tripled. Does anyone know an easy way around that?
>
> - has anyone integrated Octant Opensources OMA Open Mail Archive
> <http://octant.org> into Kolab, and if so, which are the experiences?
>
> - or perhaps Inovox-Mailarchivierungssoftware,
> <http://www.inovox.de/email-archivierung>,
> <http://sourceforge.net/projects/emailarchiving/>? Experiences?

As that is basically my baby it definitely works with Kolab ;-)
You register the proxy in your postfix and use e.g. Alfresco as  
archive. Of course it all depends on what you want to do with your  
archive (only accessible for admins vs. users, legal or research  
issues, ...).

> - Or perhaps another way? Another software, proxy or more simple
> solution? In short, how is this solved elsewhere?
>


Carsten


From aspineux at gmail.com  Fri Jan 23 17:14:35 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Fri, 23 Jan 2009 17:14:35 +0100
Subject: Kolab Mail archiving - software, methods, experiences?
In-Reply-To: <4979D88C.8030407@FuH-E.de>
References: <4978634D.7000801@FuH-E.de>
	<71fe4e760901230346k149b0dd9j2593dae70a3c042c@mail.gmail.com>
	<4979D88C.8030407@FuH-E.de>
Message-ID: <71fe4e760901230814we6e5914u73f565c471d78237@mail.gmail.com>

On Fri, Jan 23, 2009 at 3:47 PM, Christian R??ler <Roessler at fuh-e.de> wrote:
> Alain Spineux schrieb:
>> @@@bind_addr@@@:smtp      inet  n       -       n       -       -       smtpd
>> @@@bind_addr@@@:465       inet  n       -       n       -       -
>>  smtpd -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes
>
> Well, it works if I put it in (one line)
> | cleanup   unix  n       -       n       -       0       cleanup
> | -o always_bcc=archiv at kolab.lokal.de
>
> ...but that's possible not a good place, is it not?

Yes it-is, you are right, always_bcc is an option used by cleanup, not by smtpd.
You find the good place yourself.

And it works fine because, other smtpd instances use another cleanup
instcane, aka "-o cleanup_service_name=post-cleanup"

Another way was to setup always_bcc in main.cf and add "-o
always_bcc=" in the post-cleanup.

Regards.



>
> Best regrads,
> 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 alex at swiftnetcomputers.biz  Fri Jan 23 23:08:48 2009
From: alex at swiftnetcomputers.biz (Alex Chejlyk)
Date: Fri, 23 Jan 2009 17:08:48 -0500
Subject: Kolab Mail archiving - software, methods, experiences?
In-Reply-To: <4978634D.7000801@FuH-E.de>
References: <4978634D.7000801@FuH-E.de>
Message-ID: <497A3FF0.20401@swiftnetcomputers.biz>

Here is what I've done.

I use rsync to copy the whole /kolab folder to a backup server. I do 
this at 2:00am. I do take the server offline from 2:00am to 2:30am.

You can leave kolab up and still use rsync, but you must export the 
mailbox db. I think the info is on the wiki.

I also have scripts that run from each users workstation to archive 
Thunderbird's mail. This is a redundant solution, but I find two backups 
are always better than one.


I'm sure there are many much more elegant solutions, but this works for me.

Cheers,

Alex C.





Christian R??ler wrote:
> Hallo everyone,
> 
> I am in need for mail archiving, that means that every incoming and 
> outgoing mail has to be archived somewhere.
> 
> Now I am a bit overwhelmed with all the possibilities, and so I want to 
> ask the list in which ways this has already been solved, which software 
> (if so) is being used, and so on.
> 
> Several possibilities spring to my mind:
> 
> - postfix (main.cf) always_bcc=archiv at kolab.lokal.tld. Funny, but not 
> unexpected (as each mail goes three times through postfix, if I am not 
> mistaken) is that each mail goes threefold to the archive / gets 
> tripled. Does anyone know an easy way around that?
> 
> - has anyone integrated Octant Opensources OMA Open Mail Archive 
> <http://octant.org> into Kolab, and if so, which are the experiences?
> 
> - or perhaps Inovox-Mailarchivierungssoftware, 
> <http://www.inovox.de/email-archivierung>, 
> <http://sourceforge.net/projects/emailarchiving/>? Experiences?
> 
> - Or perhaps another way? Another software, proxy or more simple 
> solution? In short, how is this solved elsewhere?
> 
> Best regards,
> Christian
> 
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
> 


From wrobel at pardus.de  Sun Jan 25 08:47:14 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sun, 25 Jan 2009 08:47:14 +0100
Subject: SOLVED? Re: Cannot get freebusy to work in Kontact
In-Reply-To: <200901221646.08095.itsef-admin@brightsight.com>
References: <200810081024.43359.itsef-admin@brightsight.com>
	<200812101746.10487.itsef-admin@brightsight.com>
	<200901221630.28459.itsef-admin@brightsight.com>
	<200901221646.08095.itsef-admin@brightsight.com>
Message-ID: <20090125084714.384426g4hurkplhc@webmail.pardus.de>

Quoting ITSEF Admin <itsef-admin at brightsight.com>:

> On Thursday 22 January 2009 16:30:28 ITSEF Admin wrote:
> [...]
>> When *I* try it with my client/account, the exchange looks like this:
>>
>> [...]
>> HOST2.DOM.AIN - - [22/Jan/2009:12:26:28 +0100] "GET /freebusy/NAME2.ifb
>> HTTP/1.1" 403 770
>> [...]
>>
>> i.e. the server sends a "403" ("Forbidden") right away - my client doesn't
>> even get the "401" (which, in turn, I expect to be the reason why the user
>> name is never sent). Does that maybe ring a bell with someone?
> [...]
>
> This finally ignited some dim bulb somewhere in my mind - I had been  
> wondering
> about some password dialogues coming up asking for a password for some SSL
> certificate. Hence, I had a look at the "kssl*" files in
> ~/.kde/share/config - and moved them out of the way, then restarted kontact.
> Now freebusy works again... Apparently, some old cert had sneaked in there
> (we've been busy with SSL on our Kolab server some months back), causing the
> SSL connection to fail - resulting in the "403". Now, after I removed that
> stuff, my client gets a "401" initially, like all others.
>
> I hope this is of help to anybody...
>
> @Bernhard: Is it worthwhile to file a "wish" ticket with the request for
> better error reporting in cases like this? If kontact had reported something
> back about the error codes from the server, the bell might have started
> ringing earlier... :-}

You should definitely submit a ticket especially since you already  
have very precise information where the problem might have been located.

Cheers,

Gunnar

>
> Cheerio,
>
> Thomas
>
> _______________________________________________
> 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/20090125/b77befa9/attachment.bin

From wrobel at pardus.de  Sun Jan 25 09:27:17 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sun, 25 Jan 2009 09:27:17 +0100
Subject: multiple kolab installation question :(
In-Reply-To: <d53357b70901230415t2780724dncd50d77040cf6d46@mail.gmail.com>
References: <d53357b70901221203q4b3c8ac3le80cf06b3bd7052@mail.gmail.com>
	<200901230837.30745.steuwer@univention.de>
	<d53357b70901230415t2780724dncd50d77040cf6d46@mail.gmail.com>
Message-ID: <20090125092717.16422syrc3uaqs2s@webmail.pardus.de>

Quoting Antonio Straziota <devgioiatech at gmail.com>:

> Thanks for reply...
>
>> Horde should be able to connect to the users kolabHomeServer instead of
>> localhost. I'm not sure how Horde is preconfigured in native kolab
>> installations, but it is able to do that in general.
>
> Ok ,so, from my "salve webmail" of the master i can access to mail box
> on each other slave?

Yes, this should work. If you have problems with this, please report  
back and we'll make it work ;)

Cheers,

Gunnar

> I'll try it :-)
>
>> One drawback in your constellation are shared folders, which are  
>> shared on one
>> server only. A user on server A can't share stuff with a user on server B.
>> This can be avoided with "cyrus murder", a kind of cluster-enhancement for
>> cyrus. It is a bit tricky in setup and certainly will need patches against
>> kolabd.
>
> At this time I don't need this... but i'll study it for future ;-)
>
>> Mhm, what are your goals? Centralized user management (Kolab) or  
>> decentralized
>> user management (indipendet samba sites)?
>
> I need decentralized one: every site has kolab server and a file
> server accessible from user of THAT site.
>
> Really, my problem is that i've only one entry/exit point from/to internet.
> I have to make all kolab accessible from internet from that point, but
> all kolab server must be indipendent from the other.
>
> Thanks again.
> I'll try this architecture.
>
> _______________________________________________
> 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/20090125/53b38d8e/attachment.bin

From carsten at cburghardt.com  Sun Jan 25 12:38:02 2009
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Sun, 25 Jan 2009 12:38:02 +0100
Subject: Kolab Mail archiving - software, methods, experiences?
In-Reply-To: <497A3FF0.20401@swiftnetcomputers.biz>
References: <4978634D.7000801@FuH-E.de> <497A3FF0.20401@swiftnetcomputers.biz>
Message-ID: <497C4F1A.6000904@cburghardt.com>

Alex Chejlyk schrieb:
> Here is what I've done.
>
> I use rsync to copy the whole /kolab folder to a backup server. I do 
> this at 2:00am. I do take the server offline from 2:00am to 2:30am.
>
> You can leave kolab up and still use rsync, but you must export the 
> mailbox db. I think the info is on the wiki.
>
> I also have scripts that run from each users workstation to archive 
> Thunderbird's mail. This is a redundant solution, but I find two backups 
> are always better than one.
>
>
> I'm sure there are many much more elegant solutions, but this works for me.
>   
But this is not an archiving solution as you are talking about a backup. 
If the user deletes the mail from the mailbox it will also be gone from 
your backup. You can keep old versions of course but then you have to 
restore the old state and can not simply search through your archive. 
Normally backup and archiving have to be setup in parallel.


Carsten


From daniel.vergien at rrz.uni-hamburg.de  Sun Jan 25 13:26:21 2009
From: daniel.vergien at rrz.uni-hamburg.de (Daniel Vergien)
Date: Sun, 25 Jan 2009 13:26:21 +0100
Subject: kolab client on solaris
Message-ID: <497C5A6D.7060800@rrz.uni-hamburg.de>

Hi list,

is someone having the kolab client working on x86 solaris 10? I've 
tried some variants which all fail some place:
- the kde from openscw or blastwave is not showing any fonts
- the one from netbsds pkgsrc is having no ssl support
- all the other buildsystems (konstruct oder kde-svn) are failing at 
some point

What way have you used? I'm serious thinking about trying the 
windows-client in wine ;-)

Daniel


From kloecker at kde.org  Sun Jan 25 15:27:40 2009
From: kloecker at kde.org (Ingo =?iso-8859-1?q?Kl=F6cker?=)
Date: Sun, 25 Jan 2009 15:27:40 +0100
Subject: kolab client on solaris
In-Reply-To: <497C5A6D.7060800@rrz.uni-hamburg.de>
References: <497C5A6D.7060800@rrz.uni-hamburg.de>
Message-ID: <200901251527.44802@thufir.ingo-kloecker.de>

On Sunday 25 January 2009, Daniel Vergien wrote:
> Hi list,
>
> is someone having the kolab client working on x86 solaris 10? I've
> tried some variants which all fail some place:
> - the kde from openscw or blastwave is not showing any fonts
> - the one from netbsds pkgsrc is having no ssl support
> - all the other buildsystems (konstruct oder kde-svn) are failing at
> some point

I suppose you know http://solaris.kde.org/ ?


> What way have you used? I'm serious thinking about trying the
> windows-client in wine ;-)

Wouldn't it be easier to install Linux in a virtual machine?


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/20090125/ad1de5dd/attachment.bin

From admin at jmay.org  Sun Jan 25 16:44:06 2009
From: admin at jmay.org (Jochen May)
Date: Sun, 25 Jan 2009 16:44:06 +0100
Subject: Crash of Kontact on Windows
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAJ7BXRqPWfdNkLKYTJ3u6xjCgAAAEAAAAMKKMhvCcFtGrCcXwS/WJNMBAAAAAA==@jmay.org>

Hi,

i forgot something :-)

The crash is each time, when kontact try to check the folder shared.spam at around 25%

Greetings
Jochen


From daniel.vergien at rrz.uni-hamburg.de  Sun Jan 25 16:54:19 2009
From: daniel.vergien at rrz.uni-hamburg.de (Daniel Vergien)
Date: Sun, 25 Jan 2009 16:54:19 +0100
Subject: kolab client on solaris
In-Reply-To: <200901251527.44802@thufir.ingo-kloecker.de>
References: <497C5A6D.7060800@rrz.uni-hamburg.de>
	<200901251527.44802@thufir.ingo-kloecker.de>
Message-ID: <497C8B2B.70205@rrz.uni-hamburg.de>

Hi,

> I suppose you know http://solaris.kde.org/ ?
> 

yes, but compiling fails if I follow 
http://techbase.kde.org/Projects/KDE_on_Solaris If I use the binaries 
from the end of the page, I can use kde, but some parts are renderd 
like I only have 16 colours, sound is not working and its crashing 
from time to time.
So its not a real option.
> 
>> What way have you used? I'm serious thinking about trying the
>> windows-client in wine ;-)
> 
> Wouldn't it be easier to install Linux in a virtual machine?
> 
yes, but copy and paste is not working with the middle mouse button.

regards

daniel


From daniel.vergien at rrz.uni-hamburg.de  Sun Jan 25 16:54:24 2009
From: daniel.vergien at rrz.uni-hamburg.de (Daniel Vergien)
Date: Sun, 25 Jan 2009 16:54:24 +0100
Subject: kolab client on solaris
In-Reply-To: <200901251527.44802@thufir.ingo-kloecker.de>
References: <497C5A6D.7060800@rrz.uni-hamburg.de>
	<200901251527.44802@thufir.ingo-kloecker.de>
Message-ID: <497C8B30.3070208@rrz.uni-hamburg.de>

Hi,

> I suppose you know http://solaris.kde.org/ ?
> 

yes, but compiling fails if I follow 
http://techbase.kde.org/Projects/KDE_on_Solaris If I use the binaries 
from the end of the page, I can use kde, but some parts are renderd 
like I only have 16 colours, sound is not working and its crashing 
from time to time.
So its not a real option.
> 
>> What way have you used? I'm serious thinking about trying the
>> windows-client in wine ;-)
> 
> Wouldn't it be easier to install Linux in a virtual machine?
> 
yes, but copy and paste is not working with the middle mouse button.

regards

daniel


From kloecker at kde.org  Sun Jan 25 20:46:13 2009
From: kloecker at kde.org (Ingo =?iso-8859-1?q?Kl=F6cker?=)
Date: Sun, 25 Jan 2009 20:46:13 +0100
Subject: kolab client on solaris
In-Reply-To: <497C8B2B.70205@rrz.uni-hamburg.de>
References: <497C5A6D.7060800@rrz.uni-hamburg.de>
	<200901251527.44802@thufir.ingo-kloecker.de>
	<497C8B2B.70205@rrz.uni-hamburg.de>
Message-ID: <200901252046.19606@thufir.ingo-kloecker.de>

I'm subscribed to kolab-users, so a simple reply-to-list suits me 
fine. ;-)

On Sunday 25 January 2009, Daniel Vergien wrote:
> Hi,
>
> > I suppose you know http://solaris.kde.org/ ?
>
> yes, but compiling fails if I follow
> http://techbase.kde.org/Projects/KDE_on_Solaris If I use the binaries
> from the end of the page, I can use kde, but some parts are renderd
> like I only have 16 colours, sound is not working and its crashing
> from time to time.

AFAIK, KDE on Solaris is still alpha quality. It does seem to compile 
(mostly), but obviously this does not mean that everything works as 
good as on Linux.


> So its not a real option.

Quite frankly, apart from using the Linux or Windows versions on 
Solaris, I see no reasonable alternative. Unless you want to fix all 
the build problems, Adriaan and the others have already fixed, again on 
your own, using KDE on Solaris (self-compiled or pre-built) is your 
best option. The tiny KDE on Solaris team would surely appreciate your 
input. https://mail.kde.org/mailman/listinfo/kde-solaris


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/20090125/5b2a3f65/attachment.bin

From admin at jmay.org  Sun Jan 25 18:42:23 2009
From: admin at jmay.org (Jochen May)
Date: Sun, 25 Jan 2009 18:42:23 +0100
Subject: Crash of Kontact on Windows
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAJ7BXRqPWfdNkLKYTJ3u6xjCgAAAEAAAAHe1EkC9QaRKj93Jt7cLkcsBAAAAAA==@jmay.org>

Hi!

original, this should be the first mail and not the second.... ;-)

i try kontact on a windows xp system. For a couple of days, 
it run without any problems. Now i get the problem, each time 
when i check my folders for new mail, i get a error 
"assertion failed". a screenshot is attached.
i try to make a backtrace, but get only the message, that 
there are "no stack". i miss something?

is it normal, that on kalender, kontakt, journal, aufgaben 
are the folder structure like on screenshot kontact2.jpg? 
and when i check my mails, i get first this message like on 
screenshot kontact3.jpg. 
also, i have a couple of subfolders. but i only see the first 
sub-level of the folders. everything what is deeper than one 
level, i don?t see. any idees?

And finally guys, it?s a hell of job what you have done!!! 
Thanks a lot!

greetings 
jochen

-------------- n?chster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : kontact.jpg
Dateityp    : image/jpeg
Dateigr??e  : 23529 bytes
Beschreibung: nicht verf?gbar
URL         : http://kolab.org/pipermail/kolab-users/attachments/20090125/27510c76/kontact-0001.jpg
-------------- n?chster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : kontact3.jpg
Dateityp    : image/jpeg
Dateigr??e  : 66213 bytes
Beschreibung: nicht verf?gbar
URL         : http://kolab.org/pipermail/kolab-users/attachments/20090125/27510c76/kontact3-0001.jpg
-------------- n?chster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : kontact2.jpg
Dateityp    : image/jpeg
Dateigr??e  : 24055 bytes
Beschreibung: nicht verf?gbar
URL         : http://kolab.org/pipermail/kolab-users/attachments/20090125/27510c76/kontact2-0001.jpg

From bernhard at intevation.de  Mon Jan 26 10:29:18 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 26 Jan 2009 10:29:18 +0100
Subject: Groups for shared folders
In-Reply-To: <4979B76C.2090208@hia.rwth-aachen.de>
References: <mailman.292.1231950808.2113.kolab-users@kolab.org>
	<200901220927.49938.bernhard@intevation.de>
	<4979B76C.2090208@hia.rwth-aachen.de>
Message-ID: <200901261029.19080.bernhard@intevation.de>

On Freitag, 23. Januar 2009, Saim Kim wrote:
> > But I think this issue is about setting the ACLs from fbview
> > which is not necessary and should be done from the client.
> > ?
>
> That was the function I was looking for since we don't have an
> responsible person for each ressource. 

This does not change the situation that you should have a responsible person.
Someone needs to log in. The machine administrators can use cyradm.

> So a central interface to change the ACL's would be nice.

That is something else again.

> I didn't even know it changes come annotations of a folder.

For each folder you can set to whom it is freebusy relevant. 
So you can use it on event folders to switch generation of the freebusy lists
from that folder off. Or only the admins of the folder. The third setting is 
for all readers.

The pxfb-readable-for annotation is there to allow other people to see the 
extendend Freebusylist information from this folder.

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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090126/abe9823a/attachment.bin

From bernhard at intevation.de  Mon Jan 26 10:33:07 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 26 Jan 2009 10:33:07 +0100
Subject: Kolab Mail archiving - software, methods, experiences?
In-Reply-To: <4978634D.7000801@FuH-E.de>
References: <4978634D.7000801@FuH-E.de>
Message-ID: <200901261033.07942.bernhard@intevation.de>

On Donnerstag, 22. Januar 2009, Christian R??ler wrote:
> I am in need for mail archiving, that means that every incoming and
> outgoing mail has to be archived somewhere.
>
> Now I am a bit overwhelmed with all the possibilities, and so I want to
> ask the list in which ways this has already been solved, which software
> (if so) is being used, and so on.

Any archiver that can plug into SMTP will be able to work.
We did it a few times for small installs
that we saved emails in maildir format, split by months or weeks or whatever.

If admins can deal with unix tools (e.g. grepmail or mutt) they have very fast 
access to the emails.



-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090126/7b3853b2/attachment.bin

From bernhard at intevation.de  Mon Jan 26 10:55:00 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 26 Jan 2009 10:55:00 +0100
Subject: kolab client on solaris
In-Reply-To: <200901252046.19606@thufir.ingo-kloecker.de>
References: <497C5A6D.7060800@rrz.uni-hamburg.de>
	<497C8B2B.70205@rrz.uni-hamburg.de>
	<200901252046.19606@thufir.ingo-kloecker.de>
Message-ID: <200901261055.05967.bernhard@intevation.de>

On Sonntag, 25. Januar 2009, Ingo Kl?cker wrote:
> The tiny KDE on Solaris team would surely appreciate your
> input. https://mail.kde.org/mailman/listinfo/kde-solaris

If we can secure funding, KK would be happy to bring up to par
the KDE Kolab enterprise35 or enterprise4 clients (based on KDE 3.5 and KDE 4 
respectively.) 

-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090126/e545d1b7/attachment.bin

From bernhard at intevation.de  Mon Jan 26 11:05:39 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Mon, 26 Jan 2009 11:05:39 +0100
Subject: Crash of Kontact on Windows
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAAJ7BXRqPWfdNkLKYTJ3u6xjCgAAAEAAAAHe1EkC9QaRKj93Jt7cLkcsBAAAAAA==@jmay.org>
References: <!&!AAAAAAAAAAAYAAAAAAAAAJ7BXRqPWfdNkLKYTJ3u6xjCgAAAEAAAAHe1EkC9QaRKj93Jt7cLkcsBAAAAAA==@jmay.org>
Message-ID: <200901261105.46249.bernhard@intevation.de>

Hi Jochen,

On Sonntag, 25. Januar 2009, Jochen May wrote:
> i try kontact on a windows xp system. For a couple of days,
> it run without any problems. Now i get the problem, each time
> when i check my folders for new mail, i get a error
> "assertion failed". a screenshot is attached.

try to rebuild the index of all folders.

> i try to make a backtrace, but get only the message, that
> there are "no stack". i miss something?

Did you manage to get gdb stop there?
Maybe the info message of the KDE subsystem will help us,
see DebugView (also added to the new section
https://wiki.kolab.org/index.php/Kontact_for_Windows_(beta-huge-debug)#Diagnostics )

> is it normal, that on kalender, kontakt, journal, aufgaben
> are the folder structure like on screenshot kontact2.jpg?

No, not at all.

> and when i check my mails, i get first this message like on
> screenshot kontact3.jpg.
> also, i have a couple of subfolders. but i only see the first
> sub-level of the folders. everything what is deeper than one
> level, i don?t see. any idees?

Well your index seems to be corrupt for sure. So unless you clean up,
stuff may stay strange.
We need to reproduce how you've got there, to be able to fix the underlying 
defect.

> And finally guys, it?s a hell of job what you have done!!!

Thanks for helping with testing!

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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090126/2d5d12a6/attachment.bin

From Roessler at FuH-E.de  Mon Jan 26 14:51:57 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Mon, 26 Jan 2009 14:51:57 +0100
Subject: Openpkg packages for extending Kolab, eg Mysql
Message-ID: <497DBFFD.2070700@FuH-E.de>

Hallo,

for archive software evaluation I would need to recompile eg. kolab's 
php, which is unfortunately compiled without mysql.

But every package I search on openpkg has dead download links, mysql, 
ncurses and you-name-what.

So, has anyone the openpkg packages mysql and ncurses, and would send 
them to me, or (better), does anyone know an openpkg package mirror server?

And do others also have problems with openpkg package download?

Best regards,
Christian


From daniel.vergien at rrz.uni-hamburg.de  Mon Jan 26 15:12:12 2009
From: daniel.vergien at rrz.uni-hamburg.de (Daniel Vergien)
Date: Mon, 26 Jan 2009 15:12:12 +0100
Subject: Openpkg packages for extending Kolab, eg Mysql
In-Reply-To: <497DBFFD.2070700@FuH-E.de>
References: <497DBFFD.2070700@FuH-E.de>
Message-ID: <497DC4BC.30401@rrz.uni-hamburg.de>

Hi,

you need to be register an register your installation to be able to 
download things at openpkg.

regards


Daniel

On 01/26/09 02:51 PM, Christian R??ler wrote:
> Hallo,
> 
> for archive software evaluation I would need to recompile eg. kolab's 
> php, which is unfortunately compiled without mysql.
> 
> But every package I search on openpkg has dead download links, mysql, 
> ncurses and you-name-what.
> 
> So, has anyone the openpkg packages mysql and ncurses, and would send 
> them to me, or (better), does anyone know an openpkg package mirror server?
> 
> And do others also have problems with openpkg package download?
> 
> Best regards,
> Christian
> 
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users


-------------- n?chster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : smime.p7s
Dateityp    : application/x-pkcs7-signature
Dateigr??e  : 6495 bytes
Beschreibung: S/MIME Cryptographic Signature
URL         : http://kolab.org/pipermail/kolab-users/attachments/20090126/1d9711f6/smime.bin

From harkin.as at gmail.com  Fri Jan 23 15:40:15 2009
From: harkin.as at gmail.com (Harkin Banks)
Date: Fri, 23 Jan 2009 09:40:15 -0500
Subject: LDAP shutting down on CentOS
Message-ID: <95279D3971EB4F09A4E2437137ABF505@mdmbxp>


From Roessler at FuH-E.de  Mon Jan 26 15:32:22 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Mon, 26 Jan 2009 15:32:22 +0100
Subject: Openpkg packages for extending Kolab, eg Mysql
In-Reply-To: <497DC4BC.30401@rrz.uni-hamburg.de>
References: <497DBFFD.2070700@FuH-E.de> <497DC4BC.30401@rrz.uni-hamburg.de>
Message-ID: <497DC976.3020401@FuH-E.de>

Daniel Vergien schrieb:

 >> But every package I search on openpkg has dead download links, mysql,
 >> ncurses and you-name-what.
> you need to be register an register your installation to be able to 
> download things at openpkg.

Well, I _have_ registered... but strange, now, 2 1/2 hours after 
registration (and validating the registration) I can log onto the ftp 
server. perhaps asking the list has some speeding qualities;).

Ah well,
Christian


From aspineux at gmail.com  Mon Jan 26 19:03:35 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 26 Jan 2009 19:03:35 +0100
Subject: LDAP shutting down on CentOS
In-Reply-To: <95279D3971EB4F09A4E2437137ABF505@mdmbxp>
References: <95279D3971EB4F09A4E2437137ABF505@mdmbxp>
Message-ID: <71fe4e760901261003s7909f486g503c0b1a521ab8b9@mail.gmail.com>

On Fri, Jan 23, 2009 at 3:40 PM, Harkin Banks <harkin.as at gmail.com> wrote:
> From time-to-time, slapd is terminating.  I can't think of any reason for
> this and certainly no one is shutting it down on purpose.  I'm running
> CentOS 5.2.e15.  Below is a tail of openldap.log.  Any thoughts?  Thank you.

Once a day openpkg check for the size of the log of all services.
If required, it stop the service, roll the log and restart the service.

Can you check if the time of the shutdown match the rolling of the log ?

>
> Jan 22 00:42:28 smtp.example.com <debug> slapd[11955]: <=
> bdb_inequality_candidates: (modifyTimestamp) not indexed
> Jan 22 00:42:29 smtp.example.com <debug> slapd[11955]: <=
> bdb_inequality_candidates: (modifyTimestamp) not indexed
> Jan 22 00:42:30 smtp.example.com <debug> slapd[11955]: <=
> bdb_inequality_candidates: (modifyTimestamp) not indexed
> Jan 22 00:42:37 smtp.example.com <debug> slapd[11955]: daemon: shutdown
> requested and initiated.
> Jan 22 00:42:37 smtp.example.com <debug> slapd[11955]: slapd shutdown:
> waiting for 0 threads to terminate
> Jan 22 00:42:38 smtp.example.com <debug> slapd[11955]: slapd stopped.
> Jan 22 00:42:39 smtp.example.com <debug> slapd[28288]: @(#) $OpenLDAP: slapd
> 2.3.43 (Dec 18 2008 04:41:25) $
>        kolab at vps.example.com:/kolab/RPM/TMP/openldap-2.3.43/servers/slapd
>
>
> _______________________________________________
> 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 alex at swiftnetcomputers.biz  Mon Jan 26 20:19:23 2009
From: alex at swiftnetcomputers.biz (Alex Chejlyk)
Date: Mon, 26 Jan 2009 14:19:23 -0500
Subject: Kolab Mail archiving - software, methods, experiences?
In-Reply-To: <497C4F1A.6000904@cburghardt.com>
References: <4978634D.7000801@FuH-E.de> <497A3FF0.20401@swiftnetcomputers.biz>
	<497C4F1A.6000904@cburghardt.com>
Message-ID: <497E0CBB.8050005@swiftnetcomputers.biz>

Carsten Burghardt wrote:
> Alex Chejlyk schrieb:
>> Here is what I've done.
>>
>> I use rsync to copy the whole /kolab folder to a backup server. I do 
>> this at 2:00am. I do take the server offline from 2:00am to 2:30am.
>>
>> You can leave kolab up and still use rsync, but you must export the 
>> mailbox db. I think the info is on the wiki.
>>
>> I also have scripts that run from each users workstation to archive 
>> Thunderbird's mail. This is a redundant solution, but I find two backups 
>> are always better than one.
>>
>>
>> I'm sure there are many much more elegant solutions, but this works for me.
>>   
> But this is not an archiving solution as you are talking about a backup. 
> If the user deletes the mail from the mailbox it will also be gone from 
> your backup. You can keep old versions of course but then you have to 
> restore the old state and can not simply search through your archive. 
> Normally backup and archiving have to be setup in parallel.
> 
> 
> Carsten
> 
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
> 

Actually it is an archiving solution.
I use rsync --link-dest=/path2/fullark
The full sync is on the 1st of the month, but before the full sync is 
done, I copy the month to an archive folder. I have (incremental) 
backups for everyday of the month going back to late 2007 ; )
Space is my big issue.

Cheers,

Alex C.



From mike at rochestervball.com  Mon Jan 26 21:24:53 2009
From: mike at rochestervball.com (Michael Harnden)
Date: Mon, 26 Jan 2009 15:24:53 -0500
Subject: Accessing Horde outside home network
Message-ID: <200901261524.53454.mike@rochestervball.com>

I recently migrated from an openSUSE 10.1 installation running natively to a OpenPKG installation (v 
2.2) on Debian Etch. I use Kolab/Horde as a home email server. Works great for my wife and I who 
both travel a lot. The migration went smoothly using my backups. My problem lies in accessing Horde 
from outside of my home network.

With my openSUSE installation I could use dyndns.org to access my installation. With the Debian 
server, once I log in, I am redirected to using my home servers fqdn (home-server.site). Can I 
correct this on my new installation without creating a huge security hole? Or am I better off 
setting up a VPN server (assuming that would work).

Thanks,
Mike


From johnm at advocap.org  Mon Jan 26 21:34:05 2009
From: johnm at advocap.org (John McMonagle)
Date: Mon, 26 Jan 2009 14:34:05 -0600
Subject: kolab ldap migration questions.
In-Reply-To: <200901231056.27402.bernhard@intevation.de>
References: <200901221615.38062.johnm@advocap.org>
	<200901231056.27402.bernhard@intevation.de>
Message-ID: <497E1E3D.1040209@advocap.org>

Bernard

Thanks for the information.
Digged a little deeper and have more questions.

Bernhard Reiter wrote:
> On Donnerstag, 22. Januar 2009, John McMonagle wrote:
>   
>> Here is  one of our current records:
>> dn: uid=bradb,ou=People,dc=advocap,dc=org
>> uid: bradb
>>     
>> From kolab test:
>> dn: cn=Brad Bingham,dc=advocap,dc=org
>>     
Doesn't a dn have to be unique.
If so it's probable a larger organization will have more than one person 
with the same name.
uid needs to be unique anyway.

If I were to keep our method is there any "simple" way to change 
kolab's  settings.

Particularly the user data is used by a lot of different programs. It 
makes me concerned if forced into a particular format.  What do I do 
when 2 systems require different formats.

Sort of related.
If an external program creates a new ldap user does one have to manually 
create the imap mailbox?

I doesn't see anything in kolab admin concerning groups.
Do I need to be concerned migrating groups at all?

I see a substantial difference in mailing lists :-(
A simple example
kolab:
dn: cn=postmaster at advocap.org,dc=advocap,dc=org
objectClass: top
objectClass: kolabGroupOfNames
cn: postmaster at advocap.org
mail: postmaster at advocap.org
member: cn=John McMonagle,dc=advocap,dc=org
structuralObjectClass: kolabGroupOfNames

advocap:
# spam, Aliases, advocap.org
dn: cn=spam,ou=Aliases,dc=advocap,dc=org
cn: spam
rfc822MailMember: sysmail
objectClass: nisMailAlias

Have the company mailing lists defined as rfc822MailMember.
No way a simple search and replace will fix this :-(
I could edit /kolab/etc/postfix/ldapdistlist.cf
That will make postfix happy but am I likely to regret it?

Was thinking maybe could run both mailing list methods  at least for a 
while.

Thanks

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/20090126/dac9d269/johnm.bin

From yugm6161 at yahoo.com  Tue Jan 27 02:56:48 2009
From: yugm6161 at yahoo.com (Paul Franklin)
Date: Mon, 26 Jan 2009 17:56:48 -0800 (PST)
Subject: No subject
Message-ID: <808802.46547.qm@web59303.mail.re1.yahoo.com>

One of you wrote an excellent howto for following the trail of an email from the time it arrives until it is delivered. ?Would you please point me again to that? ?I thought I had bookmarked it but cannot find it, and I have looked at wiki but cannot seem to see it.I have an occasionally recurring problem in which all mail gets stopped somewhere for a matter of hours or (in one case) days. ?Then it suddenly starts flowing again. ?I really need to find out where that happens, and I hope that the trail will provide the clues I need.--Paul


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20090126/1ed277be/attachment.html

From admin at jmay.org  Mon Jan 26 21:17:15 2009
From: admin at jmay.org (Jochen May)
Date: Mon, 26 Jan 2009 21:17:15 +0100
Subject: Crash of Kontact on Windows
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAJ7BXRqPWfdNkLKYTJ3u6xjCgAAAEAAAAJdvFA+vM/9ClS7Fd4HewooBAAAAAA==@jmay.org>

 

Hi Bernhard,
> 
> On Sonntag, 25. Januar 2009, Jochen May wrote:
> > i try kontact on a windows xp system. For a couple of days,
> > it run without any problems. Now i get the problem, each time
> > when i check my folders for new mail, i get a error
> > "assertion failed". a screenshot is attached.
> 
> try to rebuild the index of all folders.
OK, this was the first try. after this i don?t get the error 
message like bevor. The log-file is from a later rebuild of the index.
 
> > i try to make a backtrace, but get only the message, that
> > there are "no stack". i miss something?
> 
> Did you manage to get gdb stop there?
> Maybe the info message of the KDE subsystem will help us,
> see DebugView (also added to the new section
> https://wiki.kolab.org/index.php/Kontact_for_Windows_(beta-hug
e-debug)#Diagnostics )
 
> > is it normal, that on kalender, kontakt, journal, aufgaben
> > are the folder structure like on screenshot kontact2.jpg?
> > 
> > No, not at all.
> It?s now more and more courriose. i also try to rebuild the 
> index of the kalender (with the hope, that erverything went 
> out fine). finally i get this, what you see on the screenshot. 
 
> > and when i check my mails, i get first this message like on
> > screenshot kontact3.jpg.
> > also, i have a couple of subfolders. but i only see the first
> > sub-level of the folders. everything what is deeper than one
> > level, i don?t see. any idees?
 
> Well your index seems to be corrupt for sure. So unless you 
> clean up,
> > stuff may stay strange.
> > We need to reproduce how you've got there, to be able to fix 
> > the underlying 
> > defect.
if you dont need any further information, i would clean up my 
complete installtion and start at zero.

greetings,
jochen
-------------- n?chster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : kontact.jpg
Dateityp    : image/jpeg
Dateigr??e  : 27017 bytes
Beschreibung: nicht verf?gbar
URL         : http://kolab.org/pipermail/kolab-users/attachments/20090126/af2e1b8a/kontact-0001.jpg
-------------- n?chster Teil --------------
Ein Dateianhang mit Bin?rdaten wurde abgetrennt...
Dateiname   : rebuild_all_folder.LOG
Dateityp    : application/octet-stream
Dateigr??e  : 30444 bytes
Beschreibung: nicht verf?gbar
URL         : http://kolab.org/pipermail/kolab-users/attachments/20090126/af2e1b8a/rebuild_all_folder-0001.exe

From bernhard at intevation.de  Tue Jan 27 08:49:34 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 27 Jan 2009 08:49:34 +0100
Subject: Accessing Horde outside home network
In-Reply-To: <200901261524.53454.mike@rochestervball.com>
References: <200901261524.53454.mike@rochestervball.com>
Message-ID: <200901270849.34772.bernhard@intevation.de>

On Montag, 26. Januar 2009, Michael Harnden wrote:
> With my openSUSE installation I could use dyndns.org to access my
> installation. With the Debian server, once I log in, I am redirected to
> using my home servers fqdn (home-server.site).

Should be the same as on opensuse and possible.
First it is interesting to know which part of software does the redirect.
(You could check the apache logs for instance.)

-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090127/5edbabf3/attachment.bin

From bernhard at intevation.de  Tue Jan 27 08:58:11 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 27 Jan 2009 08:58:11 +0100
Subject: kolab ldap migration questions.
In-Reply-To: <497E1E3D.1040209@advocap.org>
References: <200901221615.38062.johnm@advocap.org>
	<200901231056.27402.bernhard@intevation.de>
	<497E1E3D.1040209@advocap.org>
Message-ID: <200901270858.11402.bernhard@intevation.de>

John,

On Montag, 26. Januar 2009, John McMonagle wrote:
> Bernhard Reiter wrote:

> > On Donnerstag, 22. Januar 2009, John McMonagle wrote:

> >> Here is ?one of our current records:
> >> dn: uid=bradb,ou=People,dc=advocap,dc=org
> >> uid: bradb
> >> ? ?
> >> From kolab test:
> >> dn: cn=Brad Bingham,dc=advocap,dc=org
> >> ? ?
>
> Doesn't a dn have to be unique.
> If so it's probable a larger organization will have more than one person
> with the same name.
> uid needs to be unique anyway.

it is true that a dn must be unique. 
Larger organisations could consider using more dn elements
or a different dn scheme. The current scheme has a history,
for some discussion see
kolab/issue1549 (Patch to change dn: cn=... -> dn: mail=...)

> If I were to keep our method is there any "simple" way to change
> kolab's ?settings.
>
> Particularly the user data is used by a lot of different programs. It
> makes me concerned if forced into a particular format. ?What do I do
> when 2 systems require different formats.

That is a general problem with several applications trying to use a directory 
server and (missdesigned) LDAP.
You need to check the requirements and details and might need to adapt
some of the applications. Kolab Server can be adapted a lot, so you are not 
completely at a loss here. Still doing this change might require some 
experience. I wish it was simpler, but apparently it isn't.

> Sort of related.
> If an external program creates a new ldap user does one have to manually
> create the imap mailbox?

No, kolabd will pick changes up and create the imap account for you.
So using external LDAP tools is fine.

> I doesn't see anything in kolab admin concerning groups.
> Do I need to be concerned migrating groups at all?

Maybe.

> I see a substantial difference in mailing lists :-(
> A simple example
> kolab:
> dn: cn=postmaster at advocap.org,dc=advocap,dc=org
> objectClass: top
> objectClass: kolabGroupOfNames
> cn: postmaster at advocap.org
> mail: postmaster at advocap.org
> member: cn=John McMonagle,dc=advocap,dc=org
> structuralObjectClass: kolabGroupOfNames
>
> advocap:
> # spam, Aliases, advocap.org
> dn: cn=spam,ou=Aliases,dc=advocap,dc=org
> cn: spam
> rfc822MailMember: sysmail
> objectClass: nisMailAlias
>
> Have the company mailing lists defined as rfc822MailMember.
> No way a simple search and replace will fix this :-(
> I could edit /kolab/etc/postfix/ldapdistlist.cf
> That will make postfix happy but am I likely to regret it?

I would make a list of necessary email paths and tests this after a change
to be sure. Those kind of configuration changes are sometimes necessary.

> Was thinking maybe could run both mailing list methods ?at least for a
> while.

Sure, why not.
Note the Kolab's groups (aka server distribution lists) can be used to set 
ACLs for IMAP folders.

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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090127/dfdfdf74/attachment.bin

From bernhard at intevation.de  Tue Jan 27 09:01:11 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Tue, 27 Jan 2009 09:01:11 +0100
Subject: Crash of Kontact on Windows
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAAJ7BXRqPWfdNkLKYTJ3u6xjCgAAAEAAAAJdvFA+vM/9ClS7Fd4HewooBAAAAAA==@jmay.org>
References: <!&!AAAAAAAAAAAYAAAAAAAAAJ7BXRqPWfdNkLKYTJ3u6xjCgAAAEAAAAJdvFA+vM/9ClS7Fd4HewooBAAAAAA==@jmay.org>
Message-ID: <200901270901.11671.bernhard@intevation.de>

On Montag, 26. Januar 2009, Jochen May wrote:
> if you dont need any further information, i would clean up my
> complete installtion and start at zero.

Go ahead. 
(You could try refreshing the cache first, which basically does download all 
emails from the server again.)


-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090127/c87a5775/attachment.bin

From aspineux at gmail.com  Tue Jan 27 09:11:18 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Tue, 27 Jan 2009 09:11:18 +0100
Subject: 
In-Reply-To: <808802.46547.qm@web59303.mail.re1.yahoo.com>
References: <808802.46547.qm@web59303.mail.re1.yahoo.com>
Message-ID: <71fe4e760901270011k9fc4dcfv56edc9d3f30fbc02@mail.gmail.com>

On Tue, Jan 27, 2009 at 2:56 AM, Paul Franklin <yugm6161 at yahoo.com> wrote:
> One of you wrote an excellent howto for following the trail of an email from
> the time it arrives until it is delivered.  Would you please point me again
> to that?  I thought I had bookmarked it but cannot find it, and I have
> looked at wiki but cannot seem to see it.

search for "spineux" in the wiki :-)
I try to elegantly put my name in every wiki I write, to make them
easy to find (by myself first :-)

>
> I have an occasionally recurring problem in which all mail gets stopped
> somewhere for a matter of hours or (in one case) days.  Then it suddenly
> starts flowing again.  I really need to find out where that happens, and I
> hope that the trail will provide the clues I need.

Good luck

>
> --Paul
>
> _______________________________________________
> 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 Jan 27 10:20:48 2009
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Tue, 27 Jan 2009 10:20:48 +0100
Subject: Again: MySQL
Message-ID: <497ED1F0.2070907@FuH-E.de>

Good morning everyone,

I have the need for MySQL in the Kolab php. I have noticed that phpinfo 
shows the mysql option is not set in compile time.

The possibility Alain once mentioned (found in: 
<http://kolab.org/pipermail/kolab-users/2007-March/006078.html>)
| You can allso REcompile the php package ALONE using something like
| /kolab/bin/*openpkg* rpm --rebuild **php?????.src.rpm --define
| "with_???? yes"
| ****/kolab/bin/*openpkg* rpm -Uvh /kolab/RPM/PKG/php????.rpm

does work, but then many needed options for Kolab will be missing. After 
some testing I have lost myself in the 'define'-jungle, so I looked for 
a more 'wholesome' solution. Now, in the answer to Alain above I found 
(from Gunnar, 
<http://kolab.org/pipermail/kolab-users/2007-March/006072.html>):

| the PHP package within Kolab is not compiled with the mysql
| extension. So you would need to add the necessary flag "--with=mysql"
| to you obmtool.conf file before installing Kolab.

...but this obmtool.conf is nowhere to be found. Please, any hint? Has 
the name changed, perhaps? Or does Kolab nowadays use a different way?

Best regards, Christian


From devgioiatech at gmail.com  Tue Jan 27 19:20:24 2009
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Tue, 27 Jan 2009 19:20:24 +0100
Subject: multiple kolab installation question :(
In-Reply-To: <20090125092717.16422syrc3uaqs2s@webmail.pardus.de>
References: <d53357b70901221203q4b3c8ac3le80cf06b3bd7052@mail.gmail.com>
	<200901230837.30745.steuwer@univention.de>
	<d53357b70901230415t2780724dncd50d77040cf6d46@mail.gmail.com>
	<20090125092717.16422syrc3uaqs2s@webmail.pardus.de>
Message-ID: <d53357b70901271020u52548ccdke2af2c2e651c8700@mail.gmail.com>

hi guys...

i'm tring the solution putting the webmail server as master kolab and
more slave as local mail server,

-webmail (master)
|- site1 (slave)
|- site2 (slave)
|- etc... (slave)


I create a user on site1 from webmail and... i always login on my user
even if site1 server is powered off... :-|
if i shut down webmail, i never login on my user on site1

peraphs it's a stupid question but, if my mailbox is stored on the
slave server i can access it only if the slave server is available and
if my master server should access my mailbox also if master si
unavailable? is correct?

If no, my problem couldn't be solved by installing all kolab as slave
of a single common server, because i need all local users  to be
stored on their local kolab without any affect from the master or from
other slave...

anyone has suggestion about the use of a single webmail for all kolab
installation?
for example, if i i want to install a server with only HORDE there is
something to do on that installation make it works correctly with all
kolab?

Thanks.


2009/1/25 Gunnar Wrobel <wrobel at pardus.de>:
> Quoting Antonio Straziota <devgioiatech at gmail.com>:
>
>> Thanks for reply...
>>
>>> Horde should be able to connect to the users kolabHomeServer instead of
>>> localhost. I'm not sure how Horde is preconfigured in native kolab
>>> installations, but it is able to do that in general.
>>
>> Ok ,so, from my "salve webmail" of the master i can access to mail box
>> on each other slave?
>
> Yes, this should work. If you have problems with this, please report back
> and we'll make it work ;)
>
> Cheers,
>
> Gunnar
>
>> I'll try it :-)
>>
>>> One drawback in your constellation are shared folders, which are shared
>>> on one
>>> server only. A user on server A can't share stuff with a user on server
>>> B.
>>> This can be avoided with "cyrus murder", a kind of cluster-enhancement
>>> for
>>> cyrus. It is a bit tricky in setup and certainly will need patches
>>> against
>>> kolabd.
>>
>> At this time I don't need this... but i'll study it for future ;-)
>>
>>> Mhm, what are your goals? Centralized user management (Kolab) or
>>> decentralized
>>> user management (indipendet samba sites)?
>>
>> I need decentralized one: every site has kolab server and a file
>> server accessible from user of THAT site.
>>
>> Really, my problem is that i've only one entry/exit point from/to
>> internet.
>> I have to make all kolab accessible from internet from that point, but
>> all kolab server must be indipendent from the other.
>>
>> Thanks again.
>> I'll try this architecture.
>>
>> _______________________________________________
>> 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.
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
>


From bernhard at intevation.de  Wed Jan 28 11:22:51 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 28 Jan 2009 11:22:51 +0100
Subject: multiple kolab installation question :(
In-Reply-To: <d53357b70901271020u52548ccdke2af2c2e651c8700@mail.gmail.com>
References: <d53357b70901221203q4b3c8ac3le80cf06b3bd7052@mail.gmail.com>
	<20090125092717.16422syrc3uaqs2s@webmail.pardus.de>
	<d53357b70901271020u52548ccdke2af2c2e651c8700@mail.gmail.com>
Message-ID: <200901281122.51710.bernhard@intevation.de>

On Dienstag, 27. Januar 2009, Antonio Straziota wrote:
> if my mailbox is stored on the
> slave server i can access it only if the slave server is available 

Correct. (I mean if no server serves the filesystem, you cannot access it 
obviously.)

> and 
> if my master server should access my mailbox also if master si
> unavailable? is correct?

I do not know what you mean.
The master server cannot connect to the IMAP server on the slave server
if this is not running. 

Note that the "master" "slave" terminology in Kolab Server mainly means 
master and slave for the directory service. From the view of mailboxes it is 
better to think of homeserver and non-homeserver.
(So for some users the "master" is home and for other users it is not.)

The Webclient needs to make contact to the Homeserver for the user, because 
that is where the folders are.






-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090128/3ca081a7/attachment.bin

From bernhard at intevation.de  Wed Jan 28 11:35:05 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Wed, 28 Jan 2009 11:35:05 +0100
Subject: Again: MySQL
In-Reply-To: <497ED1F0.2070907@FuH-E.de>
References: <497ED1F0.2070907@FuH-E.de>
Message-ID: <200901281135.12560.bernhard@intevation.de>

On Dienstag, 27. Januar 2009, Christian R??ler wrote:
> | the PHP package within Kolab is not compiled with the mysql
> | extension. So you would need to add the necessary flag "--with=mysql"
> | to you obmtool.conf file before installing Kolab.
>
> ...but this obmtool.conf is nowhere to be found. Please, any hint? Has
> the name changed, perhaps? Or does Kolab nowadays use a different way?

obmtool has been replaced by install-kolab.sh, open this in an editor.



-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090128/00cf6731/attachment.bin

From devgioiatech at gmail.com  Wed Jan 28 12:10:37 2009
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Wed, 28 Jan 2009 12:10:37 +0100
Subject: multiple kolab installation question :(
In-Reply-To: <200901281122.51710.bernhard@intevation.de>
References: <d53357b70901221203q4b3c8ac3le80cf06b3bd7052@mail.gmail.com>
	<20090125092717.16422syrc3uaqs2s@webmail.pardus.de>
	<d53357b70901271020u52548ccdke2af2c2e651c8700@mail.gmail.com>
	<200901281122.51710.bernhard@intevation.de>
Message-ID: <d53357b70901280310y6738381am8ebfd7b9b728f491@mail.gmail.com>

So,
i made bootstrap for "webmail" server as master kolab and "site1" as
slave of the first one.

which kind of info resides on the master kolab about users hosted on the slave?
why, if i shut down the slave, i can access from master to a user that
resides on slave? :'-(
As you wrote, this is wrong! I should not access users of the slave if
this server is powered off!

About the sentence you don't understand, i wrong to wrote it :). The
question is: can i access users on my slave also if the master is
unavailable (powered off, ldap or any service not running)?

can you help me to understand?

or anyone as a suggestion about compiling only horde for webmail use
on multiple kolab?

Thanks again... (HELP MEEEE, PLEASE :D)


2009/1/28 Bernhard Reiter <bernhard at intevation.de>:
> On Dienstag, 27. Januar 2009, Antonio Straziota wrote:
>> if my mailbox is stored on the
>> slave server i can access it only if the slave server is available
>
> Correct. (I mean if no server serves the filesystem, you cannot access it
> obviously.)
>
>> and
>> if my master server should access my mailbox also if master si
>> unavailable? is correct?
>
> I do not know what you mean.
> The master server cannot connect to the IMAP server on the slave server
> if this is not running.
>
> Note that the "master" "slave" terminology in Kolab Server mainly means
> master and slave for the directory service. From the view of mailboxes it is
> better to think of homeserver and non-homeserver.
> (So for some users the "master" is home and for other users it is not.)
>
> The Webclient needs to make contact to the Homeserver for the user, because
> that is where the folders are.
>
>
>
>
>
>
> --
> 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 ludwig.reiter at intevation.de  Wed Jan 28 12:44:14 2009
From: ludwig.reiter at intevation.de (Ludwig Reiter)
Date: Wed, 28 Jan 2009 12:44:14 +0100
Subject: Another free/busy odditiy - Kontact vs. DNS?
In-Reply-To: <200901221733.43555.itsef-admin@brightsight.com>
References: <200901221733.43555.itsef-admin@brightsight.com>
Message-ID: <200901281244.15081.ludwig.reiter@intevation.de>

Hi,

Am Donnerstag, 22. Januar 2009 17:33:43 schrieb ITSEF Admin:
> Hi all,
>
> while I was resolving my own problem with Kontact and free/busy (see list
> archives... it was a problem with a SSL certificate), several other users
> came to me also with free/busy problems. Again, free/busy simply did not
> work - and I was not even able to find any requests from them in the server
> logs. After some experimenting I finally found the solution for this
> problem as well: Contrary to our other users (and myself), the users with
> the problem had their FreeBusyRetrieveUrl set to:
> "https://KOLABSERVER/freebusy/" All other users have
> "https://KOLABSERVER.DOM.AIN/freebusy/". To my great surprise, only the
> second version (with the full domain) works. This is especially puzzling,
> as "host KOLABSERVER" yields the same result as "host KOLABSERVER.DOM.AIN"
> on the command line. Same with Konqueror - it does not matter whether I
> enter the domain or not, Konqueror does display the correct page on our
> Kolab server. Kontact seems to be the only exception.
>
> Does anybody have an idea why this is? Should I file a bugreport?
Mmh, I have tried to reproduce this problem. I think it is a problem with 
korganizer/kontact.  Kontact/korganizer checks, if kolabserver and user id 
matchs before getting the fb list from the user id.

As example: both abc.def.xy and abc.xy map to the same kolab server. The user 
id of a test account is test at def.xy.
The configured "https://abc.def.xy/freebusy" works to get the fb list.
But "https://abc.xy/freebusy" fails, because abc.xy doesn't match the def.xy 
part of the id part of the account.

The output in this case is:
korganizer: Host 'abc.hq' doesn't match email 'test at def.xy'
korganizer: FreeBusyManager::processRetrieveQueue(): url:
korganizer: Invalid FB URL

There must be a reason for this check. I will ask this on the devel list.

Regards,
Ludwig

-- 
Intevation GmbH, Osnabr?ck
Firmensitz: Neuer Graben 17, 49074 Osnabr?ck
Registereintrag: Amtsgericht Osnabr?ck, HR B 18998
Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From itsef-admin at brightsight.com  Wed Jan 28 13:44:20 2009
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Wed, 28 Jan 2009 13:44:20 +0100
Subject: Another free/busy odditiy - Kontact vs. DNS?
In-Reply-To: <200901281244.15081.ludwig.reiter@intevation.de>
References: <200901221733.43555.itsef-admin@brightsight.com>
	<200901281244.15081.ludwig.reiter@intevation.de>
Message-ID: <200901281344.20186.itsef-admin@brightsight.com>

On Wednesday 28 January 2009 12:44:14 Ludwig Reiter wrote:
> Am Donnerstag, 22. Januar 2009 17:33:43 schrieb ITSEF Admin:
[...]
> >  Contrary to our other users (and myself), the users
> > with the problem had their FreeBusyRetrieveUrl set to:
> > "https://KOLABSERVER/freebusy/" All other users have
> > "https://KOLABSERVER.DOM.AIN/freebusy/". To my great surprise, only the
> > second version (with the full domain) works.
[...]

> Mmh, I have tried to reproduce this problem. I think it is a problem with
> korganizer/kontact.  Kontact/korganizer checks, if kolabserver and user id
> matchs before getting the fb list from the user id.
>
> As example: both abc.def.xy and abc.xy map to the same kolab server. The
> user id of a test account is test at def.xy.
> The configured "https://abc.def.xy/freebusy" works to get the fb list.
> But "https://abc.xy/freebusy" fails, because abc.xy doesn't match the
> def.xy part of the id part of the account.
>
> The output in this case is:
> korganizer: Host 'abc.hq' doesn't match email 'test at def.xy'
> korganizer: FreeBusyManager::processRetrieveQueue(): url:
> korganizer: Invalid FB URL

I never got this output (just tried again to be sure), but it sure looks like 
what we are experiencing here. Out of interest: In your test, was "Use full 
e-mail address for retrieval" on or off?


> There must be a reason for this check. I will ask this on the devel list.

Yes, I saw your mail on devel first, which triggered me to check whether I can 
see that output you mention. It's supposed to show up on the 
console/in .xsession-errors, right?

Regards,

Thomas


From ludwig.reiter at intevation.de  Thu Jan 29 10:15:55 2009
From: ludwig.reiter at intevation.de (Ludwig Reiter)
Date: Thu, 29 Jan 2009 10:15:55 +0100
Subject: Another free/busy odditiy - Kontact vs. DNS?
In-Reply-To: <200901281344.20186.itsef-admin@brightsight.com>
References: <200901221733.43555.itsef-admin@brightsight.com>
	<200901281244.15081.ludwig.reiter@intevation.de>
	<200901281344.20186.itsef-admin@brightsight.com>
Message-ID: <200901291015.56081.ludwig.reiter@intevation.de>

Hi

Am Mittwoch, 28. Januar 2009 13:44:20 schrieb ITSEF Admin:
> On Wednesday 28 January 2009 12:44:14 Ludwig Reiter wrote:
> > Am Donnerstag, 22. Januar 2009 17:33:43 schrieb ITSEF Admin:
>
> [...]
>
> > >  Contrary to our other users (and myself), the users
> > > with the problem had their FreeBusyRetrieveUrl set to:
> > > "https://KOLABSERVER/freebusy/" All other users have
> > > "https://KOLABSERVER.DOM.AIN/freebusy/". To my great surprise, only the
> > > second version (with the full domain) works.
>
> [...]
>
> > Mmh, I have tried to reproduce this problem. I think it is a problem with
> > korganizer/kontact.  Kontact/korganizer checks, if kolabserver and user
> > id matchs before getting the fb list from the user id.
> >
> > As example: both abc.def.xy and abc.xy map to the same kolab server. The
> > user id of a test account is test at def.xy.
> > The configured "https://abc.def.xy/freebusy" works to get the fb list.
> > But "https://abc.xy/freebusy" fails, because abc.xy doesn't match the
> > def.xy part of the id part of the account.
> >
> > The output in this case is:
> > korganizer: Host 'abc.hq' doesn't match email 'test at def.xy'
> > korganizer: FreeBusyManager::processRetrieveQueue(): url:
> > korganizer: Invalid FB URL
>
> I never got this output (just tried again to be sure), but it sure looks
> like what we are experiencing here. Out of interest: In your test, was "Use
> full e-mail address for retrieval" on or off?
Mmh, that means perhaps I have done a wrong test. "Use full e-mail address for
retrival" was on.

> > There must be a reason for this check. I will ask this on the devel list.
>
> Yes, I saw your mail on devel first, which triggered me to check whether I
> can see that output you mention. It's supposed to show up on the
> console/in .xsession-errors, right?
Yes, right.

Regards,
     Ludwig
-- 
Intevation GmbH, Osnabr?ck
Firmensitz: Neuer Graben 17, 49074 Osnabr?ck
Registereintrag: Amtsgericht Osnabr?ck, HR B 18998
Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner


From itsef-admin at brightsight.com  Thu Jan 29 14:27:37 2009
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Thu, 29 Jan 2009 14:27:37 +0100
Subject: Another free/busy odditiy - Kontact vs. DNS?
In-Reply-To: <200901291015.56081.ludwig.reiter@intevation.de>
References: <200901221733.43555.itsef-admin@brightsight.com>
	<200901281344.20186.itsef-admin@brightsight.com>
	<200901291015.56081.ludwig.reiter@intevation.de>
Message-ID: <200901291427.37878.itsef-admin@brightsight.com>

On Thursday 29 January 2009 10:15:55 Ludwig Reiter wrote:
> Am Mittwoch, 28. Januar 2009 13:44:20 schrieb ITSEF Admin:
> > On Wednesday 28 January 2009 12:44:14 Ludwig Reiter wrote:
[...]
> > > The output in this case is:
> > > korganizer: Host 'abc.hq' doesn't match email 'test at def.xy'
> > > korganizer: FreeBusyManager::processRetrieveQueue(): url:
> > > korganizer: Invalid FB URL
> >
> > I never got this output (just tried again to be sure), but it sure looks
> > like what we are experiencing here. Out of interest: In your test, was
> > "Use full e-mail address for retrieval" on or off?
>
> Mmh, that means perhaps I have done a wrong test. "Use full e-mail address
> for retrival" was on.

I just verified that in my case it does not matter whether I have that setting 
on or off. Only https://HOST.DOM.AIN/freebusy/ will work - 
https://HOST/freebusy/ will not.

One thing I've noticed: If I use the "short" form (HOST only), *no* requests 
are sent from Kontact to the Kolab server. I can see no activity 
in /kolab/var/apache/log/apache-access.log 
If I change the URL back to HOST.DOM.AIN, the requests can be seen. In my 
opinion, this does fit with your description - if Kontact performs the check 
you mentioned first, it probably never bothers to query the server if the 
check fails.

Still, I cannot see the output you mention - neither on the console, nor 
in .xsessions-error.

Cheerio,

Thomas


From wrobel at pardus.de  Thu Jan 29 17:03:24 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 29 Jan 2009 17:03:24 +0100
Subject: multiple kolab installation question :(
In-Reply-To: <d53357b70901280310y6738381am8ebfd7b9b728f491@mail.gmail.com>
References: <d53357b70901221203q4b3c8ac3le80cf06b3bd7052@mail.gmail.com>
	<20090125092717.16422syrc3uaqs2s@webmail.pardus.de>
	<d53357b70901271020u52548ccdke2af2c2e651c8700@mail.gmail.com>
	<200901281122.51710.bernhard@intevation.de>
	<d53357b70901280310y6738381am8ebfd7b9b728f491@mail.gmail.com>
Message-ID: <20090129170324.20073sofn36k6stw@webmail.pardus.de>

Quoting Antonio Straziota <devgioiatech at gmail.com>:

> So,
> i made bootstrap for "webmail" server as master kolab and "site1" as
> slave of the first one.
>
> which kind of info resides on the master kolab about users hosted on  
> the slave?

The LDAP tree is replicated completely, meaning that all users are  
stored in LDAP on both servers.

> why, if i shut down the slave, i can access from master to a user that
> resides on slave? :'-(

What do you mean by "access" here? IMAP access? If the slave is  
powered down I doubt you can read the mails of the users.

> As you wrote, this is wrong! I should not access users of the slave if
> this server is powered off!

True.

In case you mean that you can login via Horde even if IMAP is powered  
down: This might be related to  
https://www.intevation.de/roundup/kolab/issue3282.

>
> About the sentence you don't understand, i wrong to wrote it :). The
> question is: can i access users on my slave also if the master is
> unavailable (powered off, ldap or any service not running)?

Yes.

>
> can you help me to understand?
>
> or anyone as a suggestion about compiling only horde for webmail use
> on multiple kolab?

The current suggestion is to install a full Kolab server for that. You  
could probably also download the corresponding horde-webmail release  
and apply the Kolab patch from CVS. But that requires a bit more  
knowledge.

Cheers,

Gunnar

>
> Thanks again... (HELP MEEEE, PLEASE :D)
>
>
> 2009/1/28 Bernhard Reiter <bernhard at intevation.de>:
>> On Dienstag, 27. Januar 2009, Antonio Straziota wrote:
>>> if my mailbox is stored on the
>>> slave server i can access it only if the slave server is available
>>
>> Correct. (I mean if no server serves the filesystem, you cannot access it
>> obviously.)
>>
>>> and
>>> if my master server should access my mailbox also if master si
>>> unavailable? is correct?
>>
>> I do not know what you mean.
>> The master server cannot connect to the IMAP server on the slave server
>> if this is not running.
>>
>> Note that the "master" "slave" terminology in Kolab Server mainly means
>> master and slave for the directory service. From the view of mailboxes it is
>> better to think of homeserver and non-homeserver.
>> (So for some users the "master" is home and for other users it is not.)
>>
>> The Webclient needs to make contact to the Homeserver for the user, because
>> that is where the folders are.
>>
>>
>>
>>
>>
>>
>> --
>> 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
>



-- 
______ 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/20090129/110e46de/attachment.bin

From wrobel at pardus.de  Thu Jan 29 17:14:27 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 29 Jan 2009 17:14:27 +0100
Subject: Accessing Horde outside home network
In-Reply-To: <200901261524.53454.mike@rochestervball.com>
References: <200901261524.53454.mike@rochestervball.com>
Message-ID: <20090129171427.11563kn83hfakt2c@webmail.pardus.de>

Quoting Michael Harnden <mike at rochestervball.com>:

> I recently migrated from an openSUSE 10.1 installation running  
> natively to a OpenPKG installation (v
> 2.2) on Debian Etch. I use Kolab/Horde as a home email server. Works  
> great for my wife and I who
> both travel a lot. The migration went smoothly using my backups. My  
> problem lies in accessing Horde
> from outside of my home network.
>
> With my openSUSE installation I could use dyndns.org to access my  
> installation. With the Debian
> server, once I log in, I am redirected to using my home servers fqdn  
> (home-server.site). Can I
> correct this on my new installation without creating a huge security hole?

You should be able to correct this without any security problems. I  
assume that your server does not know that it is accessible via the  
dyndns.org fqdn. You can set the server name for horde in  
/kolab/var/kolab/www/horde/config/conf.php.

The relevant line is:

$conf['server']['name'] = $_SERVER['SERVER_NAME'];

You should be able to hard-code the server fqdn here. In general it is  
better though if the whole DNS setup is correct and your server is  
able to correctly identify itself. You might also edit /etc/hosts for  
that.

Cheers,

Gunnar

> Or am I better off
> setting up a VPN server (assuming that would work).
>
> Thanks,
> Mike
>
> _______________________________________________
> 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/20090129/202da13f/attachment.bin

From wrobel at pardus.de  Thu Jan 29 17:18:34 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 29 Jan 2009 17:18:34 +0100
Subject: Again: MySQL
In-Reply-To: <200901281135.12560.bernhard@intevation.de>
References: <497ED1F0.2070907@FuH-E.de>
	<200901281135.12560.bernhard@intevation.de>
Message-ID: <20090129171834.12764m8rdemdgfeo@webmail.pardus.de>

Quoting Bernhard Reiter <bernhard at intevation.de>:

> On Dienstag, 27. Januar 2009, Christian R??ler wrote:
>> | the PHP package within Kolab is not compiled with the mysql
>> | extension. So you would need to add the necessary flag "--with=mysql"
>> | to you obmtool.conf file before installing Kolab.
>>
>> ...but this obmtool.conf is nowhere to be found. Please, any hint? Has
>> the name changed, perhaps? Or does Kolab nowadays use a different way?
>
> obmtool has been replaced by install-kolab.sh, open this in an editor.

Yes, please try to add

-D apache_php::with_mysql=yes

in install-kolab.sh (line 25). I'm not 100% certain that this will  
work but please report back. If it works we should add it to the wiki,  
if not we should help you to get it to compile ;)

Cheers,

Gunnar

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



-- 
______ 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/20090129/3acefb5e/attachment.bin

From devgioiatech at gmail.com  Thu Jan 29 17:23:42 2009
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Thu, 29 Jan 2009 17:23:42 +0100
Subject: multiple kolab installation question :(
In-Reply-To: <20090129170324.20073sofn36k6stw@webmail.pardus.de>
References: <d53357b70901221203q4b3c8ac3le80cf06b3bd7052@mail.gmail.com>
	<20090125092717.16422syrc3uaqs2s@webmail.pardus.de>
	<d53357b70901271020u52548ccdke2af2c2e651c8700@mail.gmail.com>
	<200901281122.51710.bernhard@intevation.de>
	<d53357b70901280310y6738381am8ebfd7b9b728f491@mail.gmail.com>
	<20090129170324.20073sofn36k6stw@webmail.pardus.de>
Message-ID: <d53357b70901290823x4270a51ak1647f4606861a901@mail.gmail.com>

Thanks Gunnar!!!

> The LDAP tree is replicated completely, meaning that all users are stored in
> LDAP on both servers.

Do you know if when i apply the samba integration only on slaves, it
affect the webmail (kolab master) work (for example authentication)?

> What do you mean by "access" here? IMAP access? If the slave is powered down
> I doubt you can read the mails of the users.
>
>> As you wrote, this is wrong! I should not access users of the slave if
>> this server is powered off!
>
> True.
>
> In case you mean that you can login via Horde even if IMAP is powered down:
> This might be related to https://www.intevation.de/roundup/kolab/issue3282.

YES! it's my problem.

>
>>
>> About the sentence you don't understand, i wrong to wrote it :). The
>> question is: can i access users on my slave also if the master is
>> unavailable (powered off, ldap or any service not running)?
>
> Yes.

But i can't do this. I tried to power off the master... then i try to
login on the slave and i can't access on it

>>
>> can you help me to understand?
>>
>> or anyone as a suggestion about compiling only horde for webmail use
>> on multiple kolab?
>
> The current suggestion is to install a full Kolab server for that. You could
> probably also download the corresponding horde-webmail release and apply the
> Kolab patch from CVS. But that requires a bit more knowledge.
>

mmmhhh... Then i think i'll continue with master/slave configuration :D

> Cheers,
>
> Gunnar


Thanks again ;)


From wrobel at pardus.de  Thu Jan 29 17:31:54 2009
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 29 Jan 2009 17:31:54 +0100
Subject: multiple kolab installation question :(
In-Reply-To: <d53357b70901290823x4270a51ak1647f4606861a901@mail.gmail.com>
References: <d53357b70901221203q4b3c8ac3le80cf06b3bd7052@mail.gmail.com>
	<20090125092717.16422syrc3uaqs2s@webmail.pardus.de>
	<d53357b70901271020u52548ccdke2af2c2e651c8700@mail.gmail.com>
	<200901281122.51710.bernhard@intevation.de>
	<d53357b70901280310y6738381am8ebfd7b9b728f491@mail.gmail.com>
	<20090129170324.20073sofn36k6stw@webmail.pardus.de>
	<d53357b70901290823x4270a51ak1647f4606861a901@mail.gmail.com>
Message-ID: <20090129173154.2091130etosl4utc@webmail.pardus.de>

Quoting Antonio Straziota <devgioiatech at gmail.com>:

> Thanks Gunnar!!!
>
>> The LDAP tree is replicated completely, meaning that all users are stored in
>> LDAP on both servers.
>
> Do you know if when i apply the samba integration only on slaves, it
> affect the webmail (kolab master) work (for example authentication)?

It should not affect it as long as you don't touch central attributes  
such as the mail or uid attribute.

>
>> What do you mean by "access" here? IMAP access? If the slave is powered down
>> I doubt you can read the mails of the users.
>>
>>> As you wrote, this is wrong! I should not access users of the slave if
>>> this server is powered off!
>>
>> True.
>>
>> In case you mean that you can login via Horde even if IMAP is powered down:
>> This might be related to https://www.intevation.de/roundup/kolab/issue3282.
>
> YES! it's my problem.

While this issue is not on my list of tasks for 2.2.1 you will be able  
to configure a workaround for this in 2.2.1.

Cheers,

Gunnar

>
>>
>>>
>>> About the sentence you don't understand, i wrong to wrote it :). The
>>> question is: can i access users on my slave also if the master is
>>> unavailable (powered off, ldap or any service not running)?
>>
>> Yes.
>
> But i can't do this. I tried to power off the master... then i try to
> login on the slave and i can't access on it
>
>>>
>>> can you help me to understand?
>>>
>>> or anyone as a suggestion about compiling only horde for webmail use
>>> on multiple kolab?
>>
>> The current suggestion is to install a full Kolab server for that. You could
>> probably also download the corresponding horde-webmail release and apply the
>> Kolab patch from CVS. But that requires a bit more knowledge.
>>
>
> mmmhhh... Then i think i'll continue with master/slave configuration :D
>
>> Cheers,
>>
>> Gunnar
>
>
> Thanks again ;)
>
> _______________________________________________
> 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/20090129/6cba1367/attachment-0001.bin

From itsef-admin at brightsight.com  Thu Jan 29 17:35:44 2009
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Thu, 29 Jan 2009 17:35:44 +0100
Subject: Another free/busy odditiy - Kontact vs. DNS?
In-Reply-To: <200901230820.46839.steuwer@univention.de>
References: <200901221733.43555.itsef-admin@brightsight.com>
	<200901230820.46839.steuwer@univention.de>
Message-ID: <200901291735.44364.itsef-admin@brightsight.com>

On Friday 23 January 2009 08:20:44 Ingo Steuwer wrote:
> Am Donnerstag, 22. Januar 2009 schrieb ITSEF Admin:
[...]
> > After some experimenting I finally found the solution for
> > this problem as well: Contrary to our other users (and myself), the users
> > with the problem had their FreeBusyRetrieveUrl set to:
> > "https://KOLABSERVER/freebusy/" All other users have
> > "https://KOLABSERVER.DOM.AIN/freebusy/". To my great surprise, only the
> > second version (with the full domain) works.
[...] 
> this might be connected to your SSL-Issue. SSL-certificates are only valid
> for the FQDN (KOLABSERVER.DOM.AIN) of your server, not for the IP or
> hostname (KOLABSERVER). If you'll open https://KOLABSERVER with your
> browser you'll see a warning also. Maybe it is similar to your latest issue
> that kontact doesn't show such a warning but simply "ignores" the server
> because of the "invalied" SSL certificate.

Given the findings of Ludwig, I'd tend to assume that this problem is related 
to what he describes. Also, I was the only user in our company to run into 
SSL problems with Kontact, whereas several users ran into the problem I 
described above (funny enough, all of them had their Kontact configured by a 
colleague, who - not surprisingly - thought that HOST should work just as 
well as HOST.DOM.AIN.

I'm still surprised that I cannot see the console output Ludwig describes - as 
far as I can see, I'm using the same "--with-debug" (or suchlike) options for 
our Kubuntu packages as used in the Kolab Debian packages.

Cheerio,

Thomas


From bernhard at intevation.de  Fri Jan 30 08:59:50 2009
From: bernhard at intevation.de (Bernhard Reiter)
Date: Fri, 30 Jan 2009 08:59:50 +0100
Subject: Another free/busy odditiy - Kontact vs. DNS?
In-Reply-To: <200901291735.44364.itsef-admin@brightsight.com>
References: <200901221733.43555.itsef-admin@brightsight.com>
	<200901230820.46839.steuwer@univention.de>
	<200901291735.44364.itsef-admin@brightsight.com>
Message-ID: <200901300859.50402.bernhard@intevation.de>

On Donnerstag, 29. Januar 2009, ITSEF Admin wrote:
> I'm still surprised that I cannot see the console output Ludwig describes -
> as far as I can see, I'm using the same "--with-debug" (or suchlike)
> options for our Kubuntu packages as used in the Kolab Debian packages.

Checkout the KDE settings with "kdebugdialog".


-- 
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: 206 bytes
Desc: This is a digitally signed message part.
Url : http://kolab.org/pipermail/kolab-users/attachments/20090130/e8d64de5/attachment.bin

From Roessler at FuH-E.de  Fri Jan 30 16:45:53 2009
From: Roessler at FuH-E.de (=?ISO-8859-15?Q?Christian_R=F6=DFler?=)
Date: Fri, 30 Jan 2009 16:45:53 +0100
Subject: Again: MySQL
In-Reply-To: <20090129171834.12764m8rdemdgfeo@webmail.pardus.de>
References: <497ED1F0.2070907@FuH-E.de>	<200901281135.12560.bernhard@intevation.de>
	<20090129171834.12764m8rdemdgfeo@webmail.pardus.de>
Message-ID: <498320B1.7000407@FuH-E.de>

Gunnar Wrobel schrieb:

>> On Dienstag, 27. Januar 2009, Christian R??ler wrote:
>>> | the PHP package within Kolab is not compiled with the mysql
>>> | extension. So you would need to add the necessary flag "--with=mysql"
>>> | to you obmtool.conf file before installing Kolab.
>>> ...but this obmtool.conf is nowhere to be found. [...]
>> obmtool has been replaced by install-kolab.sh, open this in an editor.
> 
> -D apache_php::with_mysql=yes
> in install-kolab.sh (line 25). I'm not 100% certain that this will work 
> but please report back.

First let me thank you for the hint:), but unfortunately this seems not
to be enough. I have, as always, installed a Kolab in a fresh VM -
compilation goes through as usual, but inserting a php page with
phpinfo() results in:
| Configure Command 	 './configure' '--prefix=/kolab'
| '--sysconfdir=/kolab/etc/apache'
| '--with-config-file-path=/kolab/etc/apache' '--libdir=/kolab/lib/php'
| '--disable-all' '--enable-pdo' '--without-sqlite'
| '--without-pdo-sqlite' '--without-mysql' [...]

...perhaps without 'disable all'? I will try that monday morning, if you
think that's a possibilty.

> If it works we should add it to the wiki, if not we should help you to
> get it to compile ;)

Thanks again, Gunnar:)!

A nice weekend to everybody, and with best regards,
Christian


From funke at hiskp.uni-bonn.de  Fri Jan 30 17:21:57 2009
From: funke at hiskp.uni-bonn.de (Christian Funke)
Date: Fri, 30 Jan 2009 17:21:57 +0100
Subject: Postfix Domain forwarding question
Message-ID: <200901301721.57705.funke@hiskp.uni-bonn.de>

Hello,

I have set up a kolab server to serve mail for DOMAIN.COM, unfortunately I 
also have to provide support for a legacy domain OLDDOMAIN.COM, for which the 
users are identical and the mail for user at OLDDOMAIN.COM is to be delivered to 
user at DOMAIN.COM.  I habe realized this by modiying in 

/kolab/etc/postfix/main.cf

mydestination = DOMAIN.COM OLDDOMAIN.COM

and in 

/kolab/etc/postfix/virtual

@OLDDOMAIN.COM		@DOMAIN.COM

This setup works so far but has the drawback that any mail for @OLDDOMAIN.COM 
will be accepted whether the user exists or not and then it will be internally 
bounced. Is there a more elegant/efficient solution to solve this problem?

Many thanks in Advance,

Christian



From thomas at intevation.de  Fri Jan 30 17:28:32 2009
From: thomas at intevation.de (Thomas Arendsen Hein)
Date: Fri, 30 Jan 2009 17:28:32 +0100
Subject: Postfix Domain forwarding question
In-Reply-To: <200901301721.57705.funke@hiskp.uni-bonn.de>
References: <200901301721.57705.funke@hiskp.uni-bonn.de>
Message-ID: <20090130162832.GE23543.thomas@intevation.de>

* Christian Funke <funke at hiskp.uni-bonn.de> [20090130 17:22]:
> I have set up a kolab server to serve mail for DOMAIN.COM, unfortunately I 
> also have to provide support for a legacy domain OLDDOMAIN.COM, for which the 
> users are identical and the mail for user at OLDDOMAIN.COM is to be delivered to 
> user at DOMAIN.COM.  I habe realized this by modiying in 
> 
> /kolab/etc/postfix/main.cf
> 
> mydestination = DOMAIN.COM OLDDOMAIN.COM

This line is not needed.

> /kolab/etc/postfix/virtual
> 
> @OLDDOMAIN.COM		@DOMAIN.COM
> 
> This setup works so far but has the drawback that any mail for @OLDDOMAIN.COM 
> will be accepted whether the user exists or not and then it will be internally 
> bounced. Is there a more elegant/efficient solution to solve this problem?

Unfortunately I do not know a solution for this, too.
You could add one line for every email address that has to be
forwarded, maybe this could be automated with an LDAP query and
search/replace.

If you find a solution, please tell us.

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 lbf at dragonrising.com  Fri Jan 30 17:34:47 2009
From: lbf at dragonrising.com (Alex)
Date: Fri, 30 Jan 2009 16:34:47 +0000
Subject: Hosted Kolab?
In-Reply-To: <mailman.4.1233313202.21102.kolab-users@kolab.org>
References: <mailman.4.1233313202.21102.kolab-users@kolab.org>
Message-ID: <49832C27.1000802@dragonrising.com>

I'm looking at ways of outsourcing some of my companies various hosting 
tasks we would normally fire up a xen virtual server for, and was 
wondering if anyone offers kolab hosting?

For example, I'm looking at "openx hosted" to serve our advertisements 
and "gradwell" in the UK to host our VOIP PBX.

The advantages to me would be:

+ Software upgrades, including security upgrades
+ Managed backups
+ Don't have to worry about hardware faults

Does anyone know if a solution exists, or if it doesn't exist for a reason?

Thanks,

Alex



From pdf at yugm.org  Sat Jan 31 01:24:34 2009
From: pdf at yugm.org (Paul Douglas Franklin)
Date: Fri, 30 Jan 2009 16:24:34 -0800
Subject: Outlook authentication settings
Message-ID: <49839A42.4090900@yugm.org>

Hello,
I have a user who needs to send e-mail from outside our privileged 
networks on his laptop.  Can someone clue me in on the settings needed 
in Outlook?
--Paul

-- 
Paul Douglas Franklin
Computer Manager, Union Gospel Mission of Yakima, Washington
Husband of Danette
Father of Laurene, Miriam, Tycko, Timothy, Sarabeth, Marie, Dawnita, Anna Leah, Alexander, and Caleb


From aspineux at gmail.com  Sat Jan 31 10:49:01 2009
From: aspineux at gmail.com (Alain Spineux)
Date: Sat, 31 Jan 2009 10:49:01 +0100
Subject: Postfix Domain forwarding question
In-Reply-To: <20090130162832.GE23543.thomas@intevation.de>
References: <200901301721.57705.funke@hiskp.uni-bonn.de>
	<20090130162832.GE23543.thomas@intevation.de>
Message-ID: <71fe4e760901310149j32f0318drfd7c9f15f574a946@mail.gmail.com>

On Fri, Jan 30, 2009 at 5:28 PM, Thomas Arendsen Hein
<thomas at intevation.de> wrote:
> * Christian Funke <funke at hiskp.uni-bonn.de> [20090130 17:22]:
>> I have set up a kolab server to serve mail for DOMAIN.COM, unfortunately I
>> also have to provide support for a legacy domain OLDDOMAIN.COM, for which the
>> users are identical and the mail for user at OLDDOMAIN.COM is to be delivered to
>> user at DOMAIN.COM.  I habe realized this by modiying in
>>
>> /kolab/etc/postfix/main.cf
>>
>> mydestination = DOMAIN.COM OLDDOMAIN.COM
>
> This line is not needed.

It think this line is wrong, you dont have any mailboxes for
someone at OLDDOMAIN.COM, only for someone at DOMAIN.COM

Then the correct one is below !

mydestination = DOMAIN.COM


>
>> /kolab/etc/postfix/virtual
>>
>> @OLDDOMAIN.COM                @DOMAIN.COM

then to accept email for OLDDOMAIN.COM, you must add

OLDDOMAIN.COM      anything

in your virtual file, and keep the line above (with the @)

This is the way you create aliases inside postfix !


Don't forget to modify the template and run kolabconf


>>
>> This setup works so far but has the drawback that any mail for @OLDDOMAIN.COM
>> will be accepted whether the user exists or not and then it will be internally
>> bounced. Is there a more elegant/efficient solution to solve this problem?

I wrote some notes in the wiki about "domain alias" (or aliases)

>
> Unfortunately I do not know a solution for this, too.
> You could add one line for every email address that has to be
> forwarded, maybe this could be automated with an LDAP query and
> search/replace.

Maybe integrate this (domain alias management) into the kolab daemon kolabd;
it will search for all mail and alias no having  the counterpart in
the domain aliases and create them.

(|(&(mail=*@DOMAIN.COM)(!mail=*@DOMAIN.COM))
(&(alias=*@DOMAIN.COM)(!alias=*@DOMAIN.COM))
)

Then iterate over the result and create the missing entries, then
repeat this for every domain aliases !
And do this for every modification into the ldap ! This will increase
the load a little bit but how to do this in
an other  way.

Regards.

>
> If you find a solution, please tell us.
>
> 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 mike at rochestervball.com  Sat Jan 31 17:08:34 2009
From: mike at rochestervball.com (Michael Harnden)
Date: Sat, 31 Jan 2009 11:08:34 -0500
Subject: Accessing Horde outside home network
In-Reply-To: <20090129171427.11563kn83hfakt2c@webmail.pardus.de>
References: <200901261524.53454.mike@rochestervball.com>
	<20090129171427.11563kn83hfakt2c@webmail.pardus.de>
Message-ID: <200901311108.35263.mike@rochestervball.com>

On Thursday 29 January 2009 11:14:27 am Gunnar Wrobel wrote:
> Quoting Michael Harnden <mike at rochestervball.com>:
> > I recently migrated from an openSUSE 10.1 installation running
> > natively to a OpenPKG installation (v
> > 2.2) on Debian Etch. I use Kolab/Horde as a home email server. Works
> > great for my wife and I who
> > both travel a lot. The migration went smoothly using my backups. My
> > problem lies in accessing Horde
> > from outside of my home network.
> >
> > With my openSUSE installation I could use dyndns.org to access my
> > installation. With the Debian
> > server, once I log in, I am redirected to using my home servers fqdn
> > (home-server.site). Can I
> > correct this on my new installation without creating a huge security
> > hole?
>
> You should be able to correct this without any security problems. I
> assume that your server does not know that it is accessible via the
> dyndns.org fqdn. You can set the server name for horde in
> /kolab/var/kolab/www/horde/config/conf.php.
>
> The relevant line is:
>
> $conf['server']['name'] = $_SERVER['SERVER_NAME'];
>
> You should be able to hard-code the server fqdn here. In general it is
> better though if the whole DNS setup is correct and your server is
> able to correctly identify itself. You might also edit /etc/hosts for
> that.
>
> Cheers,
>
> Gunnar
>
> > Or am I better off
> > setting up a VPN server (assuming that would work).
> >
> > Thanks,
> > Mike
> >
> > _______________________________________________
> > Kolab-users mailing list
> > Kolab-users at kolab.org
> > https://kolab.org/mailman/listinfo/kolab-users
Thank you Gunnar, I will take a look at this over the weekend. I received another reply off-list 
which I will post below, that got me up and running for the week. My reply to him bounced, so I'll 
give a public thanks to Jon!
Mike

1. Enable wildcards in your dyndns.org config (so *.mysite.dyndns.org will all 
resolve correctly)

2. Remove or hardcode the redirects in your apache config 
(/kolab/etc/kolab/templates/httpd.conf.template) to either get rid of redirects entirely (which I've 
chosen) or to control exactly where it redirects to (granted, the latter is kludgey)

For my own use, I am fine with typing in https://myserver.mydomain.dyndns.org/horde (or making a 
bookmark to there)...it's only about 7 more characters than I'd have to type otherwise anyway.

The redirects are the "ErrorDocument" lines within the Location blocks in the apache config. ?If 
you're new to the apache config file, I'd also highly recommend reading through the apache 
documentation on the web. ?It's very thorough, and after reading it I found quite a few other tweaks 
to make to my config, besides removing the redirection.



From ricardo.sousa at servismart.net  Fri Jan 30 20:37:12 2009
From: ricardo.sousa at servismart.net (Ricardo Botelho de Sousa)
Date: Fri, 30 Jan 2009 19:37:12 +0000
Subject: Hosted Kolab?
References: mailman.4.1233313202.21102.kolab-users@kolab.org
Message-ID: <498356E8.3060200@servismart.net>

Hello Alex,

  I noticed your message on Kolab Users' mailing list.
  My company (an IT consulting business) is about to launch a managed 
services spinoff that I feel would cover all of your concerns with the 
added benefit of being able to provide a dedicated solution.

  Even tho we don't have an hosted specifically for Kolab what we offer 
is managed solutions from the server (virtual) to the application (we 
can also do custom development if needed). Would you like us to design 
and propose a platform to the requirements you mentioned?

  Another (potential) issue I'd like to clear is, we don't have 
operations on the UK right now. Nevertheless our network is powered by 
Clara.net which allows our average latency to the UK to be under 30 
miliseconds with a 3.4 standard deviation.

  If this setup doesn't create a problem with you we'd love to work on 
your requirements in order to assure you maximum satisfaction.

Best regards,
ricardo

-- 
ServiSMART                                      Ricardo Sousa
servimos o seu neg?cio                          tel: +351 96 298 0989