similar to: mdbox import error from read-only filesystem

Hi, you can use INDEX=/writable/path/%u in your mail_location setting to define location for the required index data when importing. Also possibly you would need to define writable location for CONTROL and VOLATILEDIR. see https://wiki.dovecot.org/MailLocation <https://wiki.dovecot.org/MailLocation> Sami > On 14 Jan 2019, at 11.23, hby <hby at hby.hu> wrote: > > Dovecot

I?m considering moving from maildir to mdbox, but don?t quite see how I should do the conversion with minimal downtime. Our userdb is ldap, and the we use this setting to point to the users maildirectory: user_attrs = mailMessageStore=mail=maildir:%$:INDEX=/indexes/%1u/%1.1u/%u,mailQuota=quota_rule=*:storage=%$ i.e. every user has a "mailMessageStore" attribute in LDAP that points to

Hi How can I convert all virtual mailboxes from maildir to mdbox? Manually, one by one, working, but I have a lot ... Virtual users and domains stored in sql database. Thats what I want: mail_location = maildir:/var/vmail/%d/%n/Maildir to mail_location = mdbox:/var/vmail/%d/%n/mdbox Thanks Levi -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s

On 2018-10-05 11:35, Timo Sirainen wrote: > On 4 Oct 2018, at 17.13, Tom Sommer <mail at tomsommer.dk> wrote: >> >> >> On 2018-10-04 15:55, Timo Sirainen wrote: >>> On 4 Oct 2018, at 14.39, Tom Sommer <mail at tomsommer.dk> wrote: >> >>>> Is this correct, and if so are there any plans to move dotlocks etc. >>>> to this

Hi According to the docs, setting VOLATILEDIR will improve I/O performance when using NFS - but as far as I can see, only vsize lock-files are put here, and little else? Is this correct, and if so are there any plans to move dotlocks etc. to this directory? Thanks. -- Tom

On 2018-10-04 15:55, Timo Sirainen wrote: > On 4 Oct 2018, at 14.39, Tom Sommer <mail at tomsommer.dk> wrote: >> Is this correct, and if so are there any plans to move dotlocks etc. >> to this directory? > > > What dotlocks? I guess mbox and Maildir have some locks that could be > moved there, but a better performance optimization for those > installations

Hi, I tried to migrate my dovecot 2.2 to a new server with a other storage configuration and dovecot 2.3. New (and old) Server uses mysql for user information I use the following storage settings mail_home = /storage1/vmail/%{userdb:path} mail_location =

> On 10/11/2020 20:07 Daniel Sch?tze <dms at cwa.uk.com> wrote: > > > Dear Aki > Thank you. Unfortunately I'm struggling to get the right syntax for this as it looks like someone else was here too > https://dovecot.org/pipermail/dovecot/2018-July/112441.html > The location in my dovecot.conf is > >

Sendmail 8.14.4 dovecot 2.0.9 I have sendmail working and it is sending mail to /var/mail/%u. I have dovecot working in that I can move emails into IMAP folders and I can send email through IMAP. I have set up dovecot to use mdbox based on the following: mail_location = mdbox:~/mail However, I seem to be lacking a key piece of information. Sendmail is sending the mail to /var/mail/%u as a

I am trying out "mdbox" under Dovecot 2.0beta5. Looking in the "mailboxes" directory under the mdbox storage root ("~/dbox" in my case), I can see that the mail folders are mapped into filesystem directories. But Dovecot seems to put all the message list information ("dovecot.index.cache", "dovecot.index.log") for any given mail folder into a

https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz.sig There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level

https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz.sig There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level

Hello, it's the first time for me writing to the list, I'm trying to change the location into which the Dovecot's locks are done reserving a special temporary directory on an other partition, then adding to the dovecont.conf the line: mail_location = maildir:~/Maildir:VOLATILEDIR=/tmp_lock/%2.256Nu/%u so that through the VOLATILEDIR directive the locks should be written in this

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:

https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz.sig Two more fixes since rc2. And repeating: There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are

https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz.sig Two more fixes since rc2. And repeating: There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are

On 16.10.2017 13:30, Mar?a Arrea wrote: > El 16/10/17 a las 12:25, Aki Tuomi escribi?: >> ITERINDEX is a flag, it's not supposed to have any value. >> >> Aki > So ITERINDEX=yes should be the right value? This is the right > mail_location settings? > >

Hi all, I am just trying to consider my options for storing a large mass of data (tens of terrabytes of files) and one idea is to build a clustered FS of some kind. Has anybody had any experience with that? Any recommendations? Thanks in advance for any and all advice. Boris.

On Thu, Oct 26, 2017 at 7:30 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > On October 26, 2017 at 4:30 PM Federico Bartolucci <federico at aruba.it> > wrote: > > > > > > Hello, > > > > it's the first time for me writing to the list, I'm trying to change the > > location into which the Dovecot's locks are done reserving

There's a bug in "folder delete" for lazy expunge, type "1 namespace", as descibed on https://wiki2.dovecot.org/Plugins/Lazyexpunge When trying to delete a mailbox that still has messages in it, but that has no EXPUNGED/<name> counterpart, the process hangs after the imap "DELETE" command, and the following appears in the log file after a 60s timeout: Jun