<feed xmlns='http://www.w3.org/2005/Atom'>
<title>archsetup/assets/outbox/2026-05-08-protonmail-bridge-cmail-triage.org, branch main</title>
<subtitle>Builds a full dev workstation from a bare Arch Linux install.
</subtitle>
<id>https://git.cjennings.net/archsetup/atom?h=main</id>
<link rel='self' href='https://git.cjennings.net/archsetup/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/archsetup/'/>
<updated>2026-05-09T15:21:36+00:00</updated>
<entry>
<title>feat: add post-install cmail Bridge setup</title>
<updated>2026-05-09T15:21:36+00:00</updated>
<author>
<name>Craig Jennings</name>
<email>c@cjennings.net</email>
</author>
<published>2026-05-09T15:21:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cjennings.net/archsetup/commit/?id=aa8069d6d4b5dd19ebc33bb6f1469b3aa0e4c020'/>
<id>urn:sha1:aa8069d6d4b5dd19ebc33bb6f1469b3aa0e4c020</id>
<content type='text'>
Bridge first-run is interactive, so I put the cmail wiring in a post-install
helper rather than running it inside archsetup. scripts/cmail-setup-finish.sh
handles the post-first-run steps idempotently: it decrypts the encrypted
cmailpass, copies Bridge's self-signed cert to ~/.config/protonbridge.pem,
symlinks the cmail-action triage helper into ~/.local/bin, and enables the
user-level protonmail-bridge service.

I added loginctl enable-linger in essential_services so the user service
survives logout — without it, triaging cmail from a remote agent or SSH
session has nothing to talk to. outro prints a four-step runbook for the
manual steps after reboot.
</content>
</entry>
</feed>
