I am evaluating UE. Very nice. Congrats.
One question though: How do I prevent deleted (or downloaded+deleted) headers from reappearing as new when I do a Rescan?? I searched the settings and i can't figure it out. This is a compact binary group. Thanks.
Deleted reappearing on rescan
as to compact binary type it is the only newsgroup type which doesn't have support for purged/expired headers, the reason is for groups with partial messages it would take a lot of memory comparing to just deleting headers defeating the purpose of this newsgroup type.
the solution is to delete headers (not to purge them) and not to reset the newsgroup (since reset newsgroup will get rid of deleted headers as well).
instead of "reset newsgroup" if you think server counters may be wrong (news server changed its article numbering) just invoke "advanced->reset header ranges" from the newsgroups pane, newsgroup context menu to reset header ranges so next time "get new headers" will get all headers again (we are not talking about rescan, no need to reset header ranges for rescan to work).
as long as headers are deleted (if you check "del" and uncheck "^del" in the quick filter you can see them) they won't reenter for regular or xpat groups.
if you change "retention" e.g. from 10 to 15 days and you applied smaller retention already it is clear then that those headers from 10 to 15 days are not in the database including deleted so then they will reenter.
in short you need to keep headers marked as deleted in the newsgroup to prevent their reentry. for other newsgroup types there is mechanism to keep headers after leaving the newsgroup (so called storage for expired/purged in properties->general and related options in the context menu in the newsgroups workspace pane) but those newsgroup types are much more memory greedy and such storage gives relative economy in RAM, still consuming much more than in the case with just "deleted headers" for compact binary (you may use those other newsgroup types for text or small newsgroups).
so no problem with compact binary at all, just you need to keep deleted headers intact in the group so the program will know which headers are deleted.
the solution is to delete headers (not to purge them) and not to reset the newsgroup (since reset newsgroup will get rid of deleted headers as well).
instead of "reset newsgroup" if you think server counters may be wrong (news server changed its article numbering) just invoke "advanced->reset header ranges" from the newsgroups pane, newsgroup context menu to reset header ranges so next time "get new headers" will get all headers again (we are not talking about rescan, no need to reset header ranges for rescan to work).
as long as headers are deleted (if you check "del" and uncheck "^del" in the quick filter you can see them) they won't reenter for regular or xpat groups.
if you change "retention" e.g. from 10 to 15 days and you applied smaller retention already it is clear then that those headers from 10 to 15 days are not in the database including deleted so then they will reenter.
in short you need to keep headers marked as deleted in the newsgroup to prevent their reentry. for other newsgroup types there is mechanism to keep headers after leaving the newsgroup (so called storage for expired/purged in properties->general and related options in the context menu in the newsgroups workspace pane) but those newsgroup types are much more memory greedy and such storage gives relative economy in RAM, still consuming much more than in the case with just "deleted headers" for compact binary (you may use those other newsgroup types for text or small newsgroups).
so no problem with compact binary at all, just you need to keep deleted headers intact in the group so the program will know which headers are deleted.