[dev] Question about problem with VANISHED CHANGEDSINCE requests.

Michael J Rubinsky mrubinsk at horde.org
Mon Nov 5 16:15:16 UTC 2012


Quoting Michael M Slusarz <slusarz at horde.org>:

> Quoting Michael J Rubinsky <mrubinsk at horde.org>:

> I'm assuming there's only a handful (if any) deletes since 587742.   
> So yes, all of the UIDs from the set should not be returned.  (If a  
> person wanted this, they could issue "UID FETCH 1:* UID (VANISHED  
> CHANGEDSINCE 1)").
>
> There's definitely something wonky going on in the code.  There's a  
> certain tipping point of modseqs where the values become incorrect.   
> For a mailbox with HIGHESTMODSEQ of 54004, I see this:
>
> a uid fetch 1:* UID (VANISHED CHANGEDSINCE 53881)
> * VANISHED (EARLIER) 1:37308,37310:40788,40791:41032,41034:41083
> a OK Fetch completed.
> b uid fetch 1:* UID (VANISHED CHANGEDSINCE 53882)
> * VANISHED (EARLIER) 41029:41030,41047:41083
> b OK Fetch completed.
>
> You can report over at the dovecot list or let me know if you want  
> me to do the same.

Done.

-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6062 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.horde.org/archives/dev/attachments/20121105/266ae15c/attachment-0001.bin>


More information about the dev mailing list