[NCUC E-team] Question

[Maryam Bakoshi]

Dear All,

With respect to the below email from Tapani, should the email be sent to
everybody or only those
who weren't confirmed before?


Many thanks,
-- 
Maryam Bakoshi
Secretariat ­ NCSG, NCUC, NPOC
Internet Corporation for Assigned Names and Numbers

Email:  maryam.bakoshi at icann.org
Mobile:  +44 7737 698036
Skype:  maryam.bakoshi.icann






On 06/11/2014 12:32, "William Drake" <william.drake at uzh.ch> wrote:

>Hi
>
>Yes, please send them to everyone to be safe.
>
>Thanks
>
>Bill
>
>> On Nov 6, 2014, at 1:10 PM, Maryam Bakoshi <maryam.bakoshi at icann.org>
>>wrote:
>> 
>> Hi Bill,
>> 
>> Below is email from Tapani as part of my correspondence with him over
>>the
>> last few days.
>> So, in regards to step (2), it is my view that the automated email is
>>sent
>> to everyone, incase there are any updates to email addresses etc, we can
>> catch it.
>> He has suggested sending to the e-team to ask for opinions.
>> Please advise.
>> 
>> Many thanks,
>> -- 
>> Maryam Bakoshi
>> Secretariat ­ NCSG, NCUC, NPOC
>> Internet Corporation for Assigned Names and Numbers
>> 
>> Email:  maryam.bakoshi at icann.org
>> Mobile:  +44 7737 698036
>> Skype:  maryam.bakoshi.icann
>> 
>> 
>> 
>> 
>> 
>> 
>> On 06/11/2014 10:47, "Tapani Tarvainen" <ncuc at tapani.tarvainen.info>
>>wrote:
>> 
>>> On Nov 06 10:22, Maryam Bakoshi (maryam.bakoshi at icann.org) wrote:
>>> 
>>>> I am ready when you are  :)
>>> 
>>> Looking at
>>> 
>>> http://lists.ncuc.org/pipermail/e-team/2013-December/000531.html
>>> 
>>> the next step would be (2), however you can't do that before a decision
>>> is made who all the message should be sent to: everybody, only those
>>> who weren't confirmed before or what. You might bring this up in
>>> the e-team list.
>>> 
>>> You can, however, experiment a little using, say, me as a test subject.
>>> The passivecheck script has a feature that allows it to be limited
>>> by name. So, try this:
>>> 
>>> psql ncuc -c "update ncucers set state=1 where name~'Tapani
>>>Tarvainen';"
>>> 
>>> That in effect makes me (and my namesakes, but there aren't any
>>> in NCUC) "unverified" (state=1).
>>> 
>>> Step (3) can be done for everybody already:
>>> 
>>> psql ncuc -c 'update ncucers set xkey=trunc(100000000*random()) where
>>> state=1;'
>>> 
>>> What that does is create a random key for each member to
>>> keep their confirmation links distinct (so they won't
>>> accidentally confirm others).
>>> 
>>> Step (4) can also be done at this point as suggested, although
>>> you might wish to look at the log first and maybe even save it
>>> rather than just removing it:
>>> 
>>> cat /var/local/ncuc/confirm.log
>>> mv /var/local/ncuc/confirm.log /var/local/ncuc/oldconfirm.log
>>> 
>>> Step (5) can be done for me only like this:
>>> 
>>> ./passivecheck.sh --match 'Tapani Tarvainen' --commit
>>> 
>>> If you omit the final "--commit" it will do a "dry run",
>>> generate the message(s) but display them to you instead
>>> of sending them out. So you might want to try that first
>>> to see what it looks like.
>>> 
>>> Once you send the message to me I'll click "ok" in it
>>> and you can proceed to step (6).
>>> 
>>> -- 
>>> Tapani Tarvainen
>> 
>
>***********************************************
>William J. Drake
>International Fellow & Lecturer
>  Media Change & Innovation Division, IPMZ
>  University of Zurich, Switzerland
>Chair, Noncommercial Users Constituency,
>  ICANN, www.ncuc.org
>william.drake at uzh.ch (direct), wjdrake at gmail.com (lists),
>  www.williamdrake.org
>***********************************************
>