similar to: plugin development guide for non-FS backing store

I would like to develop a new mailbox format for a very specialized application. Can anyone point me in the appropriate direction to get started writing a plugin? More detail for anyone interested: I need to store mail in a format that's quickly accessible and modifiable to an external process. This is for a very low-volume mail system (averaging less than 50 messages stored at any one

To all, I was wondering if it was possible to setup samba shares that use subversion as a backing store for the files. Whenever a new file is created it is added to the subversion tree, whenever a file is opened it is checked out of the subversion tree, and whenever it is deleted it is removed from the subversion tree. The idea is that one could use subversion to retain previous versions of

Hi, I'm new to this list, so first thanks for the dovecot tool! So far, it has been great to work with. Currently, I'm developing a scrambler plugin for dovecot, that should stores the mails encrypted. To do that, I've created the scrambler_ostream and scrambler_istream that does the encryption and that I hook in the mail storage process. The scrambler_ostream is stacked on top

I''m looking to move our file storage from Windows to Opensolaris/zfs. The windows box will be connected through 10g for iscsi to the storage. The windows box will continue to serve the windows clients and will be hosting approximately 4TB of data. The physical box is a sunfire x4240, single AMD 2435 processor, 16G ram, LSI 3801E HBA, ixgbe 10g card. I''m looking for suggestions

??????? Original Message ??????? On August 8, 2018 1:08 AM, Adi Pircalabu <adi at ddns.com.au> wrote: > - rsync may not be the best option depending on the format of mailboxes. If you're using maildir or maildir+ that's fine, but what about mbox or dbox ?

Hi, There''s something really bizarre in ZFS snaphot specs : "Uses no separate backing store." . Hum...if I want to mutualize one physical volume somewhere in my SAN as THE snaphots backing-store...it becomes impossible to do ! Really bad. Is there any chance to have a "backing-store-file" option in a future release ? In the same idea, it would be great to

Hi, we run a Red Hat EL 5.2 mailserver with dovecot as the imap server. Mails are stored in mbox format and there are about 134GB of mail. At the moment users copy their importent mail to their workstation accounts wich are backed up nightly. What are your suggestions to back up the mails not copied? Thanks for any comments. BTW: Dose changing the mailbox format from mbox to Maildir or dbox

My webserver also houses our mailserver. There's about six users on that mail system and I'm thinking it would be good to back up the mailboxes to my always on HTPC computer at home, which is reachable via a dynamic IP service. I know (or think) I need to use doveadm-backup for this but rather than reinvent the wheel (or use the wrong wheel altogether) I'm wondering if anyone can

I am currently running v1.1.20 and was wondering if there is any compelling reason to upgrade to v1.2 or v2.0? For example is there any security updates in v1.2 or v2.0 that aren't included in v1.1.20? The other major thing I would be interested in knowing is there any speed enhancements in the newer versions? I am using basic PAM Auth and Maildir mailboxes on a Linux box. Let me know

I posted this to the forums a little while ago but I believe the list was split at the time: Does anyone have any recommendations for changing the ZFS volblocksize when creating zfs volumes to serve as VMFS backing stores? I''ve seen several people recommend that the volblocksize be set to 64k in this situation- but without much explanation. What are the advantages and disadvantages to

I merged all the new features and latest v1.1 changes under one tree: http://hg.dovecot.org/dovecot-1.2/ The changeset order is kind of weird though. The timestamps jump all around. Wonder if there's a way to reorder them so that it looks more sane.. The status of the new features: 1. CONDSTORE extension is probably the largest change. It adds new "modification sequences" for

Hi, currently most people store their messages in some sort of folder hierarchy, so that they can find them later easily. Here, for example, mails that are connected to a project are being stored in /CompanyName/ProjectNumber folders. Now I was wondering if there is any reason against using tags instead of a folder hierarchy, because tags are better when it comes to mails that belong to

So, I was attempting to use qemu snapshots with backing stores. The QEMU docs (http://wiki.qemu.org/Documentation/CreateSnapshot) make it sound like you simply point your qemu at the snapshot after it's creation, and you're golden. When attempting this with libvirt, though, it fails. I created a snapshot using the above tutorial. the resulting file is disk.0, and a qmeu-img info on it

Hi! I want to redirect all http and https traffic from my LAN to squid in DMZ - transparent proxy. How do I do that? Regards, Sasa

Hi I intend to write a new virtual backend for dovecot. Are there any hacking docs describing how the code is organized, eventually also important structs and how to hook myself into the system, or do I have to go the classical way? Thanks --Flavius

Last night I enabled imap_quota so dovecot could report usage reported by disk quota. I don't intend to actually use the quota plugin to place any limits anytime soon though. How much overhead does this add to normal operations that allocate disk space? Ideally I'd like a situation where the only overhead is incurred when the user uses the mail client to specifically check their usage.

Thanks Yassine, My / is mounted from /dev/vda1 with the following options: [root at mail ~]# cat /etc/mtab |grep "vda1 " /dev/vda1 / ext4 rw,relatime,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group 0 0 Regards, - Eric Grammatico _/) 13 mars 2019 10:31 "Yassine Chaouche via dovecot" a ?crit: On 3/13/19 10:14 AM, Eric Grammatico via dovecot wrote: [...] Mar 11

Here is attached. - Eric Grammatico _/) 13 mars 2019 11:29 "Aki Tuomi" <aki.tuomi at open-xchange.com> a ?crit: > Can you try > > strace doveadm quota get -u victim > > and post the output of this? > > Aki > > On 13.3.2019 12.11, Eric Grammatico via dovecot wrote: > >> Looks working. >> >> [root at mail ~]# ls -lh / >>

On 3/13/19 2:10 PM, Eric Grammatico via dovecot wrote: > Thanks Aki, > > Please find attached strace for imap and quota-status which report an error at the end. > > Regards, write(2, "/usr/libexec/dovecot/quota-statu"..., 57/usr/libexec/dovecot/quota-status: invalid option -- 'u' Please retry with the good options (-u is invalid) Yassine.

The error is generated when a user get connect from a client (RainLoop, a web UI). I don't know if the client request the quota or if it's automagically pushed from the imap process. I'd say the client requests. My problem is the process imap generating the error is launched just before and stopped right after the error is raised and thus quite difficult to trace the process. - Eric