[ietf-nntp] OVER message-id

[Francois Petillon]

Charles Lindsey a écrit :
>> There is no direct synchronization between spooler and frontal on
>> article expiration. Expiration is done by batch (on spooler, il will
>> remove old spool files, on dreaderd, it will, group per group, mark
>> old entries as deleted). Direct synchronisation (ie mark an entry as
>> deleted when an article is removed) would hit disk I/O.
> So the spooler and the server may expire at different times. An article
> may be expired on the one but not on the other, either way around?

Yes and even at the same time (a text spooler who has longer retention
than the frontal and a binary spooler who has a smallest one). Usually,
you just try to keep a smallest retention on frontals than on spoolers.

  François