From albrecht.dress at lios-tech.com  Sat Nov  1 16:36:13 2008
From: albrecht.dress at lios-tech.com (Albrecht =?iso-8859-1?b?RHJl3w==?=)
Date: Sat, 01 Nov 2008 16:36:13 +0100
Subject: Free/busy lists broken - HELP!
In-Reply-To: <20081031081605.15302gijucixvzxx@kolab.lios-koeln.de>
References: <1225358234l.3914l.0l@pc-adr2.lios-koeln.de>
	<20081031064501.281239d9a4wgz9kw@webmail.pardus.de>
	<20081031081605.15302gijucixvzxx@kolab.lios-koeln.de>
Message-ID: <20081101163613.36336urhc3651my5@portal.lios-koeln.de>

Quoting Albrecht Dre? <albrecht.dress at lios-tech.com>:
> /kolab/var/kolab-freebusy/cache/ and all files and sub-folders are
> world-readable, i.e. the usual owner is kolab-n:kolab-n, files have
> (at least) 0644 permissions, and folders 0755.  Or are you referring
> to /imap/ folder permissions?

As to get more information about this bug and following a hint by  
Saim, I made a few tests.  Before starting each test, I completely  
erased the contents of the /kolab/var/kolab-freebusy/cache folder and  
then triggered the re-generation of the fb lists for  
"first.user at my-domain.com" and "second.user at my-domain.com" by calling  
the /freebusy/trigger/<user-name>/Kalender.pfb uri's as calendar user.  
  Here are my observations:


(1) Enable unauthorised download of fb lists in the admin ui (my  
standard setting).
The file aclcache.db does not contain data, the file xaclcache.db  
contains two lines in the form

  calendar at my-domain.com
  my-domain^com/first^user/Kalender,my-domain^com/second^user/Kalender

The Kalender.pvc files seem to contain the proper appointment data.

However, when I download the fb list via the /freebusy/<user-name>.ifb  
uri, I get the dummy freebusy lists.  The same applies for the *.vc  
files.  The log file tells me: "Free/busy data of owner  
first.user at my-domain.com on server srv-portal.my-server.de requested  
by user ."


(2) Disable unauthorised download of fb lists in the admin ui.
The contents of the x?aclcache.db files is the same as above.  And,  
again, the Kalender.pvc files seem to contain the proper data.

When I now try to access the *.ifb uri's, Firefox asks me to  
authenticate.  Entering first.user at my-domain.com and the proper  
password, I still get empty (dummy) fb lists, bor *both*  
first.user at my-domain.com and for second.user at my-domain.com.  However,  
the *.vc files now reside in the  
my-domain^com/first^user/my-domain^com/ sub-folder of the cache  
folder, and are all "dummy" ones.

BTW, the log file now says "Free/busy data of owner  
first.user at my-domain.com on server srv-portal.my-server.de requested  
by user first.user at my-domain.com."


(3) Switch back to unauthorised download.  The log file still says  
that I try to download as authenticated user, and the vc files are  
created below each "user folder", but they are still "dummy" ones.


I added some more debug calls to  
/kolab/lib/php/Kolab/Freebusy/Cache.php (which seems to be used by  
/kolab/var/kolab/www/freebusy/freebusy.php), and apparently it  
consults the file /kolab/var/kolab-freebusy/cache/aclcache.db.  As  
this one seems to be always empty, this might be an explanation for  
the empty fb lists.

This leads me to the question if I completely misunderstood the  
concept of fb lists (which IMHO should *always* return the fb  
information for every user, regardless of the IMAP acl setting for the  
Calender folder which should only apply to the /contents/ of  
appointments, right?), of if the creation of the lists and/or the  
related ACL's is broken.

Still, the big question is how to fix this bug...

Thanks, Albrecht.


From wrobel at pardus.de  Mon Nov  3 05:32:23 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Mon, 03 Nov 2008 05:32:23 +0100
Subject: external web client
In-Reply-To: <d53357b70810310356j10fe628dt11c2059af6532b96@mail.gmail.com>
References: <d53357b70810300437r5fefb324vc1bb79c8ee17cd6a@mail.gmail.com>
	<d53357b70810300448o46b0f44euc1cf8f70190c7608@mail.gmail.com>
	<28713.200.47.24.7.1225369602.squirrel@webmail.xtech.com.ar>
	<d53357b70810300534q77110ecfjc713d64cca750d95@mail.gmail.com>
	<50233.200.47.24.7.1225371471.squirrel@webmail.xtech.com.ar>
	<d53357b70810300831u52f532e7naea1a90c616bd39d@mail.gmail.com>
	<20081031065053.41847cr9xzxhie0w@webmail.pardus.de>
	<d53357b70810310324od1929c8p7374d6b2774896c2@mail.gmail.com>
	<d53357b70810310356j10fe628dt11c2059af6532b96@mail.gmail.com>
Message-ID: <20081103053223.166558e9ckjxuh44@webmail.pardus.de>


Quoting Antonio Straziota <devgioiatech at gmail.com>:

> As suggested in the wiki, I also try to remove nss_db library (my
> system is CENTOS) but nothing changes

What do you see in the log files within /kolab/var/apache/log/* when  
you try to log in?

Cheers,

Gunnar

>
> 2008/10/31 Antonio Straziota
dir="ltr"><devgioiatech at gmail.com[1]>
>  0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">mmmh...
> i've a problem autentication by local webmail goes fine... but when
> i try to login in horde by external webmail...i can't log in
without
> any error message...
> any idea...
>
> any idea?
>
>
>  10/31 Gunnar Wrobel  dir="ltr"><
href="mailto:wrobel at pardus.de">wrobel at pardus.de>
>  0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">   Quoting  
> Antonio Straziota <
href="mailto:devgioiatech at gmail.com">devgioiatech at gmail.com>:
>   0pt 0.8ex; padding-left: 1ex;" class="gmail_quote"> Ok,
> i've installed webmail through a fresh kolab slave installation.

  This is currently the best option. I need to fix the wiki page :)
We decided that it will be safer for users to install a complete
slave rather than installing Horde on an apache/mod_php combo without
know configuration.

only a question... can i stop all other kolab service and keep
online only Apache?

  I think that should be possible.

Cheers,

Gunnar

2008/10/30 Alejandro Bednarik
    dir="ltr"><alejandro at xtech.com.ar[1]>
   0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
  I tried this also, it works if you also copy another directory
where live
many php modules, i can't remember the exact path sorry. Kolab php
have
patches, maybe is a good idea to compile and use this as source.
The
performance using this method was not what we expect, but probably
was
the network where we set this servers...
  Cheers!
   Antonio Straziota wrote:
> Hi Alejandro,
> thanks for the reply...
>
> i'll try this solution.
>
> However, i think that installing all dependence and copying
the
> /kolab/var/kolab/www/horde in the web root of the web server
should be
> work...
> After all horde is simply a web application that needs to be
configured
>
> Anyone can help for this?
>
> Thanks.
>
> 2008/10/30 Alejandro Bednarik
  <alejandro at xtech.com.ar[2]>
>
>>
>>  Hi Antonio. I tried the same thing a couple of weeks ago,
and if i am
>> not
>> wrong that way to set another Horde is deprecated. You can
try doing a
>> normal kolab installation, but choosing Slave during the
bootstrap
>> process.
>>  For sure, someone who knows this better than me can help
you with more
>> info.
>>
>> Cheers!
>>
>>
>> Antonio Straziota wrote:
>> > ehm,
>> > hi again...
>> >
>> > i tryed to launch the script but instead of the
folder *horde*, the
>> > content
>> > of the web root is :
>> >
>> >
>> > [root at srv html]# ll
>> > -rw-r--r--  1 root root    6021 Oct 30 12:39
external-horde.sh
>> > -rw-r--r--  1 root root    6282 Oct 30 12:41
>> >
>>


HK-GW-framework_3.2_ALPHA-Fix_Prefs_for_Ingo.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    6883 Oct 30 12:41
>> >
>>


HK-GW-kronolith_2.2_RC1-Fbview_relevance.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    6901 Oct 30 12:41
>> >
>>


HK-GW-kronolith_2.2_RC1-Fbview_xfb_access.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    6193 Oct 30 12:41
>> >
>>


HK-GW-turba_2.2-Fix_editing_contacts.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    6177 Oct 30 12:41
>> >
>>


HK-GW-turba_2.2-Fix_share_id_change.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    6161 Oct 30 12:41
>> >
>>


HK-GW-turba_2.2-Ldap_read_only_fix.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    6967 Oct 30 12:41
>> >
>>


HK-JS-kronolith_2.2_RC1-Fix_library_import.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    6859 Oct 30 12:41
>> >
>>


HK-JS-nag_2.2_RC1-Fix_library_import.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    7038 Oct 30 12:41
>> >
>>


HK-SB-kronolith_2.2_RC1-Fbview_extra_params.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    7074 Oct 30 12:41
>> >
>>


HK-SB-kronolith_2.2_RC1-Fbview_save_attendees.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
       >> >
>> >
>> > Any idea?
>> >
>> > 2008/10/30 Antonio Straziota
   <devgioiatech at gmail.com[3]>
>> >
>> >> hi all,
>> >> i'm trying to install horde on a external web
server.
>> >>
>> >> i'm following the tutorial at
>> >>

href="http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde">http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde.

  >> >>
>> >> now i'm getting the script external-horde.sh with
>> >>
>> >> wget
>> >>
>>

href="http://kolab.org/cgi-bin/viewcvs-kolab.cgi/*checkout*/server/horde/Attic/external-horde.sh?rev=HEAD&search=None&hideattic=1&content-type=text/x-sh">http://kolab.org/cgi-bin/viewcvs-kolab.cgi/*checkout*/server/horde/Attic/external-horde.sh?rev=HEAD&search=None&hideattic=1&content-type=text/x-sh
   >> >>
>> >> because link in the tutorial doesn't work with
wget
>> >>
>> >> Is this script right for the kolab2.2.0?
>> >>
>> >> Thanks
>> >>
>> >>
>> > _______________________________________________
>> > Kolab-users mailing list
  >> > Kolab-users at kolab.org[4]
>> >

href="https://kolab.org/mailman/listinfo/kolab-users">https://kolab.org/mailman/listinfo/kolab-users
   >> >
>>
>>
>> --
>>  Alejandro Bednarik
>>  XTech - Soluciones Linux para Empresas
>>  (011) 5219-0678
  >>  alejandro at xtech.com.ar[5]
>>
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org[6]
>>

href="https://kolab.org/mailman/listinfo/kolab-users">https://kolab.org/mailman/listinfo/kolab-users
   >>
>
    --
   Alejandro Bednarik
  XTech - Soluciones Linux para Empresas
  (011) 5219-0678
  alejandro at xtech.com.ar[7]

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

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

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

Links:
------
[1] mailto:alejandro at xtech.com.ar
[2] mailto:alejandro at xtech.com.ar
[3] mailto:devgioiatech at gmail.com
[4] mailto:Kolab-users at kolab.org
[5] mailto:alejandro at xtech.com.ar
[6] mailto:Kolab-users at kolab.org
[7] mailto:alejandro at xtech.com.ar

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

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

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

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

Links:
------
[1] mailto:devgioiatech at gmail.com


----------------------------------------------------------------
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/20081103/7bca3a9c/attachment.bin

From wrobel at pardus.de  Mon Nov  3 05:54:38 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Mon, 03 Nov 2008 05:54:38 +0100
Subject: Free/busy lists broken - HELP!
In-Reply-To: <20081101163613.36336urhc3651my5@portal.lios-koeln.de>
References: <1225358234l.3914l.0l@pc-adr2.lios-koeln.de>
	<20081031064501.281239d9a4wgz9kw@webmail.pardus.de>
	<20081031081605.15302gijucixvzxx@kolab.lios-koeln.de>
	<20081101163613.36336urhc3651my5@portal.lios-koeln.de>
Message-ID: <20081103055438.12682xjv8nzedr1w@webmail.pardus.de>

Quoting Albrecht Dre? <albrecht.dress at lios-tech.com>:

> Quoting Albrecht Dre? <albrecht.dress at lios-tech.com>:
>> /kolab/var/kolab-freebusy/cache/ and all files and sub-folders are
>> world-readable, i.e. the usual owner is kolab-n:kolab-n, files have
>> (at least) 0644 permissions, and folders 0755.  Or are you referring
>> to /imap/ folder permissions?
>
> As to get more information about this bug and following a hint by
> Saim, I made a few tests.  Before starting each test, I completely
> erased the contents of the /kolab/var/kolab-freebusy/cache folder and
> then triggered the re-generation of the fb lists for
> "first.user at my-domain.com" and "second.user at my-domain.com" by calling
> the /freebusy/trigger/<user-name>/Kalender.pfb uri's as calendar user.
>   Here are my observations:
>
>
> (1) Enable unauthorised download of fb lists in the admin ui (my
> standard setting).
> The file aclcache.db does not contain data, the file xaclcache.db
> contains two lines in the form
>
>   calendar at my-domain.com
>   my-domain^com/first^user/Kalender,my-domain^com/second^user/Kalender
>
> The Kalender.pvc files seem to contain the proper appointment data.
>
> However, when I download the fb list via the /freebusy/<user-name>.ifb
> uri, I get the dummy freebusy lists.  The same applies for the *.vc
> files.  The log file tells me: "Free/busy data of owner
> first.user at my-domain.com on server srv-portal.my-server.de requested
> by user ."
>
>
> (2) Disable unauthorised download of fb lists in the admin ui.
> The contents of the x?aclcache.db files is the same as above.  And,
> again, the Kalender.pvc files seem to contain the proper data.
>
> When I now try to access the *.ifb uri's, Firefox asks me to
> authenticate.  Entering first.user at my-domain.com and the proper
> password, I still get empty (dummy) fb lists, bor *both*
> first.user at my-domain.com and for second.user at my-domain.com.  However,
> the *.vc files now reside in the
> my-domain^com/first^user/my-domain^com/ sub-folder of the cache
> folder, and are all "dummy" ones.
>
> BTW, the log file now says "Free/busy data of owner
> first.user at my-domain.com on server srv-portal.my-server.de requested
> by user first.user at my-domain.com."
>
>
> (3) Switch back to unauthorised download.  The log file still says
> that I try to download as authenticated user, and the vc files are
> created below each "user folder", but they are still "dummy" ones.
>
>
> I added some more debug calls to
> /kolab/lib/php/Kolab/Freebusy/Cache.php (which seems to be used by
> /kolab/var/kolab/www/freebusy/freebusy.php), and apparently it
> consults the file /kolab/var/kolab-freebusy/cache/aclcache.db.  As
> this one seems to be always empty, this might be an explanation for
> the empty fb lists.
>
> This leads me to the question if I completely misunderstood the
> concept of fb lists (which IMHO should *always* return the fb
> information for every user, regardless of the IMAP acl setting for the
> Calender folder which should only apply to the /contents/ of
> appointments, right?), of if the creation of the lists and/or the
> related ACL's is broken.
>
> Still, the big question is how to fix this bug...

Can you check if the patch in  
https://www.intevation.de/roundup/kolab/issue3074 helps?

Cheers,

Gunnar

>
> Thanks, Albrecht.
>
> _______________________________________________
> 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/20081103/377859c2/attachment.bin

From daniel.vergien at rrz.uni-hamburg.de  Mon Nov  3 09:40:28 2008
From: daniel.vergien at rrz.uni-hamburg.de (Daniel Vergien)
Date: Mon, 03 Nov 2008 09:40:28 +0100
Subject: Kolab 2.2.0 on Solaris 10 x86
Message-ID: <490EB8FC.1000400@rrz.uni-hamburg.de>

Hi,
I try to setup Kolab 2.2.0 on Solaris 10. I followed the guide for 2.1
from the wiki http://wiki.kolab.org/index.php/Solaris .

It fails when it want to install make. The full log is not attached 
since it is too big.

Thanks

Daniel


+-----------------------------------------------------------------------------+
| INSTALL: Done. Thank you for flying OpenPKG...
          |
+-----------------------------------------------------------------------------+
+ exit 0
Processing files: openpkg-20071227-20071227
Wrote: /kolab/RPM/PKG/openpkg-20071227-20071227.amd64-solaris10-kolab.rpm
Executing(%clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
--posix -e /kolab/RPM/TMP/rpm-tmp.8158
+ cd /kolab/RPM/TMP
+ '[' . = .1 ']'
+ rm -rf openpkg-20071227
+ rm -rf /kolab/RPM/TMP/openpkg-20071227-root
+ exit 0
Executing(--clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
--posix -e /kolab/RPM/TMP/rpm-tmp.8158
+ cd /kolab/RPM/TMP
+ exit 0
Preparing...
##################################################
openpkg
##################################################
:::: /tmp/install-kolab....8437/openpkg-20071227-20071227.src.rpm = 0 ::::
:::: /tmp/install-kolab....8437/make-3.81-20080101.src.rpm ::::
error: cannot open
/tmp/install-kolab....8437/make-3.81-20080101.src.rpm: No such file or
directory

-bash-3.00# ls /tmp/install-kolab....8437/
00INDEX.rdf
openpkg-20071227-20071227.amd64-solaris10-kolab.rpm
openpkg-20071227-20071227.amd64-solaris10-kolab.sh
openpkg-20071227-20071227.src.rpm
openpkg-20071227-20071227.src.sh
shtool


From albrecht.dress at lios-tech.com  Mon Nov  3 09:54:15 2008
From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=)
Date: Mon, 03 Nov 2008 09:54:15 +0100
Subject: Free/busy lists broken - HELP!
In-Reply-To: <20081103055438.12682xjv8nzedr1w@webmail.pardus.de> (from
	wrobel@pardus.de on Mon Nov  3 05:54:38 2008)
References: <1225358234l.3914l.0l@pc-adr2.lios-koeln.de>
	<20081031064501.281239d9a4wgz9kw@webmail.pardus.de>
	<20081031081605.15302gijucixvzxx@kolab.lios-koeln.de>
	<20081101163613.36336urhc3651my5@portal.lios-koeln.de>
	<20081103055438.12682xjv8nzedr1w@webmail.pardus.de>
Message-ID: <1225702455l.23362l.0l@pc-adr2.lios-koeln.de>

Hi Gunnar!

Am 03.11.2008 05:54:38 schrieb(en) Gunnar Wrobel:
> Can you check if the patch in   
> https://www.intevation.de/roundup/kolab/issue3074 helps?

I had that one already applied, as otherwise the calendar user got HTTP  
404 errors (see  
<http://www.kolab.org/pipermail/kolab-users/2008-October/008827.html>).

Isn't it possible to somehow configure in the acl's that *everyone* may  
load .ifb's or .xfb's (from Horde)?  This may not be a clean solution,  
but would at least solve my urgent needs!

Thanks, Albrecht.


From aspineux at gmail.com  Mon Nov  3 10:29:49 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 3 Nov 2008 10:29:49 +0100
Subject: Kolab 2.2.0 on Solaris 10 x86
In-Reply-To: <490EB8FC.1000400@rrz.uni-hamburg.de>
References: <490EB8FC.1000400@rrz.uni-hamburg.de>
Message-ID: <71fe4e760811030129kdb26256qdbc4ee62283194a4@mail.gmail.com>

On Mon, Nov 3, 2008 at 9:40 AM, Daniel Vergien
<daniel.vergien at rrz.uni-hamburg.de> wrote:
> Hi,
> I try to setup Kolab 2.2.0 on Solaris 10. I followed the guide for 2.1
> from the wiki http://wiki.kolab.org/index.php/Solaris .
>
> It fails when it want to install make. The full log is not attached
> since it is too big.
>
> Thanks
>
> Daniel
>
>
> +-----------------------------------------------------------------------------+
> | INSTALL: Done. Thank you for flying OpenPKG...
>          |
> +-----------------------------------------------------------------------------+
> + exit 0
> Processing files: openpkg-20071227-20071227
> Wrote: /kolab/RPM/PKG/openpkg-20071227-20071227.amd64-solaris10-kolab.rpm
> Executing(%clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
> --posix -e /kolab/RPM/TMP/rpm-tmp.8158
> + cd /kolab/RPM/TMP
> + '[' . = .1 ']'
> + rm -rf openpkg-20071227
> + rm -rf /kolab/RPM/TMP/openpkg-20071227-root
> + exit 0
> Executing(--clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
> --posix -e /kolab/RPM/TMP/rpm-tmp.8158
> + cd /kolab/RPM/TMP
> + exit 0
> Preparing...
> ##################################################
> openpkg
> ##################################################
> :::: /tmp/install-kolab....8437/openpkg-20071227-20071227.src.rpm = 0 ::::
> :::: /tmp/install-kolab....8437/make-3.81-20080101.src.rpm ::::
> error: cannot open
> /tmp/install-kolab....8437/make-3.81-20080101.src.rpm: No such file or
> directory

Do you know if this file is present and valid ?
Did you check the checksum before to start compiling ?


>
> -bash-3.00# ls /tmp/install-kolab....8437/
> 00INDEX.rdf
> openpkg-20071227-20071227.amd64-solaris10-kolab.rpm
> openpkg-20071227-20071227.amd64-solaris10-kolab.sh
> openpkg-20071227-20071227.src.rpm
> openpkg-20071227-20071227.src.sh
> shtool
>
> _______________________________________________
> 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 daniel.vergien at rrz.uni-hamburg.de  Mon Nov  3 11:03:15 2008
From: daniel.vergien at rrz.uni-hamburg.de (Daniel Vergien)
Date: Mon, 03 Nov 2008 11:03:15 +0100
Subject: Kolab 2.2.0 on Solaris 10 x86
In-Reply-To: <71fe4e760811030129kdb26256qdbc4ee62283194a4@mail.gmail.com>
References: <490EB8FC.1000400@rrz.uni-hamburg.de>
	<71fe4e760811030129kdb26256qdbc4ee62283194a4@mail.gmail.com>
Message-ID: <490ECC63.4040207@rrz.uni-hamburg.de>

Solved it myself. The checksums where ok. The problem seems that 
solaris find is not like the one kolab expects... From the begining of 
the logfile:

Changing to temporary working directory /tmp/install-kolab....8437 ...
find: Falsche Option -mindepth
find: [-H | -L] Pfadliste Pr?dikatliste

Kolab installation tag (TAG):       kolab
Kolab installation prefix (PREFIX): /kolab

I've installed another find and now it seems to compile.

Daniel

On 11/ 3/08 10:29 AM, Alain Spineux wrote:
> On Mon, Nov 3, 2008 at 9:40 AM, Daniel Vergien
> <daniel.vergien at rrz.uni-hamburg.de> wrote:
>> Hi,
>> I try to setup Kolab 2.2.0 on Solaris 10. I followed the guide for 2.1
>> from the wiki http://wiki.kolab.org/index.php/Solaris .
>>
>> It fails when it want to install make. The full log is not attached
>> since it is too big.
>>
>> Thanks
>>
>> Daniel
>>
>>
>> +-----------------------------------------------------------------------------+
>> | INSTALL: Done. Thank you for flying OpenPKG...
>>          |
>> +-----------------------------------------------------------------------------+
>> + exit 0
>> Processing files: openpkg-20071227-20071227
>> Wrote: /kolab/RPM/PKG/openpkg-20071227-20071227.amd64-solaris10-kolab.rpm
>> Executing(%clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
>> --posix -e /kolab/RPM/TMP/rpm-tmp.8158
>> + cd /kolab/RPM/TMP
>> + '[' . = .1 ']'
>> + rm -rf openpkg-20071227
>> + rm -rf /kolab/RPM/TMP/openpkg-20071227-root
>> + exit 0
>> Executing(--clean): env -i /kolab/lib/openpkg/bash --norc --noprofile
>> --posix -e /kolab/RPM/TMP/rpm-tmp.8158
>> + cd /kolab/RPM/TMP
>> + exit 0
>> Preparing...
>> ##################################################
>> openpkg
>> ##################################################
>> :::: /tmp/install-kolab....8437/openpkg-20071227-20071227.src.rpm = 0 ::::
>> :::: /tmp/install-kolab....8437/make-3.81-20080101.src.rpm ::::
>> error: cannot open
>> /tmp/install-kolab....8437/make-3.81-20080101.src.rpm: No such file or
>> directory
> 
> Do you know if this file is present and valid ?
> Did you check the checksum before to start compiling ?
> 
> 
>> -bash-3.00# ls /tmp/install-kolab....8437/
>> 00INDEX.rdf
>> openpkg-20071227-20071227.amd64-solaris10-kolab.rpm
>> openpkg-20071227-20071227.amd64-solaris10-kolab.sh
>> openpkg-20071227-20071227.src.rpm
>> openpkg-20071227-20071227.src.sh
>> shtool
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>
> 
> 
> 


From pav5088 at internode.on.net  Mon Nov  3 11:42:48 2008
From: pav5088 at internode.on.net (Mark Pavlichuk)
Date: Mon, 03 Nov 2008 20:42:48 +1000
Subject: Kolab + GOsa debugging
In-Reply-To: <71fe4e760810310828h2a03a9a4hdafd808380d1166f@mail.gmail.com>
References: <7B91BBC61758DD1183BE000C296D2CA71049A6@ct-exchange.wins.lawco.com>	
	<490564DA.6080300@internode.on.net>	
	<200810271732.30746.pollmeier@gonicus.de>	
	<49070BDC.2060209@internode.on.net>	
	<34550.200.47.24.7.1225199561.squirrel@webmail.xtech.com.ar>	
	<49087AB7.9050405@internode.on.net>
	<71fe4e760810310828h2a03a9a4hdafd808380d1166f@mail.gmail.com>
Message-ID: <490ED5A8.3040308@internode.on.net>

Alain Spineux wrote:
> You mean the "Mailbox Home Server"  ?
>
> Do you have a valid k=kolab entry  ? With a valid kolabHost attribute ?
>
> What about this ?
>
> # ldapsearch -w your_manager_password -D
> "cn=manager,cn=internal,dc=your,dc=domain,dc=com"
> "(objectClass=emailgencyServerObject)"
>
> What about attribute kolabHost 

  I've been playing so much with my test installation that I don't want 
to persist with it, so I'll be re-installing (again).  Could you (or 
anyone else) give me some hints on successfully blending Kolab /w GOsa 
in LDAP?  I'm using the Kolab debs, and I haven't managed to track down 
any documentation.

  If access to a test machine is required I can give ssh and web access.

-- 
Mark Pavlichuk
Strategic IT
ph. (07)47242890
m. 0409 124577


From NPrice at gibb.co.za  Mon Nov  3 15:07:38 2008
From: NPrice at gibb.co.za (Price,Neil)
Date: Mon, 3 Nov 2008 16:07:38 +0200 
Subject: Outlook connectors feedback
Message-ID: <7B91BBC61758DD1183BE000C296D2CA7104A15@ct-exchange.wins.lawco.com>


I've been testing some Outlook connectors on Kolab.

Toltec

It works fine and is reasonably priced. The manual is a bit confusing. Its
got an awkward method of downloading the emails via pop3 and synchronizing
it back again. You end up with 2 inboxes in Horde because of that. It uses
pst files with their limitations. Its slow on start-up and synchronization
on a big mailbox (150MB)

Its got ntlm support so a single sign on is theoretically possible if you
used a samba-kolab ldap setup, but I could not find info on this yet.

Bynari

Its got a nice feature where it will copy the emails from your existing
Outlook profile. This worked fairly well copying emails out of an MS
Exchange profile but some of the sender emails addresses got trashed in the
import. It looks really professional but it kept locking up on me while
downloading the emails on a big mailbox. It would sync to about 5% and lock
up. I will test it on another machine in case it just did not like the one I
was testing on (this is windows, remember). It does not use pst files. Its
more expensive that the Toltec one. A lot more, like 50% extra.

Konsec.

This is quite similar in principle to the Tolltec one except it does not use
pst files. I had heard that Konsec used a mapi connector but it is the same
pop3 setup. Synchronization was noticeably quicker than the other two on a
large-ish mailbox (150 MB). It was quite stable on the same PC that the
Bynari crashed on. There is also ntlm support. The manual is only available
in German.

Its quite expensive if their price list is accurate, like about 3 times the
price of Toltec.


From hjkim at bynari.net  Mon Nov  3 15:57:00 2008
From: hjkim at bynari.net (Hyun Kim)
Date: Mon, 03 Nov 2008 08:57:00 -0600
Subject: Outlook connectors feedback
Message-ID: <904d1568.1c93dc4.4fc061.211f@bynari.net>

Neil,
Will you contact me about the lockups?  We have several customers using it with no problems.  Our partner, Univention, is selling it in Germany at the same price as Toltec's, so you can purchase it from them at the same low price.

Depending on how the Connector was configured, it could be waiting on the server or has download header only, not checked.  Also, with V4.0 of the Connector, next version, pst files are used as the local store.

Thanks,
Hyun 


Mrs. Hyun Kim
President
Bynari, Inc.
2639 Electronic Lane, Suite 110
Dallas, Tx  75220
www.bynari.net
(214) 350-5772 X59
(214) 789-8674 cell
(214) 352-3530 fax

"Success is on the far side of failure."  T. J. Watson 


-----Original Message-----
From: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org] On Behalf Of Price,Neil
Sent: Monday, November 03, 2008 8:08 AM
To: kolab-users at kolab.org
Subject: Outlook connectors feedback


I've been testing some Outlook connectors on Kolab.

Toltec

It works fine and is reasonably priced. The manual is a bit confusing. Its
got an awkward method of downloading the emails via pop3 and synchronizing
it back again. You end up with 2 inboxes in Horde because of that. It uses
pst files with their limitations. Its slow on start-up and synchronization
on a big mailbox (150MB)

Its got ntlm support so a single sign on is theoretically possible if you
used a samba-kolab ldap setup, but I could not find info on this yet.

Bynari

Its got a nice feature where it will copy the emails from your existing
Outlook profile. This worked fairly well copying emails out of an MS
Exchange profile but some of the sender emails addresses got trashed in the
import. It looks really professional but it kept locking up on me while
downloading the emails on a big mailbox. It would sync to about 5% and lock
up. I will test it on another machine in case it just did not like the one I
was testing on (this is windows, remember). It does not use pst files. Its
more expensive that the Toltec one. A lot more, like 50% extra.

Konsec.

This is quite similar in principle to the Tolltec one except it does not use
pst files. I had heard that Konsec used a mapi connector but it is the same
pop3 setup. Synchronization was noticeably quicker than the other two on a
large-ish mailbox (150 MB). It was quite stable on the same PC that the
Bynari crashed on. There is also ntlm support. The manual is only available
in German.

Its quite expensive if their price list is accurate, like about 3 times the
price of Toltec.

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


From thorsten.schnebeck at gmx.net  Mon Nov  3 17:59:44 2008
From: thorsten.schnebeck at gmx.net (Thorsten Schnebeck)
Date: Mon, 3 Nov 2008 17:59:44 +0100
Subject: bounced on alias name
Message-ID: <200811031759.44964.thorsten.schnebeck@gmx.net>

Hi,

I use a kolab 2.2 master slave setup.
master server 1 lives in the internet and is imap host of domain A
slave server 2 lives in an intranet and is imap host of domain B
Kolab uses an LDAP mirror in a master slave setup.

There is user alpha. User alpha is a member of both domains. As in current 
Kolab you can not put one person to two email accounts user alpha uses one 
email address and an alias name:

mail: alpha at domain.a and alias: beta at domain.b

Everything works fine BUT I have here one side effect:
if I send a message as beta at domain.b to e.g. gamma at domain.b and 
kolabfilter has a problem (like exe-file as attachment) and wants to inform me, 
I see this:

 to=<beta at domain.b>, relay=kolabmailboxfilter, delay=0.16, 
delays=0.02/0.01/0/0.13, dsn=5.3.0, status=bounced (service
 unavailable. Command output: Failed to set recipient: Mailbox unknown.  
Either there is no mailbox associated with this name or you do not have 
authorization to see it. 5.1.1 User unknown,
 code=550, original code 550)

This is correct, there is no mailbox "beta at domain.b" as this is only an alias. 
This also happens when I don't use an alias but a distribution list.

Why does postfix and co does not know that a special alias belongs to a 
special mailbox?

Anyone?

  Bye Thorsten




From aspineux at gmail.com  Mon Nov  3 20:44:13 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 3 Nov 2008 20:44:13 +0100
Subject: bounced on alias name
In-Reply-To: <200811031759.44964.thorsten.schnebeck@gmx.net>
References: <200811031759.44964.thorsten.schnebeck@gmx.net>
Message-ID: <71fe4e760811031144v5d8babb8ubc414c54972921e9@mail.gmail.com>

On Mon, Nov 3, 2008 at 5:59 PM, Thorsten Schnebeck
<thorsten.schnebeck at gmx.net> wrote:
> Hi,
>
> I use a kolab 2.2 master slave setup.
> master server 1 lives in the internet and is imap host of domain A
> slave server 2 lives in an intranet and is imap host of domain B
> Kolab uses an LDAP mirror in a master slave setup.
>
> There is user alpha. User alpha is a member of both domains. As in current
> Kolab you can not put one person to two email accounts user alpha uses one
> email address and an alias name:
>
> mail: alpha at domain.a and alias: beta at domain.b
>
> Everything works fine BUT I have here one side effect:
> if I send a message as beta at domain.b to e.g. gamma at domain.b and
> kolabfilter has a problem (like exe-file as attachment) and wants to inform me,
> I see this:
>
>  to=<beta at domain.b>, relay=kolabmailboxfilter, delay=0.16,
> delays=0.02/0.01/0/0.13, dsn=5.3.0, status=bounced (service
>  unavailable. Command output: Failed to set recipient: Mailbox unknown.
> Either there is no mailbox associated with this name or you do not have
> authorization to see it. 5.1.1 User unknown,
>  code=550, original code 550)
>
> This is correct, there is no mailbox "beta at domain.b" as this is only an alias.
> This also happens when I don't use an alias but a distribution list.

This is a bug I have already reported, the problem is the bounced
email is not 'injeted' in
top of the email process (where the aliases stuff are done), but after
the antivirus check !
Any bounced email is clean and then dont need a anti-(virsu/spam)
verification, this was the idea.
But then you lose all the aliases stuff !

in /kolab/etc/kolab/templates/amavisd.conf.template, you can modify the line

$notify_method = $forward_method;          # where to submit notifications

by someting like

$notify_method = 'smtp:@@@local_addr@@@:25';     # where to submit notifications


>
> Why does postfix and co does not know that a special alias belongs to a
> special mailbox?
>
> Anyone?
>
>  Bye Thorsten
>
>
>
> _______________________________________________
> 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 pav5088 at internode.on.net  Mon Nov  3 21:12:00 2008
From: pav5088 at internode.on.net (Mark Pavlichuk)
Date: Tue, 04 Nov 2008 06:12:00 +1000
Subject: Kolab + GOsa debugging
In-Reply-To: <49087A3A.50004@internode.on.net>
References: <7B91BBC61758DD1183BE000C296D2CA71049A6@ct-exchange.wins.lawco.com>
	<490564DA.6080300@internode.on.net>
	<200810271732.30746.pollmeier@gonicus.de>
	<49070BDC.2060209@internode.on.net>
	<34550.200.47.24.7.1225199561.squirrel@webmail.xtech.com.ar>
	<49087A3A.50004@internode.on.net>
Message-ID: <490F5B10.8090406@internode.on.net>

  I should have also made it clear that I'm using the debs rather than 
OpenPKG  for installing Kolab (although I certainly tried adapting this 
method).

> Alejandro Bednarik wrote:
>>  Hi Mark. In /kolab/etc/kolab/templates/slapd.conf.template below
>> /kolab/etc/openldap/schema/inetorgperson.schema add
>>
>> include         /kolab/etc/openldap/schema/nis.schema
>> include         /usr/share/gosa/contrib/openldap/samba3.schema
>> include         /usr/share/gosa/contrib/openldap/goconfig.schema
>> include         /usr/share/gosa/contrib/openldap/gofirewall.schema
>> include         /usr/share/gosa/contrib/openldap/gosystem.schema
>> include         /usr/share/gosa/contrib/openldap/gofon.schema
>> include         /usr/share/gosa/contrib/openldap/goto.schema
>> include         /usr/share/gosa/contrib/openldap/goto-mime.schema
>> include         /usr/share/gosa/contrib/openldap/gofax.schema
>> include         /usr/share/gosa/contrib/openldap/goserver.schema
>> include         /usr/share/gosa/contrib/openldap/gosa+samba3.schema
>> include         /usr/share/gosa/contrib/openldap/trust.schema
>>
>> and in /kolab/etc/openldap/schema/kolab2.schem comment this entry:
>>
>> # cyrus imapd access control list
>> # acls work with users and groups
>> #attributetype ( 1.3.6.1.4.1.19414.2.1.651
>> #  NAME 'acl'
>> #  EQUALITY caseIgnoreIA5Match
>> #  SUBSTR caseIgnoreIA5SubstringsMatch
>> #  SYNTAX 1.3.6.1.4.1.1466.115.121.1.26{256} )
>>
>> Also, if after this and run kolabconf, you still have problems, you 
>> should
>> check in /kolab/etc/openldap/schema/kolab2.schema this entry
>>
>> objectclass ( 1.3.6.1.4.1.19414.2.2.9
>>   NAME 'kolabSharedFolder'
>>   DESC 'Kolab public shared folder'
>>   SUP top STRUCTURAL
>>   MUST cn
>>   MAY ( acl $
>>         alias $
>>         cyrus-userquota $
>>         kolabHomeServer $
>>         kolabFolderType $
>>         kolabDeleteflag ) )
>>
>> and delete "acl $".
>>
>> Hope this help. Cheers!

-- 
Mark Pavlichuk
Strategic IT
ph. (07)47242890
m. 0409 124577


From daniel.vergien at rrz.uni-hamburg.de  Tue Nov  4 11:00:58 2008
From: daniel.vergien at rrz.uni-hamburg.de (Daniel Vergien)
Date: Tue, 04 Nov 2008 11:00:58 +0100
Subject: Kolab 2.2 on Solaris 10 
Message-ID: <49101D5A.6080707@rrz.uni-hamburg.de>

Hi,

I try to get Kolab 2.2 running on Solaris 10. I had to do somethings 
in addtion to the wiki:

* Install another find. Since solaris find seems to have a different 
syntax than the find kolab expects

* php-chanel-horde:
/usr/sbin/install has no -p option on solaris - used temporally 
another install script

* hore-framework-kolab:
"/kolab/RPM/TMP/pear/download" is not created. Build fails with 
message: download directory "/kolab/RPM/TMP/pear/download" is not 
writeable.  Change download_dir config variable to a writeable dir
Create dir by hand

After this it compiles. Bootstrap works. The admin interface also. The 
Problem now is that the imap server is not starting. Here is the 
output from /kolab/var/imapd/log/cyrmaster.log:

Nov 04 10:51:23 kolab <debug> master[20089]: about to exec 
/kolab/bin/imapd
Nov 04 10:51:23 kolab <debug> master[27099]: process 20089 exited, 
status 75
Nov 04 10:51:23 kolab <warning> master[27099]: service imap pid 20089 
in READY state: terminated abnormally
Nov 04 10:51:23 kolab <debug> master[20097]: about to exec 
/kolab/bin/imapd
Nov 04 10:51:23 kolab <debug> master[27099]: process 20097 exited, 
status 75
Nov 04 10:51:23 kolab <warning> master[27099]: service imap pid 20097 
in READY state: terminated abnormally
Nov 04 10:51:23 kolab <debug> master[20104]: about to exec 
/kolab/bin/imapd
Nov 04 10:51:23 kolab <debug> master[27099]: process 20104 exited, 
status 75
Nov 04 10:51:23 kolab <warning> master[27099]: service imap pid 20104 
in READY state: terminated abnormally
Nov 04 10:51:23 kolab <debug> master[20110]: about to exec 
/kolab/bin/imapd
Nov 04 10:51:23 kolab <debug> master[27099]: process 20110 exited, 
status 75
Nov 04 10:51:23 kolab <warning> master[27099]: service imap pid 20110 
in READY state: terminated abnormally
Nov 04 10:51:23 kolab <debug> master[20117]: about to exec 
/kolab/bin/imapd
Nov 04 10:51:23 kolab <debug> master[27099]: process 20117 exited, 
status 75
Nov 04 10:51:23 kolab <warning> master[27099]: service imap pid 20117 
in READY state: terminated abnormally

Does someone has some ideas?

Daniel


From g.adamczyk at netkult.eu  Tue Nov  4 07:23:14 2008
From: g.adamczyk at netkult.eu (Gregor Adamczyk)
Date: Tue, 04 Nov 2008 07:23:14 +0100
Subject: Danke =?ISO-8859-15?Q?f=FCr_Kolab!!!_Thank_you_for_Kol?=
	=?ISO-8859-15?Q?ab!!!?=
Message-ID: <490FEA52.1090808@netkult.eu>

Hallo, habe Kolab nun im t?glichen Einsatz.

Vielen Dank an alle daf?r!!!

Bitte weitermachen...


Mit freundlichen Gr??en
Gregor Adamczyk


From kcaesar at hotmail.com  Tue Nov  4 12:32:54 2008
From: kcaesar at hotmail.com (kiser Caesar)
Date: Tue, 4 Nov 2008 12:32:54 +0100
Subject: New kolab version ?
Message-ID: <BLU122-W463B17EC5717372D9F5317A31C0@phx.gbl>


Hello,


We are a company of 15000 people and we are interested to migrating under kolab.
But actually I can't making this change, because I'm waiting for the new kolab version with the sycnML support...

Who have somes news on the date when this version will be avaible ?

Thank !
_________________________________________________________________
In?dit ! Des Emotic?nes D?jant?es! Installez les dans votre Messenger ! 
http://www.ilovemessenger.fr/Emoticones/EmoticonesDejantees.aspx
-------------- section suivante --------------
Une pi?ce jointe HTML a ?t? nettoy?e...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081104/5bb1f082/attachment.html

From thorsten.schnebeck at gmx.net  Tue Nov  4 12:42:25 2008
From: thorsten.schnebeck at gmx.net (Thorsten Schnebeck)
Date: Tue, 4 Nov 2008 12:42:25 +0100
Subject: bounced on alias name [Solved]
In-Reply-To: <71fe4e760811031144v5d8babb8ubc414c54972921e9@mail.gmail.com>
References: <200811031759.44964.thorsten.schnebeck@gmx.net>
	<71fe4e760811031144v5d8babb8ubc414c54972921e9@mail.gmail.com>
Message-ID: <200811041242.25826.thorsten.schnebeck@gmx.net>

On Monday 03 November 2008 20:44:13 Alain Spineux wrote:
> This is a bug I have already reported, the problem is the bounced
> email is not 'injeted' in
> top of the email process (where the aliases stuff are done), but after
> the antivirus check !
> Any bounced email is clean and then dont need a anti-(virsu/spam)
> verification, this was the idea.
> But then you lose all the aliases stuff !
>
> in /kolab/etc/kolab/templates/amavisd.conf.template, you can modify the
> line
>
> $notify_method = $forward_method;          # where to submit notifications
>
> by someting like
>
> $notify_method = 'smtp:@@@local_addr@@@:25';     # where to submit
> notifications
>
Thanks Alain :-)

works fine.

Bye

  Thorsten


From devgioiatech at gmail.com  Tue Nov  4 12:45:33 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Tue, 4 Nov 2008 12:45:33 +0100
Subject: external web client
In-Reply-To: <20081103053223.166558e9ckjxuh44@webmail.pardus.de>
References: <d53357b70810300437r5fefb324vc1bb79c8ee17cd6a@mail.gmail.com>
	<d53357b70810300448o46b0f44euc1cf8f70190c7608@mail.gmail.com>
	<28713.200.47.24.7.1225369602.squirrel@webmail.xtech.com.ar>
	<d53357b70810300534q77110ecfjc713d64cca750d95@mail.gmail.com>
	<50233.200.47.24.7.1225371471.squirrel@webmail.xtech.com.ar>
	<d53357b70810300831u52f532e7naea1a90c616bd39d@mail.gmail.com>
	<20081031065053.41847cr9xzxhie0w@webmail.pardus.de>
	<d53357b70810310324od1929c8p7374d6b2774896c2@mail.gmail.com>
	<d53357b70810310356j10fe628dt11c2059af6532b96@mail.gmail.com>
	<20081103053223.166558e9ckjxuh44@webmail.pardus.de>
Message-ID: <d53357b70811040345t121db963yd1b6f1df026ce416@mail.gmail.com>

Sorry, but in this days i'm not in office...

i'll give you this info when i come back...

thanks for the reply.

2008/11/3 Gunnar Wrobel <wrobel at pardus.de>

>
> Quoting Antonio Straziota <devgioiatech at gmail.com>:
>
>  As suggested in the wiki, I also try to remove nss_db library (my
>> system is CENTOS) but nothing changes
>>
>
> What do you see in the log files within /kolab/var/apache/log/* when you
> try to log in?
>
> Cheers,
>
> Gunnar
>
>
>> 2008/10/31 Antonio Straziota
>>
> dir="ltr"><devgioiatech at gmail.com[1]>
>
>>  0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">mmmh...
>> i've a problem autentication by local webmail goes fine... but when
>> i try to login in horde by external webmail...i can't log in
>>
> without
>
>> any error message...
>> any idea...
>>
>> any idea?
>>
>>
>>  10/31 Gunnar Wrobel  dir="ltr"><
>>
> href="mailto:wrobel at pardus.de">wrobel at pardus.de>
>
>>  0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">   Quoting Antonio
>> Straziota <
>>
> href="mailto:devgioiatech at gmail.com">devgioiatech at gmail.com>:
>
>>  0pt 0.8ex; padding-left: 1ex;" class="gmail_quote"> Ok,
>>
>> i've installed webmail through a fresh kolab slave installation.
>>
>
>  This is currently the best option. I need to fix the wiki page :)
> We decided that it will be safer for users to install a complete
> slave rather than installing Horde on an apache/mod_php combo without
> know configuration.
>
> only a question... can i stop all other kolab service and keep
> online only Apache?
>
>  I think that should be possible.
>
> Cheers,
>
> Gunnar
>
> 2008/10/30 Alejandro Bednarik
>   dir="ltr"><alejandro at xtech.com.ar[1]>
>  0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
>  I tried this also, it works if you also copy another directory
> where live
> many php modules, i can't remember the exact path sorry. Kolab php
> have
> patches, maybe is a good idea to compile and use this as source.
> The
> performance using this method was not what we expect, but probably
> was
> the network where we set this servers...
>  Cheers!
>  Antonio Straziota wrote:
>
>> Hi Alejandro,
>> thanks for the reply...
>>
>> i'll try this solution.
>>
>> However, i think that installing all dependence and copying
>>
> the
>
>> /kolab/var/kolab/www/horde in the web root of the web server
>>
> should be
>
>> work...
>> After all horde is simply a web application that needs to be
>>
> configured
>
>>
>> Anyone can help for this?
>>
>> Thanks.
>>
>> 2008/10/30 Alejandro Bednarik
>>
>  <alejandro at xtech.com.ar[2]>
>
>>
>>
>>>  Hi Antonio. I tried the same thing a couple of weeks ago,
>>>
>> and if i am
>
>> not
>>> wrong that way to set another Horde is deprecated. You can
>>>
>> try doing a
>
>> normal kolab installation, but choosing Slave during the
>>>
>> bootstrap
>
>> process.
>>>  For sure, someone who knows this better than me can help
>>>
>> you with more
>
>> info.
>>>
>>> Cheers!
>>>
>>>
>>> Antonio Straziota wrote:
>>> > ehm,
>>> > hi again...
>>> >
>>> > i tryed to launch the script but instead of the
>>>
>> folder *horde*, the
>
>> > content
>>> > of the web root is :
>>> >
>>> >
>>> > [root at srv html]# ll
>>> > -rw-r--r--  1 root root    6021 Oct 30 12:39
>>>
>> external-horde.sh
>
>> > -rw-r--r--  1 root root    6282 Oct 30 12:41
>>> >
>>>
>>>
>
>
> HK-GW-framework_3.2_ALPHA-Fix_Prefs_for_Ingo.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>  >> > -rw-r--r--  1 root root    6883 Oct 30 12:41
>
>> >
>>>
>>>
>
>
> HK-GW-kronolith_2.2_RC1-Fbview_relevance.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>  >> > -rw-r--r--  1 root root    6901 Oct 30 12:41
>
>> >
>>>
>>>
>
>
> HK-GW-kronolith_2.2_RC1-Fbview_xfb_access.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>  >> > -rw-r--r--  1 root root    6193 Oct 30 12:41
>
>> >
>>>
>>>
>
>
> HK-GW-turba_2.2-Fix_editing_contacts.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>  >> > -rw-r--r--  1 root root    6177 Oct 30 12:41
>
>> >
>>>
>>>
>
>
> HK-GW-turba_2.2-Fix_share_id_change.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>  >> > -rw-r--r--  1 root root    6161 Oct 30 12:41
>
>> >
>>>
>>>
>
>
> HK-GW-turba_2.2-Ldap_read_only_fix.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>  >> > -rw-r--r--  1 root root    6967 Oct 30 12:41
>
>> >
>>>
>>>
>
>
> HK-JS-kronolith_2.2_RC1-Fix_library_import.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>  >> > -rw-r--r--  1 root root    6859 Oct 30 12:41
>
>> >
>>>
>>>
>
>
> HK-JS-nag_2.2_RC1-Fix_library_import.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>  >> > -rw-r--r--  1 root root    7038 Oct 30 12:41
>
>> >
>>>
>>>
>
>
> HK-SB-kronolith_2.2_RC1-Fbview_extra_params.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>  >> > -rw-r--r--  1 root root    7074 Oct 30 12:41
>
>> >
>>>
>>>
>
>
> HK-SB-kronolith_2.2_RC1-Fbview_save_attendees.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>      >> >
>
>> >
>>> > Any idea?
>>> >
>>> > 2008/10/30 Antonio Straziota
>>>
>>  <devgioiatech at gmail.com[3]>
>
>> >
>>> >> hi all,
>>> >> i'm trying to install horde on a external web
>>>
>> server.
>
>> >>
>>> >> i'm following the tutorial at
>>> >>
>>>
>>
> href="http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde">
> http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde.
>
>  >> >>
>
>> >> now i'm getting the script external-horde.sh with
>>> >>
>>> >> wget
>>> >>
>>>
>>>
> href="
> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/*checkout*/server/horde/Attic/external-horde.sh?rev=HEAD&search=None&hideattic=1&content-type=text/x-sh
> ">
> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/*checkout*/server/horde/Attic/external-horde.sh?rev=HEAD&search=None&hideattic=1&content-type=text/x-sh
>  >> >>
>
>> >> because link in the tutorial doesn't work with
>>>
>> wget
>
>> >>
>>> >> Is this script right for the kolab2.2.0?
>>> >>
>>> >> Thanks
>>> >>
>>> >>
>>> > _______________________________________________
>>> > Kolab-users mailing list
>>>
>>  >> > Kolab-users at kolab.org[4]
>
>> >
>>>
>>
> href="https://kolab.org/mailman/listinfo/kolab-users">
> https://kolab.org/mailman/listinfo/kolab-users
>  >> >
>
>>
>>>
>>> --
>>>  Alejandro Bednarik
>>>  XTech - Soluciones Linux para Empresas
>>>  (011) 5219-0678
>>>
>>  >>  alejandro at xtech.com.ar[5]
>
>>
>>>
>>> _______________________________________________
>>> Kolab-users mailing list
>>> Kolab-users at kolab.org[6]
>>>
>>>
> href="https://kolab.org/mailman/listinfo/kolab-users">
> https://kolab.org/mailman/listinfo/kolab-users
>  >>
>
>>
>>    --
>  Alejandro Bednarik
>  XTech - Soluciones Linux para Empresas
>  (011) 5219-0678
>  alejandro at xtech.com.ar[7]
>
> --
> ______ http://kdab.com _______________ http://kolab-konsortium.com _
>
> p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
>
> ____ http://www.pardus.de _________________ http://gunnarwrobel.de _
> E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
> Tel.   : +49 700 6245 0000                          Bundesstrasse 29
> Fax    : +49 721 1513 52322                          D-20146 Hamburg
> --------------------------------------------------------------------
>  >> Mail at ease - Rent a kolab groupware server at p at rdus <<
> --------------------------------------------------------------------
>
> Links:
> ------
> [1] mailto:alejandro at xtech.com.ar
> [2] mailto:alejandro at xtech.com.ar
> [3] mailto:devgioiatech at gmail.com
> [4] mailto:Kolab-users at kolab.org
> [5] mailto:alejandro at xtech.com.ar
> [6] mailto:Kolab-users at kolab.org
> [7] mailto:alejandro at xtech.com.ar
>
> ----------------------------------------------------------------
> 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
>
> --
> ______ http://kdab.com _______________ http://kolab-konsortium.com _
>
> p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
>
> ____ http://www.pardus.de _________________ http://gunnarwrobel.de _
> E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
> Tel.   : +49 700 6245 0000                          Bundesstrasse 29
> Fax    : +49 721 1513 52322                          D-20146 Hamburg
> --------------------------------------------------------------------
>   >> Mail at ease - Rent a kolab groupware server at p at rdus <<
> --------------------------------------------------------------------
>
> Links:
> ------
> [1] mailto:devgioiatech at gmail.com
>
>
>
> ----------------------------------------------------------------
> 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
>
>
-------------- parte successiva --------------
Un allegato HTML ? stato rimosso...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081104/2f55d7e2/attachment-0001.html

From itsef-admin at brightsight.com  Tue Nov  4 13:24:07 2008
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Tue, 4 Nov 2008 13:24:07 +0100
Subject: Presetting some values when creating new user?
Message-ID: <200811041324.07850.itsef-admin@brightsight.com>

Hi all,

I've been wondering about something: Is there a way to preset some of the 
values one has to fill in when creating a new user via the web interface? The 
idea is to have things like "Organisation", "Street", "City" etc. preset to 
our company's address, maybe even have a default quota setting. I've been 
searching for a bit (Wiki, list archive and the Kolab templates), but came up 
empty. Any suggestions?

Regards,

Thomas


From Roessler at FuH-E.de  Tue Nov  4 13:29:39 2008
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Tue, 04 Nov 2008 13:29:39 +0100
Subject: Presetting some values when creating new user?
In-Reply-To: <200811041324.07850.itsef-admin@brightsight.com>
References: <200811041324.07850.itsef-admin@brightsight.com>
Message-ID: <49104033.1060501@FuH-E.de>

> I've been wondering about something: Is there a way to preset some of the 
> values one has to fill in when creating a new user via the web interface? The 
> idea is to have things like "Organisation", "Street", "City" etc. preset to 
> our company's address, maybe even have a default quota setting. I've been 
> searching for a bit (Wiki, list archive and the Kolab templates), but came up 
> empty. Any suggestions?

While I am not sure whether this will fit your needs, I have had nearly 
the same problem and solved it by either making the user entries by 
script (by-product of migrating entries), or having a script to modify 
users from a list later on.

Perhaps this is not what you search for, but if it helps, I can send you 
these scripts.

Best regards,
Christian


From itsef-admin at brightsight.com  Tue Nov  4 13:38:52 2008
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Tue, 4 Nov 2008 13:38:52 +0100
Subject: Making "Room Number" visible in Kontact address book?
Message-ID: <200811041338.52707.itsef-admin@brightsight.com>

Hi all,

Another usage question: One of the fields one can fill in for a user in the 
Kolab webadmin interface is the "Room Number". I find it quite handy to have, 
however, until now I have not succeeded in making this entry visible in 
Kontact (e.g. when doing an LDAP search). Does anyone out there have a hint 
for me? Thanks in advance!

Cheerio,

Thomas
-- 
==============================================================================
           Thomas Ribbrock, Team Leader IT-Team |   brightsight
           itsef-admin at brightsight.com          |   Delftechpark 1
           +31-15-2692529                       |   NL-2628XJ Delft


From itsef-admin at brightsight.com  Tue Nov  4 13:40:02 2008
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Tue, 4 Nov 2008 13:40:02 +0100
Subject: Presetting some values when creating new user?
In-Reply-To: <49104033.1060501@FuH-E.de>
References: <200811041324.07850.itsef-admin@brightsight.com>
	<49104033.1060501@FuH-E.de>
Message-ID: <200811041340.02529.itsef-admin@brightsight.com>

On Tuesday 4 November 2008 13:29:39 Christian R??ler wrote:
> While I am not sure whether this will fit your needs, I have had nearly
> the same problem and solved it by either making the user entries by
> script (by-product of migrating entries), or having a script to modify
> users from a list later on.
>
> Perhaps this is not what you search for, but if it helps, I can send you
> these scripts.

Things like that are *always* handy to have and might open up some options for 
us later. So, please do send them, I'd appreciate it!

Regards,

Thomas


From ml at radoeka.nl  Tue Nov  4 14:30:44 2008
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 4 Nov 2008 14:30:44 +0100
Subject: bounced on alias name [Solved]
In-Reply-To: <200811041242.25826.thorsten.schnebeck@gmx.net>
References: <200811031759.44964.thorsten.schnebeck@gmx.net>
	<71fe4e760811031144v5d8babb8ubc414c54972921e9@mail.gmail.com>
	<200811041242.25826.thorsten.schnebeck@gmx.net>
Message-ID: <200811041430.44370.ml@radoeka.nl>

Op Tuesday 04 November 2008 12:42:25 schreef Thorsten Schnebeck:
> On Monday 03 November 2008 20:44:13 Alain Spineux wrote:
> > This is a bug I have already reported, the problem is the bounced
> > email is not 'injeted' in
> > top of the email process (where the aliases stuff are done), but after
> > the antivirus check !
> > Any bounced email is clean and then dont need a anti-(virsu/spam)
> > verification, this was the idea.
> > But then you lose all the aliases stuff !
> >
> > in /kolab/etc/kolab/templates/amavisd.conf.template, you can modify the
> > line
> >
> > $notify_method = $forward_method; ? ? ? ? ?# where to submit
> > notifications
> >
> > by someting like
> >
> > $notify_method = 'smtp:@@@local_addr@@@:25'; ? ? # where to submit
> > notifications
>
> Thanks Alain :-)
>
> works fine.
>
> Bye
>
> ? Thorsten


Is this a general solution?  If so, shouldn't an issue be opened in the kolab 
tracker?


-- 
Richard Bos
Without a home the journey is endless


From ml at radoeka.nl  Tue Nov  4 14:32:35 2008
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 4 Nov 2008 14:32:35 +0100
Subject: New kolab version ?
In-Reply-To: <BLU122-W463B17EC5717372D9F5317A31C0@phx.gbl>
References: <BLU122-W463B17EC5717372D9F5317A31C0@phx.gbl>
Message-ID: <200811041432.35368.ml@radoeka.nl>

Op Tuesday 04 November 2008 12:32:54 schreef kiser Caesar:
> Hello,
>
>
> We are a company of 15000 people and we are interested to migrating under
> kolab. But actually I can't making this change, because I'm waiting for the
> new kolab version with the sycnML support...
>
> Who have somes news on the date when this version will be avaible ?

From http://www.kolab.org/roadmap.html :

Release 2.2.1 is envisioned for Q4 2008 or earlier. It will have at least one 
release candidate before that. Planned improvements include adding the SyncML 
improvements to Horde.
--------------------------------------

Earlier than Q4 2008 is I think not possible anymore ;)

-- 
Richard Bos
Without a home the journey is endless


From ml at radoeka.nl  Tue Nov  4 14:34:23 2008
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 4 Nov 2008 14:34:23 +0100
Subject: Presetting some values when creating new user?
In-Reply-To: <200811041340.02529.itsef-admin@brightsight.com>
References: <200811041324.07850.itsef-admin@brightsight.com>
	<49104033.1060501@FuH-E.de>
	<200811041340.02529.itsef-admin@brightsight.com>
Message-ID: <200811041434.23786.ml@radoeka.nl>

Op Tuesday 04 November 2008 13:40:02 schreef ITSEF Admin:
> On Tuesday 4 November 2008 13:29:39 Christian R??ler wrote:
> > While I am not sure whether this will fit your needs, I have had nearly
> > the same problem and solved it by either making the user entries by
> > script (by-product of migrating entries), or having a script to modify
> > users from a list later on.
> >
> > Perhaps this is not what you search for, but if it helps, I can send you
> > these scripts.
>
> Things like that are *always* handy to have and might open up some options
> for us later. So, please do send them, I'd appreciate it!

There are some scripts here:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/namespace/libexec/

Perhaps you can store in the scripts in http://wiki.kolab.org , if they are 
not too big.  That many more people could make use of them.

-- 
Richard Bos
Without a home the journey is endless


From aspineux at gmail.com  Tue Nov  4 14:35:29 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Tue, 4 Nov 2008 14:35:29 +0100
Subject: Kolab 2.2 on Solaris 10
In-Reply-To: <49101D5A.6080707@rrz.uni-hamburg.de>
References: <49101D5A.6080707@rrz.uni-hamburg.de>
Message-ID: <71fe4e760811040535i7f37625fmb9baf34df000acf5@mail.gmail.com>

On Tue, Nov 4, 2008 at 11:00 AM, Daniel Vergien
<daniel.vergien at rrz.uni-hamburg.de> wrote:
> Hi,
>
> I try to get Kolab 2.2 running on Solaris 10. I had to do somethings
> in addtion to the wiki:
>
> * Install another find. Since solaris find seems to have a different
> syntax than the find kolab expects
>
> * php-chanel-horde:
> /usr/sbin/install has no -p option on solaris - used temporally
> another install script
>
> * hore-framework-kolab:
> "/kolab/RPM/TMP/pear/download" is not created. Build fails with
> message: download directory "/kolab/RPM/TMP/pear/download" is not
> writeable.  Change download_dir config variable to a writeable dir
> Create dir by hand
>
> After this it compiles. Bootstrap works. The admin interface also. The
> Problem now is that the imap server is not starting. Here is the
> output from /kolab/var/imapd/log/cyrmaster.log:
>
> Nov 04 10:51:23 kolab <debug> master[20089]: about to exec
> /kolab/bin/imapd
> Nov 04 10:51:23 kolab <debug> master[27099]: process 20089 exited,
> status 75
> Nov 04 10:51:23 kolab <warning> master[27099]: service imap pid 20089
> in READY state: terminated abnormally
> Nov 04 10:51:23 kolab <debug> master[20097]: about to exec
> /kolab/bin/imapd
> Nov 04 10:51:23 kolab <debug> master[27099]: process 20097 exited,
> status 75
> Nov 04 10:51:23 kolab <warning> master[27099]: service imap pid 20097
> in READY state: terminated abnormally
> Nov 04 10:51:23 kolab <debug> master[20104]: about to exec
> /kolab/bin/imapd
> Nov 04 10:51:23 kolab <debug> master[27099]: process 20104 exited,
> status 75
> Nov 04 10:51:23 kolab <warning> master[27099]: service imap pid 20104
> in READY state: terminated abnormally
> Nov 04 10:51:23 kolab <debug> master[20110]: about to exec
> /kolab/bin/imapd
> Nov 04 10:51:23 kolab <debug> master[27099]: process 20110 exited,
> status 75
> Nov 04 10:51:23 kolab <warning> master[27099]: service imap pid 20110
> in READY state: terminated abnormally
> Nov 04 10:51:23 kolab <debug> master[20117]: about to exec
> /kolab/bin/imapd
> Nov 04 10:51:23 kolab <debug> master[27099]: process 20117 exited,
> status 75
> Nov 04 10:51:23 kolab <warning> master[27099]: service imap pid 20117
> in READY state: terminated abnormally
>
> Does someone has some ideas?

What about ima*.log and other log in the log directory ?

Is your imapd.conf valid ?


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



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


From ml at radoeka.nl  Tue Nov  4 14:36:17 2008
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 4 Nov 2008 14:36:17 +0100
Subject: Kolab commercial support
In-Reply-To: <dace68270810010018x1e601d59x50d25ddff36e687f@mail.gmail.com>
References: <dace68270810010018x1e601d59x50d25ddff36e687f@mail.gmail.com>
Message-ID: <200811041436.17666.ml@radoeka.nl>

Op Wednesday 01 October 2008 09:18:47 schreef Santosh Mahale:
> 2008-10-01 09:18
>   ?
> Dear All,
>
> Does anybody have an idea about the pricing and contacts info for the
> commercial support offerings from Kolab? I tried to located that
> information on the Kolab website but could not find it.
>
> Any help is much appreciated.
>
> Kind regards,
> santosh

http://www.kolab.org/ -> Commercial (on the right side of the page) results 
in: http://www.kolab-konsortium.de/en/index.html


-- 
Richard Bos
Without a home the journey is endless


From aspineux at gmail.com  Tue Nov  4 14:47:43 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Tue, 4 Nov 2008 14:47:43 +0100
Subject: bounced on alias name [Solved]
In-Reply-To: <200811041430.44370.ml@radoeka.nl>
References: <200811031759.44964.thorsten.schnebeck@gmx.net>
	<71fe4e760811031144v5d8babb8ubc414c54972921e9@mail.gmail.com>
	<200811041242.25826.thorsten.schnebeck@gmx.net>
	<200811041430.44370.ml@radoeka.nl>
Message-ID: <71fe4e760811040547j73318616x24339aaf4022ef0f@mail.gmail.com>

On Tue, Nov 4, 2008 at 2:30 PM, Richard Bos <ml at radoeka.nl> wrote:
> Op Tuesday 04 November 2008 12:42:25 schreef Thorsten Schnebeck:
>> On Monday 03 November 2008 20:44:13 Alain Spineux wrote:
>> > This is a bug I have already reported, the problem is the bounced
>> > email is not 'injeted' in
>> > top of the email process (where the aliases stuff are done), but after
>> > the antivirus check !
>> > Any bounced email is clean and then dont need a anti-(virsu/spam)
>> > verification, this was the idea.
>> > But then you lose all the aliases stuff !
>> >
>> > in /kolab/etc/kolab/templates/amavisd.conf.template, you can modify the
>> > line
>> >
>> > $notify_method = $forward_method;          # where to submit
>> > notifications
>> >
>> > by someting like
>> >
>> > $notify_method = 'smtp:@@@local_addr@@@:25';     # where to submit
>> > notifications
>>
>> Thanks Alain :-)
>>
>> works fine.
>>
>> Bye
>>
>>   Thorsten
>
>
> Is this a general solution?  If so, shouldn't an issue be opened in the kolab
> tracker?

Yes, this is an universal solution !
I thing I already opened an issue for that, with the solution above

>
>
> --
> Richard Bos
> Without a home the journey is endless
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



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


From ml at radoeka.nl  Tue Nov  4 14:58:59 2008
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 4 Nov 2008 14:58:59 +0100
Subject: bounced on alias name [Solved]
In-Reply-To: <71fe4e760811040547j73318616x24339aaf4022ef0f@mail.gmail.com>
References: <200811031759.44964.thorsten.schnebeck@gmx.net>
	<200811041430.44370.ml@radoeka.nl>
	<71fe4e760811040547j73318616x24339aaf4022ef0f@mail.gmail.com>
Message-ID: <200811041458.59417.ml@radoeka.nl>

Op Tuesday 04 November 2008 14:47:43 schreef Alain Spineux:
> >> > in /kolab/etc/kolab/templates/amavisd.conf.template, you can modify
> >> > the line
> >> >
> >> > $notify_method = $forward_method; ? ? ? ? ?# where to submit
> >> > notifications
> >> >
> >> > by someting like
> >> >
> >> > $notify_method = 'smtp:@@@local_addr@@@:25'; ? ? # where to submit
> >> > notifications
> >>
> >> Thanks Alain :-)
> >>
> >> works fine.
> >>
> >> Bye
> >>
> >> ? Thorsten
> >
> > Is this a general solution? ?If so, shouldn't an issue be opened in the
> > kolab tracker?
>
> Yes, this is an universal solution !
> I thing I already opened an issue for that, with the solution above

This one:
https://www.intevation.de/roundup/kolab/issue1863 ?

It is still there:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/templates/amavisd.conf.template.in?rev=1.13&content-type=text/vnd.viewcvs-markup

It's easily changed, should it be done???

-- 
Richard Bos
Without a home the journey is endless


From daniel.vergien at rrz.uni-hamburg.de  Tue Nov  4 17:32:07 2008
From: daniel.vergien at rrz.uni-hamburg.de (Daniel Vergien)
Date: Tue, 04 Nov 2008 17:32:07 +0100
Subject: Kolab 2.2 on Solaris 10
In-Reply-To: <71fe4e760811040535i7f37625fmb9baf34df000acf5@mail.gmail.com>
References: <49101D5A.6080707@rrz.uni-hamburg.de>
	<71fe4e760811040535i7f37625fmb9baf34df000acf5@mail.gmail.com>
Message-ID: <49107907.3090100@rrz.uni-hamburg.de>


> 
> What about ima*.log and other log in the log directory ?
> 
Thanks for pointing me on the imapd.log. It complains about db4 can 
use my database.
It seems that the backup scripts in the wiki are not cross platform 
(linux -> solaris) capable.

A fresh install works fine.

Daniel


From oszwald at web.de  Tue Nov  4 18:36:33 2008
From: oszwald at web.de (Florian Oszwald)
Date: Tue, 4 Nov 2008 18:36:33 +0100
Subject: Postfix-Kolab Paket =?iso-8859-1?q?f=FCr_opensuse?= 10.2
Message-ID: <200811041836.33578.oszwald@web.de>

Hallo Kolab User,
ich wollte auf meinem VServer Kolab installieren.

Die repositories habe ich f?r Kolab eingebunden und mit smart install kolab 
die Installation gestartet.

Es kommt jedoch die Fehlermeldung: 
FEHLER!: Kann kolab-2.2.0-2.1 at x86_64 nicht installieren: Kein Paket stellt 
postfix-kolab bereit

Es sieht so aus, als w?rde eine repository fehlen. Ich habe nach einer 
Datei/Paket im Internet gesucht, die dieses Paket bereitstellt, jedoch nichts 
gefunden.

Ich m?chte ungern  mit openpkg arbeiten. Kennt jemand den Ersteller der Pakete 
auf download.opensuse.org/repositories/server/Kolab und kann mir weiterhelfen?

Vielen Dank f?r jeden Tipp.

Gru?,
Florian


From ml at radoeka.nl  Tue Nov  4 21:14:54 2008
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 4 Nov 2008 21:14:54 +0100
Subject: Postfix-Kolab Paket =?iso-8859-1?q?f=FCr_opensuse?= 10.2
In-Reply-To: <200811041836.33578.oszwald@web.de>
References: <200811041836.33578.oszwald@web.de>
Message-ID: <200811042114.54813.ml@radoeka.nl>

Op Tuesday 04 November 2008 18:36:33 schreef Florian Oszwald:
> Hallo Kolab User,
> ich wollte auf meinem VServer Kolab installieren.
>
> Die repositories habe ich f?r Kolab eingebunden und mit smart install kolab
> die Installation gestartet.
>
> Es kommt jedoch die Fehlermeldung:
> FEHLER!: Kann kolab-2.2.0-2.1 at x86_64 nicht installieren: Kein Paket stellt
> postfix-kolab bereit

That's because with the current postfix that is available (2.4) there is not 
need for customized kolab postfix packages, as all specific kolab patches are 
nowadays part of postfix-2.4

> Es sieht so aus, als w?rde eine repository fehlen. Ich habe nach einer
> Datei/Paket im Internet gesucht, die dieses Paket bereitstellt, jedoch
> nichts gefunden.

Install postix-2.4 from the repositories:
http://download.opensuse.org/repositories/home:/vitsoft/openSUSE_10.2/
http://download.opensuse.org/repositories/home:/peternixon/openSUSE_10.2/
http://download.opensuse.org/repositories/server:/mail/openSUSE_10.2/

> Ich m?chte ungern ?mit openpkg arbeiten. Kennt jemand den Ersteller der
> Pakete auf download.opensuse.org/repositories/server/Kolab und kann mir
> weiterhelfen?

If you install postfix24, you need to create a dummy rpm that states that it 
provides postfix-kolab.  That way all dependencies are taken care of ;)


-- 
Richard Bos
Without a home the journey is endless


From albrecht.dress at lios-tech.com  Tue Nov  4 22:08:01 2008
From: albrecht.dress at lios-tech.com (Albrecht =?iso-8859-1?b?RHJl3w==?=)
Date: Tue, 04 Nov 2008 22:08:01 +0100
Subject: Free/busy lists broken - HELP!
In-Reply-To: <1225702455l.23362l.0l@pc-adr2.lios-koeln.de>
References: <1225358234l.3914l.0l@pc-adr2.lios-koeln.de>
	<20081031064501.281239d9a4wgz9kw@webmail.pardus.de>
	<20081031081605.15302gijucixvzxx@kolab.lios-koeln.de>
	<20081101163613.36336urhc3651my5@portal.lios-koeln.de>
	<20081103055438.12682xjv8nzedr1w@webmail.pardus.de>
	<1225702455l.23362l.0l@pc-adr2.lios-koeln.de>
Message-ID: <20081104220801.14595dv1fut4ivu9@portal.lios-koeln.de>

Quoting Albrecht Dre? <albrecht.dress at lios-tech.com>:
> Isn't it possible to somehow configure in the acl's that *everyone* may
> load .ifb's or .xfb's (from Horde)?  This may not be a clean solution,
> but would at least solve my urgent needs!

Still not working, so I added it to the bug tracker:  
<https://www.intevation.de/roundup/kolab/issue3208>.

Cheers, Albrecht.


From aspineux at gmail.com  Tue Nov  4 22:16:45 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Tue, 4 Nov 2008 22:16:45 +0100
Subject: [Kolab-devel] bounced on alias name [Solved]
In-Reply-To: <200811041458.59417.ml@radoeka.nl>
References: <200811031759.44964.thorsten.schnebeck@gmx.net>
	<200811041430.44370.ml@radoeka.nl>
	<71fe4e760811040547j73318616x24339aaf4022ef0f@mail.gmail.com>
	<200811041458.59417.ml@radoeka.nl>
Message-ID: <71fe4e760811041316l603f10b1x7e6583fe59fed6@mail.gmail.com>

On Tue, Nov 4, 2008 at 2:58 PM, Richard Bos <ml at radoeka.nl> wrote:
> Op Tuesday 04 November 2008 14:47:43 schreef Alain Spineux:
>> >> > in /kolab/etc/kolab/templates/amavisd.conf.template, you can modify
>> >> > the line
>> >> >
>> >> > $notify_method = $forward_method;          # where to submit
>> >> > notifications
>> >> >
>> >> > by someting like
>> >> >
>> >> > $notify_method = 'smtp:@@@local_addr@@@:25';     # where to submit
>> >> > notifications
>> >>
>> >> Thanks Alain :-)
>> >>
>> >> works fine.
>> >>
>> >> Bye
>> >>
>> >>   Thorsten
>> >
>> > Is this a general solution?  If so, shouldn't an issue be opened in the
>> > kolab tracker?
>>
>> Yes, this is an universal solution !
>> I thing I already opened an issue for that, with the solution above
>
> This one:
> https://www.intevation.de/roundup/kolab/issue1863 ?

Yes it is

>
> It is still there:
> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/templates/amavisd.conf.template.in?rev=1.13&content-type=text/vnd.viewcvs-markup

Sorry whot do do yo mean

>
> It's easily changed, should it be done???


If a user can send email using one of his alias as sender, or a
distribution list can send email then YES
it should be considered to allow them to receive NDR

>
> --
> Richard Bos
> Without a home the journey is endless
>
> _______________________________________________
> 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 oszwald at web.de  Tue Nov  4 23:05:44 2008
From: oszwald at web.de (Florian Oszwald)
Date: Tue, 4 Nov 2008 23:05:44 +0100
Subject: Postfix-Kolab Paket =?iso-8859-1?q?f=FCr_opensuse?= 10.2
Message-ID: <200811042305.44725.oszwald@web.de>

Hi Richard,
thank you for your brilliant answer. But how do I create a dummy rpm to 
fulfill all the dependencies? I searced the archive, but could not find a 
thing.

Thank you very much in advance.
Regards,
Florian


From ml at radoeka.nl  Tue Nov  4 23:35:17 2008
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 4 Nov 2008 23:35:17 +0100
Subject: [Kolab-devel] bounced on alias name [Solved]
In-Reply-To: <71fe4e760811041316l603f10b1x7e6583fe59fed6@mail.gmail.com>
References: <200811031759.44964.thorsten.schnebeck@gmx.net>
	<200811041458.59417.ml@radoeka.nl>
	<71fe4e760811041316l603f10b1x7e6583fe59fed6@mail.gmail.com>
Message-ID: <200811042335.17319.ml@radoeka.nl>

Op Tuesday 04 November 2008 22:16:45 schreef Alain Spineux:
> > This one:
> > https://www.intevation.de/roundup/kolab/issue1863 ?
>
> Yes it is

okay, but according to Thomas this is not the right solution:
"Using port 25 isn't an option, because the mails sent by amavis shouldn't go
through amavis again."
Perhaps you can convince Thomas to implement the patch anyhow, as it is better 
that what there is now.

-- 
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.


From aspineux at gmail.com  Wed Nov  5 07:47:08 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Wed, 5 Nov 2008 07:47:08 +0100
Subject: [Kolab-devel] bounced on alias name [Solved]
In-Reply-To: <200811042335.17319.ml@radoeka.nl>
References: <200811031759.44964.thorsten.schnebeck@gmx.net>
	<200811041458.59417.ml@radoeka.nl>
	<71fe4e760811041316l603f10b1x7e6583fe59fed6@mail.gmail.com>
	<200811042335.17319.ml@radoeka.nl>
Message-ID: <71fe4e760811042247h51019771r54939e5823c67ca3@mail.gmail.com>

On Tue, Nov 4, 2008 at 11:35 PM, Richard Bos <ml at radoeka.nl> wrote:
> Op Tuesday 04 November 2008 22:16:45 schreef Alain Spineux:
>> > This one:
>> > https://www.intevation.de/roundup/kolab/issue1863 ?
>>
>> Yes it is
>
> okay, but according to Thomas this is not the right solution:
> "Using port 25 isn't an option, because the mails sent by amavis shouldn't go
> through amavis again."
> Perhaps you can convince Thomas to implement the patch anyhow, as it is better
> that what there is now.
>

It should not go through amavis, but It MUST resolve the aliases !
The good solution is to enable alias resolution after amavis,
this can be done by removing the "post-cleanup" in main.cf


@@@local_addr@@@:10026 inet n   -       n       -       -  smtpd
    -o content_filter=
> just remove this line    -o cleanup_service_name=post-cleanup
    -o local_recipient_maps=
    -o relay_recipient_maps=
    -o smtpd_restriction_classes=
    -o smtpd_client_restrictions=
    -o smtpd_helo_restrictions=
    -o smtpd_sender_restrictions=
    -o smtpd_recipient_restrictions=permit_mynetworks,reject
    -o mynetworks=127.0.0.0/8
    -o strict_rfc821_envelopes=yes
    -o smtpd_error_sleep_time=0
    -o smtpd_soft_error_limit=1001
    -o smtpd_hard_error_limit=1000



> --
> Richard Bos
> We are borrowing the world of our children,
> It is not inherited from our parents.
>
> _______________________________________________
> 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 netwarrior863 at gmail.com  Wed Nov  5 18:38:12 2008
From: netwarrior863 at gmail.com (Net Warrior)
Date: Wed, 5 Nov 2008 15:38:12 -0200
Subject: Installation issue
Message-ID: <f66a6bc10811050938t4eb99654xcd4a4aeaf8d4c19c@mail.gmail.com>

Hi here guy, during the installation process I've get this error,  Am I
missing something?
Do I need to install an extra package? is this a bug?

Generating 00INDEX.rdf for source distribution ...
openpkg:ERROR: No such command "index" found in command path
openpkg:ERROR: (/kolab/libexec/openpkg).
openpkg:ERROR: Set ${OPENPKG_TOOLS_CMDPATH} appropriately.
openpkg:ERROR: Run "/kolab/bin/openpkg --help" for list of valid commands.

There is no index  file under libexec directory.
This is version 2.2.0 installing from source under SLES10

Thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081105/a23fadb5/attachment.html

From albrecht.dress at lios-tech.com  Wed Nov  5 21:48:33 2008
From: albrecht.dress at lios-tech.com (Albrecht =?iso-8859-1?b?RHJl3w==?=)
Date: Wed, 05 Nov 2008 21:48:33 +0100
Subject: Horde & Outlook: two "Posteingang" folders
Message-ID: <20081105214833.75513xubnctaba8x@portal.lios-koeln.de>

Hi all,

I have a "cosmetic" problem if users use Outlook (via Toltec) and  
Horde in parallel with the German Horde UI.

Outlook always produces a "Posteingang" folder, to which it will store  
the messages downloaded from the INBOX after processing them locally.   
Unfortunately, the translation for INBOX is also "Posteingang", i.e.  
you will end up with two "Posteingang" folders in Horde.  Needless to  
say that this is somehow confusing, in particular if people use Horde  
to design mail filters...

Is there a way to switch off the localised display of INBOX?  Then in  
Horde these folders could be distingushed, and I could explain better  
what goes on...

Thanks, Albrecht.


From kb at oe-s.de  Fri Nov  7 11:29:52 2008
From: kb at oe-s.de (U Oe)
Date: Fri, 07 Nov 2008 11:29:52 +0100
Subject: VFS Dateisystem Fehler
Message-ID: <20081107112952.98517ei9ugjyezcw@oeit.de>

Hallo an Alle

ich bekomme beim Upload mit Horde folgende Fehlermeldung

"Das VFS-Verzeichnis konnte nicht angelegt werden"

Die Anleitung wie hier:
https://www.intevation.de/roundup/kolab/issue2134
beschrieben, hat leider nicht weiter geholfen.

Wir benutzen folgendes System:
Kolab 2.1 dann Update mit den Sourcen auf Kolab 2.2

Hat jemand eine Tipp wie das Problem behoben werden kann?

Danke und viele Gr??e
Werner


From devgioiatech at gmail.com  Fri Nov  7 12:01:46 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Fri, 7 Nov 2008 12:01:46 +0100
Subject: VFS Dateisystem Fehler
In-Reply-To: <20081107112952.98517ei9ugjyezcw@oeit.de>
References: <20081107112952.98517ei9ugjyezcw@oeit.de>
Message-ID: <d53357b70811070301x2fedf69er959a1217abd5d59b@mail.gmail.com>

Hi,
from the subject could be possible your error is "Unable to create VFS
directory" when you send a mail with attachment.

if so, i resolved the problem creating directory
/kolab/var/kolab/www/horde/tmp

mkdir /kolab/var/kolab/www/horde/tmp
chown kolab-n:kolab-n -R /kolab/var/kolab/www/horde/tmp

bye

2008/11/7 U Oe <kb at oe-s.de>

> Hallo an Alle
>
> ich bekomme beim Upload mit Horde folgende Fehlermeldung
>
> "Das VFS-Verzeichnis konnte nicht angelegt werden"
>
> Die Anleitung wie hier:
> https://www.intevation.de/roundup/kolab/issue2134
> beschrieben, hat leider nicht weiter geholfen.
>
> Wir benutzen folgendes System:
> Kolab 2.1 dann Update mit den Sourcen auf Kolab 2.2
>
> Hat jemand eine Tipp wie das Problem behoben werden kann?
>
> Danke und viele Gr??e
> Werner
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
-------------- parte successiva --------------
Un allegato HTML ? stato rimosso...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081107/924985fb/attachment.html

From kb at oe-s.de  Fri Nov  7 12:17:29 2008
From: kb at oe-s.de (U Oe)
Date: Fri, 07 Nov 2008 12:17:29 +0100
Subject: VFS Dateisystem Fehler
In-Reply-To: <d53357b70811070301x2fedf69er959a1217abd5d59b@mail.gmail.com>
References: <20081107112952.98517ei9ugjyezcw@oeit.de>
	<d53357b70811070301x2fedf69er959a1217abd5d59b@mail.gmail.com>
Message-ID: <20081107121729.107141sle3s09rk0@oeit.de>

Thank you.

That was the Problem.
Now it works.

Have a nice weekend and many greetings
Werner



Quoting Antonio Straziota <devgioiatech at gmail.com>:

> Hi,
> from the subject could be possible your error is "Unable to create VFS
> directory" when you send a mail with attachment.
>
> if so, i resolved the problem creating directory
> /kolab/var/kolab/www/horde/tmp
>
> mkdir /kolab/var/kolab/www/horde/tmp
> chown kolab-n:kolab-n -R /kolab/var/kolab/www/horde/tmp
>
> bye
>
> 2008/11/7 U Oe <kb at oe-s.de>
>
>> Hallo an Alle
>>
>> ich bekomme beim Upload mit Horde folgende Fehlermeldung
>>
>> "Das VFS-Verzeichnis konnte nicht angelegt werden"
>>
>> Die Anleitung wie hier:
>> https://www.intevation.de/roundup/kolab/issue2134
>> beschrieben, hat leider nicht weiter geholfen.
>>
>> Wir benutzen folgendes System:
>> Kolab 2.1 dann Update mit den Sourcen auf Kolab 2.2
>>
>> Hat jemand eine Tipp wie das Problem behoben werden kann?
>>
>> Danke und viele Gr??e
>> Werner
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>>
>



From devgioiatech at gmail.com  Fri Nov  7 12:33:46 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Fri, 7 Nov 2008 12:33:46 +0100
Subject: VFS Dateisystem Fehler
In-Reply-To: <20081107121729.107141sle3s09rk0@oeit.de>
References: <20081107112952.98517ei9ugjyezcw@oeit.de>
	<d53357b70811070301x2fedf69er959a1217abd5d59b@mail.gmail.com>
	<20081107121729.107141sle3s09rk0@oeit.de>
Message-ID: <d53357b70811070333y5ff66114kf400b4fc5faf82f9@mail.gmail.com>

Thank you.

You too ;)

2008/11/7 U Oe <kb at oe-s.de>

> Thank you.
>
> That was the Problem.
> Now it works.
>
> Have a nice weekend and many greetings
> Werner
>
>
>
> Quoting Antonio Straziota <devgioiatech at gmail.com>:
>
> > Hi,
> > from the subject could be possible your error is "Unable to create VFS
> > directory" when you send a mail with attachment.
> >
> > if so, i resolved the problem creating directory
> > /kolab/var/kolab/www/horde/tmp
> >
> > mkdir /kolab/var/kolab/www/horde/tmp
> > chown kolab-n:kolab-n -R /kolab/var/kolab/www/horde/tmp
> >
> > bye
> >
> > 2008/11/7 U Oe <kb at oe-s.de>
> >
> >> Hallo an Alle
> >>
> >> ich bekomme beim Upload mit Horde folgende Fehlermeldung
> >>
> >> "Das VFS-Verzeichnis konnte nicht angelegt werden"
> >>
> >> Die Anleitung wie hier:
> >> https://www.intevation.de/roundup/kolab/issue2134
> >> beschrieben, hat leider nicht weiter geholfen.
> >>
> >> Wir benutzen folgendes System:
> >> Kolab 2.1 dann Update mit den Sourcen auf Kolab 2.2
> >>
> >> Hat jemand eine Tipp wie das Problem behoben werden kann?
> >>
> >> Danke und viele Gr??e
> >> Werner
> >>
> >> _______________________________________________
> >> 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
>
-------------- parte successiva --------------
Un allegato HTML ? stato rimosso...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081107/4066dc8d/attachment.html

From NPrice at gibb.co.za  Fri Nov  7 16:12:53 2008
From: NPrice at gibb.co.za (Price,Neil)
Date: Fri, 7 Nov 2008 17:12:53 +0200 
Subject: Outlook connectors feedback revisited
Message-ID: <7B91BBC61758DD1183BE000C296D2CA7104A6C@ct-exchange.wins.lawco.com>

I've been testing connectors again...

I installed the bynari on several other machines and in each case it worked
perfectly. I was unable to reproduce my original problem with it. I got some
funnies during installation but simply ignored them and it worked fine. The
"register for 30 days license" form which thankfully only pops up once did
not seem to work. Strangely I got a message from Outlook, saying the server
could not be found. But I seemed to end up with a 30 day license anyway `(I
don't have a direct internet connection, only through a proxy).

What I liked was that I could choose to download headers only. This is vital
if I am stuck in some little town with a slow connection. If you added ntlm
support for single windows sign-on then I think it is an excellent
connector. I also had excellent response from Bynari to my queries. They
also informed me their connector is available in Europe for a similar price
to the Toltec one.

I was really confused by the calendar. Konsec and Bynari both saw the same
calendar but Toltec saw an almost, but not quite, completely different one
with only 1 event in common.

Bynari showed my folders differently to the other 2, with all my folders
under an inbox, so I had an inbox under an inbox which is a bit confusing.
The other 2 showed nmy folders as I expected them, with several folders on
the same level as the inbox.

Compatibility between the different connectors leaves something to be
desired. After the Toltec connector had done its thing, the other 2 showed
attachments "Toltec.dat" on many emails. Bynari (but not Konsec) showed some
indecipherable Toltec objects in the inbox.

With the Konsec connector Outlook often told me on startup that my server
was unavailable. This may have been a side effect of the silly "buy a
license now" window that pops up at startup.  I simply tried again and it
worked.

Konsec seemed to produce an extraordinarily large pst file of over 500MB for
a 150 MB mailbox. Toltec's pst file was as expected and Bynari was very
thrifty with disk space (it stores the headers in a .db file and stores the
attachments as files).


> I've been testing some Outlook connectors on Kolab.
> 
> Toltec
> 
> It works fine and is reasonably priced. The manual is a bit 
> confusing. Its
> got an awkward method of downloading the emails via pop3 and 
> synchronizing
> it back again. You end up with 2 inboxes in Horde because of 
> that. It uses
> pst files with their limitations. Its slow on start-up and 
> synchronization
> on a big mailbox (150MB)
> 
> Its got ntlm support so a single sign on is theoretically 
> possible if you
> used a samba-kolab ldap setup, but I could not find info on this yet.
> 
> Bynari
> 
> Its got a nice feature where it will copy the emails from 
> your existing
> Outlook profile. This worked fairly well copying emails out of an MS
> Exchange profile but some of the sender emails addresses got 
> trashed in the
> import. It looks really professional but it kept locking up 
> on me while
> downloading the emails on a big mailbox. It would sync to 
> about 5% and lock
> up. I will test it on another machine in case it just did not 
> like the one I
> was testing on (this is windows, remember). It does not use 
> pst files. Its
> more expensive that the Toltec one. A lot more, like 50% extra.
> 
> Konsec.
> 
> This is quite similar in principle to the Tolltec one except 
> it does not use
> pst files. I had heard that Konsec used a mapi connector but 
> it is the same
> pop3 setup. Synchronization was noticeably quicker than the 
> other two on a
> large-ish mailbox (150 MB). It was quite stable on the same 
> PC that the
> Bynari crashed on. There is also ntlm support. The manual is 
> only available
> in German.
> 
> Its quite expensive if their price list is accurate, like 
> about 3 times the
> price of Toltec.
> 


From michael at pasdziernik.net  Fri Nov  7 16:37:17 2008
From: michael at pasdziernik.net (Michael Pasdziernik)
Date: Fri, 7 Nov 2008 16:37:17 +0100
Subject: Kolab, Outlook and vtiger or sugarcrm
Message-ID: <200811071637.17541.michael@pasdziernik.net>

Hi,
is anyone running outlook with a Kolab connector and a plugin for sugarcrm or 
vtiger crm sync? does this work?

regards
michael


From wrobel at pardus.de  Fri Nov  7 16:40:49 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Fri, 07 Nov 2008 16:40:49 +0100
Subject: Presetting some values when creating new user?
In-Reply-To: <200811041324.07850.itsef-admin@brightsight.com>
References: <200811041324.07850.itsef-admin@brightsight.com>
Message-ID: <20081107164049.9317947pwl6vowht@webmail.pardus.de>

Quoting ITSEF Admin <itsef-admin at brightsight.com>:

> Hi all,
>
> I've been wondering about something: Is there a way to preset some of the
> values one has to fill in when creating a new user via the web interface? The
> idea is to have things like "Organisation", "Street", "City" etc. preset to
> our company's address, maybe even have a default quota setting. I've been
> searching for a bit (Wiki, list archive and the Kolab templates), but came up
> empty. Any suggestions?

I hope things like this will get easier once I finally get around to  
recode the web admin in Horde. Which I admittedly tried last year and  
stopped. But in the recent months about half of this has been finally  
completed so there is a chance we get a tool with a better code base  
during next year.

Cheers,

Gunnar

>
> Regards,
>
> 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/20081107/0922c610/attachment-0001.bin

From vincent at acheson.uk.com  Fri Nov  7 16:42:42 2008
From: vincent at acheson.uk.com (vincent acheson)
Date: Fri, 7 Nov 2008 15:42:42 -0000
Subject: Kolab, Outlook and vtiger or sugarcrm
In-Reply-To: <200811071637.17541.michael@pasdziernik.net>
References: <200811071637.17541.michael@pasdziernik.net>
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAJE6f34E4PlMpqe2btQZcEyigwAAEAAAAMJ5bZHs6PRFlbzhhXsAr04BAAAAAA==@acheson.uk.com>

Toltec OK with vtiger.

Vincent

-----Original Message-----
From: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org]
On Behalf Of Michael Pasdziernik
Sent: 07 November 2008 15:37
To: kolab-users at kolab.org
Subject: Kolab, Outlook and vtiger or sugarcrm

Hi,
is anyone running outlook with a Kolab connector and a plugin for sugarcrm
or 
vtiger crm sync? does this work?

regards
michael

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


__________ Information from ESET Smart Security, version of virus signature
database 3595 (20081107) __________

The message was checked by ESET Smart Security.

http://www.eset.com



From wrobel at pardus.de  Fri Nov  7 16:43:57 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Fri, 07 Nov 2008 16:43:57 +0100
Subject: New kolab version ?
In-Reply-To: <BLU122-W463B17EC5717372D9F5317A31C0@phx.gbl>
References: <BLU122-W463B17EC5717372D9F5317A31C0@phx.gbl>
Message-ID: <20081107164357.4862193dw4cmwdhc@webmail.pardus.de>


Quoting kiser Caesar <kcaesar at hotmail.com>:

> Hello,
>
>
> We are a company of 15000 people and we are interested to migrating
> under kolab.
> But actually I can't making this change, because I'm waiting for
> the new kolab version with the sycnML support...

You are considering switching the mail server for this amount of  
people and the single relevant feature that is a blocker for you is  
SyncML? Sounds strange :)

>
> Who have somes news on the date when this version will be avaible ?

I think I mentioned before that there should be a first beta this  
month. We had hoped for last month but there are many parallel Kolab  
projects at the moment and many resources are bound.

Anyhow I finished my work on Horde today and the next step will be  
Kolab CVS. There is not that much left to do.

Cheers,

Gunnar

>
> Thank !
>
> -------------------------
> T?l?phonez gratuitement ? tous vos proches avec Windows Live
> Messenger  !
href=\"http://www.windowslive.fr/messenger/1.asp\">T?l?chargez-le
> maintenant !

-- 
____ 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/20081107/2cec01df/attachment.bin

From wrobel at pardus.de  Fri Nov  7 16:46:51 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Fri, 07 Nov 2008 16:46:51 +0100
Subject: Postfix-Kolab Paket =?utf-8?b?ZsO8cg==?= opensuse 10.2
In-Reply-To: <200811041836.33578.oszwald@web.de>
References: <200811041836.33578.oszwald@web.de>
Message-ID: <20081107164651.153031gnbb7ucfeo@webmail.pardus.de>

Quoting Florian Oszwald <oszwald at web.de>:

> Hallo Kolab User,
> ich wollte auf meinem VServer Kolab installieren.
>
> Die repositories habe ich f?r Kolab eingebunden und mit smart install kolab
> die Installation gestartet.
>
> Es kommt jedoch die Fehlermeldung:
> FEHLER!: Kann kolab-2.2.0-2.1 at x86_64 nicht installieren: Kein Paket stellt
> postfix-kolab bereit
>
> Es sieht so aus, als w?rde eine repository fehlen. Ich habe nach einer
> Datei/Paket im Internet gesucht, die dieses Paket bereitstellt, jedoch nichts
> gefunden.
>
> Ich m?chte ungern  mit openpkg arbeiten.

"ungern mit openpkg arbeiten" ist kein wirklich triftiger Grund auf  
eine native Version zu wechseln :) Die Beschreibung "ungern mit  
openpkg arbeiten" trifft schlie?lich auch auf die Kolab Entwickler zu.  
Es ist aber eine unbestreitbare Tatsache, dass keiner der nativen  
Ports derzeit mit der Stabilit?t des gut getesten  
Kolab2/OpenPKG-Servers mithalten kann. Und ein funktionierendes  
Mail-System ist etwas Nettes :)

Gru?,

Gunnar

> Kennt jemand den Ersteller der Pakete
> auf download.opensuse.org/repositories/server/Kolab und kann mir  
> weiterhelfen?
>
> Vielen Dank f?r jeden Tipp.
>
> Gru?,
> Florian
>
> _______________________________________________
> 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/20081107/f619d510/attachment.bin

From wrobel at pardus.de  Fri Nov  7 16:51:41 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Fri, 07 Nov 2008 16:51:41 +0100
Subject: Installation issue
In-Reply-To: <f66a6bc10811050938t4eb99654xcd4a4aeaf8d4c19c@mail.gmail.com>
References: <f66a6bc10811050938t4eb99654xcd4a4aeaf8d4c19c@mail.gmail.com>
Message-ID: <20081107165141.19802lg4d1r66omc@webmail.pardus.de>


Quoting Net Warrior <netwarrior863 at gmail.com>:

> Hi here guy, during the installation process I've get this error, Am  
> I missing something?
> Do I need to install an extra package? is this a bug?
>
> Generating 00INDEX.rdf for source distribution ...
> openpkg:ERROR: No such command "index" found in command
> path
> openpkg:ERROR: (/kolab/libexec/openpkg).
> openpkg:ERROR: Set ${OPENPKG_TOOLS_CMDPATH} appropriately.
> openpkg:ERROR: Run "/kolab/bin/openpkg --help" for list
> of valid commands.

Looks like you used the special "-X" flag with the install-kolab.sh  
script. This is only meant for special circumstances and you might  
have used it in an incorrect context. Can you detail why you used that  
flag and provide the complete command you ran?

Cheers,

Gunnar

>
> There is no index  file under libexec directory.
> This is version 2.2.0 installing from source under SLES10
>
> Thanks in advance.

-- 
____ 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/20081107/3aed67da/attachment.bin

From wrobel at pardus.de  Fri Nov  7 16:54:21 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Fri, 07 Nov 2008 16:54:21 +0100
Subject: Horde & Outlook: two "Posteingang" folders
In-Reply-To: <20081105214833.75513xubnctaba8x@portal.lios-koeln.de>
References: <20081105214833.75513xubnctaba8x@portal.lios-koeln.de>
Message-ID: <20081107165421.98624sh4c2ic3log@webmail.pardus.de>

Quoting Albrecht Dre? <albrecht.dress at lios-tech.com>:

> Hi all,
>
> I have a "cosmetic" problem if users use Outlook (via Toltec) and
> Horde in parallel with the German Horde UI.
>
> Outlook always produces a "Posteingang" folder, to which it will store
> the messages downloaded from the INBOX after processing them locally.
> Unfortunately, the translation for INBOX is also "Posteingang", i.e.
> you will end up with two "Posteingang" folders in Horde.  Needless to
> say that this is somehow confusing, in particular if people use Horde
> to design mail filters...

This is a know problem with Toltec.

>
> Is there a way to switch off the localised display of INBOX?  Then in
> Horde these folders could be distingushed, and I could explain better
> what goes on...

No, not really. You could of course try to hack something like this  
into the code but it is not recommended. I believe you currently have  
to live with that feature if you are using Toltec Connector  
simultaniously with other Kolab clients.

Cheers,

Gunnar

>
> Thanks, Albrecht.
>
> _______________________________________________
> 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/20081107/f390c7fa/attachment.bin

From LHendricks at austinent.com  Fri Nov  7 18:15:25 2008
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Fri, 7 Nov 2008 11:15:25 -0600 
Subject: kontact/win
Message-ID: <7907AE10BB50DD4F840E76527D27EF1902104F13@entmail.domain.austinent.com>

I have been poking around looking for a mailing list or updated info on
kontact/win but am not having much luck (hopefully it's not right under my
nose).  I am looking forward to kolab 2.2.1 and kontact/win to begin
migration from our exchange 5.5 server so if there's any way to get an
update on this that someone knows of or start using the alpha version in my
own testing that would be a great help.

 

Thanks,

Lucas Hendricks

AENTC IT Support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081107/6ec89cd9/attachment-0001.html

From netwarrior863 at gmail.com  Fri Nov  7 20:01:22 2008
From: netwarrior863 at gmail.com (Net Warrior)
Date: Fri, 7 Nov 2008 17:01:22 -0200
Subject: Installation issue
In-Reply-To: <20081107165141.19802lg4d1r66omc@webmail.pardus.de>
References: <f66a6bc10811050938t4eb99654xcd4a4aeaf8d4c19c@mail.gmail.com>
	<20081107165141.19802lg4d1r66omc@webmail.pardus.de>
Message-ID: <f66a6bc10811071101m18e9ffc6p62443735043a6b26@mail.gmail.com>

Hi, thanks for your time.

If I run the script without any parameters, which I did at the begining,
almost at the end of the installation I've get a permission denied reading
the rdf file, making a research in the list, I found that that happened to
lots of people and was due a permission set, changing permission in the tmp
directory did not resolved the problem, I found also that at certain moment
the script changes to kolab user to do some stuff, so , that's why the
permision denied.

So, what I did was, download the source to a directory, lets say, data, then
under data I created a directory called tmp, then changed permission to 777
botch directories, running the script in help mode, it says that the X
paramater generates the rdf file under the current directory where it's
executed, so in the script (install-kolab.sh ) I changed the temp
directory to be tmp under data, and tmp  has rwx to everyone, so this time
there were no permision denied error but I've got that index not found, and
taking a look under libexex there is no index command, there are rpm, and
others, so I assumed that the "index" command is part of the software,
something it compiles during the process to accomplish something which in
tern is passed as an argument to the openpkg program.

That's what I did, I'm lost, it's there another way to do that?


Thanks for your time  and support.






2008/11/7, Gunnar Wrobel <wrobel at pardus.de>:
>
>
> Quoting Net Warrior <netwarrior863 at gmail.com>:
>
> Hi here guy, during the installation process I've get this error, Am I
>> missing something?
>> Do I need to install an extra package? is this a bug?
>>
>> Generating 00INDEX.rdf for source distribution ...
>> openpkg:ERROR: No such command "index" found in command
>> path
>> openpkg:ERROR: (/kolab/libexec/openpkg).
>> openpkg:ERROR: Set ${OPENPKG_TOOLS_CMDPATH} appropriately.
>> openpkg:ERROR: Run "/kolab/bin/openpkg --help" for list
>> of valid commands.
>>
>
> Looks like you used the special "-X" flag with the install-kolab.sh script.
> This is only meant for special circumstances and you might have used it in
> an incorrect context. Can you detail why you used that flag and provide the
> complete command you ran?
>
> Cheers,
>
> Gunnar
>
>
>> There is no index  file under libexec directory.
>> This is version 2.2.0 installing from source under SLES10
>>
>> Thanks in advance.
>>
>
> --
> ____ 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081107/868ba7f3/attachment.html

From netwarrior863 at gmail.com  Fri Nov  7 20:54:26 2008
From: netwarrior863 at gmail.com (Net Warrior)
Date: Fri, 7 Nov 2008 17:54:26 -0200
Subject: Installation issue
In-Reply-To: <20081107165141.19802lg4d1r66omc@webmail.pardus.de>
References: <f66a6bc10811050938t4eb99654xcd4a4aeaf8d4c19c@mail.gmail.com>
	<20081107165141.19802lg4d1r66omc@webmail.pardus.de>
Message-ID: <f66a6bc10811071154jacdeecv9d417a96a8c345d6@mail.gmail.com>

This is what I get when running the script without any parameters, that' why
I did, what I did.

Now running:

/kolab/bin/openpkg build -kKBuZ -r
"/tmp/install-kolab.15536.5655.10943.3323" -p "ix86-suse10-kolab" -D
openldap::with_pth=no -D sasl::with_ldap -D sasl::with_login -D
sasl::with_ntlm -D postfix::with_sasl -D postfix::with_ssl -D
postfix::with_ldap -D imapd::with_kolab_nocaps
-Dkolabd::kolab_version=2.2.0
-Dkolab-webadmin::kolab_version=2.2.0
openpkg-tools openldap postfix kolabd kolab-filter kolab-freebusy
kolab-webadmin fbview-kronolith horde-kolab-client | sh

---------------------------------------
openpkg:build:FATAL: cannot open
'/tmp/install-kolab.15536.5655.10943.3323/00INDEX.rdf' (Permiso denegado)




2008/11/7, Gunnar Wrobel <wrobel at pardus.de>:
>
>
> Quoting Net Warrior <netwarrior863 at gmail.com>:
>
> Hi here guy, during the installation process I've get this error, Am I
>> missing something?
>> Do I need to install an extra package? is this a bug?
>>
>> Generating 00INDEX.rdf for source distribution ...
>> openpkg:ERROR: No such command "index" found in command
>> path
>> openpkg:ERROR: (/kolab/libexec/openpkg).
>> openpkg:ERROR: Set ${OPENPKG_TOOLS_CMDPATH} appropriately.
>> openpkg:ERROR: Run "/kolab/bin/openpkg --help" for list
>> of valid commands.
>>
>
> Looks like you used the special "-X" flag with the install-kolab.sh script.
> This is only meant for special circumstances and you might have used it in
> an incorrect context. Can you detail why you used that flag and provide the
> complete command you ran?
>
> Cheers,
>
> Gunnar
>
>
>> There is no index  file under libexec directory.
>> This is version 2.2.0 installing from source under SLES10
>>
>> Thanks in advance.
>>
>
> --
> ____ 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081107/2bdefa3e/attachment.html

From kloecker at kde.org  Fri Nov  7 20:58:09 2008
From: kloecker at kde.org (Ingo =?iso-8859-15?q?Kl=F6cker?=)
Date: Fri, 07 Nov 2008 20:58:09 +0100
Subject: kontact/win
In-Reply-To: <7907AE10BB50DD4F840E76527D27EF1902104F13@entmail.domain.austinent.com>
References: <7907AE10BB50DD4F840E76527D27EF1902104F13@entmail.domain.austinent.com>
Message-ID: <200811072058.13469@thufir.ingo-kloecker.de>

On Friday 07 November 2008, Lucas Hendricks wrote:
> I have been poking around looking for a mailing list or updated info
> on kontact/win but am not having much luck (hopefully it's not right
> under my nose).  I am looking forward to kolab 2.2.1 and kontact/win
> to begin migration from our exchange 5.5 server so if there's any way
> to get an update on this that someone knows of or start using the
> alpha version in my own testing that would be a great help.

You can find information about the status of KDE on Windows on 
http://windows.kde.org/.


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/20081107/c3e8b89e/attachment.bin

From m.gabriel at das-netzwerkteam.de  Fri Nov  7 21:09:52 2008
From: m.gabriel at das-netzwerkteam.de (Mike Gabriel)
Date: Fri, 07 Nov 2008 21:09:52 +0100
Subject: Horde & Outlook: two "Posteingang" folders
In-Reply-To: <20081107165421.98624sh4c2ic3log@webmail.pardus.de>
References: <20081105214833.75513xubnctaba8x@portal.lios-koeln.de>
	<20081107165421.98624sh4c2ic3log@webmail.pardus.de>
Message-ID: <20081107210952.16681kdlx93sjz4g@mail.das-netzwerkteam.de>

hi albrecht,

On Fr 07 Nov 2008 16:54:21 CET Gunnar Wrobel wrote:

> Quoting Albrecht Dre? <albrecht.dress at lios-tech.com>:
>
>> Hi all,
>>
>> I have a "cosmetic" problem if users use Outlook (via Toltec) and
>> Horde in parallel with the German Horde UI.
>>
>> Outlook always produces a "Posteingang" folder, to which it will store
>> the messages downloaded from the INBOX after processing them locally.
>> Unfortunately, the translation for INBOX is also "Posteingang", i.e.
>> you will end up with two "Posteingang" folders in Horde.  Needless to
>> say that this is somehow confusing, in particular if people use Horde
>> to design mail filters...
>
> This is a know problem with Toltec.
>
>>
>> Is there a way to switch off the localised display of INBOX?  Then in
>> Horde these folders could be distingushed, and I could explain better
>> what goes on...
>
> No, not really. You could of course try to hack something like this   
> into the code but it is not recommended. I believe you currently  
> have  to live with that feature if you are using Toltec Connector   
> simultaniously with other Kolab clients.
>
> Cheers,
>
> Gunnar
>
>>
>> Thanks, Albrecht.

i hacked horde's / imp's locales for that. horde's resp. the server's  
"Posteingang" is a translation of "INBOX".

outlook's "Posteingang" is an IMAP folder name.

the first you can modify by editing the German locale file de_DE.po in  
horde/imp/po. after that you have to execute the translation.php  
script in horde/po.

good luck,
mike



-- 

das netzwerkteam
mike gabriel, dorfstr. 27, 24245 barmissen
fon: +49 (4302) 281418, fax: +49 (4302) 281419
mail: m.gabriel at das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

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


From jaheme at gmx.de  Fri Nov  7 22:09:37 2008
From: jaheme at gmx.de (Jan - Hendrik Meyer)
Date: Fri, 07 Nov 2008 22:09:37 +0100
Subject: Mailbox does not exist
Message-ID: <4914AE91.1090600@gmx.de>

 Hello,

after I installed so SuSe integration package sucessfully, I've started 
to integrate Linux authentification with ldap. I used the LDAP Account 
Manager to manage the account. I created a account with the unix schemas 
and the kolab schemas for testing.
I can login the xserver and a mailbox has also been created.

But there is one error:

lmtp[29919]: verify_user(home!user.norbertlang) failed: Mailbox does not exist

I think the cause could be that the user name need to be different to the username, 
if I use the kolab and unix schema 
(because the username doesn't support the @)

Are there any solutions?

Thanks

Jan-Hendrik


From delonly at gmail.com  Sat Nov  8 21:14:13 2008
From: delonly at gmail.com (Del)
Date: Sat, 08 Nov 2008 21:14:13 +0100
Subject: New kolab version ?
In-Reply-To: <20081107164357.4862193dw4cmwdhc@webmail.pardus.de>
References: <BLU122-W463B17EC5717372D9F5317A31C0@phx.gbl>
	<20081107164357.4862193dw4cmwdhc@webmail.pardus.de>
Message-ID: <1226175253.9744.6.camel@black>

On Fri, 2008-11-07 at 16:43 +0100, Gunnar Wrobel wrote:
> Quoting kiser Caesar <kcaesar at hotmail.com>:
> 
> > Hello,
> >
> >
> > We are a company of 15000 people and we are interested to migrating
> > under kolab.
> > But actually I can't making this change, because I'm waiting for
> > the new kolab version with the sycnML support...
> 
> You are considering switching the mail server for this amount of  
> people and the single relevant feature that is a blocker for you is  
> SyncML? Sounds strange :)

Not really. It is a critical feature, and Kiser is certainly not the
only one who sees it that way. Actually, I believe SyncML support will
be the turning point for Kolab, the years ahead are going to be very
interesting :)

Cheers,
Del


From wrobel at pardus.de  Sat Nov  8 13:44:36 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sat, 08 Nov 2008 13:44:36 +0100
Subject: SyncML: A technical perspective (Re: New kolab version ?)
In-Reply-To: <1226175253.9744.6.camel@black>
References: <BLU122-W463B17EC5717372D9F5317A31C0@phx.gbl>
	<20081107164357.4862193dw4cmwdhc@webmail.pardus.de>
	<1226175253.9744.6.camel@black>
Message-ID: <20081108134436.11005f366d6mwggs@webmail.pardus.de>

Quoting Del <delonly at gmail.com>:

> On Fri, 2008-11-07 at 16:43 +0100, Gunnar Wrobel wrote:
>> Quoting kiser Caesar <kcaesar at hotmail.com>:
>>
>> > Hello,
>> >
>> >
>> > We are a company of 15000 people and we are interested to migrating
>> > under kolab.
>> > But actually I can't making this change, because I'm waiting for
>> > the new kolab version with the sycnML support...
>>
>> You are considering switching the mail server for this amount of
>> people and the single relevant feature that is a blocker for you is
>> SyncML? Sounds strange :)
>
> Not really. It is a critical feature, and Kiser is certainly not the
> only one who sees it that way. Actually, I believe SyncML support will
> be the turning point for Kolab,

I disagree. It will certainly be nice to have some synchronization  
support and people will sync their mobiles with the server. But this  
will only be a temporary solution.

A year ago I would have agreed with you. That was *before* I  
implemented SyncML support for Kolab. SyncML has some severe problems.  
Maybe not so much in the area of the protocol. But the fact that the  
actual data exchange elements used within the protocol are being left  
undefined means that any real world implementation will only ever work  
with some devices. Not with all. There will always be a plethora of  
device specific incompatibilities.

In addition I doubt that all the little corner cases (such as a user  
that looses connection during sync) will always be handled correctly.  
The result are duplicated entries.

I deliberately describe this in a negative way. Of course things will  
often work and make users happy. But from a technical point of view  
I'm pretty convinced that SyncML is not really going anywhere. Or let  
me rephrase: I hope it is not going anywhere.

Kolab is doing one thing right: It defines a format that any client  
should be able to read and write so that all other compliant clients  
can also work with the stored data. This is a pretty robust approach  
and syncing is not.

If you want clean support for this on a mobile client it is actually  
not too difficult: You add a Kolab Format compliant IMAP client on  
your mobile device and you will be fine. No syncing, no problems.

Will future clients support this? Yes, no question. IMAP access on a  
mobile client is nothing fancy. And this is why I'm currently certain  
that SyncML is just a temporary thing.

> the years ahead are going to be very
> interesting :)

Indeed.

Cheers,

Gunnar

>
> Cheers,
> Del
>
> _______________________________________________
> 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/20081108/1c7e3018/attachment.bin

From delonly at gmail.com  Sat Nov  8 23:53:05 2008
From: delonly at gmail.com (Del)
Date: Sat, 08 Nov 2008 23:53:05 +0100
Subject: SyncML: A technical perspective (Re: New kolab version ?)
In-Reply-To: <20081108134436.11005f366d6mwggs@webmail.pardus.de>
References: <BLU122-W463B17EC5717372D9F5317A31C0@phx.gbl>
	<20081107164357.4862193dw4cmwdhc@webmail.pardus.de>
	<1226175253.9744.6.camel@black>
	<20081108134436.11005f366d6mwggs@webmail.pardus.de>
Message-ID: <1226184785.6574.43.camel@merom>

On Sat, 2008-11-08 at 13:44 +0100, Gunnar Wrobel wrote:
> A year ago I would have agreed with you. That was *before* I  
> implemented SyncML support for Kolab. SyncML has some severe problems.  
> Maybe not so much in the area of the protocol. But the fact that the  
> actual data exchange elements used within the protocol are being left  
> undefined means that any real world implementation will only ever work  
> with some devices. Not with all. There will always be a plethora of  
> device specific incompatibilities.

Thanks for sharing your concerns and hindsight. I must admit that I
haven't looked into the SyncML protocol, so I am not familiar with its
shortcomings. I am grateful for any negative experiences you can share,
e.g., handsets that work well or not.

> I deliberately describe this in a negative way. Of course things will  
> often work and make users happy. But from a technical point of view  
> I'm pretty convinced that SyncML is not really going anywhere. Or let  
> me rephrase: I hope it is not going anywhere.

I do see the need for an open standardised protocol, do you see any
alternative? Is it feasible to extend SyncML specifications to mend the
shortcomings?

> Kolab is doing one thing right: It defines a format that any client  
> should be able to read and write so that all other compliant clients  
> can also work with the stored data. This is a pretty robust approach  
> and syncing is not.

Still, this requires everybody to adapt to Kolab's format, I do not
think it is a good technical solution. Do you have any experience with
Funambol's connectors? Seems they could potentially clear out some of
the troubling points having connectors to most devices.

> If you want clean support for this on a mobile client it is actually  
> not too difficult: You add a Kolab Format compliant IMAP client on  
> your mobile device and you will be fine. No syncing, no problems.
> 
> Will future clients support this? Yes, no question. IMAP access on a  
> mobile client is nothing fancy. And this is why I'm currently certain  
> that SyncML is just a temporary thing.

A good point. However, is there any Kolab client underway that will run
on most mobile devices? If not, what kind of time span are we in for?

Cheers,
Del


From helge.hess at opengroupware.org  Sun Nov  9 00:41:42 2008
From: helge.hess at opengroupware.org (Helge Hess)
Date: Sun, 9 Nov 2008 00:41:42 +0100
Subject: SyncML: A technical perspective (Re: New kolab version ?)
In-Reply-To: <1226184785.6574.43.camel@merom>
References: <BLU122-W463B17EC5717372D9F5317A31C0@phx.gbl>
	<20081107164357.4862193dw4cmwdhc@webmail.pardus.de>
	<1226175253.9744.6.camel@black>
	<20081108134436.11005f366d6mwggs@webmail.pardus.de>
	<1226184785.6574.43.camel@merom>
Message-ID: <E2F342CE-3084-4C22-B48D-2ECBA749C089@opengroupware.org>

On 08.11.2008, at 23:53, Del wrote:
> I do see the need for an open standardised protocol, do you see any
> alternative?


http://www.calconnect.org/

Greets,
   Helge


From wrobel at pardus.de  Sun Nov  9 08:21:08 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sun, 09 Nov 2008 08:21:08 +0100
Subject: kontact/win
In-Reply-To: <7907AE10BB50DD4F840E76527D27EF1902104F13@entmail.domain.austinent.com>
References: <7907AE10BB50DD4F840E76527D27EF1902104F13@entmail.domain.austinent.com>
Message-ID: <20081109082108.34965ww8bsoju3cw@webmail.pardus.de>


Quoting Lucas Hendricks <LHendricks at austinent.com>:

>
>
> I have been poking around looking for a mailing
> list or updated info on kontact/win but am not having much luck
> (hopefully it's not right under my nose).  I am looking forward to
> kolab 2.2.1

Kolab Server 2.2.1 is heavily being worked on and moved to testing/bug  
fixing phase last week. Watch the CVS commits.

Cheers,

Gunnar

> and kontact/win to begin migration from our exchange
5.5
> server so if there's any way to get an update on this that someone
> knows of or start using the alpha version in my own
w:st="on">testing that would be a great
> help.
>
>  Thanks,
>
> Lucas
> Hendricks
>
> AENTC IT
> Support

-- 
____ http://www.pardus.de[1] _________________
http://gunnarwrobel.de[2] _

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

Links:
------
[1] http://www.pardus.de
[2] http://gunnarwrobel.de


----------------------------------------------------------------
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/20081109/b46cae71/attachment.bin

From wrobel at pardus.de  Sun Nov  9 08:29:38 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sun, 09 Nov 2008 08:29:38 +0100
Subject: Mailbox does not exist
In-Reply-To: <4914AE91.1090600@gmx.de>
References: <4914AE91.1090600@gmx.de>
Message-ID: <20081109082938.542774wzzijjswco@webmail.pardus.de>

Quoting Jan - Hendrik Meyer <jaheme at gmx.de>:

>  Hello,
>
> after I installed so SuSe integration package sucessfully, I've started
> to integrate Linux authentification with ldap. I used the LDAP Account
> Manager to manage the account. I created a account with the unix schemas
> and the kolab schemas for testing.
> I can login the xserver and a mailbox has also been created.
>
> But there is one error:
>
> lmtp[29919]: verify_user(home!user.norbertlang) failed: Mailbox does  
> not exist
>
> I think the cause could be that the user name need to be different  
> to the username,
> if I use the kolab and unix schema
> (because the username doesn't support the @)

I'm not 100% certain I understand how you merge the two schemas or how  
a user account looks in your case. Maybe you could attach an LDIF  
output.

In any case a Kolab user should always have an email address as  
primary identifier. You may use the uid for any additional IDs and I  
think you should be able to use this one for uinx login.

Cheers,

Gunnar

>
> Are there any solutions?
>
> Thanks
>
> Jan-Hendrik
>
> _______________________________________________
> 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/20081109/3c4edbc2/attachment-0001.bin

From wrobel at pardus.de  Sun Nov  9 08:44:36 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sun, 09 Nov 2008 08:44:36 +0100
Subject: SyncML: A technical perspective (Re: New kolab version ?)
In-Reply-To: <1226184785.6574.43.camel@merom>
References: <BLU122-W463B17EC5717372D9F5317A31C0@phx.gbl>
	<20081107164357.4862193dw4cmwdhc@webmail.pardus.de>
	<1226175253.9744.6.camel@black>
	<20081108134436.11005f366d6mwggs@webmail.pardus.de>
	<1226184785.6574.43.camel@merom>
Message-ID: <20081109084436.12228a16omq4vtuo@webmail.pardus.de>

Quoting Del <delonly at gmail.com>:

> On Sat, 2008-11-08 at 13:44 +0100, Gunnar Wrobel wrote:
>> A year ago I would have agreed with you. That was *before* I
>> implemented SyncML support for Kolab. SyncML has some severe problems.
>> Maybe not so much in the area of the protocol. But the fact that the
>> actual data exchange elements used within the protocol are being left
>> undefined means that any real world implementation will only ever work
>> with some devices. Not with all. There will always be a plethora of
>> device specific incompatibilities.
>
> Thanks for sharing your concerns and hindsight. I must admit that I
> haven't looked into the SyncML protocol, so I am not familiar with its
> shortcomings. I am grateful for any negative experiences you can share,
> e.g., handsets that work well or not.

In general each mobile family needs its own driver in the SyncML  
implementation. This driver will handle data conversion so that both  
server and client can understand each other. As mentioned SyncML  
itself is only a protocol wrapper and does not care about the data  
carrier it is used with.

Usually the data carrier are vCards or iCal objects. But both vCard  
and iCal have not been designed for synchronization. They are simple  
storage formats. If they are being used as synchronization messages  
you get some interesting side effects. As an example: If the client  
sends a vCard without an email entry does that mean that the attribute  
should be left unchanged or did the user delete the attribute on the  
client? There are workarounds possible but there are even more complex  
problems when you get to multi-value attributes.

As such design problems are being interpreted differently by each  
client vendor you can imagine how well it works in the real world. You  
can basically tell your users: "It might work, it might not. Just try  
:)". Not good.

>
>> I deliberately describe this in a negative way. Of course things will
>> often work and make users happy. But from a technical point of view
>> I'm pretty convinced that SyncML is not really going anywhere. Or let
>> me rephrase: I hope it is not going anywhere.
>
> I do see the need for an open standardised protocol, do you see any
> alternative? Is it feasible to extend SyncML specifications to mend the
> shortcomings?

vCard is currently trying to improve the format so that it can be used  
for synchronization. But that seems to be difficult.

Of course you can try to get better data formats for synchronization  
but I can guarantee you that standardization processes take a long time.

The other alternative is what I described: Use a storage format rather  
than synchronization. "Read/Write" is much easier to implement than  
"Read/Write Client - Synchronize Client/Server - Read/Write Server".

>
>> Kolab is doing one thing right: It defines a format that any client
>> should be able to read and write so that all other compliant clients
>> can also work with the stored data. This is a pretty robust approach
>> and syncing is not.
>
> Still, this requires everybody to adapt to Kolab's format, I do not
> think it is a good technical solution.

Huh? Why not? The format of the format (use of xml) maybe something  
open to discussion. But the general idea: using a simplified format  
that can be understood by each client is the right direction.

> Do you have any experience with
> Funambol's connectors? Seems they could potentially clear out some of
> the troubling points having connectors to most devices.

As far as I know their connectors are already quite good. But I don't  
have much experience with them.

>
>> If you want clean support for this on a mobile client it is actually
>> not too difficult: You add a Kolab Format compliant IMAP client on
>> your mobile device and you will be fine. No syncing, no problems.
>>
>> Will future clients support this? Yes, no question. IMAP access on a
>> mobile client is nothing fancy. And this is why I'm currently certain
>> that SyncML is just a temporary thing.
>
> A good point. However, is there any Kolab client underway that will run
> on most mobile devices? If not, what kind of time span are we in for?

It is just the most reasonable solution. There are no concrete  
schedules or anything. And as I mentioned initially I believe that  
SyncML will indeed be a temporary solution and people will use it. But  
in the long run I don't think it is a good solution.

Cheers,

Gunnar

>
> Cheers,
> Del
>
> _______________________________________________
> 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/20081109/a0dcd5a5/attachment.bin

From jaheme at gmx.de  Sun Nov  9 18:17:32 2008
From: jaheme at gmx.de (Jan - Hendrik Meyer)
Date: Sun, 09 Nov 2008 18:17:32 +0100
Subject: Mailbox does not exist
In-Reply-To: <20081109082938.542774wzzijjswco@webmail.pardus.de>
References: <4914AE91.1090600@gmx.de>
	<20081109082938.542774wzzijjswco@webmail.pardus.de>
Message-ID: <49171B2C.2030809@gmx.de>

Hi,

anbei ein LDIF Export des nicht funktionierenden Eintrages:

<begin>
version: 1

# LDIF-Export f?r: cn=Norbert Langemeyer,ou=People,dc=home
# Suchbereich: base
# Suchfilter: (objectClass=*)
# Anzahl der Listeneintr?ge: 1

# Eintrag 1: cn=Norbert Langemeyer,ou=People,dc=home
dn: cn=Norbert Langemeyer,ou=People,dc=home
objectClass: kolabInetOrgPerson
objectClass: shadowAccount
objectClass: posixAccount
objectClass: inetOrgPerson
objectClass: organizationalPerson
objectClass: person
objectClass: hordePerson
kolabInvitationPolicy: ACT_MANUAL
kolabHomeServer: 192.168.0.1
shadowWarning: 10
shadowInactive: 10
shadowMin: 1
shadowMax: 365
shadowLastChange: 14185
homeDirectory: /home/norbertlang
loginShell: /bin/bash
uid: norbertlang
cn: Norbert Langemeyer
uidNumber: 20000
gidNumber: 10002
userPassword: {SSHA}1ezeZyrbCjlrtVOwZS28FIZq28SvYfRi
sn: Langemeyer
givenName: Norbert
mail: norbert at home
hordePrefs: default_identity:MA==
hordePrefs: identities:YTowOnt9
hordePrefs: confirm_email:YTowOnt9
hordePrefs: id:
hordePrefs: fullname:
hordePrefs: from_addr:
hordePrefs: security_question:
hordePrefs: security_answer:
hordePrefs: alternate_email:
hordePrefs: language:
hordePrefs: timezone:
hordePrefs: twentyFour:
hordePrefs: date_format:JXg=
hordePrefs: first_week_day:MA==
hordePrefs: theme:Ymx1ZXdoaXRl
hordePrefs: categories:
hordePrefs: category_colors:
hordePrefs: summary_refresh_time:MzAw
hordePrefs: show_sidebar:MQ==
hordePrefs: sidebar_width:MTUw
hordePrefs: menu_view:Ym90aA==
hordePrefs: menu_refresh_time:MzAw
hordePrefs: do_maintenance:MQ==
hordePrefs: last_maintenance:MA==
hordePrefs: confirm_maintenance:MQ==
hordePrefs: initial_application:aG9yZGU=
hordePrefs: widget_accesskey:MQ==
hordePrefs: portal_layout:YToyOntpOjA7YToxOntpOjA7YTo0OntzOjM6ImFwcCI7czo1Oi
 Job3JkZSI7czo2OiJoZWlnaHQiO2k6MTtzOjU6IndpZHRoIjtpOjE7czo2OiJwYXJhbXMiO2E6M
 jp7czo0OiJ0eXBlIjtzOjQ6InRpbWUiO3M6NjoicGFyYW1zIjthOjI6e3M6MTM6Il9yZWZyZXNo
 X3RpbWUiO3M6MToiMCI7czo0OiJ0aW1lIjtzOjc6IjI0LWhvdXIiO319fX1pOjE7YToxOntpOjA
 7YTo0OntzOjM6ImFwcCI7czo1OiJob3JkZSI7czo2OiJoZWlnaHQiO2k6MTtzOjU6IndpZHRoIj
 tpOjE7czo2OiJwYXJhbXMiO2E6Mjp7czo0OiJ0eXBlIjtzOjc6ImFjY291bnQiO3M6NjoicGFyY
 W1zIjthOjA6e319fX19
hordePrefs: remote_summaries:YTowOnt9
hordePrefs: last_login:YToyOntzOjQ6InRpbWUiO2k6MTIyNTY0MjczMztzOjQ6Imhvc3QiO
 3M6MTA6InBjMDA1LmhvbWUiO30=
hordePrefs: show_last_login:MQ==
hordePrefs: editor_plugins:YToyOntpOjA7czo4OiJMaXN0VHlwZSI7aToxO3M6MTI6IkNoY
 XJhY3Rlck1hcCI7fQ==
</end>

I hope this helps to find a solution.

Thanks
Jan-Hendrik MEyer

Gunnar Wrobel schrieb:
> Quoting Jan - Hendrik Meyer <jaheme at gmx.de>:
>
>>  Hello,
>>
>> after I installed so SuSe integration package sucessfully, I've started
>> to integrate Linux authentification with ldap. I used the LDAP Account
>> Manager to manage the account. I created a account with the unix schemas
>> and the kolab schemas for testing.
>> I can login the xserver and a mailbox has also been created.
>>
>> But there is one error:
>>
>> lmtp[29919]: verify_user(home!user.norbertlang) failed: Mailbox does 
>> not exist
>>
>> I think the cause could be that the user name need to be different to 
>> the username,
>> if I use the kolab and unix schema
>> (because the username doesn't support the @)
>
> I'm not 100% certain I understand how you merge the two schemas or how 
> a user account looks in your case. Maybe you could attach an LDIF output.
>
> In any case a Kolab user should always have an email address as 
> primary identifier. You may use the uid for any additional IDs and I 
> think you should be able to use this one for uinx login.
>
> Cheers,
>
> Gunnar
>
>>
>> Are there any solutions?
>>
>> Thanks
>>
>> Jan-Hendrik
>>
>> _______________________________________________
>> 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 netwarrior863 at gmail.com  Mon Nov 10 17:04:05 2008
From: netwarrior863 at gmail.com (Net Warrior)
Date: Mon, 10 Nov 2008 14:04:05 -0200
Subject: Installation issue
In-Reply-To: <20081107165141.19802lg4d1r66omc@webmail.pardus.de>
References: <f66a6bc10811050938t4eb99654xcd4a4aeaf8d4c19c@mail.gmail.com>
	<20081107165141.19802lg4d1r66omc@webmail.pardus.de>
Message-ID: <f66a6bc10811100804g3d240b86md7b211b623519fc@mail.gmail.com>

Problem SOLVED , hope this helps somesone else.

Due to constant permission denied errors, instead of root  I switched to
kolab users and performed the installation without any problems, now I'm in
the configuration process and everything seems to work properly.

Thanks for your time and support
Greets.



2008/11/7, Gunnar Wrobel <wrobel at pardus.de>:
>
>
> Quoting Net Warrior <netwarrior863 at gmail.com>:
>
> Hi here guy, during the installation process I've get this error, Am I
>> missing something?
>> Do I need to install an extra package? is this a bug?
>>
>> Generating 00INDEX.rdf for source distribution ...
>> openpkg:ERROR: No such command "index" found in command
>> path
>> openpkg:ERROR: (/kolab/libexec/openpkg).
>> openpkg:ERROR: Set ${OPENPKG_TOOLS_CMDPATH} appropriately.
>> openpkg:ERROR: Run "/kolab/bin/openpkg --help" for list
>> of valid commands.
>>
>
> Looks like you used the special "-X" flag with the install-kolab.sh script.
> This is only meant for special circumstances and you might have used it in
> an incorrect context. Can you detail why you used that flag and provide the
> complete command you ran?
>
> Cheers,
>
> Gunnar
>
>
>> There is no index  file under libexec directory.
>> This is version 2.2.0 installing from source under SLES10
>>
>> Thanks in advance.
>>
>
> --
> ____ 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081110/45aace00/attachment.html

From Roessler at FuH-E.de  Tue Nov 11 13:22:25 2008
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Tue, 11 Nov 2008 13:22:25 +0100
Subject: slave-rejects und SASL-log (ldap_search_st() failed: Can't contact
	LDAP server)
Message-ID: <49197901.6090106@FuH-E.de>

Guten Tag allerseits,

ich habe derletzt nun einen Kolab-Slave-Server aufgesetzt. Die ganze 
Sache funktioniert an sich sehr gut, nur gibt es da ein, zwei Dinge, die 
mich etwas irritieren.

Das erste ist folgendes: Wenn ich im Kolab-Master etwas ver?ndere (hier 
zB den Benutzer "Testa Testb", dann erhalte ich folgende reject-Meldung 
  in der reject-Logdatei des Masters (in: 
/kolab/var/openldap/openldap-slurp/replica/kolab-slave\:636.rej):

| ERROR: No such object
| replica: kolab-slave.fuhintern.de:636
| time: 1226391794.1
| dn: cn=Testa Testb,dc=kolab,dc=testintern,dc=de
| changetype: modrdn
| newrdn: cn=Testa Testc
| deleteoldrdn: 1

...allerdings wird das betreffende Objekt auf dem Slave ge?ndert, wie es 
sein soll. Wie gesagt, das irritiert mich sehr.

Meine erste Vermutung war, da? das etwa mit der SASL-Authentifizierung 
zusammenh?ngen k?nne, (Ausschnitt aus /kolab/var/sasl/log/saslauthd.log):

| Nov 11 10:20:02 kolab <error> saslauthd[6635]: user ldap_search_st()
| failed: Can't contact LDAP server
| Nov 11 10:20:02 kolab <info> saslauthd[6635]: Retrying authentication
| Nov 11 10:30:02 kolab <error> saslauthd[6625]: user ldap_search_st()
| failed: Can't contact LDAP server
| Nov 11 10:30:02 kolab <info> saslauthd[6625]: Retrying authentication
| Nov 11 10:40:02 kolab <error> saslauthd[6635]: user ldap_search_st()
| failed: Can't contact LDAP server
| Nov 11 10:40:02 kolab <info> saslauthd[6635]: Retrying authentication
| Nov 11 10:50:02 kolab <error> saslauthd[6625]: user ldap_search_st()
| failed: Can't contact LDAP server
| Nov 11 10:50:02 kolab <info> saslauthd[6625]: Retrying authentication
(usw. usf. etc.)

...so da? ich, um eventuelle Folgefehler auszuschlie?en, erst dieses 
Problem l?sen m?chte. Allerdings fiel mir dabei auf, da? diese Meldungen 
(wahrscheinlich) schon weit vor Installation und Einbindung des 
Kolab-Slave-Servers auftraten, was mich dann wiederum irritiert.

Von daher w?rde ich gern folgendes wissen: Kann mir jemand in beiden 
Zusammenh?ngen einen Tip geben?

Speziell zum zweiten Problem (SASL) war da einiges im Netz zu finden, 
allerdings nur f?r deutlich ?ltere Kolabs. Weitere Angaben liefer' ich 
nat?rlich gern nach!

Viele Gr??e,
Christian


From pdf at yugm.org  Tue Nov 11 18:53:29 2008
From: pdf at yugm.org (Paul Douglas Franklin)
Date: Tue, 11 Nov 2008 09:53:29 -0800
Subject: Privileged networks
Message-ID: <4919C699.3070201@yugm.org>

One thing I appreciate about Kolab is the privileged networks such that 
the bad guys cannot use my SMTP server to send out messages.
I have just come across a problem in the settings for privileged 
networks.  I have one individual who is wanting to travel around with a 
laptop, and I thought it appropriate to set him up with a VPN to access 
his email.  (Horde is still in my future.)
When I attempt to add his address, it allows him to send e-mails, but 
then no one else can.  All I thought I did was to add his to the end of 
the list as 10.8.2.10/24.
Given that I want the following to be privileged, what would be the 
appropriate list for the privileged networks field?
127.0.0.0
192.168.*.*
10.8.2.10
--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  Tue Nov 11 21:14:05 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Tue, 11 Nov 2008 21:14:05 +0100
Subject: Privileged networks
In-Reply-To: <4919C699.3070201@yugm.org>
References: <4919C699.3070201@yugm.org>
Message-ID: <71fe4e760811111214o5b8cd242rc1ac4ea21cf9d8d6@mail.gmail.com>

On Tue, Nov 11, 2008 at 6:53 PM, Paul Douglas Franklin <pdf at yugm.org> wrote:
> One thing I appreciate about Kolab is the privileged networks such that
> the bad guys cannot use my SMTP server to send out messages.
> I have just come across a problem in the settings for privileged
> networks.  I have one individual who is wanting to travel around with a
> laptop, and I thought it appropriate to set him up with a VPN to access
> his email.  (Horde is still in my future.)
> When I attempt to add his address, it allows him to send e-mails, but
> then no one else can.  All I thought I did was to add his to the end of
> the list as 10.8.2.10/24.
> Given that I want the following to be privileged, what would be the
> appropriate list for the privileged networks field?
> 127.0.0.0
> 192.168.*.*
> 10.8.2.10
> --Paul

try this :

127.0.0.0/8, 192.168.0.0/16, 10.8.2.10


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



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


From LHendricks at austinent.com  Tue Nov 11 22:08:24 2008
From: LHendricks at austinent.com (Lucas Hendricks)
Date: Tue, 11 Nov 2008 15:08:24 -0600
Subject: Privileged networks
Message-ID: <7907AE10BB50DD4F840E76527D27EF1902104F3E@entmail.domain.austinent.com>

If that does not take try:
 127.0.0.0/8, 192.168.0.0/16, 10.8.2.10/32

The /y part is for the subnet mask counting from left to right so you would
use /32 for a full mask representing 1 address.  Kolab should find of those
2 formats valid to represent the single address.

Lucas

-----Original Message-----
From: Alain Spineux [mailto:aspineux at gmail.com] 
Sent: Tuesday, November 11, 2008 2:14 PM
To: Paul Douglas Franklin
Cc: Kolab Users
Subject: Re: Privileged networks

On Tue, Nov 11, 2008 at 6:53 PM, Paul Douglas Franklin <pdf at yugm.org> wrote:
> One thing I appreciate about Kolab is the privileged networks such that
> the bad guys cannot use my SMTP server to send out messages.
> I have just come across a problem in the settings for privileged
> networks.  I have one individual who is wanting to travel around with a
> laptop, and I thought it appropriate to set him up with a VPN to access
> his email.  (Horde is still in my future.)
> When I attempt to add his address, it allows him to send e-mails, but
> then no one else can.  All I thought I did was to add his to the end of
> the list as 10.8.2.10/24.
> Given that I want the following to be privileged, what would be the
> appropriate list for the privileged networks field?
> 127.0.0.0
> 192.168.*.*
> 10.8.2.10
> --Paul

try this :

127.0.0.0/8, 192.168.0.0/16, 10.8.2.10


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

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


From pdf at yugm.org  Tue Nov 11 22:42:26 2008
From: pdf at yugm.org (Paul Douglas Franklin)
Date: Tue, 11 Nov 2008 13:42:26 -0800
Subject: Privileged networks
In-Reply-To: <7907AE10BB50DD4F840E76527D27EF1902104F3E@entmail.domain.austinent.com>
References: <7907AE10BB50DD4F840E76527D27EF1902104F3E@entmail.domain.austinent.com>
Message-ID: <4919FC42.5090605@yugm.org>

Thank you, Alain and Lucas.  I just received confirmation from the user 
that the single address without the /32 does work.
--Paul

Lucas Hendricks wrote:
> If that does not take try:
>  127.0.0.0/8, 192.168.0.0/16, 10.8.2.10/32
>
> The /y part is for the subnet mask counting from left to right so you would
> use /32 for a full mask representing 1 address.  Kolab should find of those
> 2 formats valid to represent the single address.
>
> Lucas
>
>   

-- 
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 devgioiatech at gmail.com  Wed Nov 12 10:32:30 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Wed, 12 Nov 2008 10:32:30 +0100
Subject: external web client
In-Reply-To: <d53357b70811040345t121db963yd1b6f1df026ce416@mail.gmail.com>
References: <d53357b70810300437r5fefb324vc1bb79c8ee17cd6a@mail.gmail.com>
	<28713.200.47.24.7.1225369602.squirrel@webmail.xtech.com.ar>
	<d53357b70810300534q77110ecfjc713d64cca750d95@mail.gmail.com>
	<50233.200.47.24.7.1225371471.squirrel@webmail.xtech.com.ar>
	<d53357b70810300831u52f532e7naea1a90c616bd39d@mail.gmail.com>
	<20081031065053.41847cr9xzxhie0w@webmail.pardus.de>
	<d53357b70810310324od1929c8p7374d6b2774896c2@mail.gmail.com>
	<d53357b70810310356j10fe628dt11c2059af6532b96@mail.gmail.com>
	<20081103053223.166558e9ckjxuh44@webmail.pardus.de>
	<d53357b70811040345t121db963yd1b6f1df026ce416@mail.gmail.com>
Message-ID: <d53357b70811120132y1da5654ay34507a68fc7f0012@mail.gmail.com>

Hi,
i'm come back :D

So, in apache-error.log there is this error:

[Wed Nov 12 00:36:02 2008] [error] [client 10.30.11.64] Directory index
forbidden by Options directive: /kolab/var/kolab/www/

but i haven't make any change in apache... it's the default installation...

Any idea?


2008/11/4 Antonio Straziota <devgioiatech at gmail.com>

> Sorry, but in this days i'm not in office...
>
> i'll give you this info when i come back...
>
> thanks for the reply.
>
> 2008/11/3 Gunnar Wrobel <wrobel at pardus.de>
>
>
>> Quoting Antonio Straziota <devgioiatech at gmail.com>:
>>
>>  As suggested in the wiki, I also try to remove nss_db library (my
>>> system is CENTOS) but nothing changes
>>>
>>
>> What do you see in the log files within /kolab/var/apache/log/* when you
>> try to log in?
>>
>> Cheers,
>>
>> Gunnar
>>
>>
>>> 2008/10/31 Antonio Straziota
>>>
>> dir="ltr"><devgioiatech at gmail.com[1]>
>>
>>>  0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">mmmh...
>>> i've a problem autentication by local webmail goes fine... but when
>>> i try to login in horde by external webmail...i can't log in
>>>
>> without
>>
>>> any error message...
>>> any idea...
>>>
>>> any idea?
>>>
>>>
>>>  10/31 Gunnar Wrobel  dir="ltr"><
>>>
>> href="mailto:wrobel at pardus.de">wrobel at pardus.de>
>>
>>>  0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">   Quoting Antonio
>>> Straziota <
>>>
>> href="mailto:devgioiatech at gmail.com">devgioiatech at gmail.com>:
>>
>>>  0pt 0.8ex; padding-left: 1ex;" class="gmail_quote"> Ok,
>>>
>>> i've installed webmail through a fresh kolab slave installation.
>>>
>>
>>  This is currently the best option. I need to fix the wiki page :)
>> We decided that it will be safer for users to install a complete
>> slave rather than installing Horde on an apache/mod_php combo without
>> know configuration.
>>
>> only a question... can i stop all other kolab service and keep
>> online only Apache?
>>
>>  I think that should be possible.
>>
>> Cheers,
>>
>> Gunnar
>>
>> 2008/10/30 Alejandro Bednarik
>>   dir="ltr"><alejandro at xtech.com.ar[1]>
>>  0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
>>  I tried this also, it works if you also copy another directory
>> where live
>> many php modules, i can't remember the exact path sorry. Kolab php
>> have
>> patches, maybe is a good idea to compile and use this as source.
>> The
>> performance using this method was not what we expect, but probably
>> was
>> the network where we set this servers...
>>  Cheers!
>>  Antonio Straziota wrote:
>>
>>> Hi Alejandro,
>>> thanks for the reply...
>>>
>>> i'll try this solution.
>>>
>>> However, i think that installing all dependence and copying
>>>
>> the
>>
>>> /kolab/var/kolab/www/horde in the web root of the web server
>>>
>> should be
>>
>>> work...
>>> After all horde is simply a web application that needs to be
>>>
>> configured
>>
>>>
>>> Anyone can help for this?
>>>
>>> Thanks.
>>>
>>> 2008/10/30 Alejandro Bednarik
>>>
>>  <alejandro at xtech.com.ar[2]>
>>
>>>
>>>
>>>>  Hi Antonio. I tried the same thing a couple of weeks ago,
>>>>
>>> and if i am
>>
>>> not
>>>> wrong that way to set another Horde is deprecated. You can
>>>>
>>> try doing a
>>
>>> normal kolab installation, but choosing Slave during the
>>>>
>>> bootstrap
>>
>>> process.
>>>>  For sure, someone who knows this better than me can help
>>>>
>>> you with more
>>
>>> info.
>>>>
>>>> Cheers!
>>>>
>>>>
>>>> Antonio Straziota wrote:
>>>> > ehm,
>>>> > hi again...
>>>> >
>>>> > i tryed to launch the script but instead of the
>>>>
>>> folder *horde*, the
>>
>>> > content
>>>> > of the web root is :
>>>> >
>>>> >
>>>> > [root at srv html]# ll
>>>> > -rw-r--r--  1 root root    6021 Oct 30 12:39
>>>>
>>> external-horde.sh
>>
>>> > -rw-r--r--  1 root root    6282 Oct 30 12:41
>>>> >
>>>>
>>>>
>>
>>
>> HK-GW-framework_3.2_ALPHA-Fix_Prefs_for_Ingo.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>>  >> > -rw-r--r--  1 root root    6883 Oct 30 12:41
>>
>>> >
>>>>
>>>>
>>
>>
>> HK-GW-kronolith_2.2_RC1-Fbview_relevance.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>>  >> > -rw-r--r--  1 root root    6901 Oct 30 12:41
>>
>>> >
>>>>
>>>>
>>
>>
>> HK-GW-kronolith_2.2_RC1-Fbview_xfb_access.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>>  >> > -rw-r--r--  1 root root    6193 Oct 30 12:41
>>
>>> >
>>>>
>>>>
>>
>>
>> HK-GW-turba_2.2-Fix_editing_contacts.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>>  >> > -rw-r--r--  1 root root    6177 Oct 30 12:41
>>
>>> >
>>>>
>>>>
>>
>>
>> HK-GW-turba_2.2-Fix_share_id_change.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>>  >> > -rw-r--r--  1 root root    6161 Oct 30 12:41
>>
>>> >
>>>>
>>>>
>>
>>
>> HK-GW-turba_2.2-Ldap_read_only_fix.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>>  >> > -rw-r--r--  1 root root    6967 Oct 30 12:41
>>
>>> >
>>>>
>>>>
>>
>>
>> HK-JS-kronolith_2.2_RC1-Fix_library_import.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>>  >> > -rw-r--r--  1 root root    6859 Oct 30 12:41
>>
>>> >
>>>>
>>>>
>>
>>
>> HK-JS-nag_2.2_RC1-Fix_library_import.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>>  >> > -rw-r--r--  1 root root    7038 Oct 30 12:41
>>
>>> >
>>>>
>>>>
>>
>>
>> HK-SB-kronolith_2.2_RC1-Fbview_extra_params.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>>  >> > -rw-r--r--  1 root root    7074 Oct 30 12:41
>>
>>> >
>>>>
>>>>
>>
>>
>> HK-SB-kronolith_2.2_RC1-Fbview_save_attendees.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
>>      >> >
>>
>>> >
>>>> > Any idea?
>>>> >
>>>> > 2008/10/30 Antonio Straziota
>>>>
>>>  <devgioiatech at gmail.com[3]>
>>
>>> >
>>>> >> hi all,
>>>> >> i'm trying to install horde on a external web
>>>>
>>> server.
>>
>>> >>
>>>> >> i'm following the tutorial at
>>>> >>
>>>>
>>>
>> href="http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde">
>> http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde.
>>
>>  >> >>
>>
>>> >> now i'm getting the script external-horde.sh with
>>>> >>
>>>> >> wget
>>>> >>
>>>>
>>>>
>> href="
>> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/*checkout*/server/horde/Attic/external-horde.sh?rev=HEAD&search=None&hideattic=1&content-type=text/x-sh
>> ">
>> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/*checkout*/server/horde/Attic/external-horde.sh?rev=HEAD&search=None&hideattic=1&content-type=text/x-sh
>>  >> >>
>>
>>> >> because link in the tutorial doesn't work with
>>>>
>>> wget
>>
>>> >>
>>>> >> Is this script right for the kolab2.2.0?
>>>> >>
>>>> >> Thanks
>>>> >>
>>>> >>
>>>> > _______________________________________________
>>>> > Kolab-users mailing list
>>>>
>>>  >> > Kolab-users at kolab.org[4]
>>
>>> >
>>>>
>>>
>> href="https://kolab.org/mailman/listinfo/kolab-users">
>> https://kolab.org/mailman/listinfo/kolab-users
>>  >> >
>>
>>>
>>>>
>>>> --
>>>>  Alejandro Bednarik
>>>>  XTech - Soluciones Linux para Empresas
>>>>  (011) 5219-0678
>>>>
>>>  >>  alejandro at xtech.com.ar[5]
>>
>>>
>>>>
>>>> _______________________________________________
>>>> Kolab-users mailing list
>>>> Kolab-users at kolab.org[6]
>>>>
>>>>
>> href="https://kolab.org/mailman/listinfo/kolab-users">
>> https://kolab.org/mailman/listinfo/kolab-users
>>  >>
>>
>>>
>>>    --
>>  Alejandro Bednarik
>>  XTech - Soluciones Linux para Empresas
>>  (011) 5219-0678
>>  alejandro at xtech.com.ar[7]
>>
>> --
>> ______ http://kdab.com _______________ http://kolab-konsortium.com _
>>
>> p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
>>
>> ____ http://www.pardus.de _________________ http://gunnarwrobel.de _
>> E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
>> Tel.   : +49 700 6245 0000                          Bundesstrasse 29
>> Fax    : +49 721 1513 52322                          D-20146 Hamburg
>> --------------------------------------------------------------------
>>  >> Mail at ease - Rent a kolab groupware server at p at rdus <<
>> --------------------------------------------------------------------
>>
>> Links:
>> ------
>> [1] mailto:alejandro at xtech.com.ar
>> [2] mailto:alejandro at xtech.com.ar
>> [3] mailto:devgioiatech at gmail.com
>> [4] mailto:Kolab-users at kolab.org
>> [5] mailto:alejandro at xtech.com.ar
>> [6] mailto:Kolab-users at kolab.org
>> [7] mailto:alejandro at xtech.com.ar
>>
>> ----------------------------------------------------------------
>> 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
>>
>> --
>> ______ http://kdab.com _______________ http://kolab-konsortium.com _
>>
>> p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
>>
>> ____ http://www.pardus.de _________________ http://gunnarwrobel.de _
>> E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
>> Tel.   : +49 700 6245 0000                          Bundesstrasse 29
>> Fax    : +49 721 1513 52322                          D-20146 Hamburg
>> --------------------------------------------------------------------
>>   >> Mail at ease - Rent a kolab groupware server at p at rdus <<
>> --------------------------------------------------------------------
>>
>> Links:
>> ------
>> [1] mailto:devgioiatech at gmail.com
>>
>>
>>
>> ----------------------------------------------------------------
>> 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
>>
>>
>
-------------- parte successiva --------------
Un allegato HTML ? stato rimosso...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081112/110f6642/attachment-0001.html

From wrobel at pardus.de  Thu Nov 13 10:45:53 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Thu, 13 Nov 2008 10:45:53 +0100
Subject: external web client
In-Reply-To: <d53357b70811120132y1da5654ay34507a68fc7f0012@mail.gmail.com>
References: <d53357b70810300437r5fefb324vc1bb79c8ee17cd6a@mail.gmail.com>
	<28713.200.47.24.7.1225369602.squirrel@webmail.xtech.com.ar>
	<d53357b70810300534q77110ecfjc713d64cca750d95@mail.gmail.com>
	<50233.200.47.24.7.1225371471.squirrel@webmail.xtech.com.ar>
	<d53357b70810300831u52f532e7naea1a90c616bd39d@mail.gmail.com>
	<20081031065053.41847cr9xzxhie0w@webmail.pardus.de>
	<d53357b70810310324od1929c8p7374d6b2774896c2@mail.gmail.com>
	<d53357b70810310356j10fe628dt11c2059af6532b96@mail.gmail.com>
	<20081103053223.166558e9ckjxuh44@webmail.pardus.de>
	<d53357b70811040345t121db963yd1b6f1df026ce416@mail.gmail.com>
	<d53357b70811120132y1da5654ay34507a68fc7f0012@mail.gmail.com>
Message-ID: <20081113104553.18735zggnh2r9uw4@webmail.pardus.de>


Quoting Antonio Straziota <devgioiatech at gmail.com>:

> Hi,
> i'm come back :D
>
> So, in apache-error.log there is this error:
>
> [Wed Nov 12 00:36:02 2008] [error] [client 10.30.11.64[1]]
> Directory index forbidden by Options directive:
> /kolab/var/kolab/www/
>  but i haven't make any change in apache... it's the default
> installation...
>
> Any idea?

Which URL do you try to access?

By the way I kind of lost the thread here. It is better to avoid top  
posting and place your replies below the stuff you want to comment.  
That way the discussion thread remains understandable. Using HTML  
mails also does not help very much. Try to use plain text on public  
mailing lists :)

Cheers,

Gunnar

>
>
> 2008/11/4 Antonio Straziota
dir="ltr"><devgioiatech at gmail.com[2]>
>  0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">Sorry, but
in
> this days i'm not in office...
>
> i'll give you this info when i come back...
>  thanks for the reply.
>
> 2008/11/3 Gunnar Wrobel  dir="ltr"><
href="mailto:wrobel at pardus.de">wrobel at pardus.de>
>    0pt 0.8ex; padding-left: 1ex;" class="gmail_quote"> Quoting  
> Antonio Straziota <
href="mailto:devgioiatech at gmail.com">devgioiatech at gmail.com>:
>      margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"
> class="gmail_quote"> As suggested in the wiki, I also try to
> remove nss_db library (my
> system is CENTOS) but nothing changes

  What do you see in the log files within /kolab/var/apache/log/* when
you try to log in?

Cheers,

Gunnar

2008/10/31 Antonio Straziota
    dir="ltr"><devgioiatech at gmail.com[1]>
   0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">mmmh...
i've a problem autentication by local webmail goes fine... but when
i try to login in horde by external webmail...i can't log in
    without
   any error message...
any idea...

any idea?

   10/31 Gunnar Wrobel  dir="ltr"><
  href="mailto:wrobel at pardus.de">wrobel at pardus.de>
   0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">   Quoting
Antonio Straziota <
   href="mailto:devgioiatech at gmail.com">devgioiatech at gmail.com>:
   0pt 0.8ex; padding-left: 1ex;" class="gmail_quote"> Ok,
i've installed webmail through a fresh kolab slave installation.

  This is currently the best option. I need to fix the wiki page :)
We decided that it will be safer for users to install a complete
slave rather than installing Horde on an apache/mod_php combo without
know configuration.

only a question... can i stop all other kolab service and keep
online only Apache?

  I think that should be possible.

Cheers,

Gunnar

2008/10/30 Alejandro Bednarik
   dir="ltr"><alejandro at xtech.com.ar[1]>
  0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
  I tried this also, it works if you also copy another directory
where live
many php modules, i can't remember the exact path sorry. Kolab php
have
patches, maybe is a good idea to compile and use this as source.
The
performance using this method was not what we expect, but probably
was
the network where we set this servers...
  Cheers!
  Antonio Straziota wrote:
  Hi Alejandro,
thanks for the reply...

i'll try this solution.

However, i think that installing all dependence and copying
   the
  /kolab/var/kolab/www/horde in the web root of the web server
   should be
  work...
After all horde is simply a web application that needs to be
   configured

Anyone can help for this?

Thanks.

2008/10/30 Alejandro Bednarik
    <alejandro at xtech.com.ar[2]>

  Hi Antonio. I tried the same thing a couple of weeks ago,
    and if i am
  not
wrong that way to set another Horde is deprecated. You can
    try doing a
  normal kolab installation, but choosing Slave during the
    bootstrap
  process.
  For sure, someone who knows this better than me can help
    you with more
  info.

Cheers!

Antonio Straziota wrote:
> ehm,
> hi again...
>
> i tryed to launch the script but instead of the
    folder *horde*, the
  > content
> of the web root is :
>
>
> [root at srv html]# ll
> -rw-r--r--  1 root root    6021 Oct 30 12:39
    external-horde.sh
  > -rw-r--r--  1 root root    6282 Oct 30 12:41
>

HK-GW-framework_3.2_ALPHA-Fix_Prefs_for_Ingo.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    6883 Oct 30 12:41
  >

HK-GW-kronolith_2.2_RC1-Fbview_relevance.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    6901 Oct 30 12:41
  >

HK-GW-kronolith_2.2_RC1-Fbview_xfb_access.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    6193 Oct 30 12:41
  >

HK-GW-turba_2.2-Fix_editing_contacts.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    6177 Oct 30 12:41
  >

HK-GW-turba_2.2-Fix_share_id_change.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    6161 Oct 30 12:41
  >

HK-GW-turba_2.2-Ldap_read_only_fix.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    6967 Oct 30 12:41
  >

HK-JS-kronolith_2.2_RC1-Fix_library_import.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    6859 Oct 30 12:41
  >

HK-JS-nag_2.2_RC1-Fix_library_import.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    7038 Oct 30 12:41
  >

HK-SB-kronolith_2.2_RC1-Fbview_extra_params.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
  >> > -rw-r--r--  1 root root    7074 Oct 30 12:41
  >

HK-SB-kronolith_2.2_RC1-Fbview_save_attendees.patch?logsort=date&sortby=file&hideattic=1&search=None&hidecvsroot=1&diff_format=h
      >> >
  >
> Any idea?
>
> 2008/10/30 Antonio Straziota
     <devgioiatech at gmail.com[3]>
  >
>> hi all,
>> i'm trying to install horde on a external web
    server.
  >>
>> i'm following the tutorial at
>>

href="http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde">http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde.

  >> >>
  >> now i'm getting the script external-horde.sh with
>>
>> wget
>>

href="http://kolab.org/cgi-bin/viewcvs-kolab.cgi/*checkout*/server/horde/Attic/external-horde.sh?rev=HEAD&search=None&hideattic=1&content-type=text/x-sh">http://kolab.org/cgi-bin/viewcvs-kolab.cgi/*checkout*/server/horde/Attic/external-horde.sh?rev=HEAD&search=None&hideattic=1&content-type=text/x-sh
  >> >>
  >> because link in the tutorial doesn't work with
    wget
  >>
>> Is this script right for the kolab2.2.0?
>>
>> Thanks
>>
>>
> _______________________________________________
> Kolab-users mailing list
     >> > Kolab-users at kolab.org[4]
  >

href="https://kolab.org/mailman/listinfo/kolab-users">https://kolab.org/mailman/listinfo/kolab-users
  >> >

--
  Alejandro Bednarik
  XTech - Soluciones Linux para Empresas
  (011) 5219-0678
     >>  alejandro at xtech.com.ar[5]

_______________________________________________
Kolab-users mailing list
  Kolab-users at kolab.org[6]

href="https://kolab.org/mailman/listinfo/kolab-users">https://kolab.org/mailman/listinfo/kolab-users
  >>

     --
  Alejandro Bednarik
  XTech - Soluciones Linux para Empresas
  (011) 5219-0678
  alejandro at xtech.com.ar[7]

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

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

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

Links:
------
[1] mailto:alejandro at xtech.com.ar
[2] mailto:alejandro at xtech.com.ar
[3] mailto:devgioiatech at gmail.com
[4] mailto:Kolab-users at kolab.org
[5] mailto:alejandro at xtech.com.ar
[6] mailto:Kolab-users at kolab.org
[7] mailto:alejandro at xtech.com.ar

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

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

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

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

Links:
------
   [1] mailto:devgioiatech at gmail.com

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

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

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

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

Links:
------
[1] http://10.30.11.64
[2] mailto:devgioiatech at gmail.com


----------------------------------------------------------------
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/20081113/50617dad/attachment.bin

From devgioiatech at gmail.com  Thu Nov 13 13:20:46 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Thu, 13 Nov 2008 13:20:46 +0100
Subject: external web client
In-Reply-To: <20081113104553.18735zggnh2r9uw4@webmail.pardus.de>
References: <d53357b70810300437r5fefb324vc1bb79c8ee17cd6a@mail.gmail.com>
	<50233.200.47.24.7.1225371471.squirrel@webmail.xtech.com.ar>
	<d53357b70810300831u52f532e7naea1a90c616bd39d@mail.gmail.com>
	<20081031065053.41847cr9xzxhie0w@webmail.pardus.de>
	<d53357b70810310324od1929c8p7374d6b2774896c2@mail.gmail.com>
	<d53357b70810310356j10fe628dt11c2059af6532b96@mail.gmail.com>
	<20081103053223.166558e9ckjxuh44@webmail.pardus.de>
	<d53357b70811040345t121db963yd1b6f1df026ce416@mail.gmail.com>
	<d53357b70811120132y1da5654ay34507a68fc7f0012@mail.gmail.com>
	<20081113104553.18735zggnh2r9uw4@webmail.pardus.de>
Message-ID: <d53357b70811130420l4565994dn337aa69d98012aea@mail.gmail.com>

I've installed a slave kolab for webmail use... but when i try to
login in horde by external webmail...i can't log in  without any error
message...

kolab master:
hostname: srv.demo.tst

kolab slave:
webmail.demo.tst

only horde fails to log me in...

i put ip and hostname of kolab master in /etc/hosts of kolab slave.
but nothing changes.

As you suggest, i took a look at at apache log dir...
and  i found in in apache-error.log the error:

[Wed Nov 12 00:36:02 2008] [error] [client 10.30.11.64[1]] Directory
index forbidden by Options directive: /kolab/var/kolab/www/



PS: I'm sorry for html mail...i don't realize that :P


From Roessler at FuH-E.de  Thu Nov 13 15:21:03 2008
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Thu, 13 Nov 2008 15:21:03 +0100
Subject: slave-rejects und SASL-log (ldap_search_st() failed: Can't contact
	LDAP server)
Message-ID: <491C37CF.9010903@FuH-E.de>

Hallo everybody,

well, I have sent the german version to the english list - sorry, this 
should have gone to the german list, of course. So now again in english...

I installed a Kolab slave server, some days ago. It works nicely, but 
there are some things irritating me.

First: If I change a normal entry on the Kolab master (here, for example 
the user "Testa Testb" I got a notice in the reject logfile of the 
master (at /kolab/var/openldap/openldap-slurp/replica/kolab-slave\:636.rej):

| ERROR: No such object
| replica: kolab-slave.fuhintern.de:636
| time: 1226391794.1
| dn: cn=Testa Testb,dc=kolab,dc=testintern,dc=de
| changetype: modrdn
| newrdn: cn=Testa Testc
| deleteoldrdn: 1

..but the object will be correctly replicated to the slave, as it should 
be. As said, that's irritating.

After noticing sone SASL entries in the SASL log file I guessed it could 
perhaps have something to do with SASL authentification (snippet from 
/kolab/var/sasl/log/saslauthd.log):

| Nov 11 10:20:02 kolab <error> saslauthd[6635]: user ldap_search_st()
| failed: Can't contact LDAP server
| Nov 11 10:20:02 kolab <info> saslauthd[6635]: Retrying authentication
| Nov 11 10:30:02 kolab <error> saslauthd[6625]: user ldap_search_st()
| failed: Can't contact LDAP server
| Nov 11 10:30:02 kolab <info> saslauthd[6625]: Retrying authentication
| Nov 11 10:40:02 kolab <error> saslauthd[6635]: user ldap_search_st()
| failed: Can't contact LDAP server
| Nov 11 10:40:02 kolab <info> saslauthd[6635]: Retrying authentication
| Nov 11 10:50:02 kolab <error> saslauthd[6625]: user ldap_search_st()
| failed: Can't contact LDAP server
| Nov 11 10:50:02 kolab <info> saslauthd[6625]: Retrying authentication
(usw. usf. etc.)

so I would like to solve this problem first to make sure the replication 
problem above is not a following error of this. But I noticed that 
perhaps these messages also happened before the setup of the slave 
server, which irritates me also.

So, please, can anyone give me a hint, perhaps? If more information is 
needed I would gladly provide more.

Best regards,
Christian


From carsten at cburghardt.com  Thu Nov 13 21:29:05 2008
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Thu, 13 Nov 2008 21:29:05 +0100
Subject: Mail not rejected
Message-ID: <200811132129.05713.carsten@cburghardt.com>

Hi list,

I am a little confused about the postfix behaviour of my kolab 2.2 
installation. I added several domains in the kolab web frontend. The default 
distribution lists are then created for postmaster, abuse and so on. 
I have added myself to the adressbook and added some aliases like "cb" to the 
list. When I send an email to an invalid/unknown username like 
nonsense@<mydomain> then the email is not rejected by postfix but it passes 
through to postmaster. Where does that catch-all entry come from and how can 
I get rid of it? I have no entries in my virtual table so that must be a 
result of the ldap query I assume.
SuSE 10.3 with their Kolab packages.


Thanks

Carsten


From viljoenjp at workforce.co.za  Fri Nov 14 13:09:50 2008
From: viljoenjp at workforce.co.za (JP Viljoen)
Date: Fri, 14 Nov 2008 14:09:50 +0200
Subject: Mail duplication
Message-ID: <200811141409.50773.viljoenjp@workforce.co.za>

Hi all

I've had a few users complaining that they get mail multiple times (2 or more, 
average up to 40) when sent from certain people. All the senders in the 
building are generally using Outlook. Just want to hear if anyone on the 
lists has had similar issues, and/or possibly a resolution for the issue. I 
by nature can't think that it's the pieces of software the mailserver is 
built on (the Kolab stack), but since I know the previous administrators of 
this setup weren't very .. future-minded .. I wouldn't rule out the 
possibility. I have done some checking around every now and then when a user 
complains and I generally find that in the cases where users do report 
multiple mail, the maillog entries show a verbatim copy of the message-ID in 
each of maillog entries for the mail. Does anyone perhaps have an idea what 
could cause this? It's all just normal SMTP, no use of the Toltec connector, 
and everything in a LAN environment.

Regards
JP


From Grenzlaeufer at gmx.net  Fri Nov 14 14:01:07 2008
From: Grenzlaeufer at gmx.net (Volker Stoppe)
Date: Fri, 14 Nov 2008 14:01:07 +0100
Subject: Old mail-address still active, while distribution list with same name
	exists
Message-ID: <op.ukl035rb7qpqkm@imacnum>

Hallo!

I have a strange problem. We had an mail-address with a forward to an  
other mail-address. Then we deleted the first mail-address and created a  
distribution list with the same name and several recipients. The strange  
thing is, that everytime a mail gets sent to the distribution list, only  
the recipient of the old mail address gets the mail. I also deleted the  
distribution list and made a slapcat. There was no name of the  
distribution list or old mail address anymore, but the old reciepient  
still got the mail. I checked the postfix-log for this behaviour. With the  
distribution list created the slapcat told me that this list all members  
it should have. I restarted all services and also rebooted the server at  
night, but it didn?t help.

Short form of my descriptin:

name1 (address) -> recepient1
name1 gets deleted
name1 (as distribution list) is created: with recepeint1, reciepient2 and  
reciepient3
mail to name1 -> mail is only sent to reciepient1

System:
Debian 4.0
Kolab 2.1

Had anyonve have similar behaviour before? I would be glad for every hint!

Greetings

Volker


From alex at swiftnetcomputers.biz  Fri Nov 14 16:17:15 2008
From: alex at swiftnetcomputers.biz (Alex Chejlyk)
Date: Fri, 14 Nov 2008 10:17:15 -0500
Subject: Mail duplication
In-Reply-To: <200811141409.50773.viljoenjp@workforce.co.za>
References: <200811141409.50773.viljoenjp@workforce.co.za>
Message-ID: <491D967B.6060802@swiftnetcomputers.biz>

JP Viljoen wrote:
> Hi all
> 
> I've had a few users complaining that they get mail multiple times (2 or more, 
> average up to 40) when sent from certain people. All the senders in the 
> building are generally using Outlook. Just want to hear if anyone on the 
> lists has had similar issues, and/or possibly a resolution for the issue. I 
> by nature can't think that it's the pieces of software the mailserver is 
> built on (the Kolab stack), but since I know the previous administrators of 
> this setup weren't very .. future-minded .. I wouldn't rule out the 
> possibility. I have done some checking around every now and then when a user 
> complains and I generally find that in the cases where users do report 
> multiple mail, the maillog entries show a verbatim copy of the message-ID in 
> each of maillog entries for the mail. Does anyone perhaps have an idea what 
> could cause this? It's all just normal SMTP, no use of the Toltec connector, 
> and everything in a LAN environment.
> 
> Regards
> JP
> 
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
> 
Are you using Toltec? I've seen this with Toltec connector and large pst's.


From aspineux at gmail.com  Fri Nov 14 17:41:44 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Fri, 14 Nov 2008 17:41:44 +0100
Subject: Mail not rejected
In-Reply-To: <200811132129.05713.carsten@cburghardt.com>
References: <200811132129.05713.carsten@cburghardt.com>
Message-ID: <71fe4e760811140841o5f5e633eh17205a93479e0f36@mail.gmail.com>

On Thu, Nov 13, 2008 at 9:29 PM, Carsten Burghardt
<carsten at cburghardt.com> wrote:
> Hi list,
>
> I am a little confused about the postfix behaviour of my kolab 2.2
> installation. I added several domains in the kolab web frontend. The default
> distribution lists are then created for postmaster, abuse and so on.
> I have added myself to the adressbook and added some aliases like "cb" to the
> list. When I send an email to an invalid/unknown username like
> nonsense@<mydomain> then the email is not rejected by postfix but it passes
> through to postmaster. Where does that catch-all entry come from and how can
> I get rid of it? I have no entries in my virtual table so that must be a
> result of the ldap query I assume.
> SuSE 10.3 with their Kolab packages.

you can query your ldap for that

postmap -q nonsense@<mydomain> ldap:/kolab/etc/postfix/ldapvirtual.cf

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



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


From aspineux at gmail.com  Fri Nov 14 17:51:10 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Fri, 14 Nov 2008 17:51:10 +0100
Subject: Old mail-address still active,
	while distribution list with same name exists
In-Reply-To: <op.ukl035rb7qpqkm@imacnum>
References: <op.ukl035rb7qpqkm@imacnum>
Message-ID: <71fe4e760811140851o7029502dn4d1d01e2fd81ab0d@mail.gmail.com>

On Fri, Nov 14, 2008 at 2:01 PM, Volker Stoppe <Grenzlaeufer at gmx.net> wrote:
> Hallo!
>
> I have a strange problem. We had an mail-address with a forward to an
> other mail-address. Then we deleted the first mail-address and created a
> distribution list with the same name and several recipients. The strange
> thing is, that everytime a mail gets sent to the distribution list, only
> the recipient of the old mail address gets the mail. I also deleted the
> distribution list and made a slapcat. There was no name of the
> distribution list or old mail address anymore, but the old reciepient
> still got the mail. I checked the postfix-log for this behaviour. With the
> distribution list created the slapcat told me that this list all members
> it should have. I restarted all services and also rebooted the server at
> night, but it didn?t help.
>
> Short form of my descriptin:
>
> name1 (address) -> recepient1
> name1 gets deleted
> name1 (as distribution list) is created: with recepeint1, reciepient2 and
> reciepient3
> mail to name1 -> mail is only sent to reciepient1
>
> System:
> Debian 4.0
> Kolab 2.1
>
> Had anyonve have similar behaviour before? I would be glad for every hint!
>

The forward is done by cyrus imap at delivery, by a sieve script. (
look in lmtpd.log )
The sieve scrip is attached to a mailbox and probably not deleted at
deletion of the mailbox.

Kolabd could maybe delete such script at creation and/or deletion time
to prevent this kind of problem

look into /kolab/var/imapd/sieve/ for the scripts and delete manualy
all files in the directory with the same name as mailbox.

You could also recreate the normal user, reset the forwarding, then
recreate the list ! This is longer



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



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


From aspineux at gmail.com  Fri Nov 14 18:12:44 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Fri, 14 Nov 2008 18:12:44 +0100
Subject: Mail duplication
In-Reply-To: <200811141409.50773.viljoenjp@workforce.co.za>
References: <200811141409.50773.viljoenjp@workforce.co.za>
Message-ID: <71fe4e760811140912r71734274w4b60987973eda753@mail.gmail.com>

On Fri, Nov 14, 2008 at 1:09 PM, JP Viljoen <viljoenjp at workforce.co.za> wrote:
> Hi all
>
> I've had a few users complaining that they get mail multiple times (2 or more,
> average up to 40) when sent from certain people. All the senders in the
> building are generally using Outlook. Just want to hear if anyone on the
> lists has had similar issues, and/or possibly a resolution for the issue. I
> by nature can't think that it's the pieces of software the mailserver is
> built on (the Kolab stack), but since I know the previous administrators of
> this setup weren't very .. future-minded .. I wouldn't rule out the
> possibility. I have done some checking around every now and then when a user
> complains and I generally find that in the cases where users do report
> multiple mail, the maillog entries show a verbatim copy of the message-ID in
> each of maillog entries for the mail. Does anyone perhaps have an idea what
> could cause this? It's all just normal SMTP, no use of the Toltec connector,
> and everything in a LAN environment.

Can you compare the header part of two "identical" email ?

>
> Regards
> JP
>
> _______________________________________________
> 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  Fri Nov 14 19:53:46 2008
From: s.kim at hia.rwth-aachen.de (Saim Kim)
Date: Fri, 14 Nov 2008 19:53:46 +0100
Subject: Automatic Conflict Resolution not working -freebusy list the cause?
Message-ID: <491DC93A.3030002@hia.rwth-aachen.de>

Hello,

I have ressource accounts, that should automatically decline event 
invitation if they are already booked -but it doesn't work.

Test Scenario:

User A books ressource R.
Ressource R accepts.
User B books ressource R with a time overlap.
Ressource R accepts eventhough an exisiting event should cause a conflict.

I checked the issue tracker and found two issues which are related to 
freebusy generation of another users/ressources calendar: 
https://www.intevation.de/roundup/kolab/issue3208
https://www.intevation.de/roundup/kolab/issue3074

Is it possible, that this is caused by one of these issues?

Nice weekend
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 carsten at cburghardt.com  Fri Nov 14 20:56:55 2008
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Fri, 14 Nov 2008 20:56:55 +0100
Subject: Mail not rejected
In-Reply-To: <71fe4e760811140841o5f5e633eh17205a93479e0f36@mail.gmail.com>
References: <200811132129.05713.carsten@cburghardt.com>
	<71fe4e760811140841o5f5e633eh17205a93479e0f36@mail.gmail.com>
Message-ID: <20081114205655.12501znrhyasbfnk@www.inovox.de>

Hi Alain,

Quoting "Alain Spineux" <aspineux at gmail.com>:

> On Thu, Nov 13, 2008 at 9:29 PM, Carsten Burghardt
> <carsten at cburghardt.com> wrote:
>> Hi list,
>>
>> I am a little confused about the postfix behaviour of my kolab 2.2
>> installation. I added several domains in the kolab web frontend. The default
>> distribution lists are then created for postmaster, abuse and so on.
>> I have added myself to the adressbook and added some aliases like  
>> "cb" to the
>> list. When I send an email to an invalid/unknown username like
>> nonsense@<mydomain> then the email is not rejected by postfix but it passes
>> through to postmaster. Where does that catch-all entry come from and how can
>> I get rid of it? I have no entries in my virtual table so that must be a
>> result of the ldap query I assume.
>> SuSE 10.3 with their Kolab packages.
>
> you can query your ldap for that
>
> postmap -q nonsense@<mydomain> ldap:/kolab/etc/postfix/ldapvirtual.cf

It returns nothing.

I tested some usernames and noticed an (for me) inconsistent  
behaviour. A mail to mail at mydomain is accepted whereas  
nonsense at mydomain is rejected. I have not created an alias entry for  
"mail" that is for sure.


Carsten


From oszwald at web.de  Thu Nov 13 07:23:55 2008
From: oszwald at web.de (Florian Oszwald)
Date: Thu, 13 Nov 2008 07:23:55 +0100
Subject: kolab on opensuse 10.2 problem with php
Message-ID: <200811130723.55921.oszwald@web.de>

Hi all,
after I managed together with the help of this list to install kolab on 
opensuse 10.2, I now have the following situtation:

When accessing the link https://mysite.tlc.com/kolab/admin
I do not get anything.
1) So I made sure, that SSL works, 
2) added the following lines to php.ini:
include_path='.:/usr/share/php5:/usr/share/php5/PEAR:/usr/share/php5/kolab/admin/include/:/usr/share/php5/Smarty/:/etc/kolab
3) and changed the value in php.ini display-errors to On
4) restart the server

Then when accessing https://mysite.tlc.com/kolab/admin/index.php I get

Warning: require_once(kolab/admin/include/mysmarty.php): failed to open 
stream: No such file or directory in /srv/www/htdocs/kolab/admin/index.php on 
line 21 Fatal error: require_once(): Failed opening required 
'kolab/admin/include/mysmarty.php' 
(include_path='.:/usr/share/php5:/usr/share/php5/PEAR:/usr/share/php5/kolab/admin/include/:/usr/share/php5/Smarty/:/etc/kolab/') 
in /srv/www/htdocs/kolab/admin/index.php on line 21 

tail /var/log/apache2/error_log 

gives me

PHP Fatal error:  require_once(): Failed opening required 
'kolab/admin/include/mysmarty.php' 
(include_path='.:/usr/share/php5:/usr/share/php5/PEAR:/usr/share/php5/kolab/admin/include/:/usr/share/php5/Smarty/:/etc/kolab/') 
in /srv/www/htdocs/kolab/admin/index.php on line 21

I assume there is some path set the wrong way, but where?

Thank you so much in advance.

Regards,
Florian


From ml at radoeka.nl  Fri Nov 14 23:01:44 2008
From: ml at radoeka.nl (Richard Bos)
Date: Fri, 14 Nov 2008 23:01:44 +0100
Subject: kolab on opensuse 10.2 problem with php
In-Reply-To: <200811130723.55921.oszwald@web.de>
References: <200811130723.55921.oszwald@web.de>
Message-ID: <200811142301.45305.ml@radoeka.nl>

Op Thursday 13 November 2008 07:23:55 schreef Florian Oszwald:
> in /srv/www/htdocs/kolab/admin/index.php on line 21

Can you provide line21 of the file /srv/www/htdocs/kolab/admin/index.php
(and of course some lines around it).


-- 
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.


From aspineux at gmail.com  Sat Nov 15 04:05:56 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sat, 15 Nov 2008 04:05:56 +0100
Subject: Mail not rejected
In-Reply-To: <20081114205655.12501znrhyasbfnk@www.inovox.de>
References: <200811132129.05713.carsten@cburghardt.com>
	<71fe4e760811140841o5f5e633eh17205a93479e0f36@mail.gmail.com>
	<20081114205655.12501znrhyasbfnk@www.inovox.de>
Message-ID: <71fe4e760811141905q44da3ec1k9cfca0718fa3b95a@mail.gmail.com>

On Fri, Nov 14, 2008 at 8:56 PM, Carsten Burghardt
<carsten at cburghardt.com> wrote:
> Hi Alain,
>
> Quoting "Alain Spineux" <aspineux at gmail.com>:
>
>> On Thu, Nov 13, 2008 at 9:29 PM, Carsten Burghardt
>> <carsten at cburghardt.com> wrote:
>>> Hi list,
>>>
>>> I am a little confused about the postfix behaviour of my kolab 2.2
>>> installation. I added several domains in the kolab web frontend. The default
>>> distribution lists are then created for postmaster, abuse and so on.
>>> I have added myself to the adressbook and added some aliases like
>>> "cb" to the
>>> list. When I send an email to an invalid/unknown username like
>>> nonsense@<mydomain> then the email is not rejected by postfix but it passes
>>> through to postmaster. Where does that catch-all entry come from and how can
>>> I get rid of it? I have no entries in my virtual table so that must be a
>>> result of the ldap query I assume.
>>> SuSE 10.3 with their Kolab packages.
>>
>> you can query your ldap for that
>>
>> postmap -q nonsense@<mydomain> ldap:/kolab/etc/postfix/ldapvirtual.cf
>
> It returns nothing.

You must also check using /kolab/etc/postfix/ldapdislist.cf

>
> I tested some usernames and noticed an (for me) inconsistent
> behaviour. A mail to mail at mydomain is accepted whereas
> nonsense at mydomain is rejected. I have not created an alias entry for
> "mail" that is for sure.
>
>
> Carsten
>
> _______________________________________________
> 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 oszwald at web.de  Sat Nov 15 08:53:11 2008
From: oszwald at web.de (Florian Oszwald)
Date: Sat, 15 Nov 2008 08:53:11 +0100
Subject: kolab on opensuse 10.2 problem with php
In-Reply-To: <200811142301.45305.ml@radoeka.nl>
References: <200811130723.55921.oszwald@web.de>
	<200811142301.45305.ml@radoeka.nl>
Message-ID: <200811150853.12237.oszwald@web.de>

Hi, this is around line 21 in index.php:
require_once('kolab/admin/include/mysmarty.php');
require_once('kolab/admin/include/headers.php');
require_once('kolab/admin/include/locale.php');
require_once('kolab/admin/include/authenticate.php');

/**** Authentication etc. ***/

require_once('kolab/admin/include/menu.php');



Am Friday 14 November 2008 23:01:44 schrieben Sie:
> Op Thursday 13 November 2008 07:23:55 schreef Florian Oszwald:
> > in /srv/www/htdocs/kolab/admin/index.php on line 21
>
> Can you provide line21 of the file /srv/www/htdocs/kolab/admin/index.php
> (and of course some lines around it).


From carsten at cburghardt.com  Sat Nov 15 15:52:24 2008
From: carsten at cburghardt.com (Carsten Burghardt)
Date: Sat, 15 Nov 2008 15:52:24 +0100
Subject: Mail not rejected
In-Reply-To: <71fe4e760811141905q44da3ec1k9cfca0718fa3b95a@mail.gmail.com>
References: <200811132129.05713.carsten@cburghardt.com>	
	<71fe4e760811140841o5f5e633eh17205a93479e0f36@mail.gmail.com>	
	<20081114205655.12501znrhyasbfnk@www.inovox.de>
	<71fe4e760811141905q44da3ec1k9cfca0718fa3b95a@mail.gmail.com>
Message-ID: <491EE228.1060301@cburghardt.com>

Alain Spineux schrieb:
> On Fri, Nov 14, 2008 at 8:56 PM, Carsten Burghardt
> <carsten at cburghardt.com> wrote:
>   
>> Hi Alain,
>>
>> Quoting "Alain Spineux" <aspineux at gmail.com>:
>>
>>     
>>> On Thu, Nov 13, 2008 at 9:29 PM, Carsten Burghardt
>>> <carsten at cburghardt.com> wrote:
>>>       
>>>> Hi list,
>>>>
>>>> I am a little confused about the postfix behaviour of my kolab 2.2
>>>> installation. I added several domains in the kolab web frontend. The default
>>>> distribution lists are then created for postmaster, abuse and so on.
>>>> I have added myself to the adressbook and added some aliases like
>>>> "cb" to the
>>>> list. When I send an email to an invalid/unknown username like
>>>> nonsense@<mydomain> then the email is not rejected by postfix but it passes
>>>> through to postmaster. Where does that catch-all entry come from and how can
>>>> I get rid of it? I have no entries in my virtual table so that must be a
>>>> result of the ldap query I assume.
>>>> SuSE 10.3 with their Kolab packages.
>>>>         
>>> you can query your ldap for that
>>>
>>> postmap -q nonsense@<mydomain> ldap:/kolab/etc/postfix/ldapvirtual.cf
>>>       
>> It returns nothing.
>>     
>
> You must also check using /kolab/etc/postfix/ldapdislist.cf
>   
I did this but the result is the same: no return.


Regards

Carsten
-------------- n?chster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081115/98bf28a7/attachment.html

From aspineux at gmail.com  Sun Nov 16 05:06:37 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sun, 16 Nov 2008 05:06:37 +0100
Subject: Mail not rejected
In-Reply-To: <491EE228.1060301@cburghardt.com>
References: <200811132129.05713.carsten@cburghardt.com>
	<71fe4e760811140841o5f5e633eh17205a93479e0f36@mail.gmail.com>
	<20081114205655.12501znrhyasbfnk@www.inovox.de>
	<71fe4e760811141905q44da3ec1k9cfca0718fa3b95a@mail.gmail.com>
	<491EE228.1060301@cburghardt.com>
Message-ID: <71fe4e760811152006r25746e80oab1bc26aaeb67d4a@mail.gmail.com>

On Sat, Nov 15, 2008 at 3:52 PM, Carsten Burghardt
<carsten at cburghardt.com> wrote:
> Alain Spineux schrieb:
>
> On Fri, Nov 14, 2008 at 8:56 PM, Carsten Burghardt
> <carsten at cburghardt.com> wrote:
>
>
> Hi Alain,
>
> Quoting "Alain Spineux" <aspineux at gmail.com>:
>
>
>
> On Thu, Nov 13, 2008 at 9:29 PM, Carsten Burghardt
> <carsten at cburghardt.com> wrote:
>
>
> Hi list,
>
> I am a little confused about the postfix behaviour of my kolab 2.2
> installation. I added several domains in the kolab web frontend. The default
> distribution lists are then created for postmaster, abuse and so on.
> I have added myself to the adressbook and added some aliases like
> "cb" to the
> list. When I send an email to an invalid/unknown username like
> nonsense@<mydomain> then the email is not rejected by postfix but it passes
> through to postmaster. Where does that catch-all entry come from and how can
> I get rid of it? I have no entries in my virtual table so that must be a
> result of the ldap query I assume.
> SuSE 10.3 with their Kolab packages.
>
>
> you can query your ldap for that
>
> postmap -q nonsense@<mydomain> ldap:/kolab/etc/postfix/ldapvirtual.cf
>
>
> It returns nothing.
>
>
> You must also check using /kolab/etc/postfix/ldapdislist.cf
>
>
> I did this but the result is the same: no return.

search the postfix.log and lmtpd.log to understand what is appening.

Use my tutorial :

http://wiki.kolab.org/index.php/What_is_happening_to_my_emails_where_are_their._Search_your_postfix_log_to_find_them


Hope this help

>
>
> Regards
>
> Carsten
>
> _______________________________________________
> 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 wrobel at pardus.de  Sun Nov 16 08:54:32 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sun, 16 Nov 2008 08:54:32 +0100
Subject: Automatic Conflict Resolution not working -freebusy list the
	cause?
In-Reply-To: <491DC93A.3030002@hia.rwth-aachen.de>
References: <491DC93A.3030002@hia.rwth-aachen.de>
Message-ID: <20081116085432.13946wypekjk8iw4@webmail.pardus.de>

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

> Hello,
>
> I have ressource accounts, that should automatically decline event
> invitation if they are already booked -but it doesn't work.
>
> Test Scenario:
>
> User A books ressource R.
> Ressource R accepts.
> User B books ressource R with a time overlap.
> Ressource R accepts eventhough an exisiting event should cause a conflict.
>
> I checked the issue tracker and found two issues which are related to
> freebusy generation of another users/ressources calendar:
> https://www.intevation.de/roundup/kolab/issue3208
> https://www.intevation.de/roundup/kolab/issue3074
>
> Is it possible, that this is caused by one of these issues?

Yes, I think so. These issues should heve been fixed for  
Kolab-Server-2.2.1 but I'll try to check 2.2.0 next week and see if I  
can provide a decent fix (patch) for the server as at least   
kolab/issue3208 has not been fixed yet.

Cheers,

Gunnar

>
> Nice weekend
> 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/20081116/fec87021/attachment.bin

From wrobel at pardus.de  Mon Nov 17 08:32:26 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Mon, 17 Nov 2008 08:32:26 +0100
Subject: [Kolab-devel] Running Kolab2/OpenPKG-2.2 on Amazon EC2 (was:
	Kolab in the clouds)
In-Reply-To: <20081021111032.13843cl51kv1wayo@webmail.pardus.de>
References: <20081014081347.27441bu8f5a6cfq8@webmail.pardus.de>
	<200810171744.22064.bernhard@intevation.de>
	<20081021111032.13843cl51kv1wayo@webmail.pardus.de>
Message-ID: <20081117083226.17031qut78i2a7fo@webmail.pardus.de>

Quoting Gunnar Wrobel <wrobel at pardus.de>:

> Quoting Bernhard Reiter <bernhard at intevation.de>:
>
>> On Dienstag, 14. Oktober 2008, Gunnar Wrobel wrote:
>>> The current one is AMI "ami-6e2eca07" and I update the thread once
>>> I  publish others.
>>
>> This might warrent a new wiki page to keep the overview and the
>> instructions. :)
>
> Yes, will do that once I have a 2.2 image. I'll write down some
> instructions on how to use the images then.

I generated a Kolab2/OpenPKG-2.2 server image which is available with  
the ID "ami-c910f4a0".

In addition I created instructions on how to get a Kolab server up and  
running in 10 minutes. See

https://wiki.kolab.org/index.php/Kolab2_on_Amazons_EC2

Please note that this is really only meant for testing purposes. As  
far as I know most of Amazons EC2 network is black listed as spammers  
like the possibility to start up a virtual machine and send a few mails.

A question to the developer crowd: Is there significant interest in  
having a pre-release Kolab-Server-2.2.1 on EC2?

Cheers,

Gunnar

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



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

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

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


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

From kumarrajnishgupta at gmail.com  Mon Nov 17 10:47:07 2008
From: kumarrajnishgupta at gmail.com (rajnish kumar)
Date: Mon, 17 Nov 2008 15:17:07 +0530
Subject: Disclamair for kolab
Message-ID: <6ce9bfc90811170147h48b6d9e4p3fdc19208b16fb86@mail.gmail.com>

Dear friends
                  I want to put disclamair in my kolab for out going
mails. I start work with "ALTER MIME" but it is not get successful. So
plz share with me if any one has done so far.

with regds
rajnish


From grenzlaeufer at gmx.net  Mon Nov 17 11:36:14 2008
From: grenzlaeufer at gmx.net (Volker Stoppe)
Date: Mon, 17 Nov 2008 11:36:14 +0100
Subject: Old mail-address still active, while distribution list with same
	name exists
In-Reply-To: <71fe4e760811140851o7029502dn4d1d01e2fd81ab0d@mail.gmail.com>
References: <op.ukl035rb7qpqkm@imacnum>
	<71fe4e760811140851o7029502dn4d1d01e2fd81ab0d@mail.gmail.com>
Message-ID: <op.ukreeotar7zxeq@vst-tp.lichtplatz.net>

Hallo!

On Fri, 14 Nov 2008 17:51:10 +0100, Alain Spineux <aspineux at gmail.com>  
wrote:
>> name1 (address) -> recepient1
>> name1 gets deleted
>> name1 (as distribution list) is created: with recepeint1, reciepient2  
>> and
>> reciepient3
>> mail to name1 -> mail is only sent to reciepient1

> The forward is done by cyrus imap at delivery, by a sieve script. (
> look in lmtpd.log )
> The sieve scrip is attached to a mailbox and probably not deleted at
> deletion of the mailbox.
> Kolabd could maybe delete such script at creation and/or deletion time
> to prevent this kind of problem
> look into /kolab/var/imapd/sieve/ for the scripts and delete manualy
> all files in the directory with the same name as mailbox.
> You could also recreate the normal user, reset the forwarding, then
> recreate the list ! This is longer


Unfortunately nothing helped. I found the folder with the scripts, deleted  
it but it didn't help. Then I deleted the distribution list, recreated the  
user, created a forward for the user and deleted the forward and the  
user-account again. Nothing changed. Below are some logs.

Maybe anyone else has an other idea?

Greetings

Volker





When I do a slapcat, the distribution list has the right members:

mail:/kolab/var/imapd/log# slapcat | grep -A 25 mylist
/kolab/etc/openldap/slapd.conf: line 66: new attribute <member>
dn: cn=mylist at domain.com,dc=domain,dc=com
objectClass: kolabGroupOfNames
cn: mylist at domain.com
mail: mylist at domain.com
member: cn=User A,dc=domain,dc=com
member: cn=User B,dc=domain,dc=com
member: cn=User C,dc=domain,dc=com
structuralObjectClass: kolabGroupOfNames
entryUUID: 7e756234-48dc-102d-8ff0-37fef441d556
creatorsName: cn=manager,cn=internal,dc=domain,dc=com
createTimestamp: 20081117101607Z
entryCSN: 20081117101607Z#000000#00#000000
modifiersName: cn=manager,cn=internal,dc=domain,dc=com
modifyTimestamp: 20081117101607Z



lmtp.log
Nov 17 11:21:46 mail <debug> lmtp[30196]: accepted connection
Nov 17 11:21:46 mail <debug> lmtp[30196]: connection from localhost  
[127.0.0.1] preauth'd as postman
Nov 17 11:21:46 mail <debug> lmtp[30196]: append_fromstage: message 2639  
added to domain.com!user.user^c
Nov 17 11:21:46 mail <info> lmtp[30196]: Delivered:  
<op.ukrdq8aogaej35 at vst-tp.lichtplatz.net> to mailbox:  
domain.com!user.user^c
Nov 17 11:21:46 mail <debug> lmtp[30196]: mystore: starting txn 2147487238
Nov 17 11:21:46 mail <debug> lmtp[30196]: mystore: committing txn  
2147487238
Nov 17 11:21:46 mail <debug> lmtp[30196]: duplicate_mark:  
<op.ukrdq8aogaej35 at vst-tp.lichtplatz.net> .user^c+ at domain.com.sieve.  
1226917306 0


mail:/kolab/var/postfix/log# cat postfix.log | grep 34B1C128079:
Nov 17 11:21:46 mail <info> postfix/smtpd[30054]: 34B1C128079:  
client=217-20-117-138.company.de[217.20.117.138]
Nov 17 11:21:46 mail <info> postfix/cleanup[30020]: 34B1C128079:  
message-id=<op.ukrdq8aogaej35 at vst-tp.lichtplatz.net>
Nov 17 11:21:46 mail <info> postfix/qmgr[25211]: 34B1C128079:  
from=<vst at company.de>, size=1732, nrcpt=1 (queue active)
Nov 17 11:21:46 mail <info> postfix/pipe[29135]: 34B1C128079:  
to=<user.c at domain.com>, orig_to=<mylist at domain.com>, relay=kolabfilter,  
delay=0, status=sent (mail.domain.com)
Nov 17 11:21:46 mail <info> postfix/qmgr[25211]: 34B1C128079: removed


From aspineux at gmail.com  Mon Nov 17 19:04:55 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 17 Nov 2008 19:04:55 +0100
Subject: Old mail-address still active,
	while distribution list with same name exists
In-Reply-To: <op.ukreeotar7zxeq@vst-tp.lichtplatz.net>
References: <op.ukl035rb7qpqkm@imacnum>
	<71fe4e760811140851o7029502dn4d1d01e2fd81ab0d@mail.gmail.com>
	<op.ukreeotar7zxeq@vst-tp.lichtplatz.net>
Message-ID: <71fe4e760811171004x116ae793xcd264974ead14c26@mail.gmail.com>

On Mon, Nov 17, 2008 at 11:36 AM, Volker Stoppe <grenzlaeufer at gmx.net> wrote:
> Hallo!
>
> On Fri, 14 Nov 2008 17:51:10 +0100, Alain Spineux <aspineux at gmail.com>
> wrote:
>>> name1 (address) -> recepient1
>>> name1 gets deleted
>>> name1 (as distribution list) is created: with recepeint1, reciepient2
>>> and
>>> reciepient3
>>> mail to name1 -> mail is only sent to reciepient1
>
>> The forward is done by cyrus imap at delivery, by a sieve script. (
>> look in lmtpd.log )
>> The sieve scrip is attached to a mailbox and probably not deleted at
>> deletion of the mailbox.
>> Kolabd could maybe delete such script at creation and/or deletion time
>> to prevent this kind of problem
>> look into /kolab/var/imapd/sieve/ for the scripts and delete manualy
>> all files in the directory with the same name as mailbox.
>> You could also recreate the normal user, reset the forwarding, then
>> recreate the list ! This is longer
>
>
> Unfortunately nothing helped. I found the folder with the scripts, deleted
> it but it didn't help. Then I deleted the distribution list, recreated the
> user, created a forward for the user and deleted the forward and the
> user-account again. Nothing changed. Below are some logs.
>
> Maybe anyone else has an other idea?

Is-it an openpkg distrib ?

Take a look at,
http://wiki.kolab.org/index.php/What_is_happening_to_my_emails_where_are_their._Search_your_postfix_log_to_find_them
maybe this will help

did you look at /kolab/var/resmgr/resmgr.log

One again what about the postmap query for the distribution list ?

>
> Greetings
>
> Volker
>
>
>
>
>
> When I do a slapcat, the distribution list has the right members:
>
> mail:/kolab/var/imapd/log# slapcat | grep -A 25 mylist
> /kolab/etc/openldap/slapd.conf: line 66: new attribute <member>
> dn: cn=mylist at domain.com,dc=domain,dc=com
> objectClass: kolabGroupOfNames
> cn: mylist at domain.com
> mail: mylist at domain.com
> member: cn=User A,dc=domain,dc=com
> member: cn=User B,dc=domain,dc=com
> member: cn=User C,dc=domain,dc=com
> structuralObjectClass: kolabGroupOfNames
> entryUUID: 7e756234-48dc-102d-8ff0-37fef441d556
> creatorsName: cn=manager,cn=internal,dc=domain,dc=com
> createTimestamp: 20081117101607Z
> entryCSN: 20081117101607Z#000000#00#000000
> modifiersName: cn=manager,cn=internal,dc=domain,dc=com
> modifyTimestamp: 20081117101607Z
>
>
>
> lmtp.log
> Nov 17 11:21:46 mail <debug> lmtp[30196]: accepted connection
> Nov 17 11:21:46 mail <debug> lmtp[30196]: connection from localhost
> [127.0.0.1] preauth'd as postman
> Nov 17 11:21:46 mail <debug> lmtp[30196]: append_fromstage: message 2639
> added to domain.com!user.user^c
> Nov 17 11:21:46 mail <info> lmtp[30196]: Delivered:
> <op.ukrdq8aogaej35 at vst-tp.lichtplatz.net> to mailbox:
> domain.com!user.user^c
> Nov 17 11:21:46 mail <debug> lmtp[30196]: mystore: starting txn 2147487238
> Nov 17 11:21:46 mail <debug> lmtp[30196]: mystore: committing txn
> 2147487238
> Nov 17 11:21:46 mail <debug> lmtp[30196]: duplicate_mark:
> <op.ukrdq8aogaej35 at vst-tp.lichtplatz.net> .user^c+ at domain.com.sieve.
> 1226917306 0
>

You have no error like
Nov 13 09:30:30 eg01.emailgency.loc <debug> lmtpunix[2859]: IOERROR:
fstating sieve script
/kolab/var/imapd/sieve/domain/a/atesteg01.emailgency.loc/c/catcha
ll^atesteg01^emailgency^loc/defaultbc: (2) No such file or directory

meaning their is no default sieve script, then you should have one !

The good way to manage sieve script is to use sieveshell like in :

/kolab/bin/sieveshell -u admin at eg01.emailgency.loc -a
admin at eg01.emailgency.loc localhost
connecting to localhost
Please enter your password:
> help
Usage:
  sieveshell [-u username] [-a authname] [-r realm] <server>

help             - this screen
list             - list scripts on server
put <filename> [<target name>]
                 - upload script to server
get <name> [<filename>]
                 - get script. if no filename display to stdout
delete <name>    - delete script.
activate <name>  - set a script as the active script
deactivate       - deactivate all scripts
quit             - quit
> list
kolab-forward.siv  <- active script


Try to remove and deactive the script this way


>
> mail:/kolab/var/postfix/log# cat postfix.log | grep 34B1C128079:
> Nov 17 11:21:46 mail <info> postfix/smtpd[30054]: 34B1C128079:
> client=217-20-117-138.company.de[217.20.117.138]
> Nov 17 11:21:46 mail <info> postfix/cleanup[30020]: 34B1C128079:
> message-id=<op.ukrdq8aogaej35 at vst-tp.lichtplatz.net>
> Nov 17 11:21:46 mail <info> postfix/qmgr[25211]: 34B1C128079:
> from=<vst at company.de>, size=1732, nrcpt=1 (queue active)
> Nov 17 11:21:46 mail <info> postfix/pipe[29135]: 34B1C128079:
> to=<user.c at domain.com>, orig_to=<mylist at domain.com>, relay=kolabfilter,
> delay=0, status=sent (mail.domain.com)
> Nov 17 11:21:46 mail <info> postfix/qmgr[25211]: 34B1C128079: removed
>
> _______________________________________________
> 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 Nov 17 21:05:38 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Mon, 17 Nov 2008 21:05:38 +0100
Subject: [Kolab-devel] Running Kolab2/OpenPKG-2.2 on Amazon EC2 (was:
	Kolab in the clouds)
In-Reply-To: <20081117083226.17031qut78i2a7fo@webmail.pardus.de>
References: <20081014081347.27441bu8f5a6cfq8@webmail.pardus.de>
	<200810171744.22064.bernhard@intevation.de>
	<20081021111032.13843cl51kv1wayo@webmail.pardus.de>
	<20081117083226.17031qut78i2a7fo@webmail.pardus.de>
Message-ID: <71fe4e760811171205w16e25a16lde3ee684034cbd57@mail.gmail.com>

On Mon, Nov 17, 2008 at 8:32 AM, Gunnar Wrobel <wrobel at pardus.de> wrote:
> Quoting Gunnar Wrobel <wrobel at pardus.de>:
>
>> Quoting Bernhard Reiter <bernhard at intevation.de>:
>>
>>> On Dienstag, 14. Oktober 2008, Gunnar Wrobel wrote:
>>>>
>>>> The current one is AMI "ami-6e2eca07" and I update the thread once
>>>> I  publish others.
>>>
>>> This might warrent a new wiki page to keep the overview and the
>>> instructions. :)
>>
>> Yes, will do that once I have a 2.2 image. I'll write down some
>> instructions on how to use the images then.
>
> I generated a Kolab2/OpenPKG-2.2 server image which is available with the ID
> "ami-c910f4a0".

Hi Gunnar

Could you give us an idea of the cost of the use :
- for example for the installation of kolab2.2
- for its use, say create 2 users and send some emails in between.




>
> In addition I created instructions on how to get a Kolab server up and
> running in 10 minutes. See
>
> https://wiki.kolab.org/index.php/Kolab2_on_Amazons_EC2
>
> Please note that this is really only meant for testing purposes. As far as I
> know most of Amazons EC2 network is black listed as spammers like the
> possibility to start up a virtual machine and send a few mails.
>
> A question to the developer crowd: Is there significant interest in having a
> pre-release Kolab-Server-2.2.1 on EC2?
>
> Cheers,
>
> Gunnar
>
>>
>> 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://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-devel mailing list
>> Kolab-devel at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-devel
>
>
>
> --
> ______ http://kdab.com _______________ http://kolab-konsortium.com _
>
> p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
>
> ____ http://www.pardus.de _________________ http://gunnarwrobel.de _
> E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
> Tel.   : +49 700 6245 0000                          Bundesstrasse 29
> Fax    : +49 721 1513 52322                          D-20146 Hamburg
> --------------------------------------------------------------------
>   >> Mail at ease - Rent a kolab groupware server at p at rdus <<
> --------------------------------------------------------------------
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
> _______________________________________________
> 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 wrobel at pardus.de  Mon Nov 17 21:24:33 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Mon, 17 Nov 2008 21:24:33 +0100
Subject: [Kolab-devel] Running Kolab2/OpenPKG-2.2 on Amazon EC2 (was:
	Kolab in the clouds)
In-Reply-To: <71fe4e760811171205w16e25a16lde3ee684034cbd57@mail.gmail.com>
References: <20081014081347.27441bu8f5a6cfq8@webmail.pardus.de>
	<200810171744.22064.bernhard@intevation.de>
	<20081021111032.13843cl51kv1wayo@webmail.pardus.de>
	<20081117083226.17031qut78i2a7fo@webmail.pardus.de>
	<71fe4e760811171205w16e25a16lde3ee684034cbd57@mail.gmail.com>
Message-ID: <20081117212433.19974e6up759fx8g@webmail.pardus.de>

Quoting Alain Spineux <aspineux at gmail.com>:

> On Mon, Nov 17, 2008 at 8:32 AM, Gunnar Wrobel <wrobel at pardus.de> wrote:
>> Quoting Gunnar Wrobel <wrobel at pardus.de>:
>>
>>> Quoting Bernhard Reiter <bernhard at intevation.de>:
>>>
>>>> On Dienstag, 14. Oktober 2008, Gunnar Wrobel wrote:
>>>>>
>>>>> The current one is AMI "ami-6e2eca07" and I update the thread once
>>>>> I  publish others.
>>>>
>>>> This might warrent a new wiki page to keep the overview and the
>>>> instructions. :)
>>>
>>> Yes, will do that once I have a 2.2 image. I'll write down some
>>> instructions on how to use the images then.
>>
>> I generated a Kolab2/OpenPKG-2.2 server image which is available with the ID
>> "ami-c910f4a0".
>
> Hi Gunnar
>
> Could you give us an idea of the cost of the use :
> - for example for the installation of kolab2.2
> - for its use, say create 2 users and send some emails in between.

Traffic is cheap, the computing power is not very cheap. 10 cents per hour.

If you would consider having a machine running 24/7 on AWS it would be  
expensive. But as I mentioned before I wouldn't recommend running a  
mail server there. It has some other uses though.

The reason why I constructed the images was that it is extremely  
helpful when handling user requests. If a user comes with a question  
or a bug report on Kolab Server 2.1 it does not help too much if my  
only answer is: "Hm, sorry I am currently developing on the Kolab  
server, only have CVS installed and don't see the problem you are  
describing."

With AWS it takes me five minutes to choose any of the older Kolab  
server versions and check the problem there. And I turn the machine  
off an hour later. So the costs for that are negligible.

In addition AWS is nice for upgrade testing when developing.

I made the images public since I believe they might be helpful for  
others, too. If somebody wants to test the Kolab server it takes only  
a few minutes to get the system up and running so that you can test  
features.

Maybe it is also helpful for the native ports to see how the Kolab  
server works on OpenPKG.

Cheers,

Gunnar

>
>
>
>
>>
>> In addition I created instructions on how to get a Kolab server up and
>> running in 10 minutes. See
>>
>> https://wiki.kolab.org/index.php/Kolab2_on_Amazons_EC2
>>
>> Please note that this is really only meant for testing purposes. As far as I
>> know most of Amazons EC2 network is black listed as spammers like the
>> possibility to start up a virtual machine and send a few mails.
>>
>> A question to the developer crowd: Is there significant interest in having a
>> pre-release Kolab-Server-2.2.1 on EC2?
>>
>> Cheers,
>>
>> Gunnar
>>
>>>
>>> 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://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-devel mailing list
>>> Kolab-devel at kolab.org
>>> https://kolab.org/mailman/listinfo/kolab-devel
>>
>>
>>
>> --
>> ______ http://kdab.com _______________ http://kolab-konsortium.com _
>>
>> p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium
>>
>> ____ http://www.pardus.de _________________ http://gunnarwrobel.de _
>> E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
>> Tel.   : +49 700 6245 0000                          Bundesstrasse 29
>> Fax    : +49 721 1513 52322                          D-20146 Hamburg
>> --------------------------------------------------------------------
>>   >> Mail at ease - Rent a kolab groupware server at p at rdus <<
>> --------------------------------------------------------------------
>>
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>> _______________________________________________
>> 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
>
> _______________________________________________
> 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/20081117/79a863c4/attachment.bin

From ml at radoeka.nl  Tue Nov 18 00:19:10 2008
From: ml at radoeka.nl (Richard Bos)
Date: Tue, 18 Nov 2008 00:19:10 +0100
Subject: [Kolab-devel] Running Kolab2/OpenPKG-2.2 on Amazon EC2 (was:
	Kolab in the clouds)
In-Reply-To: <20081117212433.19974e6up759fx8g@webmail.pardus.de>
References: <20081014081347.27441bu8f5a6cfq8@webmail.pardus.de>
	<71fe4e760811171205w16e25a16lde3ee684034cbd57@mail.gmail.com>
	<20081117212433.19974e6up759fx8g@webmail.pardus.de>
Message-ID: <200811180019.11017.ml@radoeka.nl>

Op Monday 17 November 2008 21:24:33 schreef Gunnar Wrobel:
> In addition AWS is nice for upgrade testing when developing.
>
> I made the images public since I believe they might be helpful for ?
> others, too. If somebody wants to test the Kolab server it takes only ?
> a few minutes to get the system up and running so that you can test ?
> features.
>
> Maybe it is also helpful for the native ports to see how the Kolab ?
> server works on OpenPKG.


would something like this, be possible with for example virtual box images?

-- 
Richard Bos
We are borrowing the world of our children,
It is not inherited from our parents.


From albrecht.dress at lios-tech.com  Wed Nov 19 11:20:06 2008
From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=)
Date: Wed, 19 Nov 2008 11:20:06 +0100
Subject: Log Rotation Question
Message-ID: <1227090006l.24345l.0l@pc-adr2.lios-koeln.de>

Hi,

looking through the log files of my Kolab 2.2.0 installation, it seems  
as if the files in the folders

/kolab/var/kolab-filter/log
/kolab/var/kolab-freebusy/log

are not being rotated.  Is that intended, or did I miss something?  I  
was expecting that the installation does this, as for the  
postfix/cyrus/... logs.  One file  
(/kolab/var/kolab-filter/log/filter.log) is meanwhile ~120 megs large...

Thanks, Albrecht.


From albrecht.dress at lios-tech.com  Wed Nov 19 11:28:05 2008
From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=)
Date: Wed, 19 Nov 2008 11:28:05 +0100
Subject: [Outlook] shared calendars & reminders
Message-ID: <1227090485l.24345l.1l@pc-adr2.lios-koeln.de>

Hi,

I have an installation in which most users use Outlook w/ Toltec.  We  
have several shared read-only calendar folders, which people simply  
"invite" as to publish appointments as information.

I noticed that if the appointment contains a reminder setting, users  
running Outlook 2007 seem to get reminders from appointments in the  
shared folders even if they are not participants.  If they try to  
cancel the reminder, Outlook/Toltec apparently tries to modify the  
appointment, which fails as the calendar is read-only, resulting in  
more nagging about messages which cannot be stored in the IMAP folder.   
Older Outlook versions apparently do not show this strange "reminder".

Is this a known issue/feature?  As the reminders/errors are annoying,  
it would be nice to have a workaround.  Do you know if (and how?)  
Outlook 2007 can be instructed /not/ to display reminders from certain  
calendars?

An other option (involving some hacking) might be to have an option  
which makes calendars "silent", and to instruct the Kolab filter script  
to remove the reminder function (this is the <alarm> XML tag, right?)  
from calendar objects before they get inserted into the respective  
folders.

Any ideas?

Thanks, Albrecht.


From joon at radleys.co.za  Wed Nov 19 12:39:07 2008
From: joon at radleys.co.za (Joon Radley)
Date: Wed, 19 Nov 2008 13:39:07 +0200
Subject: [Outlook] shared calendars & reminders
In-Reply-To: <1227090485l.24345l.1l@pc-adr2.lios-koeln.de>
References: <1227090485l.24345l.1l@pc-adr2.lios-koeln.de>
Message-ID: <000401c94a3b$714e42d0$53eac870$@co.za>

Hi Albrecht,

Just send a mail to support at toltec.co.za. We have a utility that can set the
reminder flag on folders.

Best Regards

Joon Radley
Radley Network Technologies CC
Cell: +27 (0)83 368 8557
Fax: +27 (0)12 998 4346
E-mail: joon at radleys.co.za
Web: www.toltec.co.za

> -----Original Message-----
> From: kolab-users-bounces at kolab.org [mailto:kolab-users-
> bounces at kolab.org] On Behalf Of Albrecht Dre?
> Sent: Wednesday, November 19, 2008 12:28 PM
> To: Kolab Users List
> Subject: [Outlook] shared calendars & reminders
> 
> Hi,
> 
> I have an installation in which most users use Outlook w/ Toltec.  We
> have several shared read-only calendar folders, which people simply
> "invite" as to publish appointments as information.
> 
> I noticed that if the appointment contains a reminder setting, users
> running Outlook 2007 seem to get reminders from appointments in the
> shared folders even if they are not participants.  If they try to
> cancel the reminder, Outlook/Toltec apparently tries to modify the
> appointment, which fails as the calendar is read-only, resulting in
> more nagging about messages which cannot be stored in the IMAP folder.
> Older Outlook versions apparently do not show this strange "reminder".
> 
> Is this a known issue/feature?  As the reminders/errors are annoying,
> it would be nice to have a workaround.  Do you know if (and how?)
> Outlook 2007 can be instructed /not/ to display reminders from certain
> calendars?
> 
> An other option (involving some hacking) might be to have an option
> which makes calendars "silent", and to instruct the Kolab filter script
> to remove the reminder function (this is the <alarm> XML tag, right?)
> from calendar objects before they get inserted into the respective
> folders.
> 
> Any ideas?
> 
> Thanks, Albrecht.
> 
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users


From albrecht.dress at lios-tech.com  Sun Nov 23 18:45:12 2008
From: albrecht.dress at lios-tech.com (Albrecht =?iso-8859-1?b?RHJl3w==?=)
Date: Sun, 23 Nov 2008 18:45:12 +0100
Subject: Log Rotation Question
In-Reply-To: <1227090006l.24345l.0l@pc-adr2.lios-koeln.de>
References: <1227090006l.24345l.0l@pc-adr2.lios-koeln.de>
Message-ID: <20081123184512.48472gaw2c9egj3c@portal.lios-koeln.de>

Quoting Albrecht Dre? <albrecht.dress at lios-tech.com>:
> looking through the log files of my Kolab 2.2.0 installation, it seems
> as if the files in the folders
>
> /kolab/var/kolab-filter/log
> /kolab/var/kolab-freebusy/log
>
> are not being rotated.

Having a closer look at it, this seems to be a bug  
<https://www.intevation.de/roundup/kolab/issue3264>.

Furthermore, the file /kolab/var/kolab-filter/log/fatal.log contains  
lots of messages like

PHP Notice:  Undefined index:  xxx in  
/kolab/lib/php/Kolab/Filter/Resource.php on line yyy

Now, is this just a notice which can be ignored (as the entry  
suggests), or is this a fata error (as the file name implies)?  The  
same applies also for /kolab/var/kolab-freebusy/log/php-error.log, btw.

Thanks, Albrecht.


From Roessler at FuH-E.de  Mon Nov 24 11:43:19 2008
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Mon, 24 Nov 2008 11:43:19 +0100
Subject: slave-rejects und SASL-log (ldap_search_st() failed: Can't contact
	LDAP server)
In-Reply-To: <491C37CF.9010903@FuH-E.de>
References: <491C37CF.9010903@FuH-E.de>
Message-ID: <492A8547.1080306@FuH-E.de>

Christian R??ler schrieb:

Hallo everyone,

 > First: If I change a normal entry on the Kolab master (here, for 
example the user "Testa Testb" I got a notice in the reject logfile of 
the master (at 
/kolab/var/openldap/openldap-slurp/replica/kolab-slave\:636.rej):
 > | ERROR: No such object
 > | replica: kolab-slave.fuhintern.de:636
 > | time: 1226391794.1
 > | dn: cn=Testa Testb,dc=kolab,dc=testintern,dc=de
 > | changetype: modrdn
 > | newrdn: cn=Testa Testc
 > | deleteoldrdn: 1
 > ..but the object will be correctly replicated to the slave, as it
 > should be. As said, that's irritating.
 > After noticing sone SASL entries in the SASL log file I guessed it
 > could perhaps have something to do with SASL authentification (snippet
 > from /kolab/var/sasl/log/saslauthd.log):
 > | Nov 11 10:20:02 kolab <error> saslauthd[6635]: user ldap_search_st()
 > | failed: Can't contact LDAP server
 > | Nov 11 10:20:02 kolab <info> saslauthd[6635]: Retrying
 > | authentication

Please, can you take a look whether or not this happens at your 
installations also, so I will know if this is something happening 
elsewhere too, or just here on my installations?

Thanks and best regards,
Christian R??ler


From devgioiatech at gmail.com  Mon Nov 24 14:27:29 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Mon, 24 Nov 2008 14:27:29 +0100
Subject: external web client
In-Reply-To: <d53357b70811130420l4565994dn337aa69d98012aea@mail.gmail.com>
References: <d53357b70810300437r5fefb324vc1bb79c8ee17cd6a@mail.gmail.com>
	<d53357b70810300831u52f532e7naea1a90c616bd39d@mail.gmail.com>
	<20081031065053.41847cr9xzxhie0w@webmail.pardus.de>
	<d53357b70810310324od1929c8p7374d6b2774896c2@mail.gmail.com>
	<d53357b70810310356j10fe628dt11c2059af6532b96@mail.gmail.com>
	<20081103053223.166558e9ckjxuh44@webmail.pardus.de>
	<d53357b70811040345t121db963yd1b6f1df026ce416@mail.gmail.com>
	<d53357b70811120132y1da5654ay34507a68fc7f0012@mail.gmail.com>
	<20081113104553.18735zggnh2r9uw4@webmail.pardus.de>
	<d53357b70811130420l4565994dn337aa69d98012aea@mail.gmail.com>
Message-ID: <d53357b70811240527h5fe3e03fsf83b37f5d8031496@mail.gmail.com>

Hi all,
i got a workin external webmail client.

the login problem was related to mailbox format on the slave...infact,
converting from skiplist to berkley it works.

I've only a question:
if my mailbox is located on master kolab server, why the mailbox
format on the slave make me impossible to access it?

Any idea?

Thanks



2008/11/13 Antonio Straziota <devgioiatech at gmail.com>:
> I've installed a slave kolab for webmail use... but when i try to
> login in horde by external webmail...i can't log in  without any error
> message...
>
> kolab master:
> hostname: srv.demo.tst
>
> kolab slave:
> webmail.demo.tst
>
> only horde fails to log me in...
>
> i put ip and hostname of kolab master in /etc/hosts of kolab slave.
> but nothing changes.
>
> As you suggest, i took a look at at apache log dir...
> and  i found in in apache-error.log the error:
>
> [Wed Nov 12 00:36:02 2008] [error] [client 10.30.11.64[1]] Directory
> index forbidden by Options directive: /kolab/var/kolab/www/
>
>
>
> PS: I'm sorry for html mail...i don't realize that :P
>


From oszwald at web.de  Mon Nov 24 20:58:46 2008
From: oszwald at web.de (Florian Oszwald)
Date: Mon, 24 Nov 2008 20:58:46 +0100
Subject: DB Error: not found with Horde and Kolab
Message-ID: <200811242058.46844.oszwald@web.de>

Hi all,

I now have horde installed working together with kolab on opensuse 10.2.

The problem is, that i get the message DB Error: not found everytime I log in 
on a new day or making a new entry in the calendar or in notes.

In /var/log/horde/horde.log I do not get any useful information about this 
problem. On the internet I found, that it might be related to the SQL, but I 
am using it together with Kolab, so there is no need for sql, is there?

Thank you very much in advance.
Regards,
Florian


From aspineux at gmail.com  Tue Nov 25 01:14:23 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Tue, 25 Nov 2008 01:14:23 +0100
Subject: external web client
In-Reply-To: <d53357b70811240527h5fe3e03fsf83b37f5d8031496@mail.gmail.com>
References: <d53357b70810300437r5fefb324vc1bb79c8ee17cd6a@mail.gmail.com>
	<20081031065053.41847cr9xzxhie0w@webmail.pardus.de>
	<d53357b70810310324od1929c8p7374d6b2774896c2@mail.gmail.com>
	<d53357b70810310356j10fe628dt11c2059af6532b96@mail.gmail.com>
	<20081103053223.166558e9ckjxuh44@webmail.pardus.de>
	<d53357b70811040345t121db963yd1b6f1df026ce416@mail.gmail.com>
	<d53357b70811120132y1da5654ay34507a68fc7f0012@mail.gmail.com>
	<20081113104553.18735zggnh2r9uw4@webmail.pardus.de>
	<d53357b70811130420l4565994dn337aa69d98012aea@mail.gmail.com>
	<d53357b70811240527h5fe3e03fsf83b37f5d8031496@mail.gmail.com>
Message-ID: <71fe4e760811241614la72c644s39e5e91883c646bf@mail.gmail.com>

On Mon, Nov 24, 2008 at 2:27 PM, Antonio Straziota
<devgioiatech at gmail.com> wrote:
> Hi all,
> i got a workin external webmail client.
>
> the login problem was related to mailbox format on the slave...infact,
> converting from skiplist to berkley it works.
>
> I've only a question:
> if my mailbox is located on master kolab server, why the mailbox
> format on the slave make me impossible to access it?

because its is trying to access le mailbox localy (on the slave).
This look like an error.

Where did you found an error ? Witch one ? In wich log file ? on witch
computer ?


>
> Any idea?
>
> Thanks
>
>
>
> 2008/11/13 Antonio Straziota <devgioiatech at gmail.com>:
>> I've installed a slave kolab for webmail use... but when i try to
>> login in horde by external webmail...i can't log in  without any error
>> message...
>>
>> kolab master:
>> hostname: srv.demo.tst
>>
>> kolab slave:
>> webmail.demo.tst
>>
>> only horde fails to log me in...
>>
>> i put ip and hostname of kolab master in /etc/hosts of kolab slave.
>> but nothing changes.
>>
>> As you suggest, i took a look at at apache log dir...
>> and  i found in in apache-error.log the error:
>>
>> [Wed Nov 12 00:36:02 2008] [error] [client 10.30.11.64[1]] Directory
>> index forbidden by Options directive: /kolab/var/kolab/www/
>>
>>
>>
>> PS: I'm sorry for html mail...i don't realize that :P
>>
>
> _______________________________________________
> 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 christian.tardif at servinfo.ca  Tue Nov 25 05:30:58 2008
From: christian.tardif at servinfo.ca (Christian Tardif)
Date: Mon, 24 Nov 2008 23:30:58 -0500
Subject: Strange kolab behaviour.... 
Message-ID: <492B7F82.5050003@servinfo.ca>

Hi Kolab Users!

I have a strange problem for which I have no answer, so I'm asking...

I have two servers: ambrosia.servinfo.ca (kolab server answering for 
servinfo.ca mails), and pegasus.servinfo.ca (which answers for 
echo.servinfo.ca (sympa mailing list)). For users anywhere on the Net, 
the mailing list system is working perfectly. But for servinfo.ca users, 
it does not. A user sending mail to (for example) test at echo.servinfo.ca 
will get its mail bounced, because ambrosia complains that 
test at servinfo.ca does not exists.

I can see, also, that a mail sent to test at echo.servinfo.ca from anywhere 
(but not from servinfo.ca users) on the Net will get to its way. But 
users from ambrosia (servinfo.ca users) will get a mail, apparently sent 
to test at servinfo.ca. The won't be able to reply.

Why is ambrosia server readdressing the mails not intended to be treated 
by himself? Can't they just get thru?  How do I fix that behaviour?  
This is rather annoying...  and it makes me mad (which is, also, quite 
annoying  :-))

Thanks,

-- 
Christian Tardif




From devgioiatech at gmail.com  Tue Nov 25 10:48:55 2008
From: devgioiatech at gmail.com (Antonio Straziota)
Date: Tue, 25 Nov 2008 10:48:55 +0100
Subject: external web client
In-Reply-To: <71fe4e760811241614la72c644s39e5e91883c646bf@mail.gmail.com>
References: <d53357b70810300437r5fefb324vc1bb79c8ee17cd6a@mail.gmail.com>
	<d53357b70810310324od1929c8p7374d6b2774896c2@mail.gmail.com>
	<d53357b70810310356j10fe628dt11c2059af6532b96@mail.gmail.com>
	<20081103053223.166558e9ckjxuh44@webmail.pardus.de>
	<d53357b70811040345t121db963yd1b6f1df026ce416@mail.gmail.com>
	<d53357b70811120132y1da5654ay34507a68fc7f0012@mail.gmail.com>
	<20081113104553.18735zggnh2r9uw4@webmail.pardus.de>
	<d53357b70811130420l4565994dn337aa69d98012aea@mail.gmail.com>
	<d53357b70811240527h5fe3e03fsf83b37f5d8031496@mail.gmail.com>
	<71fe4e760811241614la72c644s39e5e91883c646bf@mail.gmail.com>
Message-ID: <d53357b70811250148t48e0c7c0h8fb8e8f06d071b9@mail.gmail.com>

Really i excluded that this could be the problem, because of webmail
related problem was only on the slave server.
I took a look to all possible causes. and, also thaks to passed
experiences, i consider to try this solution.

and after mailbox conversion it works

> Where did you found an error ?
on the slave kolab

> Witch one ?
Nov 24 13:19:21 web.demo.tst <warning> imap[10352]: DBERROR db4:
/kolab/var/imapd/mailboxes.db: unexpected file type or format
Nov 24 13:19:21 web.demo.tst <error> imap[10352]: DBERROR: opening
/kolab/var/imapd/mailboxes.db: Invalid argument
Nov 24 13:19:21 web.demo.tst <error> imap[10352]: DBERROR: opening
/kolab/var/imapd/mailboxes.db: cyrusdb error
Nov 24 13:19:21 web.demo.tst <error> imap[10352]: Fatal error: can't
read mailboxes file

> In wich log file ?
/kolab/var/imapd/log/imapd.log

> on witch computer ?
both master and slave are Centos 5.2

Just another question:

because i need only webmail and MTA funcion, if i stop useless
services on the slave (such as openldap or imap server) for security
reason or other, it affects the mail system work? or all service must
be running on both the servers?

Thanks.


2008/11/25 Alain Spineux <aspineux at gmail.com>:
> On Mon, Nov 24, 2008 at 2:27 PM, Antonio Straziota
> <devgioiatech at gmail.com> wrote:
>> Hi all,
>> i got a workin external webmail client.
>>
>> the login problem was related to mailbox format on the slave...infact,
>> converting from skiplist to berkley it works.
>>
>> I've only a question:
>> if my mailbox is located on master kolab server, why the mailbox
>> format on the slave make me impossible to access it?
>
> because its is trying to access le mailbox localy (on the slave).
> This look like an error.
>
> Where did you found an error ? Witch one ? In wich log file ? on witch
> computer ?
>
>
>>
>> Any idea?
>>
>> Thanks
>>
>>
>>
>> 2008/11/13 Antonio Straziota <devgioiatech at gmail.com>:
>>> I've installed a slave kolab for webmail use... but when i try to
>>> login in horde by external webmail...i can't log in  without any error
>>> message...
>>>
>>> kolab master:
>>> hostname: srv.demo.tst
>>>
>>> kolab slave:
>>> webmail.demo.tst
>>>
>>> only horde fails to log me in...
>>>
>>> i put ip and hostname of kolab master in /etc/hosts of kolab slave.
>>> but nothing changes.
>>>
>>> As you suggest, i took a look at at apache log dir...
>>> and  i found in in apache-error.log the error:
>>>
>>> [Wed Nov 12 00:36:02 2008] [error] [client 10.30.11.64[1]] Directory
>>> index forbidden by Options directive: /kolab/var/kolab/www/
>>>
>>>
>>>
>>> PS: I'm sorry for html mail...i don't realize that :P
>>>
>>
>> _______________________________________________
>> 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 Nov 25 12:11:47 2008
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Tue, 25 Nov 2008 12:11:47 +0100
Subject: Possible workaround(s) for mail user temporary suspension?
Message-ID: <492BDD73.3090300@FuH-E.de>

Hallo everybody,

I was searching for a possibility to suspend an user account (mail 
account, primarily). After a little bit of internet research I just 
found a wish for exactly the same thing: 
http://www.kolab.org/pipermail/kolab-devel/2005-August/004188.html

Can anyone tell me if this suggestion is already implemented in Kolab, 
and I am just too dense today to find it? And, if not, has anyone a good 
work-around for this?

Best regards,
Christian R??ler


From itsef-admin at brightsight.com  Tue Nov 25 14:55:44 2008
From: itsef-admin at brightsight.com (ITSEF Admin)
Date: Tue, 25 Nov 2008 14:55:44 +0100
Subject: Mail not rejected
In-Reply-To: <20081114205655.12501znrhyasbfnk@www.inovox.de>
References: <200811132129.05713.carsten@cburghardt.com>
	<71fe4e760811140841o5f5e633eh17205a93479e0f36@mail.gmail.com>
	<20081114205655.12501znrhyasbfnk@www.inovox.de>
Message-ID: <200811251455.44954.itsef-admin@brightsight.com>

On Friday 14 November 2008 20:56:55 Carsten Burghardt wrote:
> I tested some usernames and noticed an (for me) inconsistent
> behaviour. A mail to mail at mydomain is accepted whereas
> nonsense at mydomain is rejected. I have not created an alias entry for
> "mail" that is for sure.

Is "mail at domain" the only "strange" address that works? "mail at domain" *seems* 
to be a standard address that always work. I have not been able to track down 
where this is defined or where Kolab enables this, but it sure 
worked "out-of-the-box" on our Kolab server as well (2.0.x and 2.1).

Cheerio,

Thomas


From aspineux at gmail.com  Tue Nov 25 21:45:42 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Tue, 25 Nov 2008 21:45:42 +0100
Subject: Strange kolab behaviour....
In-Reply-To: <492B7F82.5050003@servinfo.ca>
References: <492B7F82.5050003@servinfo.ca>
Message-ID: <71fe4e760811251245x71d6c2b8ga097c1800af91c39@mail.gmail.com>

On Tue, Nov 25, 2008 at 5:30 AM, Christian Tardif
<christian.tardif at servinfo.ca> wrote:
> Hi Kolab Users!
>
> I have a strange problem for which I have no answer, so I'm asking...
>
> I have two servers: ambrosia.servinfo.ca (kolab server answering for
> servinfo.ca mails), and pegasus.servinfo.ca (which answers for
> echo.servinfo.ca (sympa mailing list)). For users anywhere on the Net,
> the mailing list system is working perfectly. But for servinfo.ca users,
> it does not. A user sending mail to (for example) test at echo.servinfo.ca
> will get its mail bounced, because ambrosia complains that
> test at servinfo.ca does not exists.
>
> I can see, also, that a mail sent to test at echo.servinfo.ca from anywhere
> (but not from servinfo.ca users) on the Net will get to its way. But
> users from ambrosia (servinfo.ca users) will get a mail, apparently sent
> to test at servinfo.ca. The won't be able to reply.
>
> Why is ambrosia server readdressing the mails not intended to be treated
> by himself? Can't they just get thru?  How do I fix that behaviour?
> This is rather annoying...  and it makes me mad (which is, also, quite
> annoying  :-))

read  "masquerade_domains" option in

http://www.postfix.org/postconf.5.html#masquerade_domains


>
> Thanks,
>
> --
> Christian Tardif
>
>
>
> _______________________________________________
> 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  Tue Nov 25 21:55:24 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Tue, 25 Nov 2008 21:55:24 +0100
Subject: Possible workaround(s) for mail user temporary suspension?
In-Reply-To: <492BDD73.3090300@FuH-E.de>
References: <492BDD73.3090300@FuH-E.de>
Message-ID: <71fe4e760811251255p2914099ckf86974aa0a3247e4@mail.gmail.com>

On Tue, Nov 25, 2008 at 12:11 PM, Christian R??ler <Roessler at fuh-e.de> wrote:
> Hallo everybody,
>
> I was searching for a possibility to suspend an user account (mail

What do you means by suspend ?

Able to read his mail but not eable to send ?
Even not ebale to access his mailbox ?
Email sent to him should bounce ?

> account, primarily). After a little bit of internet research I just
> found a wish for exactly the same thing:
> http://www.kolab.org/pipermail/kolab-devel/2005-August/004188.html
>
> Can anyone tell me if this suggestion is already implemented in Kolab,
> and I am just too dense today to find it? And, if not, has anyone a good
> work-around for this?


What I do, is to edit the ldap 'userPassword' attribute like that :

{SSHA}aAKCKsf+qzWqQUBhvpCZIHgXX23A/Tnz

into :

disabled{SSHA}aAKCKsf+qzWqQUBhvpCZIHgXX23A/Tnz

That way cannot login anymore but I keep the original password safe.

Regards.

>
> Best regards,
> Christian R??ler
>
> _______________________________________________
> 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 christian.tardif at servinfo.ca  Wed Nov 26 02:16:32 2008
From: christian.tardif at servinfo.ca (Christian Tardif)
Date: Tue, 25 Nov 2008 20:16:32 -0500
Subject: Strange kolab behaviour....
In-Reply-To: <71fe4e760811251245x71d6c2b8ga097c1800af91c39@mail.gmail.com>
References: <492B7F82.5050003@servinfo.ca>
	<71fe4e760811251245x71d6c2b8ga097c1800af91c39@mail.gmail.com>
Message-ID: <492CA370.6090402@servinfo.ca>

Alain Spineux wrote:
> On Tue, Nov 25, 2008 at 5:30 AM, Christian Tardif
> <christian.tardif at servinfo.ca> wrote:
>   
>> Hi Kolab Users!
>>
>> I have a strange problem for which I have no answer, so I'm asking...
>>
>> I have two servers: ambrosia.servinfo.ca (kolab server answering for
>> servinfo.ca mails), and pegasus.servinfo.ca (which answers for
>> echo.servinfo.ca (sympa mailing list)). For users anywhere on the Net,
>> the mailing list system is working perfectly. But for servinfo.ca users,
>> it does not. A user sending mail to (for example) test at echo.servinfo.ca
>> will get its mail bounced, because ambrosia complains that
>> test at servinfo.ca does not exists.
>>
>> I can see, also, that a mail sent to test at echo.servinfo.ca from anywhere
>> (but not from servinfo.ca users) on the Net will get to its way. But
>> users from ambrosia (servinfo.ca users) will get a mail, apparently sent
>> to test at servinfo.ca. The won't be able to reply.
>>
>> Why is ambrosia server readdressing the mails not intended to be treated
>> by himself? Can't they just get thru?  How do I fix that behaviour?
>> This is rather annoying...  and it makes me mad (which is, also, quite
>> annoying  :-))
>>     
>
> read  "masquerade_domains" option in
>
> http://www.postfix.org/postconf.5.html#masquerade_domains

Got it! Thanks!


-- 
Christian Tardif


From Roessler at FuH-E.de  Wed Nov 26 09:19:32 2008
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Wed, 26 Nov 2008 09:19:32 +0100
Subject: Possible workaround(s) for mail user temporary suspension?
In-Reply-To: <71fe4e760811251255p2914099ckf86974aa0a3247e4@mail.gmail.com>
References: <492BDD73.3090300@FuH-E.de>
	<71fe4e760811251255p2914099ckf86974aa0a3247e4@mail.gmail.com>
Message-ID: <492D0694.4020308@FuH-E.de>

Alain Spineux schrieb:

>> I was searching for a possibility to suspend an user account (mail
> What do you means by suspend ?
> Able to read his mail but not eable to send ?
> Even not ebale to access his mailbox ?
> Email sent to him should bounce ?

Well, I just need the 'suspended' user to stay in the LDAP tree for the 
posixAccount, also for the nss-ldap in the intranet, and as 
documentation that the user once existed.

But the user should not be able to log in anymore, and Kolab should not 
take emails for him/her. One could say that Kolab should behave like the 
uses does not exist.

>> Can anyone tell me if this suggestion is already implemented in Kolab,
>> and I am just too dense today to find it? And, if not, has anyone a good
>> work-around for this?
> What I do, is to edit the ldap 'userPassword' attribute like that :
> {SSHA}aAKCKsf+qzWqQUBhvpCZIHgXX23A/Tnz
> into :
> disabled{SSHA}aAKCKsf+qzWqQUBhvpCZIHgXX23A/Tnz
> That way cannot login anymore but I keep the original password safe.

Thank you for that hint, this will surely prove useful.

Best regards, and thanks for your answer,
Christian R??ler


From kcaesar at hotmail.com  Wed Nov 26 10:42:55 2008
From: kcaesar at hotmail.com (kiser Caesar)
Date: Wed, 26 Nov 2008 10:42:55 +0100
Subject: Trouble with a domain maintainer user..
Message-ID: <BLU122-W48D982FD2285D96388850CA30A0@phx.gbl>


Hello !

I have a strange trouble with a domain maintainer user..
I explain, when this user want affect per exemple some quota value and click submit, all seems ok..
But when this user return in the email account setting the value is not registered.

Can you tell me more on this trouble ?


Thanks
_________________________________________________________________
In?dit ! Des Emotic?nes D?jant?es! Installez les dans votre Messenger ! 
http://www.ilovemessenger.fr/Emoticones/EmoticonesDejantees.aspx
-------------- section suivante --------------
Une pi?ce jointe HTML a ?t? nettoy?e...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081126/f0e76d08/attachment.html

From aspineux at gmail.com  Thu Nov 27 07:48:59 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Thu, 27 Nov 2008 07:48:59 +0100
Subject: Possible workaround(s) for mail user temporary suspension?
In-Reply-To: <492D0694.4020308@FuH-E.de>
References: <492BDD73.3090300@FuH-E.de>
	<71fe4e760811251255p2914099ckf86974aa0a3247e4@mail.gmail.com>
	<492D0694.4020308@FuH-E.de>
Message-ID: <71fe4e760811262248x9760f18m2d62a737948d9187@mail.gmail.com>

On Wed, Nov 26, 2008 at 9:19 AM, Christian R??ler <Roessler at fuh-e.de> wrote:
> Alain Spineux schrieb:
>
>>> I was searching for a possibility to suspend an user account (mail
>> What do you means by suspend ?
>> Able to read his mail but not eable to send ?
>> Even not ebale to access his mailbox ?
>> Email sent to him should bounce ?
>
> Well, I just need the 'suspended' user to stay in the LDAP tree for the
> posixAccount, also for the nss-ldap in the intranet, and as
> documentation that the user once existed.

You can remove all the Kolab's related objectClass and their attributes.
Then these cleaned entry will be ignored by postfix and probably by
the weba admin interface too.
I dont know if any tools exist for this.


>
> But the user should not be able to log in anymore, and Kolab should not
> take emails for him/her. One could say that Kolab should behave like the
> uses does not exist.
>
>>> Can anyone tell me if this suggestion is already implemented in Kolab,
>>> and I am just too dense today to find it? And, if not, has anyone a good
>>> work-around for this?
>> What I do, is to edit the ldap 'userPassword' attribute like that :
>> {SSHA}aAKCKsf+qzWqQUBhvpCZIHgXX23A/Tnz
>> into :
>> disabled{SSHA}aAKCKsf+qzWqQUBhvpCZIHgXX23A/Tnz
>> That way cannot login anymore but I keep the original password safe.
>
> Thank you for that hint, this will surely prove useful.
>
> Best regards, and thanks for your answer,
> Christian R??ler
>
> _______________________________________________
> 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  Thu Nov 27 11:08:02 2008
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Thu, 27 Nov 2008 11:08:02 +0100
Subject: Possible workaround(s) for mail user temporary suspension?
In-Reply-To: <71fe4e760811262248x9760f18m2d62a737948d9187@mail.gmail.com>
References: <492BDD73.3090300@FuH-E.de>	
	<71fe4e760811251255p2914099ckf86974aa0a3247e4@mail.gmail.com>	
	<492D0694.4020308@FuH-E.de>
	<71fe4e760811262248x9760f18m2d62a737948d9187@mail.gmail.com>
Message-ID: <492E7182.6010106@FuH-E.de>

Alain Spineux schrieb:

>>>> I was searching for a possibility to suspend an user account (mail
>>> What do you means by suspend ?
>>> Able to read his mail but not eable to send ?
>>> Even not ebale to access his mailbox ?
>>> Email sent to him should bounce ?
>> Well, I just need the 'suspended' user to stay in the LDAP tree for the
>> posixAccount, also for the nss-ldap in the intranet, and as
>> documentation that the user once existed.
> You can remove all the Kolab's related objectClass and their attributes.
> Then these cleaned entry will be ignored by postfix and probably by
> the weba admin interface too. I dont know if any tools exist for this.

I also have not found any tools for this.

Well, I had just the same thoughts, so for trying it out I wrote a shell 
script that reads a given user entry, strips each Kolab related entry 
and object class from it and writes the Kolab related entries into an 
LDAP archive branch. After testing I notified Kolab really does not 
recognize the 'stripped' entry anymore. While that script is very, very 
buggy until now , I think it will suffice as 'proof of concept', so far.

I think it would be surely better if there wwould be a Kolab-integrated 
solution, I am sure I could live with this for a while. Unfortunately, 
while I am good at scripting I am really bad with PHP, so I see no 
chance for me to integrate this into the web frontend.

I do also see the problem that (with this solution) the disabling would 
be possible, as Kolab 'sees' the entry then; but not re-enabling, as 
Kolab would not see the disabled entry.

So I would be glad for a better solution, but as said, I think I have to 
live with the scripted solution for now.

Again, thanks for your hints!

Best regards,
Christian


From loic.elineau at benefacere.fr  Thu Nov 27 11:36:10 2008
From: loic.elineau at benefacere.fr (=?iso-8859-1?q?Lo=EFc_Elineau?=)
Date: Thu, 27 Nov 2008 11:36:10 +0100
Subject: Add logging info for untrusted sender
Message-ID: <200811271136.10514.loic.elineau@benefacere.fr>

Hi all,
Since a few days, we experience new kind of spam: somes use one of our address 
to send spam to the same address.
For example: spammers pretend being "contact at ourdomain.org" to send spams to 
"contact at ourdomain.org".
The result is, that the spam is effectively sent to "contact at ourdomain.org" 
even if the sender is prefixed with "UNTRUSTED"

Is there a way to block untrusted sender if they pretend being from a domain 
at the kolab server? Another solution should be to add logging info to 
portfix.log (and thus eject them thew fail2log). But how to achieve this?

best regards,

-- 
Lo?c Elineau
Bene Facere
http://www.benefacere.fr/


From NPrice at gibb.co.za  Thu Nov 27 12:02:28 2008
From: NPrice at gibb.co.za (Price,Neil)
Date: Thu, 27 Nov 2008 13:02:28 +0200
Subject: Add logging info for untrusted sender
Message-ID: <7B91BBC61758DD1183BE000C296D2CA7104C55@ct-exchange.wins.lawco.com>

On 27 November 2008 12:36 PM Lo?c Elineau wrote 

> Since a few days, we experience new kind of spam: somes use one of our
address 
> to send spam to the same address.
> For example: spammers pretend being "contact at ourdomain.org" to send spams
to 
> "contact at ourdomain.org".
> The result is, that the spam is effectively sent to
"contact at ourdomain.org" 
> even if the sender is prefixed with "UNTRUSTED"
> 
> Is there a way to block untrusted sender if they pretend being from a
domain 
> at the kolab server? Another solution should be to add logging info to 
> portfix.log (and thus eject them thew fail2log). But how to 
> achieve this?

I don't use this within Kolab as I use a Postfix relay server but on that
server I have

In main.cf:

smtpd_recipient_restrictions = (lots of stuff),
                               permit_mynetworks,
                               check_sender_access
hash:/etc/postfix/sender_checks,
                               (lots of stuff incl rbl checks)

And in /etc/postfix/sender_checks I have

# disallow any incoming supposedly from one of our peebles
arcus.co.za                     550 Illegal sender domain part
arcusgibb.co.za                 550 Illegal sender domain part
gibb.co.za                      550 Illegal sender domain part

Where these are my domains. Since my Kolab server is on a trusted network,
this rule does get applied to outgoing email. It blocks anyone attempting to
fake my domains.

I'm sure this could easily be adapted to a situation where the Kolab server
is not using a relay server.


From aspineux at gmail.com  Thu Nov 27 14:00:28 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Thu, 27 Nov 2008 14:00:28 +0100
Subject: Add logging info for untrusted sender
In-Reply-To: <200811271136.10514.loic.elineau@benefacere.fr>
References: <200811271136.10514.loic.elineau@benefacere.fr>
Message-ID: <71fe4e760811270500w2b215769q4b321f199225c40d@mail.gmail.com>

On Thu, Nov 27, 2008 at 11:36 AM, Lo?c Elineau
<loic.elineau at benefacere.fr> wrote:
> Hi all,
> Since a few days, we experience new kind of spam: somes use one of our address
> to send spam to the same address.
> For example: spammers pretend being "contact at ourdomain.org" to send spams to
> "contact at ourdomain.org".
> The result is, that the spam is effectively sent to "contact at ourdomain.org"
> even if the sender is prefixed with "UNTRUSTED"
>
> Is there a way to block untrusted sender if they pretend being from a domain
> at the kolab server? Another solution should be to add logging info to
> portfix.log (and thus eject them thew fail2log). But how to achieve this?
>
> best regards,

SPF is the solution, but their is no support integrated into kolab yet.

>
> --
> Lo?c Elineau
> Bene Facere
> http://www.benefacere.fr/
>
> _______________________________________________
> 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 loic.elineau at benefacere.fr  Thu Nov 27 15:33:47 2008
From: loic.elineau at benefacere.fr (=?iso-8859-1?q?Lo=EFc_Elineau?=)
Date: Thu, 27 Nov 2008 15:33:47 +0100
Subject: Add logging info for untrusted sender
In-Reply-To: <7B91BBC61758DD1183BE000C296D2CA7104C55@ct-exchange.wins.lawco.com>
References: <7B91BBC61758DD1183BE000C296D2CA7104C55@ct-exchange.wins.lawco.com>
Message-ID: <200811271533.48134.loic.elineau@benefacere.fr>

Thanks,
I'll give a look at kolab's postfix configuration and try this

> >
> > Is there a way to block untrusted sender if they pretend being from a
>
> domain
>
> > at the kolab server? Another solution should be to add logging info to
> > portfix.log (and thus eject them thew fail2log). But how to
> > achieve this?
>
> I don't use this within Kolab as I use a Postfix relay server but on that
> server I have
>
> In main.cf:
>
> smtpd_recipient_restrictions = (lots of stuff),
>                                permit_mynetworks,
>                                check_sender_access
> hash:/etc/postfix/sender_checks,
>                                (lots of stuff incl rbl checks)
>
> And in /etc/postfix/sender_checks I have
>
> # disallow any incoming supposedly from one of our peebles
> arcus.co.za                     550 Illegal sender domain part
> arcusgibb.co.za                 550 Illegal sender domain part
> gibb.co.za                      550 Illegal sender domain part
>
> Where these are my domains. Since my Kolab server is on a trusted network,
> this rule does get applied to outgoing email. It blocks anyone attempting
> to fake my domains.
>
> I'm sure this could easily be adapted to a situation where the Kolab server
> is not using a relay server.
>

Regards,

-- 
Lo?c Elineau
http://www.benefacere.fr/


From loic.elineau at benefacere.fr  Thu Nov 27 15:57:25 2008
From: loic.elineau at benefacere.fr (=?iso-8859-1?q?Lo=EFc_Elineau?=)
Date: Thu, 27 Nov 2008 15:57:25 +0100
Subject: Add logging info for untrusted sender
In-Reply-To: <71fe4e760811270500w2b215769q4b321f199225c40d@mail.gmail.com>
References: <200811271136.10514.loic.elineau@benefacere.fr>
	<71fe4e760811270500w2b215769q4b321f199225c40d@mail.gmail.com>
Message-ID: <200811271557.25756.loic.elineau@benefacere.fr>

I am not sure I explained my problem correctly:
Actually, every user who wants to send mail with our servers has to 
authenticate its SMTP connection. We don't trust any network at all.

The problem is, that when a user don't authenticate, the server relay the mail 
if the recipient is the same as the unauthentified sender, just prefixing the 
sender with "UNTRUSTED".

I don't want kolab to add "UNTRUSTED", I'd like it to respond with 550 error. 
I am not sure SPF will be the right solution for this problem. Is it?

Best regards,
> >
> > Is there a way to block untrusted sender if they pretend being from a
> > domain at the kolab server? Another solution should be to add logging
> > info to portfix.log (and thus eject them thew fail2log). But how to
> > achieve this?
> >
> > best regards,
>
> SPF is the solution, but their is no support integrated into kolab yet.

-- 
Lo?c Elineau
http://www.benefacere.fr/


From Roessler at FuH-E.de  Fri Nov 28 12:19:13 2008
From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=)
Date: Fri, 28 Nov 2008 12:19:13 +0100
Subject: Possible workaround(s) for mail user temporary suspension?
In-Reply-To: <492E7182.6010106@FuH-E.de>
References: <492BDD73.3090300@FuH-E.de>		<71fe4e760811251255p2914099ckf86974aa0a3247e4@mail.gmail.com>		<492D0694.4020308@FuH-E.de>	<71fe4e760811262248x9760f18m2d62a737948d9187@mail.gmail.com>
	<492E7182.6010106@FuH-E.de>
Message-ID: <492FD3B1.3030304@FuH-E.de>

Christian R??ler schrieb:

> Alain Spineux schrieb:
>>>>> I was searching for a possibility to suspend an user account (mail
>>>> What do you means by suspend ?
>>>> Able to read his mail but not eable to send ?
>>>> Even not ebale to access his mailbox ?
>>>> Email sent to him should bounce ?
>>> Well, I just need the 'suspended' user to stay in the LDAP tree for the
>>> posixAccount, also for the nss-ldap in the intranet, and as
>>> documentation that the user once existed.
>> You can remove all the Kolab's related objectClass and their attributes.
>> Then these cleaned entry will be ignored by postfix and probably by
>> the weba admin interface too. I dont know if any tools exist for this.
> I also have not found any tools for this. [...] Well, I had just the same
 > thoughts, so for trying it out I wrote a shell script that reads a given
 > user entry, strips each Kolab related entry and object class from it and
 > writes the Kolab related entries into an LDAP archive branch.

Well, me again - funny answering my own mail.

I have written three scripts (a wrapper script for deciding, a disabling 
script, an enabling script) for disabling and re-enabling users, and 
they are functioning so far. If someone would deem them useful for, 
perhaps, expanding them or using them as a base for writing better ones, 
I would gladly share them here.

But they were written quickly yesterday, and surely they have a lot of 
potential for optimizing, and a bit more debugging.

Best regards, Christian


From jaheme at gmx.de  Sat Nov 29 18:16:33 2008
From: jaheme at gmx.de (Jan - Hendrik Meyer)
Date: Sat, 29 Nov 2008 18:16:33 +0100
Subject: Horde problem/SSL problem
In-Reply-To: <49171B2C.2030809@gmx.de>
References: <4914AE91.1090600@gmx.de>	<20081109082938.542774wzzijjswco@webmail.pardus.de>
	<49171B2C.2030809@gmx.de>
Message-ID: <493178F1.4080100@gmx.de>

Hello,

this problem seems to relate only to this user - and I can solve it by 
recreating the account.

But some problems have survived the time:

1.) I've a Horde problem, too.
I can login with the Kolab users, but I can't see any email and calender 
functions - is there anything I could have forgotten?

I've used http://en.opensuse.org/Kolab to configure Horde!

2.) Another problem is, that there
If I want to use a mail programm like Kontact or Thunderbird I can't 
connect via ssl, only the standard imap port is working
If I want to send an email there is exactly the same problem. The SSL 
port 465 does not work while the port 25 is working well.

Of course, the firewall is open for these ports.

Do I need to create some extra certifications to use the ssl support of 
kolab or can this problem caused by something else?

Thanks

Jan-Hendrik


Jan - Hendrik Meyer schrieb:
> Hi,
>
> anbei ein LDIF Export des nicht funktionierenden Eintrages:
>
> <begin>
> version: 1
>
> # LDIF-Export f?r: cn=Norbert Langemeyer,ou=People,dc=home
> # Suchbereich: base
> # Suchfilter: (objectClass=*)
> # Anzahl der Listeneintr?ge: 1
>
> # Eintrag 1: cn=Norbert Langemeyer,ou=People,dc=home
> dn: cn=Norbert Langemeyer,ou=People,dc=home
> objectClass: kolabInetOrgPerson
> objectClass: shadowAccount
> objectClass: posixAccount
> objectClass: inetOrgPerson
> objectClass: organizationalPerson
> objectClass: person
> objectClass: hordePerson
> kolabInvitationPolicy: ACT_MANUAL
> kolabHomeServer: 192.168.0.1
> shadowWarning: 10
> shadowInactive: 10
> shadowMin: 1
> shadowMax: 365
> shadowLastChange: 14185
> homeDirectory: /home/norbertlang
> loginShell: /bin/bash
> uid: norbertlang
> cn: Norbert Langemeyer
> uidNumber: 20000
> gidNumber: 10002
> userPassword: {SSHA}1ezeZyrbCjlrtVOwZS28FIZq28SvYfRi
> sn: Langemeyer
> givenName: Norbert
> mail: norbert at home
> hordePrefs: default_identity:MA==
> hordePrefs: identities:YTowOnt9
> hordePrefs: confirm_email:YTowOnt9
> hordePrefs: id:
> hordePrefs: fullname:
> hordePrefs: from_addr:
> hordePrefs: security_question:
> hordePrefs: security_answer:
> hordePrefs: alternate_email:
> hordePrefs: language:
> hordePrefs: timezone:
> hordePrefs: twentyFour:
> hordePrefs: date_format:JXg=
> hordePrefs: first_week_day:MA==
> hordePrefs: theme:Ymx1ZXdoaXRl
> hordePrefs: categories:
> hordePrefs: category_colors:
> hordePrefs: summary_refresh_time:MzAw
> hordePrefs: show_sidebar:MQ==
> hordePrefs: sidebar_width:MTUw
> hordePrefs: menu_view:Ym90aA==
> hordePrefs: menu_refresh_time:MzAw
> hordePrefs: do_maintenance:MQ==
> hordePrefs: last_maintenance:MA==
> hordePrefs: confirm_maintenance:MQ==
> hordePrefs: initial_application:aG9yZGU=
> hordePrefs: widget_accesskey:MQ==
> hordePrefs: portal_layout:YToyOntpOjA7YToxOntpOjA7YTo0OntzOjM6ImFwcCI7czo1Oi
>  Job3JkZSI7czo2OiJoZWlnaHQiO2k6MTtzOjU6IndpZHRoIjtpOjE7czo2OiJwYXJhbXMiO2E6M
>  jp7czo0OiJ0eXBlIjtzOjQ6InRpbWUiO3M6NjoicGFyYW1zIjthOjI6e3M6MTM6Il9yZWZyZXNo
>  X3RpbWUiO3M6MToiMCI7czo0OiJ0aW1lIjtzOjc6IjI0LWhvdXIiO319fX1pOjE7YToxOntpOjA
>  7YTo0OntzOjM6ImFwcCI7czo1OiJob3JkZSI7czo2OiJoZWlnaHQiO2k6MTtzOjU6IndpZHRoIj
>  tpOjE7czo2OiJwYXJhbXMiO2E6Mjp7czo0OiJ0eXBlIjtzOjc6ImFjY291bnQiO3M6NjoicGFyY
>  W1zIjthOjA6e319fX19
> hordePrefs: remote_summaries:YTowOnt9
> hordePrefs: last_login:YToyOntzOjQ6InRpbWUiO2k6MTIyNTY0MjczMztzOjQ6Imhvc3QiO
>  3M6MTA6InBjMDA1LmhvbWUiO30=
> hordePrefs: show_last_login:MQ==
> hordePrefs: editor_plugins:YToyOntpOjA7czo4OiJMaXN0VHlwZSI7aToxO3M6MTI6IkNoY
>  XJhY3Rlck1hcCI7fQ==
> </end>
>
> I hope this helps to find a solution.
>
> Thanks
> Jan-Hendrik MEyer
>
> Gunnar Wrobel schrieb:
>   
>> Quoting Jan - Hendrik Meyer <jaheme at gmx.de>:
>>
>>     
>>>  Hello,
>>>
>>> after I installed so SuSe integration package sucessfully, I've started
>>> to integrate Linux authentification with ldap. I used the LDAP Account
>>> Manager to manage the account. I created a account with the unix schemas
>>> and the kolab schemas for testing.
>>> I can login the xserver and a mailbox has also been created.
>>>
>>> But there is one error:
>>>
>>> lmtp[29919]: verify_user(home!user.norbertlang) failed: Mailbox does 
>>> not exist
>>>
>>> I think the cause could be that the user name need to be different to 
>>> the username,
>>> if I use the kolab and unix schema
>>> (because the username doesn't support the @)
>>>       
>> I'm not 100% certain I understand how you merge the two schemas or how 
>> a user account looks in your case. Maybe you could attach an LDIF output.
>>
>> In any case a Kolab user should always have an email address as 
>> primary identifier. You may use the uid for any additional IDs and I 
>> think you should be able to use this one for uinx login.
>>
>> Cheers,
>>
>> Gunnar
>>
>>     
>>> Are there any solutions?
>>>
>>> Thanks
>>>
>>> Jan-Hendrik
>>>
>>> _______________________________________________
>>> 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
>
> No virus found in this incoming message.
> Checked by AVG - http://www.avg.com 
> Version: 8.0.169 / Virus Database: 270.9.0/1778 - Release Date: 09.11.2008 14:14
>
>
>
>   


From wrobel at pardus.de  Sat Nov 29 22:35:00 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sat, 29 Nov 2008 22:35:00 +0100
Subject: Log Rotation Question
In-Reply-To: <20081123184512.48472gaw2c9egj3c@portal.lios-koeln.de>
References: <1227090006l.24345l.0l@pc-adr2.lios-koeln.de>
	<20081123184512.48472gaw2c9egj3c@portal.lios-koeln.de>
Message-ID: <20081129223500.13926z1ud9jqcq88@webmail.pardus.de>

Quoting Albrecht Dre? <albrecht.dress at lios-tech.com>:

> Quoting Albrecht Dre? <albrecht.dress at lios-tech.com>:
>> looking through the log files of my Kolab 2.2.0 installation, it seems
>> as if the files in the folders
>>
>> /kolab/var/kolab-filter/log
>> /kolab/var/kolab-freebusy/log
>>
>> are not being rotated.
>
> Having a closer look at it, this seems to be a bug
> <https://www.intevation.de/roundup/kolab/issue3264>.
>
> Furthermore, the file /kolab/var/kolab-filter/log/fatal.log contains
> lots of messages like
>
> PHP Notice:  Undefined index:  xxx in
> /kolab/lib/php/Kolab/Filter/Resource.php on line yyy
>
> Now, is this just a notice which can be ignored (as the entry
> suggests), or is this a fata error (as the file name implies)?  The
> same applies also for /kolab/var/kolab-freebusy/log/php-error.log, btw.

The notices can in fact be ignored. Though I hope they are gone with  
Kolab Server 2.2.1.

The reason why this appears in a log called "fatal.log": For  
Kolab_Filter we have the special situation that we *never* *ever* want  
it to really fail and abort as this is handling mails. So once we hit  
programming errors, I want to see this in fatal.log. This specific log  
is catching all programming errors I made and this also includes the  
notices even if those are not fatal. It would be too much effort to  
make the distinction between a notice and a fatal error.

And in fact we shouldn't have PHP notices anywhere in the code. This  
is just a clean PHP coding practice. I know older Kolab server  
versions simply turned of these notices and now that I turned them on  
we see many such things from the Kolab webadmin but that needs to get  
fixed eventually.

Cheers,

Gunnar

>
> Thanks, Albrecht.
>
> _______________________________________________
> 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/20081129/c84e922b/attachment.bin

From wrobel at pardus.de  Sat Nov 29 22:54:06 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sat, 29 Nov 2008 22:54:06 +0100
Subject: Add logging info for untrusted sender
In-Reply-To: <200811271557.25756.loic.elineau@benefacere.fr>
References: <200811271136.10514.loic.elineau@benefacere.fr>
	<71fe4e760811270500w2b215769q4b321f199225c40d@mail.gmail.com>
	<200811271557.25756.loic.elineau@benefacere.fr>
Message-ID: <20081129225406.977471nqljgy4p44@webmail.pardus.de>

Quoting Lo?c Elineau <loic.elineau at benefacere.fr>:

> I am not sure I explained my problem correctly:
> Actually, every user who wants to send mail with our servers has to
> authenticate its SMTP connection. We don't trust any network at all.
>
> The problem is, that when a user don't authenticate, the server  
> relay the mail
> if the recipient is the same as the unauthentified sender, just prefixing the
> sender with "UNTRUSTED".
>
> I don't want kolab to add "UNTRUSTED", I'd like it to respond with 550 error.

Should be possible by switching to "Reject forged from header" in the  
Kolab web admin "Service" tab.

Cheers,

Gunnar

> I am not sure SPF will be the right solution for this problem. Is it?
>
> Best regards,
>> >
>> > Is there a way to block untrusted sender if they pretend being from a
>> > domain at the kolab server? Another solution should be to add logging
>> > info to portfix.log (and thus eject them thew fail2log). But how to
>> > achieve this?
>> >
>> > best regards,
>>
>> SPF is the solution, but their is no support integrated into kolab yet.
>
> --
> Lo?c Elineau
> http://www.benefacere.fr/
>
> _______________________________________________
> 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/20081129/97be48f4/attachment.bin

From wrobel at pardus.de  Sat Nov 29 22:55:38 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sat, 29 Nov 2008 22:55:38 +0100
Subject: Trouble with a domain maintainer user..
In-Reply-To: <BLU122-W48D982FD2285D96388850CA30A0@phx.gbl>
References: <BLU122-W48D982FD2285D96388850CA30A0@phx.gbl>
Message-ID: <20081129225538.809756vnt6pyvmo0@webmail.pardus.de>


Quoting kiser Caesar <kcaesar at hotmail.com>:

> Hello !
>
> I have a strange trouble with a domain maintainer user..
> I explain, when this user want affect per exemple some quota value
> and click submit, all seems ok..
> But when this user return in the email account setting the value is
> not registered.
>
> Can you tell me more on this trouble ?

I think this is an open bug in the Kolab web admin. Did you check our  
bug database? It might also have been resolved for Kolab Server 2.2.1  
already.

Cheers,

Gunnar

>
>
> Thanks
>
> -------------------------
> Souhaitez vous  ? ?tre au bureau sans y ?tre ? ?
target=\"_new\"
>
href=\"http://www.microsoft.com/france/windows/bts/default.mspx\">Oui
> je le veux !

-- 
____ 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/20081129/c8ae0fda/attachment.bin

From wrobel at pardus.de  Sat Nov 29 23:03:51 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sat, 29 Nov 2008 23:03:51 +0100
Subject: DB Error: not found with Horde and Kolab
In-Reply-To: <200811242058.46844.oszwald@web.de>
References: <200811242058.46844.oszwald@web.de>
Message-ID: <20081129230351.21175jzgywmqlnk0@webmail.pardus.de>

Quoting Florian Oszwald <oszwald at web.de>:

> Hi all,
>
> I now have horde installed working together with kolab on opensuse 10.2.
>
> The problem is, that i get the message DB Error: not found everytime I log in
> on a new day or making a new entry in the calendar or in notes.
>
> In /var/log/horde/horde.log I do not get any useful information about this
> problem. On the internet I found, that it might be related to the SQL, but I
> am using it together with Kolab, so there is no need for sql, is there?

Correct. In general there is no need for a database. If Horde gives  
you this error the configuration provided by the package maintainers  
is broken and you should submit a bug concerning the package.

For newer Horde/Kolab installations you need a database if you want to  
use SyncML. But it should be sufficient if this is based on sqlite and  
I see it as a package maintainers task to provide a correctly  
preconfigured database in that case.

Cheers,

Gunnar

>
> Thank you very much in advance.
> Regards,
> Florian
>
> _______________________________________________
> 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/20081129/d02dc586/attachment-0001.bin

From wrobel at pardus.de  Sat Nov 29 23:07:16 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sat, 29 Nov 2008 23:07:16 +0100
Subject: Possible workaround(s) for mail user temporary suspension?
In-Reply-To: <492FD3B1.3030304@FuH-E.de>
References: <492BDD73.3090300@FuH-E.de>
	<71fe4e760811251255p2914099ckf86974aa0a3247e4@mail.gmail.com>
	<492D0694.4020308@FuH-E.de>
	<71fe4e760811262248x9760f18m2d62a737948d9187@mail.gmail.com>
	<492E7182.6010106@FuH-E.de> <492FD3B1.3030304@FuH-E.de>
Message-ID: <20081129230716.211676ob8brj6ko4@webmail.pardus.de>

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

> Christian R??ler schrieb:
>
>> Alain Spineux schrieb:
>>>>>> I was searching for a possibility to suspend an user account (mail
>>>>> What do you means by suspend ?
>>>>> Able to read his mail but not eable to send ?
>>>>> Even not ebale to access his mailbox ?
>>>>> Email sent to him should bounce ?
>>>> Well, I just need the 'suspended' user to stay in the LDAP tree for the
>>>> posixAccount, also for the nss-ldap in the intranet, and as
>>>> documentation that the user once existed.
>>> You can remove all the Kolab's related objectClass and their attributes.
>>> Then these cleaned entry will be ignored by postfix and probably by
>>> the weba admin interface too. I dont know if any tools exist for this.
>> I also have not found any tools for this. [...] Well, I had just the same
>  > thoughts, so for trying it out I wrote a shell script that reads a given
>  > user entry, strips each Kolab related entry and object class from it and
>  > writes the Kolab related entries into an LDAP archive branch.
>
> Well, me again - funny answering my own mail.
>
> I have written three scripts (a wrapper script for deciding, a disabling
> script, an enabling script) for disabling and re-enabling users, and
> they are functioning so far. If someone would deem them useful for,
> perhaps, expanding them or using them as a base for writing better ones,
> I would gladly share them here.

As you mentioned there is a bug already requesting such a feature I'd  
suggest you attach the scripts there. We are very happy about any such  
contribution!

The Wiki might also be a good place for things like this.

Cheers,

Gunnar

>
> But they were written quickly yesterday, and surely they have a lot of
> potential for optimizing, and a bit more debugging.
>
> 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/20081129/178b517b/attachment.bin

From wrobel at pardus.de  Sat Nov 29 23:31:04 2008
From: wrobel at pardus.de (Gunnar Wrobel)
Date: Sat, 29 Nov 2008 23:31:04 +0100
Subject: Horde problem/SSL problem
In-Reply-To: <493178F1.4080100@gmx.de>
References: <4914AE91.1090600@gmx.de>
	<20081109082938.542774wzzijjswco@webmail.pardus.de>
	<49171B2C.2030809@gmx.de> <493178F1.4080100@gmx.de>
Message-ID: <20081129233104.46204bd4nz9kkv6s@webmail.pardus.de>

Quoting Jan - Hendrik Meyer <jaheme at gmx.de>:

> Hello,
>
> this problem seems to relate only to this user - and I can solve it by
> recreating the account.
>
> But some problems have survived the time:
>
> 1.) I've a Horde problem, too.
> I can login with the Kolab users, but I can't see any email and calender
> functions - is there anything I could have forgotten?
>
> I've used http://en.opensuse.org/Kolab to configure Horde!

Something about this still seems to be broken because there were  
several OpenSuse users reporting problems with Suse. Please contact  
the maintainers of that port.

You could also try to install a Kolab/OpenPKG server and get the Horde  
configuration from there. The OpenPKG version will in general be much  
more stable than any of the native ports.

Cheers,

Gunnar

>
> 2.) Another problem is, that there
> If I want to use a mail programm like Kontact or Thunderbird I can't
> connect via ssl, only the standard imap port is working
> If I want to send an email there is exactly the same problem. The SSL
> port 465 does not work while the port 25 is working well.
>
> Of course, the firewall is open for these ports.
>
> Do I need to create some extra certifications to use the ssl support of
> kolab or can this problem caused by something else?
>
> Thanks
>
> Jan-Hendrik
>
>
> Jan - Hendrik Meyer schrieb:
>> Hi,
>>
>> anbei ein LDIF Export des nicht funktionierenden Eintrages:
>>
>> <begin>
>> version: 1
>>
>> # LDIF-Export f?r: cn=Norbert Langemeyer,ou=People,dc=home
>> # Suchbereich: base
>> # Suchfilter: (objectClass=*)
>> # Anzahl der Listeneintr?ge: 1
>>
>> # Eintrag 1: cn=Norbert Langemeyer,ou=People,dc=home
>> dn: cn=Norbert Langemeyer,ou=People,dc=home
>> objectClass: kolabInetOrgPerson
>> objectClass: shadowAccount
>> objectClass: posixAccount
>> objectClass: inetOrgPerson
>> objectClass: organizationalPerson
>> objectClass: person
>> objectClass: hordePerson
>> kolabInvitationPolicy: ACT_MANUAL
>> kolabHomeServer: 192.168.0.1
>> shadowWarning: 10
>> shadowInactive: 10
>> shadowMin: 1
>> shadowMax: 365
>> shadowLastChange: 14185
>> homeDirectory: /home/norbertlang
>> loginShell: /bin/bash
>> uid: norbertlang
>> cn: Norbert Langemeyer
>> uidNumber: 20000
>> gidNumber: 10002
>> userPassword: {SSHA}1ezeZyrbCjlrtVOwZS28FIZq28SvYfRi
>> sn: Langemeyer
>> givenName: Norbert
>> mail: norbert at home
>> hordePrefs: default_identity:MA==
>> hordePrefs: identities:YTowOnt9
>> hordePrefs: confirm_email:YTowOnt9
>> hordePrefs: id:
>> hordePrefs: fullname:
>> hordePrefs: from_addr:
>> hordePrefs: security_question:
>> hordePrefs: security_answer:
>> hordePrefs: alternate_email:
>> hordePrefs: language:
>> hordePrefs: timezone:
>> hordePrefs: twentyFour:
>> hordePrefs: date_format:JXg=
>> hordePrefs: first_week_day:MA==
>> hordePrefs: theme:Ymx1ZXdoaXRl
>> hordePrefs: categories:
>> hordePrefs: category_colors:
>> hordePrefs: summary_refresh_time:MzAw
>> hordePrefs: show_sidebar:MQ==
>> hordePrefs: sidebar_width:MTUw
>> hordePrefs: menu_view:Ym90aA==
>> hordePrefs: menu_refresh_time:MzAw
>> hordePrefs: do_maintenance:MQ==
>> hordePrefs: last_maintenance:MA==
>> hordePrefs: confirm_maintenance:MQ==
>> hordePrefs: initial_application:aG9yZGU=
>> hordePrefs: widget_accesskey:MQ==
>> hordePrefs: portal_layout:YToyOntpOjA7YToxOntpOjA7YTo0OntzOjM6ImFwcCI7czo1Oi
>>  Job3JkZSI7czo2OiJoZWlnaHQiO2k6MTtzOjU6IndpZHRoIjtpOjE7czo2OiJwYXJhbXMiO2E6M
>>  jp7czo0OiJ0eXBlIjtzOjQ6InRpbWUiO3M6NjoicGFyYW1zIjthOjI6e3M6MTM6Il9yZWZyZXNo
>>  X3RpbWUiO3M6MToiMCI7czo0OiJ0aW1lIjtzOjc6IjI0LWhvdXIiO319fX1pOjE7YToxOntpOjA
>>  7YTo0OntzOjM6ImFwcCI7czo1OiJob3JkZSI7czo2OiJoZWlnaHQiO2k6MTtzOjU6IndpZHRoIj
>>  tpOjE7czo2OiJwYXJhbXMiO2E6Mjp7czo0OiJ0eXBlIjtzOjc6ImFjY291bnQiO3M6NjoicGFyY
>>  W1zIjthOjA6e319fX19
>> hordePrefs: remote_summaries:YTowOnt9
>> hordePrefs: last_login:YToyOntzOjQ6InRpbWUiO2k6MTIyNTY0MjczMztzOjQ6Imhvc3QiO
>>  3M6MTA6InBjMDA1LmhvbWUiO30=
>> hordePrefs: show_last_login:MQ==
>> hordePrefs: editor_plugins:YToyOntpOjA7czo4OiJMaXN0VHlwZSI7aToxO3M6MTI6IkNoY
>>  XJhY3Rlck1hcCI7fQ==
>> </end>
>>
>> I hope this helps to find a solution.
>>
>> Thanks
>> Jan-Hendrik MEyer
>>
>> Gunnar Wrobel schrieb:
>>
>>> Quoting Jan - Hendrik Meyer <jaheme at gmx.de>:
>>>
>>>
>>>>  Hello,
>>>>
>>>> after I installed so SuSe integration package sucessfully, I've started
>>>> to integrate Linux authentification with ldap. I used the LDAP Account
>>>> Manager to manage the account. I created a account with the unix schemas
>>>> and the kolab schemas for testing.
>>>> I can login the xserver and a mailbox has also been created.
>>>>
>>>> But there is one error:
>>>>
>>>> lmtp[29919]: verify_user(home!user.norbertlang) failed: Mailbox does
>>>> not exist
>>>>
>>>> I think the cause could be that the user name need to be different to
>>>> the username,
>>>> if I use the kolab and unix schema
>>>> (because the username doesn't support the @)
>>>>
>>> I'm not 100% certain I understand how you merge the two schemas or how
>>> a user account looks in your case. Maybe you could attach an LDIF output.
>>>
>>> In any case a Kolab user should always have an email address as
>>> primary identifier. You may use the uid for any additional IDs and I
>>> think you should be able to use this one for uinx login.
>>>
>>> Cheers,
>>>
>>> Gunnar
>>>
>>>
>>>> Are there any solutions?
>>>>
>>>> Thanks
>>>>
>>>> Jan-Hendrik
>>>>
>>>> _______________________________________________
>>>> 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
>>
>> No virus found in this incoming message.
>> Checked by AVG - http://www.avg.com
>> Version: 8.0.169 / Virus Database: 270.9.0/1778 - Release Date:  
>> 09.11.2008 14:14
>>
>>
>>
>>
>
> _______________________________________________
> 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/20081129/c719319f/attachment.bin

From aspineux at gmail.com  Sun Nov 30 06:46:37 2008
From: aspineux at gmail.com (Alain Spineux)
Date: Sun, 30 Nov 2008 06:46:37 +0100
Subject: Add logging info for untrusted sender
In-Reply-To: <200811271557.25756.loic.elineau@benefacere.fr>
References: <200811271136.10514.loic.elineau@benefacere.fr>
	<71fe4e760811270500w2b215769q4b321f199225c40d@mail.gmail.com>
	<200811271557.25756.loic.elineau@benefacere.fr>
Message-ID: <71fe4e760811292146p59d6f60aqb4c9f486a388c454@mail.gmail.com>

On Thu, Nov 27, 2008 at 3:57 PM, Lo?c Elineau
<loic.elineau at benefacere.fr> wrote:
> I am not sure I explained my problem correctly:
> Actually, every user who wants to send mail with our servers has to
> authenticate its SMTP connection. We don't trust any network at all.
>
> The problem is, that when a user don't authenticate, the server relay the mail
> if the recipient is the same as the unauthentified sender, just prefixing the
> sender with "UNTRUSTED".
>
> I don't want kolab to add "UNTRUSTED", I'd like it to respond with 550 error.
> I am not sure SPF will be the right solution for this problem. Is it?


Sorry I didn(t know about the "UNTRUSTED" label added by kolab, I was
thinking about
something else.
Do you want to deny any unauthenticated connection ?

>
> Best regards,
>> >
>> > Is there a way to block untrusted sender if they pretend being from a
>> > domain at the kolab server? Another solution should be to add logging
>> > info to portfix.log (and thus eject them thew fail2log). But how to
>> > achieve this?
>> >
>> > best regards,
>>
>> SPF is the solution, but their is no support integrated into kolab yet.
>
> --
> Lo?c Elineau
> http://www.benefacere.fr/
>



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


From till at kdab.net  Mon Nov 17 08:52:11 2008
From: till at kdab.net (Till Adam)
Date: Mon, 17 Nov 2008 07:52:11 -0000
Subject: Making "Room Number" visible in Kontact address book?
In-Reply-To: <200811041338.52707.itsef-admin@brightsight.com>
References: <200811041338.52707.itsef-admin@brightsight.com>
Message-ID: <200811170852.02680.till@kdab.net>

Hey Thomas,

On Tuesday 04 November 2008 13:38:52 ITSEF Admin wrote:

> Another usage question: One of the fields one can fill in for a user in the
> Kolab webadmin interface is the "Room Number". I find it quite handy to
> have, however, until now I have not succeeded in making this entry visible
> in Kontact (e.g. when doing an LDAP search). Does anyone out there have a
> hint for me? Thanks in advance!

Currently the kolab format does not define a room number attribute for 
contacts, and the other Kolab clients (including Kontact) thus do not offer 
it. It sounds like a useful thing to me, and should be an easy addition, so if 
you could file an issue in the roundup requesting this field to be added, 
we'll work on that including it, if possible.

Thanks for your input, 

Till

-- 
Till Adam
KDAB - platform independent software services
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kolab.org/pipermail/kolab-users/attachments/20081117/c879c91e/attachment.html