[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: closing spam bugs

From: Chad Walstrom
Subject: Re: closing spam bugs
Date: Fri, 28 Apr 2006 11:29:55 -0500

Ralf Wildenhues <address@hidden>  wrote:
> But both of these options require login access to the host on which
> gnats is running (which I don't have and need currently), right?

Yes, to edit the dbconfig file, you need to be the DB administrator
with file editing access.  However, using pr-edit and query-pr only
requires you to log in to the GNATS interface, not a shell interface.

Ohh...  You're using an old GNATS aren't you, one without gnatsd
support.  Yeah, you'ld probably need shell access for that.

> The first one seems like it could be inconvenient for genuine bug
> reports, the second one sounds pretty hacky to me.

It actually works pretty well.  There are rare occasions when a DB
lock prevents me from closing spam, but that little script saves us a
lot of grief.

> So, how about a gnats+gnatsweb enhancement: add a button to the edit
> page to close spam bugs; this would then not cause a mail to be
> written to the reporter's email address?

I don't believe the older gnatsweb is being developed.  I've tried
editing the reporter's email before in gnatsweb and had problems, but
haven't had a chance to debug it.  However, the procedure for not
sending replies to the spammer or spoofed address is by changing the
reporter and originator to a /dev/null address (we use address@hidden).

Chad Walstrom <address@hidden> 
           assert(expired(knowledge)); /* core dump */

reply via email to

[Prev in Thread] Current Thread [Next in Thread]