At Mon, 30 Jun 2008 15:48:10 -0700, 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 > this sort > of thing would horrify them. I agree that this is horrifying. More importantly, doesn't this mean that this is a problem we actually need a solution for pronto? As I understand Glen's message, he's saying that this is a bug in mailman triggered by some problem in TMDA. I realize that TMDA is being replaced, but presumably Henrik's code isn't perfect, so don't we have to worry about it triggering the same behavior? Glen, I'm sure there are some people on this list who understand mailman well. I realize you may not have complete info, but if you can provide us some more information--e.g., what file(s) got stomped and which code you think stomped it--about what you think happened, maybe they can help track it down? -Ekr > 2) 3 years since the last backup? Oi. > > Mike > > Glen wrote: > > All - > > > > I was asked by the IAOC to post a message to the IETF and SIP lists, > > to ensure that people were aware that the subscriber lists for the > > IETF and SIP lists were damaged as a result of an anomaly in TMDA and > > Mailman that occurred Thursday night. > > > > Basically, TMDA misbehaved, and, in the process, caused Mailman to > > encounter a transient failure in the reading of its databases for > > these two lists. As a result, rather than simply holding the mail and > > retrying it, Mailman decided to discard the current list databases and > > re-create them from 3-year-old data, for both the IETF and the SIP lists. > > > > *sigh* > > > > No email was lost to the system or the archives; however, some people > > may have missed some messages, or may still not be resubscribed to the > > list. > > > > Of course we restored the files from backups; however, we want to make > > sure that everyone gets the mail they missed, and that everyone is > > subscribed to these lists who wishes to be subscribed. > > > > So... > > > > If you're reading this message in your email box, you're subscribed to > > the list identified in the subject line, and all should be okay. > > > > If you're reading this message in the archives, wondering why you're > > not getting list mail, please take a moment to resubscribe yourself to > > the list, which should resolve your problem. > > > > And regardless, if you feel you missed any mail, we do have the > > archives available for your reference. > > > > IETF List Subscription Link: https://www.ietf.org/mailman/listinfo/ietf > > IETF List Archive Link: http://www.ietf.org/mail-archive/web/ietf/ > > > > SIP List Subscription Link: https://www.ietf.org/mailman/listinfo/sip > > SIP List Archive Link: http://www.ietf.org/mail-archive/web/sip/ > > > > We are in the home stretch of getting TMDA removed and replaced on the > > servers, and I apologize for any inconvenience caused by this issue. > > Because server problems apparently happen only in the dead of night, > > you can be sure that we feel any and all pain anyone may be experiencing. > > > > If you need any assistance, please contact the IETF Secretariat, using > > the links at: http://www.ietf.org/secretariat/ > > > > Thank you, > > Glen Barney > > IT Director > > AMS (IETF Secretariat) > > _______________________________________________ > > Ietf mailing list > > Ietf@xxxxxxxx > > https://www.ietf.org/mailman/listinfo/ietf > > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf _______________________________________________ Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf