gmail +reply-all drops the original message's CC recipients (v0.22.5)

Open
#911 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #923 by @ZIFeIYUuuuuuu — closed without merging

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
cli

Research direction

Start at the gmail +reply-all command and trace how it builds the outgoing message from the original headers. Reproduce the supplied case, then verify the sent message metadata headers; done means the original CC recipients are retained while self is excluded, without requiring additional --cc arguments.

Written by the indexing model from the issue text.

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.

Dominant language
Rust
Stars
32.3k
Forks
2k
Avg merge
16h 3m
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleworkspace/cli

All issues in googleworkspace/cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.