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

MAS-WP-0003-T03: record Gmail send results

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 10:42:02 +02:00
parent 6518044633
commit 5bcf966d7b
1 changed files with 12 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

13
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: todo
status: progress
priority: high
state_hub_task_id: "b2af3eb2-0d4b-5cea-b033-99d47c938298"
```
@ -102,6 +102,17 @@ Then reply to a service message sent from `ticket=ID@`. For each
combination, record whether the provider's compose form accepts the
address and what envelope recipient arrives.
- 2026-10-18, Gmail (one client; web or mobile not yet recorded): the
compose form accepted all four addresses unquoted. Each arrived 08:40-08:41Z
in its own SMTP session (209.85.x, STARTTLS, BDAT). The envelope recipient
and header To were byte-identical to what was typed: no quoting, no
rewriting, no stripping of `!`, `=` or the `+comments` facet. The gateway
classified them as expected: `ticket!callback` P2 function/callback → 201
created; `ticket=ID` and `ticket=RE=2026-4711` P1 resource → 202;
`ticket=ID+comments` P1 resource, facet `comments` → 202.
Still open: the second Gmail client, Outlook.com, the corporate gateway,
and the reply test (blocked: no outbound mail).
## Forwarding and list paths
```task