From rs at blinkenlichten.de Wed Oct 1 10:18:27 2008 From: rs at blinkenlichten.de (Rouven Sacha) Date: Wed, 01 Oct 2008 10:18:27 +0200 Subject: Kolabd crashes after deleting user In-Reply-To: <200809302338.17403.ml@radoeka.nl> References: <1222768494.6804.33.camel@campocampo> <200809301307.14217.ml@radoeka.nl> <48E23982.7050200@blinkenlichten.de> <200809302338.17403.ml@radoeka.nl> Message-ID: <48E33253.8080403@blinkenlichten.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Richard Bos schrieb: >> installing libnet-ldap-perl from debian unstable (0.38-1) as recommended >> doesn't help either, kolabd now crashes immediately on startup, just as >> you encountered it. > Hmm, interesting ;) What version did you use before? Can you make a diff > between the 2? I used 0.37 up till now. However, 0.38 provides 2 bug fixes: - From which of the 40 perl modules in libnet-ldap-perl should i make a diff of? > bserver-netsrv:~# dpkg -L libnet-ldap-perl|grep .pm$|wc -l > 40 Cheers, Rouven - -- Blinkenlichten Open Source Solutions Eigm?ller, Maass, Sacha GbR Weigandufer 45 12059 Berlin tel: +49 30 13896247 fax: +49 30 13896249 mobil: +49 174 4220127 http://www.blinkenlichten.de/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI4zJTuYBpvajAnXYRAoZEAKCvvRRzlzxhJ6f6JFiP2QxvgLBxnwCeLIXw k4aLsWMcNJn6aWY+HcuSQns= =a2e7 -----END PGP SIGNATURE----- From rs at blinkenlichten.de Wed Oct 1 11:32:43 2008 From: rs at blinkenlichten.de (Rouven Sacha) Date: Wed, 01 Oct 2008 11:32:43 +0200 Subject: [SOLVED] Re: Kolabd crashes after deleting user In-Reply-To: <48E33253.8080403@blinkenlichten.de> References: <1222768494.6804.33.camel@campocampo> <200809301307.14217.ml@radoeka.nl> <48E23982.7050200@blinkenlichten.de> <200809302338.17403.ml@radoeka.nl> <48E33253.8080403@blinkenlichten.de> Message-ID: <48E343BB.30200@blinkenlichten.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rouven Sacha schrieb: > Richard Bos schrieb: > >>> installing libnet-ldap-perl from debian unstable (0.38-1) as recommended >>> doesn't help either, kolabd now crashes immediately on startup, just as >>> you encountered it. The patch from Mathieu Parent from https://www.intevation.de/roundup/kolab/msg16878 seems to fix these issues for me. I succesfully created and deleted a user in the frontend and kolabd synced these changes successfully without crashing! Thanks for your help! Cheers, Rouven - -- Blinkenlichten Open Source Solutions Eigm?ller, Maass, Sacha GbR Weigandufer 45 12059 Berlin tel: +49 30 13896247 fax: +49 30 13896249 mobil: +49 174 4220127 http://www.blinkenlichten.de/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI40O7uYBpvajAnXYRAoTcAKCDSW6AufyICie1mD00IZ649v1YrQCgsZ66 Ty2e9FYBZU5Le/IavUJn2Ms= =r67S -----END PGP SIGNATURE----- From wrobel at pardus.de Wed Oct 1 16:47:39 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Wed, 01 Oct 2008 16:47:39 +0200 Subject: Multi-domains in Kolab 2.2.0 final. In-Reply-To: References: Message-ID: <20081001164739.30192xyx2xli8zuo@webmail.pardus.de> Quoting kiser Caesar : > Hello, > > I have a strange problem with Kolab 2.2.0 final, I just install a > new server and I configured as follows: > > A primary domain such as "domain.ext" and several > sub-domains such as the "subdomain1.domain.ext", > "subdomain2.domain.ext" ..... > > In the web administration page I can see my users in different > areas, but when I want sending emails from one of sub-domains, mail > arrive at my correspondent is in the form toto at domain.ext and not in > toto at subdomain.ext. > > Who have an idea about this problem? Who can help me? Alains comment is correct. The problem is caused by the masquerading in postfix. I don't think the domain functionality was constructed with subdomains in mind. It works with domain-a.ext and domain-b.ext but not domain-a.ext and sub.domain-a.ext. You should open a bug in the issue tracker about this. > > Then I have another question, how many slave server a master server > can support? This should be limited by the hardware of the master server. It will mainly relay mails through postfix and provide the central LDAP server. With decent hardware many slaves should be possible. Cheers, Gunnar > > Thank you! > > ------------------------- > Votre correspondant a choisi Hotmail et profite d'un stockage > quasiment illimit?. href=\"http://www.windowslive.fr/hotmail/default.asp\"> Cr?ez un > compte Hotmail gratuitement ! -- ____ 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. From wrobel at pardus.de Wed Oct 1 16:52:48 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Wed, 01 Oct 2008 16:52:48 +0200 Subject: Horde LDAP errors In-Reply-To: <4975.170.130.105.186.1222781709.squirrel@webmail.gibb.co.za> References: <4975.170.130.105.186.1222781709.squirrel@webmail.gibb.co.za> Message-ID: <20081001165248.48091okm2y8qur40@webmail.pardus.de> Quoting "Price,Neil" : > I'm seeing the following in my horde log file: > > HORDE [error] [horde] Internal LDAP error. Details have been logged for > the administrator. [pid 20612 on line 337 of > "/usr/share/horde3/lib/Horde/Prefs/ldap.php"] > HORDE [error] [horde] Zero or more than one DN returned from search; > unable to determine user's correct DN > > I don't see see any corresponding errors in the ldap log (unless I have > not enabled the correct log level) > > Horde version is 3.3 with Kolab 2.20 (Debian port). Test.php shows I have > pecl'd all my pears correctly. That version is still rather fresh and not yet fully Kolab tested to be honest. I need to get my patches straight for that one soon. > > Horde still seems to work but does not retrieve Kolab user info (I'm not > sure if its supposed to. I checked the search dn and the password are > correct (phppw) > > Any pointers? Do you log in with a uid/email that is present more than once in your LDAP tree? Cheers, Gunnar > > > _______________________________________________ > Kolab-users mailing list > Kolab-users at kolab.org > https://kolab.org/mailman/listinfo/kolab-users > -- ____ http://www.pardus.de _________________ http://gunnarwrobel.de _ E-mail : p at rdus.de Dr. Gunnar Wrobel Tel. : +49 700 6245 0000 Bundesstrasse 29 Fax : +49 721 1513 52322 D-20146 Hamburg -------------------------------------------------------------------- >> Mail at ease - Rent a kolab groupware server at p at rdus << -------------------------------------------------------------------- ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From antony.java at gmail.com Wed Oct 1 16:54:37 2008 From: antony.java at gmail.com (Antony Raj) Date: Wed, 1 Oct 2008 20:24:37 +0530 Subject: Integration of Kolab with Active Directory Message-ID: Dear guys, Is there a documentation that states the integration of Kolab with Active Directory? If there is, please let me know about it? -- Regards Antony Raj. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://kolab.org/pipermail/kolab-users/attachments/20081001/125c70a6/attachment.html From wrobel at pardus.de Wed Oct 1 16:57:50 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Wed, 01 Oct 2008 16:57:50 +0200 Subject: Integration of Kolab with Active Directory In-Reply-To: References: Message-ID: <20081001165750.67897kahh6uezcgs@webmail.pardus.de> Quoting Antony Raj : > Dear guys, > > Is there a documentation that states the integration of Kolab with > Active Directory? > > If there is, please let me know about it? Hm, I personally don't know of such documents but as we have code specific to AD there might be such a thing. Bernhard? Cheers, Gunnar > > > -- > Regards > Antony Raj. > -- ____ 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. From antony.java at gmail.com Wed Oct 1 17:02:41 2008 From: antony.java at gmail.com (Antony Raj) Date: Wed, 1 Oct 2008 20:32:41 +0530 Subject: Integration of Kolab with Active Directory In-Reply-To: <20081001165750.67897kahh6uezcgs@webmail.pardus.de> References: <20081001165750.67897kahh6uezcgs@webmail.pardus.de> Message-ID: Please share it with us Regards Antony Raj On Wed, Oct 1, 2008 at 8:27 PM, Gunnar Wrobel wrote: > > Quoting Antony Raj : > > > Dear guys, > > > > Is there a documentation that states the integration of Kolab with > > Active Directory? > > > > If there is, please let me know about it? > > Hm, I personally don't know of such documents but as we have code > specific to AD there might be such a thing. > > Bernhard? > > Cheers, > > Gunnar > > > > > > > -- > > Regards > > Antony Raj. > > > > -- > ____ 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 > -- Regards Antony Raj. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://kolab.org/pipermail/kolab-users/attachments/20081001/7ba3ad45/attachment.html From aspineux at gmail.com Wed Oct 1 21:50:43 2008 From: aspineux at gmail.com (Alain Spineux) Date: Wed, 1 Oct 2008 21:50:43 +0200 Subject: Multi-domains in Kolab 2.2.0 final. In-Reply-To: <20081001164739.30192xyx2xli8zuo@webmail.pardus.de> References: <20081001164739.30192xyx2xli8zuo@webmail.pardus.de> Message-ID: <71fe4e760810011250r3f7b3acfke2a81bdcb26d1dd8@mail.gmail.com> On Wed, Oct 1, 2008 at 4:47 PM, Gunnar Wrobel wrote: > > Quoting kiser Caesar : > >> Hello, >> >> I have a strange problem with Kolab 2.2.0 final, I just install a >> new server and I configured as follows: >> >> A primary domain such as "domain.ext" and several >> sub-domains such as the "subdomain1.domain.ext", >> "subdomain2.domain.ext" ..... >> >> In the web administration page I can see my users in different >> areas, but when I want sending emails from one of sub-domains, mail >> arrive at my correspondent is in the form toto at domain.ext and not > in >> toto at subdomain.ext. >> >> Who have an idea about this problem? Who can help me? > > Alains comment is correct. The problem is caused by the masquerading > in postfix. I don't think the domain functionality was constructed > with subdomains in mind. It works with domain-a.ext and domain-b.ext > but not domain-a.ext and sub.domain-a.ext. > > You should open a bug in the issue tracker about this. A bug ? Are you sure ? Kolab want to hide other SMTP in the LAN, but not sub-domain, only computer. How to make the difference between computer.domain.com and sub.domain.com both looks the same. This is a "feature" of kolab ! In fact this look more like an useless feature ! Regards > >> >> Then I have another question, how many slave server a master server >> can support? > > This should be limited by the hardware of the master server. It will > mainly relay mails through postfix and provide the central LDAP > server. With decent hardware many slaves should be possible. > > Cheers, > > Gunnar > >> >> Thank you! >> >> ------------------------- >> Votre correspondant a choisi Hotmail et profite d'un stockage >> quasiment illimit?. > href=\"http://www.windowslive.fr/hotmail/default.asp\"> Cr?ez un >> compte Hotmail gratuitement ! > > -- > ____ 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 > -- Alain Spineux aspineux gmail com May the sources be with you From bernhard.reiter at intevation.de Thu Oct 2 10:13:45 2008 From: bernhard.reiter at intevation.de (Bernhard Reiter) Date: Thu, 2 Oct 2008 10:13:45 +0200 Subject: Integration of Kolab with Active Directory In-Reply-To: <20081001165750.67897kahh6uezcgs@webmail.pardus.de> References: <20081001165750.67897kahh6uezcgs@webmail.pardus.de> Message-ID: <200810021013.49650.bernhard.reiter@intevation.de> On Wednesday 01 October 2008 16:57, Gunnar Wrobel wrote: > Quoting Antony Raj : > > Is there a documentation that states the integration of Kolab with > > Active Directory? > > > > If there is, please let me know about it? > > Hm, I personally don't know of such documents but as we have code ? > specific to AD there might be such a thing. > > Bernhard? I am not aware of such a document. Did you try searching the wiki and the mailing archives? The South African company Codefusion (which does not exist anymore for other reasons) did a couple of projects coupling AD and Kolab Server, that is were the source code came from, it probably needs a retest. There was a proprietary product claiming to couple Kolab Server and AD once, but I had no experience with it. At the core Active Directory is a directory server also offering LDAP. Kolab Server can be coupled with many directory servers that speak LDAP, you need to put in the additional attributes, make sure you get triggered on changes and decide which management interface to use. (That is the basic work-schedule for such a project.) Bernhard -- Managing Director - Owner: www.intevation.net (Free Software Company) Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com. Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://kolab.org/pipermail/kolab-users/attachments/20081002/900e73f0/attachment.bin From antony.java at gmail.com Thu Oct 2 10:25:40 2008 From: antony.java at gmail.com (Antony Raj) Date: Thu, 2 Oct 2008 13:55:40 +0530 Subject: Integration of Kolab with Active Directory In-Reply-To: <200810021013.49650.bernhard.reiter@intevation.de> References: <20081001165750.67897kahh6uezcgs@webmail.pardus.de> <200810021013.49650.bernhard.reiter@intevation.de> Message-ID: Bernard, Thanks for your response. I tried searching to get a page that talks about Active Directory, I couldn't find any. Do I have access to that code, so that I can test it? I understand that I will have to add Kolab specific attribute into Active Directory, but I would like to know where all I would be expected to change the configuration? Am I expected to change the code for the same as well? With Warm Regards Antony Raj. On Thu, Oct 2, 2008 at 1:43 PM, Bernhard Reiter < bernhard.reiter at intevation.de> wrote: > On Wednesday 01 October 2008 16:57, Gunnar Wrobel wrote: > > Quoting Antony Raj : > > > > Is there a documentation that states the integration of Kolab with > > > Active Directory? > > > > > > If there is, please let me know about it? > > > > Hm, I personally don't know of such documents but as we have code > > specific to AD there might be such a thing. > > > > Bernhard? > > I am not aware of such a document. > Did you try searching the wiki and the mailing archives? > > The South African company Codefusion (which does not exist anymore for > other > reasons) did a couple of projects coupling AD and Kolab Server, that is > were > the source code came from, it probably needs a retest. There was a > proprietary product claiming to couple Kolab Server and AD once, but I had > no > experience with it. > > At the core Active Directory is a directory server also offering LDAP. > Kolab Server can be coupled with many directory servers that speak LDAP, > you > need to put in the additional attributes, make sure you get triggered on > changes and decide which management interface to use. (That is the basic > work-schedule for such a project.) > > Bernhard > > -- > Managing Director - Owner: www.intevation.net (Free Software > Company) > Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com. > Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 > Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner > > _______________________________________________ > Kolab-users mailing list > Kolab-users at kolab.org > https://kolab.org/mailman/listinfo/kolab-users > > -- Regards Antony Raj. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://kolab.org/pipermail/kolab-users/attachments/20081002/f5420dbf/attachment.html From alessio at skye.it Thu Oct 2 12:06:57 2008 From: alessio at skye.it (Alessio Cecchi) Date: Thu, 2 Oct 2008 12:06:57 +0200 Subject: Integration of Kolab with Active Directory In-Reply-To: <200810021013.49650.bernhard.reiter@intevation.de> References: <20081001165750.67897kahh6uezcgs@webmail.pardus.de> <200810021013.49650.bernhard.reiter@intevation.de> Message-ID: <200810021206.57562.alessio@skye.it> Il Thursday 02 October 2008 10:13:45 Bernhard Reiter ha scritto: > > Quoting Antony Raj : > > > Is there a documentation that states the integration of Kolab with > > > Active Directory? > > > > > > If there is, please let me know about it? > > > > Hm, I personally don't know of such documents but as we have code ? > > specific to AD there might be such a thing. > > > > Bernhard? > > I am not aware of such a document. > Did you try searching the wiki and the mailing archives? I have found this: http://osdir.com/ml/kde.kolab.user/2006-02/msg00032.html Ciao -- Alessio Cecchi is: @ ILS -> http://www.linux.it/~alessice/ Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/ @ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it @ LOLUG -> neo-Socio http://www.lolug.net From bernhard at intevation.de Thu Oct 2 16:24:08 2008 From: bernhard at intevation.de (Bernhard Reiter) Date: Thu, 2 Oct 2008 16:24:08 +0200 Subject: kdepim enterprise35 for debian lenny In-Reply-To: <200809142248.20940.michael@mailwurm.org> References: <200809142248.20940.michael@mailwurm.org> Message-ID: <200810021624.09647.bernhard@intevation.de> On Sunday 14 September 2008 22:48, Michael wrote: > (repackage) debian etch kdepim-enterprise35 packages for debian > lenny. ? > > To install please put this lines in your sources.list: > > deb http://mailwurm.org lenny kdepim-enterprise35 > deb-src http://mailwurm.org lenny kdepim-enterprise35 BTW: I could successfully rebuild from the source-packages kdepim_3.5.9.enterprise.0.20080908.858460-mm1 a version for powerpc for Debian unstable (sid) 20080922. (Haven't tested the binaries yet.) -- Managing Director - Owner: www.intevation.net (Free Software Company) Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com. Intevation GmbH, Neuer Graben 17, Osnabr?ck, DE; AG Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://kolab.org/pipermail/kolab-users/attachments/20081002/37af0e76/attachment.bin From mark at rtsw.co.uk Fri Oct 3 12:50:47 2008 From: mark at rtsw.co.uk (Mark Seagrief) Date: Fri, 3 Oct 2008 11:50:47 +0100 Subject: Kolab 2.2 upgrade from 2.1 failure on php-channel-horde Message-ID: <200810031150.47986.mark@rtsw.co.uk> Hi, I kicked off an upgrade of a Kolab installation last night to upgrade from 2.1.0 to 2.2.0. I'm installing from source on Ubuntu 7.04 server edition with kernel 2.6.20-16-server. Most of the RPMs seem to have built correctly and installed fine, but php-channel-horde seems to have failed. The final few lines of the log are: Package Horde_Alarm-0.1.0.tgz done Tag the released code with `pear cvstag Alarm/package.xml' (or set the CVS tag RELEASE_0_1_0 by hand) + env 'PHP_PEAR_PHP_BIN=/kolab/bin/php -d safe_mode=off -d memory_limit=40M' PHP_PEAR_CACHE_DIR=/kolab/RPM/TMP/pear/cache /kolab/bin/pear install --force --loose --nodeps --offline --packagingroot=/kolab/RPM/TMP/horde-framework-kolab-3.2_rc3-root Horde_Alarm-0.1.0.tgz could not extract the package.xml file from "Horde_Alarm-0.1.0.tgz" Cannot download non-local package "Horde_Alarm-0.1.0.tgz" Package "Horde_Alarm-0.1.0.tgz" is not valid install failed error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.48129 (%install) I've check on the system and I do have a file that has been created called Horde_Alarm-0.1.0.tgz in /kolab/RPM/TMP/framework/ Any ideas as to what is causing this problem? Anybody encountered something similar? I'm going to grab another machine and try an installtion of 2.2 from scratch and see if that helps/exhibits this problem. Many thanks, Mark -- Mark Seagrief RT Software From jaheme at gmx.de Fri Oct 3 14:19:43 2008 From: jaheme at gmx.de (Jan - Hendrik Meyer) Date: Fri, 03 Oct 2008 14:19:43 +0200 Subject: A problem with mail delivering In-Reply-To: <48DFAD42.20002@gmx.de> References: <48DFAD42.20002@gmx.de> Message-ID: <48E60DDF.3010605@gmx.de> Hello, after changing some rights, the cyrus server is working correctly. The messages I've written don't appear anymore. But without any error message, no message I've written can be found in the cyrus imap postbox. It's empty. I tested with the command: echo $(date) | mailx -s test noname at home Postfix shows some messages like this: Sep 29 20:29:33 lxmain postfix/smtp[32013]: D699C22C24C: to=, orig_to=, relay=127.0.0.1[127.0.0.1]:10024, delay=0.57, delays=0.18/0.02/0.01/0.37, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 582D322C2AA) Sep 29 20:29:33 lxmain postfix/qmgr[31785]: D699C22C24C: removed Sep 29 20:29:33 lxmain postfix/pipe[32018]: 582D322C2AA: to=, relay=kolabmailboxfilter, delay=0.28, delays=0.06/0.02/0/0.2, dsn=2.0.0, status=sent (delivered via kolabmailboxfilter service) Sep 29 20:29:33 lxmain postfix/qmgr[31785]: 582D322C2AA: removed and amavis seems to scan the message: Sep 29 20:29:33 lxmain.Home /usr/sbin/amavisd[31563]: (31563-01) Passed, -> , quarantine D-8O1JfSg7tV, Message-ID: <20080929182932.9D8F322C2AA at lxmain.Home>, Hits: 2.34 Sep 29 20:29:33 lxmain.Home /usr/sbin/amavisd[31563]: (31563-01) Passed CLEAN, -> , Hits: 2.34, tag=3, tag2=6.3, kill=6.3, queued_as: 582D322C2AA, L/0/0/0 Maybe this is a message, that indicates a error: Oct 3 08:45:43 lxmain imap[26981]: dracconn: localhost: RPC: Program not registered Oct 3 08:45:43 lxmain imap[26981]: DRAC notifications disabled Does anyone know what the problem could be? Thanks Jan-Hendrik Meyer Jan - Hendrik Meyer schrieb: > Hello, > > Thanks for the help last time - it worked for me > > But there are 2 more errors i've found in the logfiles and experienced > by not receiving mails: > . > 1.) The following line can be found in the warn file and mail.err file > in my log directory: > > Sep 28 08:46:40 lxmain kolabquotawarn[22664]: fatal: Unable to connect > to local Cyrus admin interface > > 2.) Furthermore the next line can be found in the mail file: > > Sep 28 17:38:49 lxmain postfix/pipe[29242]: 328B522C2AB: to=, relay=kolabmailboxfilter, delay=377537, delays=377513/0.03/0/24, dsn=4.3.0, status=deferred (temporary failure. Command output: Failed to connect socket: Connection refused, original code ) > > > There is one process called cyrus in my process table and there is no > other clue determined the error. > > Last but not least, I can't log in with my ldap users in horde web > frontend after configurating horde. No error can be found in the horde log. > > > I hope for some good solutions ;) > > Thanks > > Jan-Hendrik Meyer > > _______________________________________________ > 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.7.5/1696 - Release Date: 28.09.2008 13:30 > > > > From fastfish at gmail.com Mon Oct 6 23:12:31 2008 From: fastfish at gmail.com (Bazooka Joe) Date: Mon, 6 Oct 2008 13:12:31 -0800 Subject: Can't log into IMAP server In-Reply-To: <20080822193725.36837332galtcv40@webmail2.pardus.de> References: <6b789da50808201107v592ab25foc5c4ded124e444f6@mail.gmail.com> <71fe4e760808201200p59d03cd2t431609b74302ef8a@mail.gmail.com> <6b789da50808201337hb2d3360l4c0471b0930d1c75@mail.gmail.com> <20080822193725.36837332galtcv40@webmail2.pardus.de> Message-ID: <6b789da50810061412u525e2bc7y25f94730aa0db0f1@mail.gmail.com> I did a full os and kolab reinstall and have the same problem. I was able to telnet and got a response from ports 143 On Fri, Aug 22, 2008 at 9:37 AM, Gunnar Wrobel wrote: > Quoting "Bazooka Joe" : > >> I was using full email addr as user name. >> >> Tbird doesn't even ask me for pw - I don't think imap is working. > > Did kolabconf run fine and configure your system correctly? If you had > errors running the kolabconf script you would see these in the syslog. > > Cheers, > > Gunnar > >> >> >> >> On Wed, Aug 20, 2008 at 11:00 AM, Alain Spineux wrote: >>> On Wed, Aug 20, 2008 at 8:07 PM, Bazooka Joe wrote: >>>> New to Kolab - first install - added 2 users >>>> >>>> Problem - Can't log in to IMAP server as users. >>>> >>>> Horde responds - >>>> "Login failed because your username or password was entered incorrectly." >>>> >>>> Thunderbird - >>>> "Connection to server timed out" >>>> >>>> I have the crymaster service running which is what I understand takes >>>> the imap connection. >>>> >>>> I just noticed I also have all these hung quota processes as well >>>> >>>> kolab 2572 0.0 0.0 5836 1480 ? S 03:30 0:00 crond >>>> kolab 2577 0.0 0.6 14328 12620 ? Ss 03:30 0:00 >>>> /kolab/bin/perl /kolab/etc/kolab/kolabquotawarn >>> >>> >>> You most use the email address to login, including the domain ! >>> >>> >>>> >>>> thx >>>> -bazooka >>>> >>>> _______________________________________________ >>>> 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 >> > > > > -- > ____ http://www.pardus.de _________________ http://gunnarwrobel.de _ > > E-mail : p at rdus.de Dr. Gunnar Wrobel > Tel. : +49 700 6245 0000 Bundesstrasse 29 > Fax : +49 721 1513 52322 D-20146 Hamburg > -------------------------------------------------------------------- > >> Mail at ease - Rent a kolab groupware server at p at rdus << > -------------------------------------------------------------------- > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > _______________________________________________ > Kolab-users mailing list > Kolab-users at kolab.org > https://kolab.org/mailman/listinfo/kolab-users > From fastfish at gmail.com Mon Oct 6 23:19:14 2008 From: fastfish at gmail.com (Bazooka Joe) Date: Mon, 6 Oct 2008 13:19:14 -0800 Subject: Can't log into IMAP server In-Reply-To: <20080822193725.36837332galtcv40@webmail2.pardus.de> References: <6b789da50808201107v592ab25foc5c4ded124e444f6@mail.gmail.com> <71fe4e760808201200p59d03cd2t431609b74302ef8a@mail.gmail.com> <6b789da50808201337hb2d3360l4c0471b0930d1c75@mail.gmail.com> <20080822193725.36837332galtcv40@webmail2.pardus.de> Message-ID: <6b789da50810061419l50a59005vcf06a75770254c34@mail.gmail.com> sorry i didn't mean to send that yet. and ports 993, 389 everything seems to be running problem - can't login in horde get bad username/passwd error for username i am using full email addr -bazooka On Fri, Aug 22, 2008 at 9:37 AM, Gunnar Wrobel wrote: > Quoting "Bazooka Joe" : > >> I was using full email addr as user name. >> >> Tbird doesn't even ask me for pw - I don't think imap is working. > > Did kolabconf run fine and configure your system correctly? If you had > errors running the kolabconf script you would see these in the syslog. > > Cheers, > > Gunnar > >> >> >> >> On Wed, Aug 20, 2008 at 11:00 AM, Alain Spineux wrote: >>> On Wed, Aug 20, 2008 at 8:07 PM, Bazooka Joe wrote: >>>> New to Kolab - first install - added 2 users >>>> >>>> Problem - Can't log in to IMAP server as users. >>>> >>>> Horde responds - >>>> "Login failed because your username or password was entered incorrectly." >>>> >>>> Thunderbird - >>>> "Connection to server timed out" >>>> >>>> I have the crymaster service running which is what I understand takes >>>> the imap connection. >>>> >>>> I just noticed I also have all these hung quota processes as well >>>> >>>> kolab 2572 0.0 0.0 5836 1480 ? S 03:30 0:00 crond >>>> kolab 2577 0.0 0.6 14328 12620 ? Ss 03:30 0:00 >>>> /kolab/bin/perl /kolab/etc/kolab/kolabquotawarn >>> >>> >>> You most use the email address to login, including the domain ! >>> >>> >>>> >>>> thx >>>> -bazooka >>>> >>>> _______________________________________________ >>>> 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 >> > > > > -- > ____ http://www.pardus.de _________________ http://gunnarwrobel.de _ > > E-mail : p at rdus.de Dr. Gunnar Wrobel > Tel. : +49 700 6245 0000 Bundesstrasse 29 > Fax : +49 721 1513 52322 D-20146 Hamburg > -------------------------------------------------------------------- > >> Mail at ease - Rent a kolab groupware server at p at rdus << > -------------------------------------------------------------------- > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > _______________________________________________ > Kolab-users mailing list > Kolab-users at kolab.org > https://kolab.org/mailman/listinfo/kolab-users > From fastfish at gmail.com Mon Oct 6 23:24:09 2008 From: fastfish at gmail.com (Bazooka Joe) Date: Mon, 6 Oct 2008 13:24:09 -0800 Subject: Can't log into IMAP server In-Reply-To: <6b789da50810061419l50a59005vcf06a75770254c34@mail.gmail.com> References: <6b789da50808201107v592ab25foc5c4ded124e444f6@mail.gmail.com> <71fe4e760808201200p59d03cd2t431609b74302ef8a@mail.gmail.com> <6b789da50808201337hb2d3360l4c0471b0930d1c75@mail.gmail.com> <20080822193725.36837332galtcv40@webmail2.pardus.de> <6b789da50810061419l50a59005vcf06a75770254c34@mail.gmail.com> Message-ID: <6b789da50810061424r44ee5c03x534f1d17d7e0a575@mail.gmail.com> ***SOLVED**** I was installing this on a local network and nothing was resolving. in /etc/hosts file I added domain given in kolab conf and it worked. 127.0.0.1 kolab1.domain.tdl kolab1 -bazooka On Mon, Oct 6, 2008 at 1:19 PM, Bazooka Joe wrote: > sorry i didn't mean to send that yet. > > and ports 993, 389 > > everything seems to be running > > problem - can't login in horde get bad username/passwd error > > for username i am using full email addr > > -bazooka > > On Fri, Aug 22, 2008 at 9:37 AM, Gunnar Wrobel wrote: >> Quoting "Bazooka Joe" : >> >>> I was using full email addr as user name. >>> >>> Tbird doesn't even ask me for pw - I don't think imap is working. >> >> Did kolabconf run fine and configure your system correctly? If you had >> errors running the kolabconf script you would see these in the syslog. >> >> Cheers, >> >> Gunnar >> >>> >>> >>> >>> On Wed, Aug 20, 2008 at 11:00 AM, Alain Spineux wrote: >>>> On Wed, Aug 20, 2008 at 8:07 PM, Bazooka Joe wrote: >>>>> New to Kolab - first install - added 2 users >>>>> >>>>> Problem - Can't log in to IMAP server as users. >>>>> >>>>> Horde responds - >>>>> "Login failed because your username or password was entered incorrectly." >>>>> >>>>> Thunderbird - >>>>> "Connection to server timed out" >>>>> >>>>> I have the crymaster service running which is what I understand takes >>>>> the imap connection. >>>>> >>>>> I just noticed I also have all these hung quota processes as well >>>>> >>>>> kolab 2572 0.0 0.0 5836 1480 ? S 03:30 0:00 crond >>>>> kolab 2577 0.0 0.6 14328 12620 ? Ss 03:30 0:00 >>>>> /kolab/bin/perl /kolab/etc/kolab/kolabquotawarn >>>> >>>> >>>> You most use the email address to login, including the domain ! >>>> >>>> >>>>> >>>>> thx >>>>> -bazooka >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >> >> >> >> -- >> ____ http://www.pardus.de _________________ http://gunnarwrobel.de _ >> >> E-mail : p at rdus.de Dr. Gunnar Wrobel >> Tel. : +49 700 6245 0000 Bundesstrasse 29 >> Fax : +49 721 1513 52322 D-20146 Hamburg >> -------------------------------------------------------------------- >> >> Mail at ease - Rent a kolab groupware server at p at rdus << >> -------------------------------------------------------------------- >> >> >> ---------------------------------------------------------------- >> This message was sent using IMP, the Internet Messaging Program. >> >> _______________________________________________ >> Kolab-users mailing list >> Kolab-users at kolab.org >> https://kolab.org/mailman/listinfo/kolab-users >> > From wrobel at pardus.de Tue Oct 7 09:41:01 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Tue, 07 Oct 2008 09:41:01 +0200 Subject: A problem with mail delivering In-Reply-To: <48E60DDF.3010605@gmx.de> References: <48DFAD42.20002@gmx.de> <48E60DDF.3010605@gmx.de> Message-ID: <20081007094101.19345yn9ajhh7ssg@webmail.pardus.de> Quoting Jan - Hendrik Meyer : > Hello, > > after changing some rights, Meaning you don't use the OpenPKG based installation? You should always state the Kolab version you are using in error reports as it makes it easier for us to identify possible error sources. > the cyrus server is working correctly. > The messages I've written don't appear anymore. > > But without any error message, no message I've written can be found in > the cyrus imap postbox. It's empty. > I tested with the command: > > echo $(date) | mailx -s test noname at home > > Postfix shows some messages like this: > > Sep 29 20:29:33 lxmain postfix/smtp[32013]: D699C22C24C: > to=, orig_to=, > relay=127.0.0.1[127.0.0.1]:10024, delay=0.57, > delays=0.18/0.02/0.01/0.37, dsn=2.0.0, status=sent (250 2.0.0 Ok: > queued as 582D322C2AA) > Sep 29 20:29:33 lxmain postfix/qmgr[31785]: D699C22C24C: removed > Sep 29 20:29:33 lxmain postfix/pipe[32018]: 582D322C2AA: > to=, relay=kolabmailboxfilter, delay=0.28, > delays=0.06/0.02/0/0.2, dsn=2.0.0, status=sent (delivered via > kolabmailboxfilter service) > Sep 29 20:29:33 lxmain postfix/qmgr[31785]: 582D322C2AA: removed > > and > > amavis seems to scan the message: > > Sep 29 20:29:33 lxmain.Home /usr/sbin/amavisd[31563]: (31563-01) > Passed, -> , quarantine D-8O1JfSg7tV, > Message-ID: <20080929182932.9D8F322C2AA at lxmain.Home>, Hits: 2.34 > Sep 29 20:29:33 lxmain.Home /usr/sbin/amavisd[31563]: (31563-01) > Passed CLEAN, -> , Hits: 2.34, tag=3, > tag2=6.3, kill=6.3, queued_as: 582D322C2AA, L/0/0/0 > > Maybe this is a message, that indicates a error: > > Oct 3 08:45:43 lxmain imap[26981]: dracconn: localhost: RPC: > Program not registered > Oct 3 08:45:43 lxmain imap[26981]: DRAC notifications disabled > > Does anyone know what the problem could be? What does the lmtp log say? Cheers, Gunnar > > Thanks > > Jan-Hendrik Meyer > > > > Jan - Hendrik Meyer schrieb: >> Hello, >> >> Thanks for the help last time - it worked for me >> >> But there are 2 more errors i've found in the logfiles and experienced >> by not receiving mails: >> . >> 1.) The following line can be found in the warn file and mail.err file >> in my log directory: >> >> Sep 28 08:46:40 lxmain kolabquotawarn[22664]: fatal: Unable to connect >> to local Cyrus admin interface >> >> 2.) Furthermore the next line can be found in the mail file: >> >> Sep 28 17:38:49 lxmain postfix/pipe[29242]: 328B522C2AB: >> to=, relay=kolabmailboxfilter, delay=377537, >> delays=377513/0.03/0/24, dsn=4.3.0, status=deferred (temporary >> failure. Command output: Failed to connect socket: Connection >> refused, original code ) >> >> >> There is one process called cyrus in my process table and there is no >> other clue determined the error. >> >> Last but not least, I can't log in with my ldap users in horde web >> frontend after configurating horde. No error can be found in the horde log. >> >> >> I hope for some good solutions ;) >> >> Thanks >> >> Jan-Hendrik Meyer >> >> _______________________________________________ >> 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.7.5/1696 - Release Date: >> 28.09.2008 13:30 >> >> >> >> > > _______________________________________________ > 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/20081007/eb3bee21/attachment.bin From wrobel at pardus.de Tue Oct 7 09:52:22 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Tue, 07 Oct 2008 09:52:22 +0200 Subject: Integration of Kolab with Active Directory In-Reply-To: References: <20081001165750.67897kahh6uezcgs@webmail.pardus.de> <200810021013.49650.bernhard.reiter@intevation.de> Message-ID: <20081007095222.4306793fctjz9lpy@webmail.pardus.de> Quoting Antony Raj : > Bernard, > > Thanks for your response. I tried searching to get a page that talks > about Active Directory, > I couldn't find any. > Do I have access to that code, so that I can test it? The ad code is part of perl kolab (see also our cvs: http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/perl-kolab/lib/Kolab/LDAP/Backend/ad.pm) Cheers, Gunnar > > I understand that I will have to add Kolab specific attribute into > Active Directory, but I would like to know where all I would be > expected to change the configuration? > Am I expected to change the code for the same as well? > > With Warm Regards > Antony Raj. > > > On Thu, Oct 2, 2008 at 1:43 PM, Bernhard > Reiter dir=\"ltr\"> wrote: > 0pt 0.8ex; padding-left: 1ex;\" class=\"gmail_quote\"> class=\"Ih2E3d\">On Wednesday 01 October 2008 16:57, Gunnar Wrobel > wrote: > > Quoting Antony Raj : > > > Is there a documentation > that states the integration of Kolab with > > > Active Directory? > > > > > > If there is, please let me know about it? > > > > Hm, I personally don't know of such documents but as we have > code > specific to AD there might be such a thing. > > > > Bernhard? > I am not aware of such a document. > Did you try searching the wiki and the mailing archives? > The South African company Codefusion (which does not exist anymore > for other > reasons) did a couple of projects coupling AD and Kolab Server, > that is were > the source code came from, it probably needs a retest. There was a > proprietary product claiming to couple Kolab Server and AD once, > but I had no > experience with it. > At the core Active Directory is a directory server also offering > LDAP. > Kolab Server can be coupled with many directory servers that speak > LDAP, you > need to put in the additional attributes, make sure you get > triggered on > changes and decide which management interface to use. (That is the > basic > work-schedule for such a project.) > Bernhard > -- > Managing Director - Owner: href=\"http://www.intevation.net\">www.intevation.net > (Free Software Company) > Germany Coordinator: href=\"http://fsfeurope.org\">fsfeurope.org. Coordinator: target=\"_blank\" > href=\"http://www.Kolab-Konsortium.com\">www.Kolab-Konsortium.com. > Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 > Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver > Wagner > _______________________________________________ > Kolab-users mailing list > Kolab-users at kolab.org[3] > href=\"https://kolab.org/mailman/listinfo/kolab-users\">https://kolab.org/mailman/listinfo/kolab-users -- Regards Antony Raj. -- ____ 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:bernhard.reiter at intevation.de [2] mailto:antony.java at gmail.com [3] mailto:Kolab-users at kolab.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From wrobel at pardus.de Tue Oct 7 09:57:04 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Tue, 07 Oct 2008 09:57:04 +0200 Subject: Kolab 2.2 upgrade from 2.1 failure on php-channel-horde In-Reply-To: <200810031150.47986.mark@rtsw.co.uk> References: <200810031150.47986.mark@rtsw.co.uk> Message-ID: <20081007095704.177818rd30oyknk0@webmail.pardus.de> Quoting Mark Seagrief : > Hi, > > I kicked off an upgrade of a Kolab installation last night to upgrade from > 2.1.0 to 2.2.0. > > I'm installing from source on Ubuntu 7.04 server edition with kernel > 2.6.20-16-server. > > Most of the RPMs seem to have built correctly and installed fine, but > php-channel-horde seems to have failed. > > The final few lines of the log are: > > > Package Horde_Alarm-0.1.0.tgz done > Tag the released code with `pear cvstag Alarm/package.xml' > (or set the CVS tag RELEASE_0_1_0 by hand) > + env 'PHP_PEAR_PHP_BIN=/kolab/bin/php -d safe_mode=off -d memory_limit=40M' > PHP_PEAR_CACHE_DIR=/kolab/RPM/TMP/pear/cache /kolab/bin/pear install --force > --loose --nodeps --offline > --packagingroot=/kolab/RPM/TMP/horde-framework-kolab-3.2_rc3-root > Horde_Alarm-0.1.0.tgz > could not extract the package.xml file from "Horde_Alarm-0.1.0.tgz" > Cannot download non-local package "Horde_Alarm-0.1.0.tgz" > Package "Horde_Alarm-0.1.0.tgz" is not valid > install failed > error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.48129 (%install) These lines seem to originate from the horde-framework installation rather than from php-channel-horde. Can you post the log messages concerning php-channel-horde since you say compilation failed for that one. Cheers, Gunnar > > > I've check on the system and I do have a file that has been created called > Horde_Alarm-0.1.0.tgz in /kolab/RPM/TMP/framework/ > > Any ideas as to what is causing this problem? Anybody encountered something > similar? > > I'm going to grab another machine and try an installtion of 2.2 from scratch > and see if that helps/exhibits this problem. > > Many thanks, > > Mark > > -- > > Mark Seagrief > RT Software > > _______________________________________________ > 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/20081007/68600612/attachment.bin From wrobel at pardus.de Tue Oct 7 10:02:45 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Tue, 07 Oct 2008 10:02:45 +0200 Subject: Server fqdn change In-Reply-To: <200809290142.07088.akopciuch@bddf.ca> References: <3256.170.130.105.186.1222150609.squirrel@webmail.gibb.co.za> <200809252222.22513.ml@radoeka.nl> <20080929070624.14302cbghsuceatc@webmail.pardus.de> <200809290142.07088.akopciuch@bddf.ca> Message-ID: <20081007100245.13667bbe8mqttv48@webmail.pardus.de> Quoting "Andrew J. Kopciuch" : >> >> I guess the old domain should be kept. Renaming all the users does not >> make too much sense as that also affects the data stored in IMAP. Its >> easier to solve that by using aliases. >> > > Not to mention the breakage of the mail itself. The mail spool is stored on > disk under the domain. That would have to be moved, and I have no idea about > the side-effects of that. > > You already mentioned the ACLs stored in IMAP, which would also be broken. > There's also the sieve and freebusy information that would need to be moved, > and I'm also not sure about any data changes required there. > > To throw another wrench in the mix, imagine multiple slaves? > > There are several pieces that are tied to the FQDN, both in LDAP, > and on disk. > It's not a trivial thing to change the FQDN. > > Aliases could instantly provide a new email address, but the UID would still > remain under the previous domain (if you just used the default UID ... which > I assume most people would). > > I realize I am not providing much help here, but my brain is flying in all > directions thinking about what a FQDN change would require. Large > installations would be a massive amount of work. > > We all seem to be making points in theory. I am wondering if there is anyone > out there who has actually done this before? They might provide some > insights. > > The only client of mine to go through a domain change, was moving > co-locations, and rebuilding servers all at the same time, so we just built a > new server under the new domain, and created aliases for the old domain if > needed. So we avoided doing this sort of thing in place. You definitely added some very valid points and I think the simple conclusion is that a script at this point would be way too much effort for the rather small gain. Cheers, Gunnar > > :S > > > Andy > > -- ____ 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. From devgioiatech at gmail.com Tue Oct 7 12:28:44 2008 From: devgioiatech at gmail.com (Antonio Straziota) Date: Tue, 7 Oct 2008 12:28:44 +0200 Subject: Can't log into IMAP server In-Reply-To: <6b789da50810061424r44ee5c03x534f1d17d7e0a575@mail.gmail.com> References: <6b789da50808201107v592ab25foc5c4ded124e444f6@mail.gmail.com> <71fe4e760808201200p59d03cd2t431609b74302ef8a@mail.gmail.com> <6b789da50808201337hb2d3360l4c0471b0930d1c75@mail.gmail.com> <20080822193725.36837332galtcv40@webmail2.pardus.de> <6b789da50810061419l50a59005vcf06a75770254c34@mail.gmail.com> <6b789da50810061424r44ee5c03x534f1d17d7e0a575@mail.gmail.com> Message-ID: hi all, i have the same problem... In the past i solved the problem on a 2.2rc3 in the same way... but now, on a fresh install of 2.2.0 it doesn't work. i tried all telnet and all service respond to it. i check also ps ax | grep cyrmaster 28605 pts/0 R+ 0:00 grep cyrmaster 31398 ? Ss 0:00 /kolab/bin/cyrmaster -d Then i suppose all works correctly. However if i try to run /kolab/bin/cyradm -u manager localhost the console hangs. It should prompt for the password...but nothing happen Any idea? Thanks in advance 2008/10/6 Bazooka Joe > ***SOLVED**** > > I was installing this on a local network and nothing was resolving. > > in /etc/hosts file I added domain given in kolab conf and it worked. > > 127.0.0.1 kolab1.domain.tdl kolab1 > > -bazooka > > On Mon, Oct 6, 2008 at 1:19 PM, Bazooka Joe wrote: > > sorry i didn't mean to send that yet. > > > > and ports 993, 389 > > > > everything seems to be running > > > > problem - can't login in horde get bad username/passwd error > > > > for username i am using full email addr > > > > -bazooka > > > > On Fri, Aug 22, 2008 at 9:37 AM, Gunnar Wrobel wrote: > >> Quoting "Bazooka Joe" : > >> > >>> I was using full email addr as user name. > >>> > >>> Tbird doesn't even ask me for pw - I don't think imap is working. > >> > >> Did kolabconf run fine and configure your system correctly? If you had > >> errors running the kolabconf script you would see these in the syslog. > >> > >> Cheers, > >> > >> Gunnar > >> > >>> > >>> > >>> > >>> On Wed, Aug 20, 2008 at 11:00 AM, Alain Spineux > wrote: > >>>> On Wed, Aug 20, 2008 at 8:07 PM, Bazooka Joe > wrote: > >>>>> New to Kolab - first install - added 2 users > >>>>> > >>>>> Problem - Can't log in to IMAP server as users. > >>>>> > >>>>> Horde responds - > >>>>> "Login failed because your username or password was entered > incorrectly." > >>>>> > >>>>> Thunderbird - > >>>>> "Connection to server timed out" > >>>>> > >>>>> I have the crymaster service running which is what I understand takes > >>>>> the imap connection. > >>>>> > >>>>> I just noticed I also have all these hung quota processes as well > >>>>> > >>>>> kolab 2572 0.0 0.0 5836 1480 ? S 03:30 0:00 > crond > >>>>> kolab 2577 0.0 0.6 14328 12620 ? Ss 03:30 0:00 > >>>>> /kolab/bin/perl /kolab/etc/kolab/kolabquotawarn > >>>> > >>>> > >>>> You most use the email address to login, including the domain ! > >>>> > >>>> > >>>>> > >>>>> thx > >>>>> -bazooka > >>>>> > >>>>> _______________________________________________ > >>>>> 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 > >>> > >> > >> > >> > >> -- > >> ____ 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 > >> > > > > _______________________________________________ > 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/20081007/41bd4902/attachment.html From devgioiatech at gmail.com Tue Oct 7 12:50:31 2008 From: devgioiatech at gmail.com (Antonio Straziota) Date: Tue, 7 Oct 2008 12:50:31 +0200 Subject: Can't log into IMAP server In-Reply-To: References: <6b789da50808201107v592ab25foc5c4ded124e444f6@mail.gmail.com> <71fe4e760808201200p59d03cd2t431609b74302ef8a@mail.gmail.com> <6b789da50808201337hb2d3360l4c0471b0930d1c75@mail.gmail.com> <20080822193725.36837332galtcv40@webmail2.pardus.de> <6b789da50810061419l50a59005vcf06a75770254c34@mail.gmail.com> <6b789da50810061424r44ee5c03x534f1d17d7e0a575@mail.gmail.com> Message-ID: Checking the troubleshooting section on the wiki i find this faq... http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_IMAP applying given solution it seems to work. thanks 2008/10/7 Antonio Straziota > hi all, > i have the same problem... > In the past i solved the problem on a 2.2rc3 in the same way... but now, on > a fresh install of 2.2.0 it doesn't work. > > i tried all telnet and all service respond to it. > i check also > > ps ax | grep cyrmaster > 28605 pts/0 R+ 0:00 grep cyrmaster > 31398 ? Ss 0:00 /kolab/bin/cyrmaster -d > > Then i suppose all works correctly. > However if i try to run /kolab/bin/cyradm -u manager localhost > the console hangs. It should prompt for the password...but nothing happen > > Any idea? > Thanks in advance > > > > 2008/10/6 Bazooka Joe > > ***SOLVED**** >> >> I was installing this on a local network and nothing was resolving. >> >> in /etc/hosts file I added domain given in kolab conf and it worked. >> >> 127.0.0.1 kolab1.domain.tdl kolab1 >> >> -bazooka >> >> On Mon, Oct 6, 2008 at 1:19 PM, Bazooka Joe wrote: >> > sorry i didn't mean to send that yet. >> > >> > and ports 993, 389 >> > >> > everything seems to be running >> > >> > problem - can't login in horde get bad username/passwd error >> > >> > for username i am using full email addr >> > >> > -bazooka >> > >> > On Fri, Aug 22, 2008 at 9:37 AM, Gunnar Wrobel >> wrote: >> >> Quoting "Bazooka Joe" : >> >> >> >>> I was using full email addr as user name. >> >>> >> >>> Tbird doesn't even ask me for pw - I don't think imap is working. >> >> >> >> Did kolabconf run fine and configure your system correctly? If you had >> >> errors running the kolabconf script you would see these in the syslog. >> >> >> >> Cheers, >> >> >> >> Gunnar >> >> >> >>> >> >>> >> >>> >> >>> On Wed, Aug 20, 2008 at 11:00 AM, Alain Spineux >> wrote: >> >>>> On Wed, Aug 20, 2008 at 8:07 PM, Bazooka Joe >> wrote: >> >>>>> New to Kolab - first install - added 2 users >> >>>>> >> >>>>> Problem - Can't log in to IMAP server as users. >> >>>>> >> >>>>> Horde responds - >> >>>>> "Login failed because your username or password was entered >> incorrectly." >> >>>>> >> >>>>> Thunderbird - >> >>>>> "Connection to server timed out" >> >>>>> >> >>>>> I have the crymaster service running which is what I understand >> takes >> >>>>> the imap connection. >> >>>>> >> >>>>> I just noticed I also have all these hung quota processes as well >> >>>>> >> >>>>> kolab 2572 0.0 0.0 5836 1480 ? S 03:30 0:00 >> crond >> >>>>> kolab 2577 0.0 0.6 14328 12620 ? Ss 03:30 0:00 >> >>>>> /kolab/bin/perl /kolab/etc/kolab/kolabquotawarn >> >>>> >> >>>> >> >>>> You most use the email address to login, including the domain ! >> >>>> >> >>>> >> >>>>> >> >>>>> thx >> >>>>> -bazooka >> >>>>> >> >>>>> _______________________________________________ >> >>>>> 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 >> >>> >> >> >> >> >> >> >> >> -- >> >> ____ 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 >> >> >> > >> >> _______________________________________________ >> 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/20081007/2172af0b/attachment-0001.html From jwalls at browntransmission.com Tue Oct 7 16:06:41 2008 From: jwalls at browntransmission.com (Jeffrey Walls) Date: Tue, 7 Oct 2008 10:06:41 -0400 Subject: Upgrade failure again Message-ID: <8D252631F7204344A049B15B7B6EA9B2@lancaster.browntransmission.com> Trying again to upgrade to Kolab 2.2 on Fedora 5, from Kolab 2.1. The problem now is in perl-mail: :::: /tmp/install-kolab.6968.5087.1078.1447/gzip-1.3.12-20080101.src.rpm = 0 ::: : :::: /tmp/install-kolab.6968.5087.1078.1447/perl-mail-5.10.0-20080117.src.rpm :: :: Installing /tmp/install-kolab.6968.5087.1078.1447/perl-mail-5.10.0-20080117.src. rpm Executing(%prep): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e / kolab/RPM/TMP/rpm-tmp.54697 + cd /kolab/RPM/TMP + cd /kolab/RPM/TMP + rm -rf perl-mail-5.10.0 + /kolab/lib/openpkg/shtool mkdir -f -p -m 755 -p perl-mail-5.10.0 + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/MailTools-2.02.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/MIME-tools-5.425.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/MIME-Lite-3.021.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/MIME-Base64-3.07.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/MIME-Explode-0.38.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/MIME-Types-1.23.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/User-Identity-0.92.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/Mail-IMAPClient-3.03.tar. gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/Mail-Box-2.080.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/Mail-MboxParser-0.55.tar. gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/Mail-Mbox-MessageParser-1 .5000.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/Mail-Sendmail-0.79.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/Mail-Sender-0.8.13.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/Email-Address-1.889.tar.g z + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/Email-Valid-0.179.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/Email-Simple-2.003.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/Email-MessageID-1.351.tar .gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/Email-MIME-ContentType-1. 014.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/Email-MIME-Encodings-1.31 1.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/Email-MIME-1.861.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/Email-MIME-Modifier-1.442 .tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/perl-mail/Email-MIME-Creator-1.454. tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + /kolab/lib/openpkg/shtool subst -e 's;/usr/lib/sendmail;/kolab/sbin/sendmail;' + /kolab/lib/openpkg/shtool subst -e 's;/usr/lib/sendmail;/kolab/sbin/sendmail;' MIME-Lite-3.021/lib/MIME/Lite.pm + exit 0 Executing(%build): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.9511 + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + exit 0 Executing(%install): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.9511 + cd /kolab/RPM/TMP + cd perl-mail-5.10.0 + rm -rf /kolab/RPM/TMP/perl-mail-5.10.0-root + /kolab/bin/perl-openpkg prepare IO object version 1.23_01 does not match bootstrap parameter 1.23 at /kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 226. Compilation failed in require at /kolab/bin/perl-openpkg line 29. BEGIN failed--compilation aborted at /kolab/bin/perl-openpkg line 29. error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.9511 (%install) RPM build errors: Bad exit status from /kolab/RPM/TMP/rpm-tmp.9511 (%install) -- Jeffrey Walls IT Manager Brown Transmission and Bearing Co. PO Box 11117 Lancaster PA 17605-1117 717 295-9200 ext 214 717 295-9025 fax http://www.browntransmission.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://kolab.org/pipermail/kolab-users/attachments/20081007/b29c28b1/attachment.html From devgioiatech at gmail.com Tue Oct 7 18:08:13 2008 From: devgioiatech at gmail.com (Antonio Straziota) Date: Tue, 7 Oct 2008 18:08:13 +0200 Subject: Alfresco + Kolab authentication Message-ID: hi all, i have to use kolab ldap backand to authenticate my kolab users on alfresco CMS. In detail: - i have Liferay configured with a CAS server and LDAP - CAS Server configured with LDAP - Alfresco configured with LDAP Now i've to configure Alfresco with LDAP. With SIMPLE autentication mode i've no problem, but i want to configure the authentication metod in DIGEST?MD5. Can i configure Kolab LDAP to accept connection in SASL DIGEST-MD5? My configuration is Kolab 2.2.0 stable on a CentOS 5.2 Xen VM Thanks in advance. Antonio. -------------- parte successiva -------------- Un allegato HTML ? stato rimosso... URL: http://kolab.org/pipermail/kolab-users/attachments/20081007/809be709/attachment.html From itsef-admin at brightsight.com Wed Oct 8 10:24:43 2008 From: itsef-admin at brightsight.com (ITSEF Admin) Date: Wed, 8 Oct 2008 10:24:43 +0200 Subject: Cannot get freebusy to work in Kontact Message-ID: <200810081024.43359.itsef-admin@brightsight.com> Hi all, I'm trying to get freebusy to work in my own Kontact (enterprise35) - so far without luck. Here's what I see so far: - We have several users for whom freebusy just works (same Kontact version and no significant differences in korganizerrc, as far as I can see) - For those users, the reqests I can see on the server (apache log) include a login name - If I use a browser to get the freebusy information "manually", I get asked for a username and password. Once I supply them, I get the text. Hence, freebusy does indeed work correctly on the server. - In Settings -> Calendar -> Free/Busy -> Retrieve, I have set username and password - however, none of those seems to get used by my client. The username can be seen in korganizerrc, but it can never be seen in the serverlogs. - Restarting Kontact did not help Basically, it looks like "my" Kontact refuses to send the username/password I have entered when trying to retrieve the freebusy information. Unfortunately, I have absolutely no idea why, especially, as it seems to work for other users with the same Kontact version. I have seen the Wiki article on the topic, but that does not seem to have any clues. BTW: The Wiki article states that the URL for freebusy is supposed to be "https://my-domain.de/freebusy/%EMAIL%.ifb". Is this still correct for enterprise35? I'm asking 'cause all our users with working freebusy have "https://my-domain.de/freebusy/" in there - which is the way kolabwizard sets it. As usual - any insight is most appreciated. Regards, Thomas From albrecht.dress at lios-tech.com Wed Oct 8 15:02:48 2008 From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=) Date: Wed, 08 Oct 2008 15:02:48 +0200 Subject: calendar user gets a http 404 error? Message-ID: <1223470968l.19722l.3l@pc104141.koeln.nktcables.com> Hi all, while trying out the Toltec connector with Kolab 2.2, I see the following error messages in the Apache log: srv-kolab.my-company.de - calendar at my-company.com [08/Oct/2008:13:58:30 +0200] "GET /freebusy/trigger/test2%40my-company.com/Kalender.pfb HTTP/1.0" 404 468 (Note: the domains of the users [my-company.com] and the computers [my-company.de] are different by intention - hope that doesn't make a difference!) The Calendar user *does* have write permissions to the "Kalender" folder of user test2: localhost> lam INBOX/Kalender test2 at my-company.com lrswikxtecda calendar at my-company.com lrswipkxtecd The field "apache-allow-unauthenticated-fb" in the kolab LDAP entry is set to TRUE. Any idea what goes wrong here? Thanks, Albrecht. From tmalone at lancer-ins.com Wed Oct 8 23:17:57 2008 From: tmalone at lancer-ins.com (Tom Malone) Date: Wed, 08 Oct 2008 17:17:57 -0400 Subject: Kolab Server and z-push. Message-ID: <48ED2385.5090300@lancer-ins.com> Earlier this year there was talk on the z-push forums about creating a backend for the Kolab server. Has anyone heard of any progress on this? I have also asked on the z-push forums but so far nobody there has answered. Thanks Tom =========================================================================== The information contained in this communication may be confidential, is intended only for the use of the recipient(s) named above, and may be legally privileged. You are hereby notified that any dissemination, distribution or copying of this communication and any of its contents or attachments is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this message and please delete this message from all computers and servers. From devgioiatech at gmail.com Thu Oct 9 09:14:03 2008 From: devgioiatech at gmail.com (Antonio Straziota) Date: Thu, 9 Oct 2008 09:14:03 +0200 Subject: Alfresco + Kolab authentication In-Reply-To: References: Message-ID: Nobody can help me? 2008/10/7 Antonio Straziota > hi all, > i have to use kolab ldap backand to authenticate my kolab users on alfresco > CMS. > > In detail: > - i have Liferay configured with a CAS server and LDAP > - CAS Server configured with LDAP > - Alfresco configured with LDAP > > Now i've to configure Alfresco with LDAP. With SIMPLE autentication mode > i've no problem, but i want to configure the authentication metod in > DIGEST?MD5. > > Can i configure Kolab LDAP to accept connection in SASL DIGEST-MD5? > > My configuration is Kolab 2.2.0 stable on a CentOS 5.2 Xen VM > > Thanks in advance. > Antonio. > -------------- parte successiva -------------- Un allegato HTML ? stato rimosso... URL: http://kolab.org/pipermail/kolab-users/attachments/20081009/721df551/attachment.html From wrobel at pardus.de Thu Oct 9 09:29:05 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Thu, 09 Oct 2008 09:29:05 +0200 Subject: Upgrade failure again In-Reply-To: <8D252631F7204344A049B15B7B6EA9B2@lancaster.browntransmission.com> References: <8D252631F7204344A049B15B7B6EA9B2@lancaster.browntransmission.com> Message-ID: <20081009092905.13141mx28tedzd8g@webmail.pardus.de> Quoting Jeffrey Walls : > Trying again to upgrade to Kolab 2.2 > on Fedora 5, from Kolab 2.1. The problem now is in > perl-mail: :::: > /tmp/install-kolab.6968.5087.1078.1447/gzip-1.3.12-20080101.src.rpm > = 0 ::: : :::: > /tmp/install-kolab.6968.5087.1078.1447/perl-mail-5.10.0-20080117.src.rpm > :: :: Installing > /tmp/install-kolab.6968.5087.1078.1447/perl-mail-5.10.0-20080117.src. > > rpm Executing(%prep): env -i > /kolab/lib/openpkg/bash --norc --noprofile --posix -e / > kolab/RPM/TMP/rpm-tmp.54697 + cd /kolab/RPM/TMP + cd /kolab/RPM/TMP > + rm -rf perl-mail-5.10.0 + /kolab/lib/openpkg/shtool mkdir > -f -p -m 755 -p perl-mail-5.10.0 + cd perl-mail-5.10.0 + > /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/MailTools-2.02.tar.gz + /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/MIME-tools-5.425.tar.gz + /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/MIME-Lite-3.021.tar.gz + /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/MIME-Base64-3.07.tar.gz + /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/MIME-Explode-0.38.tar.gz + > /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/MIME-Types-1.23.tar.gz + /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/User-Identity-0.92.tar.gz + > /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Mail-IMAPClient-3.03.tar. gz + > /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Mail-Box-2.080.tar.gz + /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Mail-MboxParser-0.55.tar. gz + > /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Mail-Mbox-MessageParser-1 .5000.tar.gz + > /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Mail-Sendmail-0.79.tar.gz + > /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Mail-Sender-0.8.13.tar.gz + > /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-Address-1.889.tar.g z + > /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-Valid-0.179.tar.gz + > /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-Simple-2.003.tar.gz + > /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-MessageID-1.351.tar .gz + > /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-MIME-ContentType-1. 014.tar.gz + > /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-MIME-Encodings-1.31 1.tar.gz + > /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-MIME-1.861.tar.gz + /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-MIME-Modifier-1.442 .tar.gz + > /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-MIME-Creator-1.454. tar.gz + > /kolab/lib/openpkg/tar -xf > - + STATUS=0 + '[' 0 -ne 0 ']' + /kolab/lib/openpkg/shtool subst > -e 's;/usr/lib/sendmail;/kolab/sbin/sendmail;' + > /kolab/lib/openpkg/shtool subst > -e 's;/usr/lib/sendmail;/kolab/sbin/sendmail;' > MIME-Lite-3.021/lib/MIME/Lite.pm + exit 0 Executing(%build): env -i > /kolab/lib/openpkg/bash --norc --noprofile --posix -e > /kolab/RPM/TMP/rpm-tmp.9511 + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + exit 0 Executing(%install): env -i > /kolab/lib/openpkg/bash --norc --noprofile --posix -e > /kolab/RPM/TMP/rpm-tmp.9511 + cd /kolab/RPM/TMP + cd > perl-mail-5.10.0 + rm -rf > /kolab/RPM/TMP/perl-mail-5.10.0-root + /kolab/bin/perl-openpkg > prepare IO object version 1.23_01 does not > match bootstrap parameter 1.23 at > /kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 226. > > > Compilation failed in require at > /kolab/bin/perl-openpkg line 29. BEGIN failed--compilation aborted > at /kolab/bin/perl-openpkg line 29. error: Bad exit status from > /kolab/RPM/TMP/rpm-tmp.9511 (%install) RPM build errors: Bad > exit status from > /kolab/RPM/TMP/rpm-tmp.9511 (%install) This seems to be a common error with perl (http://www.perlmonks.org/index.pl?node_id=491084) though I did not see such problem reports with Kolab yet. I would guess that there might be some perl library in your base distribution interferes with the Kolab perl libraries. But that is a wild guess. Thomas, maybe you have another idea? I guess you should submit a bug report. Cheers, Gunnar > > -- > Jeffrey Walls IT Manager Brown Transmission and > Bearing Co. PO Box 11117 Lancaster PA > 17605-1117 717 295-9200 ext 214 717 295-9025 fax _ > color=\"#0000ff\">http://www.browntransmission.com_[1] -- ______ 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://www.browntransmission.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/20081009/8235ed71/attachment.bin From wrobel at pardus.de Thu Oct 9 09:40:19 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Thu, 09 Oct 2008 09:40:19 +0200 Subject: Alfresco + Kolab authentication In-Reply-To: References: Message-ID: <20081009094019.53801fsl8yqixc2o@webmail.pardus.de> Quoting Antonio Straziota : > hi all, > i have to use kolab ldap backand to authenticate my kolab users on > alfresco CMS. > > In detail: > - i have Liferay configured with a CAS server and LDAP > - CAS Server configured with LDAP > - Alfresco configured with LDAP > > Now i've to configure Alfresco with LDAP. With SIMPLE autentication > mode i've no problem, but i want to configure the authentication > metod in DIGEST$B!](BMD5. > > Can i configure Kolab LDAP to accept connection in SASL DIGEST-MD5? I admit I'm not 100% certain how your setup looks like. Of course Alfresco can authenticate using SASL to authenticate against the Kolab LDAP server. But your request sounds like you wish LDAP to use SASL (something like http://tldp.org/HOWTO/LDAP-HOWTO/sasl.html) which is not possible as OpenLDAP is the SASL backend and that would result in a circular dependency. Cheers, Gunnar > My configuration is Kolab 2.2.0 stable on a CentOS 5.2 Xen VM > Thanks in advance. > Antonio. > -- ____ 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. From wrobel at pardus.de Thu Oct 9 09:40:49 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Thu, 09 Oct 2008 09:40:49 +0200 Subject: Alfresco + Kolab authentication In-Reply-To: References: Message-ID: <20081009094049.17211wt3w82mg70g@webmail.pardus.de> Quoting Antonio Straziota : > Nobody can help me? Patience :) > > 2008/10/7 Antonio Straziota dir=\"ltr\"> > #cccccc; margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;\"> dir=\"ltr\">hi all, > i have to use kolab ldap backand to authenticate my kolab users on > alfresco CMS. > > In detail: > - i have Liferay configured with a CAS server and LDAP > - CAS Server configured with LDAP > - Alfresco configured with LDAP > > Now i've to configure Alfresco with LDAP. With SIMPLE autentication > mode i've no problem, but i want to configure the authentication > metod in DIGEST$B!](BMD5. > > Can i configure Kolab LDAP to accept connection in SASL DIGEST-MD5? > My configuration is Kolab 2.2.0 stable on a CentOS 5.2 Xen VM > Thanks in advance. > Antonio. > -- ______ http://kdab.com[2] _______________ http://kolab-konsortium.com[3] _ p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium ____ http://www.pardus.de[4] _________________ http://gunnarwrobel.de[5] _ 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 [2] http://kdab.com [3] http://kolab-konsortium.com [4] http://www.pardus.de [5] 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/20081009/d0f059b5/attachment-0001.bin From wrobel at pardus.de Thu Oct 9 09:45:31 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Thu, 09 Oct 2008 09:45:31 +0200 Subject: calendar user gets a http 404 error? In-Reply-To: <1223470968l.19722l.3l@pc104141.koeln.nktcables.com> References: <1223470968l.19722l.3l@pc104141.koeln.nktcables.com> Message-ID: <20081009094531.13487kdqgar313go@webmail.pardus.de> Quoting Albrecht Dre? : > Hi all, > > while trying out the Toltec connector with Kolab 2.2, I see the > following error messages in the Apache log: > > srv-kolab.my-company.de - calendar at my-company.com [08/Oct/2008:13:58:30 > +0200] "GET /freebusy/trigger/test2%40my-company.com/Kalender.pfb > HTTP/1.0" 404 468 Try to enter that URL into your normal browser. This should show you why you actually get 404 here. Cheers, Gunnar > > (Note: the domains of the users [my-company.com] and the computers > [my-company.de] are different by intention - hope that doesn't make a > difference!) > > The Calendar user *does* have write permissions to the "Kalender" > folder of user test2: > > localhost> lam INBOX/Kalender > test2 at my-company.com lrswikxtecda > calendar at my-company.com lrswipkxtecd > > The field "apache-allow-unauthenticated-fb" in the kolab LDAP entry is > set to TRUE. > > Any idea what goes wrong here? > > 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/20081009/70c1a232/attachment.bin From wrobel at pardus.de Thu Oct 9 09:54:40 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Thu, 09 Oct 2008 09:54:40 +0200 Subject: Kolab Server and z-push. In-Reply-To: <48ED2385.5090300@lancer-ins.com> References: <48ED2385.5090300@lancer-ins.com> Message-ID: <20081009095440.20041tgzctg1463o@webmail.pardus.de> Quoting Tom Malone : > Earlier this year there was talk on the z-push forums about creating a > backend for the Kolab server. > > Has anyone heard of any progress on this? I have also asked on the > z-push forums but so far nobody there has answered. I don't think anybody is currently working on this. From a short look at the z-push code I assume that it should not be too hard to combine the z-push backend with the Horde-SyncML backend code. Nevertheless I'd assume we'd need a customer contracting us for that. As far as I know it is not on any todo list at the moment. Cheers, Gunnar > > Thanks > Tom > > > =========================================================================== > > The information contained in this communication may be confidential, is > intended only for the use of the recipient(s) named above, and may be > legally privileged. You are hereby notified that any dissemination, > distribution or copying of this communication and any of its contents or > attachments is strictly prohibited. If you have received this > communication in error, please notify us immediately by replying to this > message and please delete this message from all computers and servers. > > _______________________________________________ > 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/20081009/a3f9631f/attachment.bin From albrecht.dress at lios-tech.com Thu Oct 9 10:21:50 2008 From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=) Date: Thu, 09 Oct 2008 10:21:50 +0200 Subject: calendar user gets a http 404 error? In-Reply-To: <20081009094531.13487kdqgar313go@webmail.pardus.de> (from wrobel@pardus.de on Thu Oct 9 09:45:31 2008) Message-ID: <1223540510l.24908l.0l@pc104141.koeln.nktcables.com> Am 09.10.2008 09:45:31 schrieb(en) Gunnar Wrobel: >> srv-kolab.my-company.de - calendar at my-company.com >> [08/Oct/2008:13:58:30 +0200] "GET >> /freebusy/trigger/test2%40my-company.com/Kalender.pfb HTTP/1.0" 404 >> 468 > > Try to enter that URL into your normal browser. This should show you > why you actually get 404 here. O.k., loaded the page in Firefox as "calendar at my-company.com" using the password I found in /kolab/etc/kolab/kolab.conf and got: Not found The requested URL /freebusy/trigger/test2%40my-company.com/Kalender.pfb was not found on this server. IMAP error. Folder: user/test2/Kalender. Error: Permission denied Apache/2.2.8 (OpenPKG/CURRENT) mod_ssl/2.2.8 OpenSSL/0.9.8g PHP/5.2.6 Server at 10.16.0.1 Port 443 I do not understand this message, as the calendar user *does* have full permissions on this folder: root at srv-kolab:~# /kolab/bin/cyradm --user test2 localhost Password:localhost> lam INBOX/Kalender test2 at my-domain.com lrswikxtecda calendar at my-domain.com lrswipkxtecd Any idea? Thanks, Albrecht. From albrecht.dress at lios-tech.com Thu Oct 9 10:31:58 2008 From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=) Date: Thu, 09 Oct 2008 10:31:58 +0200 Subject: Toltec connector duplicates appointment attendees Message-ID: <1223541118l.24908l.1l@pc104141.koeln.nktcables.com> Hi all, while evaluating the Toltec connector and Toltec LDAP address book for Outlook I found a puzzling behaviour... I created two users "Test 1 Benutzer" and "Test 2 Benutzer", both accepting invitations automatically. Invitations are sent from "Test 1 Benutzer" to "Test 2 Benutzer", taking the latter from the LDAP address book. If I configure the LDAP address book to show names as "First Last", everything works fine. However, setting it to display names as "Last, First" (which results in "Benutzer, Test 2" for the example above), the "accept" message will create a /second/ user in the appointment object in IMAP: Benutzer, Test 2 test2 at my-company.com none true required Test 2 Benutzer test2 at my-company.com accepted true optional The first entry was the original one, and the second has been added. I checked the vcalendar message produced automatically, and it contains only "ATTENDEE;PARTSTAT=ACCEPTED:MAILTO:test2 at my-company.com". I'm not sure whether Toltec or Outlook or Kolab is the source of the bug, but it is somewhat annoying... Any idea how it could be fixed? Thanks, Albrecht. From hans.moser at ofd-sth.niedersachsen.de Thu Oct 9 10:48:31 2008 From: hans.moser at ofd-sth.niedersachsen.de (Marc Patermann) Date: Thu, 09 Oct 2008 10:48:31 +0200 Subject: Alfresco + Kolab authentication In-Reply-To: References: Message-ID: <48EDC55F.5020004@ofd-sth.niedersachsen.de> Gunnar Wrobel schrieb: > Quoting Antonio Straziota : >> Now i've to configure Alfresco with LDAP. With SIMPLE autentication >> mode i've no problem, but i want to configure the authentication >> metod in DIGEST$B!](BMD5. >> >> Can i configure Kolab LDAP to accept connection in SASL DIGEST-MD5? Yes. > I admit I'm not 100% certain how your setup looks like. Of course > Alfresco can authenticate using SASL to authenticate against the Kolab > LDAP server. But your request sounds like you wish LDAP to use SASL > (something like http://tldp.org/HOWTO/LDAP-HOWTO/sasl.html) which is > not possible as OpenLDAP is the SASL backend and that would result in > a circular dependency. Not true! "The DIGEST-MD5 mechanism is the mandatory-to-implement authentication mechanism for LDAPv3." Have a look at the OpenLDAP Admin Guide SASL section: -> http://www.openldap.org/doc/admin23/sasl.html Marc From devgioiatech at gmail.com Thu Oct 9 12:22:59 2008 From: devgioiatech at gmail.com (Antonio Straziota) Date: Thu, 9 Oct 2008 12:22:59 +0200 Subject: Alfresco + Kolab authentication In-Reply-To: <48EDC55F.5020004@ofd-sth.niedersachsen.de> References: <48EDC55F.5020004@ofd-sth.niedersachsen.de> Message-ID: hi, thanks to all for the reply. So, It could be possible using secrets stored in the LDAP? From hans.moser at ofd-sth.niedersachsen.de Thu Oct 9 12:52:40 2008 From: hans.moser at ofd-sth.niedersachsen.de (Marc Patermann) Date: Thu, 09 Oct 2008 12:52:40 +0200 Subject: Alfresco + Kolab authentication In-Reply-To: References: <48EDC55F.5020004@ofd-sth.niedersachsen.de> Message-ID: <48EDE278.2080504@ofd-sth.niedersachsen.de> Antonio Straziota schrieb: > So, It could be possible using secrets stored in the LDAP? You _can_ use DIGEST-MD5 authentication against the OpenLDAP server. > "This section describes the use of the SASL DIGEST-MD5 mechanism using > secrets stored either in the directory itself or in Cyrus SASL's own > database. DIGEST-MD5 relies on the client and the server sharing a > "secret", usually a password" > > Is it correct? You do not trust the official OpenLDAP documentation? :) DIGEST-MD5 is an shared secret mechanism. The shared secret can be the password. This depends on clear text passwords in LDAP, otherwise you don't have the same secret to share. An alternative secret store would be sasldb2 or Kerberos i.e. But I don't think this is what you want. > I'll try it. Thanks for the help... > > PS: Any other suggetion are welcome :D I don't really see an alternative. You have the Kolab LDAP server which is OpenLDAP and you want to use shared secret auth against it which OpenLDAP offers. Done. Marc From jwalls at browntransmission.com Thu Oct 9 14:51:55 2008 From: jwalls at browntransmission.com (Jeffrey Walls) Date: Thu, 9 Oct 2008 08:51:55 -0400 Subject: Upgrade failure again Message-ID: Ok Issue 3130 created on the bug tracker. -- Jeffrey Walls IT Manager Brown Transmission and Bearing Co. PO Box 11117 Lancaster PA 17605-1117 717 295-9200 ext 214 717 295-9025 fax http://www.browntransmission.com > _____________________________________________ > From: Jeffrey Walls [mailto:jwalls at browntransmission.com] > Sent: Tuesday, October 07, 2008 10:07 AM > To: 'kolab-users at kolab.org' > Subject: Upgrade failure again > > Trying again to upgrade to Kolab 2.2 on Fedora 5, from Kolab 2.1. > > The problem now is in perl-mail: > > :::: /tmp/install-kolab.6968.5087.1078.1447/gzip-1.3.12-20080101.src.rpm = > 0 ::: > : > :::: > /tmp/install-kolab.6968.5087.1078.1447/perl-mail-5.10.0-20080117.src.rpm > :: > :: > Installing > /tmp/install-kolab.6968.5087.1078.1447/perl-mail-5.10.0-20080117.src. > rpm > Executing(%prep): env -i /kolab/lib/openpkg/bash --norc --noprofile > --posix -e / > kolab/RPM/TMP/rpm-tmp.54697 > + cd /kolab/RPM/TMP > + cd /kolab/RPM/TMP > + rm -rf perl-mail-5.10.0 > + /kolab/lib/openpkg/shtool mkdir -f -p -m 755 -p perl-mail-5.10.0 > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/MailTools-2.02.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/MIME-tools-5.425.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/MIME-Lite-3.021.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/MIME-Base64-3.07.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/MIME-Explode-0.38.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/MIME-Types-1.23.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/User-Identity-0.92.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Mail-IMAPClient-3.03.tar. > gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Mail-Box-2.080.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Mail-MboxParser-0.55.tar. > gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Mail-Mbox-MessageParser-1 > .5000.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Mail-Sendmail-0.79.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Mail-Sender-0.8.13.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-Address-1.889.tar.g > z > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-Valid-0.179.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-Simple-2.003.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-MessageID-1.351.tar > .gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-MIME-ContentType-1. > 014.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-MIME-Encodings-1.31 > 1.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-MIME-1.861.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-MIME-Modifier-1.442 > .tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + /kolab/lib/openpkg/gzip -dc > /kolab/RPM/SRC/perl-mail/Email-MIME-Creator-1.454. > tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + /kolab/lib/openpkg/shtool subst -e > 's;/usr/lib/sendmail;/kolab/sbin/sendmail;' > + /kolab/lib/openpkg/shtool subst -e > 's;/usr/lib/sendmail;/kolab/sbin/sendmail;' > MIME-Lite-3.021/lib/MIME/Lite.pm > + exit 0 > Executing(%build): env -i /kolab/lib/openpkg/bash --norc --noprofile > --posix -e /kolab/RPM/TMP/rpm-tmp.9511 > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + exit 0 > Executing(%install): env -i /kolab/lib/openpkg/bash --norc --noprofile > --posix -e /kolab/RPM/TMP/rpm-tmp.9511 > + cd /kolab/RPM/TMP > + cd perl-mail-5.10.0 > + rm -rf /kolab/RPM/TMP/perl-mail-5.10.0-root > + /kolab/bin/perl-openpkg prepare > IO object version 1.23_01 does not match bootstrap parameter 1.23 at > /kolab/lib/perl/5.10.0/i686-linux/DynaLoader.pm line 226. > Compilation failed in require at /kolab/bin/perl-openpkg line 29. > BEGIN failed--compilation aborted at /kolab/bin/perl-openpkg line 29. > error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.9511 (%install) > > > RPM build errors: > Bad exit status from /kolab/RPM/TMP/rpm-tmp.9511 (%install) > > -- > Jeffrey Walls > IT Manager > Brown Transmission and Bearing Co. > PO Box 11117 > Lancaster PA 17605-1117 > 717 295-9200 ext 214 > 717 295-9025 fax > http://www.browntransmission.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://kolab.org/pipermail/kolab-users/attachments/20081009/7318b645/attachment-0001.html From kcaesar at hotmail.com Thu Oct 9 15:38:32 2008 From: kcaesar at hotmail.com (kiser Caesar) Date: Thu, 9 Oct 2008 15:38:32 +0200 Subject: Kolab + HTC ? Message-ID: Hello, Someone can say me if kolab can work with an HTC ? And syncing emails and calendars ? Excuse me if this is not the first time we ask you... :) Thank ! _________________________________________________________________ Installez gratuitement les 20 ?m?ticones Windows Live Messenger les plus fous ! Cliquez ici ! http://www.emoticones-messenger.fr/ -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: http://kolab.org/pipermail/kolab-users/attachments/20081009/10677581/attachment.html From delonly at gmail.com Thu Oct 9 17:07:11 2008 From: delonly at gmail.com (Del) Date: Thu, 09 Oct 2008 17:07:11 +0200 Subject: Kolab + HTC ? In-Reply-To: References: Message-ID: <1223564831.15177.14.camel@black> Hello Kiser, You may currently be able use the Toltec connector just as for Outlook on PC (cross-check with Toltec to see if mobiles are supported): http://www.toltec.co.za/default.html Starting from version 2.2.1 (expected November? still eagerly awaiting Gunnar) you should finally be able to use the SyncML protocol: http://en.wikipedia.org/wiki/Syncml which is implemented in Horde: http://www.horde.org/sync/ for just about any mobile phone. Microsoft has as far as I know as usual refrained from implementing open protocols, so I believe you would need a plug-in for HTC, where Funambol seems to be a natural choice: https://www.forge.funambol.org/download/ I assume you can sync mail directly through IMAP, provided your phone support it. Cheers, Del On Thu, 2008-10-09 at 15:38 +0200, kiser Caesar wrote: > Hello, > > Someone can say me if kolab can work with an HTC ? > And syncing emails and calendars ? > > Excuse me if this is not the first time we ask you... :) > > Thank ! > > ______________________________________________________________________ > T?l?phonez gratuitement ? tous vos proches avec Windows Live > Messenger ! T?l?chargez-le maintenant ! > _______________________________________________ > Kolab-users mailing list > Kolab-users at kolab.org > https://kolab.org/mailman/listinfo/kolab-users From mark at rtsw.co.uk Thu Oct 9 19:02:41 2008 From: mark at rtsw.co.uk (Mark Seagrief) Date: Thu, 9 Oct 2008 18:02:41 +0100 Subject: Kolab 2.2 upgrade from 2.1 failure on php-channel-horde In-Reply-To: <20081007095704.177818rd30oyknk0@webmail.pardus.de> References: <200810031150.47986.mark@rtsw.co.uk> <20081007095704.177818rd30oyknk0@webmail.pardus.de> Message-ID: <200810091802.41479.mark@rtsw.co.uk> On Tuesday 07 October 2008 08:57, Gunnar Wrobel wrote: > Quoting Mark Seagrief : > > Hi, > > > > I kicked off an upgrade of a Kolab installation last night to upgrade > > from 2.1.0 to 2.2.0. > > > > I'm installing from source on Ubuntu 7.04 server edition with kernel > > 2.6.20-16-server. > > > > Most of the RPMs seem to have built correctly and installed fine, but > > php-channel-horde seems to have failed. > > > > The final few lines of the log are: > > > > > > Package Horde_Alarm-0.1.0.tgz done > > Tag the released code with `pear cvstag Alarm/package.xml' > > (or set the CVS tag RELEASE_0_1_0 by hand) > > + env 'PHP_PEAR_PHP_BIN=/kolab/bin/php -d safe_mode=off -d > > memory_limit=40M' PHP_PEAR_CACHE_DIR=/kolab/RPM/TMP/pear/cache > > /kolab/bin/pear install --force --loose --nodeps --offline > > --packagingroot=/kolab/RPM/TMP/horde-framework-kolab-3.2_rc3-root > > Horde_Alarm-0.1.0.tgz > > could not extract the package.xml file from "Horde_Alarm-0.1.0.tgz" > > Cannot download non-local package "Horde_Alarm-0.1.0.tgz" > > Package "Horde_Alarm-0.1.0.tgz" is not valid > > install failed > > error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.48129 (%install) > > These lines seem to originate from the horde-framework installation > rather than from php-channel-horde. Can you post the log messages > concerning php-channel-horde since you say compilation failed for that > one. > > Cheers, > > Gunnar > > > I've check on the system and I do have a file that has been created > > called Horde_Alarm-0.1.0.tgz in /kolab/RPM/TMP/framework/ > > > > Any ideas as to what is causing this problem? Anybody encountered > > something similar? > > > > I'm going to grab another machine and try an installtion of 2.2 from > > scratch and see if that helps/exhibits this problem. > > > > Many thanks, > > > > Mark > > > > -- > > > > Mark Seagrief > > RT Software > > > > _______________________________________________ > > Kolab-users mailing list > > Kolab-users at kolab.org > > https://kolab.org/mailman/listinfo/kolab-users Hi Gunnar, Sorry for the delay in getting back to you. I've had another look through the logs and I was initially mistaken, php-channel-horde does appear to have worked. I have the following in my log file: Preparing... ################################################## php-channel-horde ################################################## channel-add: Channel "pear.horde.org" exists, use channel-update to update entry Channel already exists! Update of Channel "pear.horde.org" succeeded :::: /tmp/install-kolab.20815.18405.11728.1940/php-channel-horde-1.0-1.src.rpm = 0 :::: :::: /tmp/install-kolab.20815.18405.11728.1940/horde-framework-kolab-3.2_rc3-20080405.src.rpm :::: Installing /tmp/install-kolab.20815.18405.11728.1940/horde-framework-kolab-3.2_rc3-20080405.src.rpm So I assume it is the building of the horde-framework-kolab rpm from source that is failing. I've attached a snippet of the log file with the, hopefully, relevant output. I've taken out the output from a tar command that listed a few thousand lines of files, but left in the lines for the files for the Alarm. Many thanks for your time, Cheers, Mark -- Mark Seagrief RT Software e: mark at rtsw.co.uk t: +44 207 16 888 20 p: Unit D, 2 Chesney Street, Battersea, London, SW11 5JT -------------- next part -------------- Preparing... ################################################## php-channel-horde ################################################## channel-add: Channel "pear.horde.org" exists, use channel-update to update entry Channel already exists! Update of Channel "pear.horde.org" succeeded :::: /tmp/install-kolab.20815.18405.11728.1940/php-channel-horde-1.0-1.src.rpm = 0 :::: :::: /tmp/install-kolab.20815.18405.11728.1940/horde-framework-kolab-3.2_rc3-20080405.src.rpm :::: Installing /tmp/install-kolab.20815.18405.11728.1940/horde-framework-kolab-3.2_rc3-20080405.src.rpm Executing(%prep): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.35798 + cd /kolab/RPM/TMP + set +x +----------------------------------Warning------------------------------------+ | This OpenPKG package is of class JUNK. | | This means it is still in DEVELOPMENT state. | | Hence it is still NOT ready even for general evaluation. | | Do not use it at all, except in development environments! | | It is definitely unstable and incompletely packaged. | +-----------------------------------------------------------------------------+ + cd /kolab/RPM/TMP + rm -rf framework + /kolab/lib/openpkg/bzip2 -dc /kolab/RPM/SRC/horde-framework-kolab/horde-framework-3.2_rc3.tar.bz2 + /kolab/lib/openpkg/tar -xvvf - drwxr-xr-x wrobel/users 0 2008-03-13 11:34 framework/ -rw-r--r-- wrobel/users 14 2008-02-18 07:40 framework/.htaccess drwxr-xr-x wrobel/users 0 2008-02-18 07:40 framework/Alarm/ -rw-r--r-- wrobel/users 20507 2008-02-18 07:40 framework/Alarm/Alarm.php drwxr-xr-x wrobel/users 0 2008-02-18 07:40 framework/Alarm/Alarm/ drwxr-xr-x wrobel/users 0 2008-02-18 07:40 framework/Alarm/Alarm/CVS/ -rw-r--r-- wrobel/users 63 2008-03-13 11:34 framework/Alarm/Alarm/CVS/Entries -rw-r--r-- wrobel/users 22 2008-02-18 07:40 framework/Alarm/Alarm/CVS/Repository -rw-r--r-- wrobel/users 47 2008-02-18 07:40 framework/Alarm/Alarm/CVS/Root -rw-r--r-- wrobel/users 21 2008-03-13 11:34 framework/Alarm/Alarm/CVS/Tag -rw-r--r-- wrobel/users 330 2008-02-18 07:40 framework/Alarm/Alarm/CVS/Template -rw-r--r-- wrobel/users 16502 2008-02-18 07:40 framework/Alarm/Alarm/sql.php drwxr-xr-x wrobel/users 0 2008-02-18 07:40 framework/Alarm/CVS/ -rw-r--r-- wrobel/users 151 2008-03-13 11:34 framework/Alarm/CVS/Entries -rw-r--r-- wrobel/users 16 2008-02-18 07:40 framework/Alarm/CVS/Repository -rw-r--r-- wrobel/users 47 2008-02-18 07:40 framework/Alarm/CVS/Root -rw-r--r-- wrobel/users 21 2008-03-13 11:34 framework/Alarm/CVS/Tag -rw-r--r-- wrobel/users 330 2008-02-18 07:40 framework/Alarm/CVS/Template -rw-r--r-- wrobel/users 1644 2008-02-18 07:40 framework/Alarm/package.xml drwxr-xr-x wrobel/users 0 2008-02-18 07:40 framework/Alarm/tests/ -rw-r--r-- wrobel/users 41 2008-02-18 07:40 framework/Alarm/tests/.cvsignore -rw-r--r-- wrobel/users 9090 2008-02-21 10:39 framework/Alarm/tests/001.phpt drwxr-xr-x wrobel/users 0 2008-02-18 07:40 framework/Alarm/tests/CVS/ -rw-r--r-- wrobel/users 193 2008-03-13 11:34 framework/Alarm/tests/CVS/Entries -rw-r--r-- wrobel/users 22 2008-02-18 07:40 framework/Alarm/tests/CVS/Repository -rw-r--r-- wrobel/users 47 2008-02-18 07:40 framework/Alarm/tests/CVS/Root -rw-r--r-- wrobel/users 21 2008-03-13 11:34 framework/Alarm/tests/CVS/Tag -rw-r--r-- wrobel/users 330 2008-02-18 07:40 framework/Alarm/tests/CVS/Template -rw-r--r-- wrobel/users 513 2008-02-18 07:40 framework/Alarm/tests/setup.inc.dist SNIP - removed output from tar -rw-r--r-- wrobel/users 3110 2008-03-13 11:34 framework/Reflection/lib/Horde/Reflection/Wiki.php -rw-r--r-- wrobel/users 2608 2008-03-13 11:34 framework/Reflection/package.xml + STATUS=0 + '[' 0 -ne 0 ']' + cd framework + echo 'Patch #0 (HK-GW-Fix_Prefs_for_Ingo_framework-3.2-rc3.patch):' Patch #0 (HK-GW-Fix_Prefs_for_Ingo_framework-3.2-rc3.patch): + /kolab/lib/openpkg/patch -p2 -s -b + echo 'Patch #1 (HK-GW-Fbview_xfb_concept_framework-3.2-rc3.patch):' Patch #1 (HK-GW-Fbview_xfb_concept_framework-3.2-rc3.patch): + /kolab/lib/openpkg/patch -p2 -s -b + echo 'Patch #2 (HK-GW-Freebusy_free_events_framework-3.2-rc3.patch):' Patch #2 (HK-GW-Freebusy_free_events_framework-3.2-rc3.patch): + /kolab/lib/openpkg/patch -p2 -s -b + echo 'Patch #3 (HK-GW-LDAP_user_alias_framework-3.2-rc3.patch):' Patch #3 (HK-GW-LDAP_user_alias_framework-3.2-rc3.patch): + /kolab/lib/openpkg/patch -p2 -s -b + exit 0 Executing(%build): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.48129 + cd /kolab/RPM/TMP + cd framework + exit 0 Executing(%install): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.48129 + cd /kolab/RPM/TMP + cd framework + for PKG in '**/package.xml' + '[' Alarm/package.xml '!=' Role_Webroot/package.xml -a Alarm/package.xml '!=' Rampage/package.xml -a Alarm/package.xml '!=' Text_Textile/package.xml -a Alarm/package.xml '!=' Lens/package.xml -a Alarm/package.xml '!=' Text_Diff/package.xml ']' + env 'PHP_PEAR_PHP_BIN=/kolab/bin/php -d safe_mode=off -d memory_limit=40M' PHP_PEAR_CACHE_DIR=/kolab/RPM/TMP/pear/cache /kolab/bin/pear package Alarm/package.xml Analyzing Alarm/sql.php Analyzing Alarm.php Warning: Parser error: token_get_all() function must exist to analyze source code Warning: Parser error: token_get_all() function must exist to analyze source code Warning: Channel validator warning: field "date" - Release Date "2007-02-01" is not today Package Horde_Alarm-0.1.0.tgz done Tag the released code with `pear cvstag Alarm/package.xml' (or set the CVS tag RELEASE_0_1_0 by hand) + env 'PHP_PEAR_PHP_BIN=/kolab/bin/php -d safe_mode=off -d memory_limit=40M' PHP_PEAR_CACHE_DIR=/kolab/RPM/TMP/pear/cache /kolab/bin/pear install --force --loose --nodeps --offline --packagingroot=/kolab/RPM/TMP/horde-framework-kolab-3.2_rc3-root Horde_Alarm-0.1.0.tgz could not extract the package.xml file from "Horde_Alarm-0.1.0.tgz" Cannot download non-local package "Horde_Alarm-0.1.0.tgz" Package "Horde_Alarm-0.1.0.tgz" is not valid install failed error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.48129 (%install) From delonly at gmail.com Thu Oct 9 17:13:56 2008 From: delonly at gmail.com (Del) Date: Thu, 09 Oct 2008 17:13:56 +0200 Subject: Alfresco + Kolab authentication In-Reply-To: References: <48EDC55F.5020004@ofd-sth.niedersachsen.de> Message-ID: <1223565236.15177.20.camel@black> Hello Antonio, Please make time to document your solution in the wiki as you go along: http://wiki.kolab.org/index.php/Main_Page You are not the only one interested in a document management system ;) Cheers, Del On Thu, 2008-10-09 at 12:22 +0200, Antonio Straziota wrote: > hi, > thanks to all for the reply. > > So, It could be possible using secrets stored in the LDAP? > > From the link posted by Marc: > > "This section describes the use of the SASL DIGEST-MD5 mechanism using > secrets stored either in the directory itself or in Cyrus SASL's own > database. DIGEST-MD5 relies on the client and the server sharing a > "secret", usually a password" > > Is it correct? > > I'll try it. Thanks for the help... > > PS: Any other suggetion are welcome :D > > bye > > 2008/10/9 Marc Patermann > Gunnar Wrobel schrieb: > > Quoting Antonio Straziota : > > > >> Now i've to configure Alfresco with LDAP. With SIMPLE > autentication > >> mode i've no problem, but i want to configure the > authentication > > >> metod in DIGEST$B!](BMD5. > >> > >> Can i configure Kolab LDAP to accept connection in SASL > DIGEST-MD5? > > Yes. > > > I admit I'm not 100% certain how your setup looks like. Of > course > > Alfresco can authenticate using SASL to authenticate against > the Kolab > > LDAP server. But your request sounds like you wish LDAP to > use SASL > > (something like http://tldp.org/HOWTO/LDAP-HOWTO/sasl.html) > which is > > not possible as OpenLDAP is the SASL backend and that would > result in > > a circular dependency. > > Not true! > "The DIGEST-MD5 mechanism is the mandatory-to-implement > authentication > mechanism for LDAPv3." > > Have a look at the OpenLDAP Admin Guide SASL section: -> > http://www.openldap.org/doc/admin23/sasl.html > > > Marc > > > _______________________________________________ > 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 dvadell at linuxclusters.com.ar Thu Oct 9 22:03:16 2008 From: dvadell at linuxclusters.com.ar (Diego M. Vadell) Date: Thu, 9 Oct 2008 18:03:16 -0200 Subject: Kolab creates user but does not creates its mailbox (anymore) Message-ID: <200810091803.16848.dvadell@linuxclusters.com.ar> Hi, I'm using Kolab 2.2.0 with CentOS 5.2 . I have already used this combination with great success. Today we unplugged the old Exchange server, and added the last accounts. To our surprise, those last mail accounts were in the Kolab administration web page, but the only thing that was missing was cyrus' mailbox. We started getting "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" in postfix' log. Creating the mailbox solved the problem (using cyradm, and just cm user/XXXX at domain.tdl). Also, we deleted some users and they got stuck with the "this user is deleted... waiting for cleanup" message in the admin interface. I restarted kolabd (openpkg rc kolabd stop , and then start) and those messages went away, with the deleted accounts. But the first problem still persists. I added a user with /kolab/libexec/kolab/adduser as the wiki says ( http://wiki.kolab.org/index.php/Kolab2_Server_Troubleshooting_-_Mail_accounts ) and although the user is in the admin web page now, it's cyrus mailbox does not exists. Question: What part of Kolab is responsible of creating the cyrus account, so I can futher troubleshoot it? Thanks in advance, -- Diego. From ml at radoeka.nl Thu Oct 9 23:14:06 2008 From: ml at radoeka.nl (Richard Bos) Date: Thu, 9 Oct 2008 23:14:06 +0200 Subject: Kolab creates user but does not creates its mailbox (anymore) In-Reply-To: <200810091803.16848.dvadell@linuxclusters.com.ar> References: <200810091803.16848.dvadell@linuxclusters.com.ar> Message-ID: <200810092314.06395.ml@radoeka.nl> Hi Diego, Op Thursday 09 October 2008 22:03:16 schreef Diego M. Vadell: > Question: What part of Kolab is responsible of creating the cyrus account, > so I can futher troubleshoot it? you can restart the kolab daemon (kolabd). Very often this helps, to resolve the problem. -- Richard Bos We are borrowing the world of our children, It is not inherited from our parents. From dvadell at linuxclusters.com.ar Thu Oct 9 22:25:26 2008 From: dvadell at linuxclusters.com.ar (Diego M. Vadell) Date: Thu, 9 Oct 2008 18:25:26 -0200 Subject: Kolab creates user but does not creates its mailbox (anymore) In-Reply-To: <200810092318.00630.ml@radoeka.nl> References: <200810091803.16848.dvadell@linuxclusters.com.ar> <200810092314.06395.ml@radoeka.nl> <200810092318.00630.ml@radoeka.nl> Message-ID: <200810091825.27170.dvadell@linuxclusters.com.ar> Hi, Thank you very much. But I have already done that, 3 times. It did fixed the web page (the "waiting for deletion" messages) but still it doesn't create cyrus' mailboxes. Is it kolabd responsible for making the mailbox? How can I debug it? Thanks -- Diego. On Thursday 09 October 2008 19:18:00 Richard Bos wrote: > Op Thursday 09 October 2008 23:14:06 schreef Richard Bos: > > Hi Diego, > > > > Op Thursday 09 October 2008 22:03:16 schreef Diego M. Vadell: > > > Question: What part of Kolab is responsible of creating the cyrus > > > account, so I can futher troubleshoot it? > > > > you can restart the kolab daemon (kolabd). Very often this helps, to > > resolve the problem. > > if this does not work, restart all kolab related services... > > How is it going with the patch that you dropped at the php developers? Any > sign of live from the php developers? From alex at swiftnetcomputers.biz Thu Oct 9 23:25:50 2008 From: alex at swiftnetcomputers.biz (Alex Chejlyk) Date: Thu, 09 Oct 2008 17:25:50 -0400 Subject: Kolab creates user but does not creates its mailbox (anymore) In-Reply-To: <200810092314.06395.ml@radoeka.nl> References: <200810091803.16848.dvadell@linuxclusters.com.ar> <200810092314.06395.ml@radoeka.nl> Message-ID: <48EE76DE.2020107@swiftnetcomputers.biz> I had this happen once when the server ran out of hard drive space. Richard Bos wrote: > Hi Diego, > > Op Thursday 09 October 2008 22:03:16 schreef Diego M. Vadell: >> Question: What part of Kolab is responsible of creating the cyrus account, >> so I can futher troubleshoot it? > > you can restart the kolab daemon (kolabd). Very often this helps, to resolve > the problem. > From ml at radoeka.nl Thu Oct 9 23:44:03 2008 From: ml at radoeka.nl (Richard Bos) Date: Thu, 9 Oct 2008 23:44:03 +0200 Subject: Kolab creates user but does not creates its mailbox (anymore) In-Reply-To: <200810091825.27170.dvadell@linuxclusters.com.ar> References: <200810091803.16848.dvadell@linuxclusters.com.ar> <200810092318.00630.ml@radoeka.nl> <200810091825.27170.dvadell@linuxclusters.com.ar> Message-ID: <200810092344.03760.ml@radoeka.nl> Op Thursday 09 October 2008 22:25:26 schreef Diego M. Vadell: > Hi, > Thank you very much. But I have already done that, 3 times. It did fixed > the web page (the "waiting for deletion" messages) but still it doesn't > create cyrus' mailboxes. > > Is it kolabd responsible for making the mailbox? How can I debug it? I believe it is indeed. You can debug it with setting the loglevel to e.g. 5 in the etc/kolab/kolab.conf, like: log_level : 5 and monitor the messages file. The process of adding a user, is like: Add user to ldap, ldap replicates this data to the slaves. One of the slaves is the kolabd, the kolabd extracts the info it needs, and created the mailbox. Thinking out load: would it be useful to add a real ldap slave to the system, that way it would be easy to determine whether replication works (just dump the dit from the slave). > Thanks > -- Diego. > > On Thursday 09 October 2008 19:18:00 Richard Bos wrote: > > Op Thursday 09 October 2008 23:14:06 schreef Richard Bos: > > > Hi Diego, > > > > > > Op Thursday 09 October 2008 22:03:16 schreef Diego M. Vadell: > > > > Question: What part of Kolab is responsible of creating the cyrus > > > > account, so I can futher troubleshoot it? > > > > > > you can restart the kolab daemon (kolabd). Very often this helps, to > > > resolve the problem. > > > > if this does not work, restart all kolab related services... > > > > How is it going with the patch that you dropped at the php developers? > > Any sign of live from the php developers? > > _______________________________________________ > Kolab-users mailing list > Kolab-users at kolab.org > https://kolab.org/mailman/listinfo/kolab-users -- Richard Bos We are borrowing the world of our children, It is not inherited from our parents. From dvadell at linuxclusters.com.ar Thu Oct 9 23:20:51 2008 From: dvadell at linuxclusters.com.ar (Diego M. Vadell) Date: Thu, 9 Oct 2008 19:20:51 -0200 Subject: Kolab creates user but does not creates its mailbox (anymore) - SOLVED In-Reply-To: <200810092344.03760.ml@radoeka.nl> References: <200810091803.16848.dvadell@linuxclusters.com.ar> <200810091825.27170.dvadell@linuxclusters.com.ar> <200810092344.03760.ml@radoeka.nl> Message-ID: <200810091920.52456.dvadell@linuxclusters.com.ar> Hi, I restarted openLDAP and everything started working. Somehow, kolabd was not receiving the updates. Thanks Richard for your explanation! I wouldn't have done it without it. -- Diego. On Thursday 09 October 2008 19:44:03 Richard Bos wrote: > Op Thursday 09 October 2008 22:25:26 schreef Diego M. Vadell: > > Hi, > > Thank you very much. But I have already done that, 3 times. It did > > fixed the web page (the "waiting for deletion" messages) but still it > > doesn't create cyrus' mailboxes. > > > > Is it kolabd responsible for making the mailbox? How can I debug it? > > I believe it is indeed. You can debug it with setting the loglevel to e.g. > 5 in the etc/kolab/kolab.conf, like: > log_level : 5 > and monitor the messages file. > > The process of adding a user, is like: > Add user to ldap, ldap replicates this data to the slaves. One of the > slaves is the kolabd, the kolabd extracts the info it needs, and created > the mailbox. > > Thinking out load: would it be useful to add a real ldap slave to the > system, that way it would be easy to determine whether replication works > (just dump the dit from the slave). > > > Thanks > > -- Diego. > > > > On Thursday 09 October 2008 19:18:00 Richard Bos wrote: > > > Op Thursday 09 October 2008 23:14:06 schreef Richard Bos: > > > > Hi Diego, > > > > > > > > Op Thursday 09 October 2008 22:03:16 schreef Diego M. Vadell: > > > > > Question: What part of Kolab is responsible of creating the cyrus > > > > > account, so I can futher troubleshoot it? > > > > > > > > you can restart the kolab daemon (kolabd). Very often this helps, to > > > > resolve the problem. > > > > > > if this does not work, restart all kolab related services... > > > > > > How is it going with the patch that you dropped at the php developers? > > > Any sign of live from the php developers? > > > > _______________________________________________ > > Kolab-users mailing list > > Kolab-users at kolab.org > > https://kolab.org/mailman/listinfo/kolab-users From NPrice at gibb.co.za Fri Oct 10 12:48:01 2008 From: NPrice at gibb.co.za (Price,Neil) Date: Fri, 10 Oct 2008 12:48:01 +0200 Subject: Horde sql charset error Message-ID: <7B91BBC61758DD1183BE000C296D2CA708BE67@ct-exchange.wins.lawco.com> I get this error in my logs: -------- Oct 10 12:25:01 HORDE [emergency] [horde] Required "charset" not specified in horde configuration. The file /etc/horde/horde3/../config/conf.php should contain a $conf['sql']['params']['charset'] setting. -------- My database is set to "none" in Horde (I'm assuming I don't need mysql when using Horde with Kolab) If I add the setting manually it gets wiped out on the next config change. Do I simply ignore the error or am I supposed to be using a database? Apologies if this is a really stupid question. Horde version is 3.3 From m.ouderling at linxs.nl Sun Oct 12 15:32:47 2008 From: m.ouderling at linxs.nl (Rene Ouderling) Date: Sun, 12 Oct 2008 15:32:47 +0200 Subject: Error security issue 22 Message-ID: <200810121532.47517.m.ouderling@linxs.nl> I'm having the following problem: I'm still using Kolab Server 2.1 and when i follow the instruction for security issue 22 i encounter the following error. /kolab/bin/openpkg rpm --rebuild clamav-0.94-20080905.src.rpm Installing clamav-0.94-20080905.src.rpm error: Failed build dependencies: ? ? ? ? openpkg >= 20060823 is needed by clamav-0.94-20080905 Can anyone point me in the right direction to solve this problem, could not find a similar one in the archives mvg/kind regards Rene Ouderling From jaheme at gmx.de Mon Oct 13 00:47:32 2008 From: jaheme at gmx.de (Jan - Hendrik Meyer) Date: Mon, 13 Oct 2008 00:47:32 +0200 Subject: A problem with mail delivering In-Reply-To: <20081007094101.19345yn9ajhh7ssg@webmail.pardus.de> References: <48DFAD42.20002@gmx.de> <48E60DDF.3010605@gmx.de> <20081007094101.19345yn9ajhh7ssg@webmail.pardus.de> Message-ID: <48F27E84.2040006@gmx.de> Quoting Gunnar Wrobel > Quoting Jan - Hendrik Meyer : > >> Hello, >> >> after changing some rights, > > Meaning you don't use the OpenPKG based installation? You should > always state the Kolab version you are using in error reports as it > makes it easier for us to identify possible error sources. Yes, it's a kolab 2.2 version from 14. august. > >> the cyrus server is working correctly. >> The messages I've written don't appear anymore. >> >> But without any error message, no message I've written can be found in >> the cyrus imap postbox. It's empty. >> I tested with the command: >> >> echo $(date) | mailx -s test noname at home >> >> Postfix shows some messages like this: >> >> Sep 29 20:29:33 lxmain postfix/smtp[32013]: D699C22C24C: >> to=, orig_to=, >> relay=127.0.0.1[127.0.0.1]:10024, delay=0.57, >> delays=0.18/0.02/0.01/0.37, dsn=2.0.0, status=sent (250 2.0.0 Ok: >> queued as 582D322C2AA) >> Sep 29 20:29:33 lxmain postfix/qmgr[31785]: D699C22C24C: removed >> Sep 29 20:29:33 lxmain postfix/pipe[32018]: 582D322C2AA: >> to=, relay=kolabmailboxfilter, delay=0.28, >> delays=0.06/0.02/0/0.2, dsn=2.0.0, status=sent (delivered via >> kolabmailboxfilter service) >> Sep 29 20:29:33 lxmain postfix/qmgr[31785]: 582D322C2AA: removed >> >> and >> >> amavis seems to scan the message: >> >> Sep 29 20:29:33 lxmain.Home /usr/sbin/amavisd[31563]: (31563-01) >> Passed, -> , quarantine D-8O1JfSg7tV, >> Message-ID: <20080929182932.9D8F322C2AA at lxmain.Home>, Hits: 2.34 >> Sep 29 20:29:33 lxmain.Home /usr/sbin/amavisd[31563]: (31563-01) >> Passed CLEAN, -> , Hits: 2.34, tag=3, >> tag2=6.3, kill=6.3, queued_as: 582D322C2AA, L/0/0/0 >> >> Maybe this is a message, that indicates a error: >> >> Oct 3 08:45:43 lxmain imap[26981]: dracconn: localhost: RPC: Program >> not registered >> Oct 3 08:45:43 lxmain imap[26981]: DRAC notifications disabled >> >> Does anyone know what the problem could be? > > What does the lmtp log say? I can't find any logfile. There is also no process called anything like lmtp. > > Cheers, > > Gunnar > >> >> Thanks >> >> Jan-Hendrik Meyer >> From wrobel at pardus.de Mon Oct 13 08:11:13 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Mon, 13 Oct 2008 08:11:13 +0200 Subject: A problem with mail delivering In-Reply-To: <48F27E84.2040006@gmx.de> References: <48DFAD42.20002@gmx.de> <48E60DDF.3010605@gmx.de> <20081007094101.19345yn9ajhh7ssg@webmail.pardus.de> <48F27E84.2040006@gmx.de> Message-ID: <20081013081113.88291himve88sp7o@webmail.pardus.de> Quoting Jan - Hendrik Meyer : > > Quoting Gunnar Wrobel >> Quoting Jan - Hendrik Meyer : >> >>> Hello, >>> >>> after changing some rights, >> >> Meaning you don't use the OpenPKG based installation? You should >> always state the Kolab version you are using in error reports as it >> makes it easier for us to identify possible error sources. > Yes, it's a kolab 2.2 version from 14. august. Installed based on OpenPKG? I'm slightly confused as the 2.2.0 Release was on 12th July. But maybe you refer to your installation date. Anyhow I'm not certain why you had to modify some of the rights. On a standard Kolab server installation this should not be necessary at all. So I'm wondering why modifications were necessary and which modifications you made? >> >>> the cyrus server is working correctly. >>> The messages I've written don't appear anymore. >>> >>> But without any error message, no message I've written can be found in >>> the cyrus imap postbox. It's empty. >>> I tested with the command: >>> >>> echo $(date) | mailx -s test noname at home >>> >>> Postfix shows some messages like this: >>> >>> Sep 29 20:29:33 lxmain postfix/smtp[32013]: D699C22C24C: >>> to=, orig_to=, >>> relay=127.0.0.1[127.0.0.1]:10024, delay=0.57, >>> delays=0.18/0.02/0.01/0.37, dsn=2.0.0, status=sent (250 2.0.0 Ok: >>> queued as 582D322C2AA) >>> Sep 29 20:29:33 lxmain postfix/qmgr[31785]: D699C22C24C: removed >>> Sep 29 20:29:33 lxmain postfix/pipe[32018]: 582D322C2AA: >>> to=, relay=kolabmailboxfilter, delay=0.28, >>> delays=0.06/0.02/0/0.2, dsn=2.0.0, status=sent (delivered via >>> kolabmailboxfilter service) >>> Sep 29 20:29:33 lxmain postfix/qmgr[31785]: 582D322C2AA: removed >>> >>> and >>> >>> amavis seems to scan the message: >>> >>> Sep 29 20:29:33 lxmain.Home /usr/sbin/amavisd[31563]: (31563-01) >>> Passed, -> , quarantine D-8O1JfSg7tV, >>> Message-ID: <20080929182932.9D8F322C2AA at lxmain.Home>, Hits: 2.34 >>> Sep 29 20:29:33 lxmain.Home /usr/sbin/amavisd[31563]: (31563-01) >>> Passed CLEAN, -> , Hits: 2.34, tag=3, >>> tag2=6.3, kill=6.3, queued_as: 582D322C2AA, L/0/0/0 >>> >>> Maybe this is a message, that indicates a error: >>> >>> Oct 3 08:45:43 lxmain imap[26981]: dracconn: localhost: RPC: Program >>> not registered >>> Oct 3 08:45:43 lxmain imap[26981]: DRAC notifications disabled >>> >>> Does anyone know what the problem could be? >> >> What does the lmtp log say? > I can't find any logfile. There is also no process called anything like > lmtp. That there is no process called lmtp is okay. This is just a temporary process when processing a message. The log file should be located at /kolab/var/imapd/log/lmtpd.log. If there is no such log file it would mean cyrus never actually gets messages delivered from postfix. Do you have anything in the log file /kolab/var/kolab-filter/log/filter.log? This is the filter that should contact the cyrus imap server. Cheers, Gunnar > >> >> Cheers, >> >> Gunnar >> >>> >>> Thanks >>> >>> Jan-Hendrik Meyer >>> > > _______________________________________________ > 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/20081013/01158aaf/attachment.bin From wrobel at pardus.de Mon Oct 13 08:38:39 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Mon, 13 Oct 2008 08:38:39 +0200 Subject: Toltec connector duplicates appointment attendees In-Reply-To: <1223541118l.24908l.1l@pc104141.koeln.nktcables.com> References: <1223541118l.24908l.1l@pc104141.koeln.nktcables.com> Message-ID: <20081013083839.21124kvdpbf7ccg0@webmail.pardus.de> Quoting Albrecht Dre? : > Hi all, > > while evaluating the Toltec connector and Toltec LDAP address book for > Outlook I found a puzzling behaviour... > > I created two users "Test 1 Benutzer" and "Test 2 Benutzer", both > accepting invitations automatically. Invitations are sent from "Test 1 > Benutzer" to "Test 2 Benutzer", taking the latter from the LDAP address > book. > > If I configure the LDAP address book to show names as "First Last", > everything works fine. However, setting it to display names as "Last, > First" (which results in "Benutzer, Test 2" for the example above), the > "accept" message will create a /second/ user in the appointment object > in IMAP: > > > Benutzer, Test 2 > test2 at my-company.com > none > true > required > > > Test 2 Benutzer > test2 at my-company.com > accepted > true > optional > > > The first entry was the original one, and the second has been added. I > checked the vcalendar message produced automatically, and it contains > only "ATTENDEE;PARTSTAT=ACCEPTED:MAILTO:test2 at my-company.com". > > I'm not sure whether Toltec or Outlook or Kolab is the source of the > bug, but it is somewhat annoying... Any idea how it could be fixed? I looked at the code and to me it looks like a Toltec bug then. The resource management code only takes information from the iTip message and stores it on the IMAP server. It does not does not mangle the list of attendees as far as I can see. Could you change the invitation handling to "manual" for your test user so that the messages don't get processed automatically. This way you could take a look at the invitation you get from Toltec. 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/20081013/1effd9a6/attachment.bin From wrobel at pardus.de Mon Oct 13 08:51:35 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Mon, 13 Oct 2008 08:51:35 +0200 Subject: Error security issue 22 In-Reply-To: <200810121532.47517.m.ouderling@linxs.nl> References: <200810121532.47517.m.ouderling@linxs.nl> Message-ID: <20081013085135.189913en18mirieo@webmail.pardus.de> Quoting Rene Ouderling : > I'm having the following problem: > I'm still using Kolab Server 2.1 and when i follow the instruction for > security issue 22 i encounter the following error. > > /kolab/bin/openpkg rpm --rebuild clamav-0.94-20080905.src.rpm > Installing clamav-0.94-20080905.src.rpm > error: Failed build dependencies: > openpkg >= 20060823 is needed by clamav-0.94-20080905 Oh, that is not okay and a bug. Thanks for the info. @Thomas: I think this would need fixing. Cheers, Gunnar > > Can anyone point me in the right direction to solve this problem, could not > find a similar one in the archives > > mvg/kind regards > > Rene Ouderling > > _______________________________________________ > 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/20081013/37218ae6/attachment.bin From wrobel at pardus.de Mon Oct 13 08:56:06 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Mon, 13 Oct 2008 08:56:06 +0200 Subject: Horde sql charset error In-Reply-To: <7B91BBC61758DD1183BE000C296D2CA708BE67@ct-exchange.wins.lawco.com> References: <7B91BBC61758DD1183BE000C296D2CA708BE67@ct-exchange.wins.lawco.com> Message-ID: <20081013085606.94484a52rk1ddvcw@webmail.pardus.de> Hi Neil, Quoting "Price,Neil" : > > I get this error in my logs: > > -------- > Oct 10 12:25:01 HORDE [emergency] [horde] Required "charset" not specified > in horde configuration. > > The file /etc/horde/horde3/../config/conf.php should contain a > $conf['sql']['params']['charset'] setting. > -------- > > My database is set to "none" in Horde (I'm assuming I don't need mysql when > using Horde with Kolab) Indeed you don't need it. > > If I add the setting manually it gets wiped out on the next config change. > > Do I simply ignore the error or am I supposed to be using a database? > Apologies if this is a really stupid question. I would not ignore errors in the Horde log files. It looks like the person configuring Horde for your system made some mistakes. > > Horde version is 3.3 Not supported with Kolab (yet). At least not from my side. Some bugs are to be expected :) I assume that Kolab-Server-2.2.1 will also provide Horde-3.3 but it will have some patches. You are obviously running on one of the native ports and as usual some bugs can be expected there. Cheers, Gunnar > > _______________________________________________ > 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/20081013/b579e2a2/attachment-0001.bin From wrobel at pardus.de Mon Oct 13 08:57:17 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Mon, 13 Oct 2008 08:57:17 +0200 Subject: calendar user gets a http 404 error? In-Reply-To: <1223540510l.24908l.0l@pc104141.koeln.nktcables.com> References: <1223540510l.24908l.0l@pc104141.koeln.nktcables.com> Message-ID: <20081013085717.190753k6o02n0w4k@webmail.pardus.de> Quoting Albrecht Dre? : > Am 09.10.2008 09:45:31 schrieb(en) Gunnar Wrobel: >>> srv-kolab.my-company.de - calendar at my-company.com >>> [08/Oct/2008:13:58:30 +0200] "GET >>> /freebusy/trigger/test2%40my-company.com/Kalender.pfb HTTP/1.0" 404 >>> 468 >> >> Try to enter that URL into your normal browser. This should show you >> why you actually get 404 here. > > O.k., loaded the page in Firefox as "calendar at my-company.com" using the > password I found in /kolab/etc/kolab/kolab.conf and got: > > > Not found > > The requested URL /freebusy/trigger/test2%40my-company.com/Kalender.pfb > was not found on this server. > > IMAP error. Folder: user/test2/Kalender. Error: Permission denied > > Apache/2.2.8 (OpenPKG/CURRENT) mod_ssl/2.2.8 OpenSSL/0.9.8g PHP/5.2.6 > Server at 10.16.0.1 Port 443 > > > I do not understand this message, as the calendar user *does* have full > permissions on this folder: > > > root at srv-kolab:~# /kolab/bin/cyradm --user test2 localhost > Password:localhost> lam INBOX/Kalender > test2 at my-domain.com lrswikxtecda > calendar at my-domain.com lrswipkxtecd > > > Any idea? Looks like a bug. Any relevant lines in your free/busy log (at /kolab/var/kolab-freebusy/log/freebusy.log)? What happens if you give admin ("a") rights to the calendar user? 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/20081013/9a662164/attachment.bin From Roessler at FuH-E.de Mon Oct 13 09:59:51 2008 From: Roessler at FuH-E.de (=?ISO-8859-1?Q?Christian_R=F6=DFler?=) Date: Mon, 13 Oct 2008 09:59:51 +0200 Subject: Expanding user.php so it enters three more fields into LDAP Message-ID: <48F2FFF7.6060101@FuH-E.de> Good morning to everyone, I am working for some time with Kolab, and I have to say I think it is a very nice software. Now I try to enhance the admin interface a bit while evaluating the possibility of a migration to Kolab Well, my problem is such: I want to get sone posixGroup functionality for the user type 'groups'. As I obviously cannot just connect posixGroup to the object (as inetOrgPerson/kolabInetOrgPerson would be present) I have thought of making a scheme of my own with an auxiliary objectClass, which brings the three attributes I need. These attributes would be 'generate/delete companion posixGroup, list of UIDs for group, eventually password'. Then I would use a script to generate a posixGroup at the appropriate place in the hierarchy. This already functions reasonably well. But I fail in modifying user.php as such, that it writes my objectClass (with the three attributes) to LDAP - regrettably my PHP knowledge is rather bad. So I would be most grateful if anyone could help me. Best regards and many thanks, Christian R??ler (Roessler) PS. My scheme uses this attributes: generateCompanionGroup - boolean - SINGLE-VALUE membersCompanionGroup - IA5 - SINGLE-VALUE passwordCompanionGroup - IA5 - SINGLE-VALUE ...and the object is: companionGroup - AUXILIARY - MUST ( generateCompanionGroup ) MAY ( membersCompanionGroup $ passwordCompanionGroup ) ) From albrecht.dress at lios-tech.com Mon Oct 13 12:18:25 2008 From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=) Date: Mon, 13 Oct 2008 12:18:25 +0200 Subject: calendar user gets a http 404 error? In-Reply-To: <20081013085717.190753k6o02n0w4k@webmail.pardus.de> (from wrobel@pardus.de on Mon Oct 13 08:57:17 2008) Message-ID: <1223893105l.16237l.2l@pc104141.koeln.nktcables.com> Hi Gunnar! Am 13.10.2008 08:57:17 schrieb(en) Gunnar Wrobel: > Looks like a bug. Any relevant lines in your free/busy log (at > /kolab/var/kolab-freebusy/log/freebusy.log)? Here's a full story of a request from freebusy.log (delay caused by entering the calendar pwd manually): Oct 13 11:52:32 Kolab Free/Busy [debug] [horde] Starting generation of partial free/busy data for folder test2 at my-company.com/Kalender [pid 26601 on line 52 of "/kolab/var/kolab/www/freebusy/pfb.php"] Oct 13 11:52:32 Kolab Free/Busy [debug] [horde] Partial free/busy data of owner test2 at my-company.com on server srv-portal.my-company.de requested by user . [pid 26601 on line 63 of "/kolab/var/kolab/www/freebusy/pfb.php"] Oct 13 11:52:32 Kolab Free/Busy [error] [horde] Please authenticate! [pid 26601 on line 124 of "/kolab/lib/php/Kolab/Freebusy/Page.php"] Oct 13 11:52:58 Kolab Free/Busy [debug] [horde] Starting generation of partial free/busy data for folder test2 at my-company.com/Kalender [pid 26170 on line 52 of "/kolab/var/kolab/www/freebusy/pfb.php"] Oct 13 11:52:58 Kolab Free/Busy [debug] [horde] Partial free/busy data of owner test2 at my-company.com on server srv-portal.my-company.de requested by user calendar at my-company.com. [pid 26170 on line 63 of "/kolab/var/kolab/www/freebusy/pfb.php"] Oct 13 11:52:59 Kolab Free/Busy [debug] [horde] Creating free/busy information from 1223848800 to 1229036400 [pid 26170 on line 312 of "/kolab/lib/php/Horde/Kolab/Freebusy.php"] Oct 13 11:52:59 Kolab Free/Busy [debug] [horde] Relevance for user/test2/Kalender is readers [pid 26170 on line 211 of "/kolab/lib/php/Horde/Kolab/Freebusy.php"] Oct 13 11:52:59 Kolab Free/Busy [error] [horde] IMAP error. Folder: user/test2/Kalender. Error: Permission denied [pid 26170 on line 124 of "/kolab/lib/php/Kolab/Freebusy/Page.php"] php-error.log says: [13-Oct-2008 11:52:58] PHP Notice: Undefined index: umask in /kolab/lib/php/Horde.php on line 523 [13-Oct-2008 11:52:59] PHP Notice: Unknown: SECURITY PROBLEM: insecure server advertised AUTH=PLAIN (errflg=1) in Unknown on line 0 [13-Oct-2008 11:52:59] PHP Notice: Unknown: SECURITY PROBLEM: insecure server advertised AUTH=PLAIN (errflg=1) in Unknown on line 0 [13-Oct-2008 11:52:59] PHP Notice: Unknown: SECURITY PROBLEM: insecure server advertised AUTH=PLAIN (errflg=1) in Unknown on line 0 [13-Oct-2008 11:52:59] PHP Notice: Unknown: Permission denied (errflg=2) in Unknown on line 0 And apache-access.log: test.my-company.de - - [13/Oct/2008:11:52:32 +0200] "GET /freebusy/trigger/test2%40my-company.com/Kalender.pfb HTTP/1.1" 401 365 test.my-company.de - calendar at my-company.com [13/Oct/2008:11:52:58 +0200] "GET /freebusy/trigger/test2%40my-company.com/Kalender.pfb HTTP/1.1" 404 453 > What happens if you give admin ("a") rights to the calendar user? I added the "a" flag, is that correct (i.e. the rights are now "calendar at my-company.com lrswipkxtecda")? Anyway, it seems to work now, thanks! The bad thing is that I changed the access rights using the Toltec connector according to the "Proko2 Doc3" documentation, giving the calendar user full access (i.e. ticking all check boxes). Apparently, there is *no* difference in the Toltec interface between "lrswipkxtecda" and "lrswipkxtecd". Is there a method where I can set the proper rights to all Kalender boxes, btw? Thanks, Albrecht. From albrecht.dress at lios-tech.com Mon Oct 13 12:29:16 2008 From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=) Date: Mon, 13 Oct 2008 12:29:16 +0200 Subject: Toltec connector duplicates appointment attendees In-Reply-To: <20081013083839.21124kvdpbf7ccg0@webmail.pardus.de> (from wrobel@pardus.de on Mon Oct 13 08:38:39 2008) Message-ID: <1223893756l.16237l.3l@pc104141.koeln.nktcables.com> Hi Gunnar! Am 13.10.2008 08:38:39 schrieb(en) Gunnar Wrobel: > I looked at the code and to me it looks like a Toltec bug then. The > resource management code only takes information from the iTip message > and stores it on the IMAP server. It does not does not mangle the > list of attendees as far as I can see. I got a response from Toltec support which indicates that it is really a problem there: It seems that Outlook is using the table restriction method in the Toltec LDAP Address Book to do a look up of the user display name instead of the SMTP address. Now obviously the display name is turned around when using last name first and this is why Outlook cannot match it and creates a new attendee. I will look if there is some way to normalize the display name when Outlook passes is to the LDAP address book. I'll keep you informed when they have any news (and hopefully a fix). > Could you change the invitation handling to "manual" for your test > user so that the messages don't get processed automatically. This way > you could take a look at the invitation you get from Toltec. Looks fine, it only includes the participant's mail address, regardless of the particular setting of the LDAP address book name display. Thanks, Albrecht. From wrobel at pardus.de Tue Oct 14 07:07:27 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Tue, 14 Oct 2008 07:07:27 +0200 Subject: calendar user gets a http 404 error? In-Reply-To: <1223893105l.16237l.2l@pc104141.koeln.nktcables.com> References: <1223893105l.16237l.2l@pc104141.koeln.nktcables.com> Message-ID: <20081014070727.1114271w8a512txc@webmail.pardus.de> Quoting Albrecht Dre? : > Hi Gunnar! > > Am 13.10.2008 08:57:17 schrieb(en) Gunnar Wrobel: >> Looks like a bug. Any relevant lines in your free/busy log (at >> /kolab/var/kolab-freebusy/log/freebusy.log)? > > Here's a full story of a request from freebusy.log (delay caused by > entering the calendar pwd manually): > > > Oct 13 11:52:32 Kolab Free/Busy [debug] [horde] Starting generation of > partial free/busy data for folder test2 at my-company.com/Kalender [pid > 26601 on line 52 of "/kolab/var/kolab/www/freebusy/pfb.php"] > Oct 13 11:52:32 Kolab Free/Busy [debug] [horde] Partial free/busy data > of owner test2 at my-company.com on server srv-portal.my-company.de > requested by user . [pid 26601 on line 63 of > "/kolab/var/kolab/www/freebusy/pfb.php"] > Oct 13 11:52:32 Kolab Free/Busy [error] [horde] Please authenticate! > [pid 26601 on line 124 of "/kolab/lib/php/Kolab/Freebusy/Page.php"] > Oct 13 11:52:58 Kolab Free/Busy [debug] [horde] Starting generation of > partial free/busy data for folder test2 at my-company.com/Kalender [pid > 26170 on line 52 of "/kolab/var/kolab/www/freebusy/pfb.php"] > Oct 13 11:52:58 Kolab Free/Busy [debug] [horde] Partial free/busy data > of owner test2 at my-company.com on server srv-portal.my-company.de > requested by user calendar at my-company.com. [pid 26170 on line 63 of > "/kolab/var/kolab/www/freebusy/pfb.php"] > Oct 13 11:52:59 Kolab Free/Busy [debug] [horde] Creating free/busy > information from 1223848800 to 1229036400 [pid 26170 on line 312 of > "/kolab/lib/php/Horde/Kolab/Freebusy.php"] > Oct 13 11:52:59 Kolab Free/Busy [debug] [horde] Relevance for > user/test2/Kalender is readers [pid 26170 on line 211 of > "/kolab/lib/php/Horde/Kolab/Freebusy.php"] > Oct 13 11:52:59 Kolab Free/Busy [error] [horde] IMAP error. Folder: > user/test2/Kalender. Error: Permission denied [pid 26170 on line 124 of > "/kolab/lib/php/Kolab/Freebusy/Page.php"] > > > php-error.log says: > > > [13-Oct-2008 11:52:58] PHP Notice: Undefined index: umask in > /kolab/lib/php/Horde.php on line 523 > [13-Oct-2008 11:52:59] PHP Notice: Unknown: SECURITY PROBLEM: insecure > server advertised AUTH=PLAIN (errflg=1) in Unknown on line 0 > [13-Oct-2008 11:52:59] PHP Notice: Unknown: SECURITY PROBLEM: insecure > server advertised AUTH=PLAIN (errflg=1) in Unknown on line 0 > [13-Oct-2008 11:52:59] PHP Notice: Unknown: SECURITY PROBLEM: insecure > server advertised AUTH=PLAIN (errflg=1) in Unknown on line 0 > [13-Oct-2008 11:52:59] PHP Notice: Unknown: Permission denied > (errflg=2) in Unknown on line 0 > > > And apache-access.log: > > > test.my-company.de - - [13/Oct/2008:11:52:32 +0200] "GET > /freebusy/trigger/test2%40my-company.com/Kalender.pfb HTTP/1.1" 401 365 > test.my-company.de - calendar at my-company.com [13/Oct/2008:11:52:58 > +0200] "GET /freebusy/trigger/test2%40my-company.com/Kalender.pfb > HTTP/1.1" 404 453 > > >> What happens if you give admin ("a") rights to the calendar user? > > I added the "a" flag, is that correct (i.e. the rights are now > "calendar at my-company.com lrswipkxtecda")? Anyway, it seems to work > now, thanks! > > The bad thing is that I changed the access rights using the Toltec > connector according to the "Proko2 Doc3" documentation, giving the > calendar user full access (i.e. ticking all check boxes). Apparently, > there is *no* difference in the Toltec interface between > "lrswipkxtecda" and "lrswipkxtecd". Is there a method where I can set > the proper rights to all Kalender boxes, btw? I don't think you need to do that. Can you try to apply the patch in https://www.intevation.de/roundup/kolab/issue3074 and see if it also resolves the problem? 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/20081014/eac81f59/attachment.bin From wrobel at pardus.de Tue Oct 14 08:00:12 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Tue, 14 Oct 2008 08:00:12 +0200 Subject: Kolab 2.2 upgrade from 2.1 failure on php-channel-horde In-Reply-To: <200810091802.41479.mark@rtsw.co.uk> References: <200810031150.47986.mark@rtsw.co.uk> <20081007095704.177818rd30oyknk0@webmail.pardus.de> <200810091802.41479.mark@rtsw.co.uk> Message-ID: <20081014080012.656740ogkj8685us@webmail.pardus.de> Quoting Mark Seagrief : > On Tuesday 07 October 2008 08:57, Gunnar Wrobel wrote: >> Quoting Mark Seagrief : >> > Hi, >> > >> > I kicked off an upgrade of a Kolab installation last night to upgrade >> > from 2.1.0 to 2.2.0. >> > >> > I'm installing from source on Ubuntu 7.04 server edition with kernel >> > 2.6.20-16-server. >> > >> > Most of the RPMs seem to have built correctly and installed fine, but >> > php-channel-horde seems to have failed. >> > >> > The final few lines of the log are: >> > >> > >> > Package Horde_Alarm-0.1.0.tgz done >> > Tag the released code with `pear cvstag Alarm/package.xml' >> > (or set the CVS tag RELEASE_0_1_0 by hand) >> > + env 'PHP_PEAR_PHP_BIN=/kolab/bin/php -d safe_mode=off -d >> > memory_limit=40M' PHP_PEAR_CACHE_DIR=/kolab/RPM/TMP/pear/cache >> > /kolab/bin/pear install --force --loose --nodeps --offline >> > --packagingroot=/kolab/RPM/TMP/horde-framework-kolab-3.2_rc3-root >> > Horde_Alarm-0.1.0.tgz >> > could not extract the package.xml file from "Horde_Alarm-0.1.0.tgz" >> > Cannot download non-local package "Horde_Alarm-0.1.0.tgz" >> > Package "Horde_Alarm-0.1.0.tgz" is not valid >> > install failed >> > error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.48129 (%install) >> >> These lines seem to originate from the horde-framework installation >> rather than from php-channel-horde. Can you post the log messages >> concerning php-channel-horde since you say compilation failed for that >> one. >> >> Cheers, >> >> Gunnar >> >> > I've check on the system and I do have a file that has been created >> > called Horde_Alarm-0.1.0.tgz in /kolab/RPM/TMP/framework/ >> > >> > Any ideas as to what is causing this problem? Anybody encountered >> > something similar? >> > >> > I'm going to grab another machine and try an installtion of 2.2 from >> > scratch and see if that helps/exhibits this problem. >> > >> > Many thanks, >> > >> > Mark >> > >> > -- >> > >> > Mark Seagrief >> > RT Software >> > >> > _______________________________________________ >> > Kolab-users mailing list >> > Kolab-users at kolab.org >> > https://kolab.org/mailman/listinfo/kolab-users > > Hi Gunnar, > > Sorry for the delay in getting back to you. > > I've had another look through the logs and I was initially mistaken, > php-channel-horde does appear to have worked. I have the following in my log > file: > > > Preparing... > ################################################## > php-channel-horde > ################################################## > channel-add: Channel "pear.horde.org" exists, use channel-update to update > entry > Channel already exists! > Update of Channel "pear.horde.org" succeeded > :::: > /tmp/install-kolab.20815.18405.11728.1940/php-channel-horde-1.0-1.src.rpm > = 0 :::: > :::: > /tmp/install-kolab.20815.18405.11728.1940/horde-framework-kolab-3.2_rc3-20080405.src.rpm > :::: > Installing > /tmp/install-kolab.20815.18405.11728.1940/horde-framework-kolab-3.2_rc3-20080405.src.rpm > > > So I assume it is the building of the horde-framework-kolab rpm from source > that is failing. I've attached a snippet of the log file with the, > hopefully, relevant output. I've taken out the output from a tar command > that listed a few thousand lines of files, but left in the lines for the > files for the Alarm. Hm, it is hard to tell from the log output why PEAR if trying to download the package rather than using the one provided within the RPM package. But PEAR is definitely confused there. I'll build another Kolab-2.2 soon and will compare the log output of a successful install with the snippet you sent and get back to you then. In any case it would be good if you create a bug report as a reminder. Cheers, Gunnar > > Many thanks for your time, > > Cheers, > > Mark > > -- > > Mark Seagrief > RT Software > e: mark at rtsw.co.uk > t: +44 207 16 888 20 > p: Unit D, 2 Chesney Street, Battersea, London, SW11 5JT > -- ______ 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/20081014/ce312735/attachment.bin From thomas at intevation.de Tue Oct 14 08:18:48 2008 From: thomas at intevation.de (Thomas Arendsen Hein) Date: Tue, 14 Oct 2008 08:18:48 +0200 Subject: Error security issue 22 In-Reply-To: <20081013085135.189913en18mirieo@webmail.pardus.de> References: <200810121532.47517.m.ouderling@linxs.nl> <20081013085135.189913en18mirieo@webmail.pardus.de> Message-ID: <20081014061848.GB25621.thomas@intevation.de> * Gunnar Wrobel [20081013 08:51]: > Quoting Rene Ouderling : > > >I'm having the following problem: > >I'm still using Kolab Server 2.1 and when i follow the instruction for > >security issue 22 i encounter the following error. > > > >/kolab/bin/openpkg rpm --rebuild clamav-0.94-20080905.src.rpm > >Installing clamav-0.94-20080905.src.rpm > >error: Failed build dependencies: > > openpkg >= 20060823 is needed by clamav-0.94-20080905 > > Oh, that is not okay and a bug. Thanks for the info. > > @Thomas: I think this would need fixing. Citing the instructions: | The ClamAV source RPM patched to be compilable with Kolab Server 2.1 and 2.0 | is available from the Kolab download mirrors as: | security-updates/20080911/clamav-0.94-20080905_kolab.src.rpm So just juse the other .src.rpm and it should work. Regards, Thomas -- thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998 Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available Url : http://kolab.org/pipermail/kolab-users/attachments/20081014/c50e457d/attachment-0001.bin From albrecht.dress at lios-tech.com Tue Oct 14 09:57:54 2008 From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=) Date: Tue, 14 Oct 2008 09:57:54 +0200 Subject: calendar user gets a http 404 error? In-Reply-To: <20081014070727.1114271w8a512txc@webmail.pardus.de> (from wrobel@pardus.de on Tue Oct 14 07:07:27 2008) References: <1223893105l.16237l.2l@pc104141.koeln.nktcables.com> <20081014070727.1114271w8a512txc@webmail.pardus.de> Message-ID: <1223971074l.21406l.0l@pc104141.koeln.nktcables.com> Hi Gunnar! Am 14.10.2008 07:07:27 schrieb(en) Gunnar Wrobel: > I don't think you need to do that. Can you try to apply the patch in > > https://www.intevation.de/roundup/kolab/issue3074 > > and see if it also resolves the problem? Yes, it then simply works. Thanks a lot for your support! Cheers, Albrecht. From Andreas.Gungl at osp-dd.de Tue Oct 14 10:32:37 2008 From: Andreas.Gungl at osp-dd.de (Andreas Gungl) Date: Tue, 14 Oct 2008 10:32:37 +0200 Subject: Client stati questions Message-ID: <200810141032.37665@osp-dd.de> Hello, I have questions regarding the status of the Kolab clients. 1) What about Kontact for MacOS? Is it available in a stable version yet? If yes, are there some kind of packages available for download, or do I need to compile from source? 2) AFAIR Horde is considered to be stable enough for production use in combination with a Kolab server. What about the CalDAV support in Horde? Does it work with Kolab out of the box, or will that work only in a future release? Thanks to all who can provide answers to the questions. Kolab works like a charm in combination with Linux clients. But if we talk about MacOS, I'm a bit lost regarding reasonable information about what's possible right now. Andreas From akopciuch at bddf.ca Tue Oct 14 10:49:52 2008 From: akopciuch at bddf.ca (Andrew J. Kopciuch) Date: Tue, 14 Oct 2008 02:49:52 -0600 Subject: Client stati questions In-Reply-To: <200810141032.37665@osp-dd.de> References: <200810141032.37665@osp-dd.de> Message-ID: <200810140249.59570.akopciuch@bddf.ca> On October 14, 2008, Andreas Gungl wrote: > Hello, > > I have questions regarding the status of the Kolab clients. > > 1) What about Kontact for MacOS? Is it available in a stable version yet? > If yes, are there some kind of packages available for download, or do I > need to compile from source? > http://mac.kde.org/ All the info about running KDE stuff for macs can be found there. Andy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. Url : http://kolab.org/pipermail/kolab-users/attachments/20081014/de3bded7/attachment.bin From Andreas.Gungl at osp-dd.de Tue Oct 14 11:08:50 2008 From: Andreas.Gungl at osp-dd.de (Andreas Gungl) Date: Tue, 14 Oct 2008 11:08:50 +0200 Subject: Client stati questions In-Reply-To: <200810140249.59570.akopciuch@bddf.ca> References: <200810141032.37665@osp-dd.de> <200810140249.59570.akopciuch@bddf.ca> Message-ID: <200810141108.50335@osp-dd.de> Am Tuesday 14 October 2008 schrieb Andrew J. Kopciuch: > On October 14, 2008, Andreas Gungl wrote: > > Hello, > > > > I have questions regarding the status of the Kolab clients. > > > > 1) What about Kontact for MacOS? Is it available in a stable version > > yet? If yes, are there some kind of packages available for download, or > > do I need to compile from source? > > http://mac.kde.org/ > > All the info about running KDE stuff for macs can be found there. Thanks for the pointer. The pages aren't very detailed about the state of "KDE 4.1.2 Packages for Mac OS X 10.4 and 10.5" though. I assume the kdepim programs (not kdepimlibs) are in the KDE-Mac_Everything.dmg - is that true? Because the KDE-Mac_KDE4.1.2_1.1.dmg doesn't have them. Do you already have experience with Kontact of KDE 4 on a Mac? Can you recommend to use it? Andreas From devgioiatech at gmail.com Tue Oct 14 12:12:06 2008 From: devgioiatech at gmail.com (Antonio Straziota) Date: Tue, 14 Oct 2008 12:12:06 +0200 Subject: Alfresco + Kolab authentication In-Reply-To: <1223565236.15177.20.camel@black> References: <48EDC55F.5020004@ofd-sth.niedersachsen.de> <1223565236.15177.20.camel@black> Message-ID: hi, i'm sorry, but i can't write a document about this because i'm only kolab admin... A developer is responsible of the integration with alfresco and he ask me if is possibile to autenticate kolab user through MD5 encryption. sorry...:( 2008/10/9 Del > Hello Antonio, > > Please make time to document your solution in the wiki as you go along: > http://wiki.kolab.org/index.php/Main_Page > You are not the only one interested in a document management system ;) > > Cheers, > Del > > On Thu, 2008-10-09 at 12:22 +0200, Antonio Straziota wrote: > > hi, > > thanks to all for the reply. > > > > So, It could be possible using secrets stored in the LDAP? > > > > From the link posted by Marc: > > > > "This section describes the use of the SASL DIGEST-MD5 mechanism using > > secrets stored either in the directory itself or in Cyrus SASL's own > > database. DIGEST-MD5 relies on the client and the server sharing a > > "secret", usually a password" > > > > Is it correct? > > > > I'll try it. Thanks for the help... > > > > PS: Any other suggetion are welcome :D > > > > bye > > > > 2008/10/9 Marc Patermann > > Gunnar Wrobel schrieb: > > > Quoting Antonio Straziota : > > > > > > >> Now i've to configure Alfresco with LDAP. With SIMPLE > > autentication > > >> mode i've no problem, but i want to configure the > > authentication > > > > >> metod in DIGEST$B!](BMD5. > > >> > > >> Can i configure Kolab LDAP to accept connection in SASL > > DIGEST-MD5? > > > > Yes. > > > > > I admit I'm not 100% certain how your setup looks like. Of > > course > > > Alfresco can authenticate using SASL to authenticate against > > the Kolab > > > LDAP server. But your request sounds like you wish LDAP to > > use SASL > > > (something like http://tldp.org/HOWTO/LDAP-HOWTO/sasl.html) > > which is > > > not possible as OpenLDAP is the SASL backend and that would > > result in > > > a circular dependency. > > > > Not true! > > "The DIGEST-MD5 mechanism is the mandatory-to-implement > > authentication > > mechanism for LDAPv3." > > > > Have a look at the OpenLDAP Admin Guide SASL section: -> > > http://www.openldap.org/doc/admin23/sasl.html > > > > > > Marc > > > > > > _______________________________________________ > > 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/20081014/95f39cfe/attachment.html From m.ouderling at linxs.nl Tue Oct 14 13:42:52 2008 From: m.ouderling at linxs.nl (Rene Ouderling) Date: Tue, 14 Oct 2008 13:42:52 +0200 Subject: Error security issue 22 In-Reply-To: <20081014061848.GB25621.thomas@intevation.de> References: <200810121532.47517.m.ouderling@linxs.nl> <20081013085135.189913en18mirieo@webmail.pardus.de> <20081014061848.GB25621.thomas@intevation.de> Message-ID: <200810141342.52598.m.ouderling@linxs.nl> Op dinsdag 14 oktober 2008 08:18, schreef Thomas Arendsen Hein: > * Gunnar Wrobel [20081013 08:51]: > > Quoting Rene Ouderling : > > >I'm having the following problem: > > >I'm still using Kolab Server 2.1 and when i follow the instruction for > > >security issue 22 i encounter the following error. > > > > > >/kolab/bin/openpkg rpm --rebuild clamav-0.94-20080905.src.rpm > > >Installing clamav-0.94-20080905.src.rpm > > >error: Failed build dependencies: > > > openpkg >= 20060823 is needed by clamav-0.94-20080905 > > > > Oh, that is not okay and a bug. Thanks for the info. > > > > @Thomas: I think this would need fixing. > > Citing the instructions: > | The ClamAV source RPM patched to be compilable with Kolab Server 2.1 and > | 2.0 is available from the Kolab download mirrors as: > | security-updates/20080911/clamav-0.94-20080905_kolab.src.rpm > > So just juse the other .src.rpm and it should work. > > Regards, > Thomas Sorry for the stupid mistake. I was indeed using the wrong src.rpm. Thnx Mvg Rene Ouderling From kcaesar at hotmail.com Tue Oct 14 15:14:18 2008 From: kcaesar at hotmail.com (kiser Caesar) Date: Tue, 14 Oct 2008 15:14:18 +0200 Subject: New kolab version ? Message-ID: Hello, When will be available the new verrsion of Kolab (beta or final)? With the SyncML support ? I do not see any recent news on the roadmap: ( Thank you! _________________________________________________________________ Email envoy? avec Windows Live Hotmail. Dites adieux aux spam et virus, passez ? Hotmail?! C'est gratuit ! http://www.windowslive.fr/hotmail/default.asp -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: http://kolab.org/pipermail/kolab-users/attachments/20081014/f75a9f2e/attachment.html From delonly at gmail.com Tue Oct 14 20:01:42 2008 From: delonly at gmail.com (Del) Date: Tue, 14 Oct 2008 20:01:42 +0200 Subject: New kolab version ? In-Reply-To: References: Message-ID: <1224007302.9441.7.camel@merom> Hello Gunnar is working on it and has indicated beta version early November, just look back a couple of weeks in this list and you will find the information. You are not the only one waiting ;) Cheers, Del On Tue, 2008-10-14 at 15:14 +0200, kiser Caesar wrote: > > Hello, > > When will be available the new verrsion of Kolab (beta or final)? With > the SyncML support ? > I do not see any recent news on the roadmap: ( > > > Thank you! > > ______________________________________________________________________ > Qui vous permet d'enregistrer la TV sur votre PC et lire vos emails > sur votre mobile ? la r?ponse en vid?o la r?ponse en vid?o > _______________________________________________ > Kolab-users mailing list > Kolab-users at kolab.org > https://kolab.org/mailman/listinfo/kolab-users From delonly at gmail.com Tue Oct 14 20:04:14 2008 From: delonly at gmail.com (Del) Date: Tue, 14 Oct 2008 20:04:14 +0200 Subject: Alfresco + Kolab authentication In-Reply-To: References: <48EDC55F.5020004@ofd-sth.niedersachsen.de> <1223565236.15177.20.camel@black> Message-ID: <1224007454.9441.11.camel@merom> Hello again, Why don't you try to persuade him to document his work on the wiki. That way you guys will get help maintaining the documentation and get it updated for free. It is a win-win situation. Much better than sticking it under your pillow :) Cheers, Del On Tue, 2008-10-14 at 12:12 +0200, Antonio Straziota wrote: > hi, > i'm sorry, but i can't write a document about this because i'm only > kolab admin... > A developer is responsible of the integration with alfresco and he ask > me if is possibile to autenticate kolab user through MD5 encryption. > > sorry...:( > > 2008/10/9 Del > Hello Antonio, > > Please make time to document your solution in the wiki as you > go along: > http://wiki.kolab.org/index.php/Main_Page > You are not the only one interested in a document management > system ;) > > Cheers, > Del > > > On Thu, 2008-10-09 at 12:22 +0200, Antonio Straziota wrote: > > hi, > > thanks to all for the reply. > > > > So, It could be possible using secrets stored in the LDAP? > > > > From the link posted by Marc: > > > > "This section describes the use of the SASL DIGEST-MD5 > mechanism using > > secrets stored either in the directory itself or in Cyrus > SASL's own > > database. DIGEST-MD5 relies on the client and the server > sharing a > > "secret", usually a password" > > > > Is it correct? > > > > I'll try it. Thanks for the help... > > > > PS: Any other suggetion are welcome :D > > > > bye > > > > 2008/10/9 Marc Patermann > > > Gunnar Wrobel schrieb: > > > Quoting Antonio Straziota > : > > > > > > >> Now i've to configure Alfresco with LDAP. With > SIMPLE > > autentication > > >> mode i've no problem, but i want to configure the > > authentication > > > > >> metod in DIGEST$B!](BMD5. > > >> > > >> Can i configure Kolab LDAP to accept connection > in SASL > > DIGEST-MD5? > > > > Yes. > > > > > I admit I'm not 100% certain how your setup looks > like. Of > > course > > > Alfresco can authenticate using SASL to > authenticate against > > the Kolab > > > LDAP server. But your request sounds like you wish > LDAP to > > use SASL > > > (something like > http://tldp.org/HOWTO/LDAP-HOWTO/sasl.html) > > which is > > > not possible as OpenLDAP is the SASL backend and > that would > > result in > > > a circular dependency. > > > > Not true! > > "The DIGEST-MD5 mechanism is the > mandatory-to-implement > > authentication > > mechanism for LDAPv3." > > > > Have a look at the OpenLDAP Admin Guide SASL > section: -> > > http://www.openldap.org/doc/admin23/sasl.html > > > > > > Marc > > > > > > _______________________________________________ > > 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 aspineux at gmail.com Tue Oct 14 21:04:29 2008 From: aspineux at gmail.com (Alain Spineux) Date: Tue, 14 Oct 2008 21:04:29 +0200 Subject: Expanding user.php so it enters three more fields into LDAP In-Reply-To: <48F2FFF7.6060101@FuH-E.de> References: <48F2FFF7.6060101@FuH-E.de> Message-ID: <71fe4e760810141204r5b3fba31g6f77dae7dae83c70@mail.gmail.com> On Mon, Oct 13, 2008 at 9:59 AM, Christian R??ler wrote: > Good morning to everyone, > > I am working for some time with Kolab, and I have to say I think it is a > very nice software. Now I try to enhance the admin interface a bit while > evaluating the possibility of a migration to Kolab > > Well, my problem is such: I want to get sone posixGroup functionality > for the user type 'groups'. As I obviously cannot just connect > posixGroup to the object (as inetOrgPerson/kolabInetOrgPerson would be > present) I have thought of making a scheme of my own with an auxiliary > objectClass, which brings the three attributes I need. > > These attributes would be 'generate/delete companion posixGroup, list of > UIDs for group, eventually password'. Then I would use a script to > generate a posixGroup at the appropriate place in the hierarchy. > > This already functions reasonably well. But I fail in modifying user.php > as such, that it writes my objectClass (with the three attributes) to > LDAP - regrettably my PHP knowledge is rather bad. Maybe you could find some very precise piece of code in the patch of this thread : https://www.intevation.de/roundup/kolab/issue2997 Hope this help > > So I would be most grateful if anyone could help me. > > Best regards and many thanks, > Christian R??ler (Roessler) > > > PS. My scheme uses this attributes: > generateCompanionGroup - boolean - SINGLE-VALUE > membersCompanionGroup - IA5 - SINGLE-VALUE > passwordCompanionGroup - IA5 - SINGLE-VALUE > > ...and the object is: > companionGroup - AUXILIARY - > MUST ( generateCompanionGroup ) > MAY ( membersCompanionGroup $ passwordCompanionGroup ) ) > > _______________________________________________ > 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 nprice at gibb.co.za Wed Oct 15 13:02:37 2008 From: nprice at gibb.co.za (Neil Price) Date: Wed, 15 Oct 2008 13:02:37 +0200 Subject: Toltec/Kolab Message-ID: I'm testing the Toltec connector on Kolab(I'm using it to write this message). The setup is a bit strange though I understand that is because of flaws in Outlook (big surprise). Calendar sync works fine, I find incoming email handling strange. As I understand it, Toltec downloads the mail through pop3 and then syncs it back to the server. This did not appear to work until I noticed a 2nd Inbox in Horde/Imp with the same emails that Outook sees. So I have 2 inboxes, is that the way it is meant to be? The documentation is silent on this issue. Anybody ever tried Open Connector beta (http://openconnector.org/) with Kolab? From ml at radoeka.nl Wed Oct 15 19:19:47 2008 From: ml at radoeka.nl (Richard Bos) Date: Wed, 15 Oct 2008 19:19:47 +0200 Subject: Interview with Horde lead developer Jan Schneider Message-ID: <200810151919.48032.ml@radoeka.nl> There is a long interview with Jan Schneider from Horde faim on: http://www.techworld.com.au/article/263744/open_source_identity_horde_lead_developer_jan_schneider -- Richard Bos We are borrowing the world of our children, It is not inherited from our parents. From jaheme at gmx.de Wed Oct 15 22:44:38 2008 From: jaheme at gmx.de (Jan - Hendrik Meyer) Date: Wed, 15 Oct 2008 22:44:38 +0200 Subject: A problem with mail delivering In-Reply-To: <20081013081113.88291himve88sp7o@webmail.pardus.de> References: <48DFAD42.20002@gmx.de> <48E60DDF.3010605@gmx.de> <20081007094101.19345yn9ajhh7ssg@webmail.pardus.de> <48F27E84.2040006@gmx.de> <20081013081113.88291himve88sp7o@webmail.pardus.de> Message-ID: <48F65636.5090702@gmx.de> Gunnar Wrobel schrieb: > Quoting Jan - Hendrik Meyer : > >> >> Quoting Gunnar Wrobel >>> Quoting Jan - Hendrik Meyer : >>> >>>> Hello, >>>> >>>> after changing some rights, >>> >>> Meaning you don't use the OpenPKG based installation? You should >>> always state the Kolab version you are using in error reports as it >>> makes it easier for us to identify possible error sources. >> Yes, it's a kolab 2.2 version from 14. august. > > Installed based on OpenPKG? I'm slightly confused as the 2.2.0 Release > was on 12th July. But maybe you refer to your installation date. > > Anyhow I'm not certain why you had to modify some of the rights. On a > standard Kolab server installation this should not be necessary at > all. So I'm wondering why modifications were necessary and which > modifications you made? > It's compiled OpenPKG version which is distributed over the openSUSE Buildservice. It integrated into the system directory instead of /kolab/ These modifications seems to be caused by these packages even there is no hint on the installation doc website >>> >>>> the cyrus server is working correctly. >>>> The messages I've written don't appear anymore. >>>> >>>> But without any error message, no message I've written can be found in >>>> the cyrus imap postbox. It's empty. >>>> I tested with the command: >>>> >>>> echo $(date) | mailx -s test noname at home >>>> >>>> Postfix shows some messages like this: >>>> >>>> Sep 29 20:29:33 lxmain postfix/smtp[32013]: D699C22C24C: >>>> to=, orig_to=, >>>> relay=127.0.0.1[127.0.0.1]:10024, delay=0.57, >>>> delays=0.18/0.02/0.01/0.37, dsn=2.0.0, status=sent (250 2.0.0 Ok: >>>> queued as 582D322C2AA) >>>> Sep 29 20:29:33 lxmain postfix/qmgr[31785]: D699C22C24C: removed >>>> Sep 29 20:29:33 lxmain postfix/pipe[32018]: 582D322C2AA: >>>> to=, relay=kolabmailboxfilter, delay=0.28, >>>> delays=0.06/0.02/0/0.2, dsn=2.0.0, status=sent (delivered via >>>> kolabmailboxfilter service) >>>> Sep 29 20:29:33 lxmain postfix/qmgr[31785]: 582D322C2AA: removed >>>> >>>> and >>>> >>>> amavis seems to scan the message: >>>> >>>> Sep 29 20:29:33 lxmain.Home /usr/sbin/amavisd[31563]: (31563-01) >>>> Passed, -> , quarantine D-8O1JfSg7tV, >>>> Message-ID: <20080929182932.9D8F322C2AA at lxmain.Home>, Hits: 2.34 >>>> Sep 29 20:29:33 lxmain.Home /usr/sbin/amavisd[31563]: (31563-01) >>>> Passed CLEAN, -> , Hits: 2.34, tag=3, >>>> tag2=6.3, kill=6.3, queued_as: 582D322C2AA, L/0/0/0 >>>> >>>> Maybe this is a message, that indicates a error: >>>> >>>> Oct 3 08:45:43 lxmain imap[26981]: dracconn: localhost: RPC: Program >>>> not registered >>>> Oct 3 08:45:43 lxmain imap[26981]: DRAC notifications disabled >>>> >>>> Does anyone know what the problem could be? >>> >>> What does the lmtp log say? >> I can't find any logfile. There is also no process called anything like >> lmtp. > > That there is no process called lmtp is okay. This is just a temporary > process when processing a message. The log file should be located at > /kolab/var/imapd/log/lmtpd.log. If there is no such log file it would > mean cyrus never actually gets messages delivered from postfix. Do you > have anything in the log file /kolab/var/kolab-filter/log/filter.log? > This is the filter that should contact the cyrus imap server. In filter.log I found an error: [pid 4833 on line 198 of "/usr/share/php5/PEAR/Kolab/Filter/Filter.php"] Oct 13 00:44:38 Kolab Filter [debug] [horde] Filter_Incoming starting up (sender=root at home, recipients=noname at home, client_address=127.0.0.1) [pid 4833 on line 184 of "/usr/share/php5/PEAR/Kolab/Filter/Filter.php"] Oct 13 00:44:39 Kolab Filter [error] [horde] Invalid response code received from server > [pid 4833 on line 184 of "/usr/share/php5/PEAR/Kolab/Filter/Transport.php"] Oct 13 00:44:39 Kolab Filter [info] [horde] Filter_Incoming successfully completed (sender=root at home, recipients=noname at home, client_address=127.0.0.1, id=<20081012224436.5B72122C2AA at lxmain.Home>) [pid 4833 on line 163 of "/usr/share/php5/PEAR/Kolab/Filter/Filter.php"] but i con't know why the server answers with such a message? Jan-Hendrik Meyer > > Cheers, > > Gunnar > > >> >>> >>> Cheers, >>> >>> Gunnar >>> >>>> >>>> Thanks >>>> >>>> Jan-Hendrik Meyer >>>> >> >> _______________________________________________ >> 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 > -------------- n?chster Teil -------------- Ein Dateianhang mit HTML-Daten wurde abgetrennt... URL: http://kolab.org/pipermail/kolab-users/attachments/20081015/dd386f7e/attachment.html From ml at radoeka.nl Wed Oct 15 23:33:27 2008 From: ml at radoeka.nl (Richard Bos) Date: Wed, 15 Oct 2008 23:33:27 +0200 Subject: A problem with mail delivering In-Reply-To: <48F65636.5090702@gmx.de> References: <48DFAD42.20002@gmx.de> <20081013081113.88291himve88sp7o@webmail.pardus.de> <48F65636.5090702@gmx.de> Message-ID: <200810152333.28048.ml@radoeka.nl> Op Wednesday 15 October 2008 22:44:38 schreef Jan - Hendrik Meyer: > > Anyhow I'm not certain why you had to modify some of the rights. On a > > standard Kolab server installation this should not be necessary at > > all. So I'm wondering why modifications were necessary and which > > modifications you made? > > It's compiled OpenPKG version which is distributed over the openSUSE > Buildservice. This is not possible. It's either the openpkg version or the opensuse version ;) You can compare openpkg with a distribution. In your case you have the native opensuse version. The openpkg version and the opensuse are build from the same sources, with respect for the specific kolab packages. But many other packages (perl, php) or just taken as is from the opensuse repository (ies). > These modifications seems to be caused by these packages even there is > no hint on the installation doc website I missed the part about the modifications sorry. -- Richard Bos We are borrowing the world of our children, It is not inherited from our parents. From pav5088 at internode.on.net Thu Oct 16 04:32:54 2008 From: pav5088 at internode.on.net (Mark Pavlichuk) Date: Thu, 16 Oct 2008 12:32:54 +1000 Subject: duplicate calendar entries Message-ID: <48F6A7D6.9050906@internode.on.net> We have been trialing Kolab v2.2 (/w Horde and Toltec clients... users mainly on Toltec) for a couple of weeks, but now we have a difficulty - one user is having calendar entries replicating themselves - eventually there can be tens or hundreds of duplications. Is this a known problem? If not, are there any generic fixes we could try? If I need more information what should I collect and bring back to the list? I should mention a couple of things : - the problem started just after some network issues. A switch power supply wasn't supplying enough juice, so there may have been network connectivity issues leading up to the calendar duplication problem. - we're using Kolab and Horde debs (yes, I know... but that's the only real way to get Kolab and Horde to peacefully coexist with other services running on the same box). -- Mark Pavlichuk Strategic IT ph. (07)47242890 m. 0409 124577 From rs at blinkenlichten.de Thu Oct 16 10:25:32 2008 From: rs at blinkenlichten.de (Rouven Sacha) Date: Thu, 16 Oct 2008 10:25:32 +0200 Subject: duplicate calendar entries In-Reply-To: <48F6A7D6.9050906@internode.on.net> References: <48F6A7D6.9050906@internode.on.net> Message-ID: <200810161025.33434.rs@blinkenlichten.de> On Thursday 16 October 2008 04:32:54 Mark Pavlichuk wrote: > We have been trialing Kolab v2.2 (/w Horde and Toltec clients... > users mainly on Toltec) for a couple of weeks, but now we have a > difficulty - one user is having calendar entries replicating themselves > - eventually there can be tens or hundreds of duplications. Ah. Nice to have that confirmed. We once had a calendar with 90.000 identical entries with kontact and synckolab. > - we're using Kolab and Horde debs (yes, I know... but that's the > only real way to get Kolab and Horde to peacefully coexist with other > services running on the same box). We are using the same packages so that error might be a packaging error. Alioth has new kolab packages today - we should submit a bugreport to the debian maintainers if that problem still exists. Cheers, Rouven -- Blinkenlichten Open Source Solutions Eigm?ller, Maass, Sacha GbR Weigandufer 45 12059 Berlin tel: +49 30 13896247 fax: +49 30 13896249 mobil: +49 174 4220127 http://www.blinkenlichten.de/ From computech at telkomsa.net Thu Oct 16 16:02:58 2008 From: computech at telkomsa.net (Nazeer) Date: Thu, 16 Oct 2008 16:02:58 +0200 Subject: Kolab 2.1 Side bar missing Message-ID: <006601c92f97$e505a790$af10f6b0$@net> Hi Some of the users in Kolab 2.1 does not have a side bar in horde. Any Ideas? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://kolab.org/pipermail/kolab-users/attachments/20081016/2f7a4753/attachment.html From viljoenjp at workforce.co.za Fri Oct 17 15:00:16 2008 From: viljoenjp at workforce.co.za (JP Viljoen) Date: Fri, 17 Oct 2008 15:00:16 +0200 Subject: Distribution lists issue Message-ID: <200810171500.16704.viljoenjp@workforce.co.za> Hi I've got an inherited kolab setup, which I'm learning as I go along, and currently I'm having an issue where distribution list addresses which get set up do not seem to work. I created a list named testlist, and when sending mail to it, I get the following output in the maillogs: Oct 17 14:50:45 10.0.0.2 postfix/pipe[26399]: B99131F0017: to=, relay=kolabfilter, delay=0.14, delays=0.03/0/0/0.1, dsn=2.0.0, status=sent (delivered via kolabfilter service) Oct 17 14:50:47 10.0.0.2 postfix/smtp[3706]: CA0E51F0029: to=, relay=127.0.0.1[127.0.0.1]:10024, delay=1.3, delays=0.06/0/0/1.3, dsn=2.6.0, status=sent (250 2.6.0 Ok, id=03348-07, from MTA([127.0.0.1]:10026): 250 2.0.0 Ok: queued as 1410F1F0017) Oct 17 14:50:47 10.0.0.2 postfix/pipe[3341]: 1410F1F0017: to=, relay=kolabmailboxfilter, delay=0.12, delays=0.06/0/0/0.06, 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 ) I have also tried restarting the kolab service (just in case, since I have no idea how the kolab architecture works for refreshing configuration information or such), and still get the same output after it. Any help or information would be appreciated. Some more information, if needed: gentoo based server, with the following packages and versions: # equery l kolab [ Searching for package 'kolab' in all categories among: ] * installed packages [I--] [ ] dev-perl/perl-kolab-2.1 (0) [I--] [ ] dev-php/horde-framework-kolab-3.2_alpha (0) [I--] [ ] net-mail/kolab-resource-handlers-2.1 (0) [I--] [ ] net-mail/kolab-webadmin-2.1 (0) [I--] [ ] net-mail/kolabd-2.1 (0) [I--] [ ~] www-apps/horde-imp-kolab-4.2_alpha (4.2_alpha) [I--] [ ~] www-apps/horde-ingo-kolab-1.2_alpha (1.2_alpha) [I--] [ ~] www-apps/horde-kolab-3.2_alpha (3.2_alpha) [I--] [ ~] www-apps/horde-kolab-all-3 (0) [I--] [ ~] www-apps/horde-kronolith-kolab-2.2_alpha (2.2_alpha) [I--] [ ~] www-apps/horde-mnemo-kolab-2.2_alpha (2.2_alpha) [I--] [ ~] www-apps/horde-nag-kolab-2.2_alpha (2.2_alpha) [I--] [ ~] www-apps/horde-passwd-kolab-3.0.1 (3.0.1) [I--] [ ~] www-apps/horde-turba-kolab-2.2_alpha (2.2_alpha) Regards JP From jaheme at gmx.de Sat Oct 18 11:53:02 2008 From: jaheme at gmx.de (Jan - Hendrik Meyer) Date: Sat, 18 Oct 2008 11:53:02 +0200 Subject: A problem with mail delivering In-Reply-To: <200810152333.28048.ml@radoeka.nl> References: <48DFAD42.20002@gmx.de> <20081013081113.88291himve88sp7o@webmail.pardus.de> <48F65636.5090702@gmx.de> <200810152333.28048.ml@radoeka.nl> Message-ID: <48F9B1FE.3020203@gmx.de> Richard Bos schrieb: > Op Wednesday 15 October 2008 22:44:38 schreef Jan - Hendrik Meyer: > >>> Anyhow I'm not certain why you had to modify some of the rights. On a >>> standard Kolab server installation this should not be necessary at >>> all. So I'm wondering why modifications were necessary and which >>> modifications you made? >>> >> It's compiled OpenPKG version which is distributed over the openSUSE >> Buildservice. >> > > This is not possible. It's either the openpkg version or the opensuse > version ;) You can compare openpkg with a distribution. In your case you > have the native opensuse version. The openpkg version and the opensuse are > build from the same sources, with respect for the specific kolab packages. > But many other packages (perl, php) or just taken as is from the opensuse > repository (ies). > > I understand what you mean. The OpenPKG version utilzes its own packages, unlike the openSUSE version, which utilizes the openSUSE packages... >> These modifications seems to be caused by these packages even there is >> no hint on the installation doc website >> > > I missed the part about the modifications sorry. > > I've installed the version by the installation guide http://en.opensuse.org/Kolab Furthermore I've changed the database format from skiplist to berkeley database format and I've changed the ownergroup of the following directories to kolab: /etc/sysconfig/kolab /var/log/kolab /var/lib/kolab /var/adm/backup/kolab /usr/share/php5/kolab /usr/share/kolab /usr/share/doc/packages/kolab /usr/lib/kolab That was all. Cheers, Jan-Hendrik From ml at radoeka.nl Sat Oct 18 12:15:29 2008 From: ml at radoeka.nl (Richard Bos) Date: Sat, 18 Oct 2008 12:15:29 +0200 Subject: A problem with mail delivering In-Reply-To: <48F9B1FE.3020203@gmx.de> References: <48DFAD42.20002@gmx.de> <200810152333.28048.ml@radoeka.nl> <48F9B1FE.3020203@gmx.de> Message-ID: <200810181215.30793.ml@radoeka.nl> Op Saturday 18 October 2008 11:53:02 schreef Jan - Hendrik Meyer: > > I missed the part about the modifications sorry. > > > I've installed the version by the installation guide > http://en.opensuse.org/Kolab :) Look at the history. What openSUSE version are you using. > Furthermore I've changed the database format from skiplist to berkeley > database format Berkeley is the default db format. Do you mean that you converted your old databases from skiplist to berkeley? > and I've changed the ownergroup of the following directories > to kolab: > > /etc/sysconfig/kolab > /var/log/kolab > /var/lib/kolab > /var/adm/backup/kolab > /usr/share/php5/kolab > /usr/share/kolab > /usr/share/doc/packages/kolab > /usr/lib/kolab Why was that needed? Those should be correct from the beginning (as delivered by the rpm). Please check with 'rpm -V ' what has changed on file and compared to what the rpm delivers. Use rpm -qf to find the package that delivers the file, or use: rpm -V $(rpm -qf /usr/share/doc/packages/kolab) to do it all in one line. In the end this results in the packages: kolab and kolab-webadmin -- Richard Bos We are borrowing the world of our children, It is not inherited from our parents. From jaheme at gmx.de Sat Oct 18 17:51:38 2008 From: jaheme at gmx.de (Jan - Hendrik Meyer) Date: Sat, 18 Oct 2008 17:51:38 +0200 Subject: A problem with mail delivering In-Reply-To: <200810181215.30793.ml@radoeka.nl> References: <48DFAD42.20002@gmx.de> <200810152333.28048.ml@radoeka.nl> <48F9B1FE.3020203@gmx.de> <200810181215.30793.ml@radoeka.nl> Message-ID: <48FA060A.8030002@gmx.de> Richard Bos schrieb: > Op Saturday 18 October 2008 11:53:02 schreef Jan - Hendrik Meyer: > >>> I missed the part about the modifications sorry. >>> >>> >> I've installed the version by the installation guide >> http://en.opensuse.org/Kolab >> > > :) Look at the history. What openSUSE version are you using. > > I've used the openSUSE 10.3 x86_64 >> Furthermore I've changed the database format from skiplist to berkeley >> database format >> > > Berkeley is the default db format. Do you mean that you converted your old > databases from skiplist to berkeley? > > Exactly - It could be caused by testing the imap daemon without kolab some time before... >> and I've changed the ownergroup of the following directories >> to kolab: >> >> /etc/sysconfig/kolab >> /var/log/kolab >> /var/lib/kolab >> /var/adm/backup/kolab >> /usr/share/php5/kolab >> /usr/share/kolab >> /usr/share/doc/packages/kolab >> /usr/lib/kolab >> > > Why was that needed? Those should be correct from the beginning (as delivered > by the rpm). Please check with 'rpm -V ' what has changed on file > and compared to what the rpm delivers. > > Use rpm -qf to find the package that delivers the file, or use: > rpm -V $(rpm -qf /usr/share/doc/packages/kolab) to do it all in one line. > > In the end this results in the packages: kolab and kolab-webadmin > > Your Command for e.g. /usr/lib/kolab -> package kolab gives me the following content: ......G. /usr/lib/kolab ......G. /usr/lib/kolab/adduser ......G. /usr/lib/kolab/deluser ......G. /usr/lib/kolab/listusers ......G. /usr/lib/kolab/newconfig ......G. /usr/lib/kolab/services ......G. /usr/lib/kolab/showlog ......G. /usr/lib/kolab/showuser ......G. /usr/lib/kolab/start ......G. /usr/lib/kolab/stop ......G. /usr/share/doc/packages/kolab/kolabd ......G. d /usr/share/doc/packages/kolab/kolabd/AUTHORS ......G. d /usr/share/doc/packages/kolab/kolabd/COPYING ......G. d /usr/share/doc/packages/kolab/kolabd/ChangeLog ......G. d /usr/share/doc/packages/kolab/kolabd/NEWS ......G. d /usr/share/doc/packages/kolab/kolabd/README.amavisd ......G. d /usr/share/doc/packages/kolab/kolabd/README.ldapdelete ......G. d /usr/share/doc/packages/kolab/kolabd/README.outlook ......G. d /usr/share/doc/packages/kolab/kolabd/README.sieve ......G. d /usr/share/doc/packages/kolab/kolabd/README.webgui ......G. /usr/share/kolab/scripts/kolab_bootstrap ......G. /usr/share/kolab/scripts/kolab_ca.sh ......G. /usr/share/kolab/scripts/kolab_smtpdpolicy ......G. /usr/share/kolab/scripts/kolab_sslcert.sh ......G. /usr/share/kolab/scripts/kolab_upgrade ......G. /usr/share/kolab/scripts/kolabcron ......G. /usr/share/kolab/scripts/kolabdcachetool ......G. /usr/share/kolab/scripts/kolabquotareport ......G. /usr/share/kolab/scripts/kolabquotawarn ......G. /usr/share/kolab/scripts/workaround.sh ......G. /var/adm/backup/kolab ......G. /var/lib/kolab ......G. /var/log/kolab ......G. /var/log/kolab/filter ......G. /var/log/kolab/freebusy for the kolab-webadmin it looks nearly the same. But I can't see anything which is important for me? What does the G and the d mean? Cheers, Jan-Hendrik From ml at radoeka.nl Sat Oct 18 20:47:05 2008 From: ml at radoeka.nl (Richard Bos) Date: Sat, 18 Oct 2008 20:47:05 +0200 Subject: A problem with mail delivering In-Reply-To: <48FA060A.8030002@gmx.de> References: <48DFAD42.20002@gmx.de> <200810181215.30793.ml@radoeka.nl> <48FA060A.8030002@gmx.de> Message-ID: <200810182047.06566.ml@radoeka.nl> Op Saturday 18 October 2008 17:51:38 schreef Jan - Hendrik Meyer: > > ? > > Your Command for e.g. /usr/lib/kolab -> package kolab gives me the > following content: > > ......G. ? ?/usr/lib/kolab > ......G. ? ?/usr/lib/kolab/adduser > ......G. ? ?/usr/lib/kolab/deluser > ......G. ? ?/usr/lib/kolab/listusers > ......G. ? ?/usr/lib/kolab/newconfig > ......G. ? ?/usr/lib/kolab/services > ......G. ? ?/usr/lib/kolab/showlog > ......G. ? ?/usr/lib/kolab/showuser > ......G. ? ?/usr/lib/kolab/start > ......G. ? ?/usr/lib/kolab/stop > ......G. ? ?/usr/share/doc/packages/kolab/kolabd > ......G. ?d /usr/share/doc/packages/kolab/kolabd/AUTHORS > ......G. ?d /usr/share/doc/packages/kolab/kolabd/COPYING > ......G. ?d /usr/share/doc/packages/kolab/kolabd/ChangeLog > ......G. ?d /usr/share/doc/packages/kolab/kolabd/NEWS > ......G. ?d /usr/share/doc/packages/kolab/kolabd/README.amavisd > ......G. ?d /usr/share/doc/packages/kolab/kolabd/README.ldapdelete > ......G. ?d /usr/share/doc/packages/kolab/kolabd/README.outlook > ......G. ?d /usr/share/doc/packages/kolab/kolabd/README.sieve > ......G. ?d /usr/share/doc/packages/kolab/kolabd/README.webgui > ......G. ? ?/usr/share/kolab/scripts/kolab_bootstrap > ......G. ? ?/usr/share/kolab/scripts/kolab_ca.sh > ......G. ? ?/usr/share/kolab/scripts/kolab_smtpdpolicy > ......G. ? ?/usr/share/kolab/scripts/kolab_sslcert.sh > ......G. ? ?/usr/share/kolab/scripts/kolab_upgrade > ......G. ? ?/usr/share/kolab/scripts/kolabcron > ......G. ? ?/usr/share/kolab/scripts/kolabdcachetool > ......G. ? ?/usr/share/kolab/scripts/kolabquotareport > ......G. ? ?/usr/share/kolab/scripts/kolabquotawarn > ......G. ? ?/usr/share/kolab/scripts/workaround.sh > ......G. ? ?/var/adm/backup/kolab > ......G. ? ?/var/lib/kolab > ......G. ? ?/var/log/kolab > ......G. ? ?/var/log/kolab/filter > ......G. ? ?/var/log/kolab/freebusy > > for the kolab-webadmin it looks nearly the same. > > But I can't see anything which is important for me? What does the G and > the d mean? See http://linux.die.net/man/8/rpm and look for "The format of the output is a string of 8 characters" d %doc documentation file G Group ownership differs For all above mentioned files, the group ownership should be root. Do you have apparmor active. Perhaps that application changes the ownership because of security? -- Richard Bos We are borrowing the world of our children, It is not inherited from our parents. From jaheme at gmx.de Sat Oct 18 22:05:59 2008 From: jaheme at gmx.de (Jan - Hendrik Meyer) Date: Sat, 18 Oct 2008 22:05:59 +0200 Subject: A problem with mail delivering In-Reply-To: <200810182047.06566.ml@radoeka.nl> References: <48DFAD42.20002@gmx.de> <200810181215.30793.ml@radoeka.nl> <48FA060A.8030002@gmx.de> <200810182047.06566.ml@radoeka.nl> Message-ID: <48FA41A7.7060907@gmx.de> Richard Bos schrieb: > Op Saturday 18 October 2008 17:51:38 schreef Jan - Hendrik Meyer: > >>> >>> >> Your Command for e.g. /usr/lib/kolab -> package kolab gives me the >> following content: >> >> ......G. /usr/lib/kolab >> ......G. /usr/lib/kolab/adduser >> ......G. /usr/lib/kolab/deluser >> ......G. /usr/lib/kolab/listusers >> ......G. /usr/lib/kolab/newconfig >> ......G. /usr/lib/kolab/services >> ......G. /usr/lib/kolab/showlog >> ......G. /usr/lib/kolab/showuser >> ......G. /usr/lib/kolab/start >> ......G. /usr/lib/kolab/stop >> ......G. /usr/share/doc/packages/kolab/kolabd >> ......G. d /usr/share/doc/packages/kolab/kolabd/AUTHORS >> ......G. d /usr/share/doc/packages/kolab/kolabd/COPYING >> ......G. d /usr/share/doc/packages/kolab/kolabd/ChangeLog >> ......G. d /usr/share/doc/packages/kolab/kolabd/NEWS >> ......G. d /usr/share/doc/packages/kolab/kolabd/README.amavisd >> ......G. d /usr/share/doc/packages/kolab/kolabd/README.ldapdelete >> ......G. d /usr/share/doc/packages/kolab/kolabd/README.outlook >> ......G. d /usr/share/doc/packages/kolab/kolabd/README.sieve >> ......G. d /usr/share/doc/packages/kolab/kolabd/README.webgui >> ......G. /usr/share/kolab/scripts/kolab_bootstrap >> ......G. /usr/share/kolab/scripts/kolab_ca.sh >> ......G. /usr/share/kolab/scripts/kolab_smtpdpolicy >> ......G. /usr/share/kolab/scripts/kolab_sslcert.sh >> ......G. /usr/share/kolab/scripts/kolab_upgrade >> ......G. /usr/share/kolab/scripts/kolabcron >> ......G. /usr/share/kolab/scripts/kolabdcachetool >> ......G. /usr/share/kolab/scripts/kolabquotareport >> ......G. /usr/share/kolab/scripts/kolabquotawarn >> ......G. /usr/share/kolab/scripts/workaround.sh >> ......G. /var/adm/backup/kolab >> ......G. /var/lib/kolab >> ......G. /var/log/kolab >> ......G. /var/log/kolab/filter >> ......G. /var/log/kolab/freebusy >> >> for the kolab-webadmin it looks nearly the same. >> >> But I can't see anything which is important for me? What does the G and >> the d mean? >> > > See http://linux.die.net/man/8/rpm and look for > "The format of the output is a string of 8 characters" > d %doc documentation file > G Group ownership differs > > For all above mentioned files, the group ownership should be root. Do you > have apparmor active. Perhaps that application changes the ownership because > of security? > > Hello, after I've changed the rights of these directories back to root and deleted the directory /var/spool/imap/.stage/ everything works fine. Thanks for your help. From s.kim at hia.rwth-aachen.de Mon Oct 20 11:32:00 2008 From: s.kim at hia.rwth-aachen.de (Saim Kim) Date: Mon, 20 Oct 2008 11:32:00 +0200 Subject: Urgent: /kolab/share/clamav full Message-ID: <48FC5010.5060206@hia.rwth-aachen.de> Hello, I'm wondering what files are saved in the /kolab/share/clamav directory besides some config or database files. I have 38 GB full of files named clamav-numbersnumbersnumbers. Is it safe to delete those files because the harddisk space is getting critically low at the moment? Best regards, Saim -- -------------------------------------------------------------------------- Dipl.-Ing. Saim Kim Lehrstuhl fuer Medizinische Informationstechnik Helmholtz-Institut fuer Biomedizinische Technik RWTH Aachen Pauwelsstr. 20, D-52074 Aachen --- Web: http://www.medit.hia.rwth-aachen.de/ Tel: +49-(0)241-80 23218 Fax: +49-(0)241-80 82442 email: s.kim at hia.rwth-aachen.de -------------------------------------------------------------------------- From albrecht.dress at lios-tech.com Mon Oct 20 14:40:14 2008 From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=) Date: Mon, 20 Oct 2008 14:40:14 +0200 Subject: automatically re-start LDAP in case of crash Message-ID: <1224506414l.26135l.0l@pc104141.koeln.nktcables.com> Hi all, it seems that I'm also affected by the LDAP crash of issue #2982 [1]. As I use slapd for both Kolab and Samba/Posix log-ons, a crash of it will leave the whole system unusable. I also assume that no mails will be delivered anymore, as no users can be checked, and they will therefore bounce, right? While this is probably not a Kolab issue, I wonder how I can automatically re-start slapd /immediately/ when it segfaults. In particular, there is a remark in the issue that the data base had "crashed", too, and that db_recover had to be used (how?). As OpenLDAP is a very critical core component of Kolab, IMO it would be a valuable add-on to have such a watch-and-restart-if-necessary feature. Thanks, Albrecht. [1] From alessio at skye.it Mon Oct 20 19:00:50 2008 From: alessio at skye.it (Alessio Cecchi) Date: Mon, 20 Oct 2008 19:00:50 +0200 Subject: Urgent: /kolab/share/clamav full In-Reply-To: <48FC5010.5060206@hia.rwth-aachen.de> References: <48FC5010.5060206@hia.rwth-aachen.de> Message-ID: <200810201900.50216.alessio@skye.it> Il Monday 20 October 2008 11:32:00 Saim Kim ha scritto: > Hello, > > I'm wondering what files are saved in the /kolab/share/clamav directory > besides some config or database files. I have 38 GB full of files named > clamav-numbersnumbersnumbers. Is it safe to delete those files because > the harddisk space is getting critically low at the moment? Yes, you can delete its and after re-run freshclam. Ciao -- Alessio Cecchi is: @ ILS -> http://www.linux.it/~alessice/ Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/ @ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it @ LOLUG -> neo-Socio http://www.lolug.net From sbambach at gmx.net Mon Oct 20 20:08:21 2008 From: sbambach at gmx.net (Stefan Bambach) Date: Mon, 20 Oct 2008 20:08:21 +0200 Subject: Kolab 2.2 addressbook export as spamassassin whitelist Message-ID: <200810202008.21555.stefanb@bambach.intra> Hi, I'm new to this list. So please don't blame if my question is already answered. Please send me the corresponding link. I want to export my personal addressbook from imap to convert it to a format that spamassassin can read (with read_hash). The global whitelist would be ok, since I'm the only person using kolab at home. All should happen automatically on server per e.g. cronjob. Without any action I have to take manually. So how can I export the addressbook from imap? Or how can I configure spamassassin that it will read it direktly from my addressbook? Perhaps there's a way to install some kind of callback, that will be called when addresses are edited (Although a complete export would be better, than an incrementally callback mechanism)? What are my options to solve this problem? ciao. Stefan From wrobel at pardus.de Tue Oct 21 11:14:32 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Tue, 21 Oct 2008 11:14:32 +0200 Subject: Toltec/Kolab In-Reply-To: References: Message-ID: <20081021111432.59965ghgzuiec8s8@webmail.pardus.de> Quoting Neil Price : > I'm testing the Toltec connector on Kolab(I'm using it to write this > message). The setup is a bit strange though I understand that is because of > flaws in Outlook (big surprise). > > Calendar sync works fine, I find incoming email handling strange. > > As I understand it, Toltec downloads the mail through pop3 and then syncs it > back to the server. This did not appear to work until I noticed a 2nd Inbox > in Horde/Imp with the same emails that Outook sees. So I have 2 inboxes, is > that the way it is meant to be? The documentation is silent on this issue. As far as I know this is the way it is supposed to be. I guess it is somewhat confusing if you use it together with other clients. You should contact Toltec support if you need more detailed information. > > Anybody ever tried Open Connector beta (http://openconnector.org/) with > Kolab? Not as far as I know. I don't have the impression it works with Kolab. Cheers, Gunnar > > > _______________________________________________ > 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/20081021/e314c78e/attachment.bin From wrobel at pardus.de Tue Oct 21 11:20:50 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Tue, 21 Oct 2008 11:20:50 +0200 Subject: Kolab 2.1 Side bar missing In-Reply-To: <006601c92f97$e505a790$af10f6b0$@net> References: <006601c92f97$e505a790$af10f6b0$@net> Message-ID: <20081021112050.28976n67puz9owg8@webmail.pardus.de> Quoting Nazeer : > Hi Some of the users in Kolab 2.1 does not have a side bar in > horde. Any Ideas? As Kolab-Server-2.1 does not include Horde you are obviously using a non-standard installation variant and it would help if you include some details about your installation. In any case I would check the horde and php error logs. You should have some information in there that might help to diagnose the error. Cheers, Gunnar > > Thanks __________ Information from ESET Smart Security, version of virus > signature database 3519 (20081013) __________ > > The message was checked by ESET Smart Security. > > http://www.eset.com[1] -- ______ 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://www.eset.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/20081021/48505a36/attachment.bin From wrobel at pardus.de Tue Oct 21 11:26:00 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Tue, 21 Oct 2008 11:26:00 +0200 Subject: Distribution lists issue In-Reply-To: <200810171500.16704.viljoenjp@workforce.co.za> References: <200810171500.16704.viljoenjp@workforce.co.za> Message-ID: <20081021112600.752326yg5ycy6hj4@webmail.pardus.de> Quoting JP Viljoen : > Hi > > I've got an inherited kolab setup, which I'm learning as I go along, > and currently I'm having an issue where distribution list addresses > which get set up > do not seem to work. I created a list named testlist, and when > sending mail to it, I get the following output in the maillogs: > > Oct 17 14:50:45 10.0.0.2 postfix/pipe[26399]: B99131F0017: > to=, relay=kolabfilter, delay=0.14, > delays=0.03/0/0/0.1, > dsn=2.0.0, status=sent (delivered via kolabfilter service) > Oct 17 14:50:47 10.0.0.2 postfix/smtp[3706]: CA0E51F0029: > to=, relay=127.0.0.1[127.0.0.1]:10024, delay=1.3, > delays=0.06/0/0/1.3, dsn=2.6.0, status=sent (250 2.6.0 Ok, > id=03348-07, from MTA([127.0.0.1]:10026): 250 2.0.0 Ok: queued as > 1410F1F0017) > Oct 17 14:50:47 10.0.0.2 postfix/pipe[3341]: 1410F1F0017: > to=, relay=kolabmailboxfilter, delay=0.12, > delays=0.06/0/0/0.06, 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 ) > > I have also tried restarting the kolab service (just in case, since > I have no idea how the kolab architecture works for refreshing > configuration > information or such), and still get the same output after it. Any > help or information would be appreciated. Some more information, if > needed: gentoo > based server, with the following packages and versions: > > # equery l kolab > [ Searching for package 'kolab' in all categories among: ] > * installed packages > [I--] [ ] dev-perl/perl-kolab-2.1 (0) > [I--] [ ] dev-php/horde-framework-kolab-3.2_alpha (0) > [I--] [ ] net-mail/kolab-resource-handlers-2.1 (0) > [I--] [ ] net-mail/kolab-webadmin-2.1 (0) > [I--] [ ] net-mail/kolabd-2.1 (0) > [I--] [ ~] www-apps/horde-imp-kolab-4.2_alpha (4.2_alpha) > [I--] [ ~] www-apps/horde-ingo-kolab-1.2_alpha (1.2_alpha) > [I--] [ ~] www-apps/horde-kolab-3.2_alpha (3.2_alpha) > [I--] [ ~] www-apps/horde-kolab-all-3 (0) > [I--] [ ~] www-apps/horde-kronolith-kolab-2.2_alpha (2.2_alpha) > [I--] [ ~] www-apps/horde-mnemo-kolab-2.2_alpha (2.2_alpha) > [I--] [ ~] www-apps/horde-nag-kolab-2.2_alpha (2.2_alpha) > [I--] [ ~] www-apps/horde-passwd-kolab-3.0.1 (3.0.1) > [I--] [ ~] www-apps/horde-turba-kolab-2.2_alpha (2.2_alpha) Uh, oh. This is a Kolab2/Gentoo-2.1 installation. I am the maintainer of that port and I did not continue that line of the server. The 2.1 version was something that helped me getting a good grip on the shortcomings of running Kolab on Gentoo. And I mainly used this for ideas on Kolab2/Gentoo-2.2. This version is not finished yet though. If your server is anything near to being used in production I'd really recommend to switch to the Kolab2/OpenPKG-2.2 version. You should be able to cleanly migrate the data from the older Gentoo system. Cheers, Gunnar > > Regards > JP > > _______________________________________________ > 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/20081021/5b397da1/attachment.bin From wrobel at pardus.de Tue Oct 21 11:52:01 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Tue, 21 Oct 2008 11:52:01 +0200 Subject: automatically re-start LDAP in case of crash In-Reply-To: <1224506414l.26135l.0l@pc104141.koeln.nktcables.com> References: <1224506414l.26135l.0l@pc104141.koeln.nktcables.com> Message-ID: <20081021115201.19596ymzh0iljpss@webmail.pardus.de> Quoting Albrecht Dre? : > Hi all, > > it seems that I'm also affected by the LDAP crash of issue #2982 [1]. > As I use slapd for both Kolab and Samba/Posix log-ons, a crash of it > will leave the whole system unusable. I also assume that no mails will > be delivered anymore, as no users can be checked, and they will > therefore bounce, right? > > While this is probably not a Kolab issue, I wonder how I can > automatically re-start slapd /immediately/ when it segfaults. In > particular, there is a remark in the issue that the data base had > "crashed", too, and that db_recover had to be used (how?). As OpenLDAP > is a very critical core component of Kolab, IMO it would be a valuable > add-on to have such a watch-and-restart-if-necessary feature. I guess you could install monit for the task. I think it was part of the Kolab server in former times. At least there is an entry in CVS for it. I don't know why it was dropped though. Cheers, Gunnar > > Thanks, Albrecht. > > [1] > > _______________________________________________ > 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/20081021/35ddef1b/attachment-0001.bin From wrobel at pardus.de Tue Oct 21 11:56:45 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Tue, 21 Oct 2008 11:56:45 +0200 Subject: Kolab 2.2 addressbook export as spamassassin whitelist In-Reply-To: <200810202008.21555.stefanb@bambach.intra> References: <200810202008.21555.stefanb@bambach.intra> Message-ID: <20081021115645.11456hyhthcxrfc0@webmail.pardus.de> Quoting Stefan Bambach : > Hi, > > I'm new to this list. So please don't blame if my question is already > answered. Please send me the corresponding link. > > I want to export my personal addressbook from imap to convert it to a format > that spamassassin can read (with read_hash). The global whitelist would be > ok, since I'm the only person using kolab at home. > > All should happen automatically on server per e.g. cronjob. Without > any action > I have to take manually. > > So how can I export the addressbook from imap? Any Kolab client should allow you to expert the addressbook into a defined format (vCards, csv, etc.). You would of course need to script the conversion to the spamassassin format. > > Or how can I configure spamassassin that it will read it direktly from my > addressbook? You can't do that. At least not out of the box and it would need some serious programming. It is certainly not impossible but I doubt the effort is worth the benefit. > > Perhaps there's a way to install some kind of callback, that will be called > when addresses are edited (Although a complete export would be better, than > an incrementally callback mechanism)? > > What are my options to solve this problem? Also depends on some additional parameters. Is this something you want only for your own personal account or should this be server-wide for all users? If its just for you I'd just export the addresses once in a while and run it through a scripted converter to get the addresses whitelisted. Cheers, Gunnar > > ciao. Stefan > > _______________________________________________ > 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/20081021/6473b4f9/attachment.bin From viljoenjp at workforce.co.za Tue Oct 21 12:13:36 2008 From: viljoenjp at workforce.co.za (JP Viljoen) Date: Tue, 21 Oct 2008 12:13:36 +0200 Subject: Distribution lists issue In-Reply-To: <20081021112600.752326yg5ycy6hj4@webmail.pardus.de> References: <200810171500.16704.viljoenjp@workforce.co.za> <20081021112600.752326yg5ycy6hj4@webmail.pardus.de> Message-ID: <200810211213.36794.viljoenjp@workforce.co.za> On Tuesday 21 October 2008 11:26:00 Gunnar Wrobel wrote: > Uh, oh. This is a Kolab2/Gentoo-2.1 installation. I am the maintainer > of that port and I did not continue that line of the server. The 2.1 > version was something that helped me getting a good grip on the > shortcomings of running Kolab on Gentoo. And I mainly used this for > ideas on Kolab2/Gentoo-2.2. This version is not finished yet though. > > If your server is anything near to being used in production I'd really > recommend to switch to the Kolab2/OpenPKG-2.2 version. You should be > able to cleanly migrate the data from the older Gentoo system. Hiya Thanks for responding, especially with the exact details. And it is, in fact, in production doing close to 5GB's of mail per day on average. Could you perhaps point me to a specific migration guide if it's in the archives somewhere? I will also start looking at the Wiki now, but if anyone knows of any pitfalls which one could experience I would greatly appreciate it if they could share. Regards -J From s.kim at hia.rwth-aachen.de Tue Oct 21 12:27:59 2008 From: s.kim at hia.rwth-aachen.de (Saim Kim) Date: Tue, 21 Oct 2008 12:27:59 +0200 Subject: Urgent: /kolab/share/clamav full In-Reply-To: <200810201900.50216.alessio@skye.it> References: <48FC5010.5060206@hia.rwth-aachen.de> <200810201900.50216.alessio@skye.it> Message-ID: <48FDAEAF.4090303@hia.rwth-aachen.de> Hello Alessio, thank you for your answer! Everything is working again. Best regards, Saim Alessio Cecchi schrieb: > Il Monday 20 October 2008 11:32:00 Saim Kim ha scritto: > >> Hello, >> >> I'm wondering what files are saved in the /kolab/share/clamav directory >> besides some config or database files. I have 38 GB full of files named >> clamav-numbersnumbersnumbers. Is it safe to delete those files because >> the harddisk space is getting critically low at the moment? >> > > Yes, you can delete its and after re-run freshclam. > > Ciao > -- -------------------------------------------------------------------------- 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 albrecht.dress at lios-tech.com Tue Oct 21 12:30:28 2008 From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=) Date: Tue, 21 Oct 2008 12:30:28 +0200 Subject: automatically re-start LDAP in case of crash In-Reply-To: <20081021115201.19596ymzh0iljpss@webmail.pardus.de> (from wrobel@pardus.de on Tue Oct 21 11:52:01 2008) Message-ID: <1224585028l.31074l.1l@pc104141.koeln.nktcables.com> Hi Gunnar: Am 21.10.2008 11:52:01 schrieb(en) Gunnar Wrobel: > I guess you could install monit for the task. I think it was part of > the Kolab server in former times. At least there is an entry in CVS > for it. I don't know why it was dropped though. Thanks for that hint! Maybe I'll write my own script to do that, as Monit looks somewhat "heavy" for that task. Something like: open a socket connection to slapd, if it breaks try to re-connect, if that times out, run openpkg to stop OpenLDAP, issue a db_restore (just to be safe), and again use openpkg to launch OpenLDAP again. A simple perl script should be sufficient. What do you think, is that approach correct? A fix for OpenLDAP would of course be the preferred solution - again had a crash with the same symptoms tonight. Do you know how I could get more debugging info out of slapd to track the issue? Thanks, Albrecht. From kcaesar at hotmail.com Tue Oct 21 16:14:47 2008 From: kcaesar at hotmail.com (kiser Caesar) Date: Tue, 21 Oct 2008 16:14:47 +0200 Subject: Kolab + outlook connectors ? Message-ID: Hello ! I need to buy a large number of outlook connectors for kolab. Toltec seems to be the right choice but I have read bad experience with it. So .. What do you think? Toltec or Konsec? Thank you for your answers ! _________________________________________________________________ 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/20081021/c988a52f/attachment.html From sbambach at gmx.net Tue Oct 21 18:42:05 2008 From: sbambach at gmx.net (Stefan Bambach) Date: Tue, 21 Oct 2008 18:42:05 +0200 Subject: Kolab 2.2 addressbook export as spamassassin whitelist In-Reply-To: <20081021115645.11456hyhthcxrfc0@webmail.pardus.de> References: <200810202008.21555.stefanb@bambach.intra> <20081021115645.11456hyhthcxrfc0@webmail.pardus.de> Message-ID: <200810211842.05641.stefanb@bambach.intra> Hi, thx gunnar. I'm a developer. So coding is no problem for me. > > So how can I export the addressbook from imap? > > Any Kolab client should allow you to expert the addressbook into a > defined format (vCards, csv, etc.). yes. but i want to export it automatically on server. Is there a command line client ? (GUI clients are not really an option for automated exports on server) > You would of course need to script the conversion to the spamassassin > format. right. >> > Or how can I configure spamassassin that it will read it direktly from my > > addressbook? > > You can't do that. At least not out of the box and it would need some > serious programming. It is certainly not impossible but I doubt the > effort is worth the benefit. No problem. Than I have to generate the correct file format for spamassassin. > > Perhaps there's a way to install some kind of callback, that will be > > called when addresses are edited (Although a complete export would be > > better, than an incrementally callback mechanism)? > > > > What are my options to solve this problem? > > Also depends on some additional parameters. Is this something you want > only for your own personal account or should this be server-wide for > all users? Since I'm the only person, it doesn't matter. Could be server-wide, yes. (Thought of storing adressbook in ldap again (as I did before kolab). But I don't like ldap very much and it's not the way kolab wants to do this) >> If its just for you I'd just export the addresses once in a while and > run it through a scripted converter to get the addresses whitelisted. Would be no problem. But No. I know that I will forget to do that ;-) What about adapting a java,python,groovy,C, ... client, that can connect to kolab and export the data? perhaps one of the connectors for other groupwares ? Perhaps an simple imap client, that extract the attachments and than parse the xml? Or I saw that I can do "grep smtp-address *" in /kolab/var/imapd/spool/domain/b/blabla.intra/s/user/self/Contacts ... As long as it will not be base64 encoded/zipped, this simple solution would work too? But I'm not sure, if sometimes this data will be base64 encoded... And if I sometimes need more users in kolab, I will merge all contacts in one global whitelist. That's no problem. It's not a public server. I really need one thing, after tuning spamassassin again. Whitelist all known users, as most of the other mails will be marked via spamassassin and than deleted with sieve... and the tuning will be really hardcore. So you have to write emails to me really really carefully... No binaries, html, ... Or you are part of my addressbook... That's the only way to really fight against spam effectively. Ideas? ciao. Stefan From dvadell at linuxclusters.com.ar Tue Oct 21 19:05:19 2008 From: dvadell at linuxclusters.com.ar (Diego M. Vadell) Date: Tue, 21 Oct 2008 14:05:19 -0300 (ART) Subject: Kolab 2.2 addressbook export as spamassassin whitelist In-Reply-To: <200810211842.05641.stefanb@bambach.intra> References: <200810202008.21555.stefanb@bambach.intra> <20081021115645.11456hyhthcxrfc0@webmail.pardus.de> <200810211842.05641.stefanb@bambach.intra> Message-ID: <55902.157.92.44.72.1224608719.squirrel@sec.bit-consulting.com.ar> Hi, As the address book is stored in an imap folder, maybe you can: 1. Use inotify to be notified about changes. 2. Login with cyrus' master password. 3. For every user (or maybe only you), get the last emails with vcards 4. Parse them and add everything into spamassassin. I've done 2. and something like 3 with perl's Imap::Admin. I'm sure there should be something similar for your preferred language. Just my 2 cents -- Diego. >>> If its just for you I'd just export the addresses once in a while and >> run it through a scripted converter to get the addresses whitelisted. > > Would be no problem. But No. I know that I will forget to do that ;-) > > What about adapting a java,python,groovy,C, ... client, that can connect > to > kolab and export the data? perhaps one of the connectors for other > groupwares ? > > Perhaps an simple imap client, that extract the attachments and than parse > the > xml? > > From alex at swiftnetcomputers.biz Tue Oct 21 19:11:05 2008 From: alex at swiftnetcomputers.biz (Alex Chejlyk) Date: Tue, 21 Oct 2008 13:11:05 -0400 Subject: Kolab + outlook connectors ? In-Reply-To: References: Message-ID: <48FE0D29.8020200@swiftnetcomputers.biz> Toltec works well (imo) if the Outlook users keep their mailboxes at a reasonably small size. Toltec becomes problematic when there are thousands of email messages in the inbox/sent/deleted/contacts/calendar items. I've also found that limiting who has ability to modify the addressbooks and calendars is helpful. I've had users mistakenly delete the whole contact list more than once.... I've also ran into problems where recurring appointments are set with no end dates. This will cause the calender to increase in size to the point of poor performance, doubling, etc. The best course is to use Kontact, but that is not always a viable option. Cheers, Alex C. kiser Caesar wrote: > Hello ! > > I need to buy a large number of outlook connectors for kolab. > Toltec seems to be the right choice but I have read bad experience with it. > > So .. What do you think? Toltec or Konsec? > > Thank you for your answers ! > > ------------------------------------------------------------------------ > T?l?phonez gratuitement ? tous vos proches avec Windows Live Messenger > ! T?l?chargez-le maintenant ! > > > ------------------------------------------------------------------------ > > _______________________________________________ > Kolab-users mailing list > Kolab-users at kolab.org > https://kolab.org/mailman/listinfo/kolab-users From michael at pasdziernik.net Tue Oct 21 19:36:17 2008 From: michael at pasdziernik.net (Michael Pasdziernik) Date: Tue, 21 Oct 2008 19:36:17 +0200 Subject: Kolab + outlook connectors ? In-Reply-To: References: Message-ID: <200810211936.17253.michael@pasdziernik.net> Hello, In my opinion bynari connector works best when mailboxes are getting big. It does neither use .pst-files nor pop3 and the local cache separates mails and attachments so the mailcache-file does not get so big as with .pst-files. Regards Michael On Tuesday 21 October 2008 16:14:47 kiser Caesar wrote: > Hello ! > > I need to buy a large number of outlook connectors for kolab. > Toltec seems to be the right choice but I have read bad experience with > it. > > So .. What do you think? Toltec or Konsec? > > Thank you for your answers ! > > _________________________________________________________________ > In?dit ! Des Emotic?nes D?jant?es! Installez les dans votre Messenger ! > http://www.ilovemessenger.fr/Emoticones/EmoticonesDejantees.aspx From jkomar at jbox.ca Tue Oct 21 19:42:57 2008 From: jkomar at jbox.ca (Jason Komar) Date: Tue, 21 Oct 2008 11:42:57 -0600 Subject: Kolab + outlook connectors ? In-Reply-To: <200810211936.17253.michael@pasdziernik.net> References: <200810211936.17253.michael@pasdziernik.net> Message-ID: <200810211142.57809.jkomar@jbox.ca> I have been setting my up my clients running kolab with the Bynari connector and it has been working great. The only drawback has been where the client has a Blackberry, an additional piece of third party software has been required to synchronize it using the Blackberry Desktop Software. -- Jason Komar 806706 Alberta Ltd. O/A Stormfront Ventures Email: jkomar at jbox.ca Web: www.jbox.ca On Tuesday 21 October 2008 11:36:17 Michael Pasdziernik wrote: > Hello, > In my opinion bynari connector works best when mailboxes are getting big. > It does neither use .pst-files nor pop3 and the local cache separates mails > and attachments so the mailcache-file does not get so big as with > .pst-files. > > Regards > Michael > > On Tuesday 21 October 2008 16:14:47 kiser Caesar wrote: > > Hello ! > > > > I need to buy a large number of outlook connectors for kolab. > > Toltec seems to be the right choice but I have read bad experience with > > it. > > > > So .. What do you think? Toltec or Konsec? > > > > Thank you for your answers ! > > > > _________________________________________________________________ > > In?dit ! Des Emotic?nes D?jant?es! Installez les dans votre Messenger ! > > http://www.ilovemessenger.fr/Emoticones/EmoticonesDejantees.aspx > > _______________________________________________ > Kolab-users mailing list > Kolab-users at kolab.org > https://kolab.org/mailman/listinfo/kolab-users From sbambach at gmx.net Tue Oct 21 20:30:14 2008 From: sbambach at gmx.net (Stefan Bambach) Date: Tue, 21 Oct 2008 20:30:14 +0200 Subject: Kolab 2.2 addressbook export as spamassassin whitelist In-Reply-To: <55902.157.92.44.72.1224608719.squirrel@sec.bit-consulting.com.ar> References: <200810202008.21555.stefanb@bambach.intra> <200810211842.05641.stefanb@bambach.intra> <55902.157.92.44.72.1224608719.squirrel@sec.bit-consulting.com.ar> Message-ID: <200810212030.14776.stefanb@bambach.intra> Hi, > As the address book is stored in an imap folder, maybe you can: > > 1. Use inotify to be notified about changes. > 2. Login with cyrus' master password. > 3. For every user (or maybe only you), get the last emails with vcards > 4. Parse them and add everything into spamassassin. > > I've done 2. and something like 3 with perl's Imap::Admin. I'm sure there > should be something similar for your preferred language. nice idea with inotify... adapted my shell script for inotify support (grep/awk)... solved with something like (snippet): inotifywait -e modify -e delete -e create --format '%w %e %f' grep -h smtp-address /* | awk -F">" '{print $2}' | awk -F" whitelist_sender and: read_hash(\%whitelist_sender, '/kolab/var/amavisd/whitelist_sender'); activated in amavisd.conf. If I'll have more spare time, I will replace my simple shell script with a more accurate scripting language with imap admin methods (I don't know perl; I think the only well known language I do not know :-( I should really get in touch with it. There are really many tools and libs out there, that would help me in such cases. And this would be a small project to play with it) thx to all. ciao. Stefan > > Just my 2 cents > -- Diego. > > >>> If its just for you I'd just export the addresses once in a while and > >> > >> run it through a scripted converter to get the addresses whitelisted. > > > > Would be no problem. But No. I know that I will forget to do that ;-) > > > > What about adapting a java,python,groovy,C, ... client, that can connect > > to > > kolab and export the data? perhaps one of the connectors for other > > groupwares ? > > > > Perhaps an simple imap client, that extract the attachments and than > > parse the > > xml? > > _______________________________________________ > Kolab-users mailing list > Kolab-users at kolab.org > https://kolab.org/mailman/listinfo/kolab-users From ml at radoeka.nl Tue Oct 21 20:33:29 2008 From: ml at radoeka.nl (Richard Bos) Date: Tue, 21 Oct 2008 20:33:29 +0200 Subject: Distribution lists issue In-Reply-To: <200810211213.36794.viljoenjp@workforce.co.za> References: <200810171500.16704.viljoenjp@workforce.co.za> <20081021112600.752326yg5ycy6hj4@webmail.pardus.de> <200810211213.36794.viljoenjp@workforce.co.za> Message-ID: <200810212033.29383.ml@radoeka.nl> Op Tuesday 21 October 2008 12:13:36 schreef JP Viljoen: > On Tuesday 21 October 2008 11:26:00 Gunnar Wrobel wrote: > > Uh, oh. This is a Kolab2/Gentoo-2.1 installation. I am the maintainer > > of that port and I did not continue that line of the server. The 2.1 > > version was something that helped me getting a good grip on the > > shortcomings of running Kolab on Gentoo. And I mainly used this for > > ideas on Kolab2/Gentoo-2.2. This version is not finished yet though. > > > > If your server is anything near to being used in production I'd really > > recommend to switch to the Kolab2/OpenPKG-2.2 version. You should be > > able to cleanly migrate the data from the older Gentoo system. > > Hiya > > Thanks for responding, especially with the exact details. And it is, in > fact, in production doing close to 5GB's of mail per day on average. Could > you perhaps point me to a specific migration guide if it's in the archives > somewhere? I will also start looking at the Wiki now, but if anyone knows > of any pitfalls which one could experience I would greatly appreciate it if > they could share. Start reading from the bottom: http://ftp.gwdg.de/pub/linux/kolab/server/release/kolab-server-2.2.0/sources/1st.README -- Richard Bos We are borrowing the world of our children, It is not inherited from our parents. From dvadell at linuxclusters.com.ar Tue Oct 21 20:43:23 2008 From: dvadell at linuxclusters.com.ar (Diego M. Vadell) Date: Tue, 21 Oct 2008 15:43:23 -0300 (ART) Subject: Kolab 2.2 addressbook export as spamassassin whitelist In-Reply-To: <200810212030.14776.stefanb@bambach.intra> References: <200810202008.21555.stefanb@bambach.intra> <200810211842.05641.stefanb@bambach.intra> <55902.157.92.44.72.1224608719.squirrel@sec.bit-consulting.com.ar> <200810212030.14776.stefanb@bambach.intra> Message-ID: <43759.157.92.44.71.1224614603.squirrel@sec.bit-consulting.com.ar> hi, Thanks for sharing. -- Diego. > Hi, > >> As the address book is stored in an imap folder, maybe you can: >> >> 1. Use inotify to be notified about changes. >> 2. Login with cyrus' master password. >> 3. For every user (or maybe only you), get the last emails with vcards >> 4. Parse them and add everything into spamassassin. >> >> I've done 2. and something like 3 with perl's Imap::Admin. I'm sure >> there >> should be something similar for your preferred language. > > nice idea with inotify... adapted my shell script for inotify support > (grep/awk)... > > solved with something like (snippet): > inotifywait -e modify -e delete -e create --format '%w %e %f' > grep -h smtp-address /* | awk -F">" '{print $2}' | awk -F" $1}' | sort | uniq > whitelist_sender > > and: > read_hash(\%whitelist_sender, '/kolab/var/amavisd/whitelist_sender'); > activated in amavisd.conf. > > If I'll have more spare time, I will replace my simple shell script with a > more accurate scripting language with imap admin methods (I don't know > perl; > I think the only well known language I do not know :-( I should really get > in > touch with it. There are really many tools and libs out there, that would > help me in such cases. And this would be a small project to play with it) > > thx to all. > > ciao. Stefan > >> >> Just my 2 cents >> -- Diego. >> >> >>> If its just for you I'd just export the addresses once in a while >> and >> >> >> >> run it through a scripted converter to get the addresses whitelisted. >> > >> > Would be no problem. But No. I know that I will forget to do that ;-) >> > >> > What about adapting a java,python,groovy,C, ... client, that can >> connect >> > to >> > kolab and export the data? perhaps one of the connectors for other >> > groupwares ? >> > >> > Perhaps an simple imap client, that extract the attachments and than >> > parse the >> > xml? >> >> _______________________________________________ >> 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 albrecht.dress at lios-tech.com Wed Oct 22 10:02:26 2008 From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=) Date: Wed, 22 Oct 2008 10:02:26 +0200 Subject: Q about Group Accounts Message-ID: <1224662546l.3871l.0l@pc104141.koeln.nktcables.com> Hi, while setting up Kolab in a test environment, I ran into a probably dumb question for which I cannot find the answer in the docs... Is it possible to send mails from the outside world to a group account (like messages to a normal user, but different from messages to an internal user)? The reason behind is to have a group like "sales", which shall receive messages from everywhere, but many people may subscribe to the imap folders and read/process messages. Thanks, Albrecht. From NPrice at gibb.co.za Thu Oct 23 07:29:58 2008 From: NPrice at gibb.co.za (Price,Neil) Date: Thu, 23 Oct 2008 07:29:58 +0200 Subject: Ldap replication Message-ID: <7B91BBC61758DD1183BE000C296D2CA7104990@ct-exchange.wins.lawco.com> Since we have some developers here.. What kind of replication is planned for future versions of Kolab? Undoubtedly syncrepl support is planned. But what kind? Delta syncrepl replica? N-way multi-master? The debian port already uses delta syncrepl but it takes a lot of tweaking to get it to work, if at all. From gabriele_d_g at yahoo.it Thu Oct 23 16:30:32 2008 From: gabriele_d_g at yahoo.it (Gabriele Di Giambelardini) Date: Thu, 23 Oct 2008 14:30:32 +0000 (GMT) Subject: kolab 2.2 Message-ID: <206681.88280.qm@web25907.mail.ukl.yahoo.com> Hi to all, I have a big problem with kolab 2 performance. I have an server with 10 GB of RAM and about 150000 users. After I imported the user in the kolab ldap the server become very very slow, it's impossible use a webmail. so I installed the webmail on other server with eaccelerator. But now on my main server the kolab imapd take all the CPU and every thing is too slow. The are some settings for imap of if somebody know the why of this latency... THANKS Scopri il blog di Yahoo! Mail: Trucchi, novit? e scrivi la tua opinione. http://www.ymailblogit.com/blog -------------- next part -------------- An HTML attachment was scrubbed... URL: http://kolab.org/pipermail/kolab-users/attachments/20081023/5e0bc6f7/attachment.html From alessio at skye.it Thu Oct 23 17:51:44 2008 From: alessio at skye.it (Alessio Cecchi) Date: Thu, 23 Oct 2008 17:51:44 +0200 Subject: Problem with kolabquotawarn Message-ID: <200810231751.45071.alessio@skye.it> Hi, in the syslog of this kolab server i found this: Oct 23 17:30:02 mail kolabquotawarn: Warning: Could not read /kolab/etc/kolab/kolab.conf Oct 23 17:30:02 mail kolabquotawarn: C Error: One or more required configuration variables (`bind_dn', `bind_pw', `ldap_uri' and/or `base_dn') are missing in `kolab.conf' Oct 23 17:30:02 mail kolabquotawarn: C Error: Unable to bind to DN `' Oct 23 17:30:02 mail kolabquotawarn: C Error: Unable to find kolab object `k=kolab,' Oct 23 17:30:02 mail kolabquotawarn[14826]: fatal: Can't read configuration, please make sure that kolabquotawarn runs with sufficient privileges mail:~# ls -lh /kolab/etc/kolab/kolab.conf -rw------- 1 kolab-n kolab-n 1009 Mar 25 2008 /kolab/etc/kolab/kolab.conf Why in others kolab server the owner of kolab.conf is "kolab" and not "kolab-n"? But kolab is running without, apparantly, problem. How can i fix this error? Thanks -- Alessio Cecchi is: @ ILS -> http://www.linux.it/~alessice/ Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/ @ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it @ LOLUG -> neo-Socio http://www.lolug.net From steuwer at univention.de Fri Oct 24 08:34:26 2008 From: steuwer at univention.de (Ingo Steuwer) Date: Fri, 24 Oct 2008 08:34:26 +0200 Subject: kolab 2.2 In-Reply-To: <206681.88280.qm@web25907.mail.ukl.yahoo.com> References: <206681.88280.qm@web25907.mail.ukl.yahoo.com> Message-ID: <200810240834.27971.steuwer@univention.de> Hi, Am Donnerstag, 23. Oktober 2008 schrieb Gabriele Di Giambelardini: > Hi to all, I have a big problem with kolab 2 performance. > I have an server with 10 GB of RAM and about 150000 users. Once they are imported into LDAP and the mail-spools are created, the pure amount of users should not be the problem, but the number of current users and the number/size of deliviered mails. We installed a kolab-based mailserver with ~80000 users (mailaccounts) and Horde webmail on a far smaller hardware (one server, 2GB RAM) years ago. > After I imported the user in the kolab ldap the server become very very > slow, it's impossible use a webmail. so I installed the webmail on other > server with eaccelerator. But now on my main server the kolab imapd take > all the CPU and every thing is too slow. The are some settings for imap of > if somebody know the why of this latency... THANKS We [1] had trouble with cyrus and horde getting slow in large installations because of a very inefficient group-ACL-computing of cyrus. In some cases it helps to activate "nscd" with large cache sizes (mhm, I don't know if nscd is part of a standard Kolab-distributon?), in other scenarios we deactivated this in Cyrus' imapd.conf (unix_group_enable: no) - which is OK as long as group ACLs are not required. But this might also be slightly different in plain Kolab. You should try to figure out what the imapd really does. Is it during a login, mail-delivery, folder-operations etc.; maybe imapd is only waiting for something else (Disk I/O, LDAP, ...)? Regards Ingo Steuwer [1] Please note that we don't use the openpkg-distribution of kolab but a derivated installation based on Debian with patches and configurations similar to/derived from plain kolab. > > > Scopri il blog di Yahoo! Mail: > Trucchi, novit? e scrivi la tua opinione. > http://www.ymailblogit.com/blog -- Ingo Steuwer Projektmanagement steuwer at univention.de Univention GmbH Linux for your Business fon: +49 421 22 232-43 Mary-Somerville-Str.1 28359 Bremen mob: +49 173 2112971 http://www.univention.de fax: +49 421 22 232-99 From gabriele_d_g at yahoo.it Fri Oct 24 09:17:55 2008 From: gabriele_d_g at yahoo.it (Gabriele Di Giambelardini) Date: Fri, 24 Oct 2008 07:17:55 +0000 (GMT) Subject: kolab 2.2 Message-ID: <830843.9341.qm@web25901.mail.ukl.yahoo.com> Thanks, But I don't know the why in my htop I see the imap have a 100% of CPU... There is some parameter or something I should do ?? thanks ________________________________ Da: Ingo Steuwer A: kolab-users at kolab.org Cc: Gabriele Di Giambelardini Inviato: Venerd? 24 ottobre 2008, 8:34:26 Oggetto: Re: kolab 2.2 Hi, Am Donnerstag, 23. Oktober 2008 schrieb Gabriele Di Giambelardini: > Hi to all, I have a big problem with kolab 2 performance. > I have an server with 10 GB of RAM and about 150000 users. Once they are imported into LDAP and the mail-spools are created, the pure amount of users should not be the problem, but the number of current users and the number/size of deliviered mails. We installed a kolab-based mailserver with ~80000 users (mailaccounts) and Horde webmail on a far smaller hardware (one server, 2GB RAM) years ago. > After I imported the user in the kolab ldap the server become very very > slow, it's impossible use a webmail. so I installed the webmail on other > server with eaccelerator. But now on my main server the kolab imapd take > all the CPU and every thing is too slow. The are some settings for imap of > if somebody know the why of this latency... THANKS We [1] had trouble with cyrus and horde getting slow in large installations because of a very inefficient group-ACL-computing of cyrus. In some cases it helps to activate "nscd" with large cache sizes (mhm, I don't know if nscd is part of a standard Kolab-distributon?), in other scenarios we deactivated this in Cyrus' imapd.conf (unix_group_enable: no) - which is OK as long as group ACLs are not required. But this might also be slightly different in plain Kolab. You should try to figure out what the imapd really does. Is it during a login, mail-delivery, folder-operations etc.; maybe imapd is only waiting for something else (Disk I/O, LDAP, ...)? Regards Ingo Steuwer [1] Please note that we don't use the openpkg-distribution of kolab but a derivated installation based on Debian with patches and configurations similar to/derived from plain kolab. > > > Scopri il blog di Yahoo! Mail: > Trucchi, novit? e scrivi la tua opinione. > http://www.ymailblogit.com/blog -- Ingo Steuwer Projektmanagement steuwer at univention.de Univention GmbH Linux for your Business fon: +49 421 22 232-43 Mary-Somerville-Str.1 28359 Bremen mob: +49 173 2112971 http://www.univention.de fax: +49 421 22 232-99 _______________________________________________ Kolab-users mailing list Kolab-users at kolab.org https://kolab.org/mailman/listinfo/kolab-users Scopri il blog di Yahoo! Mail: Trucchi, novit? e scrivi la tua opinione. http://www.ymailblogit.com/blog -------------- next part -------------- An HTML attachment was scrubbed... URL: http://kolab.org/pipermail/kolab-users/attachments/20081024/fc97b250/attachment.html From gabriele_d_g at yahoo.it Fri Oct 24 11:22:31 2008 From: gabriele_d_g at yahoo.it (Gabriele Di Giambelardini) Date: Fri, 24 Oct 2008 09:22:31 +0000 (GMT) Subject: kolab 2.2 Message-ID: <364110.87325.qm@web25907.mail.ukl.yahoo.com> Ok after many many tests, the imapd service use all the CPU only when an user use the horde webmail.... Any solution?? ________________________________ Da: Gabriele Di Giambelardini A: Ingo Steuwer ; kolab-users at kolab.org Inviato: Venerd? 24 ottobre 2008, 9:17:55 Oggetto: Re: kolab 2.2 Thanks, But I don't know the why in my htop I see the imap have a 100% of CPU... There is some parameter or something I should do ?? thanks ________________________________ Da: Ingo Steuwer A: kolab-users at kolab.org Cc: Gabriele Di Giambelardini Inviato: Venerd? 24 ottobre 2008, 8:34:26 Oggetto: Re: kolab 2.2 Hi, Am Donnerstag, 23. Oktober 2008 schrieb Gabriele Di Giambelardini: > Hi to all, I have a big problem with kolab 2 performance. > I have an server with 10 GB of RAM and about 150000 users. Once they are imported into LDAP and the mail-spools are created, the pure amount of users should not be the problem, but the number of current users and the number/size of deliviered mails. We installed a kolab-based mailserver with ~80000 users (mailaccounts) and Horde webmail on a far smaller hardware (one server, 2GB RAM) years ago. > After I imported the user in the kolab ldap the server become very very > slow, it's impossible use a webmail. so I installed the webmail on other > server with eaccelerator. But now on my main server the kolab imapd take > all the CPU and every thing is too slow. The are some settings for imap of > if somebody know the why of this latency... THANKS We [1] had trouble with cyrus and horde getting slow in large installations because of a very inefficient group-ACL-computing of cyrus. In some cases it helps to activate "nscd" with large cache sizes (mhm, I don't know if nscd is part of a standard Kolab-distributon?), in other scenarios we deactivated this in Cyrus' imapd.conf (unix_group_enable: no) - which is OK as long as group ACLs are not required. But this might also be slightly different in plain Kolab. You should try to figure out what the imapd really does. Is it during a login, mail-delivery, folder-operations etc.; maybe imapd is only waiting for something else (Disk I/O, LDAP, ...)? Regards Ingo Steuwer [1] Please note that we don't use the openpkg-distribution of kolab but a derivated installation based on Debian with patches and configurations similar to/derived from plain kolab. > > > Scopri il blog di Yahoo! Mail: > Trucchi, novit? e scrivi la tua opinione. > http://www.ymailblogit.com/blog -- Ingo Steuwer Projektmanagement steuwer at univention.de Univention GmbH Linux for your Business fon: +49 421 22 232-43 Mary-Somerville-Str.1 28359 Bremen mob: +49 173 2112971 http://www.univention.de fax: +49 421 22 232-99 _______________________________________________ Kolab-users mailing list Kolab-users at kolab.org https://kolab.org/mailman/listinfo/kolab-users ________________________________ Scopri il Blog di Yahoo! Mail: trucchi, novit?, consigli... e scrivi la tua opinione! Scopri il blog di Yahoo! Mail: Trucchi, novit? e scrivi la tua opinione. http://www.ymailblogit.com/blog -------------- next part -------------- An HTML attachment was scrubbed... URL: http://kolab.org/pipermail/kolab-users/attachments/20081024/18858da7/attachment-0001.html From m.ouderling at linxs.nl Fri Oct 24 11:56:03 2008 From: m.ouderling at linxs.nl (Rene Ouderling) Date: Fri, 24 Oct 2008 11:56:03 +0200 Subject: Error installing kolab 2.2 on debian Message-ID: <200810241156.04120.m.ouderling@linxs.nl> Hi, Yesterday i installed KOLAB 2.2 on a testsystem with Debian etch 4.04. The installation finished without a problem. specification (uname -a) of the test system: Linux xxxx 2.6.18-6-686 #1 SMP Thu Oct 9 15:52:18 UTC 2008 i686 GNU/Linux. Today I want to install Kolab 2.2 (with openpkg) on a virtual server also running debian. Specs of the server (uname -a) Linux xxxxxxxxxx 2.6.26-1-amd64 #1 SMP Thu Oct 9 14:16:53 UTC 2008 x86_64 GNU/Linux After following the procedure and installing the nessesary programs like make, gcc, flex, bison, libtool, automake and autoconf I am getting an error during compilation. /tmp/openpkg-20071227/tar-1.19/lib/argp.h:607: multiple definition of `_option_is_end' tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp.h:607: first defined here ../lib/libtar.a(argp-eexst.o): In function `_option_is_short': /tmp/openpkg-20071227/tar-1.19/lib/argp.h:595: multiple definition of `_option_is_short' tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp.h:595: first defined here ../lib/libtar.a(argp-eexst.o): In function `argp_usage': /tmp/openpkg-20071227/tar-1.19/lib/argp.h:589: multiple definition of `argp_usage' tar.o:/tmp/openpkg-20071227/tar-1.19/src/../lib/argp.h:589: first defined here collect2: ld returned 1 exit status make[2]: *** [tar] Error 1 make[2]: Leaving directory `/tmp/openpkg-20071227/tar-1.19/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/openpkg-20071227/tar-1.19' make: *** [all] Error 2 + exit 2 + exit 2 ./openpkg.boot:ERROR: script returned non-null value Has anyone an idea what is wrong. Kind regards Rene From steuwer at univention.de Fri Oct 24 12:20:22 2008 From: steuwer at univention.de (Ingo Steuwer) Date: Fri, 24 Oct 2008 12:20:22 +0200 Subject: kolab 2.2 In-Reply-To: <364110.87325.qm@web25907.mail.ukl.yahoo.com> References: <364110.87325.qm@web25907.mail.ukl.yahoo.com> Message-ID: <200810241220.23190.steuwer@univention.de> Hello, Am Freitag, 24. Oktober 2008 schrieb Gabriele Di Giambelardini: > Ok after many many tests, the imapd service use all the CPU only when an > user use the horde webmail.... Any solution?? during login or the whole session? Is it connected with a special use-case? You might enable user-specific logfiles in cyrus or increase the loglevel to get an impression of what imapd "does". Regards Ingo Steuwer > > ________________________________ > Da: Gabriele Di Giambelardini > A: Ingo Steuwer ; kolab-users at kolab.org > Inviato: Venerd? 24 ottobre 2008, 9:17:55 > Oggetto: Re: kolab 2.2 > > > Thanks, But I don't know the why in my htop I see the imap have a 100% of > CPU... There is some parameter or something I should do ?? > thanks > > > > > ________________________________ > Da: Ingo Steuwer > A: kolab-users at kolab.org > Cc: Gabriele Di Giambelardini > Inviato: Venerd? 24 ottobre 2008, 8:34:26 > Oggetto: Re: kolab 2.2 > > Hi, > > Am Donnerstag, 23. Oktober 2008 schrieb Gabriele Di Giambelardini: > > Hi to all, I have a big problem with kolab 2 performance. > > I have an server with 10 GB of RAM and about 150000 users. > > Once they are imported into LDAP and the mail-spools are created, the pure > amount of users should not be the problem, but the number of current users > and the number/size of deliviered mails. We installed a kolab-based > mailserver with ~80000 users (mailaccounts) and Horde webmail on a far > smaller hardware (one server, 2GB RAM) years ago. > > > After I imported the user in the kolab ldap the server become very very > > slow, it's impossible use a webmail. so I installed the webmail on other > > server with eaccelerator. But now on my main server the kolab imapd take > > all the CPU and every thing is too slow. The are some settings for imap > > of if somebody know the why of this latency... THANKS > > We [1] had trouble with cyrus and horde getting slow in large installations > because of a very inefficient group-ACL-computing of cyrus. In some cases > it helps to activate "nscd" with large cache sizes (mhm, I don't know if > nscd is part of a standard Kolab-distributon?), in other scenarios we > deactivated this in Cyrus' imapd.conf (unix_group_enable: no) - which is OK > as long as group ACLs are not required. But this might also be slightly > different in plain Kolab. > > You should try to figure out what the imapd really does. Is it during a > login, mail-delivery, folder-operations etc.; maybe imapd is only waiting > for something else (Disk I/O, LDAP, ...)? > > Regards > Ingo Steuwer > > [1] Please note that we don't use the openpkg-distribution of kolab but a > derivated installation based on Debian with patches and configurations > similar to/derived from plain kolab. > > > Scopri il blog di Yahoo! Mail: > > Trucchi, novit? e scrivi la tua opinione. > > http://www.ymailblogit.com/blog -- Ingo Steuwer Projektmanagement steuwer at univention.de Univention GmbH Linux for your Business fon: +49 421 22 232-43 Mary-Somerville-Str.1 28359 Bremen mob: +49 173 2112971 http://www.univention.de fax: +49 421 22 232-99 From gabriele_d_g at yahoo.it Fri Oct 24 13:43:10 2008 From: gabriele_d_g at yahoo.it (Gabriele Di Giambelardini) Date: Fri, 24 Oct 2008 11:43:10 +0000 (GMT) Subject: kolab 2.2 Message-ID: <345261.6262.qm@web25901.mail.ukl.yahoo.com> After login imapd take 100% cpu ________________________________ Da: Ingo Steuwer A: kolab-users at kolab.org Cc: Gabriele Di Giambelardini Inviato: Venerd? 24 ottobre 2008, 12:20:22 Oggetto: Re: kolab 2.2 Hello, Am Freitag, 24. Oktober 2008 schrieb Gabriele Di Giambelardini: > Ok after many many tests, the imapd service use all the CPU only when an > user use the horde webmail.... Any solution?? during login or the whole session? Is it connected with a special use-case? You might enable user-specific logfiles in cyrus or increase the loglevel to get an impression of what imapd "does". Regards Ingo Steuwer > > ________________________________ > Da: Gabriele Di Giambelardini > A: Ingo Steuwer ; kolab-users at kolab.org > Inviato: Venerd? 24 ottobre 2008, 9:17:55 > Oggetto: Re: kolab 2.2 > > > Thanks, But I don't know the why in my htop I see the imap have a 100% of > CPU... There is some parameter or something I should do ?? > thanks > > > > > ________________________________ > Da: Ingo Steuwer > A: kolab-users at kolab.org > Cc: Gabriele Di Giambelardini > Inviato: Venerd? 24 ottobre 2008, 8:34:26 > Oggetto: Re: kolab 2.2 > > Hi, > > Am Donnerstag, 23. Oktober 2008 schrieb Gabriele Di Giambelardini: > > Hi to all, I have a big problem with kolab 2 performance. > > I have an server with 10 GB of RAM and about 150000 users. > > Once they are imported into LDAP and the mail-spools are created, the pure > amount of users should not be the problem, but the number of current users > and the number/size of deliviered mails. We installed a kolab-based > mailserver with ~80000 users (mailaccounts) and Horde webmail on a far > smaller hardware (one server, 2GB RAM) years ago. > > > After I imported the user in the kolab ldap the server become very very > > slow, it's impossible use a webmail. so I installed the webmail on other > > server with eaccelerator. But now on my main server the kolab imapd take > > all the CPU and every thing is too slow. The are some settings for imap > > of if somebody know the why of this latency... THANKS > > We [1] had trouble with cyrus and horde getting slow in large installations > because of a very inefficient group-ACL-computing of cyrus. In some cases > it helps to activate "nscd" with large cache sizes (mhm, I don't know if > nscd is part of a standard Kolab-distributon?), in other scenarios we > deactivated this in Cyrus' imapd.conf (unix_group_enable: no) - which is OK > as long as group ACLs are not required. But this might also be slightly > different in plain Kolab. > > You should try to figure out what the imapd really does. Is it during a > login, mail-delivery, folder-operations etc.; maybe imapd is only waiting > for something else (Disk I/O, LDAP, ...)? > > Regards > Ingo Steuwer > > [1] Please note that we don't use the openpkg-distribution of kolab but a > derivated installation based on Debian with patches and configurations > similar to/derived from plain kolab. > > > Scopri il blog di Yahoo! Mail: > > Trucchi, novit? e scrivi la tua opinione. > > http://www.ymailblogit.com/blog -- Ingo Steuwer Projektmanagement steuwer at univention.de Univention GmbH Linux for your Business fon: +49 421 22 232-43 Mary-Somerville-Str.1 28359 Bremen mob: +49 173 2112971 http://www.univention.de fax: +49 421 22 232-99 _______________________________________________ Kolab-users mailing list Kolab-users at kolab.org https://kolab.org/mailman/listinfo/kolab-users Scopri il blog di Yahoo! Mail: Trucchi, novit? e scrivi la tua opinione. http://www.ymailblogit.com/blog -------------- next part -------------- An HTML attachment was scrubbed... URL: http://kolab.org/pipermail/kolab-users/attachments/20081024/273b0a89/attachment.html From m.ouderling at linxs.nl Fri Oct 24 14:23:13 2008 From: m.ouderling at linxs.nl (Rene Ouderling) Date: Fri, 24 Oct 2008 14:23:13 +0200 Subject: Error installing kolab 2.2 on debian In-Reply-To: <200810241156.04120.m.ouderling@linxs.nl> References: <200810241156.04120.m.ouderling@linxs.nl> Message-ID: <200810241423.13979.m.ouderling@linxs.nl> Op vrijdag 24 oktober 2008 11:56, schreef Rene Ouderling: > make[2]: *** [tar] Error 1 It looks like i am having te same problem as issue 2871 in the Bug/Wish tracker. a workaround is mentioned in the readme 1st document but icant find it in the document what comes with the downloaded sources. Could someone give me some information. BTW I tried to compile with gcc-4.1 and gcc-4.2 wait exact the same errors. Kind regards Rene From m.ouderling at linxs.nl Fri Oct 24 16:41:49 2008 From: m.ouderling at linxs.nl (Rene Ouderling) Date: Fri, 24 Oct 2008 16:41:49 +0200 Subject: Error installing kolab 2.2 on debian In-Reply-To: <200810241423.13979.m.ouderling@linxs.nl> References: <200810241156.04120.m.ouderling@linxs.nl> <200810241423.13979.m.ouderling@linxs.nl> Message-ID: <200810241641.49716.m.ouderling@linxs.nl> Op vrijdag 24 oktober 2008 14:23, schreef Rene Ouderling: > Op vrijdag 24 oktober 2008 11:56, schreef Rene Ouderling: > > make[2]: *** [tar] Error 1 > > It looks like i am having te same problem as issue 2871 in the Bug/Wish > tracker. a workaround is mentioned in the readme 1st document but icant > find it in the document what comes with the downloaded sources. > > Could someone give me some information. > > BTW I tried to compile with gcc-4.1 and gcc-4.2 wait exact the same errors. > > Kind regards > > Rene > > _______________________________________________ > Kolab-users mailing list > Kolab-users at kolab.org > https://kolab.org/mailman/listinfo/kolab-users Asked to change Debian lenny/amd64 to debian etch and we will try again. From m.ouderling at linxs.nl Fri Oct 24 22:03:47 2008 From: m.ouderling at linxs.nl (Rene Ouderling) Date: Fri, 24 Oct 2008 22:03:47 +0200 Subject: gmp compilation error on amd64 Message-ID: <200810242203.47892.m.ouderling@linxs.nl> Again no luck with the installation but now on debian etch. After about two hours the compilation process fails at gmp. See the log below. This problem is the same as issue 2928 and there is the mentioning of a patch which i believe is the same as in a mail from Thomas see the link http://kolab.org/pipermail/kolab-commits/2008q3/008490.KHTML But could someone tell me how to implement this patch. Can' t find it in the wiki Kind regards Rene ------------------------------------------------------------------------------------------------------------------------------------- Preparing... ################################################## pkgconfig ################################################## :::: /tmp/install-kolab.27585.21778.20215.2505/pkgconfig-0.23-20080117.src.rpm = 0 :::: :::: /tmp/install-kolab.27585.21778.20215.2505/gmp-4.2.2-20080101.src.rpm :::: Installing /tmp/install-kolab.27585.21778.20215.2505/gmp-4.2.2-20080101.src.rpm Executing(%prep): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.95270 + cd /kolab/RPM/TMP + cd /kolab/RPM/TMP + rm -rf gmp-4.2.2 + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/gmp/gmp-4.2.2.tar.gz + /kolab/lib/openpkg/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd gmp-4.2.2 + echo 'Patch #0 (gmp.patch):' Patch #0 (gmp.patch): + /kolab/lib/openpkg/patch -p0 -s -b + rm -rf mpn/sparc32 mpn/sparc64 + exit 0 Executing(%build): env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.29339 + cd /kolab/RPM/TMP + cd gmp-4.2.2 + export CC=/kolab/bin/cc + CC=/kolab/bin/cc + export CFLAGS=-fPIC + CFLAGS=-fPIC + case "amd64-debian4.0" in + ./configure --prefix=/kolab --disable-shared checking build system type... pentium2-unknown-linux-gnu checking host system type... pentium2-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking ABI=32 checking whether /kolab/bin/cc is gcc... yes checking compiler /kolab/bin/cc -fPIC ... yes checking compiler /kolab/bin/cc -fPIC has sizeof(long)==4... no configure: error: could not find a working compiler, see config.log for details error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.29339 (%build) ----------------------------------------------------------------------------------------------------------------------------------------------- From aspineux at gmail.com Sun Oct 26 18:49:15 2008 From: aspineux at gmail.com (Alain Spineux) Date: Sun, 26 Oct 2008 18:49:15 +0100 Subject: kolab 2.2 In-Reply-To: <206681.88280.qm@web25907.mail.ukl.yahoo.com> References: <206681.88280.qm@web25907.mail.ukl.yahoo.com> Message-ID: <71fe4e760810261049m714cecd9i4b1374bb6621fe6d@mail.gmail.com> On Thu, Oct 23, 2008 at 3:30 PM, Gabriele Di Giambelardini wrote: > Hi to all, I have a big problem with kolab 2 performance. > I have an server with 10 GB of RAM and about 150000 users. 150K users is a lot on a single server running all the mail stuff ! Which OS are your running ? Are you using a 64bits OS ? Are your 10GB of RAM all in use ? Maybe this page could give you some hints on how it is difficult to tune a mail server ! http://blog.fastmail.fm/2007/09/21/reiserfs-bugs-32-bit-vs-64-bit-kernels-cache-vs-inode-memory/ Are you using a RAID 5 ? RAID 10 could give you better performances ! > After I imported the user in the kolab ldap the server become very very > slow, it's impossible use a webmail. so I installed the webmail on other > server with eaccelerator. > But now on my main server the kolab imapd take all the CPU and every thing > is too slow. > The are some settings for imap of if somebody know the why of this > latency... > THANKS > > ________________________________ > Scopri il Blog di Yahoo! Mail: trucchi, novit?, consigli... e scrivi la tua > opinione! > _______________________________________________ > 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 Sun Oct 26 19:07:25 2008 From: aspineux at gmail.com (Alain Spineux) Date: Sun, 26 Oct 2008 19:07:25 +0100 Subject: gmp compilation error on amd64 In-Reply-To: <200810242203.47892.m.ouderling@linxs.nl> References: <200810242203.47892.m.ouderling@linxs.nl> Message-ID: <71fe4e760810261107m79bc310dwf88327ba6e9055e6@mail.gmail.com> On Fri, Oct 24, 2008 at 9:03 PM, Rene Ouderling wrote: > Again no luck with the installation but now on debian etch. After about two > hours the compilation process fails at gmp. See the log below. This problem > is the same as issue 2928 and there is the mentioning of a patch which i > believe is the same as in a mail from Thomas see the link > http://kolab.org/pipermail/kolab-commits/2008q3/008490.KHTML > But could someone tell me how to implement this patch. Can' t find it in the > wiki First install the sources # openpkg rpm -i gmp-XXXXX.src.rpm then edit the file gmp.spec that shoud be somewhere in /kolab/RPM/SRC/gmp To match the one described in http://kolab.org/pipermail/kolab-commits/2008q3/008490.html then recompile the package # openpkg rpm -bb /kolab/RPM/SRC/gmp/gmp.spec The last line of the log shoud give you the full path of the newly compiled package. Install it # openpkg rpm -Uvh /kolab/RPM/PKG/gmpXXXXX.rpm and try to continue the install process OR OR OR OR OR instead of creating a binary package, create a source package # openpkg rpm -bs /kolab/RPM/SRC/gmp/gmp.spec and replace the source package by the new one that you will found somewhere in /kolab/RPM/PKG/gmpXXXXX.src.rpm Now you can try to restart the installation process from scratch on a any 64bits OS. Hope this help > > Kind regards > > Rene > ------------------------------------------------------------------------------------------------------------------------------------- > Preparing... > ################################################## > pkgconfig > ################################################## > :::: /tmp/install-kolab.27585.21778.20215.2505/pkgconfig-0.23-20080117.src.rpm > = 0 :::: > :::: /tmp/install-kolab.27585.21778.20215.2505/gmp-4.2.2-20080101.src.rpm :::: > > Installing /tmp/install-kolab.27585.21778.20215.2505/gmp-4.2.2-20080101.src.rpm > Executing(%prep): > env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.95270 > + cd /kolab/RPM/TMP > + cd /kolab/RPM/TMP > + rm -rf gmp-4.2.2 > + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/gmp/gmp-4.2.2.tar.gz > + /kolab/lib/openpkg/tar -xf - > + STATUS=0 > + '[' 0 -ne 0 ']' > + cd gmp-4.2.2 > + echo 'Patch #0 (gmp.patch):' > Patch #0 (gmp.patch): > + /kolab/lib/openpkg/patch -p0 -s -b > + rm -rf mpn/sparc32 mpn/sparc64 > + exit 0 > Executing(%build): > env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e /kolab/RPM/TMP/rpm-tmp.29339 > + cd /kolab/RPM/TMP > + cd gmp-4.2.2 > + export CC=/kolab/bin/cc > + CC=/kolab/bin/cc > + export CFLAGS=-fPIC > + CFLAGS=-fPIC > + case "amd64-debian4.0" in > + ./configure --prefix=/kolab --disable-shared > checking build system type... pentium2-unknown-linux-gnu > checking host system type... pentium2-unknown-linux-gnu > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... yes > checking whether to enable maintainer-specific portions of Makefiles... no > checking ABI=32 > checking whether /kolab/bin/cc is gcc... yes > checking compiler /kolab/bin/cc -fPIC ... yes > checking compiler /kolab/bin/cc -fPIC has sizeof(long)==4... no > configure: error: could not find a working compiler, see config.log for > details > error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.29339 (%build) > ----------------------------------------------------------------------------------------------------------------------------------------------- > > _______________________________________________ > 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 m.ouderling at linxs.nl Sun Oct 26 21:47:58 2008 From: m.ouderling at linxs.nl (Rene Ouderling) Date: Sun, 26 Oct 2008 21:47:58 +0100 Subject: gmp compilation error on amd64 In-Reply-To: <71fe4e760810261107m79bc310dwf88327ba6e9055e6@mail.gmail.com> References: <200810242203.47892.m.ouderling@linxs.nl> <71fe4e760810261107m79bc310dwf88327ba6e9055e6@mail.gmail.com> Message-ID: <200810262147.58665.m.ouderling@linxs.nl> Op zondag 26 oktober 2008 19:07, schreef Alain Spineux: > On Fri, Oct 24, 2008 at 9:03 PM, Rene Ouderling wrote: > > Again no luck with the installation but now on debian etch. After about > > two hours the compilation process fails at gmp. See the log below. This > > problem is the same as issue 2928 and there is the mentioning of a patch > > which i believe is the same as in a mail from Thomas see the link > > http://kolab.org/pipermail/kolab-commits/2008q3/008490.KHTML > > But could someone tell me how to implement this patch. Can' t find it in > > the wiki > > First install the sources > > # openpkg rpm -i gmp-XXXXX.src.rpm > > then edit the file gmp.spec that shoud be somewhere in /kolab/RPM/SRC/gmp > To match the one described in > http://kolab.org/pipermail/kolab-commits/2008q3/008490.html > > then recompile the package > > # openpkg rpm -bb /kolab/RPM/SRC/gmp/gmp.spec > > The last line of the log shoud give you the full path of the newly > compiled package. > Install it > > # openpkg rpm -Uvh /kolab/RPM/PKG/gmpXXXXX.rpm > > and try to continue the install process > > OR OR OR OR OR > > instead of creating a binary package, create a source package > > # openpkg rpm -bs /kolab/RPM/SRC/gmp/gmp.spec > > and replace the source package by the new one that you will found > somewhere in /kolab/RPM/PKG/gmpXXXXX.src.rpm > > Now you can try to restart the installation process from scratch on a > any 64bits OS. > > Hope this help > > > Kind regards > > > > Rene > > ------------------------------------------------------------------------- > >------------------------------------------------------------ Preparing... > > ################################################## > > pkgconfig > > ################################################## > > > > :::: /tmp/install-kolab.27585.21778.20215.2505/pkgconfig-0.23-20080117.s > > ::::rc.rpm > > > > = 0 :::: > > :::: /tmp/install-kolab.27585.21778.20215.2505/gmp-4.2.2-20080101.src.rp > > ::::m :::: > > > > Installing > > /tmp/install-kolab.27585.21778.20215.2505/gmp-4.2.2-20080101.src.rpm > > Executing(%prep): > > env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e > > /kolab/RPM/TMP/rpm-tmp.95270 + cd /kolab/RPM/TMP > > + cd /kolab/RPM/TMP > > + rm -rf gmp-4.2.2 > > + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/gmp/gmp-4.2.2.tar.gz > > + /kolab/lib/openpkg/tar -xf - > > + STATUS=0 > > + '[' 0 -ne 0 ']' > > + cd gmp-4.2.2 > > + echo 'Patch #0 (gmp.patch):' > > Patch #0 (gmp.patch): > > + /kolab/lib/openpkg/patch -p0 -s -b > > + rm -rf mpn/sparc32 mpn/sparc64 > > + exit 0 > > Executing(%build): > > env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e > > /kolab/RPM/TMP/rpm-tmp.29339 + cd /kolab/RPM/TMP > > + cd gmp-4.2.2 > > + export CC=/kolab/bin/cc > > + CC=/kolab/bin/cc > > + export CFLAGS=-fPIC > > + CFLAGS=-fPIC > > + case "amd64-debian4.0" in > > + ./configure --prefix=/kolab --disable-shared > > checking build system type... pentium2-unknown-linux-gnu > > checking host system type... pentium2-unknown-linux-gnu > > checking for a BSD-compatible install... /usr/bin/install -c > > checking whether build environment is sane... yes > > checking for gawk... no > > checking for mawk... mawk > > checking whether make sets $(MAKE)... yes > > checking whether to enable maintainer-specific portions of Makefiles... > > no checking ABI=32 > > checking whether /kolab/bin/cc is gcc... yes > > checking compiler /kolab/bin/cc -fPIC ... yes > > checking compiler /kolab/bin/cc -fPIC has sizeof(long)==4... no > > configure: error: could not find a working compiler, see config.log for > > details > > error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.29339 (%build) > > ------------------------------------------------------------------------- > >---------------------------------------------------------------------- > > > > _______________________________________________ > > Kolab-users mailing list > > Kolab-users at kolab.org > > https://kolab.org/mailman/listinfo/kolab-users Thnx Alain, I will give it a try tomorrow Kind regards Rene From steuwer at univention.de Mon Oct 27 07:42:14 2008 From: steuwer at univention.de (Ingo Steuwer) Date: Mon, 27 Oct 2008 07:42:14 +0100 Subject: kolab 2.2 In-Reply-To: <345261.6262.qm@web25901.mail.ukl.yahoo.com> References: <345261.6262.qm@web25901.mail.ukl.yahoo.com> Message-ID: <200810270742.15685.steuwer@univention.de> Hello, Am Freitag, 24. Oktober 2008 schrieb Gabriele Di Giambelardini: > After login imapd take 100% cpu logfiles would really help... Regards Ingo Steuwer > > > ________________________________ > Da: Ingo Steuwer > A: kolab-users at kolab.org > Cc: Gabriele Di Giambelardini > Inviato: Venerd? 24 ottobre 2008, 12:20:22 > Oggetto: Re: kolab 2.2 > > Hello, > > Am Freitag, 24. Oktober 2008 schrieb Gabriele Di Giambelardini: > > Ok after many many tests, the imapd service use all the CPU only when an > > user use the horde webmail.... Any solution?? > > during login or the whole session? Is it connected with a special use-case? > > You might enable user-specific logfiles in cyrus or increase the loglevel > to get an impression of what imapd "does". > > Regards > Ingo Steuwer > > > ________________________________ > > Da: Gabriele Di Giambelardini > > A: Ingo Steuwer ; kolab-users at kolab.org > > Inviato: Venerd? 24 ottobre 2008, 9:17:55 > > Oggetto: Re: kolab 2.2 > > > > > > Thanks, But I don't know the why in my htop I see the imap have a 100% of > > CPU... There is some parameter or something I should do ?? > > thanks > > > > > > > > > > ________________________________ > > Da: Ingo Steuwer > > A: kolab-users at kolab.org > > Cc: Gabriele Di Giambelardini > > Inviato: Venerd? 24 ottobre 2008, 8:34:26 > > Oggetto: Re: kolab 2.2 > > > > Hi, > > > > Am Donnerstag, 23. Oktober 2008 schrieb Gabriele Di Giambelardini: > > > Hi to all, I have a big problem with kolab 2 performance. > > > I have an server with 10 GB of RAM and about 150000 users. > > > > Once they are imported into LDAP and the mail-spools are created, the > > pure amount of users should not be the problem, but the number of current > > users and the number/size of deliviered mails. We installed a kolab-based > > mailserver with ~80000 users (mailaccounts) and Horde webmail on a far > > smaller hardware (one server, 2GB RAM) years ago. > > > > > After I imported the user in the kolab ldap the server become very very > > > slow, it's impossible use a webmail. so I installed the webmail on > > > other server with eaccelerator. But now on my main server the kolab > > > imapd take all the CPU and every thing is too slow. The are some > > > settings for imap of if somebody know the why of this latency... THANKS > > > > We [1] had trouble with cyrus and horde getting slow in large > > installations because of a very inefficient group-ACL-computing of cyrus. > > In some cases it helps to activate "nscd" with large cache sizes (mhm, I > > don't know if nscd is part of a standard Kolab-distributon?), in other > > scenarios we deactivated this in Cyrus' imapd.conf (unix_group_enable: > > no) - which is OK as long as group ACLs are not required. But this might > > also be slightly different in plain Kolab. > > > > You should try to figure out what the imapd really does. Is it during a > > login, mail-delivery, folder-operations etc.; maybe imapd is only waiting > > for something else (Disk I/O, LDAP, ...)? > > > > Regards > > Ingo Steuwer > > > > [1] Please note that we don't use the openpkg-distribution of kolab but a > > derivated installation based on Debian with patches and configurations > > similar to/derived from plain kolab. > > > > > Scopri il blog di Yahoo! Mail: > > > Trucchi, novit? e scrivi la tua opinione. > > > http://www.ymailblogit.com/blog -- Ingo Steuwer Projektmanagement steuwer at univention.de Univention GmbH Linux for your Business fon: +49 421 22 232-43 Mary-Somerville-Str.1 28359 Bremen mob: +49 173 2112971 http://www.univention.de fax: +49 421 22 232-99 From gabriele_d_g at yahoo.it Mon Oct 27 09:33:56 2008 From: gabriele_d_g at yahoo.it (Gabriele Di Giambelardini) Date: Mon, 27 Oct 2008 08:33:56 +0000 (GMT) Subject: kolab 2.2 Message-ID: <535139.11688.qm@web25904.mail.ukl.yahoo.com> Hi, to all The real problem is the cyrus imap use 100% CPU only when we use horde webmail. We try to use a different webmail and everythings work well.. So I suspect is some horde parameter... ________________________________ Da: Alain Spineux A: Gabriele Di Giambelardini Cc: kolab-users at kolab.org Inviato: Domenica 26 ottobre 2008, 18:49:15 Oggetto: Re: kolab 2.2 On Thu, Oct 23, 2008 at 3:30 PM, Gabriele Di Giambelardini wrote: > Hi to all, I have a big problem with kolab 2 performance. > I have an server with 10 GB of RAM and about 150000 users. 150K users is a lot on a single server running all the mail stuff ! Which OS are your running ? Are you using a 64bits OS ? Are your 10GB of RAM all in use ? Maybe this page could give you some hints on how it is difficult to tune a mail server ! http://blog.fastmail.fm/2007/09/21/reiserfs-bugs-32-bit-vs-64-bit-kernels-cache-vs-inode-memory/ Are you using a RAID 5 ? RAID 10 could give you better performances ! > After I imported the user in the kolab ldap the server become very very > slow, it's impossible use a webmail. so I installed the webmail on other > server with eaccelerator. > But now on my main server the kolab imapd take all the CPU and every thing > is too slow. > The are some settings for imap of if somebody know the why of this > latency... > THANKS > > ________________________________ > Scopri il Blog di Yahoo! Mail: trucchi, novit?, consigli... e scrivi la tua > opinione! > _______________________________________________ > 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 Scopri il blog di Yahoo! Mail: Trucchi, novit? e scrivi la tua opinione. http://www.ymailblogit.com/blog -------------- next part -------------- An HTML attachment was scrubbed... URL: http://kolab.org/pipermail/kolab-users/attachments/20081027/d5da2fe4/attachment-0001.html From m.ouderling at linxs.nl Mon Oct 27 10:23:49 2008 From: m.ouderling at linxs.nl (Rene Ouderling) Date: Mon, 27 Oct 2008 10:23:49 +0100 Subject: gmp compilation error on amd64 In-Reply-To: <71fe4e760810261107m79bc310dwf88327ba6e9055e6@mail.gmail.com> References: <200810242203.47892.m.ouderling@linxs.nl> <71fe4e760810261107m79bc310dwf88327ba6e9055e6@mail.gmail.com> Message-ID: <200810271023.50301.m.ouderling@linxs.nl> Op zondag 26 oktober 2008 19:07, schreef Alain Spineux: > On Fri, Oct 24, 2008 at 9:03 PM, Rene Ouderling wrote: > > Again no luck with the installation but now on debian etch. After about > > two hours the compilation process fails at gmp. See the log below. This > > problem is the same as issue 2928 and there is the mentioning of a patch > > which i believe is the same as in a mail from Thomas see the link > > http://kolab.org/pipermail/kolab-commits/2008q3/008490.KHTML > > But could someone tell me how to implement this patch. Can' t find it in > > the wiki > > First install the sources > > # openpkg rpm -i gmp-XXXXX.src.rpm > > then edit the file gmp.spec that shoud be somewhere in /kolab/RPM/SRC/gmp > To match the one described in > http://kolab.org/pipermail/kolab-commits/2008q3/008490.html > > then recompile the package > > # openpkg rpm -bb /kolab/RPM/SRC/gmp/gmp.spec > > The last line of the log shoud give you the full path of the newly > compiled package. > Install it > > # openpkg rpm -Uvh /kolab/RPM/PKG/gmpXXXXX.rpm > > and try to continue the install process > > OR OR OR OR OR > > instead of creating a binary package, create a source package > > # openpkg rpm -bs /kolab/RPM/SRC/gmp/gmp.spec > > and replace the source package by the new one that you will found > somewhere in /kolab/RPM/PKG/gmpXXXXX.src.rpm > > Now you can try to restart the installation process from scratch on a > any 64bits OS. > > Hope this help > > > Kind regards > > > > Rene > > ------------------------------------------------------------------------- > >------------------------------------------------------------ Preparing... > > ################################################## > > pkgconfig > > ################################################## > > > > :::: /tmp/install-kolab.27585.21778.20215.2505/pkgconfig-0.23-20080117.s > > ::::rc.rpm > > > > = 0 :::: > > :::: /tmp/install-kolab.27585.21778.20215.2505/gmp-4.2.2-20080101.src.rp > > ::::m :::: > > > > Installing > > /tmp/install-kolab.27585.21778.20215.2505/gmp-4.2.2-20080101.src.rpm > > Executing(%prep): > > env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e > > /kolab/RPM/TMP/rpm-tmp.95270 + cd /kolab/RPM/TMP > > + cd /kolab/RPM/TMP > > + rm -rf gmp-4.2.2 > > + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/gmp/gmp-4.2.2.tar.gz > > + /kolab/lib/openpkg/tar -xf - > > + STATUS=0 > > + '[' 0 -ne 0 ']' > > + cd gmp-4.2.2 > > + echo 'Patch #0 (gmp.patch):' > > Patch #0 (gmp.patch): > > + /kolab/lib/openpkg/patch -p0 -s -b > > + rm -rf mpn/sparc32 mpn/sparc64 > > + exit 0 > > Executing(%build): > > env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e > > /kolab/RPM/TMP/rpm-tmp.29339 + cd /kolab/RPM/TMP > > + cd gmp-4.2.2 > > + export CC=/kolab/bin/cc > > + CC=/kolab/bin/cc > > + export CFLAGS=-fPIC > > + CFLAGS=-fPIC > > + case "amd64-debian4.0" in > > + ./configure --prefix=/kolab --disable-shared > > checking build system type... pentium2-unknown-linux-gnu > > checking host system type... pentium2-unknown-linux-gnu > > checking for a BSD-compatible install... /usr/bin/install -c > > checking whether build environment is sane... yes > > checking for gawk... no > > checking for mawk... mawk > > checking whether make sets $(MAKE)... yes > > checking whether to enable maintainer-specific portions of Makefiles... > > no checking ABI=32 > > checking whether /kolab/bin/cc is gcc... yes > > checking compiler /kolab/bin/cc -fPIC ... yes > > checking compiler /kolab/bin/cc -fPIC has sizeof(long)==4... no > > configure: error: could not find a working compiler, see config.log for > > details > > error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.29339 (%build) > > ------------------------------------------------------------------------- > >---------------------------------------------------------------------- > > > > _______________________________________________ > > Kolab-users mailing list > > Kolab-users at kolab.org > > https://kolab.org/mailman/listinfo/kolab-users Hi Alain, The patch worked but after applying the patch and continuing with the installation i get the following ; ------------------------------------------------------------------------------------------------ Executing(%build): env -i /kolab/lib/openpkg/bash --norc --noprofile ? --posix -e /kolab/RPM/TMP/rpm-tmp.96725 + cd /kolab/RPM/TMP + cd gmp-4.2.2 + export CC=/kolab/bin/cc + CC=/kolab/bin/cc + export CFLAGS=-fPIC + CFLAGS=-fPIC + case "amd64-debian4.0" in + ./configure --prefix=/kolab --disable-shared checking build system type... pentium2-unknown-linux-gnu checking host system type... pentium2-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking ABI=32 checking whether /kolab/bin/cc is gcc... yes checking compiler /kolab/bin/cc -fPIC ... yes checking compiler /kolab/bin/cc -fPIC has sizeof(long)==4... no configure: error: could not find a working compiler, see config.log ? for details error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.96725 (%build) ---------------------------------------------------------------------------------------------------- The compiler used on debian etch is 4.1, but I don't think that that has anything to do with it or do i need to install another version of gcc?. Do you or anyone has an idea. I really want to get this server up and running. From tomas.andersson at heatex.com Mon Oct 27 10:25:15 2008 From: tomas.andersson at heatex.com (Tomas Andersson) Date: Mon, 27 Oct 2008 10:25:15 +0100 Subject: changing the attachment size of incoming email Message-ID: <001301c93815$eb5896d0$c209c470$@andersson@heatex.com> Hi. How do i change the allowed size of incoming emails. The allowed size is now 10Mb and I would like to change this to 30Mb Mvh / Meilleures salutations / Best regards / MFG, Tomas Andersson IT Administrator Heatex AB Tel.: + 46 410 710 554 Fax : + 46 410 710 529 Mob : + 46 702 772 597 Email : tomas.andersson at heatex.com Internet: www.heatex.com DISCLAIMER: 'The information contained in this email and any attachment is confidential. It is intended only for the named addressee(s). If you are not the named addressee please notify the sender immediately and do not disclose, copy or distribute the contents to any other person other than the intended addressee(s).' -------------- next part -------------- An HTML attachment was scrubbed... URL: http://kolab.org/pipermail/kolab-users/attachments/20081027/e6e5b9bc/attachment.html From bud.golf4 at laposte.net Mon Oct 27 12:40:27 2008 From: bud.golf4 at laposte.net (Bud) Date: Mon, 27 Oct 2008 12:40:27 +0100 Subject: changing the attachment size of incoming email In-Reply-To: <001301c93815$eb5896d0$c209c470$@andersson@heatex.com> References: <001301c93815$eb5896d0$c209c470$@andersson@heatex.com> Message-ID: <4905A8AB.3040609@laposte.net> edit file: /kolab/etc/kolab/templates/main.cf.template change this: # postfix default is 10 240 000 Byte = 10.24 Megabyte, # we use 20 Mebibyte = 20*2^20 Byte message_size_limit = 30971520 then: /kolab/sbin/kolabconf Regards. Tomas Andersson a ?crit : > > Hi. > > How do i change the allowed size of incoming emails. > > The allowed size is now 10Mb and I would like to change this to 30Mb > > > > Mvh / Meilleures salutations / Best regards / MFG, > > > > Tomas Andersson > > IT Administrator > > Heatex AB > > Tel.: + 46 410 710 554 > > Fax : + 46 410 710 529 > > Mob : + 46 702 772 597 > > Email : tomas.andersson at heatex.com > > > > Internet: www.heatex.com > > > > DISCLAIMER: 'The information contained in this email and any > attachment is confidential. It is intended only for the named > addressee(s). If you are not the named addressee please notify the > sender immediately and do not disclose, copy or distribute the > contents to any other person other than the intended addressee(s).' > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Kolab-users mailing list > Kolab-users at kolab.org > https://kolab.org/mailman/listinfo/kolab-users > From wrobel at pardus.de Mon Oct 27 15:36:29 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Mon, 27 Oct 2008 15:36:29 +0100 Subject: automatically re-start LDAP in case of crash In-Reply-To: <1224585028l.31074l.1l@pc104141.koeln.nktcables.com> References: <1224585028l.31074l.1l@pc104141.koeln.nktcables.com> Message-ID: <20081027153629.25472175ur2l162s@webmail.pardus.de> Quoting Albrecht Dre? : > Hi Gunnar: > > Am 21.10.2008 11:52:01 schrieb(en) Gunnar Wrobel: >> I guess you could install monit for the task. I think it was part of >> the Kolab server in former times. At least there is an entry in CVS >> for it. I don't know why it was dropped though. > > Thanks for that hint! > > Maybe I'll write my own script to do that, as Monit looks somewhat > "heavy" for that task. Something like: open a socket connection to > slapd, if it breaks try to re-connect, if that times out, run openpkg > to stop OpenLDAP, issue a db_restore (just to be safe), and again use > openpkg to launch OpenLDAP again. A simple perl script should be > sufficient. What do you think, is that approach correct? Yes, should be okay. > > A fix for OpenLDAP would of course be the preferred solution - again > had a crash with the same symptoms tonight. Do you know how I could > get more debugging info out of slapd to track the issue? You can increase the log level in /kolab/etc/kolab/templates/slapd.conf.template. But I never really liked the LDAP logs. They tend to get quite bloated if you do not know exactly what you are searching for and include a lot of detail in the logs. 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/20081027/3a1bcff3/attachment.bin From wrobel at pardus.de Mon Oct 27 15:41:15 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Mon, 27 Oct 2008 15:41:15 +0100 Subject: Q about Group Accounts In-Reply-To: <1224662546l.3871l.0l@pc104141.koeln.nktcables.com> References: <1224662546l.3871l.0l@pc104141.koeln.nktcables.com> Message-ID: <20081027154115.27982rtmpoj12ku8@webmail.pardus.de> Quoting Albrecht Dre? : > Hi, > > while setting up Kolab in a test environment, I ran into a probably > dumb question for which I cannot find the answer in the docs... > > Is it possible to send mails from the outside world to a group account > (like messages to a normal user, but different from messages to an > internal user)? The reason behind is to have a group like "sales", > which shall receive messages from everywhere, but many people may > subscribe to the imap folders and read/process messages. I think you should create a Kolab user of type "Group account" for that (the standard user management tab in the kolab webadmin). But I'm not 100% certain that I fully understand your question. 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/20081027/53b9edac/attachment.bin From wrobel at pardus.de Mon Oct 27 15:43:00 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Mon, 27 Oct 2008 15:43:00 +0100 Subject: Ldap replication In-Reply-To: <7B91BBC61758DD1183BE000C296D2CA7104990@ct-exchange.wins.lawco.com> References: <7B91BBC61758DD1183BE000C296D2CA7104990@ct-exchange.wins.lawco.com> Message-ID: <20081027154300.56993axrxwhyduw4@webmail.pardus.de> Quoting "Price,Neil" : > > Since we have some developers here.. > > What kind of replication is planned for future versions of Kolab? > Undoubtedly syncrepl support is planned. But what kind? Delta syncrepl > replica? N-way multi-master? I believe this has not yet been decided for Kolab/OpenPKG as we are not yet forced to switch to the newer LDAP versions. It is of course nice to have the native ports testing this already. Cheers, Gunnar > > The debian port already uses delta syncrepl but it takes a lot of tweaking > to get it to work, if at all. > > _______________________________________________ > 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/20081027/d79e1158/attachment.bin From wrobel at pardus.de Mon Oct 27 15:51:03 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Mon, 27 Oct 2008 15:51:03 +0100 Subject: kolab 2.2 In-Reply-To: <535139.11688.qm@web25904.mail.ukl.yahoo.com> References: <535139.11688.qm@web25904.mail.ukl.yahoo.com> Message-ID: <20081027155103.10214fm8br93kz28@webmail.pardus.de> Quoting Gabriele Di Giambelardini : > 10pt;\"> Hi, to all > The real problem is the cyrus imap use 100% CPU only when we use > horde webmail. > We try to use a different webmail and everythings work well.. The Horde version in the current Kolab Server release has not yet been really optimized to high load situations. It is specifically lacking one level of caching that you will only get in the next Kolab Server version. I expect in your case Horde is still listing all IMAP folder *for every page view*. This is extremely inefficient and needed some serious rewrite of the Horde/Kolab storage handling to get solved in a better way. This will be part of Kolab-Server-2.2.1. Even with that version I'd still be very careful with using the Horde groupware features with a Kolab server if you have many users. While Kolab code in Horde has seen some dramatic improvement over the last years I still see many areas where optimizations will be required to make it a very lean client that does not tax the main server too much. Cheers, Gunnar > > So I suspect is some horde parameter... > font-size: 10pt;\"> > 13px;\"> > ------------------------- > DA: Alain Spineux > > A: Gabriele Di > Giambelardini > CC: > kolab-users at kolab.org > INVIATO: Domenica 26 > ottobre 2008, 18:49:15 > OGGETTO: Re: kolab 2.2 > > On Thu, Oct 23, 2008 at 3:30 PM, Gabriele Di Giambelardini > wrote: > > Hi to all, I have a big problem with kolab 2 performance. > > I have an server with 10 GB of RAM and about 150000 users. > > 150K users is a lot on a single server running all the mail stuff ! > Which OS are your running ? > Are you using a 64bits OS ? > Are your 10GB of RAM all in use ? > Maybe this page could give you some hints on how it is difficult to > tune a mail server ! > href=\"http://blog.fastmail.fm/2007/09/21/reiserfs-bugs-32-bit-vs-64-bit-kernels-cache-vs-inode-memory/\">http://blog.fastmail.fm/2007/09/21/reiserfs-bugs-32-bit-vs-64-bit-kernels-cache-vs-inode-memory/ > Are you using a RAID 5 ? RAID 10 could give you better performances > ! > > > > After I imported the user in the kolab ldap the server become > very very > > slow, it's impossible use a webmail. so I installed the > webmail on other > > server with eaccelerator. > > But now on my main server the kolab imapd take all the CPU and > every thing > > is too slow. > > The are some settings for imap of if somebody know the why of > this > > latency... > > THANKS > > > > ________________________________ > > Scopri il Blog di Yahoo! Mail: trucchi, novit?, consigli... e > scrivi la tua > > opinione! > > _______________________________________________ > > Kolab-users mailing list > > Kolab-users at kolab.org[2] > > href=\"https://kolab.org/mailman/listinfo/kolab-users\">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[3] > href=\"https://kolab.org/mailman/listinfo/kolab-users\">https://kolab.org/mailman/listinfo/kolab-users > ------------------------- > Scopri il Blog di Yahoo! Mail[4]: > trucchi, novit?, consigli... e scrivi la tua opinione! -- ______ 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:gabriele_d_g at yahoo.it [2] mailto:Kolab-users at kolab.org [3] mailto:Kolab-users at kolab.org [4] http://us.rd.yahoo.com/mail/it/taglines/yahoo/ymail/SIG=11djrg460/**http%3A%2F%2Fwww.ymailblogit.com%2Fblog%2F ---------------------------------------------------------------- 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/20081027/6c2cd8a5/attachment.bin From wrobel at pardus.de Mon Oct 27 15:54:05 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Mon, 27 Oct 2008 15:54:05 +0100 Subject: Problem with kolabquotawarn In-Reply-To: <200810231751.45071.alessio@skye.it> References: <200810231751.45071.alessio@skye.it> Message-ID: <20081027155405.15204twvfjkpmt4w@webmail.pardus.de> Quoting Alessio Cecchi : > Hi, > > in the syslog of this kolab server i found this: > > Oct 23 17:30:02 mail kolabquotawarn: Warning: Could not > read /kolab/etc/kolab/kolab.conf > Oct 23 17:30:02 mail kolabquotawarn: C Error: One or more required > configuration variables (`bind_dn', `bind_pw', `ldap_uri' and/or `base_dn') > are missing in `kolab.conf' > Oct 23 17:30:02 mail kolabquotawarn: C Error: Unable to bind to DN `' > Oct 23 17:30:02 mail kolabquotawarn: C Error: Unable to find kolab object > `k=kolab,' > Oct 23 17:30:02 mail kolabquotawarn[14826]: fatal: Can't read configuration, > please make sure that kolabquotawarn runs with sufficient privileges > > mail:~# ls -lh /kolab/etc/kolab/kolab.conf > -rw------- 1 kolab-n kolab-n 1009 Mar 25 2008 /kolab/etc/kolab/kolab.conf > > Why in others kolab server the owner of kolab.conf is "kolab" and > not "kolab-n"? That is indeed strange. It should indeed be owned by "kolab" and not by "kolab-n". I think I remember a similar bug report. Is this an installation from scratch or did you upgrade it? If you did upgrade it what was your upgrade path? Cheers, Gunnar > > But kolab is running without, apparantly, problem. How can i fix this error? > > Thanks > -- > Alessio Cecchi is: > @ ILS -> http://www.linux.it/~alessice/ > Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/ > @ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it > @ LOLUG -> neo-Socio http://www.lolug.net > > _______________________________________________ > 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/20081027/7c47950b/attachment-0001.bin From nprice at gibb.co.za Mon Oct 27 20:13:38 2008 From: nprice at gibb.co.za (Neil Price) Date: Mon, 27 Oct 2008 21:13:38 +0200 Subject: Ldap replication In-Reply-To: <20081027154300.56993axrxwhyduw4@webmail.pardus.de> References: <7B91BBC61758DD1183BE000C296D2CA7104990@ct-exchange.wins.lawco.com> <20081027154300.56993axrxwhyduw4@webmail.pardus.de> Message-ID: <490612E2.60401@gibb.co.za> Gunnar Wrobel wrote: >> What kind of replication is planned for future versions of Kolab? >> Undoubtedly syncrepl support is planned. But what kind? Delta syncrepl >> replica? N-way multi-master? >I believe this has not yet been decided for Kolab/OpenPKG as we are >not yet forced to switch to the newer LDAP versions. It is of course >nice to have the native ports testing this already. My vote is for Multi-master. It does not support delta-syncrepl (and is therefore a bit inefficient) but I'm sure it will in the future. For a geographically dispersed implementation, multi-master makes sense. Master-slave has a single point of failure although you could alleviate this by syncing different parts of the tree differently but that would be very difficult to set up in some generalised fashion. Mathieu's Debian port uses a master-slave delta syncrepl although I am still confused by his setup and unable to get it to work. I've paused that until I can rtfm some more and grok openldap better. From ml at radoeka.nl Mon Oct 27 22:37:04 2008 From: ml at radoeka.nl (Richard Bos) Date: Mon, 27 Oct 2008 22:37:04 +0100 Subject: Ldap replication In-Reply-To: <490612E2.60401@gibb.co.za> References: <7B91BBC61758DD1183BE000C296D2CA7104990@ct-exchange.wins.lawco.com> <20081027154300.56993axrxwhyduw4@webmail.pardus.de> <490612E2.60401@gibb.co.za> Message-ID: <200810272237.04758.ml@radoeka.nl> Op Monday 27 October 2008 20:13:38 schreef Neil Price: > ?>I believe this has not yet been decided for Kolab/OpenPKG as we are > ?>not yet forced to switch to the newer LDAP versions. It is of course > ?>nice to have the native ports testing this already. > > My vote is for Multi-master. It does not support delta-syncrepl (and is > therefore a bit inefficient) but I'm sure it will in the future. > > For a geographically dispersed implementation, ?multi-master makes > sense. Master-slave has a single point of failure although you could > alleviate this by syncing different parts of the tree differently but > that would be very difficult to set up in some generalised fashion. > > Mathieu's Debian port uses ?a master-slave delta syncrepl although I am > still confused by his setup and unable to get it to work. I've paused > that until I can rtfm some more and grok openldap better. perhaps that the following kolab issues shine some light on the better: https://www.intevation.de/roundup/kolab/msg17168 keep syncrepl cookie on disk between sessions https://www.intevation.de/roundup/kolab/issue3152 Make syncrepl backend works in refreshAndPersist mode https://www.intevation.de/roundup/kolab/issue3154 Reduce syncrepl overload https://www.intevation.de/roundup/kolab/issue3155 As you can see this open replication mode is very much in development. If your issue is not in the list above, you might as well open an issue for it yourself (don't forget to put mathieu on the assignment list). -- Richard Bos We are borrowing the world of our children, It is not inherited from our parents. From aspineux at gmail.com Tue Oct 28 07:59:38 2008 From: aspineux at gmail.com (Alain Spineux) Date: Tue, 28 Oct 2008 07:59:38 +0100 Subject: gmp compilation error on amd64 In-Reply-To: <200810271023.50301.m.ouderling@linxs.nl> References: <200810242203.47892.m.ouderling@linxs.nl> <71fe4e760810261107m79bc310dwf88327ba6e9055e6@mail.gmail.com> <200810271023.50301.m.ouderling@linxs.nl> Message-ID: <71fe4e760810272359l2994bdf1p18a5105b98e884e7@mail.gmail.com> On Mon, Oct 27, 2008 at 10:23 AM, Rene Ouderling wrote: > Op zondag 26 oktober 2008 19:07, schreef Alain Spineux: >> On Fri, Oct 24, 2008 at 9:03 PM, Rene Ouderling > wrote: >> > Again no luck with the installation but now on debian etch. After about >> > two hours the compilation process fails at gmp. See the log below. This >> > problem is the same as issue 2928 and there is the mentioning of a patch >> > which i believe is the same as in a mail from Thomas see the link >> > http://kolab.org/pipermail/kolab-commits/2008q3/008490.KHTML >> > But could someone tell me how to implement this patch. Can' t find it in >> > the wiki >> >> First install the sources >> >> # openpkg rpm -i gmp-XXXXX.src.rpm >> >> then edit the file gmp.spec that shoud be somewhere in /kolab/RPM/SRC/gmp >> To match the one described in >> http://kolab.org/pipermail/kolab-commits/2008q3/008490.html >> >> then recompile the package >> >> # openpkg rpm -bb /kolab/RPM/SRC/gmp/gmp.spec >> >> The last line of the log shoud give you the full path of the newly >> compiled package. >> Install it >> >> # openpkg rpm -Uvh /kolab/RPM/PKG/gmpXXXXX.rpm >> >> and try to continue the install process >> >> OR OR OR OR OR >> >> instead of creating a binary package, create a source package >> >> # openpkg rpm -bs /kolab/RPM/SRC/gmp/gmp.spec >> >> and replace the source package by the new one that you will found >> somewhere in /kolab/RPM/PKG/gmpXXXXX.src.rpm >> >> Now you can try to restart the installation process from scratch on a >> any 64bits OS. >> >> Hope this help >> >> > Kind regards >> > >> > Rene >> > ------------------------------------------------------------------------- >> >------------------------------------------------------------ Preparing... >> > ################################################## >> > pkgconfig >> > ################################################## >> > >> > :::: /tmp/install-kolab.27585.21778.20215.2505/pkgconfig-0.23-20080117.s >> > ::::rc.rpm >> > >> > = 0 :::: >> > :::: /tmp/install-kolab.27585.21778.20215.2505/gmp-4.2.2-20080101.src.rp >> > ::::m :::: >> > >> > Installing >> > /tmp/install-kolab.27585.21778.20215.2505/gmp-4.2.2-20080101.src.rpm >> > Executing(%prep): >> > env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e >> > /kolab/RPM/TMP/rpm-tmp.95270 + cd /kolab/RPM/TMP >> > + cd /kolab/RPM/TMP >> > + rm -rf gmp-4.2.2 >> > + /kolab/lib/openpkg/gzip -dc /kolab/RPM/SRC/gmp/gmp-4.2.2.tar.gz >> > + /kolab/lib/openpkg/tar -xf - >> > + STATUS=0 >> > + '[' 0 -ne 0 ']' >> > + cd gmp-4.2.2 >> > + echo 'Patch #0 (gmp.patch):' >> > Patch #0 (gmp.patch): >> > + /kolab/lib/openpkg/patch -p0 -s -b >> > + rm -rf mpn/sparc32 mpn/sparc64 >> > + exit 0 >> > Executing(%build): >> > env -i /kolab/lib/openpkg/bash --norc --noprofile --posix -e >> > /kolab/RPM/TMP/rpm-tmp.29339 + cd /kolab/RPM/TMP >> > + cd gmp-4.2.2 >> > + export CC=/kolab/bin/cc >> > + CC=/kolab/bin/cc >> > + export CFLAGS=-fPIC >> > + CFLAGS=-fPIC >> > + case "amd64-debian4.0" in >> > + ./configure --prefix=/kolab --disable-shared >> > checking build system type... pentium2-unknown-linux-gnu >> > checking host system type... pentium2-unknown-linux-gnu >> > checking for a BSD-compatible install... /usr/bin/install -c >> > checking whether build environment is sane... yes >> > checking for gawk... no >> > checking for mawk... mawk >> > checking whether make sets $(MAKE)... yes >> > checking whether to enable maintainer-specific portions of Makefiles... >> > no checking ABI=32 >> > checking whether /kolab/bin/cc is gcc... yes >> > checking compiler /kolab/bin/cc -fPIC ... yes >> > checking compiler /kolab/bin/cc -fPIC has sizeof(long)==4... no >> > configure: error: could not find a working compiler, see config.log for >> > details >> > error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.29339 (%build) >> > ------------------------------------------------------------------------- >> >---------------------------------------------------------------------- >> > >> > _______________________________________________ >> > Kolab-users mailing list >> > Kolab-users at kolab.org >> > https://kolab.org/mailman/listinfo/kolab-users > > Hi Alain, > > The patch worked but after applying the patch and continuing with the > installation i get the following ; > ------------------------------------------------------------------------------------------------ > Executing(%build): env -i /kolab/lib/openpkg/bash --norc --noprofile > --posix -e /kolab/RPM/TMP/rpm-tmp.96725 > + cd /kolab/RPM/TMP > + cd gmp-4.2.2 > + export CC=/kolab/bin/cc > + CC=/kolab/bin/cc > + export CFLAGS=-fPIC > + CFLAGS=-fPIC > + case "amd64-debian4.0" in > + ./configure --prefix=/kolab --disable-shared > checking build system type... pentium2-unknown-linux-gnu > checking host system type... pentium2-unknown-linux-gnu > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... yes > checking whether to enable maintainer-specific portions of Makefiles... no > checking ABI=32 > checking whether /kolab/bin/cc is gcc... yes > checking compiler /kolab/bin/cc -fPIC ... yes > checking compiler /kolab/bin/cc -fPIC has sizeof(long)==4... no > configure: error: could not find a working compiler, see config.log > for details Did you read http://www.intevation.de/roundup/kolab/issue2928 ? > error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.96725 (%build) > ---------------------------------------------------------------------------------------------------- > The compiler used on debian etch is 4.1, but I don't think that that has > anything to do with it or do i need to install another version of gcc?. Do > you or anyone has an idea. I really want to get this server up and running. > > _______________________________________________ > 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 NPrice at gibb.co.za Tue Oct 28 09:58:16 2008 From: NPrice at gibb.co.za (Price,Neil) Date: Tue, 28 Oct 2008 10:58:16 +0200 Subject: Ldap replication Message-ID: <7B91BBC61758DD1183BE000C296D2CA71049C8@ct-exchange.wins.lawco.com> Richard Bos wrote: > As you can see this open replication mode is very much in > development. If your issue is not in the list above, you might as > well open an issue for it yourself (don't forget to put mathieu on > the assignment list). So I see! Impressive stuff, especially from Mathieu. One of my issues is indeed covered. I see I am also mentioned for a small bug I pointed out. Fame at last! Mathieu has given me a lot of pointers so I'm about to give it another go. From mailinglists at vanhlebarsoftware.com Tue Oct 28 13:30:00 2008 From: mailinglists at vanhlebarsoftware.com (Eric A. Bonney) Date: Tue, 28 Oct 2008 08:30:00 -0400 Subject: Can I use Kolab with Exim/Dovecot instead of Cyrus? Message-ID: <200810280830.00695.mailinglists@vanhlebarsoftware.com> I currently have my home mail server setup with Exim4, Dovecot and Horde. I really want to be able to get my my PIM data from my server into Kontact. I have tried using WebDAV but I do not think that Kontact supports that method and all my research has led me to Kolab. I really only want to use Kolab as a backend for my Kontact applications for the family so that we can share calendars and be able to get our own PIM data from our phones to the server and then down to our machines. I am running Kubuntu 8.04 on all the machines in the house, including the server. When I attempted to install Kolab from the repository it wants to remove my installation of Exim4-heavy during the installation process. I know after reading some of the website that Kolab seems to depend on Cyrus, but I was hoping that I might be able to setup Kolab as a backend and still keep my mail server running as it is. Thanks for the help. -Eric From pav5088 at internode.on.net Tue Oct 28 13:55:56 2008 From: pav5088 at internode.on.net (Mark Pavlichuk) Date: Tue, 28 Oct 2008 22:55:56 +1000 Subject: Kolab + GOsa debugging In-Reply-To: <200810271732.30746.pollmeier@gonicus.de> References: <7B91BBC61758DD1183BE000C296D2CA71049A6@ct-exchange.wins.lawco.com> <490564DA.6080300@internode.on.net> <200810271732.30746.pollmeier@gonicus.de> Message-ID: <49070BDC.2060209@internode.on.net> I'm trying to get GOsa (a GUI to manage LDAP based services) to coexist with Kolab. GOsa ships with its own custom kolab2.schema based on v1.22 instead of the v1.27 version that ships with Kolab currently. Slapd won't start... The error message slapd gives is here : http://lists.alioth.debian.org/pipermail/pkg-kolab-devel/2008-October/001829.html There is more relevant info, file contents etc... in the thread following that message. Unfortunately my LDAP skills are weak, and although I think I've tracked the problem to a particular part of the GOsa supplied schema I don't know how to fix things. The latest post in the thread follows (Cajus is the lead GOsa developer) : Cajus Pollmeier wrote: > Am Monday 27 October 2008 07:51:06 schrieb Mark Pavlichuk: > >> Neil Price from the pkg-kolab-devel mailing list has some queries >> about the GOsa kolab2.schema file : >> >> Price,Neil wrote: >> >>>> I did a grep for 1.3.6.1.4.1.19414.3.2.5 and it's part of >>>> kolab2.schema. Fabian Hickert earlier brought my attention >>>> to the fact >>>> that I needed to replace the Kolab provided schema with a >>>> GOsa provided >>>> version. The Kolab provided version contains : >>>> >>>> objectclass ( 1.3.6.1.4.1.19414.3.2.5 >>>> NAME 'kolabGroupOfNames' >>>> DESC 'Kolab group of names (DNs) derived from RFC2256' >>>> SUP groupOfNames STRUCTURAL >>>> MAY ( mail $ >>>> kolabDeleteflag ) ) >>>> >>>> The GOsa provided version is slightly different : >>>> >>>> objectclass ( 1.3.6.1.4.1.19414.3.2.5 >>>> NAME 'kolabGroupOfNames' >>>> DESC 'Kolab group of names (DNs) derived from RFC2256' >>>> SUP top AUXILIARY >>>> MAY ( mail $ >>>> kolabDeleteflag ) ) >>>> >>> Thats does not look right. The Kolab one inherits from groupofnames but >>> the Gosa one inherits nothing. Its also AUXILIARY which means (AFAIK) >>> that it cannot be used in a DIT, its only intended for creating other >>> objectclasses. >>> >>> You are also not supposed to mess with these definitions, they are >>> registered with IANA and are supposedly globally unique. >>> >>> Maybe go back to Fabian and ask him to explain the logic behind the >>> change. >>> > > The modifications are done by reason. The kolab schema doesn't allow bundling > with ordinary group of name objects - which is bad from our point of view. > > Be sure that you include our schema files (kolab + rfc) and your slapd should > start. We're using these for our productive systems - so it works. > > Cajus > -- Mark Pavlichuk Strategic IT ph. (07)47242890 m. 0409 124577 From alejandro at xtech.com.ar Tue Oct 28 14:12:41 2008 From: alejandro at xtech.com.ar (Alejandro Bednarik) Date: Tue, 28 Oct 2008 10:12:41 -0300 (ART) Subject: Kolab + GOsa debugging In-Reply-To: <49070BDC.2060209@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> Message-ID: <34550.200.47.24.7.1225199561.squirrel@webmail.xtech.com.ar> 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 wrote: > I'm trying to get GOsa (a GUI to manage LDAP based services) to > coexist with Kolab. GOsa ships with its own custom kolab2.schema based > on v1.22 instead of the v1.27 version that ships with Kolab currently. > > Slapd won't start... The error message slapd gives is here : > http://lists.alioth.debian.org/pipermail/pkg-kolab-devel/2008-October/001829.html > > There is more relevant info, file contents etc... in the thread > following that message. > > Unfortunately my LDAP skills are weak, and although I think I've > tracked the problem to a particular part of the GOsa supplied schema I > don't know how to fix things. The latest post in the thread follows > (Cajus is the lead GOsa developer) : > > Cajus Pollmeier wrote: >> Am Monday 27 October 2008 07:51:06 schrieb Mark Pavlichuk: >> >>> Neil Price from the pkg-kolab-devel mailing list has some queries >>> about the GOsa kolab2.schema file : >>> >>> Price,Neil wrote: >>> >>>>> I did a grep for 1.3.6.1.4.1.19414.3.2.5 and it's part of >>>>> kolab2.schema. Fabian Hickert earlier brought my attention >>>>> to the fact >>>>> that I needed to replace the Kolab provided schema with a >>>>> GOsa provided >>>>> version. The Kolab provided version contains : >>>>> >>>>> objectclass ( 1.3.6.1.4.1.19414.3.2.5 >>>>> NAME 'kolabGroupOfNames' >>>>> DESC 'Kolab group of names (DNs) derived from RFC2256' >>>>> SUP groupOfNames STRUCTURAL >>>>> MAY ( mail $ >>>>> kolabDeleteflag ) ) >>>>> >>>>> The GOsa provided version is slightly different : >>>>> >>>>> objectclass ( 1.3.6.1.4.1.19414.3.2.5 >>>>> NAME 'kolabGroupOfNames' >>>>> DESC 'Kolab group of names (DNs) derived from RFC2256' >>>>> SUP top AUXILIARY >>>>> MAY ( mail $ >>>>> kolabDeleteflag ) ) >>>>> >>>> Thats does not look right. The Kolab one inherits from groupofnames >>>> but >>>> the Gosa one inherits nothing. Its also AUXILIARY which means (AFAIK) >>>> that it cannot be used in a DIT, its only intended for creating other >>>> objectclasses. >>>> >>>> You are also not supposed to mess with these definitions, they are >>>> registered with IANA and are supposedly globally unique. >>>> >>>> Maybe go back to Fabian and ask him to explain the logic behind the >>>> change. >>>> >> >> The modifications are done by reason. The kolab schema doesn't allow >> bundling >> with ordinary group of name objects - which is bad from our point of >> view. >> >> Be sure that you include our schema files (kolab + rfc) and your slapd >> should >> start. We're using these for our productive systems - so it works. >> >> Cajus >> > -- > Mark Pavlichuk > Strategic IT > ph. (07)47242890 > m. 0409 124577 > > _______________________________________________ > Kolab-users mailing list > Kolab-users at kolab.org > https://kolab.org/mailman/listinfo/kolab-users > -- Alejandro Bednarik XTech - Soluciones Linux para Empresas (011) 5219-0678 alejandro at xtech.com.ar From benoit.mortier at opensides.be Wed Oct 29 09:41:59 2008 From: benoit.mortier at opensides.be (Benoit Mortier) Date: Wed, 29 Oct 2008 09:41:59 +0100 Subject: list of sucessfull implementation Message-ID: <200810290941.59770.benoit.mortier@opensides.be> Hello Everybody, It's very hard to find reference of Kolab installation around the world, and i got asked fairly often about those. I wanted to start a page reference in the wiki but got very few entries. Could everybody send his reference here so we can publish them on the wiki Cheers -- Benoit Mortier CEO OpenSides "logiciels libres pour entreprises" : http://www.opensides.be/ Contributor to Gosa Project : http://gosa-project.org/ Contributeur to Nagios Plugins : http://nagiosplugins.org/ From roland.kaeser at intersoft-networks.ch Wed Oct 29 11:08:42 2008 From: roland.kaeser at intersoft-networks.ch (Roland =?iso-8859-1?q?K=E4ser?=) Date: Wed, 29 Oct 2008 11:08:42 +0100 Subject: Kolab 2.2 and Syncml Message-ID: <200810291108.43053.roland.kaeser@intersoft-networks.ch> Hello I'm running here a Kolab 2.2 version (production) and would like to integrate the new syncml support. Currently I coulnd't find a regarding package. Is there a howto which describes the integration of the syncml support in kolab? Thanks Roland K?ser -- Roland K?ser, Systems Engineer Fulachstr. 197, CH-8200 Schaffhausen Tel.: +41 76 481 37 85, www.intersoft-networks.ch mailto:roland.kaeser at intersoft-networks.ch ---------------------------------------------------------------------------------------------------------------------------------- Diejenigen, die ihre Freiheit zugunsten der Sicherheit aufgeben, werden am Ende keines von beiden haben - und verdienen es auch nicht. (Benjamin Franklin) ---------------------------------------------------------------------------------------------------------------------------------- From albrecht.dress at lios-tech.com Wed Oct 29 14:59:57 2008 From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=) Date: Wed, 29 Oct 2008 14:59:57 +0100 Subject: Toltec & Folder Sharing Message-ID: <1225288797l.18554l.1l@pc-adr2.lios-koeln.de> Hi all, I have a question about Kolab folder sharing. The task is to give a number of users access to a shared account which is named, say, support. So, I first created a Group account with this name within Kolab. Using cyradm, I gave the users who shall be able to access these folders full acl access. When I then open Outlook with the Toltec connector (configured for the personal account), I see folders like "user/support/Junk", etc. I cannot see the Inbox of that account. The folders are arranged in a "flat" structure instead on the usual tree. What I would like to do is - hide these user/something folders from my "Personal Folders"; - instead have a separate tree for the shared stuff; - I do *not* want to access the folders using the user name and password of the shared account, but with the user name and password of the "real" user (this is apparently what is described in the "Proko2 Doc3" document). Any insight about a proper setup would be really appreciated! Thanks in advance, Albrecht. From albrecht.dress at lios-tech.com Wed Oct 29 15:56:33 2008 From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=) Date: Wed, 29 Oct 2008 15:56:33 +0100 Subject: Revisited: Postfix Virtual Alias Domains & Kolab In-Reply-To: <71fe4e760809080229r752ce4ffkcef24f115fb5003e@mail.gmail.com> (from aspineux@gmail.com on Mon Sep 8 11:29:38 2008) Message-ID: <1225292193l.18554l.2l@pc-adr2.lios-koeln.de> Am 08.09.2008 11:29:38 schrieb(en) Alain Spineux: > I wrote this wiki > > https://wiki.kolab.org/index.php/Managing_Domain_aliases > > hope this help Unfortunately, I ran into some problems using your descriptions... In my setup, I have the following e-mail addresses/domains: - some.user at my-company.com <-- this is the "main" account; - some.user at the-server.de <-- Kolab is running on the-server.de, and I want to catch messages from applications which /internally/ send to this address. It shall however also be visible from the external world; - some.user at my.home-provider.com <-- this is the user's private address with an ISP. I first tried the last option on your wiki page, i.e. I had - "query_filter = (&(!(kolabDeleteFlag=*))(|(alias=%u at my-company.com)(mail=%u at my-company.com)(uid=%u)))" in ldapvirtual.cf; - "the-server.de whatever" in virtual. Now, when I try to send a message to some.user at my.home-provider.com, Kolab will accept and redirect it to some.user at my-company.com, which is obviously not what I want. I then switched to the second version, i.e. reverted to the standard query filter in ldapvirtual.cf, and added the "@the-server.de @my-company.com" to virtual. Now mail gets out to the home account, but when I telnet to port 25 of the Kolab postfix, it accepts (as reply to "rcpt to:" commands) messages for some.user at my-company.com, for some.user at the-server.de, and also for some.user at my.home-provider.com! I think the best approach would actually be to use the "better" query filter (as to reject unknown accounts), but how can I first sort out all destination domains which are not mine? Any help from a postfix guru would be welcome! Thanks, Albrecht. From pav5088 at internode.on.net Wed Oct 29 16:01:11 2008 From: pav5088 at internode.on.net (Mark Pavlichuk) Date: Thu, 30 Oct 2008 01:01:11 +1000 Subject: Kolab + GOsa debugging In-Reply-To: <34550.200.47.24.7.1225199561.squirrel@webmail.xtech.com.ar> 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> Message-ID: <49087AB7.9050405@internode.on.net> Your instructions read as if you're not using the GOsa version of the kolab2 schema. Is this correct? I tested this method, and after creating and activating a server I could modify the kolab server settings, but when editing a user and trying to add a mail address there was no mail server selectable. 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 wrobel at pardus.de Thu Oct 30 09:07:05 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Thu, 30 Oct 2008 09:07:05 +0100 Subject: Can I use Kolab with Exim/Dovecot instead of Cyrus? In-Reply-To: <200810280830.00695.mailinglists@vanhlebarsoftware.com> References: <200810280830.00695.mailinglists@vanhlebarsoftware.com> Message-ID: <20081030090705.72024xgpt60gc6dw@webmail.pardus.de> Quoting "Eric A. Bonney" : > I currently have my home mail server setup with Exim4, Dovecot and Horde. I > really want to be able to get my my PIM data from my server into Kontact. I > have tried using WebDAV but I do not think that Kontact supports that method > and all my research has led me to Kolab. > > I really only want to use Kolab as a backend for my Kontact applications for > the family so that we can share calendars and be able to get our own PIM data > from our phones to the server and then down to our machines. > > I am running Kubuntu 8.04 on all the machines in the house, including the > server. When I attempted to install Kolab from the repository it wants to > remove my installation of Exim4-heavy during the installation process. I know > after reading some of the website that Kolab seems to depend on Cyrus, but I > was hoping that I might be able to setup Kolab as a backend and still keep my > mail server running as it is. This is not possible. Kolab provides a well tested system of a dozen or more components that are being configured to work together flawlessly. Of course you can try to use your own components but then you don't need Kolab and build your own type of mail server. This is possible but requires a decent amount of knowledge (which you probably have as your are already running your own mail server). Concerning the connection between Kontact and Dovecot: This is (not yet) possible. Only the Cyrus IMAP server has all the required features for Kolab data storage. This is currently being prepared for dovecot but it is work in progress and I'd only expect this to work in the next year. Cheers, Gunnar > > Thanks for the help. > > -Eric > > _______________________________________________ > 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/20081030/d888d0a0/attachment.bin From wrobel at pardus.de Thu Oct 30 09:32:41 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Thu, 30 Oct 2008 09:32:41 +0100 Subject: Kolab 2.2 and Syncml In-Reply-To: <200810291108.43053.roland.kaeser@intersoft-networks.ch> References: <200810291108.43053.roland.kaeser@intersoft-networks.ch> Message-ID: <20081030093241.614527hc1fe9ck00@webmail.pardus.de> Quoting Roland K?ser : > Hello > > I'm running here a Kolab 2.2 version (production) and would like to integrate > the new syncml support. Currently I coulnd't find a regarding package. Is > there a howto which describes the integration of the syncml support in kolab? > No, there is no howto. It will be part of Kolab-Server-2.2.1 which we are preparing at the moment. Cheers, Gunnar > Thanks > > Roland K?ser > > -- > Roland K?ser, Systems Engineer > Fulachstr. 197, CH-8200 Schaffhausen > Tel.: +41 76 481 37 85, www.intersoft-networks.ch > mailto:roland.kaeser at intersoft-networks.ch > ---------------------------------------------------------------------------------------------------------------------------------- > Diejenigen, die ihre Freiheit zugunsten der Sicherheit aufgeben, > werden am Ende keines von beiden haben - und verdienen es auch nicht. > (Benjamin Franklin) > ---------------------------------------------------------------------------------------------------------------------------------- > > _______________________________________________ > 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/20081030/c547e3d9/attachment.bin From wrobel at pardus.de Thu Oct 30 09:35:59 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Thu, 30 Oct 2008 09:35:59 +0100 Subject: Toltec & Folder Sharing In-Reply-To: <1225288797l.18554l.1l@pc-adr2.lios-koeln.de> References: <1225288797l.18554l.1l@pc-adr2.lios-koeln.de> Message-ID: <20081030093559.19715i6myrwxpq7k@webmail.pardus.de> Quoting Albrecht Dre? : > Hi all, > > I have a question about Kolab folder sharing. The task is to give a > number of users access to a shared account which is named, say, support. > > So, I first created a Group account with this name within Kolab. Using > cyradm, I gave the users who shall be able to access these folders full > acl access. When I then open Outlook with the Toltec connector > (configured for the personal account), I see folders like > "user/support/Junk", etc. I cannot see the Inbox of that account. The > folders are arranged in a "flat" structure instead on the usual tree. > > What I would like to do is > - hide these user/something folders from my "Personal Folders"; > - instead have a separate tree for the shared stuff; > - I do *not* want to access the folders using the user name and > password of the shared account, but with the user name and password of > the "real" user (this is apparently what is described in the "Proko2 > Doc3" document). This is how stuff works in the Kolab web client. So I'd rather contact Toltec support about the possibilities to configure such a layout. Cheers, Gunnar > > Any insight about a proper setup would be really appreciated! > > Thanks in advance, > 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/20081030/875a9b21/attachment-0001.bin From albrecht.dress at lios-tech.com Thu Oct 30 10:17:14 2008 From: albrecht.dress at lios-tech.com (=?UTF-8?q?Albrecht_Dre=C3=9F?=) Date: Thu, 30 Oct 2008 10:17:14 +0100 Subject: Free/busy lists broken - HELP! Message-ID: <1225358234l.3914l.0l@pc-adr2.lios-koeln.de> Hi all, I have a HUGE problem with free/busy lists which unfortunately occurred only after migrating to the new Kolab system... The problem is that I apparently can successfully trigger fb list generation, but reading them always returns an empty list. Here are the details (huge, sorry): Call (as calendar user) "https://kolab.my-server.de/freebusy/trigger/the.user%40my-company.com/Kalender.pfb", which gives the following log entries in /kolab/var/kolab-freebusy/log/freebusy.log: Kolab Free/Busy [debug] [horde] Starting generation of partial free/busy data for folder the.user at my-company.com/Kalender [pid 8740 on line 52 of "/kolab/var/kolab/www/freebusy/pfb.php"] Kolab Free/Busy [debug] [horde] Partial free/busy data of owner the.user at my-company.com on server srv-portal.my-server.de requested by user calendar at my-company.com. [pid 8740 on line 63 of "/kolab/var/kolab/www/freebusy/pfb.php"] Kolab Free/Busy [debug] [horde] Creating free/busy information from 1225321200 to 1230505200 [pid 8740 on line 317 of "/kolab/lib/php/Horde/Kolab/Freebusy.php"] Kolab Free/Busy [debug] [horde] No relevance value found for user/the.user/Kalender [pid 8740 on line 207 of "/kolab/lib/php/Horde/Kolab/Freebusy.php"] Kolab Free/Busy [debug] [horde] ACL for user/the.user/Kalender is a:1:{s:22:"calendar at my-company.com";s:12:"lrswipkxtecd";} [pid 8740 on line 241 of "/kolab/lib/php/Horde/Kolab/Freebusy.php"] Kolab Free/Busy [debug] [horde] No extended ACL value found for user/the.user/Kalender [pid 8740 on line 263 of "/kolab/lib/php/Horde/Kolab/Freebusy.php"] Kolab Free/Busy [debug] [horde] FreeBusyCache::store(file=lios-tech^com/wieland^hill/Kalender, relevance=admins, acl=Array, xacl= calendar at my-company.com) [pid 8740 on line 127 of "/kolab/lib/php/Kolab/Freebusy/Cache.php"] Kolab Free/Busy [debug] [horde] Delivering partial free/busy data (extended=). [pid 8740 on line 120 of "/kolab/var/kolab/www/freebusy/pfb.php"] Kolab Free/Busy [debug] [horde] Partial free/busy generation complete, execution time was 0.16107892990112 seconds. [pid 8740 on line 128 of "/kolab/var/kolab/www/freebusy/pfb.php"] The returned data looks fine: BEGIN:VCALENDAR VERSION:2.0 PRODID:-//proko2//freebusy 1.0//EN METHOD:PUBLISH BEGIN:VFREEBUSY ORGANIZER;cn=The User:MAILTO:the.user at my-company.com DTSTAMP:20081030T090125Z DTSTART:20081029T230000Z DTEND:20081228T230000Z FREEBUSY:20081030T140000Z/20081030T143000Z FREEBUSY:20081030T180000Z/20081030T190000Z FREEBUSY:20081031T090000Z/20081031T103000Z FREEBUSY:20081101T230000Z/20081105T230000Z FREEBUSY:20081111T090000Z/20081111T100000Z FREEBUSY:20081113T090000Z/20081113T163000Z FREEBUSY:20081205T180000Z/20081205T220000Z FREEBUSY:20081219T180000Z/20081219T230000Z END:VFREEBUSY END:VCALENDAR Now I call "https://kolab.my-server.de/freebusy/the.user at my-company.com.ifb", giving the following log data: Kolab Free/Busy [debug] [horde] Starting generation of free/busy data for user the.user at my-company.com [pid 26797 on line 49 of "/kolab/var/kolab/www/freebusy/freebusy.php"] Kolab Free/Busy [debug] [horde] Free/busy data of owner the.user at my-company.com on server srv-portal.my-server.de requested by user . [pid 26797 on line 60 of "/kolab/var/kolab/www/freebusy/freebusy.php"] Kolab Free/Busy [debug] [horde] Free/busy generation complete, execution time was 0.018148899078369 seconds. [pid 26797 on line 96 of "/kolab/var/kolab/www/freebusy/freebusy.php"] but the data returned is BEGIN:VCALENDAR VERSION:2.0 PRODID:-//proko2//freebusy 1.0//EN METHOD:PUBLISH BEGIN:VFREEBUSY ORGANIZER;cn=The User:MAILTO:the.user at my-company.com DTSTAMP:20081030T074609Z URL:http://kolab.my-server.de/freebusy/the.user at my-company.com.ifb COMMENT:This is a dummy vfreebusy that indicates an empty calendar FREEBUSY:19700101T000000Z/19700101T000000Z END:VFREEBUSY END:VCALENDAR Any idea what goes wrong here? The kolab server has a number of DNS aliases (like kolab, srv-kolab, srv-portal, ...), might this be a problem (shouldn't, as Apache replies, right?)? Help - my users are killing me as their calendars don't work! ;-) Thanks for any insight, Albrecht. From devgioiatech at gmail.com Thu Oct 30 12:37:00 2008 From: devgioiatech at gmail.com (Antonio Straziota) Date: Thu, 30 Oct 2008 12:37:00 +0100 Subject: external web client Message-ID: hi all, i'm trying to install horde on a external web server. i'm following the tutorial at http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde. now i'm getting the script external-horde.sh with wget 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 -------------- parte successiva -------------- Un allegato HTML ? stato rimosso... URL: http://kolab.org/pipermail/kolab-users/attachments/20081030/cb568870/attachment.html From devgioiatech at gmail.com Thu Oct 30 12:48:59 2008 From: devgioiatech at gmail.com (Antonio Straziota) Date: Thu, 30 Oct 2008 12:48:59 +0100 Subject: external web client In-Reply-To: References: Message-ID: 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 > hi all, > i'm trying to install horde on a external web server. > > i'm following the tutorial at > http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde. > > now i'm getting the script external-horde.sh with > > wget > 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 > > -------------- parte successiva -------------- Un allegato HTML ? stato rimosso... URL: http://kolab.org/pipermail/kolab-users/attachments/20081030/5ba6c252/attachment.html From alejandro at xtech.com.ar Thu Oct 30 13:26:42 2008 From: alejandro at xtech.com.ar (Alejandro Bednarik) Date: Thu, 30 Oct 2008 09:26:42 -0300 (ART) Subject: external web client In-Reply-To: References: Message-ID: <28713.200.47.24.7.1225369602.squirrel@webmail.xtech.com.ar> 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 > >> hi all, >> i'm trying to install horde on a external web server. >> >> i'm following the tutorial at >> http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde. >> >> now i'm getting the script external-horde.sh with >> >> wget >> 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 > https://kolab.org/mailman/listinfo/kolab-users > -- Alejandro Bednarik XTech - Soluciones Linux para Empresas (011) 5219-0678 alejandro at xtech.com.ar From alejandro at xtech.com.ar Thu Oct 30 13:57:51 2008 From: alejandro at xtech.com.ar (Alejandro Bednarik) Date: Thu, 30 Oct 2008 09:57:51 -0300 (ART) Subject: external web client In-Reply-To: References: <28713.200.47.24.7.1225369602.squirrel@webmail.xtech.com.ar> Message-ID: <50233.200.47.24.7.1225371471.squirrel@webmail.xtech.com.ar> 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 > >> >> 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 >> > >> >> hi all, >> >> i'm trying to install horde on a external web server. >> >> >> >> i'm following the tutorial at >> >> http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde. >> >> >> >> now i'm getting the script external-horde.sh with >> >> >> >> wget >> >> >> 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 >> > https://kolab.org/mailman/listinfo/kolab-users >> > >> >> >> -- >> Alejandro Bednarik >> XTech - Soluciones Linux para Empresas >> (011) 5219-0678 >> alejandro at xtech.com.ar >> >> >> _______________________________________________ >> Kolab-users mailing list >> Kolab-users at kolab.org >> https://kolab.org/mailman/listinfo/kolab-users >> > -- Alejandro Bednarik XTech - Soluciones Linux para Empresas (011) 5219-0678 alejandro at xtech.com.ar From mailinglists at vanhlebarsoftware.com Thu Oct 30 14:04:09 2008 From: mailinglists at vanhlebarsoftware.com (Eric A. Bonney) Date: Thu, 30 Oct 2008 09:04:09 -0400 Subject: Can I use Kolab with Exim/Dovecot instead of Cyrus? In-Reply-To: <20081030090705.72024xgpt60gc6dw@webmail.pardus.de> References: <200810280830.00695.mailinglists@vanhlebarsoftware.com> <20081030090705.72024xgpt60gc6dw@webmail.pardus.de> Message-ID: <200810300904.09704.mailinglists@vanhlebarsoftware.com> On Thursday 30 October 2008 04:07:05 Gunnar Wrobel wrote: > Quoting "Eric A. Bonney" : > > I currently have my home mail server setup with Exim4, Dovecot and Horde. > > I really want to be able to get my my PIM data from my server into > > Kontact. I have tried using WebDAV but I do not think that Kontact > > supports that method and all my research has led me to Kolab. > > > > I really only want to use Kolab as a backend for my Kontact applications > > for the family so that we can share calendars and be able to get our own > > PIM data from our phones to the server and then down to our machines. > > > > I am running Kubuntu 8.04 on all the machines in the house, including the > > server. When I attempted to install Kolab from the repository it wants to > > remove my installation of Exim4-heavy during the installation process. I > > know after reading some of the website that Kolab seems to depend on > > Cyrus, but I was hoping that I might be able to setup Kolab as a backend > > and still keep my mail server running as it is. > > This is not possible. Kolab provides a well tested system of a dozen > or more components that are being configured to work together > flawlessly. Of course you can try to use your own components but then > you don't need Kolab and build your own type of mail server. This is > possible but requires a decent amount of knowledge (which you > probably have as your are already running your own mail server). > I was afraid this might be the answer. :) Oh well I guess I am off to learn about Cyrus and see if I can make a change over to it and how difficult that change might be then.. Thanks for the help though! -Eric From devgioiatech at gmail.com Thu Oct 30 16:31:15 2008 From: devgioiatech at gmail.com (Antonio Straziota) Date: Thu, 30 Oct 2008 16:31:15 +0100 Subject: external web client In-Reply-To: <50233.200.47.24.7.1225371471.squirrel@webmail.xtech.com.ar> References: <28713.200.47.24.7.1225369602.squirrel@webmail.xtech.com.ar> <50233.200.47.24.7.1225371471.squirrel@webmail.xtech.com.ar> Message-ID: Ok, i've installed webmail through a fresh kolab slave installation. only a question... can i stop all other kolab service and keep online only Apache? 2008/10/30 Alejandro Bednarik > > 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 > > > >> > >> 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 > >> > > >> >> hi all, > >> >> i'm trying to install horde on a external web server. > >> >> > >> >> i'm following the tutorial at > >> >> http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde. > >> >> > >> >> now i'm getting the script external-horde.sh with > >> >> > >> >> wget > >> >> > >> > 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 > >> > https://kolab.org/mailman/listinfo/kolab-users > >> > > >> > >> > >> -- > >> Alejandro Bednarik > >> XTech - Soluciones Linux para Empresas > >> (011) 5219-0678 > >> alejandro at xtech.com.ar > >> > >> > >> _______________________________________________ > >> Kolab-users mailing list > >> Kolab-users at kolab.org > >> https://kolab.org/mailman/listinfo/kolab-users > >> > > > > > -- > Alejandro Bednarik > XTech - Soluciones Linux para Empresas > (011) 5219-0678 > alejandro at xtech.com.ar > > > -------------- parte successiva -------------- Un allegato HTML ? stato rimosso... URL: http://kolab.org/pipermail/kolab-users/attachments/20081030/573126bd/attachment.html From devgioiatech at gmail.com Thu Oct 30 16:35:38 2008 From: devgioiatech at gmail.com (Antonio Straziota) Date: Thu, 30 Oct 2008 16:35:38 +0100 Subject: external web client In-Reply-To: References: <28713.200.47.24.7.1225369602.squirrel@webmail.xtech.com.ar> <50233.200.47.24.7.1225371471.squirrel@webmail.xtech.com.ar> Message-ID: another one :D Are users data replicated on kolab slave? just because if i want webmail in DMZ for internet access it's not secure option 2008/10/30 Antonio Straziota > Ok, > i've installed webmail through a fresh kolab slave installation. > > only a question... can i stop all other kolab service and keep online only > Apache? > > > 2008/10/30 Alejandro Bednarik > >> >> 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 >> > >> >> >> >> 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 >> >> > >> >> >> hi all, >> >> >> i'm trying to install horde on a external web server. >> >> >> >> >> >> i'm following the tutorial at >> >> >> http://wiki.kolab.org/index.php/Kolab2_Installation_-_Horde. >> >> >> >> >> >> now i'm getting the script external-horde.sh with >> >> >> >> >> >> wget >> >> >> >> >> >> 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 >> >> > https://kolab.org/mailman/listinfo/kolab-users >> >> > >> >> >> >> >> >> -- >> >> Alejandro Bednarik >> >> XTech - Soluciones Linux para Empresas >> >> (011) 5219-0678 >> >> alejandro at xtech.com.ar >> >> >> >> >> >> _______________________________________________ >> >> Kolab-users mailing list >> >> Kolab-users at kolab.org >> >> https://kolab.org/mailman/listinfo/kolab-users >> >> >> > >> >> >> -- >> Alejandro Bednarik >> XTech - Soluciones Linux para Empresas >> (011) 5219-0678 >> alejandro at xtech.com.ar >> >> >> > -------------- parte successiva -------------- Un allegato HTML ? stato rimosso... URL: http://kolab.org/pipermail/kolab-users/attachments/20081030/3d130945/attachment-0001.html From albrecht.dress at lios-tech.com Thu Oct 30 21:52:32 2008 From: albrecht.dress at lios-tech.com (Albrecht =?iso-8859-1?b?RHJl3w==?=) Date: Thu, 30 Oct 2008 21:52:32 +0100 Subject: Free/busy lists broken - HELP! In-Reply-To: <1225358234l.3914l.0l@pc-adr2.lios-koeln.de> References: <1225358234l.3914l.0l@pc-adr2.lios-koeln.de> Message-ID: <20081030215232.894250gepv9nvssw@portal.lios-koeln.de> Quoting Albrecht Dre? : > Hi all, > > I have a HUGE problem with free/busy lists which unfortunately occurred > only after migrating to the new Kolab system... > > The problem is that I apparently can successfully trigger fb list > generation, but reading them always returns an empty list. Here are > the details (huge, sorry): No idea if this gives further insight into the problem, but... I completely erased the contents of the fb cache folder by calling "rm -rf /kolab/var/kolab-freebusy/cache/*". Then I ran the trigger, which produced aclcache.db (db_dump reports it doesn't contain any data) and xaclcache.db (containing two entries "calendar at my-company.com" and "my-company^com/the^user/Kalender") in the cache folder, plus a folder structure like "my-company^com/the^user", containing three files of which Kalender.pvc contains (afaict) the proper data. When I then run the command to load the ifb, a new file "my-company^com/the^user.vc" is created, containing the empty fb list. This looks like the "transition" from the Kalender files to the vc file is somehow broken... Thanks, Albrecht. From albrecht.dress at lios-tech.com Thu Oct 30 22:00:39 2008 From: albrecht.dress at lios-tech.com (Albrecht =?iso-8859-1?b?RHJl3w==?=) Date: Thu, 30 Oct 2008 22:00:39 +0100 Subject: automatically re-start LDAP in case of crash In-Reply-To: <20081027153629.25472175ur2l162s@webmail.pardus.de> References: <1224585028l.31074l.1l@pc104141.koeln.nktcables.com> <20081027153629.25472175ur2l162s@webmail.pardus.de> Message-ID: <20081030220039.17844o2bq4620dx3@portal.lios-koeln.de> Hi Gunnar, sorry for getting back to you so late, I'm currently figthing desperately with other stuff (fb lists are always empty...). Quoting Gunnar Wrobel : > Yes, should be okay. O.k., I have a very simple script now, which I probably extend a little bit to periodically send a silly query to the server, so slapd will not terminate the connection due to inactivity. Are you interested in it? > You can increase the log level in > /kolab/etc/kolab/templates/slapd.conf.template. Hmm, didn't have any crashes since a week now, although the box went "live" and sees a lot more traffic. I switched off SElinux (usually not a good idea, but I didn't fully succeed with writing the necessary policies) then, btw, maybe this makes a difference? Cheers, Albrecht. From wrobel at pardus.de Fri Oct 31 06:45:01 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Fri, 31 Oct 2008 06:45:01 +0100 Subject: Free/busy lists broken - HELP! In-Reply-To: <1225358234l.3914l.0l@pc-adr2.lios-koeln.de> References: <1225358234l.3914l.0l@pc-adr2.lios-koeln.de> Message-ID: <20081031064501.281239d9a4wgz9kw@webmail.pardus.de> Quoting Albrecht Dre? : > Hi all, > > I have a HUGE problem with free/busy lists which unfortunately occurred > only after migrating to the new Kolab system... > > The problem is that I apparently can successfully trigger fb list > generation, but reading them always returns an empty list. Here are > the details (huge, sorry): > > Call (as calendar user) > "https://kolab.my-server.de/freebusy/trigger/the.user%40my-company.com/Kalender.pfb", > which gives the following log entries in > /kolab/var/kolab-freebusy/log/freebusy.log: > > > Kolab Free/Busy [debug] [horde] Starting generation of partial > free/busy data for folder the.user at my-company.com/Kalender [pid 8740 on > line 52 of "/kolab/var/kolab/www/freebusy/pfb.php"] > Kolab Free/Busy [debug] [horde] Partial free/busy data of owner > the.user at my-company.com on server srv-portal.my-server.de requested by > user calendar at my-company.com. [pid 8740 on line 63 of > "/kolab/var/kolab/www/freebusy/pfb.php"] > Kolab Free/Busy [debug] [horde] Creating free/busy information from > 1225321200 to 1230505200 [pid 8740 on line 317 of > "/kolab/lib/php/Horde/Kolab/Freebusy.php"] > Kolab Free/Busy [debug] [horde] No relevance value found for > user/the.user/Kalender [pid 8740 on line 207 of > "/kolab/lib/php/Horde/Kolab/Freebusy.php"] > Kolab Free/Busy [debug] [horde] ACL for user/the.user/Kalender is > a:1:{s:22:"calendar at my-company.com";s:12:"lrswipkxtecd";} [pid 8740 on > line 241 of "/kolab/lib/php/Horde/Kolab/Freebusy.php"] > Kolab Free/Busy [debug] [horde] No extended ACL value found for > user/the.user/Kalender [pid 8740 on line 263 of > "/kolab/lib/php/Horde/Kolab/Freebusy.php"] > Kolab Free/Busy [debug] [horde] > FreeBusyCache::store(file=lios-tech^com/wieland^hill/Kalender, > relevance=admins, acl=Array, xacl= calendar at my-company.com) [pid 8740 > on line 127 of "/kolab/lib/php/Kolab/Freebusy/Cache.php"] > Kolab Free/Busy [debug] [horde] Delivering partial free/busy data > (extended=). [pid 8740 on line 120 of > "/kolab/var/kolab/www/freebusy/pfb.php"] > Kolab Free/Busy [debug] [horde] Partial free/busy generation complete, > execution time was 0.16107892990112 seconds. [pid 8740 on line 128 of > "/kolab/var/kolab/www/freebusy/pfb.php"] > > > The returned data looks fine: > > > BEGIN:VCALENDAR > VERSION:2.0 > PRODID:-//proko2//freebusy 1.0//EN > METHOD:PUBLISH BEGIN:VFREEBUSY > ORGANIZER;cn=The User:MAILTO:the.user at my-company.com > DTSTAMP:20081030T090125Z > DTSTART:20081029T230000Z > DTEND:20081228T230000Z > FREEBUSY:20081030T140000Z/20081030T143000Z > FREEBUSY:20081030T180000Z/20081030T190000Z > FREEBUSY:20081031T090000Z/20081031T103000Z > FREEBUSY:20081101T230000Z/20081105T230000Z > FREEBUSY:20081111T090000Z/20081111T100000Z > FREEBUSY:20081113T090000Z/20081113T163000Z > FREEBUSY:20081205T180000Z/20081205T220000Z > FREEBUSY:20081219T180000Z/20081219T230000Z > END:VFREEBUSY > END:VCALENDAR > > > Now I call > "https://kolab.my-server.de/freebusy/the.user at my-company.com.ifb", > giving the following log data: > > > Kolab Free/Busy [debug] [horde] Starting generation of free/busy data > for user the.user at my-company.com [pid 26797 on line 49 of > "/kolab/var/kolab/www/freebusy/freebusy.php"] > Kolab Free/Busy [debug] [horde] Free/busy data of owner > the.user at my-company.com on server srv-portal.my-server.de requested by > user . [pid 26797 on line 60 of > "/kolab/var/kolab/www/freebusy/freebusy.php"] > Kolab Free/Busy [debug] [horde] Free/busy generation complete, > execution time was 0.018148899078369 seconds. [pid 26797 on line 96 of > "/kolab/var/kolab/www/freebusy/freebusy.php"] > > > but the data returned is > > > BEGIN:VCALENDAR > VERSION:2.0 > PRODID:-//proko2//freebusy 1.0//EN > METHOD:PUBLISH > BEGIN:VFREEBUSY > ORGANIZER;cn=The User:MAILTO:the.user at my-company.com > DTSTAMP:20081030T074609Z > URL:http://kolab.my-server.de/freebusy/the.user at my-company.com.ifb > COMMENT:This is a dummy vfreebusy that indicates an empty calendar > FREEBUSY:19700101T000000Z/19700101T000000Z > END:VFREEBUSY > END:VCALENDAR > > > Any idea what goes wrong here? I would guess this might be a problem with the folder rights. Which rights does the user retrieving the free/busy data have on the folder in question? We also track some free/busy problems in our tracker. Maybe you are affected by one of these? > The kolab server has a number of DNS > aliases (like kolab, srv-kolab, srv-portal, ...), might this be a > problem (shouldn't, as Apache replies, right?)? No, that should not be a problem. Cheers, Gunnar > > Help - my users are killing me as their calendars don't work! ;-) > > Thanks for any insight, > 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/20081031/8ee1a870/attachment.bin From wrobel at pardus.de Fri Oct 31 06:50:53 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Fri, 31 Oct 2008 06:50:53 +0100 Subject: external web client In-Reply-To: References: <28713.200.47.24.7.1225369602.squirrel@webmail.xtech.com.ar> <50233.200.47.24.7.1225371471.squirrel@webmail.xtech.com.ar> Message-ID: <20081031065053.41847cr9xzxhie0w@webmail.pardus.de> Quoting Antonio Straziota : > 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\"> > 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 > > > > >> > >> 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 > > >> > > >> >> 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. -------------- 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/20081031/d6620868/attachment.bin From wrobel at pardus.de Fri Oct 31 06:53:25 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Fri, 31 Oct 2008 06:53:25 +0100 Subject: external web client In-Reply-To: References: <28713.200.47.24.7.1225369602.squirrel@webmail.xtech.com.ar> <50233.200.47.24.7.1225371471.squirrel@webmail.xtech.com.ar> Message-ID: <20081031065325.12862nt2dmub9jcw@webmail.pardus.de> Quoting Antonio Straziota : > another one :D > Are users data replicated on kolab slave? In general yes, but if you turn openldap off and remove the current data you should be fine. @thomas, bernhard: We might wish to invest some time into providing clearer guidelines for an external Kolab web client setup. Cheers, Gunnar > just because if i want webmail in DMZ for internet access it's not > secure option > 2008/10/30 Antonio Straziota dir=\"ltr\"> > 0pt 0.8ex; padding-left: 1ex;\" class=\"gmail_quote\">Ok, > i've installed webmail through a fresh kolab slave installation. > > only a question... can i stop all other kolab service and keep > online only Apache? 2008/10/30 Alejandro Bednarik dir=\"ltr\">< href=\"mailto:alejandro at xtech.com.ar\">alejandro at xtech.com.ar> > 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 < href=\"mailto:alejandro at xtech.com.ar\">alejandro at xtech.com.ar> > > > >> > >> 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 < href=\"mailto:devgioiatech at gmail.com\">devgioiatech at gmail.com> > >> > > >> >> 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 > >> > href=\"mailto:Kolab-users at kolab.org\">Kolab-users at kolab.org > >> > href=\"https://kolab.org/mailman/listinfo/kolab-users\">https://kolab.org/mailman/listinfo/kolab-users > >> > > >> > >> > >> -- > >> Alejandro Bednarik > >> XTech - Soluciones Linux para Empresas > >> (011) 5219-0678 > >> href=\"mailto:alejandro at xtech.com.ar\">alejandro at xtech.com.ar > >> > >> > >> _______________________________________________ > >> Kolab-users mailing list > >> href=\"mailto:Kolab-users at kolab.org\">Kolab-users at kolab.org > >> href=\"https://kolab.org/mailman/listinfo/kolab-users\">https://kolab.org/mailman/listinfo/kolab-users > >> > > > -- > Alejandro Bednarik > XTech - Soluciones Linux para Empresas > (011) 5219-0678 > href=\"mailto:alejandro at xtech.com.ar\">alejandro at xtech.com.ar > -- ____ 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/20081031/453f6f51/attachment-0001.bin From wrobel at pardus.de Fri Oct 31 06:58:50 2008 From: wrobel at pardus.de (Gunnar Wrobel) Date: Fri, 31 Oct 2008 06:58:50 +0100 Subject: automatically re-start LDAP in case of crash In-Reply-To: <20081030220039.17844o2bq4620dx3@portal.lios-koeln.de> References: <1224585028l.31074l.1l@pc104141.koeln.nktcables.com> <20081027153629.25472175ur2l162s@webmail.pardus.de> <20081030220039.17844o2bq4620dx3@portal.lios-koeln.de> Message-ID: <20081031065850.12514nat1npna46c@webmail.pardus.de> Quoting Albrecht Dre? : > Hi Gunnar, > > sorry for getting back to you so late, I'm currently figthing > desperately with other stuff (fb lists are always empty...). > > Quoting Gunnar Wrobel : >> Yes, should be okay. > > O.k., I have a very simple script now, which I probably extend a > little bit to periodically send a silly query to the server, so slapd > will not terminate the connection due to inactivity. Are you > interested in it? Yes. You could either attach this or directly place it in the wiki (which is what I would do with it). As mentioned we don't have monitoring in the Kolab Server at the moment and I guess we are not going to add it in the near future so it should remain an optional add on which we currently document in the wiki. In principle it would be good to understand why the slapd fails though :) > >> You can increase the log level in >> /kolab/etc/kolab/templates/slapd.conf.template. > > Hmm, didn't have any crashes since a week now, although the box went > "live" and sees a lot more traffic. I switched off SElinux (usually > not a good idea, but I didn't fully succeed with writing the necessary > policies) then, btw, maybe this makes a difference? I don't know much about SElinux. DOes it have loggging and does the LDAP crash coincide with a SElinux event? Cheers, Gunnar > > Cheers, 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/20081031/240c4285/attachment.bin From albrecht.dress at lios-tech.com Fri Oct 31 08:16:05 2008 From: albrecht.dress at lios-tech.com (Albrecht =?iso-8859-1?b?RHJl3w==?=) Date: Fri, 31 Oct 2008 08:16:05 +0100 Subject: Free/busy lists broken - HELP! In-Reply-To: <20081031064501.281239d9a4wgz9kw@webmail.pardus.de> References: <1225358234l.3914l.0l@pc-adr2.lios-koeln.de> <20081031064501.281239d9a4wgz9kw@webmail.pardus.de> Message-ID: <20081031081605.15302gijucixvzxx@kolab.lios-koeln.de> Hi Gunnar! Quoting Gunnar Wrobel : > I would guess this might be a problem with the folder rights. Which > rights does the user retrieving the free/busy data have on the > folder in question? /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? > We also track some free/busy problems in our tracker. Maybe you are > affected by one of these? I tried to scan them, but didn't find anything which "really" fits. The other puzzling thing is that it *did* work in my test setup with a small number of test users. Now, after migrating to a real production environment, it "suddenly" stopped to work. The interesting thing is that the Kalender.pvc (created by the calendar user, but world-readable) file seems to contain the correct data, whereas the *.vc file contains the empty fb list. If I understand the process correctly, both are created by the /kolab/var/kolab/www/freebusy/freebusy.php script, right? Is there a way how I can debug/trace its operation? Thanks, Albrecht. From albrecht.dress at lios-tech.com Fri Oct 31 08:27:17 2008 From: albrecht.dress at lios-tech.com (Albrecht =?iso-8859-1?b?RHJl3w==?=) Date: Fri, 31 Oct 2008 08:27:17 +0100 Subject: automatically re-start LDAP in case of crash In-Reply-To: <20081031065850.12514nat1npna46c@webmail.pardus.de> References: <1224585028l.31074l.1l@pc104141.koeln.nktcables.com> <20081027153629.25472175ur2l162s@webmail.pardus.de> <20081030220039.17844o2bq4620dx3@portal.lios-koeln.de> <20081031065850.12514nat1npna46c@webmail.pardus.de> Message-ID: <20081031082717.22836vr9u34822xh@kolab.lios-koeln.de> Hi Gunnar! Quoting Gunnar Wrobel : > Yes. You could either attach this or directly place it in the wiki > (which is what I would do with it). As mentioned we don't have > monitoring in the Kolab Server at the moment and I guess we are not > going to add it in the near future so it should remain an optional > add on which we currently document in the wiki. Will do that during the weekend (hopefully, if I can resolve the fb bug), stay tuned... > In principle it would be good to understand why the slapd fails though :) I agree! Unfortunately, the openldap mailing list wasn't really helpful - it has a few references to this type of crash, but not a real solution. > I don't know much about SElinux. DOes it have loggging and does the > LDAP crash coincide with a SElinux event? Well, I have only "half" policies for the Kolab stuff, derived from the Ubuntu Hardy reference policies. Basically, my policies put the stuff which lives in a non-standard place (like /kolab/bin instead of /usr/bin) into the right domains, and adds rules for the extra processes. Still unfinished, as I mentioned, though. :-( I had SELinux running in permissive mode, with the dontaudit rules being disabled, and also auditd running. No, there were no SELinux events, but I don't know if the dontaudit rules were /really/ disabled. E.g. during a SELinux training with one of the Gurus (Ralf Spenneberg) we ran into a strange Apache crash on Debian, caused by nscd. It's a truly complicated beast! Cheers, Albrecht. From s.kim at hia.rwth-aachen.de Fri Oct 31 10:41:50 2008 From: s.kim at hia.rwth-aachen.de (Saim Kim) Date: Fri, 31 Oct 2008 10:41:50 +0100 Subject: Free/busy lists broken - HELP! In-Reply-To: <20081030215232.894250gepv9nvssw@portal.lios-koeln.de> References: <1225358234l.3914l.0l@pc-adr2.lios-koeln.de> <20081030215232.894250gepv9nvssw@portal.lios-koeln.de> Message-ID: <490AD2DE.5050705@hia.rwth-aachen.de> Hello Albrecht, Albrecht Dre? schrieb: >
Quoting > Albrecht Dre? : >> Hi all, >> >> I have a HUGE problem with free/busy lists which unfortunately occurred >> only after migrating to the new Kolab system... >> >> The problem is that I apparently can successfully trigger fb list >> generation, but reading them always returns an empty list. Here are >> the details (huge, sorry): you seem to have a similiar problem that I had as well a while ago. Did you check the mailing list history for solutions? > No idea if this gives further insight into the problem, but... > > I completely erased the contents of the fb cache folder by calling "rm > -rf /kolab/var/kolab-freebusy/cache/*". > > Then I ran the trigger, which produced aclcache.db (db_dump reports it > doesn't contain any data) and xaclcache.db (containing two entries > "calendar at my-company.com" and "my-company^com/the^user/Kalender") in > the cache folder, plus a folder structure like > "my-company^com/the^user", containing three files of which > Kalender.pvc contains (afaict) the proper data. > > When I then run the command to load the ifb, a new file > "my-company^com/the^user.vc" is created, containing the empty fb list. > > This looks like the "transition" from the Kalender files to the vc > file is somehow broken... Hm, I think that was the solution for me. Even though I did had problems to start the freebusy generation. One thing was to turn of unauthorized freebusy list access (as stated in the wiki or mailing list posting). The other thing was that a non-exisiting user account IMAP folder stopped the "automatic" regeneration of the freebusy information. That had something to do with delete "[UNSHARED]" folders that are created by the Toltec Connector. Cheers 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 devgioiatech at gmail.com Fri Oct 31 11:24:45 2008 From: devgioiatech at gmail.com (Antonio Straziota) Date: Fri, 31 Oct 2008 11:24:45 +0100 Subject: external web client In-Reply-To: <20081031065053.41847cr9xzxhie0w@webmail.pardus.de> References: <28713.200.47.24.7.1225369602.squirrel@webmail.xtech.com.ar> <50233.200.47.24.7.1225371471.squirrel@webmail.xtech.com.ar> <20081031065053.41847cr9xzxhie0w@webmail.pardus.de> Message-ID: 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 > > Quoting Antonio Straziota : > > 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\"> > >> 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 >> >> >> > >> >> >> >> 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 >> >> >> > >> >> >> 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 > > -------------- parte successiva -------------- Un allegato HTML ? stato rimosso... URL: http://kolab.org/pipermail/kolab-users/attachments/20081031/0bf3cc87/attachment-0001.html From devgioiatech at gmail.com Fri Oct 31 11:56:11 2008 From: devgioiatech at gmail.com (Antonio Straziota) Date: Fri, 31 Oct 2008 11:56:11 +0100 Subject: external web client In-Reply-To: References: <28713.200.47.24.7.1225369602.squirrel@webmail.xtech.com.ar> <50233.200.47.24.7.1225371471.squirrel@webmail.xtech.com.ar> <20081031065053.41847cr9xzxhie0w@webmail.pardus.de> Message-ID: As suggested in the wiki, I also try to remove nss_db library (my system is CENTOS) but nothing changes 2008/10/31 Antonio Straziota > 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 > >> >> Quoting Antonio Straziota : >> >> 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\"> >> >>> 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 >>> >>> >>> > >>> >> >>> >> 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 >>> >>> >> > >>> >> >> 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 >> >> > -------------- parte successiva -------------- Un allegato HTML ? stato rimosso... URL: http://kolab.org/pipermail/kolab-users/attachments/20081031/f6cde341/attachment.html From aspineux at gmail.com Fri Oct 31 16:09:13 2008 From: aspineux at gmail.com (Alain Spineux) Date: Fri, 31 Oct 2008 16:09:13 +0100 Subject: Revisited: Postfix Virtual Alias Domains & Kolab In-Reply-To: <1225292193l.18554l.2l@pc-adr2.lios-koeln.de> References: <71fe4e760809080229r752ce4ffkcef24f115fb5003e@mail.gmail.com> <1225292193l.18554l.2l@pc-adr2.lios-koeln.de> Message-ID: <71fe4e760810310809n2102d94as11da0e38aa752cf1@mail.gmail.com> On Wed, Oct 29, 2008 at 3:56 PM, Albrecht Dre? wrote: > Am 08.09.2008 11:29:38 schrieb(en) Alain Spineux: >> >> I wrote this wiki >> >> https://wiki.kolab.org/index.php/Managing_Domain_aliases >> >> hope this help > > Unfortunately, I ran into some problems using your descriptions... In my > setup, I have the following e-mail addresses/domains: > - some.user at my-company.com <-- this is the "main" account; > - some.user at the-server.de <-- Kolab is running on the-server.de, and I > want to catch messages from applications which /internally/ send to this > address. It shall however also be visible from the external world; > - some.user at my.home-provider.com <-- this is the user's private address with > an ISP. > > I first tried the last option on your wiki page, i.e. I had > > - "query_filter = > (&(!(kolabDeleteFlag=*))(|(alias=%u at my-company.com)(mail=%u at my-company.com)(uid=%u)))" > in ldapvirtual.cf; > - "the-server.de whatever" in virtual. > > Now, when I try to send a message to some.user at my.home-provider.com, Kolab > will accept and redirect it to some.user at my-company.com, which is obviously > not what I want. MY MISTAKE !!! and more seriously if you try to send to some.user at gmail.com it will be redirected to some.user at my-company.com ! In fact any address in the form some.user@ will be redirected to some.user at my-company.com if some.user at my-company.com is a valid local address !!! To correct this we have to add a condition about the domain, something like (|(foobar.de=%d)(foobar.net=%d)) but this is not valid LDAP filter anymore ! Then we have to forget this solution, I will remove it from the WIKI > > I then switched to the second version, i.e. reverted to the standard query > filter in ldapvirtual.cf, and added the "@the-server.de @my-company.com" to > virtual. Now mail gets out to the home account, but when I telnet to port > 25 of the Kolab postfix, it accepts (as reply to "rcpt to:" commands) > messages for some.user at my-company.com, for some.user at the-server.de, and also > for some.user at my.home-provider.com! Then my.home-provider.com should be defined somewhere in ldap or virtual, or maybe hard coded in main.cf ! Just remove it ! > > I think the best approach would actually be to use the "better" query filter > (as to reject unknown accounts), but how can I first sort out all > destination domains which are not mine? Any help from a postfix guru would > be welcome! > > Thanks, Albrecht. > The normal way, is to add the domain, and create any required aliases one by one. -- Alain Spineux aspineux gmail com May the sources be with you From aspineux at gmail.com Fri Oct 31 16:28:13 2008 From: aspineux at gmail.com (Alain Spineux) Date: Fri, 31 Oct 2008 16:28:13 +0100 Subject: Kolab + GOsa debugging In-Reply-To: <49087AB7.9050405@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> <49087AB7.9050405@internode.on.net> Message-ID: <71fe4e760810310828h2a03a9a4hdafd808380d1166f@mail.gmail.com> On Wed, Oct 29, 2008 at 4:01 PM, Mark Pavlichuk wrote: > Your instructions read as if you're not using the GOsa version of the > kolab2 schema. Is this correct? > > I tested this method, and after creating and activating a server I > could modify the kolab server settings, but when editing a user and > trying to add a mail address there was no mail server selectable. 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 ? > > > 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 > > > _______________________________________________ > 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 santoshmahale at gmail.com Wed Oct 1 09:18:50 2008 From: santoshmahale at gmail.com (Santosh Mahale) Date: Wed, 01 Oct 2008 07:18:50 -0000 Subject: Kolab commercial support Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://kolab.org/pipermail/kolab-users/attachments/20081001/3158eab8/attachment.html From rbos at opensuse.org Wed Oct 1 11:12:55 2008 From: rbos at opensuse.org (Richard Bos) Date: Wed, 01 Oct 2008 09:12:55 -0000 Subject: Kolabd crashes after deleting user In-Reply-To: <48E33253.8080403@blinkenlichten.de> References: <1222768494.6804.33.camel@campocampo> <200809301307.14217.ml@radoeka.nl> <48E23982.7050200@blinkenlichten.de> <200809302338.17403.ml@radoeka.nl> <48E33253.8080403@blinkenlichten.de> Message-ID: <20081001091252.GA82949@xs4all.nl> On Wed, Oct 01, 2008 at 10:18:27AM +0200, Rouven Sacha wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Richard Bos schrieb: > > >> installing libnet-ldap-perl from debian unstable (0.38-1) as recommended > >> doesn't help either, kolabd now crashes immediately on startup, just as > >> you encountered it. > > > Hmm, interesting ;) What version did you use before? Can you make a diff > > between the 2? I used 0.37 up till now. However, 0.38 provides 2 bug fixes: > > - From which of the 40 perl modules in libnet-ldap-perl should i make a > diff of? > > > bserver-netsrv:~# dpkg -L libnet-ldap-perl|grep .pm$|wc -l all :) As I don't know which one changed. Is it possible to have the old installed in some temp directory? With rpm this is possible like this: rpm2cpio | cpio -id If the same is possible for deb pkgs (which I assume it is), you can than run a tool like: find -name "*.pm" | while read M; do echo === $M === diff -u /$M $M done Redirect the diff to a diff. Hopefully it is not too big, so it is clear what has changed... I'm afraid however, that it is a big diff as the 0.37 release added the syncrepl support to perl-ldap..... BUT perhaps is not needed, see issue: https://www.intevation.de/roundup/kolab/issue1755 https://www.intevation.de/roundup/kolab/msg16878 Perhaps that is the real (temporarely) solution? -- Richard From quintin at sita.fs.gov.za Thu Oct 30 10:16:22 2008 From: quintin at sita.fs.gov.za (Quintin Terblanche) Date: Thu, 30 Oct 2008 11:16:22 +0200 Subject: eGroupware/Kolab2/Outlook/Kontact Message-ID: <49097B66.9040502@sita.fs.gov.za> Sorry if this is not mend for you, I have a problem syncing outlook with egroupware, but only the group calendars and group contacts, it doesnt show on my outlook but is on the egroupware user website.. if you can help me, please let me know before I go in to much detail and waist your time. Quintin Terblanche -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.