aboutsummaryrefslogtreecommitdiffstats
path: root/assets/images
diff options
context:
space:
mode:
authorDanilo M. <danix@danix.xyz>2026-08-20 18:25:31 +0200
committerDanilo M. <danix@danix.xyz>2026-08-20 18:25:31 +0200
commit8fc28de18f903e4bc9d9777589edc819ed9ea996 (patch)
tree4d831ef75a8966c3138fe4634de3a9781f15e758 /assets/images
parent2baf2d4e2c1d8d059a0795bf46596c64c28e01e5 (diff)
downloadqtmaildir-8fc28de18f903e4bc9d9777589edc819ed9ea996.tar.gz
qtmaildir-8fc28de18f903e4bc9d9777589edc819ed9ea996.zip
feat(config): send_command and the [compose] section, item 123
An account's ability to send IS its send_command's presence. Not a separate receive_only key: with one key there is nothing to keep in step and nothing to contradict, and a receive-only account is expressed by omission, which is how one real account here is meant to work. Startup validation follows the startup_query pattern, and is deliberately asymmetric. A default_account that cannot send is warned about, because the user named an account and expects mail to come from it. An installation where NO account can send is not: that is a valid read-only installation, and warning about it would train the user to ignore warnings. Every [compose] key reads through value(key, default) rather than testing contains(), because send_delay_ms = 0 is a real setting meaning 'send at once' that a zero-test would mistake for unset. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015muoUo2GdxmBDSp5vjYcbE
Diffstat (limited to 'assets/images')
0 files changed, 0 insertions, 0 deletions