similar to: v2.1.3 released

I have a situation where I need to migrate e-mails from Outlook 2011 (Mac) to Apple Mail. Having looked at all options, I have resorted to the, perhaps, most difficult way: Create folders on the IMAP server, copy e-mails into them from Outlook, connect Apple Mail and do the reverse. However, I have hit a wall. I am running Dovecot 2.1.2 on FreeBSD, with mdbox storage. In my first attempt, I have

On 1 Oct 2019, at 16.31, Ralf Hildebrandt via dovecot <dovecot at dovecot.org> wrote: > > I set up system copying all mails to a backup system. > > This used to work without a hitch - now in the last few days mails > would pile up in the Postfix Queue, waiting to be delivered using the > lmtp transport into dovecot. > > So dovecot was being slow, but why? After

(Note: I am not subscribed to this ML, so please be sure to CC me in replies.) Hello, I see a strange bug when running dovecot under btrfs with a mailbox in mdbox format. At some point, which can take a few minutes or more than a day, dovecot starts logging pread() failures, like so: Apr 02 23:43:42 thetick dovecot[570]: imap(marcec): Error: pread() failed with file

http://hg.dovecot.org/dovecot-dbox-redesign/ Looks like multi-dbox scales pretty nicely. Even after 100k messages the peak saved msgs/sec is the same as the initial saved msgs/sec, even if the average slows down somewhat. I tested this by first deleting mailbox, then running "imaptest" for a second to get saving to start writing several fields to dovecot.index.cache file. Then ran

I set up system copying all mails to a backup system. This used to work without a hitch - now in the last few days mails would pile up in the Postfix Queue, waiting to be delivered using the lmtp transport into dovecot. So dovecot was being slow, but why? After all, nothing changed. After reading some articles on stackoverflow I found a way of finding out which file gets the most IO: % sysdig

Hello list, we continue our tests using Dovecot on a RHEL 6.1 Cluster Backend with GFS2, also we are using dovecot as a Director for user node persistence, everything was ok until we started stress testing the solution with imaptest, we had many deadlocks, cluster filesystems corruptions and hangs, specially in index filesystem, we have configured the backend as if they were on a NFS like setup

Hello I have found this entries in my log /var/log/maillog.13.xz:Jun 6 17:03:26 buzon dovecot: imap(juanan): Error: mdbox /buzones//18/66/juanan/mailboxes/P7.Bielorrusia/cd-eslpod-enviado/dbox-Mails: Storage keeps breaking /var/log/maillog.108.xz:Mar 4 01:42:09 buzon dovecot: imap(lbandera): Error: mdbox /buzones/0b/11/lbandera/mailboxes/Sent/dbox-Mails: Storage keeps breaking

I'm playing with running dovecot over NFS and I am running into some issues. I have followed the guide at http://wiki2.dovecot.org/NFS and my setup includes 1 nfs server and 1 client running postfix/dovecot. In testing I am running postal via the command: postal -t 10 -c 10 localhost users399 The test file has a list of 399 users to deliver to. I've provided a sample of the errors

Hello all, I am running dovecot- 2.3.5.2 with mdbox storage. I deleted the dovecot.index* from all my folders, which led to mails not being displayed. I rebuilt the indexes for all the users after that, using: doveadm force-resync -u user at domain "*" However, the problem now is that Outlook,configured for IMAP, is not able to sync the mails with the server. I can login to the server

Hi, I am seeing constant "Log synchronization error"s in my logs. See later for an example. This is dovecot 2.2.4, pigeonhole 0.4.1, and postfix 2.10.1 (with mailbox_command = /usr/libexec/dovecot/deliver) on a Fedora 19 system. I am using packages from Atrpms so there are some patches applied - ask for details. The mailboxes have resently been moved from a i386 system. I have

I am seeing the following errors in my logs, which I believe are preventing Outlook from syncing. How do I solve these? Can I just delete the index.cache?? Jun 18 11:23:34 imap(technical at mydomain.co.ke)<59754><g5UC1JSLPhkpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29:

> On 19/10/2020 09:48 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > On Mon, 19 Oct 2020 at 09:27, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > > > On 19/10/2020 09:16 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > > > > Bump! > > > > > > >

Bug Report: We had one of our solr server down for a while, then observed a lot of "Warning: fscking index file " actions. Version 2.2.27 with auto fsck. A follow up investigation shows direct one to one relationship between solr error and subsequent fscking. The fscking lasts for quite a long time (for at least an hour) when the mailbox is concurrently accessed. Thank you. Netfront

On Mon, 19 Oct 2020 at 09:27, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > On 19/10/2020 09:16 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > Bump! > > > > > > On Fri, 16 Oct 2020 at 13:26, Odhiambo Washington <odhiambo at gmail.com> > wrote: > > > > > > > > > > > > On

I'm seeing the following error in our logs when removing mailboxes (we are using mdbox and dovecot 2.1.8): Aug 1 20:03:36 msgsrv dovecot: imap(test at test.com): Error: stat(/mailstore/domains/test.com/test/mdbox/mailboxes/Spam) failed: Operation not permitted Aug 1 20:03:36 msgsrv dovecot: imap(test at test.com): Mailbox deleted: Spam When I run truss against the process it appears the

Hi, I have a "ubuntu10.04 + ext4-filesystem + dovecot-2.0.13 +mdbox" configuration in my server. It works fine with ~50k accounts. Recently happened a filesystem corruption in a device of StMailLocation and I fix with fsck.ext4. After this crash, one account began to show access timeout and errors like this on force-resync: # doveadm force-resync -u account INBOX doveadm(account):

I've updated http://wiki2.dovecot.org/MailLocation regarding a typical mail_location entry for dbox. Previously it said: mail_location = dbox:~/dbox but of course "dbox" is now the old name for "sdbox", so the example should be updated to say "sdbox" and there might/ought also to be an example for "mdbox". In

http://dovecot.org/releases/2.0/dovecot-2.0.4.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.4.tar.gz.sig multi-dbox users: Be careful about the INDEX change. Maildir users: I hope v2.0 is now finally stable. * multi-dbox: If :INDEX=path is specified, keep storage/dovecot.map.index* files also in the index path rather than in the main storage directory. WARNING: if you specified

http://dovecot.org/releases/2.0/dovecot-2.0.4.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.4.tar.gz.sig multi-dbox users: Be careful about the INDEX change. Maildir users: I hope v2.0 is now finally stable. * multi-dbox: If :INDEX=path is specified, keep storage/dovecot.map.index* files also in the index path rather than in the main storage directory. WARNING: if you specified

Hi Aki, thanks for looking into this :) Am 14.08.18 um 15:15 schrieb Aki Tuomi: > can you turn on mail_debug=yes and run doveadm -Dv mailbox delete and > provide output and logs from both servers? root at ka-nfs-mail:~# doveadm -Dv mailbox delete? -u h 'INBOX/Fachbereiche ' Debug: Loading modules from directory: /usr/lib/dovecot Debug: Module loaded: