How email CC's are implemented

--===============2036673411==
Content-Type: multipart/alternative; boundary=001a114aa33a05faa90549c2c944

--001a114aa33a05faa90549c2c944
Content-Type: text/plain; charset=UTF-8

Using RT 4.2. Our experience sending ad hoc CC's entered on the fly is that
the Requestor's do not see evidence of the CC's in their version of that
email. The CC receiver gets in independent email just to them. This leads
to confusion on the Requestor's part... "Did <insert name here> get a CC on
this?". It happens a lot.

The workaround appears to be setting up the CC in People as a permament
feature of the ticket. That way, everyone's heading reflects to To: and CC:
addresses. But it takes extra time, and afterward one may not want to CC
that same person as the thread continues. And I know it's possible to
suppress that.

I just argue that CC acknowledgements in the header should function the
same way, for CC's logged in People and CC's entered directly in the CC
entry form. This appears to not be an option in the config, or I missed it.
Anyone else wishing CC handling was uniform?

Nick

-- 
Nicholas Herlick
President
Herlick Data Systems
[email protected]
Office 909-798-2898
Mobile 951-903-4177

--001a114aa33a05faa90549c2c944
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Using RT 4.2. Our experience sending ad hoc=
 CC&#39;s entered on the fly is that the Requestor&#39;s do not see evidenc=
e of the CC&#39;s in their version of that email. The CC receiver gets in i=
ndependent email just to them. This leads to confusion on the Requestor&#39=
;s part... &quot;Did &lt;insert name here&gt; get a CC on this?&quot;. It h=
appens a lot.<br><br></div>The workaround appears to be setting up the CC i=
n People as a permament feature of the ticket. That way, everyone&#39;s hea=
ding reflects to To: and CC: addresses. But it takes extra time, and afterw=
ard one may not want to CC that same person as the thread continues. And I =
know it&#39;s possible to suppress that.<br><br></div>I just argue that CC =
acknowledgements in the header should function the same way, for CC&#39;s l=
ogged in People and CC&#39;s entered directly in the CC entry form. This ap=
pears to not be an option in the config, or I missed it. Anyone else wishin=
g CC handling was uniform?<br><br></div>Nick<br clear=3D"all"><div><div><di=
v><div><br>-- <br><div class=3D"gmail_signature" data-smartmail=3D"gmail_si=
gnature"><div dir=3D"ltr"><div><div><div><div>Nicholas Herlick<br></div>Pre=
sident<br></div>Herlick Data Systems<br></div><a href=3D"mailto:nick@memsys=
.com" target=3D"_blank">[email protected]</a><br></div>Office 909-798-2898<br=
><div>Mobile 951-903-4177<br></div></div></div>
</div></div></div></div></div>

--001a114aa33a05faa90549c2c944--

--===============2036673411==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

---------
RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
* Paris - April 24-26, 2017
--===============2036673411==--