DEAR PEOPLE FROM THE FUTURE: Here's what we've figured out so far...

Welcome! This is a Q&A website for computer programmers and users alike, focused on helping fellow programmers and users. Read more

What are you stuck on? Ask a question and hopefully somebody will be able to help you out!
+1 vote

I reviewed this article and decided to setup a similar mbsync rule.

But I cannot get the rule for only the Inbox and Sent to work.

Channel work-inbox
Master :work-remote:
Slave :work-local:
# Only sync  Inbox
Patterns Inbox Sent
# Automatically create missing mailboxes, both locally and on the server
Create Both
# Save the synchronization state files in the relevant directory
SyncState *

I have and have had a rule for everything like the work-all example. And I got that working. But for some reason the work-inbox will not sync.

edited by

The configuration looks simple enough, are you sure that Patterns is matching the right folder names? Can you run mbsync --debug and add the output to the question? It could give more information about what's going on.


Good idea, thanks. The output is huge, too long to be useful. So I used diff between my original and this one and it looks like it misses the pattern for "Inbox" even though both mbsync and mutt print that directory as "Inbox". So I tried all upper case and that worked.

Here's the part of the diff from my original that shows it syncing my INBOX. I have truncated that last line due to the length and because PII...

< M: Enter select_box, name=INBOX
< M: Leave select_box, ret=0
< S: Enter select_box, name=INBOX
< S: Leave select_box, ret=0
< S: Called get_box_path, ...

I've found this old thread from 2017 where they suggest that mbsync fails to make the pattern matching for "inbox" case insensitive despite IMAP not having such requirement. It could be that the issue remains unfixed, or you have an old version.

1 Answer

0 votes
Contributions licensed under CC0