similar to: dovecot local indexes and multiple servers

Hi, could someone answer my following questions about dovecot indexes? - If I delete dovecot indexes, it recreates them without any problem, right? - If dovecot recreates indexes, it does not affect users (they don't have to download all emails again, seen flag is not lost etc.) or is there any problem? - If I use mail_location = ...:INDEX=MEMORY, it recreates indexes every time dovecot is

Hi, On saturday one of our dovecot machines had an OOPS, and we had to powercycle it. When it came up, it did a filesystem fsck (ext4) and fixed a couple things, but nothing in lost+found. Now, about 50 users have a problem where their indexes are corrupted. Dovecot tries to fix them, but for some reason it is failing. The users are seeing their mails duplicated and they cannot delete mails. I

Hello everybody, We are updating our old dovecot 1.1 servers to 2.0. We have a farm os servers, with users in nfs filesystems and indexes in local fs. Mail is stored in maildir format. We don't warrant that a user is always directed to the same server, although our load balancer sends all request from one IP to the same server (during a session time with a inactivity timeout). This is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, I have one thousand virtual users with mdbox mailbox format and 10 GByte quota. I have noticed some performance problem related to I/O (the mailbox disk is a 6TB raid1+0 on ISCSI), so I want to put the index files on a different disk. My actual mail_location is: mail_location = mdbox:/var/vmail/%-1.1u/%u/mdbox and I want to switch

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

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 using mdbox now (Dovecot 2.2.4), with indexes on a separate disk. Works fine, but the directories for indexes are also present in the storage folder, and are empty. Userdb (sql) returns this: home /var/vmail/domains/somedomain/someuser mail mdbox:~/mdbox:INDEX=/mnt/spool/dovecot/index/somedomain/s/someuser And the created directory structure is:

Hello, I'm facing an issue where deleted emails keep re-appearing after my mailbox index gets recreated.??I'm running version 2.2.36 of dovecot, but I tested the same scenario under 2.3.10. I'm also using mdbox, autoexpunge, and using dovecot replication. I've had several instances now where some expunged emails show up again in a mailbox. I noticed this error: doveadm: Error:

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

2017-01-31 13:03 GMT+03:00 Aki Tuomi <aki.tuomi at dovecot.fi>: > >> On January 30, 2017 at 10:53 AM Andrey Melnikov <temnota.am at gmail.com> wrote: >> >> >> 2017-01-30 11:43 GMT+03:00 Aki Tuomi <aki.tuomi at dovecot.fi>: >> > Hi! >> > >> > Please send these to dovecot at dovecot.org instead of us directly. Thank you.

http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz.sig * Pre-login CAPABILITY includes IDLE again. Mainly to make Blackberry servers happy. * auth: auth_cache_negative_ttl default was 0 in earlier v2.0.x, but it was supposed to be 1 hour as in v1.x. Changed it back to 1h. If you want it disabled, make sure doveconf shows it as 0.

http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.6.tar.gz.sig * Pre-login CAPABILITY includes IDLE again. Mainly to make Blackberry servers happy. * auth: auth_cache_negative_ttl default was 0 in earlier v2.0.x, but it was supposed to be 1 hour as in v1.x. Changed it back to 1h. If you want it disabled, make sure doveconf shows it as 0.

Hi Looking for some insight into mdbox index file management and recovery from corruptions. I have a two node cluster on NFS with proxy director in front for user stickness. One node (a nominated master) bidirectionally replicates to a 3rd node on a DR site. We periodically get index file corruptions resulting in rebuilds. However the user experience is poor as messages read/deleted from

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

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

But is that not adviced in the manual[1]? I am also in the process of setting up dovecot behind a haproxy. Still testing with this. I was wondering why one would choose haproxy and not eg dovecot proxy (with director) [1] https://wiki2.dovecot.org/HAProxy -----Original Message----- From: Zelic Bojan [mailto:bojan.zelic at kudelskisecurity.com] Sent: woensdag 26 augustus 2020 23:39 To:

Hi, I use sis to deduplicate attachments, here is my `doveconf -n` ------------ auth_cache_size = 10 M auth_failure_delay = 5 secs auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb auth_ssl_username_from_cert = yes auth_username_format = %Ln default_vsz_limit = 512 M lmtp_rcpt_check_quota = yes mail_attachment_detection_options = add-flags-on-save mail_attachment_dir =

The Dovecot wiki [1] doesn't list either Exim, Postfix or anything else as supporting the dbox. I did some searching in the Exim archives and have found only one message mentioning dbox, sdbox or mdbox. [2] I think an RFC would go a long way towards getting the format supported. Has Timo, or anyone else, considered submitting an RFC to the IETF? My question was how are we going to use it