similar to: Expuning & Purging doesn't fully remove emails?

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:

?I managed to figure this out. Just wanted to follow up if anyone in the future encounters the same issue. I am using HAProxy along with dovecot replication. When an email comes in... it is round robin'd to each of the 2 dovecot/postfix servers. I have postfix running on each server and it uses the local dovecot LMTP service for storing the mails. We sometimes get surges of emails(hundreds

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 >

Yesterday I had to recover an e-mail which a user had deleted. If I understand this correctly the message was expunged but not purged (doveadm purge had not been run). This e-mail was clearly still in the mdbox stored with zlib compression as I could tell using the doveadm dump command (doveadm dump -t dbox filename). I could however not reveal the e-mail with the normal doveadm fetch -u

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

To a degree I agree .. given mdbox doesnt delete until purge .. but then would be nice if purge took a dovecot search rather than just ditch everything with refcount=0 ... in that way could say purge everything thats been marked as delete according to a specified criteria. rgds Matt completly unrelated moved mailserver back home and listed on cyren so atm getting bounced by dovecot.fi .. have

I have some users where I'd like to expunge their mail at different times. For example, I may have some users who I want to expunge everything from every folder at 30 days. Others where I'd like to expunge everything at 90 days. And still others where I only want to expunge mail from the Trash and Junk folders, and nowhere else. Is there a way to do some sort of lookup for this? Or

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

Hi Aki, Am 18.09.17 um 11:13 schrieb Aki Tuomi: > On 18.09.2017 12:10, Ralf Becker wrote: >> Am 14.09.17 um 01:07 schrieb Timo Sirainen: >>> On 7 Sep 2017, at 17.42, Ralf Becker <rb at egroupware.org> wrote: >>>> Dovecot 2.2.31 with mailboxes in mdbox format. >>>> >>>> Since a couple of days some mailboxes have the problem, that sieve

Hi, I'm testing Dovecot 2.0rc2 with mdbox mail format and I'm not sure what this exactly means: http://wiki2.dovecot.org/MailboxFormat/dbox Quote from wiki page: ===== Expunging a message only decreases the message's refcount. The space is later freed in "purge" step. This may be done automatically within the session or later in a nightly cronjob when there's less

Hi! When I force-resync a mailbox of mine, I see following output: # doveadm force-resync -u $USER $PATH doveadm($USER): Warning: mdbox .../storage: Inconsistency in map index ($X,$Y2 != $X,$Y2) doveadm($USER): Warning: fscking index file .../storage/dovecot.map.index doveadm($USER): Warning: mdbox .../storage: rebuilding indexes doveadm($USER): Error: mdbox .../storage: Duplicate GUID $G in

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

I noticed today I checked a users mailbox with the mutt command: mutt -f /home/bob/email/ There I saw he had 100 messages that had been deleted but not yet purged from his inbox so they're still using up disk storage on my email server. My question is does Dovecot have a process to automatically delete these messages after a certain period of time? I would like to think that they don't

Hi Aki, Am 18.09.17 um 11:22 schrieb Aki Tuomi: > On 18.09.2017 12:20, Ralf Becker wrote: >> Hi Aki, >> >> Am 18.09.17 um 11:13 schrieb Aki Tuomi: >>> On 18.09.2017 12:10, Ralf Becker wrote: >>>> Am 14.09.17 um 01:07 schrieb Timo Sirainen: >>>>> On 7 Sep 2017, at 17.42, Ralf Becker <rb at egroupware.org> wrote:

On 24/8/20 7:12, Fabien KOCIK wrote: > First, extract user list using doveadm users '*'. > Then process this list to fit your needs (seven parts for a week and a > part processed by week day for example). > Finally, use -u option of doveadm purge into a loop. This is a good idea for installations with tons of users. Good point. I would be personally interested in incremental

Anyone know how to setup dovecot with mdbox so that it can be used through shared storage from multiple hosts? I've setup a gluster volume and am sharing it between 2 test clients. I'm using postfix/dovecot LDA for delivery and I'm using postal to send mail between 40 users. In doing this, I'm seeing these errors in the logs Mar 21 09:36:29 test-gluster-client2 dovecot:

Shot in the dark here...haven't tried it myself so no promises. There's probably a much better way to do this but sometimes a little "brute force" helps. Theoretical steps: 1. Stop all mail processes - both SMTP and IMAP. 2. Use "doveadm sync" to backup the user mailbox, e.g., doveadm backup -u user mdbox:/tmp/usermail 3. Verify /tmp/usermail looks reasonable

Hello Is it a bug in lazy expunge plugin or am I missing something? Dovecot v2.0.1 (c5111fb65b0b) home = /mail/%Ld/%Ln mail_location = mdbox:/mail/%Ld/%Ln/mdbox sources.list - debian (squeeze) .. deb http://xi.rename-it.nl/debian testing-auto/dovecot-2.0 main Config changes - - - plugin { lazy_expunge = .EXPUNGED/ } namespace { type = private separator = / prefix = inbox = yes

Am 14.09.17 um 01:07 schrieb Timo Sirainen: > On 7 Sep 2017, at 17.42, Ralf Becker <rb at egroupware.org> wrote: >> Dovecot 2.2.31 with mailboxes in mdbox format. >> >> Since a couple of days some mailboxes have the problem, that sieve rules >> moving mails to folders stop working and .sieve.log in mailbox shows: >> >> sieve: info: started log at Sep 07