It would be nice if the template syntax could be extended to allow specifying attachments. In my case, I currently use several standard templates with attachments (in another email client I'd like to switch from to aerc) which are sent to students when they ask predictable questions.
This is a partial overlap with #108, as one could could then also choose attachments interactively via an external tool using
It would be nice if files to be attached could optionally be selected using an external command (which has to returns absolute paths to the files, one per line). This way, one could use tools like fzf for rapid selection.
It would be nice if templates would have access to the To, Cc and Subject headers of the original message when replying or forwarding.
Background: I use my own mail domain with a catchall account and frequently give out emails of the form email@example.com. When forwarding or replying to such an email, I would like to copy the To or Cc header of the original message to the From header of the reply.
On IRC, doing this via alias globbing was proposed. As there are also some real email accounts at mydoma.in, specifying *@mydoma.in as an alias would not be enough. For example, when replying to an email sent to my father (firstname.lastname@example.org) with me (email@example.com) in Cc should take the From header from Cc instead of To when replying. Therefore, one would at least need to specify a regular expression as an alias. From my point of view, this adds too much complexity, while extending available template fields is a trivial change.
followup: when placing a symlink to my notmuch database directory with the name
.notmuchin my maildir and then specifying the maildir as
source, everything works perfectly, so I guess this indeed is a bug.
When trying to use the notmuch backend with separate database and maildir paths, message files are found as paths are created incorrectly. My account.conf reads
[mail] source = notmuch:///path/to/database from = firstname.lastname@example.org query-map = /path/to/query_map default = inbox maildir-store = /path/to/maildir
Folder view says “unable to fetch header” in each row, when trying to open a message the error is
could not get MessageInfo: open /path/to/database/relative_path/to/message_file: no such file or directory
In other words, the message paths are apparently constructed by taking the path given in source and then concatenating the relative path to the message. That last path is relative to maildir-store, however. My notmuch is correctly configured, i.e. issuing
notmuch search --output=files <query>yields the correct paths to the message files.
Maybe this is a configuration error on my side, but if so I don't see it.