I enable CC parsing in config.pm. I notice that CC email addresses are
parsed correctly only when the ticket is created. If during the email
thread, new email address is used in the CC field using the email client
when sending out the email, it will not be parsed and stored in the CC
field under the People section at the web interface.
Have you experienced the same thing? I use rt-2-0-14. Any ideas?
Thanks.
Sherrill
Sherrill (Pei-chih) Verbrugge
“The fear of the Lord is the beginning of knowledge” - Proverbs 1:7
I enable CC parsing in config.pm. I notice that CC email addresses are
parsed correctly only when the ticket is created. If during the email
thread, new email address is used in the CC field using the email client
when sending out the email, it will not be parsed and stored in the CC
field under the People section at the web interface.
Not a bug, but how rt-mailgate is setup. The function
ParseCcAddressesFromHead, which does the actual parsing of addresses
from the header, is only called if rt-mailgate was unable to determine a
ticket id.
This patch might do it (untested, though); it adds another call to
ParseCcAddressesFromHead, and calls AddWatcher for each thing it finds.
Unfortunately, it had to be added twice, but hey, this is a 5 minute
hack…
I enable CC parsing in config.pm. I notice that CC email addresses are
parsed correctly only when the ticket is created. If during the email
thread, new email address is used in the CC field using the email client
when sending out the email, it will not be parsed and stored in the CC
field under the People section at the web interface.
Not a bug, but how rt-mailgate is setup.
As a word of warning, it’s this way by design. If it were set up such
that you could be added as a Cc just by ccing yourself on a ticket
update, the system would be open to an attack which let random third
parties grant themselves “Cc” role rights to a ticket.