2bdc588e319e5ec0613a934b2917cbdef3c4797f — Clayton Craft 8 months ago 677dd36
content/2021-03-21-notmuch-aerc: reference part 2
1 files changed, 6 insertions(+), 0 deletions(-)

M content/2021-03-21-notmuch-aerc.md
M content/2021-03-21-notmuch-aerc.md => content/2021-03-21-notmuch-aerc.md +6 -0
@@ 4,6 4,12 @@ date = 2021-03-21
tags = ["notmuch", "email"]

## Update:
See [part 2](@/2021-03-21-notmuch-aerc-part2.md) for a better solution.

## Original post:

I recently moved to using [aerc](https://aerc-mail.org/) for email after using mutt (and then neomutt) for some number of years. Today I decided to go beyond a simple maildir for organizing mails locally, and use the notmuch backend for aerc. I use neomutt + notmuch for $dayjob, so I'm no stranger to creating tag 'rules' and searching, etc. What I was unprepared for is that aerc does *not* care about sent mails after pushing them to smtp. Contrast this to mutt and it's `record` setting that will save sent mails to some configured location.

The "[official stance](https://lists.sr.ht/~sircmpwn/aerc/%3C20200812212533.116534-1-andreser%40mit.edu%3E#<20200813053634.solhxjf5jvrsm2jf@feather.localdomain>)" on this seems to be either use a custom send script that saves off the mail to a sent dir, or configure something on your mail provider to store mails in the imap Sent folder. I have been using aerc as the smtp client here, but use msmtp elsewhere. Neither support any mechanism for storing sent mails. I decided that option 2 must be the "easier" route in this case.