[rt-users] Bulk delete

[asterr]

If changing the status of the tickets to "deleted" is sufficient, you should
be able to do a ticket search for all tickets with that requestor.  At the
bottom of the list of tickets, there is a link to update all tickets.  Then
change the status to delete.


As for preventing future problems, I think you want to block those e-mails
at your MTA.  In my case, we only allow ticket creation for privileged users.
This prevents spam from entering RT very nicely, but may not be an appropriate
solution, if you have a large customer base that should be able to submit
RT tickets.

-Aaron



On Tue, 10 Feb 2004, Hariharan wrote:

> Hello
> 
> I am faced with about 7000 tickets in a queue. Was wondering if someone
> could suggest a method to mass delete these junk tickets without going
> through the web interface.
> 
> Also, is there a way I can protect my queues in future from such problems?
> 
> Am not sure how to trace out the problem, all the 7000 emails are from a
> single domain ( incorrectaddress.autoresponder at 4c-alameda.org )
> 
> These are the headers:
> 
> Message-Id: <200401311326.HAA11215 at amaretto.propagation.net>
> Subject: incorrectaddress.autoresponder
> From: incorrectaddress.autoresponder at 4c-alameda.org
> Delivered-To: esatsang.net-membership at esatsang.net
> Return-Path: <incorrectaddress.autoresponder at 4c-alameda.org>
> Received: (qmail 29747 invoked by uid 505); 31 Jan 2004 08:36:08 -0500
> Received: from incorrectaddress.autoresponder at 4c-alameda.org by seed by
> uid 502 with qmail-scanner-1.16  ( Clear:.  Processed in 0.146418 secs);
> 31 Jan 2004 13:36:08 -0000
> Received: from 1-21-97-216-rev.propagation.net (HELO
> amaretto.propagation.net) (216.97.21.1) by 0 with SMTP; 31 Jan 2004
> 08:36:08 -0500
> Received: (from mail at localhost) by amaretto.propagation.net
> (8.9.3p2/8.8.5) id HAA11215 for membership at esatsang.net; Sat, 31 Jan 2004
> 07:26:02 -0600
> Date: Sat, 31 Jan 2004 07:26:02 -0600
> X-Loop: one
> To: membership at esatsang.net
> X-RT-Original-Encoding: iso-8859-1
> content-type: text/plain; charset="utf-8"
> Content-Length: 304
> 
> 
> How can I trouble shoot this problem?
> 
> Thanks for any pointers
> 
> Hari
> 
> 
> 
> 
> 
> 
> _______________________________________________
> rt-users mailing list
> rt-users at lists.bestpractical.com
> http://lists.bestpractical.com/mailman/listinfo/rt-users
> 
> Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm
> 
> 
>