Re: [Dovecot] Trying to get metadata plugin working
Hi Thomas and List! Am Montag, 16. Januar 2012, 16:51:45 schrieb Thomas Koch: dict: Error: file dict commit: file_dotlock_open(~/Maildir/shared-metadata) failed: No such file or directory The dovecot-metadata is still a work in progress, despite my earlier message reading differently. I assumed because Akonadi began to work (my telnet tests were already successful since a while), that the dovecot plugin would also work, but noticed later that everything was a coincidence. Anyway, my config is: plugin { metadata_dict = proxy::metadata } dict { metadata = file:/var/lib/dovecot/shared-metadata } This appears to work for me - I think the key is the proxy::. --Dennis signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] Trying to get metadata plugin working
On 16.1.2012, at 17.51, Thomas Koch wrote: dict: Error: file dict commit: file_dotlock_open(~/Maildir/shared-metadata) failed: No such file or directory It's not expanding ~/ dict { metadata = file:~/Maildir/shared-metadata Use %h/ instead of ~/
Re: [Dovecot] Trying to get metadata plugin working
Timo Sirainen: Use %h/ instead of ~/ Hi Timo, it doesn't expand either %h nor %%h. When I hardcode the path to my dev user's homedir I get a permission error. After hardcoding it to /tmp/shared-metadata the file gets at least written, but the content looks strange: shared/mailbox/7c2ae515102e144f172dd1887b74/shared//vendor/kolab/folder- test true Best regards, Thomas Koch, http://www.koch.ro
Re: [Dovecot] Trying to get metadata plugin working
On 16.1.2012, at 20.26, Thomas Koch wrote: Timo Sirainen: Use %h/ instead of ~/ Hi Timo, it doesn't expand either %h nor %%h. Oh, right, wrong place. If you make it go through proxy, it doesn't do any expansion. It's then accessed by the dict process (which probably runs as dovecot user). You could instead use something like: metadata_dict = file:%h/Maildir/shared-metadata When I hardcode the path to my dev user's homedir I get a permission error. After hardcoding it to /tmp/shared-metadata the file gets at least written, but the content looks strange: shared/mailbox/7c2ae515102e144f172dd1887b74/shared//vendor/kolab/folder- test true I haven't really looked at what the metadata plugin actually does..