Couldn’t tell you to be honest. I don’t know if people within the organization
are doing it or customers that send tickets in.
Keep up with me and what I’m up to: http://theillien.blogspot.com
Matt Westfall wrote:
Is it happening from a large base of submitters? or just one or two?
Mathew Snyder wrote:
Unfortunately, this is an impractical solution. I’d have to contact every
single one of our customers and ask that they change their email client if that
is even possible.Keep up with me and what I’m up to: http://theillien.blogspot.com
Matt Westfall wrote:
The best thing to do might be to fix the e-mail client that’s separating
e-mail addresses with semicolons instead of the RFC dictated commas.Mathew Snyder wrote:
For some reason we have a slew of users which are in the format
user1;user2;user3;user4. These users are labeled as “Autocreated when added as
a watcher” Presumably, either when someone was creating a ticket directly in RT
or forwarding an email to RT in order to automate the creation, these users were
inserted into the one of the email-recipient fields. Doing so, again
presumably, didn’t parse the list in order to check the existence of the users
and instead, viewed it as a single entity which didn’t already exist.
Is it possible to eliminate this behaviour or do I need to simply stay on top of
them by manually searching for and removing them?
Keep up with me and what I’m up to: http://theillien.blogspot.com