similar to: new mailbox format v2

I've been doing some thinking on a new better mailbox format that'd be faster than mbox and maildir for most common uses. Comments welcome. It won't come to Dovecot v1.0, but I'll probably create another branch to Dovecot CVS where I'll start implementing it and some other possibly destabilizing changes. Generic ------- The point is to have a mailbox format where the mailbox

I don't think anyone uses dbox currently, so the whole format could still be redesigned. So I was thinking about doing two major changes: 1. Rely on index files a lot more. The flags are already stored in index files, so there's no need to waste I/O updating them to dbox files all the time. They could still be updated (if indexes get deleted, the flags aren't all gone), but less

This is about how to implement multiple msgs/file dbox format. The current v1.1's one msg/file design would stay pretty much the same and it would be compatible with this new design. dbox directories with multiple msgs/file would be like: ~/dbox/storage/ has the actual mail data for all mailboxes ~/dbox/mailboxes/ has subdirectories containing mailboxes and their indexes Also since dbox

Hi! I noticed that this command ... : for USERNAME in ${USERS};do /usr/local/bin/doveadm -Dv expunge -u "${USERNAME}" mailbox sa.* SAVEDBEFORE 1d done ... does not expunge mails if ran from crontab. It shows in the Debug output what would have been done, but it doesn't really expunge those mails. This command runs daily, and every day the list of expunged mails (in the Debug

Hi, I've been experimenting with using Lazy_Expunge as a tool to enforce document retention policies (by keeping users from deleting emails forever, instead expiring them after a set time). My problem is, how do I keep the user from deleting/expunging mails *inside the expunge folder itself*? I am using dovecot-1.2.10 built from FreeBSD's ports tree, and I am using the following

Configuration ------------- There could be global and user-specific configuration files, similar to how ACLs work. I think the global virtual mailboxes should be only defaults though, so that users could delete them and create a new mailbox (virtual or non-virtual) with the same name. The global virtual mailboxes could be described in a single file, such as: Trash deleted Work/My Unseen

Changes: - Added goal 8 and rewrote mailbox synchronization plan. - Added new SELECT command to change active mailbox and removed mailbox ID from command parameters Goals ----- 1. If a single (or configurable number of) server dies, no mails must be lost that have been reported to IMAP/SMTP clients as being successfully stored. 2. Must be able to automatically recover from a server

> doveadm expunge -u <user> mailbox '*' savedbefore 30d That doesn't work for me either. The command is accepted, but the messages are not expunged. I guess my search/fetch will just have to return the mailbox name, in addition to other fields, and then I'll need to loop through the mailbox names and perform multiple expunges for each user. I understand the desire to

Hi all, I've run into an issue with in-place mailbox format conversions between mdbox and maildir and wondered if someone could assist. When using dsync to convert a mailbox, the conversion loses a mailbox GUID and produces a warning. This behavior seems to have been introduced between version 2.2.31 and 2.2.32. See below for the full debug output from both versions followed by the dovecot

I'll probably be implementing multi-master replication this summer. My previous thoughts about it are here: http://dovecot.org/list/dovecot/2007-December/027284.html Below is a description of how the replication protocol will probably work. It should work just as well for master-slave and multi-master setups. Comments welcome. I'll write later a separate mail about how it'll be

http://dovecot.org/test/ Again only mbox fixes. I found some more bugs which could have also caused some of the mbox problems that people reported. They were found when I today thought I'd again do a bit of testing with my favourite 1.4GB mbox. Then I thought I might as well see how it compares against UW-IMAP. First a bit of explanations how they work internally: Dovecot 1.0-test24

I'm trying to set up a pop3 server for a project for class, but it keeps giving me the following error: Error: Login user doesn't exist: dovecot Fatal: Invalid configuration in /usr/local/etc/dovecot.conf And I have no clue what's wrong. I've look and modifying the dovecot.conffile for days and I am not having any luck. ## Dovecot configuration file # If you're in a

I just had to write this even while it's not just yet in CVS, but it's only a few fixes away from being committed.. My year long dream has finally came true :) [Summary: Next release will have REALLY kickass indexes] Previously the biggest problem with caching message data in indexes was that we had to do it while syncing the mailbox, before client even saw those messages. This caused

Hello, I have a segfault problem, and I can not resolve myself. The details below (stack trace, config....). Maybe important to reproduce, everithing working well until I connect with SoGo ActiveSync (SoGo web, and other IMAP clients are working well). So maybe the SoGo send something magical command if the user client use the ActiveSyn... (the IMAP debug attached too) Thanks, Balazs Toth

v1.1.0 is finally getting closer, so it's time to start planning what happens after it. Below is a list of some of the larger features I'm planning on implementing. I'm not yet sure in which order, so I think it's time to ask again what features companies would be willing to pay for? Sponsoring Dovecot development gets you: - listed in Credits in www.dovecot.org - listed in

On 12/30/2016 11:03 AM, Michael Fox wrote: >> doveadm expunge -u <user> mailbox '*' savedbefore 30d > > That doesn't work for me either. The command is accepted, but the messages > are not expunged. Huh, it certainly did for me, although I used "all" instead of "savedbefore 30d" since I just wanted to empty the trash. What version of Dovecot?

https://dovecot.org/releases/2.2/rc/dovecot-2.2.33.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.33.rc1.tar.gz.sig There are a couple more small changes still coming, but this should be very close to the final release. I'm especially interested in hearing if there are any problems with doveadm log proxying or with director. We've improved our automated director tests quite a

https://dovecot.org/releases/2.2/rc/dovecot-2.2.33.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.33.rc1.tar.gz.sig There are a couple more small changes still coming, but this should be very close to the final release. I'm especially interested in hearing if there are any problems with doveadm log proxying or with director. We've improved our automated director tests quite a

Not really, as the steps outlined by Timo would not get done. Aki > On 17 February 2019 at 10:56 Joan Moreau via dovecot <dovecot at dovecot.org> wrote: > > > In such case, as long as the API is not upgraded, should > > doveadm index -A -q \* > > be considered a replacement of > > doveadm fts rescan > > On 2019-02-14 16:24, Timo Sirainen via

In such case, as long as the API is not upgraded, should doveadm index -A -q \* be considered a replacement of doveadm fts rescan On 2019-02-14 16:24, Timo Sirainen via dovecot wrote: > Hi, > > The rescan() function is a bit badly designed. Currently what you could do what fts-lucene does and: > - Get list of UIDs for all mails in each folder > - If Xapian has UID that