Open duckwork opened 1 year ago
Actually the problem might be in applying the changes to the notmuch database. I'm honestly not sure how to proceed here, but it could be something with my notmuch config. I'll keep this issue open until i figure it out if I can :)
I think I see what's happening here. mujmap unconditionally creates mailboxes for the set of all tags that exist in its database, period, regardless of whether or any mail entries it owns contains them. There are two ways to approach this that jump out to me.
Since the second option is easier, I might do that one first, and then go back to 1 and implement that as well. Thank you for the issue report :)
Awesome, thank you so much!
My notmuch database pulls email from my personal (via mujmap) as well as two work accounts (via lieer). When I try to sync changes with mujmap, it tries to create tags related to work on my Fastmail account and fails.
While debugging while it fails would be useful (I can paste a trace with -vvv if needed), ideally I wouldn't be syncing those tags to Fastmail at all. What do you think about adding a configuration option to ignore certain tags from sync altogether?
If this feature already exists or is possible another way, I do apologize for the duplicate issue!