Mass email creating Tickets

Hi Guys I am fairly new to this RT stuff but a question I have is about
scrips. I need a way to stop a ticket from being created when the email
address provided is on a mass email. I have an email address which is used
for users to send in a ticket, but the email is also on a countrywide
distribution list which HR, Health and safety, etc use, everytime they send
a mass email to everyone it creates a ticket in my RT. In my scrips I am
able to change statuses depending on queues etc but when writing a scrip to
sort this out I am stuck.

I figure if I am able to say “Email was sent to more than one person”
therefore update status to “deleted”.

However, I am unsure on how to do such a thing. Any ideas?

Thanks

View this message in context: http://requesttracker.8502.n7.nabble.com/Mass-email-creating-Tickets-tp57582.html

Would it not be easier to remove your queue email from the distribution list; or am missing something?

Jon-----Original Message-----
From: AdamThomas [adam.thomas@sgs.com]
Received: Tuesday, 03 Jun 2014, 20:52
To: rt-users@lists.bestpractical.com [rt-users@lists.bestpractical.com]
Subject: [rt-users] Mass email creating Tickets

Hi Guys I am fairly new to this RT stuff but a question I have is about
scrips. I need a way to stop a ticket from being created when the email
address provided is on a mass email. I have an email address which is used
for users to send in a ticket, but the email is also on a countrywide
distribution list which HR, Health and safety, etc use, everytime they send
a mass email to everyone it creates a ticket in my RT. In my scrips I am
able to change statuses depending on queues etc but when writing a scrip to
sort this out I am stuck.

I figure if I am able to say “Email was sent to more than one person”
therefore update status to “deleted”.

However, I am unsure on how to do such a thing. Any ideas?

Thanks

View this message in context: http://requesttracker.8502.n7.nabble.com/Mass-email-creating-Tickets-tp57582.html
RT Training - Boston, September 9-10
Training — Best Practical Solutions

This email has been processed by Smoothwall Anti-Spam - www.smoothwall.net

I have already tried that but the administrator is giving a hard time about it :/-------- Original message --------
From: Jon Witts jwitts@queenmargarets.com
Date: 06-03-2014 4:49 PM (GMT-05:00)
To: rt-users@lists.bestpractical.com,“Thomas, Adam (Lakefield)” Adam.Thomas@sgs.com
Subject: RE: [rt-users] Mass email creating Tickets

Would it not be easier to remove your queue email from the distribution list; or am missing something?

Jon

-----Original Message-----
From: AdamThomas [adam.thomas@sgs.com]
Received: Tuesday, 03 Jun 2014, 20:52
To: rt-users@lists.bestpractical.com [rt-users@lists.bestpractical.com]
Subject: [rt-users] Mass email creating Tickets

Hi Guys I am fairly new to this RT stuff but a question I have is about
scrips. I need a way to stop a ticket from being created when the email
address provided is on a mass email. I have an email address which is used
for users to send in a ticket, but the email is also on a countrywide
distribution list which HR, Health and safety, etc use, everytime they send
a mass email to everyone it creates a ticket in my RT. In my scrips I am
able to change statuses depending on queues etc but when writing a scrip to
sort this out I am stuck.

I figure if I am able to say “Email was sent to more than one person”
therefore update status to “deleted”.

However, I am unsure on how to do such a thing. Any ideas?

Thanks

View this message in context: http://requesttracker.8502.n7.nabble.com/Mass-email-creating-Tickets-tp57582.html
RT Training - Boston, September 9-10
Training — Best Practical Solutions

This email has been processed by Smoothwall Anti-Spam - www.smoothwall.nethttp://www.smoothwall.net/

Information in this email and any attachments is confidential and
intended solely for the use of the individual(s) to whom it is addressed
or otherwise directed. Please note that any views or opinions presented
in this email are solely those of the author and do not necessarily
represent those of the Company.
Finally, the recipient should check this email and any attachments for
the presence of viruses. The Company accepts no liability for any damage
caused by any virus transmitted by this email.
All SGS services are rendered in accordance with the applicable SGS
conditions of service available on request and accessible at