docs(adr-0011): record the mail.gitborg.se sending domain #60
Inga granskare
Etiketter
Inga etiketter
area/backups
area/ci
area/control-panel
area/identity
area/infra
area/observability
area/payments
area/security
area/storage
area/web
blocked
needs-info
needs-triage
ready-for-implementation
type
bug
type
chore
type
docs
type
epic
type
feature
type
task
wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
Inga beroenden satta
Referens
bitborg/bitborg-docs!60
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "docs/mail-domain-adr-0011"
Borttagning av en gren är permanent. Även om den borttagna grenen kan fortsätta existera en kort tid innan den faktiskt tas bort, kan det INTE ångras i de flesta fall. Vill du fortsätta?
ADR 0011 documented
no-reply@email.gitborg.seas the sender for both the portal (Sweego HTTP API)and Forgejo (Sweego SMTP relay), and asserted that
email.gitborg.se"must be a verified Sweegosending domain (SPF/DKIM)".
That is now false. The sending domain moved to
mail.gitborg.sewhen the Sweego credentials werereissued on 2026-07-31. Confirmed against live DNS:
mail.gitborg.secarries the DKIM delegation(
sweego1._domainkey.mail.gitborg.se→…-dkim.sweego.co) and its own_dmarcrecord, whileemail.gitborg.sehas no DNS records left at all.Approach
Recorded as an inline
_Amended 2026-07-31:_note — the convention already used in ADR 0006 —rather than a silent rewrite. The ISMS cites
decisions/as the auditable decision trail for controlA.8.32, so an ADR that quietly revises its factual claims undermines the thing it is evidence for.
The amendment states what the domain was, and that it changed when the credentials were reissued.
The entry also now:
the vaguer "SPF/DKIM";
alerts@on the same domain;forgejo_mailer_fromin bitborg-infra and a hardcoded constant in bitborg-web — and that they cameapart on this move, so a future domain change must touch both repos.
That last point is the part worth having in the ADR: the drift was not a typo, it was a structural
consequence of the sender being defined twice, and the next person to move the domain will hit it
again unless the ADR says so.
1062cdef37dad95231aa