Best way to disable mail notification during mass ticket creation?

When creating large numbers of tickets via Tools/Offline, is there a
good way of disabling associated mail notification? I’m using RT
3.6.6. In 2006, Jesse suggested using a temporary override template (in
my case named ‘Admin Correspondence’) hardwired to a nobody address.

It would be great to have a checkbox on the Tools/Offline page to
"disable mail notification". Anything else is going to be potentially
disruptive of normal RT usage.

Maybe there’s no good way to do this. Not knowing anything about RT
internals, it seems like the “right” RT implementation of this might
require something like per-session scrips, the ability to override
global (and queue) scrips, and possibly even a new privilege. Ugh.

-Kevin Murphy

Kevin Murphy wrote:

When creating large numbers of tickets via Tools/Offline, is there a
good way of disabling associated mail notification?
On second thought, this is a pretty darn rare requirement. I retract my
question and comments :slight_smile:

-Kevin

Kevin Murphy wrote:

When creating large numbers of tickets via Tools/Offline, is there a
good way of disabling associated mail notification?
On second thought, this is a pretty darn rare requirement. I
retract my
question and comments :slight_smile:

If you did want to do this, I’d probably use the API and do this:

BEGIN {
no warnings ‘redefine’;
use RT::Action::SendEmail;
sub RT::Action::SendEmail::SendMessage { return 1 }
};

PGP.sig (186 Bytes)

You could just make the Autoreply template blank. No email will be sent.On Mon, Apr 14, 2008 at 4:20 PM, Kevin Murphy murphy@genome.chop.edu wrote:

When creating large numbers of tickets via Tools/Offline, is there a
good way of disabling associated mail notification? I’m using RT
3.6.6. In 2006, Jesse suggested using a temporary override template (in
my case named ‘Admin Correspondence’) hardwired to a nobody address.

It would be great to have a checkbox on the Tools/Offline page to
“disable mail notification”. Anything else is going to be potentially
disruptive of normal RT usage.

Maybe there’s no good way to do this. Not knowing anything about RT
internals, it seems like the “right” RT implementation of this might
require something like per-session scrips, the ability to override
global (and queue) scrips, and possibly even a new privilege. Ugh.

-Kevin Murphy


The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com