commit 2d77a99e3bd9c8df2e0cd668a6b18afcb5997fe0
parent 285263cb72a802e6eac15e096e4124bca8432d09
Author: Michał M. Sapka <michal@sapka.me>
Date: Mon, 3 Jul 2023 11:35:24 +0200
fix: typo
Diffstat:
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/2023/notmuch.md b/content/2023/notmuch.md
@@ -50,11 +50,11 @@ SyncState *
Then type `mbsybc -a`, wait for a few (hundred? depending on the mailbox size) minutes, and voila. Your `~/Mail/gmail/` is now populated with all your messages. Let's break down the config.
-Mbsync(1) assumes two stores exist: local (on your computer) and remote (the IMAP server). A store is a place where mail exists. We have then configured in lines 1-3 and 5-11.
+Mbsync(1) assumes two stores exist: local (on your computer) and remote (the IMAP server). A store is a place where mail exists. We have then configured in lines 1-4 and 6-11.
The remote one is self-explanatory. One thing to remember: some providers will require you to use an app-specific password and reject auth attempts with the normal one. Our password in line 11 can be either a string with the password or an arbitrary command (think `cat ~/my-secret-password` or a CLI password manager).
-The local store is just a definition of local folders to use. It can be anywhere, but `~/Mail` is the standard, and many mail clients will assume that you store your email there.
+The local store is just a definition of local folders to use. It can be anywhere, but `~/Mail` is the standard, anxd many mail clients will assume that you store your email there.
On line 13, we start to define a channel, which is how mbsync(1) works. One store is `far` (remote), while the other is `near` (on your machine). The rest of the config defines behavior. Refer to the manual, but in my case:
- it will create non-matching mailboxes
