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

MAS-WP-0003-T03: reply round trip verified; T03 done

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:28:59 +02:00
parent 1885c88418
commit 8559b70dbd
1 changed files with 14 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -86,7 +86,7 @@ exists, keep replies in the outbox only.
```task
id: MAS-WP-0003-T03
status: progress
status: done
priority: high
state_hub_task_id: "b2af3eb2-0d4b-5cea-b033-99d47c938298"
```
@ -149,6 +149,19 @@ address and what envelope recipient arrives.
`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.
Reply leg 2: the first answer was lost. During TEM setup an MX
`10 blackhole.tem.scaleway.com` had been added at the same priority as
ours, so about half of inbound mail went to Scaleway's discard host
silently. The record was removed at 11:28Z (TTL 3600). Do not add the TEM
blackhole MX to a domain that receives mail. The re-sent answer arrived
11:28:39Z: Gmail replied to `ticket=GS-85QJ8WC09P@mas.coulomb.social`
byte-identical (envelope and To), with In-Reply-To the service
Message-ID and References carrying both. The gateway parsed it as a P1
resource (ticket/GS-85QJ8WC09P); the app returned 200 correlated, and
the ticket thread now holds both messages.
T03 result: no provider/client combination (Gmail web, Gmail mobile, M365
via Outlook mobile and desktop) rewrote, quoted or rejected any test
address, in either direction.
## Forwarding and list paths