I created a “nomail” queue that had no scrips that created
correspondence (which of course means unassigning all of the default
scrips and recreating individually for each queue).
Stopping sendmail or whatever email daemon you use will give you a
chance to breathe as well.
Whenever someone would used a horribly stupid vacation rule that messed
up the headers (like used to happen all the time on an older version of
GroupWise), I’d move the ticket to that queue. At one point we also had
procmail use regex matching for things that sounded like vacation mail
subject lines and put vacation sounding messages in that queue
Procmail also redirects tagged spam to that queue as well (why write
back spammers and potentially verify your address?).
Vivek Khera wrote:
How do I halt this problem in the short term? How do I prevent this
from happening in future?
Short term: you either temporarily remove your autorespond scrip or
you block the sender at the mail server until the loop is broken.
RT really needs a built-in autoresponder squelch system. We get
into autoresponder wars on occasion. If we’re lucky they have the
original subject so they all go to the same ticket… once we burned
thru like 20k tickets before we could stop it.
Be sure to check out the RT Wiki at http://wiki.bestpractical.com
Download a free sample chapter of RT Essentials from O’Reilly Media at http://rtbook.bestpractical.com
WE’RE COMING TO YOUR TOWN SOON - RT Training in Amsterdam, Boston and
San Francisco - Find out more at http://bestpractical.com/services/training.html
UC Berkeley Extension