problems with gam forward threads

43 views
Skip to first unread message

Brian Gray

unread,
May 22, 2026, 6:04:55 PMMay 22
to

I think that GAM forward threads has two problems:


1) the command sends to the specified recipient (as expected) but also to a recipient that was BCCed in the original message (not expected)


2) the option addorigfieldstosubject adds the recipient of the forwarded message to the subject line instead of the recipient of the original message



Windows 11 10.0.26200 SP0 Multiprocessor Free AMD64

Version Check:

  Current: 7.43.09

   Latest: 7.43.09


Steps to reproduce:


In account fteacher@ send an email to anthony.example@ and BCC fake.student@


Result: The email arrives in both inboxes as expected.


image.png



In account fteacher@ add a label ToForward to the sent message.


Use the command below to forward the email to another account


gam user fteacher@ forward threads bgray@ query label:ToForward addorigfieldstosubject doit


Result 1: the message is forwarded as expected to bgray@ (with original fields added to the subject line) but it is also sent BCC to fake.student@ (a BCC recipient of the original message).  fake.student is not named in the GAM command, and should not receive the forwarded message.


Result 2: the subject line of the message is "Fwd: second test (Original From: Shirley Yujest <ftea...@sstx.org> To: bg...@sstx.org Date: Fri, 22 May 2026 16:22:56 -0500)" - bgray@ is the address that the message was forwarded to - not the To: address of the original message.



This is the header info for the forwarded message as seen by fake.student@.
image.png


--

Brian Gray

unread,
May 22, 2026, 6:22:15 PMMay 22
to GAM for Google Workspace

I just noticed that the command had a syntax error: the keyword recipient|to is missing.  It should have been:

 gam user ftea...@sstx.org forward threads to bg...@sstx.org query label:ToForward addorigfieldstosubject doit

I'm now surprised that that the original command worked at all. I repeated the test with the corrected syntax and got the same unexpected results: the message was still delivered to the BCC recipient of the original message and the subject line still has the wrong text for the To: part of the added fields.

Ross Scroggs

unread,
May 22, 2026, 6:33:09 PMMay 22
to google-ap...@googlegroups.com
Brian,

Send me a private Meet/Zoom invitation and we'll investigate.

Ross
----
Ross Scroggs



--
You received this message because you are subscribed to the Google Groups "GAM for Google Workspace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-man...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-apps-manager/0969738d-676a-48da-9a96-55dcde39a00en%40googlegroups.com.

Brian Gray

unread,
May 23, 2026, 1:26:38 PMMay 23
to GAM for Google Workspace

Bugs were fixed in version 7.43.10.  Docs were updated to indicate that keyword to is optional.

Ross - thanks for the quick help!!
 
Reply all
Reply to author
Forward
0 new messages