Fix nood.al SPF record -- missing new mail infrastructure IPs #20
Labels
No labels
blocked
borg-backup
ceph
forgejo
in-progress
infra
netdata
nextcloud
p:high
p:low
p:medium
searxng
service-onboard
swarm-nodes
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
copper/ccnet-prod-devops#20
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
nood.al's SPF record was never updated for the mail migration to
ccnet-wv-mailcow / the wg-box edge relay. Confirmed 2026-07-09 via DNS-over-HTTPS:
This only authorizes the old mailcow VPS IP. It's missing the new
infrastructure entirely -- both the new IPv4 and the IPv6 address. Outbound
mail from nood.al addresses (there's a real mailbox, solsticehorizon@nood.al)
sent through the new edge relay will currently fail SPF.
For comparison, the other three domains (coppercore.net, coppercore.cc,
notify.coppercore.net) were correctly updated and currently read:
nood.al's SPF record should be updated to match that pattern (add
ip4:178.156.194.104/32 and ip6:2a01:4ff:f0:f3d7::1/128 -- keep the old
entries for now per the existing transition approach, prune all old-IP
entries once ccnet-mailcow-ash-1 is actually decommissioned in Phase 5).
DNS is hosted at Hurricane Electric (dns.he.net) -- no API credentials in
this repo, change must be made by hand via the HE.net portal, same as the
other domains' SPF updates during this migration.
Related: mail migration plan (Phase 3/5).