On Mon, Nov 10, 2025 at 12:33:32PM +0100, Philippe Bruhat (BooK) wrote:
isync's purpose is to keep both sides in sync. MaxMessages is a deviation
from that. when you push that number down to zero, that's _literally_
extreme, and you've gone from syncing to fetching.
Can't the requested workflow be simply scripted as:
- synchronize with isync (getting all the emails from the remote)
- move all the email to a non-synchronized folder (emptying the local)
- synchronize again (removing all emails from the remote)
...yes, I suppose so. Is the MaxMessages code so buggy or poorly tested
that it's necessary, though?
_______________________________________________
isync-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/isync-devel
