[Rtir] Odd Blocks reports

[Tony Arnold]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kevin,

On 25/11/13 20:11, Kevin Falcone wrote:
> On Sat, Nov 23, 2013 at 11:52:09AM +0000, Tony Arnold wrote:
>> I've been through the same thing. I originally had our network
>> team configured as admincc watchers on the blocks queue. This
>> made sending block requests very easy as we didn't have to put
>> anything in the correspondents field when creating the block.
>> 
>> However, the status of tickets in the blocks queue can be 
>> automatically updated by correspondence. So I create a block in 
>> 'Activation pending' state. Message goes off to network team who 
>> then reply. This changes the state to 'Activated'. Similar thing 
>> happens on removal.
>> 
>> This does not work when the network team is configured as
>> watchers rather than specified as correspondents. This is because
>> the state change only gets done if the incoming e-mail is from
>> one of the requesters of the ticket.
>> 
>> So we took off the watchers and we now specify the network team 
>> explicitly every time we create a block. We have to specify the 
>> members of the team explicitly, we cannot even use their group 
>> mailing list address.
> 
> This surprises me - default RTIR scrips use On Correspond - RTIR
> Set Status of Block
> 
> That On Correspond condition is a literal "Any Correspondence by 
> anybody" not "On correspondence from Requestors".

I think the scrip SetRTIRstate, condition 'RTIR Require State Change',
Action is 'RTIR Set Block State' is the relevant one here. It's how it
came out of the box, no local mods.

Regards,
Tony.
- -- 
Tony Arnold,                        Tel: +44 (0) 161 275 6093
Head of IT Security,                Fax: +44 (0) 705 344 3082
University of Manchester,           Mob: +44 (0) 773 330 0039
Manchester M13 9PL.                 Email: tony.arnold at manchester.ac.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlKT1yQACgkQIsyKE/d21hm3BACfZUxogcu5PEfNBW7PcQscYpz5
71IAoLGbl7FC3vFEtcYWsRpQ0FmmF2ad
=phoJ
-----END PGP SIGNATURE-----