1. Forum
  2. Usenet
  3. NEWS.SOFTWARE.READERS

  • trn question (spam in alt.obituaries)

    From Kenny McCormack@21:1/5 to All on Wed Sep 27 15:38:19 2023
    (Meta Note: lots of context information in the Subject: line. It is expected that readers are able to read the Subject: line. Sometimes people complain that they don't read Subjects. If you are one of those, this post might
    not make sense to you...)

    Content follows:

    a.o has gotten bombed with spam the last few days.

    I've noticed that the spam always contains URLs that look like https://bit.ly/...

    So, I wrote in my killfile something like:

    /https:..bit\.ly/a:=j

    Now, I've noticed that this works well when entering the group. All the
    newly posted spam gets killed. However, if spam comes in while I am
    reading the group, which often happens, the newly arrived spam does not get killed; I have to kill it manually. Normally, this is not the case; in
    general this sort of things works. But in this case, it does not. Is this
    a bug? Or is there something about 'a' type searches that behaves
    differently from normal "Subject only" type searches?

    --
    They say that Trump is a stupid man's idea of a clever man, a poor man's
    idea of a rich man, and a weak man's idea of a strong man.

    Well, Melania is an unclassy man's idea of classy.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to Kenny McCormack on Wed Sep 27 16:11:30 2023
    Kenny McCormack <gazelle@shell.xmission.com> wrote:

    (Meta Note: lots of context information in the Subject: line. It is expected >that readers are able to read the Subject: line. Sometimes people complain >that they don't read Subjects. If you are one of those, this post might
    not make sense to you...)

    Content follows:

    a.o has gotten bombed with spam the last few days.

    I've noticed that the spam always contains URLs that look like >https://bit.ly/...

    So, I wrote in my killfile something like:

    /https:..bit\.ly/a:=j

    I assume you've threaded the group. Make sure you use the + so you don't
    junk other articles in the thread.

    /a+

    Plenty of people filter on the G2 client which shows up in the headers.
    This captures anything injected through Google Groups. I don't because I
    still want to read legitimate posts, however few there are.

    /h+

    Now, I've noticed that this works well when entering the group. All the >newly posted spam gets killed. However, if spam comes in while I am
    reading the group, which often happens, the newly arrived spam does not get >killed; I have to kill it manually. Normally, this is not the case; in >general this sort of things works. But in this case, it does not. Is this
    a bug? Or is there something about 'a' type searches that behaves >differently from normal "Subject only" type searches?

    Wow. I have no idea what to tell you. I've been using trn4 since it
    first became available. The kill file operates on new articles that come
    in while I'm reading the group.

    Just quit the client and restart the next time it happens.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From candycanearter07@21:1/5 to All on Wed Sep 27 11:38:53 2023
    On 9/27/23 11:31, rek2 hispagatos wrote:
    a.o has gotten bombed with spam the last few days.

    I've noticed that the spam always contains URLs that look like
    https://bit.ly/...

    So, I wrote in my killfile something like:

    /https:..bit\.ly/a:=j


    I am one of those that just kills anything that comes from google
    groups, I think if anyone is half serious about usenet will use any of
    the many other usenet servers :)

    Happy Hacking
    ReK2


    Agreed, also killfiles are hard to write on TB.
    --
    user <candycane> is generated from /dev/urandom

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From rek2 hispagatos@21:1/5 to All on Wed Sep 27 16:31:04 2023
    a.o has gotten bombed with spam the last few days.

    I've noticed that the spam always contains URLs that look like >>https://bit.ly/...

    So, I wrote in my killfile something like:

    /https:..bit\.ly/a:=j


    I am one of those that just kills anything that comes from google
    groups, I think if anyone is half serious about usenet will use any of
    the many other usenet servers :)

    Happy Hacking
    ReK2

    --
    - {gemini,https}://{,rek2.}hispagatos.org - mastodon: @rek2@hispagatos.space
    - [https|gemini]://2600.Madrid - https://hispagatos.space/@rek2
    - https://keyoxide.org/A31C7CE19D9C58084EA42BA26C0B0D11E9303EC5

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Kenny McCormack@21:1/5 to rek2@hispagatos.org on Wed Sep 27 21:51:58 2023
    In article <uf1lc8$1n073$1@matrix.hispagatos.org>,
    rek2 hispagatos <rek2@hispagatos.org> wrote:
    a.o has gotten bombed with spam the last few days.

    I've noticed that the spam always contains URLs that look like >>>https://bit.ly/...

    So, I wrote in my killfile something like:

    /https:..bit\.ly/a:=j


    I am one of those that just kills anything that comes from google
    groups, I think if anyone is half serious about usenet will use any of
    the many other usenet servers :)

    1) Google Groups != @gmail.com

    2) That attitude - just kill anything coming from anything Google - is
    actually pretty close to reasonable in a technical group. But in basically frivolous groups like alt.obituaries, many/most of the regular posters come from "non-techy" domains, such as Google, Hotmail, AOL, etc. You'd miss a
    lot of good posts if you just kill-by-domain. Sad, but true.

    --
    "Women should not be enlightened or educated in any way. They should be segregated because they are the cause of unholy erections in holy men.

    -- Saint Augustine (354-430) --

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Eli the Bearded@21:1/5 to Kenny McCormack on Sun Oct 8 02:12:36 2023
    In news.software.readers, Kenny McCormack <gazelle@shell.xmission.com> wrote:
    a.o has gotten bombed with spam the last few days.

    I've noticed that the spam always contains URLs that look like https://bit.ly/...

    I've been seeing a large uptick in Google Groups sourced spam and have
    started to junk it all:

    /@googlegroup/HMessage-ID:k

    reading the group, which often happens, the newly arrived spam does not get killed; I have to kill it manually. Normally, this is not the case; in general this sort of things works. But in this case, it does not. Is this
    a bug? Or is there something about 'a' type searches that behaves differently from normal "Subject only" type searches?

    The 'a' article body searches are special, since they can't rely on
    overview files but must prefetch the article bodies. News servers have
    several levels of network optimization available and rn/trn likes to use
    them. You can fetch just overview (a select group of headers), full
    headers, or full article. The /a modifier only works with the last for
    this use case. I'm guessing that trn is looking for new articles only
    with overview information. The /b and /B body specific searches also
    require the full body to be loaded, but maybe because they are body
    specific they work better?

    I sidestep this by turning off checking for new articles while reading.
    It is the -K command line option, or stick it in TRNINIT environment
    variable or the ~/.trn/trnrc file:

    [environment]
    SAVESCOREFILE=/dev/null
    #
    # -e causes each page within an article to be started at
    # the top
    # -f will make trn avoid various sleep calls and the
    # prompt after the processing of the memorized commands
    # -K is used to keep a trn from checking for new news
    # while you're in the group.
    # -x{<number>}{<list>}
    # Enable the extended (threaded) features of trn beyond
    # the rn compatibility mode (this may be the default on
    # your system, use +x if you yearn for the good ol'
    # days). The <number> is the maximum number of arti-
    # cle-tree lines (from 0 to 11) you want displayed in
    # your header. Use the <list> to choose which thread
    # selector styles you like ('s'hort, 'm'edium, or
    # 'l'ong), and in what order they are selected with the
    # 'L' command.
    #
    TRNINIT="-x6ls -K -e"

    [...]

    Elijah
    ------
    has 147 lines of configuration (not comments) in his trnrc file

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