On 04/10/2011 03:46 AM, Duncan wrote: > I just tried getting all headers for an affected group, and DESPITE the > fact that it's a gmane group, gmane.* hierarchy, not carried by anything > BUT gmane, and DESPITE the fact that I have gmane set to "never expire", > the log said "expiring 64 headers for <group>, and the group is again > entirely empty. > > Re-fetching all headers doesn't seem to do anything at all. ?? > > Maybe it's the expiration going haywire. Check to see if there's a low- > use code-path where a "0" expiration is taken as literally zero days > (thus, immediately), instead of don't expire at all. > > Actually, that might explain the cross-posting link as well, since there > may be some logic that treats it differently. (Consider the case of a > cross-posted message retrieved from a short-expiration server, whether one > of the groups posted to only appears on a longer-expiration server. > Having the message disappear from the group only on the long-expiration > server at short-expiration-server time is arguably not a good thing, tho I > could see it argued either way. If Charles had some code intended to deal > with that sort of thing, that only applied to cross-posts... Now that I have my computer working again...
The only time articles get expired is when loading the headers. The conditions to expire an article are: 1) the server # is not valid 2) expiration age !=0 && age > expiration age See headers.cc:516 Are you certain the expiration age is still 0 in servers.xml? You could try checking the xref line for the affected articles to see which server id they use. The format is server:group:article# where group could be a name or one letter. Each entry on that line is checked individually. Only if all the entries are expired is the article expired.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pan-users mailing list Pan-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/pan-users
