On Thu, Jul 10, 2025 at 03:57:25PM +0200, Vincent Lefevre wrote:
> 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.
What the current[1] code does is:
- set the write flag if the file version is older than the expected version
- read the filter file rule by rule; if any expired rule is found skip
that rule set the write flag
- when all rules have been read, check the write flag and
write the file if needed.
This happens on every read of the file (e.g. also after 'E'dit filter
file).
> 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.
I don't use add_posted_to_filter but filter on "my" Message-ID only.
The format didn't change since some time before 01.1997.
And there is EVIL_INSIDE which could be used to let tin
generate the Message-ID (based on login name + FQDN.
I doubt that will be more stable than the ones comming from your
server. It's only mentioned in doc/INSTALL like FORGERY
(which does alter the Message-ID scheeme if used together with
EVIL_INSIDE) for reasons.
[1] I have a work in progress patch (lacks the 'M'enu/
tinrc option to enable it, currently it's a compile
time "option") to keep expired rules in the filter
(as they are, they are just not taken into account).
Needs some testing, but I guess it will be available
with the next snapshot/release.
> > 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 attribute file format is relative stable and there
is no expire mechanism like for filter rules. So chances
are high(er) that comments survive 1-3 years ,-)
> 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).
That should read as "feel free to adjust any _options_ manually"
and no as "everthing in the file is preserved as is".
Same applies to the tinrc and serverrc and ...
HTH,
urs
