similar to: Mail process plans: multiple connections in a process + idle processes

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

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

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

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

On 23 May 2017, at 12.10, aduprat <aduprat at linagora.com> wrote: > > Hi, > > I'm an Apache James committer and we are curious to use imaptest in order to validate our IMAP protocol implementation. > I'm using the nightlybuild : imaptest-20170506 > > > I follow the examples given in the /T/ /est IMAP server compliancy/ examples

One more data point Timo: On Tue, Mar 12, 2019, at 9:58 AM, Kostya Vasilyev via dovecot wrote: > Timo, > > On Tue, Mar 12, 2019, at 3:56 AM, Timo Sirainen via dovecot wrote: >> On 10 Mar 2019, at 10.14, Kostya Vasilyev via dovecot <dovecot at dovecot.org> wrote: >>> >>> My mail is stored under ~/mail/.imap (not sure what this format is called), I mean not

Timo, On Wed, Mar 13, 2019, at 12:39 AM, Timo Sirainen wrote: > On 12 Mar 2019, at 10.21, Kostya Vasilyev via dovecot <dovecot at dovecot.org> wrote: >> >> It makes no difference if the IDLE connection does SELECT or SELECT (CONDSTORE) prior to going IDLE. >> >> But then as far as I know (?) - in Dovecot, once any connection uses CONDSTORE ever, even once,

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

On 12 Mar 2019, at 10.21, Kostya Vasilyev via dovecot <dovecot at dovecot.org> wrote: > > It makes no difference if the IDLE connection does SELECT or SELECT (CONDSTORE) prior to going IDLE. > > But then as far as I know (?) - in Dovecot, once any connection uses CONDSTORE ever, even once, Dovecot creates data structures to track MODSEQ values, and those data structures are

Hi Timo - hope things are well :) Playing around with the CONDSTORE (RFC 4551) stuff while testing the IMAP lib I am writing and I think I have found a bug in Dovecot 1.2. RFC 4551 [4] identifies the FETCH response to a MODSEQ request as follows: fetch-mod-resp = "MODSEQ" SP "(" permsg-modsequence ")" with 'permsg-modsequence' defined as:

Hello, I have some doubts about max_mail_process option on dovecot.conf. When I set to 3, only 2 clients can be logged in at the same time. when I set it to 2, only 1 clients can be logged in. Why is the maximum number of concurrent clients is always 1 less than max_mail_process? Is any other process is also counted as mail_process other than imap and pop3? Tony

Hi, I'm an Apache James committer and we are curious to use imaptest in order to validate our IMAP protocol implementation. I'm using the nightlybuild : imaptest-20170506 I follow the examples given in the /T/ /est IMAP server compliancy/ examples https://imapwiki.org/ImapTest/Examples. And I wanted to analyse the errors reported, here are some: Error: user1 at james.org[11]: seq too

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

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

Hi folks! I have set up dsync replication with SSH according to http://wiki2.dovecot.org/Replication with the exception of having system users and calling doveadm dsync-server directly from authorized_keys, because the wrapper script posted on the above site is needless (at least in 2.2.10). However, while the two instances connect well to each other, no synchronisation is performed at all, the

http://dovecot.org/releases/1.2/dovecot-1.2.7.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.7.tar.gz.sig * IMAP: IDLE now sends "Still here" notifications to same user's connections at the same time. This hopefully reduces power usage of some mobile clients that use multiple IDLEing connections. * IMAP: If imap_capability is set, show it in the login banner. + IMAP:

http://dovecot.org/releases/1.2/dovecot-1.2.7.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.7.tar.gz.sig * IMAP: IDLE now sends "Still here" notifications to same user's connections at the same time. This hopefully reduces power usage of some mobile clients that use multiple IDLEing connections. * IMAP: If imap_capability is set, show it in the login banner. + IMAP:

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