Overview expiration

[Katsuhiro Kondou]

In article <E12fUVd-0001at-00 at g212.hadiko.de>,
	Olaf Titz <olaf at bigred.inka.de> wrote;

} The core of the matter is that expire/expireover(?) has to check for
} expired articles on self-expiring storage methods, but for my setup it
} has to check always. I still maintain the latter is correct because
} articles may get lost even accidentally, and this should not lead to
} an inconsistent overview. At least there should be a flag to activate
} such a mode.
} 
} I was running without groupbaseexpiry in the past, now switched to
} groupbaseexpiry to see if it makes any difference. Any definitive word
} on this?

Here is current expiry scheme:

groupbaseexpiry true:
 - run expireover first and do the job of expiry based on
   expire.ctl (newsgroup info is retrieved from Xref in
   overview data)
    * for non selfexpiry storage method
       - expireover also purge articles if delayrm not specified
       - run fastrm if delayrm specified to purge articles
 - then expire recreates history
    * leave entry if article still exists

groupbaseexpiry false:
 - run expire to recreate history
    * this is done class based expiry based on expire.ctl, but
      for selfexpiry storage method it's ignored and expire checks
      its existense
    * for non selfexpiry storage method
       - expire also purge articles if delayrm not specified
       - run fastrm if delayrm specified to purge articles
 - then expireover purges overview data by checking the existense
   of article

Hope this helps.
-- 
Katsuhiro Kondou