Menu

#83 Path cannot be nested under Inbox

1.5.0
cannot-reproduce
nobody
None
unknown
5
2025-03-19
2025-01-26
W_Luis
No

I upgraded isync in debian/trixie and suddenly I'm getting many errors I don't understand:
When I run mbsync <channel> I'm told: Path cannot be nested under Inbox
My .mbsyncrc contained:</channel>

MaildirStore local
Path ~/Maildir/
MapInbox Inbox

I got rid of that message by adding an Inbox line:

MaildirStore local
Path ~/Maildir/
 Inbox ~/Maildir/
 MapInbox Inbox

However, now I have another error:
Maildir warning: ignoring INBOX in /.../Maildir/ Error: channel ...: far side box INBOX cannot be opened.
I made a couple of experiments that didn't work, like removing a slash and writing
Inbox ~/Maildir or writing Inbox ~/Maildir/Inbox orInbox ~/Maildir/INBOX``, but they didn't work (and I have no mailbox named explicitly Inbox nor INBOX). Before todays upgrade mbsync worked without problems and its been 12 years. Recommendations?

Discussion

<< < 1 2 (Page 2 of 2)
  • Oswald Buddenhagen

    the warning suggests that you have a literal "INBOX" folder in your maildir, next to the "Inbox" you actually want. you should delete it after making sure there is nothing worthwhile in it.

    the error is more mystifying, as this shouldn't be even possible with MapInbox. that might be a genuine bug.

    however, your summary line says 4 boxes, while your pattern specifies only 3, so something is inconsistent here.

     
  • W_Luis

    W_Luis - 2025-03-19

    That was it. For some unknown reason I had an INBOX and an Inbox in the local machine, both empty. There was no counterpart in the mail server. I removed them and the warnings are gone. Furthermore, the summary line now says the expected number of boxes. Thanks!

     

    Last edit: W_Luis 2025-03-19
<< < 1 2 (Page 2 of 2)

Log in to post a comment.

MongoDB Logo MongoDB