Re: Exiting a group with (all?) expiring articles is currently broken

[Karl Kleinpaste <karl@charcoal.com>]

Karl Kleinpaste <karl@charcoal.com> writes:
> As of a CVS update of about 20 minutes ago (this is Thursday evening,
> 9:30pm EDT), attempting to exit this group rewards me with this stack
> trace:

> Signaling: (wrong-type-argument number-char-or-marker-p >)
>   <(> 8736)
>   sort((8740) <)
>   nnml-request-expire-articles((8736 8737 8738 8739 8740) "tomb" "" nil)

I investigated a bit, and found that the problem was a corrupt
overview in tomb.  It somehow had been abused so that the first line
in the file was this:

>		12085	315	Xref: cinnamon.vanillaknot.com tomb:8708	To: <cola55@freeze.com>	Keywords: font,color,face,arial,size,align,&nbsp,height,narrow,#000000,div,width,left,span,name,#008000,right,center,input,style,sans-s,helvetica,erif,bgcolor,background-color	

Evidently, a previous exit from tomb had not done a proper & clean job
of expiring articles, having left a partial entry for article 8708
(see Xref content) at the top of the file.

Article 8708 in this spam-catcher group must have been from a week or
more ago, and I wonder how this worked at all since that time.

The rest of the overview was fine, containing normal entries for 8736
through 8740.  Deleting the offending fragmentary line made it work
again, and all is well: All articles were expired, the articles are
gone, and the overview is now empty.

I am concerned that some recent change seems to have damaged article
expiry so as to abuse overviews.