inn-2.3.0, expire with delayrm, tradspool, seems not working

[Benedict Lofstedt]

Katsuhiro Kondou writes:
 > In article <14820.4663.834963.35860 at caligula.daimi.au.dk>,
 > 	Benedict Lofstedt <benedict at daimi.au.dk> wrote;
 > 
 > } Sep 30 08:24:57 3H:gjallar makehistory[4534111]: tradspool: can't determine class: @050000000C53000086710000000000000000@: Bad article handle
 > } 
 > } where the token corresponds to the missing xref'ed article.
 > 
 > This means those articles are not stored based on current
 > storage.conf.
 > -- 
 > Katsuhiro Kondou

That's correct, I went from inn-2.2.3 to inn-2.3.0, running a makehistory
in the process, on my existing spool area.  I used tradspool, and I still
use tradspool.

My log entries from makehistory resulted from cross-posted articles
where some of the cross-postings had been removed.  An article like this
one:

Xref: news.daimi.au.dk talk.politics.misc:1589510 alt.society.anarchy:146527 alt.fan.noam-chomsky:93243 alt.activism:499181 alt.punk:541916 alt.politics.radical-left:300160

talk/politics/misc/1589510 existed, but all the crosspostings didn't.
Result: makehistory put out a log entry for each token,
e.g. alt/activism/499181.

It's my impression that anyone making the transition I made will
experience thousands of log messages like I did, and get scared by the
sheer volume of messages.

If you need further information, I'll try to set up a sample spool area
and reproduce the output.

--- benedict