search for: modseq

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: permsg-modsequence = mod-sequence-value ;; per message mod-sequence Unfortunately, Dovecot 1.2 is return...

...ons have different IDs. This allows the sender to easily replace existing IDs to point to new mailboxes without causing any confusion. MBOX: - Mailbox ID - User name - Mailbox name - Mailbox UIDVALIDITY Reply: - [Mailbox UIDVALIDITY] (if changed - command failed) - Mailbox UIDNEXT - Highest modseq If the receiver finds out it has a different UIDVALIDITY, the mailbox requires a full resync. UIDNEXT and modseq can be used to determine if replication servers are out of sync. After mailbox ID has been assigned, the active mailbox can be changed using a command: SELECT: - Mailbox ID Requesti...

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 SELECT on the...

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 enabled. This is because modseqs aren't tracked until client has told us that it wants them. So Dovecot doesn't was...

...on you're planning and make sure that the replication will work in that kind of a setup. So, below's the milestone 1 fully described with a couple of FIXMEs left. The rest of the milestones are described only briefly. 0. Prerequisites: - Change v1.2 CONDSTORE implementation to allocate modseqs differently. Currently log file sequence + offset determines the modseq. This can't work in a cluster since their log files are different. Instead add a new "UIDs [..] have modseq X" transaction log record that gets updated when needed. UID list can be 0 to update higest-modseq. To a...

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 tracking. Per RFC 4551, "A client supporting CONDSTORE.... indicates its willingness to receive mod-sequence updates... by issuing:...

...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 messages that increase whenever the message's metadata changes. I'll probably have to reimplement the way modseqs are calculated, because modseqs will be very useful when implementing replication and the current way just doesn't work with it. If modseq-supporting clients see the current modseqs and later the server gets upgraded to new modseqs, the clients will most likely break. So this change should be...

...servers. It's safe to jump between v1.1 and v1.2 at any time or even have them concurrently accessing the same mailboxes. Dovecot v1.2 has a lot of new IMAP extensions implemented. The biggest change comes from CONDSTORE extension which adds a new concept of "modification sequences" (modseq for short). Each message has a modseq that increases whenever a flag is changed or when the message is expunged. The client can keep track of the highest seen modseq and request only changes done since the modseq. See QRESYNC (RFC 5162) for more information. Dovecot starts keeping track of the mods...

...servers. It's safe to jump between v1.1 and v1.2 at any time or even have them concurrently accessing the same mailboxes. Dovecot v1.2 has a lot of new IMAP extensions implemented. The biggest change comes from CONDSTORE extension which adds a new concept of "modification sequences" (modseq for short). Each message has a modseq that increases whenever a flag is changed or when the message is expunged. The client can keep track of the highest seen modseq and request only changes done since the modseq. See QRESYNC (RFC 5162) for more information. Dovecot starts keeping track of the mods...

...1b)?[0x7f61d9be494b]?->?/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)?[0x7f61d903aec5] and Aug?26?09:33:03?s-imap3?dovecot:?dsync-local(dv.iea-dpc.de):?Error:?/vmail/iea-dpc.de/dv/Maildir/.Projekte.BiSpra.erledigt/dovecot.index.log:?Transaction?log?changed?unexpectedly,?can't?get?modseq Aug?26?09:33:03?s-imap3?dovecot:?dsync-local(dv.iea-dpc.de):?Error:?/vmail/iea-dpc.de/dv/Maildir/.Projekte.BiSpra.erledigt/dovecot.index.log:?Transaction?log?changed?unexpectedly,?can't?get?modseq Can you help me? Gru? Andreas -- IEA Data Processing and Research Center Andreas Fineske ICT...

...ncluding 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 only one or two emails that were removed since the provided MODSEQ value. C: 8 UID FETCH 1:* UID (VANISHED CHANGEDSINCE 587742) S: * VANISHED (EARLIER) 1:119944,119947:123482,123484:128043,128045:130388,130390:130456,130458:132127,132129:135832,135834:136201,136203:136301,136303:136316,136318:138502,138504:140099,140101:141908,141910:142607,142609:142744,142746...

...-------------- VERSION dsync 3 2 Hhostname sync_ns_prefix sync_box sync_box_guid sync_type debug sync_visible_namespaces exclude_mailboxes send_mail_requests backup_send backup_recv lock_timeout no_mail_sync no_backup_overwrite purge_remote Smailbox_guid last_uidvalidity last_common_uid last_common_modseq last_common_pvt_modseq changes_during_sync Nname existence mailbox_guid uid_validity uid_next last_renamed_or_created subscribed last_subscription_change Dhierarchy_sep mailboxes dirs unsubscribes Bmailbox_guid uid_validity uid_next messages_count first_recent_uid highest_modseq highest_pvt_modseq...

Hello, I've found this in the logfile: Sep 7 23:16:55 s-imap3 dovecot: dsync-local(timss.iea-dpc.de): Error: /vmail/iea-dpc.de/timss/Maildir/.Countries.USA/dovecot.index.log: Transaction log changed unexpectedly, can't get modseq Can anyone tell me what is worng? Regards Andreas -- IEA Data Processing and Research Center Andreas Fineske Information and Communication Technology Services Mexikoring 37 22297 Hamburg Tel.: 040/48 500 550 Fax:??040/48 500 501 E-Mail: andreas.fineske at iea-dpc.de Web:??www.iea-dpc.de --

Dovecot builds just fine, but fails the tests in src/lib-index. Note that reverting this commit fixes the issue: https://github.com/dovecot/core/commit/dfa4b048ec9a174a42d6668e94501db2fb70793a $ make check for bin in test-mail-index-map test-mail-index-modseq test-mail-index-sync-ext test-mail-index-transaction-finish test-mail-index-transaction-update test-mail-transaction-log-append test-mail-transaction-log-view; do \ if ! ./$bin; then exit 1; fi; \ done mail index map lookup seq range ...................................... : ok 0 / 1 tests fail...

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 \Delet...

...mian wrote: > Dovecot builds just fine, but fails the tests in src/lib-index. > > Note that reverting this commit fixes the issue: > https://github.com/dovecot/core/commit/dfa4b048ec9a174a42d6668e94501db2fb70793a > > $ make check > for bin in test-mail-index-map test-mail-index-modseq > test-mail-index-sync-ext test-mail-index-transaction-finish > test-mail-index-transaction-update test-mail-transaction-log-append > test-mail-transaction-log-view; do \ > if ! ./$bin; then exit 1; fi; \ > done > mail index map lookup seq range .................................

http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz.sig This release fixes a memory corruption bug related to MODSEQ handling in earlier v1.2 releases. Memory corruption means that it's a security bug and possibly exploitable. MODSEQ code is new in v1.2, so v1.1 and older releases are not affected. Other than that, there is an ESORT bugfix and other fixes that were added to v1.1 branch too. -------------- ne...

http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta4.tar.gz.sig This release fixes a memory corruption bug related to MODSEQ handling in earlier v1.2 releases. Memory corruption means that it's a security bug and possibly exploitable. MODSEQ code is new in v1.2, so v1.1 and older releases are not affected. Other than that, there is an ESORT bugfix and other fixes that were added to v1.1 branch too. -------------- ne...

...rted seeing intermittent dsync failures since upgrading Dovecot to 2.3.11.3-3 (CentOS 8 using the official Dovecot repo). Sep 27 17:49:04 host dovecot[130]: dsync-local(user at host)<5GWFD2CmcF+TJwAAsNnMGQ>: Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync (Modseq 66543 no longer in transaction log (highest=66547, last_common_uid=46346, nextuid=46347)) Sep 27 17:49:04 host dovecot[130]: dsync-local(user at host)<5GWFD2CmcF+TJwAAsNnMGQ>: Error: Remote command returned error 75: ssh <options> doveadm dsync-server -u user at host It seems to ha...

...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 in IMAP command UID FETCH: Invalid CHANGEDSINCE modseq. Following the full conversation. ---- * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot on xxx ready. CIGA1 CAPABILITY * CAPAB...