ci / test (pull_request) Successful in 37s
`inbuxa relay install --token -` puts the relay a server release attaches on this machine: the static inbuxa-relay binary, checked against a checksum pinned here and against the inbuxa release keys' signature in its .sig file, owned by the inbuxa-relay user so an upgrade from the console can replace it, under inbuxa-relay.service as inbuxa-server ships it (ports 25 and 443 and nothing more). It joins with the console's token as the relay's user, starts it, and checks it stays up. It refuses on a machine that runs the mail server, where port 25 or the link's port is held, and on a relay that hasn't joined without a token. Run again it converges: it keeps a binary of its release or a newer one from the console, and the --link-listen an earlier run set. `relay status` is the relay's own status, as its user; `relay uninstall` keeps its state, and --purge resets it first, which refuses while it holds mail unless --discard-held. RelaySHA256 is empty: no release has relay binaries yet, so the command says so until the pins PR for the first one fills it in. INBUXA_RELAY_BINARY installs a local build meanwhile, and e2e/cases/relay-host.sh runs with one (RELAY_BINARY in run.sh).