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

Re: Bug#75853: TONER CARTRIDGES



On Fri, Sep 20, 2002 at 07:39:41AM -0400, Michael Stone wrote:
> On Fri, Sep 20, 2002 at 01:00:43PM +0200, Turbo Fredriksson wrote:
> >And the verification is only for the very FIRST
> >time the user have sent a bug report. The idea
> >is that the system remembers the user (well,
> >actually the mailaddress I suppose).
> 
> Regardless, people who do this just won't see mail I send them. I refuse
> to jump through hoops in trying to help someone (in this case, by
> sending a bug report.)

Mike,

Every process is mutual and somewhat is a compromise between merits and
risks.  Please do not say "regardless".  You already follow cumbersome
format of BTS mail anyway.

First of all, we can have white-list.  Any mail coming from DD, package
upstream authors, GNU, XFREE86, GNOME, KDE,... can made to be
automatically accepted (computation load issue?).

(If address spoofing becomes problem, we should deal it then.)

You are DD. Do you want to get more SPAM bug report?  Do you want more
bug reports which you can not get in touch?  Minimum protection may not
hurt, I think.

I think whoever bothers to write a reasonable bug report will not mind
replying once to get added to the list of the accepted e-mail address.

I think question is how to implement a friendly scheme to abate some gross
problems in current BTS system.  We all know it will not cure situation
completely.

I see quite a bit of ML posting from unreachable address too.  That is
less problematic than BTS but similar "first time only" confirmation
procedures may be a good idea for open ML too.

Osamu
-- 
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
        Osamu Aoki @ Cupertino CA USA, GPG-key: A8061F32
 .''`.  Debian Reference: post-installation user's guide for non-developers
 : :' : http://www.debian.org/doc/manuals/reference/ also http://qref.sf.net
 `. `'  "Our Priorities are Our Users and Free Software" --- Social Contract



Reply to: