similar to: Replication protocol design

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

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

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

Running into a weird issue in a mailbox that has 26+ keywords. In one session, I do this: S: 2 SELECT "INBOX" (QRESYNC (1255685337 78608 [...uids...])) S: [...] S: * OK [HIGHESTMODSEQ 78608] Highest S: * OK [UIDVALIDITY 1255685337] UIDs valid S: 2 OK [READ-WRITE] Select completed. C: 3 UID STORE 48386 (UNCHANGEDSINCE 78608) +FLAGS AAAAAAAA S: * 8 FETCH (UID 48386 MODSEQ (78609) FLAGS

Hi! I have two Dovecot-2.2.13 servers with Dsync Replication: server1 and server2. When I execute 'EXPUNGE' on server1 side, the messages with FLAG \Deleted are expunged only on server1. The message is still present in Server2. Could someone give me a hint reason for this ? Thanks in advance! -- Thiago Henrique ======================================================================

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

Good morning, I use ?doveadm backup -R -m foo -s $state? to create a local mirror of an imapc remote folder. When I run that command, wait for it to finish, deliver a new message to the remote folder, and run that command again, the new message does not get downloaded from the remote. I'll attach the rawlog, doveconf, etc at the end. Allow me first to summarize what I've already

RFC 5162 [3.1] states that a QRESYNC should return all changes in a SELECT/EXAMINE since the given modseq. In the following case, it looks like there is an off-by-1 error somewhere: C: A64 SELECT "TestMailboxTest" (QRESYNC (1224531494 6 1,3:5)) [MMS: MODSEQ given is 6] S: * OK [CLOSED] S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) S: * OK [PERMANENTFLAGS (\Answered \Flagged

Hello, I'd like to follow up on someone else's old thread: http://dovecot.org/list/dovecot/2012-April/082624.html I understand that Dovecot (that 2012 discussion was about version 2.0.18) can return "HIGHESTMODSEQ 1" upon SELECT if persistent modseq tracking was never enabled for a mailbox. I'd like to get a clarification on how to enable proper persistent modseq

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

On Tue, 04 Apr 2017 11:07:26 +0000 Luca Bertoncello <lucabert at lucabert.de> wrote: > Hi all, > > i've got a strange behaviour with a BlackBerry Classic Phone (BBOS > 10.3.2.2876) in combination with Dovecot 2.2.13 while trying to > fetch mails. > > Before burying myself into debugging sessions, i try to get an > understanding if the following is a Client-

Thank you for your thorough report, we'll look into it. Aki On 20.03.2018 16:56, Tomas Forsman wrote: > Hello. > > I seem to have found a race condition, when setting flags on multiple emails > rapidly. 5 commands including login to reproduce. Problem found using mutt in > real world usage. > > Seems to happen both with UID STORE 1:3 and UID STORE 1,2,3 .. > > I

Hi, some of our customers have discovered a replication issue after upgraded from 2.3.7.2 to 2.3.8. Running 2.3.8 several replication connections are hanging until defined timeout. So after some seconds there are $replication_max_conns hanging connections. Other replications are running fast and successful. Also running a doveadm sync tcp:... is working fine for all users. I can't see

Hello, after dealing with shared folder within version 2.0 rc* I started using it with a group of users. user1 shares a folder to user2. user2 has access to messages of this shared folder. After a "random" time (minutes up to several days) user2 doesn't see those messages anymore. user1 (the owner) hasn't changed anything inside this folder. All messages are still in place

Hi there, There seem to be a race condition in IMAP NOTIFY: when two events for the SELECTED mailbox are received soon after one another, sometimes only the first one is being reported to clients that enabled IMAP NOTIFY. On closer look it seems like this is most often reproducible when the delay between the two events is NOTIFY_DELAY_MSECS (500ms). This is with 2.3.4.1 from Debian sid. $

Hi, we're using quota with the maildir backend. When new mail arrives, the quota gets updated. But when mail is expunged, quota stays the same (see imap dialog below). We're using the latest version from hg ( 1.2.13 ). Any ideas? ###quota part from dovecot -n plugin: quota: maildir:User quota quota_rule: *:storage=2000M quota_warning: storage=95%% /usr/local/bin/quota-warning.sh

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

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