On Thu, Jun 3, 2021 at 4:04 PM Oswald Buddenhagen <oswald.buddenha...@gmx.de> wrote: > > On Thu, Jun 03, 2021 at 01:44:29PM -0500, Felipe Contreras wrote: > > Path ~/mail/ > > MapInbox inbox > > Inbox ~/mail/inbox > > SubFolders Verbatim > > > >However, it doesn't work, ~/Maildir is used. > > > >If I specify Inbox then it works correctly (I have an inbox inside > >~/mail/). > > > >What's the purpose of MapInbox then? > > > as the manual says, for maildir you should probably use Inbox _instead_
No, the manual says I probably *want* to place Inbox under Path. I do want to place INBOX under Path, and since MapInbox is relative to Path, I take it to mean "./foobar", as opposed to "../foobar". If the manual tried to say something different, it probably needs to be updated. > that implies mutual exclusion. I know it implies exclusion, I just added Inbox to exemplify what I want. > it *should* work if you remove the > Inbox def, but as the manual also says, SubFolders won't work for that > box then. This is not what the documentation says, it says: "this virtual mailbox does not support subfolders", that means subfolders do work just not under MapInbox. Also, it says subfolders, not SubFolders, so it's referring to the concept, not the configuration. > so just remove MapInbox, and you'll likely get what you want. I already get what I want. My question is what is MapInbox supposed to do. Moreover, I don't need SubFolders, I just added it because otherwise mbsync complains about .notmuch directories. This doesn't work: MaildirStore local Path ~/mail/ MapInbox foobar # Inbox ~/mail/inbox # SubFolders Verbatim -- Felipe Contreras _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
