Package: tin
Version: 1:2.6.5~20250409-1
Followup-For: Bug #1109039

First of all, expired filter rules have ever been removed from the
filter file since Iain changed the format between tin-1.22 and
270194APLHA so that behaviour is the same for the last ~31 years.

Second, comments in attributes (and tinrc etc.pp) have ever been dropped
when writing them since those file have a version number (for attributes
that's since 1.5.18 release 20030602).

Keeping expired filter rules should be doable with not too much efford
(likely companied with a tinrc-var which defaults to "remove expired
rules" but having an option to keep them). I'll put that on the TODO-list.

Keeping comments in the versioned files (exception is filter whith
"comment=" which was a 'simple' way to preserve them dating back to
version 1.5.15 release 20021115; before that release comments were lost
as in other files on rewrite) is more complex and I doubt it will be
added (anytime soon). That's on the TODO-list since 04-2008:

| o comments in attributes get lost (we need to do something like we do for
| the filter file)
| [20080425 Urs Janssen <[email protected]>]

urs

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2025-07-10 14:01:41 +0200, Urs Jan�en wrote:

First of all, expired filter rules have ever been removed from the
filter file since Iain changed the format between tin-1.22 and
270194APLHA so that behaviour is the same for the last ~31 years.

It is possible that these filter rules got removed before I had
a chance to see them (it is quite uncommon that I closely look
at these config files). In my case, they are created automatically
by add_posted_to_filter=ON.

It appears that I have a more general rule, which is permanent:

group=*
case=0
score=hot
msgid=vinc17\.org

(though it is not guaranteed to work in all cases, if ever my msgid
format changes), and this could be another reason why I did not
notice the issue before.

Second, comments in attributes (and tinrc etc.pp) have ever been dropped
when writing them since those file have a version number (for attributes that's since 1.5.18 release 20030602).

It's strange that I did not notice that before. Perhaps I was blindly
copying my config from my own copy to the .tin/attributes file. But
the latest changes in my own copy were done 4 years ago, and I was
not sure that this copy matched the actual config on my new machine;
that's why I looked closer in order to merge the config if need be.

Note that the attributes file starts with

# Group attributes file V1.0.xx for the TIN newsreader
# Do not edit this comment block

so that I expected that anything after this comment block would
be preserved (or nicely converted).

--
Vincent Lef�vre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)