From: Matthias A. <mat...@gm...> - 2016-09-02 06:41:46
|
Am 25.08.2016 um 16:20 schrieb Peter Griess: > Nevermind about storing lists for UIDs. I had forgotten about UIDNEXT > and ranged fetches. > > So I think the minimum required state for each folder is simply the > last seen value of UIDNEXT. Given that this is quite a bit different > than the lists of UIDs that are being tracked in fetchids, we may > indeed want a separate file for this stuff. I suppose we could live > alongside the existing fetchids scheme by encoding these values as a > fake UID. In this case, the fetchids file would contain entries like > this the following (with a POP account to start things off to show > contrast): > > pg...@po... some-pop-uid-1 > pg...@po... some-pop-uid-94 > [...] > pg...@gm... some-folder/1234567890/14 > pg...@gm... some-folder/1234567890/17 > [...] > > Peter Hi Peter, not sure if that particular encoding would work, or if rather the folder part, and some IMAP marker, would need to be part of the left-hand-side. I also wonder how widespread UIDNEXT support in server implementations is. Given that this is for fetchmail 7.0, I'd also consider overhauling the file format in general because it's highly redundant, yet at the same time not very easy to maintain regarding abandoned accounts (their data will never be removed automatically). Cheers, Matthias |