And... just as an operational reminder.... If there is something that needs to be done sitewide, on the IETF servers, you'd want to direct that request to the secretariat at ietf-action@xxxxxxxx, as opposed to the IETF discussion list. (Not implying that discussion should be stifled - not at all! - but my IT team and I don't generally have the bandwidth to follow or read all the messages on the IETF list. Sometimes, something gets forwarded to us, as it did in this case.... but generally, if you need something done on the servers, ietf-action@xxxxxxxx is the place to go.) Glen On Fri, May 10, 2019 at 9:05 AM Russ Housley <housley@xxxxxxxxxxxx> wrote: > > John: > > Wouldn't it be better for the sergeant-at-arms to give at least one warning first? If the warning is ignored, then blocking seems like the right action. > > Russ > > > > On May 10, 2019, at 11:47 AM, John Levine <johnl@xxxxxxxxx> wrote: > > > > I'm seeing a lot of mail from someone or something with the address > > info@xxxxxxxxxxxx posted to multiple IETF lists. It is all copies of > > a message apparently intended for ICANN about the renewal of a TLD > > registry. I see nothing else in the archives from this address. > > > > Since we are not ICANN and have nothing to do with TLD registries, > > can we block this please? > > > > R's, > > John > > >
