chore(secrets): new POSTFIX_SENDER_ALERTS_APIKEY after Zedmail rejected the old one #133

Merged
jfraeys merged 1 commit from jfraeys/chore/alerts-sender-key into main 2026-10-13 17:43:04 -04:00
Owner

Brings the vault in git in line with production. Zedmail answered SASL 535 Authentication failed for the alerts@ sender (the old key was a copy of ZEDMAIL_API_KEY); the operator generated a new key for alerts@, stored it and redeployed Postfix, after which the queued test mail went out (status=sent, 250 OK) and arrived in the inbox.

Only POSTFIX_SENDER_ALERTS_APIKEY differs from main (checked by key name; the script refuses anything else); the value appears nowhere. Deploys nothing and touches no staged path, so no staging run starts.

After merging: git restore secrets/vault.sops.yml (backup of your local copy: ~/.local/state/infra/vault.sops.yml.local-alerts-key-2026-10-13), git pull.

🤖 Generated with Claude Code

Brings the vault in git in line with production. Zedmail answered SASL 535 Authentication failed for the alerts@ sender (the old key was a copy of ZEDMAIL_API_KEY); the operator generated a new key for alerts@, stored it and redeployed Postfix, after which the queued test mail went out (status=sent, 250 OK) and arrived in the inbox. Only POSTFIX_SENDER_ALERTS_APIKEY differs from main (checked by key name; the script refuses anything else); the value appears nowhere. Deploys nothing and touches no staged path, so no staging run starts. After merging: git restore secrets/vault.sops.yml (backup of your local copy: ~/.local/state/infra/vault.sops.yml.local-alerts-key-2026-10-13), git pull. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
chore(secrets): new POSTFIX_SENDER_ALERTS_APIKEY (the old key was rejected by Zedmail with 535)
All checks were successful
Secret scan / scan (pull_request) Successful in 15s
6530355942
Encrypted vault only; the value is not shown anywhere. Postfix already runs with the new key (operator redeployed it).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jfraeys/infra!133
No description provided.