Re: Subscriber List Damage

From: Glen <glen at amsl.com>
To: Michael Thomas <mat at cisco.com>
Cc: sip at ietf.org, IAOC <iaoc at ietf.org>, ietf at ietf.org
Date: Mon, 30 Jun 2008 17:37:03 -0700
In-reply-to: <486962AA.3000800 at cisco.com>
References: <48671722.1020502 at amsl.com> <486962AA.3000800 at cisco.com>

Michael Thomas wrote:

1) Have you brought this up with the mailman folks? I've interacted with
them and they seem like a responsive set of folks. I'm sure that thissort
   of thing would horrify them.

I haven't yet, but will try. They'll probably want more informationthan I can give them.

2) 3 years since the last backup? Oi.

No - not three years since the last backup. I have MUCH more recentbackups than that, of course!

Three years is the age of the file that I suspect mailman used to pullits old configuration from. An old copy of the database for those twolists that was just sitting around, not being used.


Glen
_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www.ietf.org/mailman/listinfo/ietf

References:
- Subscriber List Damage
  - From: Glen
- Re: Subscriber List Damage
  - From: Michael Thomas

Prev by Date: Re: Update of RFC 2606 based on the recent ICANN changes ?
Next by Date: Re: Subscriber List Damage
Previous by thread: Re: Subscriber List Damage
Next by thread: Re: Subscriber List Damage
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: Subscriber List Damage

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.