similar to: Missing metadata on Dovecot 2.2.14, on Kolab 3.3, Centos 6.6

Am 10.09.2015 um 23:43 schrieb Timo Sirainen: > I've been once in a while over the years thinking about implementing CalDAV (and CardDAV) to Dovecot. It might be time to start that soon. Does anyone have any suggestions? So far my main goals would be: > > - scalable, of course > - configurable storage (object storage, regular fs, maybe some key-value dbs, maybe storing as

Dovecot (deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main) crached after create new metadata folder (But the folder with metadata is created). Metadata plugin v14. Coredump: http://yadi.sk/d/bsBCpRS76mXpj in log: imap(admin at example.ru): Fatal: master: service(imap): child 14339 killed with signal 11 (core dumped) [10-Jul-2013 11:46:00 +0400]: [A4A2] S: * OK [CAPABILITY

--Repost after subscription as list member --- I made some tests with metadata support in dovecot 2.2.10. Previously I had dovecot 2.2.4 with external metadata plugin who work well. I use dovecot with roundcube and roundcube plugins from kolab project . First, the feature activation was tricky and rather undocumented. I spent about half hour googling, after that I set: imap_metadata = yes and

Hi, I just wanted to let you know, that I've written a HOWTO on Samba and Kolab integration. In other words, I tried to explain, hopefully in an easy way, how to add Kolab groupware functionality to an existing Samba/OpenLDAP setup - so that both Samba and Kolab users would use the same credentials. You can find it on http://wpkg.org/kolab Of course feel free to comment :) -- Tomek

hi, is dovecot are support all required feature for kolab imap server? the requirements can be found here: http://www.kolab.org/doc/kolabformat-2.0rc3-html/index.html ie. can i replace cyrus-imap with dovecot in a kolab server? thanks in advance. yours. -- Levente "Si vis pacem para bellum!"

Does anyone have Kolab running on Centos 4.x. I have always used Centos 3.x and Kolab 1.0 todate, but cannot find a howto for Kolab V2.x Any clues/url's welcome. Thanks Denis

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 LDAP Account Manager (LAM) 4.3.RC1 - September 1st, 2013 ======================================================== LAM is a web frontend for managing accounts stored in an LDAP directory. Announcement: - ------------- Added Unix user+group support for Samba 4. Additionally, you may now manage Kolab groups. Custom fields support read-only fields and

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 LDAP Account Manager (LAM) 4.3 - September 17th, 2013 ===================================================== LAM is a web frontend for managing accounts stored in an LDAP directory. Announcement: - ------------- Added Unix user+group support for Samba 4. Additionally, you may now manage Kolab groups. Custom fields support read-only fields and file

Debian Wheezy dovecot 2.2.4 (deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2.patched main) dovecot-metadata-plugin v14 /var/lib/dovecot 777 dovecot:dovecot /var/lib/dovecot/shared-metadata 700 dovecot:dovecot /var/run/dovecot 777 dovecot:dovecot /var/run/divecot/dict 666 mail:dovecot Test1 - create calendar UTF7 mailbox (no errors in

Hello everyone! I just released dovecot-metadata-8, which is an implementation of RFC 5464 (IMAP METADATA), allowing to add comments/annotations/metadata to folders of an email account. The major feature is that it works with Akonadi, or more specifically the Kolab backend thereof, while being dovecot-2.0 compatible. The module consists of 3 plugins, two IMAP frontends and one backend: *

Hi Timo, Hi *, was written the other day we started to use Dovecot 1.2 for our Kolab with Dovecot project, but it turned out that there are quite a bunch of issues with 1.2 (which is ok, as it hasn't even been announced as beta till now). We have a customer who should get a first test installation of Kolab with Dovecot in the first week of September and for that we need the features

According to http://www.dovecot.org/list/dovecot/2005-June/007569.html support for the Kolab storage format was discussed in 2005. Has this support been added since then? I really don't like Cyrus and would prefer to use Dovecot for my groupware needs.

Hi, I'm working on a Kolab related project and wanted to use dovecot on my dev machine. However I'm stuck with the metadata-plugin. I "solved" the permissions problems but now I get dict: Error: file dict commit: file_dotlock_open(~/Maildir/shared-metadata) failed: No such file or directory Before that, I had dict { metadata = file:/var/lib/dovecot/shared-metadata but

In Dovecot 2.2.4 metadata-plugin crach on setmetadata but worked on ascii folders? but not worked on utf7 (non ascii) folders. [13-Jul-2013 19:15:36 +0400]: [F537] S: A0002 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS

On dovecot 2.2.12 compiled from source I use ActiveSync with kolab-syncroton. When running a test i have this imap log: [29-Mar-2014 22:58:25 +0200]: [F658] S: A0004 OK Getmetadata completed. [29-Mar-2014 22:58:25 +0200]: [F658] C: A0005 SETMETADATA INBOX (/private/vendor/kolab/activesync "{\"DEVICE\":{\"601099122\":{\"ID\":

Hello, Horde (http://horde.org) has the ability to store its preferences direct into a users imap mailbox using imap metadata extension. There are two implementations of the imap extension. 1. a dovecot plugin: http://hg.dovecot.org/dovecot-metadata-plugin 2. dovecot itself: http://www.dovecot.org/list/dovecot/2013-November/093243.html I setup Horde and dovecot-2.2.5 to use this extension and

Hi, I'm trying to use the current version of dovecot as the IMAP server for Kolab and things seem to be working more or less OK, but while working on it I've found a dovecot bug that can probably be fixed quickly by someone familiar with the code. I've found the problem using shared folders, but it is related to ACLs and METADATA. The problem appears when a user only has the

Hi list I currently having troubles to "connect" dovecot (for proxy) to an existing LDAP. If I got the dovecot wiki right only userdb is needed for a proxy setup where the proxy does not authenticate but just forward to the backend for authentication. So I setup the following in dovecot-ldap.conf.ext user_attrs = =password,=y=nopasswd,=y=proxy,mailHost=host user_filter =

On 08/23/2017 07:07 PM, Rupert Gallagher wrote: > I still find impediments to the adoption of any of those "solutions". Too many software dependencies, like PHP, DB, python, and a virtual machine. --- There are two portable file formats for calendar and contacts that work across applications and systems, but no server that can use them, and use them safely. You will need however a

>From a thread with Adrian on llvm-commits I looked a little at cases where DwarfCompileUnit's getOrCreateContextDIE's "fallback to return the CU" didn't fire when a CU DIE was required (ie: when the "getDIE" call actually found the CU before the fallback happened) This seems unnecessary, and any case where we do this (where a metadata node has a non-null