On Mon, Jun 01, 2020 at 11:09:01PM +0200, Uwe Kleine-König wrote:
On Mon, Jun 01, 2020 at 11:55:15AM +0200, Oswald Buddenhagen wrote:
anyway, i think this translates to:
INBOX
INBOX.intlist.customer.AAA
INBOX.lists.barebox
...
so the question whether everything is nested under INBOX is answered with
yes.
I think the above contradicts this guess?
true that, i keep forgetting that maildir++ is a bit funny (see commit
0f24ca31b5fa).
i presume that implies that you have INBOX.private or some such?
Yes, that's the eventual goal. Not sure yet if I want my private mail in
a "private" subfolder or directly in ~/Mailbox.
Maybe the latter isn't easily possible?
if the private mailbox has subfolders, then it could be a problem.
but the asymmetry would bother me too much to even consider it anyway.
how do you access these local mailboxes (which MUA)?
mutt + notmuch.
ok, in this case i would recommend that you don't bother with maildir++,
as that's not native to mutt and would not help in any way.
for mutt alone, i would recommend against true hierarchies at all, as
mutt isn't too good with them, so it's best to use Flatten (which makes
SubFolders entirely irrelevant). the bad news here is that Path not
ending at a folder boundary isn't supported, as you found out yourself
(i actually wanted it a long time ago, but dropped the ball as i
couldn't remember the use case for it). so for the time being, you just
can't have a truly flat folder that aggregates different sources.
anyway, with notmuch, you should have more flexiblity (i never used
notmuch myself, so this is conjecture): you can just have separate
Stores with the Paths ~/mail-{work,private}/ or ~/mail/{work,private}/
(whether you Flatten within them or use SubFolders Verbatim depends
entirely on notmuch's ability to recurse automatically), and still have
them presented as an aggregated flat list.
fwiw, i never tried to aggregate work and private mail - i even have
separate mutt configs which i use via wrapper commands. but a few times
i actually needed to move mails between these "domains", and it was more
bothersome than i'd like, so i might rethink my setup as well.
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
