mail: reachable MTA-STS policy, and sign bounces and reports

The certificate did not cover mta-sts.rubenhensen.nl, so senders could
not fetch the MTA-STS policy. Add the name, and a port 80 host for its
ACME challenge.

Stalwart signs bounces and DMARC/TLS reports with the DKIM signers named
rsa-<domain> and ed25519-<domain>. Ours were called rsa and ed25519, so
those messages went out unsigned. Rename them.

A new name on the certificate means a new key, so the TLSA record comes
out here and goes back with the new hash after the deploy.
This commit is contained in:
Ruben Hensen committed 2026-11-18 11:00:07 +01:00
1 parent 634cd883e5
commit c0cf02ce86
2 files changed
+16 -13

No files matched your search

-10
View File
@@ -146,13 +146,3 @@ records:
expire: 300
type: TXT
content: "v=TLSRPTv1; rua=mailto:postmaster@rubenhensen.nl"
# DANE for inbound mail: SHA-256 of the public key in the certificate
# for mail.rubenhensen.nl. Renewals keep that key (--reuse-key in
# nix-infra-machine/nodes/node001.nix). To check it against the server:
# openssl s_client -connect mail.rubenhensen.nl:25 -starttls smtp </dev/null \
# | openssl x509 -noout -pubkey | openssl pkey -pubin -outform DER \
# | openssl dgst -sha256
- name: "_25._tcp.mail"
expire: 300
type: TLSA
content: "3 1 1 718809043219a89d490b97503dd176c2557fd67a15679acdfaa0ced7143ee6b8"