search for: stacksoft

We are using dbox with lz4 compression and dovecot-lda + sieve for delivery. Mail recieved: Mar 16 06:27:55 mail2 dovecot: lda(svs at example.com): sieve: msgid=<20160316032754.4C89D2C4 at rdbms.oldstable.office.example.com>: stored mail into mailbox 'INBOX' Around 08:14:00 user start his thunderbird with local filters. He found one mail without headers. Around that time user do

Hello, Currently doveadm tool can't be used with read-only source locations because it's trying to create lock files. I'd guess lock files shouldn't be necessary on a read-only media, because no one else is going to change anything while our doveadm instance is running anyway. Example: doveadm import -u test at example.com

Hi everyone, Can someone explain me why dsync need read-write access to source box when pulling data (dsync -R backup)? I am working on migration from Dovecot 1.x with maildir to latest Dovecot 2.2.15 with mdbox and found that there is no way to do this from ro filesystem (got "failed: Read-only file system" on access to /dovecot.index.log). I am wondering is it bug or feature? I

+1 to that idea. Ask the same couple month before during migration from 1.x to 2.x but got no answer from someone who able to change this. On Tue, 17 Nov 2015 10:35:11 +0200 Teodor Milkov <tm at del.bg> wrote: > Hello, > > Currently doveadm tool can't be used with read-only source locations > because it's trying to create lock files. > > I'd guess lock