coulomb/mail-address-semantics
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

MAS-WP-0003-T03: TEM relay live; service reply authenticated (SPF/DKIM/DMARC pass)

Browse source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 252470@bnt-lap001
Assistant-Session: ad628c8f-4be2-4979-94c9-76c7ed6f8241
This commit is contained in:
tegwick 2026-10-18 13:26:20 +02:00
parent f782de3320
commit 1885c88418
1 changed files with 10 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

12
workplans/MAS-WP-0003-provider-live-test.md
View file

@ -139,8 +139,16 @@ address and what envelope recipient arrives.
the chroot lacked resolv.conf, which is why rDNS showed "unknown".
Tested locally against the real TEM endpoint with dummy credentials:
TLS verified, SASL rejected as expected.
Pending: TEM domain verification and DNS at IONOS (operator), Secret,
redeploy, then the reply send.
Relay login: OpenBao platform/suppliers/scaleway/mas-tem-relay, synced
by ExternalSecret `mas-relay` (ops-mason MASON-WP-0014, CCR-2026-0051).
The ExternalSecret needs explicit target metadata because of
reject-secret-last-applied. The first relay attempt got 535 from TEM
until the operator added the missing TEM IAM policy.
Reply leg 1 (2026-10-18): Gmail → `ticket!callback@` created ticket
GS-85QJ8WC09P. The service reply From
`ticket=GS-85QJ8WC09P@mas.coulomb.social` was accepted by TEM at 11:23:46Z
and arrived at Gmail with SPF pass, DKIM pass (d=mas.coulomb.social) and
DMARC pass. Gmail displays the `=` From address unmodified.
## Forwarding and list paths