similar to: HIGHESTMODSEQ tracking

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

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- or a Server-specific error in the behaviour: CIGA8 UID FETCH 10009:10035 (UID FLAGS) (CHANGEDSINCE NOMODSEQ) CIGA8 BAD Error

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

Not technically a bug, but a small waste of bandwidth: it seems (at least as of 1.2.10) that if neither CONDSTORE/QRESYNC are enabled dovecot still sends HIGHESTMODSEQ info: a examine Testing.AAA * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $Forwarded impflag0 impflag1 impflag2) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 309 EXISTS * 0 RECENT * OK [UNSEEN 5] First unseen. * OK

Quoting RFC 5465 (NOTIFY): ?If the NOTIFY command enables MessageNew, MessageExpunge, AnnotationChange, or FlagChange notifications for a mailbox other than the currently selected mailbox, and the client has specified the STATUS indicator parameter, then the server MUST send a STATUS response for that mailbox before NOTIFY's tagged OK. [?] If either AnnotationChange or

http://dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz.sig I've been really busy the last few months, as I guess people in Dovecot mailing list have seen since I haven't been very responsive. There are at least some dsync bugs I haven't had time to look into yet. The busyness probably continues for a while more, but the next year is

http://dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.10.tar.gz.sig I've been really busy the last few months, as I guess people in Dovecot mailing list have seen since I haven't been very responsive. There are at least some dsync bugs I haven't had time to look into yet. The busyness probably continues for a while more, but the next year is

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

http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz.sig A few announcements first: I'm now going to start being more strict about not answering Dovecot questions sent to me privately (especially support requests, but also bug reports, feature requests, etc). Often those questions could be answered by other people in the mailing list as

http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz.sig A few announcements first: I'm now going to start being more strict about not answering Dovecot questions sent to me privately (especially support requests, but also bug reports, feature requests, etc). Often those questions could be answered by other people in the mailing list as

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

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

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

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-

Hello, I'm using dovecot 2.3.10 in OpenSUSE and I have configured a master/master replication between two backends, it works well but I have found an issue with the replication of the HIGHESTMODSEQ. When I move a set of message from a mailbox to other, e.g. move 3 messages from INBOX to Junk, the HIGHESTMODSEQ get different on each server, with no errors in the log: [Borrador] 34:34

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:

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

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