Hello > Gunnar, > > Gunnar Wrobel schrieb: >> Quoting Saim Kim : >> >>> Hello, >>> >>> after succesfully importing the LDAP backup from the old server with >>> your help, I'm now struggeling with the import of the annotations.db >>> file. I checked the mailing list and found several remarks on how to >>> backup the file and the possibilty on just copying the file from a >>> backup. Unfortunatly, the copying didn't do as hoped. After copying I >>> ran the cyrreconstruct as kolab-r. That didn't change anything -the >>> calendars were still not visible. >> >> The cyrreconstruct does not have anything to do with the annotations >> as far as I know. I believe it just fixes problems with the messages >> in the mail folder. The annotations.db file is actually the only >> place where information about annotations are kept. So the only task >> should be to get that file restored as required. > ok, that's good to know. I tried to do it another way: I delete the > content of the /kolab/var/imapd. I then did a rsync with the imap > content from my backup. I then checked with the cyradm info command > and this is the result: > > Original server: > > localhost> info user/test/Kalender at medit.intern > {user/test/Kalender at medit.intern}: > comment: > condstore: false > duplicatedeliver: false > lastpop: > lastupdate: 14-Jul-2009 15:25:59 +0200 > partition: default > sharedseen: false > size: 6225112 > share-params: > YToyOntzOjY6InNvdXJjZSI7czo1OiJrb2xhYiI7czo0OiJuYW1lIjtzOjg6IkthbGVuZGVyIjt9 > > folder-type: event.default > incidences-for: readers > xfb-readable: test at medit.intern test3 at medit.intern > > > New server: > > localhost> info user/test/Kalender at medit.intern > {user/test/Kalender at medit.intern}: > comment: t/plain > condstore: false > duplicatedeliver: false > lastpop: > lastupdate: 3-Jul-2009 15:40:24 +0200 > partition: default > sharedseen: false > size: 6175303 > share-params: > OntzOjY6InNvdXJjZSI7czo1OiJrb2xhYiI7czo0OiJuYW1lIjtzOjg6IkthbGVuZGVyIjt9 > folder-type: t.default > incidences-for: ers > xfb-readable: t at medit.intern test3 at medit.intern > > Interestingly, some of the critical parts are truncated? -> > folder-type, etc. Any on how to prevent this? I guess this could be > one solution to my IMAP problem... >>> A manual typesetting to event with the >>> mboxcfg successfully restored a user calendar. For about 30+ users this >>> would be cumbersome... >> >> In the worst case you could script that step. > hmm, as a complete linux noobie this would be really time consuming... >>> >>> I tried to export the annotations.db to skiplist format using the >>> cvt_cyrusdb on the source machine and convert it on the destination >>> machine back to berkeley format. Then I would run the cyrreconstruct >>> command as kolab-r. All the mailboxes are listed but if I check them >>> with "info" from the cyradm interface the kolab specific annotations >>> are >>> missing. >> >> Can you try to dump the database contents to text format using: >> >> /kolab/bin/db_dump /kolab/var/imapd/annotations.db > >> annotations_db_backup.txt > > I made a db dump as suggested but when I look into the text file it > only contains the following information: > VERSION=3 > format=bytevalue > type=btree > db_pagesize=4096 > HEADER=END > 6d656469742e696e7465726e217368617265645e61647265737362756368002f76656e646f722f6b6f6c61622f666f6c6465722d747970650000 > > > Lots of more numbers here... I guess the dump was successfull. > >>> So, in essence: Is there a recommanded way of recovering the >>> annotations.db like the mailbox.db? I tried to convert to flat format >>> and then back to berkeley format but I would get an error message: >>> "Converting from /kolab/var/imapd/annotations.db (berkeley) to >>> /tmp/annotest.test (flat) Warning: apparently empty database >>> converted." >> >> Hm, does not sound too good. > So, after I dumped the annotations.db from the original maschine, how > can I get it back into berkeley format? I tried to use > /kolab/bin/cvt_cyrusdb /tmp/annotations.db.txt flat > /tmp/annotations.db berkeley. Even though I get the same warning as > before ("Warning: apparently empty database converted"), I get a > resulting annotations.db file which is much smaller than before (8 kB > compared to 229 kB)? And converting it back to flat format results in > a 0 kB file? > > > > > > Ok, so the usual way would be recover the data from backup and just > copying the annotations.db file to its original location and > everything should work, right? Is that also correct for a version > change (from 2.2 to 2.2.2)? > > 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 steuwer at univention.de Thu Jul 23 09:31:44 2009 From: steuwer at univention.de (Ingo Steuwer) Date: Thu, 23 Jul 2009 09:31:44 +0200 Subject: Question about **SHUDDER** Microsoft Outlook and Entourage In-Reply-To: <4A67C2B4.50206@gmail.com> References: <4A67C2B4.50206@gmail.com> Message-ID: <200907230931.46230.steuwer@univention.de> Hi, Am Donnerstag, 23. Juli 2009 schrieb Joseph Hardeman: > Hey Guys, > > I was curious if anyone has tried or been able to "Fake" Outlook and > Entourage into thinking that Kolab is an Exchange Server so that the > users can share and delegate Calendars and stuff. I have been looking > at a lot of different servers over the last several months when I got a > chance, including Kerio and Zimbra, which allows this to be done (Zimbra > with their iCal plugin which only comes with a paid version of Zimbra), > but I was hoping to find an open source option verse having to pay for > one or **SHUDDER** having to pay for an Exchange server and possibly AD > servers. all stable OSS groupware solutions I know use connectors/plugins for Outlook. For Kolab there are three connectors I know of: Toltec, Konsec and Bynari; all three are closed source with a small per-client license-fee. > Or if anyone can point me to an open source mail server solution to do > this it would be great too. I think openchange is what you are looking for, but AFAIK the projekt is far from stable: http://www.openchange.org/ Regards Ingo Steuwer > Anyway, thanks for any advice or help. And if I am asking on the wrong > list and I should be asking on the Horde list let me know. > > Thanks > > Joe -- Ingo Steuwer Head of Professional Services Univention GmbH Linux for your business Mary-Somerville-Str.1 28359 Bremen Tel.: +49 421 22232-43 Fax : +49 421 22232-99 Mob : +49 173 2112971 steuwer at univention.de> http://www.univention.de Gesch?ftsf?hrer: Peter H. Ganten HRB 20755 Amtsgericht Bremen Steuer-Nr.: 71-597-02876 From NPrice at gibb.co.za Thu Jul 23 11:57:37 2009 From: NPrice at gibb.co.za (Price,Neil) Date: Thu, 23 Jul 2009 11:57:37 +0200 Subject: Question about **SHUDDER** Microsoft Outlook and Entourage Message-ID: <7B91BBC61758DD1183BE000C296D2CA71A2F3B@ct-exchange.wins.lawco.com> > I think openchange is what you are looking for, but AFAIK the > projekt is far > from stable: > http://www.openchange.org/ Openchange is impressive but I tried it and you are correct, it is unstable. I could crash it at will. It requires Samba 4 which is still in alpha. But with the release of M$ MAPI docs, it is making rapid progress. Heres an idea. Openchange allows for a custom back-end server plugin. You could write the plugin to connect to a Kolab server and make it look like M Sexchange to Outlook but still have the advantage of other clients, stability and customization. As an aside, the release of MS protocol docs (thanks to EU) have had unexpected benefits for MS as the Samba and Openchange teams have pointed out several bugs to them. From bernhard at intevation.de Thu Jul 23 17:13:38 2009 From: bernhard at intevation.de (Bernhard Reiter) Date: Thu, 23 Jul 2009 17:13:38 +0200 Subject: Use a different Host to store Imap Data on In-Reply-To: <200907222304.27997.webmaster@computational-chemistry.org> References: <200907222304.27997.webmaster@computational-chemistry.org> Message-ID: <200907231713.38712.bernhard@intevation.de> Am Mittwoch, 22. Juli 2009 23:04:27 schrieb Alexander Schr?ter: > a little bit about my situation. I currently use a Kolab Server and my ISPs > Mailserver. Since my ISPs Mailserver has a nearly 100% Uptime, a lot of > Storage Space and Automated Backup. I want to use it as storage space for > the kolab's imap data. > > The problem is that I only have access to my ISPs Server via Imap. So my > question is: > > Is it possible to tell kolab/cyrus to store the mail not on the local > machine but on my ISPs Imap account. I haven't heard about such a feature in cyrus imapd. Cyrus imapd usually wants to store stuff in a (posix compatible, full blown) filesystem. You could try to go crazy in trying to map that filesystem via the net somehow for backup purposes, but this does not sound like a good idea. Cyrus really uses the filesystem and thus even does not like network filesystem for this reason. I might be easier to just rent server space and run Kolab Server there to get the benefits of uptime and backup service. > I saw that it's possible to introduce a new partition to cyrus in the > imapd.conf and than tell the process to use this as new storage location > for certain users via "renamemailbox user.foobar.mail user.foobar.mail > newpartition". Sounds like a feature to use another file system partition, which would not help you further along. -- Managing Director - Owner: www.intevation.net (Free Software Company) Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com. Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://kolab.org/pipermail/kolab-users/attachments/20090723/a5fe7183/attachment.bin From bernhard at intevation.de Thu Jul 23 17:39:53 2009 From: bernhard at intevation.de (Bernhard Reiter) Date: Thu, 23 Jul 2009 17:39:53 +0200 Subject: BUG in Horde? In-Reply-To: <4A671E7A.3070306@oab.de> References: <4A671E7A.3070306@oab.de> Message-ID: <200907231739.57579.bernhard@intevation.de> Hi, Am Mittwoch, 22. Juli 2009 16:13:14 schrieb Alexander Marx: > Kann es sein, dass die Horde Version vom Kolab 2.2.2 einen Bug hat?
> is there a bug within kronolith of kolab 2.2.2??
yes, it is possible that Kolab's webclient has defects. (BTW there is a German speaking mailinglist.) > if i set "germany" in the configuration of the public holidays, the
> calendar seems to be broken, only a white site appears.
> if i set it back to "discordian" the calendar shows up again.
Known problem, claimed to be fixed in CVS, but untested. Bernhard -- Managing Director - Owner: www.intevation.net (Free Software Company) Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com. Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://kolab.org/pipermail/kolab-users/attachments/20090723/1cd6d6ce/attachment.bin From bernhard at intevation.de Fri Jul 24 08:41:05 2009 From: bernhard at intevation.de (Bernhard Reiter) Date: Fri, 24 Jul 2009 08:41:05 +0200 Subject: BUG in Horde? In-Reply-To: <200907231739.57579.bernhard@intevation.de> References: <4A671E7A.3070306@oab.de> <200907231739.57579.bernhard@intevation.de> Message-ID: <200907240841.09702.bernhard@intevation.de> Alexander, (I am answering here, please post followup questions on the list and please without HTML.) Am Donnerstag, 23. Juli 2009 17:39:53 schrieb Bernhard Reiter: > > if i set "germany" in the configuration of the public holidays, the
> > calendar seems to be broken, only a white site appears.
> > if i set it back to "discordian" the calendar shows up again.
> > Known problem, claimed to be fixed in CVS, but untested. To know where the change has been made, best is to check the issue tracker or ask on the kolab-devel@ list. The location in CVS is: http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolab-webclient/ChangeLog?rev=1.19&content-type=text/vnd.viewcvs-markup 2009-07-11 Gunnar Wrobel

* kolab-webclient.spec: kolab/issue1623 ([horde/horde-kronolith] Add support for Date_Holidays) kolab/issue3509 (calender not displaying in horde if german holidays are selected) -- Managing Director - Owner: www.intevation.net (Free Software Company) Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com. Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://kolab.org/pipermail/kolab-users/attachments/20090724/86aa559b/attachment.bin From bernhard at intevation.de Fri Jul 24 08:54:50 2009 From: bernhard at intevation.de (Bernhard Reiter) Date: Fri, 24 Jul 2009 08:54:50 +0200 Subject: Installation (Version 20090515, Kolab Server 2.2.2) fails for fedora 11 (procmail) In-Reply-To: <98d946fb0907220509m55d48f47y8e4f49230a1859ba@mail.gmail.com> References: <98d946fb0907220509m55d48f47y8e4f49230a1859ba@mail.gmail.com> Message-ID: <200907240854.54633.bernhard@intevation.de> Am Mittwoch, 22. Juli 2009 14:09:10 schrieb Sasha Kacanski: > I pulled complete repository of source rpm's from > http://files.kolab.org/server/release/kolab-server-2.2.2/sources/ and > executed according to 1st.README > # sh install-kolab.sh 2>&1 | tee /cube/kolab-install/kolab-install.log > Installation fails: > > /kolab/bin/cc -c -fPIC formail.c > In file included from formail.c:25: > formisc.h:20: error: conflicting types for 'getline' > /usr/include/stdio.h:655: error: previous declaration of 'getline' was here > make[1]: *** [formail.o] Error 1 > make: *** [bins] Error 2 > error: Bad exit status from /kolab/RPM/TMP/rpm-tmp.59346 (%build) I would try moving away /usr/include/stdio.h during the initial build. (And then move it back of course.) > I researched via google some of the issues with declaration of > getline, and suggestions range from upgrading procmail to > procmail-3.22-24.fc12 from existing procmail-3.22-23.fc11.src.rpm. > Regardless of upgrade of removal of exisitng instance of procmail I > still get error with existing source supplied with kolab. Your system procmail is not the one failing, but the procmail coming with OpenPKG. So changing the system procmail does not help. :) (I just wonder if we could not get rid of the procmail dependency, but it seems that the postfix package from OpenPKG currently has it.) > According to one of more complete posts on thsi issue on getline call: > ....It is not related to gcc in any way, just the default when you don't > select any feature test macros (see > info libc 'Feature Test Macros' > ) changed in F11 from F10, now you get by default _POSIX_C_SOURCE 200809L > stuff, before you got _POSIX_C_SOURCE 200112L. POSIX 2008 newly contains > many GNU functions, like getline, fexecve, etc. > So, either fix up the packages to use different names of local functions > (preferrable), or use some Feature Test Macro to pick whatever the program > expects to be compiled with. > .... > > My question would be do I try to upgrade source src for procmail under > kolab with procmail package that has fix That sounds like a good idea, you should approach the openPKG developers and check with kolab-devel@ about it. > I am not big on fedora, and gentoo installation of kolab server 2.1 > worked but that was not a smooth sailing either. > I would like to follow openpkg format for ease of future maintenance. Yes, the Kolab Server/OpenPKG format usually is the easiest to use. Bernhard -- Managing Director - Owner: www.intevation.net (Free Software Company) Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com. Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://kolab.org/pipermail/kolab-users/attachments/20090724/868dd7e5/attachment.bin From bernhard at intevation.de Fri Jul 24 08:56:55 2009 From: bernhard at intevation.de (Bernhard Reiter) Date: Fri, 24 Jul 2009 08:56:55 +0200 Subject: libltdl.so.7 - not present in openpkg installation In-Reply-To: References: Message-ID: <200907240856.56156.bernhard@intevation.de> Am Dienstag, 21. Juli 2009 21:26:46 schrieb Johannes Graumann: > I managed to get my kolab installation back up and running on a spanking > new hosted virtual server, but upon "/etc/init.d/kolab start" (this is > debian), > > I ran into the following problem: > > apache:FAILED > > openpkg:rc:WARNING: /kolab:apache:%start: failed with return code 1 ? ? ? > > ? ? openpkg:rc:NOTICE: output from stdout/stderr is following: > > +---------------------------------------------------------------------- > > > > | apache: Syntax error on line 341 of /kolab/etc/apache/apache.conf: > > | Cannot load /kolab/libexec/apache/mod_php.so into server: > > | libltdl.so.7: cannot open shared object file: No such file or > > | directory ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? > > | ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? > > > > +---------------------------------------------------------------------- > > This was easily fixed by installing libltdl from the hosting distribution, > but has me kind of confused: isn't the whole point of providing kolab in an > openpkg environment to make it self-sufficient (aside from early build > requirements)? Yes, this is the idea. So something went wrong (I do know what of course). ,) > "find -iname libltdl.so.7" really did not dig anything up in > my original installation either ... -- Managing Director - Owner: www.intevation.net (Free Software Company) Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com. Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://kolab.org/pipermail/kolab-users/attachments/20090724/717bad07/attachment.bin From bernhard at intevation.de Fri Jul 24 09:05:35 2009 From: bernhard at intevation.de (Bernhard Reiter) Date: Fri, 24 Jul 2009 09:05:35 +0200 Subject: Funambol Connectivity In-Reply-To: <4A6443CD.5080204@oab.de> References: <4A6443CD.5080204@oab.de> Message-ID: <200907240905.36327.bernhard@intevation.de> Hi Alexander, please do not post in HTML, some people will ignore such emails and it is harder to read and quote for me as well. > PART2:
> Now, a fresh install of Kolab 2.2.2.
> I was VERY VERY happy about the new Webinterface (Horde) and with
> Thunderbird, all things seem to work perfect. (Calendar, invitations
> and so on)
> I saw the SYNCML Option and wanted to try this one out. But without
> success.
>
> I have a mobile phone Soy ericsson xperia x1 (windows mobile, with
> syncml support). native syncml doesn&apst work. so i decided to install
> the funambolclient on my phone.
> I entered the data href="https://kolab.domain.tld/client/rpc.php">https://kolab.domain.tld/cli >ent/rpc.php??? and
username and password as on the kolab server.
> The funambolclient tries to connect, then says:
> "cannot connect to server"
Sounds like the right values. > Is there a possibility to use the funambolclient with Kolab2-syncml???
I don't know, there should be I guess, but there are lots of SyncML clients. There is a wiki page, if people would want to write down their experiences: http://wiki.kolab.org/index.php/Web_Client_SyncML > Is it possible to install a funambol server, configure it so that the
> funambolserver gets all Kolab-data and then connect a mobile phone
> with funambolserver?
Not without a funambol <-> Kolab Server Connector. I've heard there is one in development. Best, Bernhard -- Managing Director - Owner: www.intevation.net (Free Software Company) Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com. Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://kolab.org/pipermail/kolab-users/attachments/20090724/0743d29a/attachment.bin From marx at oab.de Fri Jul 24 09:45:19 2009 From: marx at oab.de (Alexander Marx) Date: Fri, 24 Jul 2009 09:45:19 +0200 Subject: Upgrade Message-ID: <4A69668F.50100@oab.de> Hi List. First of all thanks for the quick replies to the dumb questions. :-) Bernhard, as i wrote lately, there's a bug in Horde webadmin with the holidays. I read the cvs notes and found that under http://ftp.gwdg.de/pub/linux/kolab/server/development-2.2/20090515-since-20090407/sources/ there are new src RPM's the kolab-webadmin package is dated from may 2009. now i want to install the release version 2.2.2 and then make a upgrade with these packages. Do you think that the relevant changes are made in the listed path? Can i just copy the srpm's to my installation and do a standard upgrade as decribed in the 1st.README? Alexander Marx* Fachinformatiker Systemintegration ACE (Astaro certified engineer) LPIC (101) From thomas at intevation.de Fri Jul 24 11:11:19 2009 From: thomas at intevation.de (Thomas Arendsen Hein) Date: Fri, 24 Jul 2009 11:11:19 +0200 Subject: Upgrade In-Reply-To: <4A69668F.50100@oab.de> References: <4A69668F.50100@oab.de> Message-ID: <20090724091119.GA3140.thomas@intevation.de> * Alexander Marx [20090724 09:45]: > Bernhard, as i wrote lately, there's a bug in Horde webadmin with the > holidays. > I read the cvs notes and found that under > http://ftp.gwdg.de/pub/linux/kolab/server/development-2.2/20090515-since-20090407/sources/ > > there are new src RPM's the kolab-webadmin package is dated from may 2009. > > now i want to install the release version 2.2.2 and then make a upgrade > with these packages. > > Do you think that the relevant changes are made in the listed path? > > Can i just copy the srpm's to my installation and do a standard upgrade > as decribed in the 1st.README? If you already have downloaded kolab-server-2.2.1/sources/ (which is 20090407) you can just copy 20090515-since-20090407/sources/ _and_ the binary packages created during your first installation and create a new index as described in 1st.README ("Generating your own 00INDEX.rdf for installations or upgrades"). 2.2.2 is 20090515, so you will just have that version afterwards. The fixes for the web client (not admin) holidays are not included in 2.2.2, just in CVS HEAD (i.e. the current development stream), so you will have to wait a little bit to get that feature. You can always look at the release-notes.txt file next to the source or binary packages to see what is included in a specific release. Regards, Thomas Arendsen Hein -- thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998 Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From thomas at intevation.de Fri Jul 24 11:26:29 2009 From: thomas at intevation.de (Thomas Arendsen Hein) Date: Fri, 24 Jul 2009 11:26:29 +0200 Subject: Installation (Version 20090515, Kolab Server 2.2.2) fails for fedora 11 (procmail) In-Reply-To: <98d946fb0907220509m55d48f47y8e4f49230a1859ba@mail.gmail.com> References: <98d946fb0907220509m55d48f47y8e4f49230a1859ba@mail.gmail.com> Message-ID: <20090724092629.GB3140.thomas@intevation.de> * Sasha Kacanski [20090722 14:15]: > My question would be do I try to upgrade source src for procmail under > kolab with procmail package that has fix or I need to possibly install > different version of gcc to fix this issue. > I tried to bypass package installation with: > # sh install-kolab.sh -x procmail 2>&1 | tee > /cube/kolab-install/kolab-install.log > or > # sh install-kolab.sh -x procmail-3.22-20080101.src.rpm 2>&1 | tee > /cube/kolab-install/kolab-install.log > but both ways I could not skip procmail installation. procmail is pulled in as a requirement of postfix, so you can't simply exclude it. The good thing is that postfix in Kolab Server does not need procmail, so you could do the following (as user "kolab") 1. install the postfix source rpm: openpkg rpm -Uvh postfix-2.4.6-20080101_kolab.src.rpm 2. remove the procmail PreReq in postfix.spec: cd /kolab/RPM/SRC/postfix $EDITOR postfix.spec 3. recompile postfix: openpkg rpm -ba postfix.spec 4. use the created source and binary RPMs to create a new installed as described in 1st.README ("Generating your own 00INDEX.rdf for installations or upgrades") (all this should work in the half-ready environment your aborted installation leaves behind) Regards, Thomas Arendsen Hein -- thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998 Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From thomas at intevation.de Fri Jul 24 11:38:34 2009 From: thomas at intevation.de (Thomas Arendsen Hein) Date: Fri, 24 Jul 2009 11:38:34 +0200 Subject: IMAP annotations truncated; Was: Upgrading problems: IMAP recovery In-Reply-To: <4A681029.1030504@hia.rwth-aachen.de> References: <4A5B7012.6040002@hia.rwth-aachen.de> <20090714100000.15661ook83401dlw@webmail.pardus.de> <4A5C8A6C.4080108@hia.rwth-aachen.de> <4A681029.1030504@hia.rwth-aachen.de> Message-ID: <20090724093834.GC3140.thomas@intevation.de> * Saim Kim [20090723 09:21]: > does anybody have an idea why the Kolab annotations in the IMAP headers > are truncated as shown below? > > > Saim Kim schrieb: > > Gunnar Wrobel schrieb: > > > > Original server: > > > > folder-type: event.default > > incidences-for: readers > > xfb-readable: test at medit.intern test3 at medit.intern > > > > > > New server: > > > > folder-type: t.default > > incidences-for: ers > > xfb-readable: t at medit.intern test3 at medit.intern We have seen the same problem on exactly one customer machine, too, but the strange thing there was that it only affected php code (i.e. resource handling), while looking at the annotations with cyradm correctly showed event.default. > > So, after I dumped the annotations.db from the original maschine, how > > can I get it back into berkeley format? I tried to use > > /kolab/bin/cvt_cyrusdb /tmp/annotations.db.txt flat > > /tmp/annotations.db berkeley. Even though I get the same warning as > > before ("Warning: apparently empty database converted"), I get a > > resulting annotations.db file which is much smaller than before (8 kB > > compared to 229 kB)? And converting it back to flat format results in > > a 0 kB file? You could try using http://kolab.org/cgi-bin/viewcvs-kolab.cgi/*checkout*/utils/admin/kolab-mailboxinfo.pl You can run it with the old database using the option "-c" to produce output suitable for import via cyradm. Regards, Thomas Arendsen Hein -- thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998 Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From thomas at intevation.de Fri Jul 24 11:41:35 2009 From: thomas at intevation.de (Thomas Arendsen Hein) Date: Fri, 24 Jul 2009 11:41:35 +0200 Subject: Change domain name In-Reply-To: References: Message-ID: <20090724094135.GD3140.thomas@intevation.de> * Johannes Graumann [20090721 21:30]: > Is there any slick way to change the mail domain name in a kolab > installation? > > I was thinking of a grep for "olddomain" followed by automated replacement > and a slap export/import cycle for the users ... At least the cyrus imap spool needs to be reconstructed, ACLs changed to the new values, etc. ... very cumbersome. http://kolab.org/cgi-bin/viewcvs-kolab.cgi/doc/raw-howtos/move-rename-user.txt?rev=1.1 discusses this problem. Regards, Thomas Arendsen Hein -- thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998 Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From johannes_graumann at web.de Fri Jul 24 13:00:15 2009 From: johannes_graumann at web.de (Johannes Graumann) Date: Fri, 24 Jul 2009 13:00:15 +0200 Subject: Change domain name References: <20090724094135.GD3140.thomas@intevation.de> Message-ID: Solved the issue with a fresh install while storing all info in an alternative kde-pim compatible offering (MailXchange). Thanks, Joh Thomas Arendsen Hein wrote: > * Johannes Graumann [20090721 21:30]: >> Is there any slick way to change the mail domain name in a kolab >> installation? >> >> I was thinking of a grep for "olddomain" followed by automated >> replacement and a slap export/import cycle for the users ... > > At least the cyrus imap spool needs to be reconstructed, ACLs > changed to the new values, etc. ... very cumbersome. > > http://kolab.org/cgi-bin/viewcvs-kolab.cgi/doc/raw-howtos/move-rename- user.txt?rev=1.1 > discusses this problem. > > Regards, > Thomas Arendsen Hein > From skacanski at gmail.com Sun Jul 26 03:28:00 2009 From: skacanski at gmail.com (Sasha Kacanski) Date: Sat, 25 Jul 2009 21:28:00 -0400 Subject: Kolab-users Digest, Vol 65, Issue 34 In-Reply-To: References: Message-ID: <98d946fb0907251828q32c1de24y785ecf71aae8e913@mail.gmail.com> Hi Thomas, First, thanks for the proposed solution. Now I understand a bit better why things did not work. I did followed your suggested fix, but ran into the problem with PHP while rebuilding postfix sources... #openpkg rpm -ba postfix.spec throws this error on modified or straight spec file... error: Failed build dependencies: pcre is needed by postfix-2.4.6-20080101_kolab Sounds like PHP and pcre did not get compiled prior to postfix to satisfy build dependencies. Should i compile PHP manually or exclude possibly from the postfix build. Regards, --sasha >> but both ways I could not skip procmail installation. > > procmail is pulled in as a requirement of postfix, so you can't > simply exclude it. > > The good thing is that postfix in Kolab Server does not need > procmail, so you could do the following (as user "kolab") > > 1. install the postfix source rpm: > ? ? openpkg rpm -Uvh postfix-2.4.6-20080101_kolab.src.rpm > 2. remove the procmail PreReq in postfix.spec: > ? ? cd /kolab/RPM/SRC/postfix > ? ? $EDITOR postfix.spec > 3. recompile postfix: > ? ? openpkg rpm -ba postfix.spec > 4. use the created source and binary RPMs to create a new installed > ? as described in 1st.README ("Generating your own 00INDEX.rdf for > ? installations or upgrades") > > (all this should work in the half-ready environment your aborted > installation leaves behind) > > Regards, > Thomas Arendsen Hein From lists at oak-wood.co.uk Sun Jul 26 21:44:42 2009 From: lists at oak-wood.co.uk (Chris Hastie) Date: Sun, 26 Jul 2009 20:44:42 +0100 Subject: Folder sharing across domains Message-ID: <4A6CB22A.7080002@oak-wood.co.uk> I'm just setting up a Kolab installation with two domains. I've tried creating a shared contacts folder, but it has to be associated with one or other domain and is then not visible to the other. Likewise, users in one domain are unable to share their folders with users from another. The permissions can be set with the full uid of the user in the other domain, but the folder remains invisible. Is it possible to share folders across domains in a single Kolab installation? -- Chris From bernhard at intevation.de Mon Jul 27 10:29:45 2009 From: bernhard at intevation.de (Bernhard Reiter) Date: Mon, 27 Jul 2009 10:29:45 +0200 Subject: Folder sharing across domains In-Reply-To: <4A6CB22A.7080002@oak-wood.co.uk> References: <4A6CB22A.7080002@oak-wood.co.uk> Message-ID: <200907271029.45539.bernhard@intevation.de> Am Sonntag, 26. Juli 2009 21:44:42 schrieb Chris Hastie: > Is it possible to share folders across domains in a single Kolab > installation? Currently it is not, this is a Cyrus IMAP limitation. See kolab/issue1141 (Cannot give users from other domains access to a folder) (I am not sure about the upcoming variant with Dovecot, but again, this is still in development, so need an expert to set it up currently.) Bernhard -- Managing Director - Owner: www.intevation.net (Free Software Company) Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com. Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://kolab.org/pipermail/kolab-users/attachments/20090727/8225f0c6/attachment.bin From webmaster at computational-chemistry.org Mon Jul 27 16:02:09 2009 From: webmaster at computational-chemistry.org (Alexander =?iso-8859-1?q?Schr=F6ter?=) Date: Mon, 27 Jul 2009 16:02:09 +0200 Subject: what mobile device would you recommend Message-ID: <200907271602.10103.webmaster@computational-chemistry.org> Hello everybody I am looking for a mobile device to use with kolab. In detail one to use with horde's syncml client. Even though I am more trying to find the right phone/palm/pocketpc for me, I think more people could benefit from information for example on the kolab wiki page. Which phones (or other clients like outlook, thunderbird, evolution) support which functions with which clients (included syncml connectors or funambol). Maybe we could start something like this? I am looking for a small portable device which is able to sync the calendar, tasks and contacts (notes are not that important to me). Of course I don't want to do that over the expensive phone line, so it needs to have wireless lan (if you do know that your phone can connect to TTLS - PAP encrypted Wireless Lans - please let me know because this is what we use at the university). I know the question is not very specific, and there is lots to talk about but I really think the project could benefit from more information about this. And I would be glad to help on that part. Thank you. Alexander Schroeter From tomas.andersson at heatex.com Mon Jul 27 16:54:49 2009 From: tomas.andersson at heatex.com (Tomas Andersson) Date: Mon, 27 Jul 2009 16:54:49 +0200 Subject: Not currently in TRANSACTION state Message-ID: <000001ca0eca$32593450$970b9cf0$@andersson@heatex.com> Newly installed Kolab 2.2.2 User is trying to activate vacation message and gets following message. What do I do to correct this? A quick answer would be appreciated Errors: Not currently in TRANSACTION state Script was: require "vacation"; -------------- next part -------------- An HTML attachment was scrubbed... URL: http://kolab.org/pipermail/kolab-users/attachments/20090727/1c7b62ab/attachment.html From greenpenguin at free.fr Tue Jul 28 07:31:54 2009 From: greenpenguin at free.fr (greenpenguin@free.fr) Date: Tue, 28 Jul 2009 07:31:54 +0200 Subject: Upgrade from 2.0 to 2.2.2 with new server In-Reply-To: <1248205269.4a6619d51a540@imp.free.fr> References: <1246995994.4a53a61ab4c91@imp.free.fr> <20090708094352.1262588l69tefs4k@webmail.pardus.de> <1248014678.4a63315654c79@imp.free.fr> <20090720160903.18043xjzt4vjwa68@webmail.pardus.de> <20090720143108.GC27082.thomas@intevation.de> <1248205269.4a6619d51a540@imp.free.fr> Message-ID: <1248759114.4a6e8d4af31f0@imp.free.fr> Hi, This is almost Ok. I have followed the instructions to upgrade from 2.0 to 2.1 and then the 2.1 to 2.2. I will write a documentation. The server is in production but I have a problem. The imapd crashes when there is load. In the imapd.log, we can find : Jul 27 10:00:14 srvmail imap[25452]: DBERROR db4: Logging region out of memory; you may need to increase its size Jul 27 10:00:14 srvmail imap[25452]: DBERROR: opening /kolab/var/imapd/annotations.db: Cannot allocate memory Jul 27 10:00:14 srvmail imap[25452]: DBERROR: opening /kolab/var/imapd/annotations.db: cyrusdb error Jul 27 10:00:14 srvmail imap[25452]: Fatal error: can't read annotations file J The only solution I have found is to to remove the annotations.db and restart the imapd service. I have searched on Internet and the solution would be to configure DB4 with DB_CONFIG. How to do this ? Where is the file ? The only file I found is in the LDAP configuration ? I need your help because the server is in production. Thanks by advance Green Penguin Selon greenpenguin at free.fr: > Ok I will try to use the 2.0->2.1 instructions and then the 2.1->2.2 > instructions. > > I am interesting for the instructions to import existing data into a fresh > installation. I think, it's very important for the future. > > > > > > Selon "Arendsen Hein, Thomas" : > > The default structure in 2.1.x and 2.2.x has changed compared to > > 2.0.x, but you can just comment the "hashimapspool: yes" line in > > /kolab/etc/kolab/templates/imapd.conf.template (as described in the > > 2.0->2.1 upgrading docs). > > > > Alternatively you can use > > > http://kolab.org/cgi-bin/viewcvs-kolab.cgi/*checkout*/utils/admin/hash-imap-spool > > to convert it from the old format to the current. > > > > I think your best bet for now is to follow the 2.0->2.1 > > instructions and then the 2.1->2.2 instructions. I think this should > > even work without installing the 2.1 packages first, but directly > > install the 2.2 ones. > > > > > @thomas: The 1st.README states "Instructions for upgrading from Kolab > > > server 2.0 will be added in a future version of this document." Is > > > this still on the list of things to do? > > > > Somehow, but with lower priority, as there is above workaround. > > > > More interesting would be instructions to import existing data into > > a fresh installations. We already have a draft for that and it was > > already used in production once, but it needs some more work before > > this can be published. > > > > 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 > > > > _______________________________________________ > > 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 liutauras.adomaitis at gmail.com Tue Jul 28 09:15:27 2009 From: liutauras.adomaitis at gmail.com (Liutauras Adomaitis) Date: Tue, 28 Jul 2009 10:15:27 +0300 Subject: Not currently in TRANSACTION state In-Reply-To: <3073774675381243497@unknownmsgid> References: <3073774675381243497@unknownmsgid> Message-ID: 2009/7/27 Tomas Andersson : > Newly installed Kolab 2.2.2 > > User is trying to activate vacation message and gets following message. > > What do I do to correct this? > > A quick answer would be appreciated > Did you try looking at LDAP database and if your user has KolabHomeServer attribute? I had the same problem for users, which where imported from Samab LDAP to Kolab LDAP database. I forgot to add kolabHomeServer attribute for them, and vacation did not work. Adding attributes has helped me. Liutauras From tomas.andersson at heatex.com Tue Jul 28 09:23:01 2009 From: tomas.andersson at heatex.com (Tomas Andersson) Date: Tue, 28 Jul 2009 09:23:01 +0200 Subject: SV: Not currently in TRANSACTION state In-Reply-To: References: <3073774675381243497@unknownmsgid> Message-ID: <000301ca0f54$40bedc40$c23c94c0$@andersson@heatex.com> The users were not imported. They were recreated manualy in the kolab admin interface ?mne: Re: Not currently in TRANSACTION state 2009/7/27 Tomas Andersson : > Newly installed Kolab 2.2.2 > > User is trying to activate vacation message and gets following message. > > What do I do to correct this? > > A quick answer would be appreciated > Did you try looking at LDAP database and if your user has KolabHomeServer attribute? I had the same problem for users, which where imported from Samab LDAP to Kolab LDAP database. I forgot to add kolabHomeServer attribute for them, and vacation did not work. Adding attributes has helped me. Liutauras From tomas.andersson at heatex.com Tue Jul 28 10:04:26 2009 From: tomas.andersson at heatex.com (Tomas Andersson) Date: Tue, 28 Jul 2009 10:04:26 +0200 Subject: SV: Not currently in TRANSACTION state In-Reply-To: References: <3073774675381243497@unknownmsgid> Message-ID: <000601ca0f5a$0832ca20$18985e60$@andersson@heatex.com> This is the LDP record for myself And KolabHomeServer is set What else could be wrong??? Child objects Object attributes None alias : tomasa at heatex.com cn : Tomas Andersson givenName : Tomas kolabHomeServer : mail.heatex.com kolabInvitationPolicy : ACT_MANUAL mail : tomas.andersson at heatex.com objectClass : top , inetOrgPerson , kolabInetOrgPerson sn : Andersson uid : tomas.andersson at heatex.com -----Ursprungligt meddelande----- Fr?n: Liutauras Adomaitis [mailto:liutauras.adomaitis at gmail.com] Skickat: den 28 juli 2009 09:15 Till: Tomas Andersson Kopia: kolab-users at kolab.org ?mne: Re: Not currently in TRANSACTION state 2009/7/27 Tomas Andersson : > Newly installed Kolab 2.2.2 > > User is trying to activate vacation message and gets following message. > > What do I do to correct this? > > A quick answer would be appreciated > Did you try looking at LDAP database and if your user has KolabHomeServer attribute? I had the same problem for users, which where imported from Samab LDAP to Kolab LDAP database. I forgot to add kolabHomeServer attribute for them, and vacation did not work. Adding attributes has helped me. Liutauras From lists at oak-wood.co.uk Tue Jul 28 10:11:41 2009 From: lists at oak-wood.co.uk (Chris Hastie) Date: Tue, 28 Jul 2009 09:11:41 +0100 Subject: what mobile device would you recommend In-Reply-To: <200907271602.10103.webmaster@computational-chemistry.org> References: <200907271602.10103.webmaster@computational-chemistry.org> Message-ID: <4A6EB2BD.70808@oak-wood.co.uk> On 27/07/09 15:02, Alexander Schr?ter wrote: > I am looking for a small portable device which is able to sync the calendar, > tasks and contacts (notes are not that important to me). Of course I don't > want to do that over the expensive phone line, so it needs to have wireless > lan (if you do know that your phone can connect to TTLS - PAP encrypted > Wireless Lans - please let me know because this is what we use at the > university). > > I've been playing with my Nokia E63 for a few days with reasonable results. The problems I'm having seem to be more to do with other clients than with the phone or SyncML functionality. Calendar is working well. One or two appointments seem to have been duplicated, but I suspect that is down to another client (also using Outlook + Toltec, Kontact and Thunderbird + SyncKolab). Tasks seems to work in one direction only - towards the phone. The phone config has no specific entry for tasks, but they seem to be being synced with the calendar. Whether this is changed if I turn off showing tasks in the calendar in the webclient I haven't established. But the phone recognises them as tasks rather than meetings. However, if I create a task on the phone, despite the sync progress saying it is sending a calendar entry to the server, I never see anything turn up there. Nor do changes made on the phone (eg marking as complete) seem to show up on the server. Contacts is giving me the most trouble (though I guess if I actually used tasks much the fact that it's one-way would be bugging me a lot more). It works, but requires some care. The problem seems to be that not all clients are created equal, and not all make use of the same fields. The field used on the phone as a default for all those numbers I've had since phones only stored one number per contact isn't displayed by Horde, Outlook or Thunderbird, but is by Kontact. The phone is fine - it seems to cope merrily with an arbitrary number of fields, but the various clients are more fussy about which fields are used, only display some, and can't agree on which ones they display. I'm also having trouble with duplicates. I painstakingly removed all such things on the phone, moved a few numbers to new fields etc and synced. Everything looked fine in Horde. But a lot of the numbers I'd deleted still appeared in TB, Kontact and Outlook. After painstakingly removing them all again in TB, they came back the next time I synced. Phone and Horde still look pretty much OK, but other clients are littered with duplicates and things I think I've deleted but they just haven't gone away. If anyone has any clues on this I'd be grateful. I'm afraid I've no idea if the phone will cope with TTLS - PAP encrypted WLANs - I've never encountered one. It is fine with my basic WLAN and with a 3g connection. HTH Chris From thomas at intevation.de Tue Jul 28 10:53:40 2009 From: thomas at intevation.de (Thomas Arendsen Hein) Date: Tue, 28 Jul 2009 10:53:40 +0200 Subject: Kolab-users Digest, Vol 65, Issue 34 In-Reply-To: <98d946fb0907251828q32c1de24y785ecf71aae8e913@mail.gmail.com> References: <98d946fb0907251828q32c1de24y785ecf71aae8e913@mail.gmail.com> Message-ID: <20090728085340.GA407.thomas@intevation.de> * Sasha Kacanski [20090726 03:33]: > I did followed your suggested fix, but ran into the problem with PHP > while rebuilding postfix sources... > #openpkg rpm -ba postfix.spec My mistake, you need to pass additional build options: openpkg rpm -ba --define 'with_fsl yes' --define 'with_ssl yes' --define 'with_sasl yes' --define 'with_ldap yes' postfix.spec > throws this error on modified or straight spec file... > error: Failed build dependencies: > pcre is needed by postfix-2.4.6-20080101_kolab > Sounds like PHP and pcre did not get compiled prior to postfix to > satisfy build dependencies. Should i compile PHP manually or exclude > possibly from the postfix build. I don't see any reference to php here, only pcre. pcre should already be installed at this stage, but if it isn't, you should try to compile/install it manually. Maybe check your build log to see if it failed to build? Regards, Thomas Arendsen Hein -- thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998 Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From thomas at intevation.de Tue Jul 28 11:05:49 2009 From: thomas at intevation.de (Thomas Arendsen Hein) Date: Tue, 28 Jul 2009 11:05:49 +0200 Subject: Upgrade from 2.0 to 2.2.2 with new server In-Reply-To: <1248759114.4a6e8d4af31f0@imp.free.fr> References: <1246995994.4a53a61ab4c91@imp.free.fr> <20090708094352.1262588l69tefs4k@webmail.pardus.de> <1248014678.4a63315654c79@imp.free.fr> <20090720160903.18043xjzt4vjwa68@webmail.pardus.de> <20090720143108.GC27082.thomas@intevation.de> <1248205269.4a6619d51a540@imp.free.fr> <1248759114.4a6e8d4af31f0@imp.free.fr> Message-ID: <20090728090549.GB407.thomas@intevation.de> * greenpenguin at free.fr [20090728 07:32]: > The imapd crashes when there is load. > In the imapd.log, we can find : > Jul 27 10:00:14 srvmail imap[25452]: DBERROR db4: Logging region out > of memory; you may need to increase its size > Jul 27 10:00:14 srvmail imap[25452]: DBERROR: opening > /kolab/var/imapd/annotations.db: Cannot allocate memory > Jul 27 10:00:14 srvmail imap[25452]: DBERROR: opening > /kolab/var/imapd/annotations.db: cyrusdb error > Jul 27 10:00:14 srvmail imap[25452]: Fatal error: can't read annotations > file > J > > The only solution I have found is to to remove the annotations.db and restart > the imapd service. > > I have searched on Internet and the solution would be to configure DB4 with > DB_CONFIG. As a quick fix I'd suggest using skiplist format for the cyrus databases again. Their stability should have improved with the new cyrus imapd used in Kolab Server 2.2.2. The upgrading docs mention how to do the convert in the other direction. > I need your help because the server is in production. You could contact the Kolab Konsortium (which Intevation is a part of) for professional support. Regards, Thomas Arendsen Hein -- thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998 Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From thomas at intevation.de Tue Jul 28 11:14:30 2009 From: thomas at intevation.de (Thomas Arendsen Hein) Date: Tue, 28 Jul 2009 11:14:30 +0200 Subject: Not currently in TRANSACTION state Message-ID: <20090728091430.GC407.thomas@intevation.de> * Tomas Andersson [20090727 16:55]: > Newly installed Kolab 2.2.2 > > User is trying to activate vacation message and gets following message. > > Errors: > > Not currently in TRANSACTION state The web admin interface tries to connect to the tcp port 2000. For this it does not use localhost, but the kolabHomeServer of the corresponding user. Therefore (and for other reasons, too) a Kolab server always needs to be able to reach itself by its own hostname. If you use NAT and/or packet filtering this could fail. A quick solution could be to add the IP of the server to its own /etc/hosts and make sure that you do not have any iptables rules which block access to itself. Regards, Thomas Arendsen Hein -- thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998 Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From tomas.andersson at heatex.com Tue Jul 28 11:23:27 2009 From: tomas.andersson at heatex.com (Tomas Andersson) Date: Tue, 28 Jul 2009 11:23:27 +0200 Subject: SV: Not currently in TRANSACTION state In-Reply-To: <20090728091430.GC407.thomas@intevation.de> References: <20090728091430.GC407.thomas@intevation.de> Message-ID: <002201ca0f65$1212b590$363820b0$@andersson@heatex.com> This is the /etc/hosts file 127.0.0.1 localhost.localdomain localhost 192.168.90.12 server02.heatex.local server02 192.168.90.12 mail.heatex.com mail # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts Shouldn?t this work??? -----Ursprungligt meddelande----- Fr?n: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org] F?r Thomas Arendsen Hein Skickat: den 28 juli 2009 11:15 Till: kolab-users at kolab.org ?mne: Re: Not currently in TRANSACTION state * Tomas Andersson [20090727 16:55]: > Newly installed Kolab 2.2.2 > > User is trying to activate vacation message and gets following message. > > Errors: > > Not currently in TRANSACTION state The web admin interface tries to connect to the tcp port 2000. For this it does not use localhost, but the kolabHomeServer of the corresponding user. Therefore (and for other reasons, too) a Kolab server always needs to be able to reach itself by its own hostname. If you use NAT and/or packet filtering this could fail. A quick solution could be to add the IP of the server to its own /etc/hosts and make sure that you do not have any iptables rules which block access to itself. Regards, Thomas Arendsen Hein -- thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998 Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner _______________________________________________ Kolab-users mailing list Kolab-users at kolab.org https://kolab.org/mailman/listinfo/kolab-users From rob at cow-frenzy.co.uk Tue Jul 28 10:51:30 2009 From: rob at cow-frenzy.co.uk (Rob Fulton) Date: Tue, 28 Jul 2009 09:51:30 +0100 (BST) Subject: IMAP works but POP3 fails Message-ID: Hi, I've just setup kolab and I'm having problems collecting mail, IMAP works fine, I can see the mails in the inbox on outlook, when I try to collect via pop3 to the same mailbox I get the following error : Unable to locate maildrop user.xxx^xxxxx: Mailbox does not exist I can't seem to find out how to increase the debug on imapd to see what directory it's actually trying to access. The cyrus.conf shows impad and pop3d using the same config file Regards Rob Fulton From thomas at intevation.de Tue Jul 28 12:16:36 2009 From: thomas at intevation.de ('Thomas Arendsen Hein') Date: Tue, 28 Jul 2009 12:16:36 +0200 Subject: SV: Not currently in TRANSACTION state Message-ID: <20090728101636.GD407.thomas@intevation.de> * Tomas Andersson [20090728 11:47]: > This is the /etc/hosts file > > 192.168.90.12 server02.heatex.local server02 > 192.168.90.12 mail.heatex.com mail I never tried to use two identical IPs in one /etc/hosts file, and according to the man page this is wrong. Better use: 192.168.90.12 mail.heatex.com mail server02.heatex.local server02 Regards, Thomas Arendsen Hein -- thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998 Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From alexander.marx at oab.de Thu Jul 30 12:14:59 2009 From: alexander.marx at oab.de (Alexander Marx) Date: Thu, 30 Jul 2009 12:14:59 +0200 Subject: fetchmail error with ssl Message-ID: <4A7172A3.3060301@oab.de> Dear List, i installed a new Kolab 2.2.2 and now i added the fetchmail rpm from openpkg. when i try to get mails from the server pop.1und1.de i get following errors: fetchmail: Server CommonName mismatch: pop.1und1.de != 212.227.15.178 fetchmail: Server certificate verification error: unable to get local issuer certificate fetchmail: Server certificate verification error: certificate not trusted fetchmail: Server certificate verification error: unable to verify the first certificate This error is discussed in plenty of sites. the best solution for UBUNTU would be to just install ca-certificates via apt-get. that does not solve the prob, as it is a openpkg rpm. What can be done to get rid of this errors? is there a openpkg package wich includes all of the ca certificates? 1und1.de seems to use a certificate from thawte. i want to put this mailserver in production so i would be glad for a quick and helpful reply. By the way: my old Kolab 2.0.3 does work with an fetchmail without errors, but that installation is 3 years old.... Thanks in advance, -- w * Alexander Marx* Fachinformatiker Systemintegration ACE (Astaro certified engineer) LPIC (101) From bernhard at intevation.de Thu Jul 30 13:46:42 2009 From: bernhard at intevation.de (Bernhard Reiter) Date: Thu, 30 Jul 2009 13:46:42 +0200 Subject: what mobile device would you recommend In-Reply-To: <4A6EB2BD.70808@oak-wood.co.uk> References: <200907271602.10103.webmaster@computational-chemistry.org> <4A6EB2BD.70808@oak-wood.co.uk> Message-ID: <200907301346.43056.bernhard@intevation.de> Chris, Am Dienstag, 28. Juli 2009 10:11:41 schrieb Chris Hastie: > I've been playing with my Nokia E63 for a few days with reasonable > results. thanks for sharing your experiences! My suggestion is that we put stuff in reachable from http://wiki.kolab.org/index.php/Web_Client_SyncML (Don't forget to state your configuration, e.g. the server version number.) Alexander, your help is really appreciated, what about starting with putting onto that wiki page a summary what Chris wrote and a link to his posting? > The problems I'm having seem to be more to do with other > clients than with the phone or SyncML functionality. > > Calendar is working well. One or two appointments seem to have been > duplicated There might be an issue for duplication handling somewhere, I do not have it at hand right now. Best, Bernhard -- Managing Director - Owner: www.intevation.net (Free Software Company) Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com. Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://kolab.org/pipermail/kolab-users/attachments/20090730/9e492fe6/attachment.bin From bernhard at intevation.de Thu Jul 30 13:49:56 2009 From: bernhard at intevation.de (Bernhard Reiter) Date: Thu, 30 Jul 2009 13:49:56 +0200 Subject: IMAP works but POP3 fails In-Reply-To: References: Message-ID: <200907301349.56480.bernhard@intevation.de> Am Dienstag, 28. Juli 2009 10:51:30 schrieb Rob Fulton: > I can't seem to find out how to increase the debug on imapd to see what > directory it's actually trying to access. Maybe this one helps: http://wiki.kolab.org/index.php/Enable_Imap_protocol_logging -- Managing Director - Owner: www.intevation.net (Free Software Company) Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com. Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. Url : http://kolab.org/pipermail/kolab-users/attachments/20090730/ad601685/attachment.bin From webmaster at computational-chemistry.org Thu Jul 30 14:37:40 2009 From: webmaster at computational-chemistry.org (Alexander =?iso-8859-15?q?Schr=F6ter?=) Date: Thu, 30 Jul 2009 14:37:40 +0200 Subject: what mobile device would you recommend In-Reply-To: <200907301346.43056.bernhard@intevation.de> References: <200907271602.10103.webmaster@computational-chemistry.org> <4A6EB2BD.70808@oak-wood.co.uk> <200907301346.43056.bernhard@intevation.de> Message-ID: <200907301437.41067.webmaster@computational-chemistry.org> Yes thank you for sharing your information. Actually I have been thinking about how to set up a wiki page for this. I signed up and I am going to propose my idea next week. I will use the information given by Chris and will add mine own. I so far have a working funambol thunderbird connector under windows and a working funambol outlook 2007 connector under windows. I hope more people share their experience. On Thursday 30 July 2009 01:46:42 pm Bernhard Reiter wrote: > Chris, > > Am Dienstag, 28. Juli 2009 10:11:41 schrieb Chris Hastie: > > I've been playing with my Nokia E63 for a few days with reasonable > > results. > > thanks for sharing your experiences! > My suggestion is that we put stuff in reachable from > http://wiki.kolab.org/index.php/Web_Client_SyncML > (Don't forget to state your configuration, e.g. the server version number.) > > Alexander, your help is really appreciated, what about starting with > putting onto that wiki page a summary what Chris wrote and a link to his > posting? > > > The problems I'm having seem to be more to do with other > > clients than with the phone or SyncML functionality. > > > > Calendar is working well. One or two appointments seem to have been > > duplicated > > There might be an issue for duplication handling somewhere, > I do not have it at hand right now. > > Best, > Bernhard From Roessler at FuH-E.de Thu Jul 30 14:38:24 2009 From: Roessler at FuH-E.de (=?ISO-8859-15?Q?Christian_R=F6=DFler?=) Date: Thu, 30 Jul 2009 14:38:24 +0200 Subject: [Info only, for the record] User deleted, awaiting cleanup... This solution applies only when using slave server(s) Message-ID: <4A719440.8020400@FuH-E.de> Hallo everyone, this here is another possible cause for the well-known message "User deleted, awaiting cleanup". As someone I know of had the same problem, I will just post the causation and solution here, so others may benefit too. This happens mostly while doing testing. If a user is created and deleted in short time, this will apply. In that case a user entry will be written into the master server. If this user gets deleted before there was time to propagate/replicate the ldap entry to the slave server(s), the dreaded message "User deleted, awaiting cleanup" will appear and stay. To be sure this applies: - do a ldapsearch for the user entry on the master server; take a look to the kolabDeleteFlag entries. - repeat the ldapsearch for the user entry on the slave server(s) mentioned in the kolabDeleteFlag entries. - if this ldapsearches turn up empty on one or more of the slave servers delete the corresponding kolabDeleteFlag entries, but make sure you let the kolabDeleteFlag entries pointing to slave servers where the user entry got propagated to stay. Voila - the message will vanish almost immediately. I hope this is helpful for somebody... Best regards, Christian From alexander.marx at oab.de Thu Jul 30 15:54:43 2009 From: alexander.marx at oab.de (Alexander Marx) Date: Thu, 30 Jul 2009 15:54:43 +0200 Subject: ldap export/import Message-ID: <4A71A623.1050605@oab.de> Hello List, to get all users from a kolab 2.0.3 server and put them into a kolab 2.2.2 server, is it possible just to do a slapcat on the 2.0.3 and on the 2.2.2 and then just copy the "user-part" from the 2.0.3-ldif to the 2.2.2 ldif and import it into the 2.2.2? -- w * Alexander Marx* Fachinformatiker Systemintegration ACE (Astaro certified engineer) LPIC (101) From greenpenguin at free.fr Fri Jul 31 22:04:24 2009 From: greenpenguin at free.fr (greenpenguin@free.fr) Date: Fri, 31 Jul 2009 22:04:24 +0200 Subject: Upgrade from 2.0 to 2.2.2 with new server In-Reply-To: <20090728090549.GB407.thomas@intevation.de> References: <1246995994.4a53a61ab4c91@imp.free.fr> <20090708094352.1262588l69tefs4k@webmail.pardus.de> <1248014678.4a63315654c79@imp.free.fr> <20090720160903.18043xjzt4vjwa68@webmail.pardus.de> <20090720143108.GC27082.thomas@intevation.de> <1248205269.4a6619d51a540@imp.free.fr> <1248759114.4a6e8d4af31f0@imp.free.fr> <20090728090549.GB407.thomas@intevation.de> Message-ID: <1249070664.4a734e485d7a9@imp.free.fr> Ok, it works in the skiplist configuration. It's strange... Thank you very much for your help. I will write a summary to migrate a 2.0 to 2.2. Selon Thomas Arendsen Hein : > * greenpenguin at free.fr [20090728 07:32]: > > The imapd crashes when there is load. > > In the imapd.log, we can find : > > Jul 27 10:00:14 srvmail imap[25452]: DBERROR db4: Logging region > out > > of memory; you may need to increase its size > > Jul 27 10:00:14 srvmail imap[25452]: DBERROR: opening > > /kolab/var/imapd/annotations.db: Cannot allocate memory > > Jul 27 10:00:14 srvmail imap[25452]: DBERROR: opening > > /kolab/var/imapd/annotations.db: cyrusdb error > > Jul 27 10:00:14 srvmail imap[25452]: Fatal error: can't read > annotations > > file > > J > > > > The only solution I have found is to to remove the annotations.db and > restart > > the imapd service. > > > > I have searched on Internet and the solution would be to configure DB4 with > > DB_CONFIG. > > As a quick fix I'd suggest using skiplist format for the cyrus > databases again. Their stability should have improved with the new > cyrus imapd used in Kolab Server 2.2.2. The upgrading docs mention > how to do the convert in the other direction. > > > I need your help because the server is in production. > > You could contact the Kolab Konsortium (which Intevation is a part > of) for professional support. > > Regards, > Thomas Arendsen Hein > > -- > thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: > 0x5816791A > Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B > 18998 > Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner > > _______________________________________________ > Kolab-users mailing list > Kolab-users at kolab.org > https://kolab.org/mailman/listinfo/kolab-users > From bogus@does.not.exist.com Tue Jul 28 09:22:36 2009 From: bogus@does.not.exist.com () Date: Tue, 28 Jul 2009 07:22:36 -0000 Subject: No subject Message-ID: From bogus@does.not.exist.com Tue Jul 28 09:22:36 2009 From: bogus@does.not.exist.com () Date: Tue, 28 Jul 2009 07:22:36 -0000 Subject: No subject Message-ID: Always reject the message. Note that enabling this setting will make the server reject any mail with non-matching sender and From header if the sender is an account on this server. This is known to cause trouble for example with mailinglists. Kolab Hostnames (for Master and Slaves) h1616679.stratoserver.net