similar to: Per-user flags/indexes for shared mailboxes

As I see in 2.0 there willn't be ability to control which flags should be shared, and which should be per-user. But may be there is some plans to implement settings to control that? It'll be great if you can write in dovecot-shared file which flags should be per-user. It's very usefull for group mailboxes, when each user should work with such mailbox like with their own. Now I

5 milestones planned currently. I'll start with the always-on multi-master replication, because that's the most difficult one to get working correctly and efficiently. So if during its implementation I find some design problems, less code needs to be fixed. Milestone 0 will hopefully be done within a month. This includes reading and replying to the rest of the mails on this list and

I wrote a mostly-working CONDSTORE support for Dovecot today. You can try it with: hg clone http://hg.dovecot.org/dovecot-condstore/ There are a few problems left: - STORE FLAGS.SILENT should be sending FETCH MODSEQ updates - When SELECTing a mailbox while CONDSTORE hasn't yet been enabled in the session, Dovecot returns a higher HIGHESTMODSEQ than what's used after CONDSTORE is

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

I drove over 2000 miles in recent days, so I had some time to think about future Dovecot things. :) Maybe for v2.1 or v3.0, whichever I happen to release next. Here's the first thought: The main idea behind mailbox list indexes was to make getting STATUS information for mailboxes from a single index file. The code was already written for Dovecot v1.1, but it was disabled because of bugs I

http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz.sig This is the only v1.2.alpha announcement I'm going to send to dovecot-news list. Next announcement will be for either v1.2.beta1 or v1.2.rc1. I'm hoping that v1.2 stabilizes pretty soon. There are no huge changes like there were in 0.99->1.0 or

http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz.sig This is the only v1.2.alpha announcement I'm going to send to dovecot-news list. Next announcement will be for either v1.2.beta1 or v1.2.rc1. I'm hoping that v1.2 stabilizes pretty soon. There are no huge changes like there were in 0.99->1.0 or

Hello, try to compile current dovecot2 beta on older machine with gcc 3.3 Compiling results in error: libtool: link: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -o .libs/imap-login client.o client-authenticate.o imap-login-settings.o imap-proxy.o ../../src/login-common/.libs/libdovecot-login.so

I merged all the new features and latest v1.1 changes under one tree: http://hg.dovecot.org/dovecot-1.2/ The changeset order is kind of weird though. The timestamps jump all around. Wonder if there's a way to reorder them so that it looks more sane.. The status of the new features: 1. CONDSTORE extension is probably the largest change. It adds new "modification sequences" for

Hi all, I've done a bit of searching and haven't seen anybody else coming across this problem yet: I noticed that Dovecot uses the opposite flags for marking messages as deleted and draft to most other MUAs I've seen or used: With PINE, mutt and uw-imapd at least, messages are marked with X-Status 'D' for Deleted, and 'T' for drafT. Dovecot reverses this behaviour,

We use a pair of replicating Dovecot servers. If a user subscribes to a folder, shared by an other user, in one replica, that does not get replicated to the other node. Subscription of regular folders below INBOX seem to replicate correctly. Is that a general bug, a known problem or do we need to enable that somehow. Here's our configuration for the concerned namespace: namespace users { ?

Hello, i have a dovecot server version 2.3.1 under CentOS 6.9 and we're using shared mailboxes with index files shared. With this configuration I can see a lot of error messages like: Jun 6 13:20:31 mail dovecot: Error: imap(userA at tutech.de)<4513> <onjjWPdtDuLAqG3R>: /export/home/imap/userA at tutech.de/shared /userB at tutech.de/folder/dovecot.index.pvt view is

Here's a list of things I've been thinking about implementing for Dovecot v2.2. Probably not all of them will make it, but I'm at least interested in working on these if I have time. Previously I've mostly been working on things that different companies were paying me to work on. This is the first time I have my own company, but the prioritization still works pretty much the same

Hello, Do you have recommendations on EXT4 and LVM options for a 3TB file-system for mdbox? We currently use the mbox format on a XFS with poor performances since the update in v2.1 (Debian). We will switch to EXT4 to have the possibility of shrinking the file-system if needed (which is not possible with XFS), we currently have LVM partitions but with mdbox we will use LVM snapshots to

I've been seeing the following wonky behavior with Dovecot. Currently this is with Dovecot 2.0.19, but I was also seeing it in earlier versions as well, including versions from the 1.x series. Some background, this is from Horde's ActiveSync library, when it is trying to determine what UIDs have recently been expunged. I can guarantee that when this command was sent, there was

Before beginning to code it, does anyone have any related ideas that could be useful before starting it? Mainly what I'm intending to do is to write a plugin for mdbox storage that allows users to expunge mails in a specific namespace only if there are other instances for the mail. So basically: * Users can't accidentally delete mails (in shared mailboxes) * Users can still move mails

Greetings, I'm new to the list. I have encountered what I believe to be a bug in the return of HIGHESTMODSEQ when talking to a IMAP client. HIGHESTMODSEQ does not appear to be incrementing when a new message arrives. The exact steps I took are: 1) Create a new mail account 2) Send a mail to the account, check that you can receive the email. Send a second mail to the account. 3) perform a

Maybe for v2.1: imap and pop3 processes can currently handle multiple connections, but they're assigned pretty much randomly to processes. It would be better if it was possible to: a) Require that a process handles only a specific user's connections b) Require that a process handles only a specific UNIX UID's connections (e.g. if each domain has a separate UID) c) Prefer to put

On 2015-06-24 13:03, Nicolas C. wrote: > Hello, > > Do you have recommendations on EXT4 and LVM options for a 3TB > file-system for mdbox? > > We currently use the mbox format on a XFS with poor performances since > the update in v2.1 (Debian). What qualifies as "poor performance"? How many users? > > We will switch to EXT4 to have the possibility of

http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc6.tar.gz http://dovecot.org/releases/2.1/rc/dovecot-2.1.rc6.tar.gz.sig I've finally finished all of my email backlog. If you haven't received an answer to some question/bugreport, resend the mail. This is hopefully the last v2.1 RC. If I don't receive any (serious) bug reports about this release in next few days, I'll just change