Repository navigation
gmail +reply-all drops the original message's CC recipients (v0.22.5) #911
Description
Version: 0.22.5 (Homebrew bottle, macOS arm64)
Repro: reply to a message whose headers are From: A, To: me, CC: B, C with:
gws gmail +reply-all --message-id <id> --body "..."
Expected (reply-all semantics): outgoing message addressed to A with B and C kept on CC (all original recipients minus self).
Actual: the sent message has To: A only — the CC header is dropped entirely, silently. Verified by fetching the sent message's metadata headers immediately after. The helper accepts --cc for additional recipients, but the whole point of reply-all is that the original CC set carries without the caller re-supplying it.
Happy to provide sanitised header dumps if useful.
Activity
y4ho0 commentedon Aug 28, 2026
I can reproduce the recipient loss when Gmail returns the header name as
CCorcc:parse_message_headerscurrently matches the exact spellingCc, even though RFC field names are case-insensitive. The later reply-all recipient builder already carriesoriginal.cccorrectly, so a casing mismatch at the parse step produces the reportedTo: A-only message.Could you confirm the
namevalue for the CC entry in the original message'spayload.headersmetadata (values/addresses can remain redacted)? I have a focused fix and regression test locally, but I want to verify that it covers your real message before opening the PR.ZIFeIYUuuuuuu commentedon Sep 9, 2026
I opened PR #923 with a focused fix and regression test: #923. The parser now accepts case-insensitive Cc header names and preserves all recipients.
fix(gmail): match message header names case-insensitively