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

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:46:17 +02:00
parent 5bcf966d7b
commit 80dd6ad286

View file

@ -102,7 +102,7 @@ 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
- 2026-10-18, Gmail web (subjects "Testmail 1-4"): 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
@ -110,8 +110,12 @@ address and what envelope recipient arrives.
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).
- 2026-10-18, Gmail mobile (subjects "Test 2.1-2.4", 08:44-08:46Z): the
result is identical to Gmail web. All four addresses were accepted
unquoted and arrived byte-identical, with the same classification and
app statuses (201/202/202/202).
Still open: Outlook.com, the corporate gateway, and the reply test
(blocked: no outbound mail).
## Forwarding and list paths