Re: Who gets an email when with bugreports [was: Re: Unauthorised activity surrounding tbb package]
On Wed, 28 Jan 2015, Vincent Lefevre wrote:
> On 2015-01-24 02:00:34 +0000, Ben Hutchings wrote:
> > On Wed, 2015-01-21 at 17:07 +1300, Chris Bannister wrote:
> > > Or an option in reportbug to do so, turned on by default. It could put
> > > an X- header in the email.
> > >
> > > That way users of reportbug can choose to be 'spammed' or not.
> > This is still unconfirmed opt-in
> > <https://en.wikipedia.org/wiki/Opt-in_email#Unconfirmed_opt-in>.
> Well, when reporting a bug, the user always receives a mail from the
> BTS. This mail could also be used as a confirmation message for this
> and future bug reports: if the user replies, he will automatically be
> subscribed to all bugs "he" reports. The next bug reports may be
> forged, but the user would have done the confirmation step, so
> couldn't complain. Or better, the reply to the confirmation message
> could contain a private key that could be used by reportbug to insert
> a X- header identifying the author of the next bug reports.
Something along these lines is what I'm planning on doing.
Don Armstrong http://www.donarmstrong.com
Taxes are not levied for the benefit of the taxed.
-- Robert Heinlein _Time Enough For Love_ p250