similar to: dsync deleting too many emails (sdbox)

Ok, now to work out the precise method (config for the target server and dsync command) to use to perform the migration from the old server to the new one, converting to dbox (s or m, depending on how the other thread discussing this turns out). I'll update the old server to 2.2.10 tomorrow morning so they're both at the same version. So, assuming both servers are running 2.2.10,

Ok... Now that I've got the niggling issues resolved, on to bigger and better things. I want to convert everyone from Maildir to dbox and enable SIS (our users use a lot of large attachments), and after some reading/googling, I think it may be better to use dsync instead of rsync for the actual migration after all since it will do this at the same time as the syncing. If I'm not

Hello, I am running dovecot 2.2.12 Current mail storage is sdbox and I am trying to compress all emails, which works fine, except for a few old mailboxes. If I run the following dsync command "dsync -u flea -o "mail_plugins=zlib" mirror maildir:~/ndbox" It fails with: dsync(flea): Error: Exporting mailbox INBOX failed: Backend doesn't support GUIDs, sync with header

Hello We are now running dovecot 2.0.9 with indexes in a ram disk and maildir storage in a test system. We have the following questions: - If there is a power outage / kernel crash, we will lose the content of ramdisk. We have tested that indexes are regenerated when a user logs in via imap, so e-mail access will be "slower" after a power outage / kernel crash, but

I'm implementing sdbox. In conf.d/10-mail.conf, with "maildir:" mail_location = maildir:/my_mailbox_path/%d/%n mail gets stored in /my_mailbox_path/%d/%n/new/ With "sdbox:" mail_location = sdbox:/my_mailbox_path/%d/%n mail gets stored in /my_mailbox_path/%d/%n/mailboxes/INBOX/dbox-Mails. How do I get rid of the '/mailboxes/' and '/dbox-Mails/' path

Hello, So ive spent the last 45 minutes or so searching the list for dbox stuff, but Im not seeing anything real definitive. My question is basically whether the dbox format is ready for production environment, is sdbox or mdbox more stable/ready than the other or does it matter? What are people's experience/review with running this format (and if you reply can you tell me which one

Hello Jack, yes, I imagine I'll have to do some work on tuning the block size on cephfs. Thanks for the advise. I knew that using mdbox, messages are not removed but I though that was true in sdbox too. Thanks again. We'll soon do benchmarks of sdbox vs mdbox over cephfs with bluestore backend. We'll have to do some some work on how to simulate user traffic, for writes and readings.

I did an hg pull; hg update, and now my Dovecot working copy doesn't build: ../../src/lib-storage/index/dbox/libstorage_dbox.a(dbox-file.o): In function `dbox_file_metadata_get': /home/paulproteus/dnlds/dovecot/src/lib-storage/index/dbox/dbox-file.c:820: undefined reference to `dbox_file_maildir_metadata_get' collect2: ld returned 1 exit status make[3]: *** [imap] Error 1 make[3]:

Hi, some time back we had similar discussions when we, as an email provider, discussed to move away from traditional NAS/NFS storage to Ceph. The problem with POSIX file systems and dovecot is that e.g. with mdbox only around ~20% of the IO operations are READ/WRITE, the rest are metadata IOs. You will not change this with using CephFS since it will basically behave the same way as e.g. NFS. We

Hi:   I did a simple test with Dovecot-2.3.9:            First step : A test account uses mdbox format to store emails with 'mail_location = mdbox:%h/%Ld/%Ln:ALT=%h/altstorage/%Ld/%Ln',           Second step: I adjust 'mail_location = auto:'  and dovecot

Hola, Dovecot: 2.2.16 (6bde7868cffd) That is the rename-it 2:2.2.16-1~auto+43 edition. In the beginning of syncing it caused scary things like: Apr 9 16:24:08 mail dovecot: dsync-server(username): Error: unlink(OX/dbox-Mails/u.10672) failed: No such file or directory Apr 9 16:24:08 mail dovecot: dsync-server(username): Error: unlink(ox/mailboxes/INBOX/dbox-Mails/u.10927) failed: No such file

Hi Dovecot peeps, I'm enjoying running /usr/lib/dovecot/imap directly as a PREAUTH IMAP pipe. I find that it outputs log messages whose severity is INFO to stdout. I'm running it as follows: /usr/lib/dovecot/imap -c /tmp/dovecot.conf and I see the following messages output to stdout: * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY

Thanks Jack. That's good to know. It is definitely something to consider. In a distributed storage scenario we might build a dedicated pool for that and tune the pool as more capacity or performance is needed. Regards, Webert Lima DevOps Engineer at MAV Tecnologia *Belo Horizonte - Brasil* *IRC NICK - WebertRLZ* On Wed, May 16, 2018 at 4:45 PM Jack <ceph at jack.fr.eu.org> wrote:

Hello, I'm using Dovecot 2.3.x and using dbox as mailbox storage format, specifically sdbox. I'm getting an error from quota about namespace is not maildir is there a setting I have to use for quota to use the sdbox?

Hi, FWIW this was also reported back in August[1] - experienced with 2.3.2.1 (not sure if earlier 2.3 releases were affected) and currently reproducible with latest 2.3.3 stable release. [1] https://www.dovecot.org/pipermail/dovecot/2018-August/112548.html Cheers, Tony On 2018-10-12 04:26, Pascal wrote: > Hello, > > I use dovecot replication and the sieve scripts are not

I'm sending this message to both dovecot and ceph-users ML so please don't mind if something seems too obvious for you. Hi, I have a question for both dovecot and ceph lists and below I'll explain what's going on. Regarding dbox format (https://wiki2.dovecot.org/MailboxFormat/dbox), when using sdbox, a new file is stored for each email message. When using mdbox, multiple

Hi, I'm trying to use dsync to convert sdbox + sis mailboxes to mbox (mbox is chosen here to "re-attach" the attachments to their original place) # dsync -Dv -u $LOGIN -o "mail_location=sdbox:/zfspool/clone_srv_mail/$LOGIN" -o "mail_attachment_dir=/zfspool/clone_srv_attachments" backup

On 02 Apr 2015, at 03:59, micah anderson <micah at riseup.net> wrote: > > > Hello, > > I'm using 2.2.13 on Debian stable, and I perform regular dsync > backups. Typically if there is an error, dsync can recover from it the > next time it is run, but I've been encountering a new error that doesn't > seem to self-heal: > > # /usr/bin/dsync -u gae

I'm considering to move my mails from maildir/mbox to mdbox. One of my doubts is: how can I restore my mails when something terrribly wrong happens. I understand that I should use doveadm import "backup_location" "mailbox" all. So I try to import with: doveadm -v import "sdbox:~/Mail/dbox-temp/spamcop/reports/" "#Dbox/spamcop/reports" all #Dbox

Gents, I'm relocating mailboxes to a new server. Before switching over to a new server I ran syncing a few times without any issues first I sync files with rsync from the old server to have a local copy, then I sync mailboxes with dsync /usr/bin/doveadm -Dv sync -u $MBOX -R "sdbox:/srv/vmail/temp/srv/srv.bgoperator.ru/${MBOX}:DIRNAME=DbOx-mAiLs" After switching over smtp