> Date: Wed, 27 Aug 2014 01:15:52 -0500 > From: Bruce Dubbs <[email protected]> > To: BLFS Development List <[email protected]> > Subject: Re: [blfs-dev] Funny problem in BLFS Support archives > > Jocelyn Fréchot wrote: > > On 27/08/2014 00:07, Fernando de Oliveira wrote: > > > >> Notice that: > >> > >> first line is *February 2030* > >> second line is *November 2027* > >> > >> Third line should be the first one. i.e, first two lines need to be > >> deleted. > > > > For the record, the two first lines are there for months, or more surely > > years. > > The one dated 2030 appears to be posted around 12 Feb 2002 18:24:01 > The one dated 2027 appears to be posted around 01 Nov 2001 16:32:20 > > Removing a message is a non-trivial task. The whole database has to be > rebuilt after removing the offending messages. I've done it before for > some messages that had embedded virii, but these are just some users > with bad dates set in their system. > > Is there any particular reason we can't just live with them? >
Well most have for years now. It's only an occasional pain here when one automatically goes to click on the top-most entry (aiming to get the current-month). I guess it's not too bad if there aren't (m)any more such rows in the table. Why not have the mail-server &/or mailing-list software reject messages that are 'too far in the future'. If you're able to do that and it works ok, then may be worth removing those existing 'feb 2030'/'nov 2027'/&c items: but otherwise, I wouldn't go around chasing down such entries - you might even just attract many more. akh > -- Bruce > -- -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
