From 100475665918e5e8c5f58db76d918eba13a0bb02 Mon Sep 17 00:00:00 2001 From: Oswald Buddenhagen Date: Mon, 9 Sep 2019 20:08:28 +0200 Subject: [PATCH] kill TODO item about killing INBOX while it's correct that mbsync doesn't strictly need to support both Inbox and Path in a single Channel due to being able to Group Channels, this "simplification" would have some undesirable effects: - the concept is part of IMAP and provides a certain level of "zero-conf" (in particular via NAMESPACE). having to set up two Stores and associated Channels for one Account to reproduce this functionality would add quite some redundancy to common configurations. - implementing MapInbox and move detection across Channels would add significant complexity. one reason why one would want this change in the first place is to get rid of the ambiguity of INBOX appearing right under Path. this could be avoided by either using a different magic prefix that cannot appear in actual mailbox names, or requiring a prefix for boxes inside path as well. neither approach seems worth the effort, given that nesting "INBOX" under Path causes problems for some other IMAP clients anyway. --- TODO | 6 ------ 1 file changed, 6 deletions(-) diff --git a/TODO b/TODO index f8c6d73..66c9489 100644 --- a/TODO +++ b/TODO @@ -37,12 +37,6 @@ Patterns. function being missing so far - this is needed for move detection, which would work only within one Channel -kill the concept of an INBOX, it is a relic from single-channel operation. -if somebody needs it, he can have two stores with different Paths. the path -can name a single (in-)box (curr. broken with maildir). an empty box name -actually means empty, so the IMAP mailbox should use INBOX for Path (can't -make that the default, as it would mess up the NAMESPACE). - add regexp-based mailbox path rewriting to the drivers. user would provide expressions for both directions. every transformation would be immediately verified with the inverse transform. PathDelimiter and Flatten would become