similar to: Internal 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

> 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! > > > > > > >

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

(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

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):

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:

This has got to be something weird in my config. And the standard disclaimer of '"happy to post doveconf -n, but wanted to see if this is normal first" :) Background: Ubuntu Xenial, running 2.2.36. Mailbox type is mdbox and I've got a period separator in my inbox namespace: namespace { hidden = no inbox = yes list = yes location = mailbox Spam { auto = no

> 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 Fri, 16 Oct 2020 at 13:15, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > > > > > On 16/10/2020 13:11

Here is what I see on the error.log: Oct 15 17:37:58 imap(technical at mydomain.name)<62260><9ucgmLax7s3F6FH2>: Error: Mailbox INBOX: Cache /var/spool/virtual/ mydomain.name/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: Deleting corrupted cache record uid=798: UID 798: Broken physical size in mailbox INBOX: read(/var/spool/virtual/

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

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

I am unable top pop mail from my server, using mdbox: Nov 02 16:35:08 pop3-login: Info: Login: user=<wash at domain.co.ke>, method=PLAIN, rip=192.168.40.79, lip=192.168.40.252, mpid=36052 Nov 02 16:35:09 pop3(wash at domain.co.ke): Error: Corrupted dbox file /var/spool/virtual/domain.co.ke/wash/mdbox/storage/m.1 (around offset=1941): Ex t refs metadata corrupted: 3861 783856

On Fri, 16 Oct 2020 at 13:15, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > On 16/10/2020 13:11 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > > > > > > > On Fri, 16 Oct 2020 at 08:19, Aki Tuomi <aki.tuomi at open-xchange.com> > wrote: > > > > On 15/10/2020 18:14 Odhiambo Washington <odhiambo

Hello I have read carefully about dbox (/http://wiki2.dovecot.org/MailboxFormat/dbox/) and I have some questions: - One of the main advantages (speed wise) of dbox over maildir is that index files are the only storage for message flags and keywords. What happens when we want to recover some messages from backup? With maildir we can rebuild message indexes, but I am not sure about

Any idea what?pid 7584 is? Aki On 2.9.2019 14.08, telsch via dovecot wrote: > Hello, > > today i got reappearing mails again, but not from purging. In the logs i > only found this. I've got massive problems by many users because > reappearing mails. If you need more information, i could provide. > > > Sep 02 12:58:43 doveadm: Warning: Transaction log file >

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

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

Hi I'm migrating some mailboxes from an old dovecot system where mailboxes are stored maildir uncompressed. I enabled zlib on the new system and migrated an account: doveadm -o mail_fsync=never backup -R -u tonyg imapc: when the account connects to the new system after a while i'm seeing the following error and the mailbox is no longer functioning: Jan 15 13:58:06 S611 dovecot:

Hi all, a dsync failed due a corrupted mdbox file. Force-resync throws the same error. (Dovecot 2.3.9.2) Is there any change to fix/repair the file? dsync-local(LOCALPART at DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Warning: fscking index file /var/mail/12/DOMAIN.TLD/242/LOCALPART/mdbox/storage/dovecot.map.index dsync-local(LOCALPART at DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Warning: