made progress on email post
This commit is contained in:
parent
b0a0c69dcc
commit
bb298ad064
GPG Key ID:
5548AD9930655715
95
blog.org
95
blog.org
|
|
@ -276,9 +276,13 @@ From SndChaser...
|
|||
|
||||
*** The Audacity team's response
|
||||
|
||||
*** My opinions
|
||||
Can't decide whether to include this section or not. If you make it all
|
||||
the way down here, let me know what you think.
|
||||
|
||||
-----------------
|
||||
|
||||
*** The privacy policy modification
|
||||
|
||||
https://github.com/audacity/audacity/issues/1213#issuecomment-875274890
|
||||
|
||||
|
||||
** TODO Catchy title about Supernote being "the new paper" :Supernote:Writing:Productivity:Organisation:
|
||||
:PROPERTIES:
|
||||
|
|
@ -482,7 +486,7 @@ allows you to edit the word before adding it just in case the OCR was
|
|||
wonky. Even with my terrible handwriting, I've found that it works very
|
||||
well and I rarely have to make edits.
|
||||
|
||||
*** TODO Pong Isi and Volpeon when finished
|
||||
*** TODO Ping Isi and Volpeon when finished
|
||||
** TODO Migrating repositories between git hosts
|
||||
** TODO A perfect email setup (for me) :Email:Workflow:CLI:Efficiency:
|
||||
:PROPERTIES:
|
||||
|
|
@ -535,7 +539,7 @@ efficient and they will remain my organisation system of choice.
|
|||
|
||||
*** The tools
|
||||
In short, the tools we will be using are...
|
||||
+ [[https://www.offlineimap.org/][OfflineIMAP]] to download our emails
|
||||
+ [[https://isync.sourceforge.io/mbsync.html][~mbsync~]] to download our emails
|
||||
+ [[https://notmuchmail.org/][~notmuch~,]] the primary way emails will be organised
|
||||
+ [[https://afew.readthedocs.io/en/latest/][~afew~]] to apply initial ~notmuch~ tags based on subject, sender, recipient, etc.
|
||||
+ [[https://neomutt.org/][NeoMutt]] to interact with those emails, reply, compose, add/remove
|
||||
|
|
@ -545,44 +549,37 @@ In short, the tools we will be using are...
|
|||
Yes, it's a lot. Yes, it's time-consuming to set up. Yes, it's worth it
|
||||
(in my opinion).
|
||||
|
||||
*** OfflineIMAP
|
||||
*** ~mbsync~
|
||||
As I said above, IMAP is limiting; we need to use some other method of
|
||||
downloading our emails. There's an awesome piece of software called
|
||||
[[https://www.offlineimap.org/][OfflineIMAP]] which is built for exactly this purpose. Its configuration
|
||||
can be rather daunting if you have as many accounts as I do (17) but
|
||||
[[https://isync.sourceforge.io/mbsync.html][mbsync]] which is built for exactly this purpose. Its configuration
|
||||
can be rather daunting if you have as many accounts as I do (19) but
|
||||
it's not /terrible/.
|
||||
|
||||
**** General
|
||||
The following sections are named *Near*, *Far*, and *Sync*. Near and Far are
|
||||
terms mbsync uses to profile /how/ your emails are stored, /where/ they're
|
||||
stored, and how to interact with them. In this guide, Far will our mail
|
||||
provider's IMAP server and Near will be our local Maildir.
|
||||
|
||||
**** Far
|
||||
#+BEGIN_SRC text
|
||||
[general]
|
||||
metadata = ~/.offlineimap
|
||||
accounts = use_exa
|
||||
maxsyncaccounts = 1
|
||||
ui = basic
|
||||
ignore-readonly = no
|
||||
pythonfile = ~/.offlineimap.py
|
||||
socktimeout = 60
|
||||
fsync = true
|
||||
IMAPAccount amo_ema
|
||||
Host imap.nixnet.email
|
||||
CertificateFile /etc/ssl/certs/ca-certificates.crt
|
||||
SSLType STARTTLS
|
||||
User amolith@nixnet.email
|
||||
PassCmd "secret-tool lookup Title amolith@nixnet.email"
|
||||
|
||||
IMAPStore amo_ema-remote
|
||||
Account amo_ema
|
||||
#+END_SRC
|
||||
|
||||
The first big option is ~accounts~; it tells OfflineIMAP what to actually
|
||||
sync. What to put there will be defined further down but ~use_exa~ is just
|
||||
filler text. The example account is ~user@example.com~ and I shortened
|
||||
that to ~use_exa~. ~maxsyncaccounts~ is also fairly important as it tells
|
||||
OfflineIMAP to only pull emails from one account at a time. This is
|
||||
certainly slower than multiple but it's also safer because we'll be
|
||||
running this in the background and don't want many OfflineIMAP processes
|
||||
executing concurrently and interfering with each other. ~pythonfile~ will
|
||||
be discussed later.
|
||||
|
||||
**** Account
|
||||
**** Near
|
||||
#+BEGIN_SRC text
|
||||
[Account use_exa]
|
||||
localrepository = use_exa-local
|
||||
remoterepository = use_exa-remote
|
||||
quick = 10
|
||||
utf8foldernames = yes
|
||||
postsynchook = notmuch new
|
||||
MaildirStore amo_ema-local
|
||||
SubFolders Verbatim
|
||||
Path ~/new-mail/amo_ema/
|
||||
Inbox ~/new-mail/amo_ema/INBOX/
|
||||
#+END_SRC
|
||||
|
||||
In the first block, ~localrepository~ and ~remoterepository~ tell OfflineIMAP where
|
||||
|
|
@ -590,25 +587,14 @@ to look for your emails. ~use_exa-local~ is an arbitrary naming scheme I use to
|
|||
differentiate between the various local and remote accounts. It can easily be
|
||||
swapped with something else.
|
||||
|
||||
**** Repository
|
||||
**** Sync
|
||||
#+BEGIN_SRC text
|
||||
[Repository use_exa-local]
|
||||
type = Maildir
|
||||
localfolders = ~/mail/use_exa
|
||||
sync_deletes = yes
|
||||
|
||||
[Repository use_exa-remote]
|
||||
type = IMAP
|
||||
remotehost = imap.example.com
|
||||
starttls = yes
|
||||
ssl = no
|
||||
remoteport = 143
|
||||
remoteuser = user@example.com
|
||||
remotepasseval = get_pass("use_exa")
|
||||
auth_mechanisms = GSSAPI, XOAUTH2, CRAM-MD5, PLAIN, LOGIN
|
||||
maxconnections = 1
|
||||
createfolders = True
|
||||
sync_deletes = yes
|
||||
Channel amo_ema
|
||||
Far :amo_ema-remote:
|
||||
Near :amo_ema-local:
|
||||
SyncState *
|
||||
Patterns *
|
||||
Create Both
|
||||
#+END_SRC
|
||||
|
||||
The repository sections describe how the emails are stored or retrieved.
|
||||
|
|
@ -817,9 +803,6 @@ If you have a different naming system, you'll have to experiment and try
|
|||
different things; I don't know what KeePassXC's other attributes are so
|
||||
I can't give other examples.
|
||||
|
||||
You could also just use the same method I described in [[*Repository][the Repository
|
||||
section]]! It will work perfectly fine here as well.
|
||||
|
||||
#+BEGIN_SRC text
|
||||
passwordeval gpg -dq ~/.mail_pass/use_exa.gpg
|
||||
#+END_SRC
|
||||
|
|
|
|||
Loading…
Reference in New Issue