diff options
| author | Danilo M. <danix@danix.xyz> | 2026-08-20 11:00:25 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-08-20 11:00:25 +0200 |
| commit | e81e4f09a6a40162d0041253a35777e547d4dd81 (patch) | |
| tree | 264d40a3e799eb91a08aa8ea01cf6d9fadfb4da9 | |
| parent | 241cf9444b36c9f5217778759e98576dc21e58fa (diff) | |
| download | qtmaildir-e81e4f09a6a40162d0041253a35777e547d4dd81.tar.gz qtmaildir-e81e4f09a6a40162d0041253a35777e547d4dd81.zip | |
docs: record what the send side actually has, in item 123
The entry said sending should be an external script on the same model as
mailsync.sh. Measured on the machine, there is no such model to copy: the
fetch side has mbsync and the send side has nothing.
No MTA is installed at all, msmtp and sendmail are both absent, and neomutt
sends over its own built-in SMTP configured per account in
~/.config/neomutt/accounts/*.rc. So the working setup this application
mirrors has no external send path either.
That makes the first question a non-UX one, ahead of everything the note
lists: sending needs either an MTA the user chooses to install and
configure, which is the only shape that keeps the no-network-protocol rule
intact, or a decision to relax that rule. Recorded so the brainstorm does
not assume the tidier answer, since installing and configuring an MTA is
work he has not asked for and the credentials already exist elsewhere.
Also notes that all five accounts already configure a drafts folder, so the
draft half has somewhere to live before anything is decided.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YDq53rMd3AQp7QmcZzpuBM
| -rw-r--r-- | docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md b/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md index b4ca450..49f4000 100644 --- a/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md +++ b/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md @@ -1018,6 +1018,25 @@ multi-recipient field, so there is prior art to reuse rather than a blank page. model, not an SMTP client written here. A design that puts a socket in this process is out of scope regardless of how the UI turns out. +**What exists on this machine, measured 2026-08-20, because the sentence above +assumes something that is not there.** "Sending should be an external script on +the same model" is easy to write and there is no such model to copy: the fetch +side has `mbsync`, and the send side has NOTHING. + +- No MTA is installed at all. `msmtp` and `sendmail` are both absent. +- neomutt sends over its OWN built-in SMTP, configured per account + (`smtp_url` and `smtp_pass` in `~/.config/neomutt/accounts/*.rc`), so the + working setup this application mirrors has no external send path either. +- All five accounts already configure a `drafts` folder, so the draft half has + somewhere to live before anything is decided. + +That is the first question for the user, and it is not a UX one: sending needs +either an MTA they choose to install and configure (msmtp being the obvious +one, and the only shape that keeps the no-network-protocol rule intact), or a +decision to relax that rule. Do not assume the first just because it is +tidier; installing and configuring an MTA is work they have not asked for, and +the credentials already exist in neomutt's files. + **Approach.** Brainstorm first, on its own branch, producing a spec under `docs/superpowers/specs/` before any code. The open questions are all UX, as the note says: where a composer lives, how a draft is stored so `notmuch` can see |