#77 near side subfolders cannot be opened

[Mark Kindred]

I've been using isync/mbsync for years without issue on ArcoLinux. Today, after updating my system (now using v1.5.0), it's throwing errors for all INBOX subfolders:

Error: channel mark@arsnova.cc: near side box INBOX/accounts cannot be opened.
Error: channel mark@arsnova.cc: near side box INBOX/acounting cannot be opened.
Error: channel mark@arsnova.cc: near side box INBOX/admin cannot be opened.
Error: channel mark@arsnova.cc: near side box INBOX/debug cannot be opened.
Error: channel mark@arsnova.cc: near side box INBOX/issues cannot be opened.

I reviewed the path info in my .mbsyncrc to make sure it's OK:

[snip]

MaildirStore mark@arsnova.cc-local
Subfolders Verbatim
Path /home/mark/.local/share/mail/mark@arsnova.cc/
Inbox /home/mark/.local/share/mail/mark@arsnova.cc/INBOX

[snip]

MaildirStore mark@kindred.cc-local
Subfolders Verbatim
Path /home/mark/.local/share/mail/mark@kindred.cc/
Inbox /home/mark/.local/share/mail/mark@kindred.cc/INBOX

Has there been a recent change that'd require me to alter my config?

In the release notes, I see "Maildir Path cannot be nested into Inbox anymore (this was never documented)" I don't think that this affects, me, but I'm not 100% sure.

[Oswald Buddenhagen]

the change doesn't affect you.

for starters, try mbsync -ls -D and attach the output (or mail it privately).

[Mark Kindred]

sent via email

[Oswald Buddenhagen]

weird, i can't see anything obviously wrong.
try mbsync -l -a -D for good measure, and attach/mail the complete config.

[Mark Kindred]

I sent the addl mbsync output and complete config via email. lmk if there's anything else I can provide to debug.

[Oswald Buddenhagen]

ok, thanks.
at least two things are going wrong here:
- INBOX and its subfolders are not listed for the local stores. this is because of commit acd6b4b, which has a bogus rationale. you can work around it by adding INBOX* to Patterns.
- it doesn't try to create the seemingly missing boxes even though you configured that. or it tries, but the error handling is misleading.

[Oswald Buddenhagen]

regarding the second point, it's actually behaving correctly, only the error message is confusing: because the folder is absent (or so it thinks), but the state file is there (in a folder it thinks is absent, heh), it concludes that the folder was deleted. this is distinct from the folder never existing, so it won't attempt to create it. and you didn't configure folder deletion propagation (which would also fail due to the other end being non-empty), so it just complains. i'll try to make the message clearer.

[Mark Kindred]

I added INBOX* to patterns, and everything is working again. Thanks

[Oswald Buddenhagen]

point 1 fixed in 8c781d4f, point 2 in 17c9cc11.