Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Subfolders don't sync, error: channel user@mail: near side box INBOX/subfolder cannot be opened #1001

Open
gerazov opened this issue Sep 11, 2024 · 0 comments

Comments

@gerazov
Copy link
Contributor

gerazov commented Sep 11, 2024

After a few days of e-mails gone missing I've found the cause to be an update in isync - sharing here to make it easier to find if anybody gets stuck before the new isync version rolls out.

I have two machines using a mutt-wizard setup that sync IMAP locally. After a couple of days (since I updated my system) I noticed that I couldn't find emails I know I read or sent. It was hard to find the root cause but I finally tracked it down to a bug (feature?) in an update in mbsync (isync) that makes it fail syncing subfolders as it can't read them locally resulting in the error:

Error: channel user@mail: near side box INBOX/subfolder cannot be opened.

To make it work, as Oswald Buddenhagen suggests add "INBOX*" in your ~/.mbsyncrc in the Patterns section, i.e. it should now read:

Patterns * !"[Gmail]/All Mail" !"*fts-flatcurve*" !"*virtual*" "INBOX*"

And don't add an ! before it - it'll invert it, i.e. it wont sync any folders matching the pattern 😅

Also if you're using a dated version of mutt-wizard it would be wise to change the mapping of O in muttrc to show error messages (i.e. delete the 2>/dev/null), since if you're using a single machine you won't be aware that nothing gets updated on your server if you don't open the webclient ...

macro index,pager O "<shell-escape>mbsync -a <enter>" "sync all mail"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant