search for: obox

...ct-fs drivers, so the RADOS dict driver may not have been necessary to implement if fs-rados was implemented instead (although I didn't check it closely enough to verify). (We've had fs-rados on our TODO list for a while also.) BTW. We've also been planning on open sourcing some of the obox pieces, mainly fs-drivers (e.g. fs-s3). The obox format maybe too, but without the "metacache" piece. The current obox code is a bit too much married into the metacache though to make open sourcing it easy. (The metacache is about storing the Dovecot index files in object storage and effi...

Hi ceph-ers, The email below was posted on the ceph mailinglist yesterday by Wido den Hollander. I guess this could be interesting for user here as well. MJ -------- Forwarded Message -------- Subject: [ceph-users] librmb: Mail storage on RADOS with Dovecot Date: Thu, 21 Sep 2017 10:40:03 +0200 (CEST) From: Wido den Hollander <wido at 42on.com> To: ceph-users at ceph.com Hi, A tracker

As my logs fill up with "imap(user at domain.com): Error: stat(/mail/doman.com/user//.dovecot.sieve/tmp) failed: Not a directory" errors, I followed the advice at https://wiki2.dovecot.org/VirtualUsers/Home and https://dovecot.org/list/dovecot/2016-June/104403.html and set in /usr/local/etc/dovecot/conf.d/10-mail.conf # By default LIST command returns all entries in maildir beginning

...b.com/exoscale/pithos> and Cassandra to get multi data center redundancy and availability. Would it be possible to have multiple Dovecot servers in disparate geographical locations all talking to the same object storage, assuming it's consistent between sites? From what I remember about obox the dovecot servers all keep a copy of the index locally and merge it with a file in the object storage at intervals, is this an issue with our concept? Also does your team have any performance analysis data on the obox plugin, or data on it's use in production?

...o use some kind of a database for storing the permanent state. I'm fine with the first two, but with 3rd I see a lot of problems and not a whole lot of benefit. But if you think of the databases (or even NFS) as blob storage, you can think of them the same as any object storage and use the same obox format with them. What I'm mainly against is attempting to create some kind of a database that has structured format like (imap_uid, flags, ...) - I'm sure that can be useful for various purposes but performance or scalability isn't one of them.

> On Feb 22, 2017, at 2:44 PM, Timo Sirainen <tss at iki.fi> wrote: > > I guess mainly the message sequence numbers in IMAP protocol makes this more difficult, but it's not an impossible problem to solve. Any thoughts on the wisdom of supporting an external database for session state or even mailbox state (like using Redis or even MySQL)? Also, would it help reliability or

...ate: December 16, 2016 at 11:25 PM > Subject: Re: making a plugin encrypt index data > > When we released our encryption plugin, mail-crypt, it's capabilities include fs-crypt. This can be used to encrypt things like FTS indexes and attachments, and with suitable mail storage, such as obox, you can also encrypt indexes. > > To extend this support to dbox or maildir, does require rather involved changes in dovecot core, which currently has no support for fs-api in index handling. This might happen on v2.3 or v2.4, depending. > > I somehow suspect that the work estimate w...

...at mail_home and mail_location should be > >> different. I plan to use this: > > I'm interested about any sources for this ? http://wiki.dovecot.org/VirtualUsers/Home "Home directory shouldn't be the same as mail directory with mbox or Maildir formats (but with dbox/obox it's fine). It's possible to do that, but you might run into trouble with it sooner or later." -- Alex JOST

...vmail vmail 2B May 31 04:14 tmp > > > Any hints as to why this isn't working? It does seem like the right > answer. The answer is in the wiki page you referred to: "Home directory shouldn't be the same as mail directory with mbox or Maildir formats (but with dbox/obox it's fine)." You should set mail_home (where for example the sieve script is saved to) to a different path than mail_location. -- Christian Kivalo

...rs at > least. > > A man can dream. > > Regards, > Tim > > > > Tim, I too have had this dream but it feels very much like people just don't care about Geo-distributed messaging at scale. Since Dovecot now supports storing messages in s3 compatible storage (using obox) I was thinking about extending an object storage app I developed using node.js on top of Cassandra to implement the s3 API and see if that could breath some life into this concept. When time permits I suppose.

...cache-worker(8839): Error: Failed to iterate dovecot1 at test.it/idx/: GET 1/metadata/sandbox/dovecot1 at test.it/idx/?file_limit=25000 failed: 401 Unauthorized Dec 27 10:52:16 mail dovecot: imap(dovecot1 at test.it): Error: user dovecot1 at test.it: Initialization failed: Namespace '': obox: USER-REF: /var/run/dovecot/metacache returned failure Dec 27 10:52:16 mail dovecot: imap(dovecot1 at test.it): Error: Invalid user settings. Refer to server log for more information. Dec 27 10:52:16 mail dovecot: imap-login: Login: user=<dovecot1 at test.it>, method=PLAIN, rip=127.0.0.1,...

...ns that changing a label changes the flag in each physical folder where the mail exists in. This is what we were planning to do for the Dovecot GMail API support. There are some initial patches for b) that would make it efficient to implement, but they don't work right with replication or with obox format, so they didn't get merged. I think I had some thoughts on how to make them work with a different design, which I probably still have somewhere written down. In any case, priority for GMail API support has dropped pretty low. Most people didn't really care about actually having GMai...

We tested dovecot for a fair amount of time and decided finally to put it into production under CentOS 7 (we are running 2.2.10). I just joined the list, so I apologize for what is probably a question that has been answered many times, but I was wondering if there are any plans to implement replication among 3 or more servers (all "masters", as with 2)? As best as I can tell,

dovecot 2.3.6 (7eab80676) FreeBSD 12.0-RELEASE-p5 amd64 I have recently been finding error messages similar to the following in my Dovecot log file: May 26 06:58:32 imap(gerard at seibercom.net)<87791><WvXT+LyJHBCubeH6>: Error: stat(/var/mail/vmail/seibercom.net/gerard/.dovecot.sieve/tmp) failed: Not a directory The message is correct as there is no such directory. The question is

Hello, I'm encrypting mail on disk using a plugin[0], but the index files are not encrypted (specifically the dovecot.index.cache can be read). I want to do is encrypt index on disk, so I'm looking for how a plugin can achieve that by hooking into the right locations. Is that easily possible in a plugin? I can turn off those indexes by passing INDEX=MEMORY, but that isn't possible

...f the index data were stored in an external database, such problems of duplicate messages occurring in a dovecot cluster could be handled by having the cluster ?lookup? the index data using the external database instead of the local copy stored on the server. This sounds a bit similar to the "obox" format that we use for storing emails and indexes to object storage in Dovecot Pro. That isn't open source though.. > If you stored the MD5 checksum of the index files (and even the message files) in the external database, you could also run a background process that would periodicall...

<<[Samba] [ANNOUNCE] Samba 3.2.1 Available for Download.eml>> ********* *BEGIN ENCRYPTED or SIGNED PART* ********* Michael Adam wrote: > That is right: the link creation in source/bin is fixed, > but the installation of the links is still broken. > > It _is_ fixed in the v3-3-test branch which will be used for > 3.3.0 (scheduled for December). The changes to the Make

Hi, I'm almost ready to migrate Courier to Dovecot 2.2.31 but I have one question about home and mail directory. It's good idea to have same directory form home and mail ? Which scenerio will be better and why ? For example: A) Home: /home/doamin/user1 Mail: /home/doamin/user1 B) Home: /home/doamin/user1/home Mail: /home/doamin/user1 C) Home: /home/doamin/user1/ Mail:

Hello, I am in the process of updating my IMAP dovecot installation and I was wondering what is the current state of the art for GMail-like user-defined labels. Are GMail-like user-defined labels now somehow achievable with dovecot? If now, what is missing? Standardized metadata formats? Support in clients? I searched the web a bit but I could not find any activity in the relevant IETF working

Hi, I have been using this setup for years: mail_home = /var/mail/vhosts/%d/%n mail_location = maildir:~ I have since learned that mail_home and mail_location should be different. I plan to use this: mail_home = /var/mail/vhosts/%d/%n mail_location = maildir:~/mail I would like the transition to be transparent for my email clients. I don't want mail/directories/sieve_scripts to