On Mon, Nov 10, 2025 at 10:05:09AM +0100, Oswald Buddenhagen via isync-devel
wrote:
Why is this such a difficult task for isync?
because MaxMessage doesn't really fit the basic scheme, its
implementation actually comes at a rather significant cost in
complexity; it's easily the most difficult part of the whole codebase.
i don't know if it would be difficult to make it support zero; it
might just work with a few minor changes. patches (with autotests)
welcome.
Found a potential bug in related behaviour: changing ExpireSide on an
account that previously had it set results in an error (".mbsyncstate
does not match ExpireSide setting").
But deleting .mbsyncstate does appear to result in previously-pulled
messages getting pushed to the server correctly.
So not sure if this is a bug.
_______________________________________________
isync-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/isync-devel
