• trn: How to search only new messages (i.e., using the THRU line)

    From Kenny McCormack@21:1/5 to All on Fri Oct 27 10:32:54 2023
    (Yes, this has to do with dealing with the Thai spam mess)

    In trn, when it is processing the "kill file", it uses the THRU line to
    tell it to ignore old articles (provided you have +k in TRNINIT). This, obviously, saves a lot of time (as well as other benefits [see below]).

    I need it to do the same thing when doing an "ad hoc" search, but can't
    figure out how. I want to do:

    /message-id.*googlegroups/h:=j

    manually (i.e., "ad hoc" while running trn) and have it only find and kill
    the new stuff (i.e., not touch old articles, presumably posted by
    legitimate Google users). (Yes, implicit in this is "I'm not going to
    worry about accidentally killing new legit Google posts - that's a risk I'm willing to take")

    Is this possible?

    --
    The only thing Trump's made great again is Saturday Night Live.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to Kenny McCormack on Fri Oct 27 17:39:15 2023
    Kenny McCormack <[email protected]> wrote:

    (Yes, this has to do with dealing with the Thai spam mess)

    Ray Banana and others are supplying NoCeMs. Can you get your News
    administrator to process them? The problem should be taken care of at
    the server level, not in a kill file.

    In trn, when it is processing the "kill file", it uses the THRU line to
    tell it to ignore old articles (provided you have +k in TRNINIT). This, >obviously, saves a lot of time (as well as other benefits [see below]).

    I need it to do the same thing when doing an "ad hoc" search, but can't >figure out how. I want to do:

    /message-id.*googlegroups/h:=j

    Kill file based on the G2 client on the X-Newsreader header if you
    really want to get rid of all articles posted through Google Groups.

    And use h+ as you are probably threading.

    manually (i.e., "ad hoc" while running trn) and have it only find and kill >the new stuff (i.e., not touch old articles, presumably posted by
    legitimate Google users). (Yes, implicit in this is "I'm not going to
    worry about accidentally killing new legit Google posts - that's a risk I'm >willing to take")

    Is this possible?

    I don't know the recipe to use to operate on new articles only. I will
    have to look it up.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Kenny McCormack@21:1/5 to Adam H. Kerman on Fri Oct 27 19:14:17 2023
    In article <uhgsk3$2c6tq$[email protected]>,
    Adam H. Kerman <[email protected]> wrote:
    Kenny McCormack <[email protected]> wrote:

    (Yes, this has to do with dealing with the Thai spam mess)

    Ray Banana and others are supplying NoCeMs. Can you get your News >administrator to process them? The problem should be taken care of at
    the server level, not in a kill file.

    Oh, I agree 1000%. Unfortunately, I don't think any kind of "local" server-side solution is going to work in my situation. Hence, I'm stuck
    with working it via kill files.

    I think the only long-term solution is for Usenet to declare the Google experiment a failure and disconnect from them completely. Call this a UDP
    - or something similar.

    BTW, not that this next means all that much, but I was discussing this
    recently in one of the affected groups (not sure which one). I stated that
    a server-side solution was needed, and was told sternly that there was no server-side solution (*) and that kill files were the only way. I think
    the person who said that was FOS, but he sure sounded sure of himself (heh heh).

    (*) His argument was that server administrator simply won't do it, because
    they don't see it as their job. It was an odd combination of "can't"
    and/or "won't" (heh heh). I am glad to hear that he is/was wrong.

    ...
    I need it to do the same thing when doing an "ad hoc" search, but can't >>figure out how. I want to do:

    /message-id.*googlegroups/h:=j

    manually (i.e., "ad hoc" while running trn) and have it only find and kill >>the new stuff (i.e., not touch old articles, presumably posted by >>legitimate Google users). (Yes, implicit in this is "I'm not going to >>worry about accidentally killing new legit Google posts - that's a risk I'm >>willing to take")

    Is this possible?

    I don't know the recipe to use to operate on new articles only. I will
    have to look it up.

    I hope you are able to do that. Just out of curiosity, what documentation
    is there for trn other than the (ancient, cryptic and hard-to-understand)
    man page?

    Note that what I am seeking may simply not exist, for the simple reason
    that:

    A) there's no direct connection between what you do manually inside of
    trn and the contents of the kill file (which has already been
    processed and is essentially out of scope at that point).
    and
    B) The THRU line will already have been updated (as part of the kill
    file processing), so you'd need a way to keep/save/remember the
    original value (the one at entry to the group).

    --
    After 4 years of disastrous screwups, Trump now favors 3 policies that I support:
    1) $2K/pp stimulus money. Who doesn't want more money?
    2) Water pressure. My shower doesn't work very well; I want Donnie to come fix it.
    3) Repeal of Section 230. This will lead to the demise of Face/Twit/Gram. Yey!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to Kenny McCormack on Sat Oct 28 02:09:06 2023
    Kenny McCormack <[email protected]> wrote:
    Adam H. Kerman <[email protected]> wrote:

    . . .

    I don't know the recipe to use to operate on new articles only. I will
    have to look it up.

    I hope you are able to do that.

    It's a matter of playing with regular expressions.

    Just out of curiosity, what documentation
    is there for trn other than the (ancient, cryptic and hard-to-understand)
    man page?

    The man page, which was never updated for trn 4 is why trn is always in
    "test" configuration,

    Note that what I am seeking may simply not exist, for the simple reason
    that:

    A) there's no direct connection between what you do manually inside of
    trn and the contents of the kill file (which has already been
    processed and is essentially out of scope at that point).
    and
    B) The THRU line will already have been updated (as part of the kill
    file processing), so you'd need a way to keep/save/remember the
    original value (the one at entry to the group).

    You're right on both points. I'll have to put a lot of thought into it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sqwertz@21:1/5 to All on Sat Oct 28 19:12:55 2023
    Then email him ferschristakes.

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