• New Neodome flood

    From Sn!pe@21:1/5 to David Ritz on Mon Jun 7 10:53:16 2021
    XPost: news.admin.net-abuse.usenet

    David Ritz <dritz@mindspring.com> wrote:

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    On Sunday, 06 June 2021 17:07 +0200,
    in article <m25yyrm3pz.fsf@raybanana.net>,
    Ray Banana <rayban@raybanana.net> wrote:

    Thus spake snipeco.2@gmail.com (Sn!pe)

    There is now a new flood running in alt.atheism, alt.usenet.kooks

    This should be the last one you'll get to see of this nonsense on E-S.

    Thanks for being a good neighbor, Ray.

    Indeed. Many thanks, Ray.

    --
    ^^ <https://youtu.be/_kqytf31a8E>

    My pet rock Gordon just is.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Neodome Admin@21:1/5 to Ray Banana on Wed Jun 9 03:44:52 2021
    XPost: news.admin.net-abuse.usenet

    Ray Banana <rayban@raybanana.net> writes:

    Thus spake snipeco.2@gmail.com (Sn!pe)

    There is now a new flood running in alt.atheism, alt.usenet.kooks

    This should be the last one you'll get to see of this nonsense on E-S.

    Just don't do it the same way The Doctor did it, Ray. I was looking at
    his solution in, I think, news.software.nntp, and if I understand
    correctly, it rejects not only articles posted to Neodome, but also
    those that just passed Neodome.

    --
    Neodome

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ray Banana@21:1/5 to All on Wed Jun 9 13:46:09 2021
    XPost: news.admin.net-abuse.usenet

    Thus spake Neodome Admin <admin@neodome.net>

    Just don't do it the same way The Doctor did it, Ray. I was looking at
    his solution in, I think, news.software.nntp, and if I understand
    correctly, it rejects not only articles posted to Neodome, but also
    those that just passed Neodome.

    Thank you for your concern, but I'm aware of the pitfalls of Cleanfeed's bad_path configuration file and I know how to filter based on the
    rightmost host name in the Path: header.

    --
    Time flies like an arrow, fruit flies like a Banana. http://www.eternal-september.org

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam H. Kerman@21:1/5 to Frank Slootweg on Thu Jun 10 00:34:44 2021
    XPost: news.admin.net-abuse.usenet

    Frank Slootweg <this@ddress.is.invalid> wrote:
    Neodome Admin <admin@neodome.net> wrote:
    "Adam H. Kerman" <ahk@chinet.com> writes:

    I wish you had the same public spirited sentiment.

    What makes you think I don't, Adam? Countless of times I've seen the
    same thing being said over and over: the advantage of Usenet compared to >>other social media is that it cannot be censored or moderated. This is >>exactly what I provide to people. Uncensored Usenet, free of charge, in
    any amounts you want, - more than you ever wanted, probably, but that's >>another question.

    I'm piggy-backing on Frank's article as Neodome Admin's article didn't
    appear on e-s.

    If a user is allowed to flood a newsgroup, he himself is disrupting the
    normal flow of discussion. That's censorship. When floods are large
    enough to shut down certain News sites, that's a denial of service
    attack.

    Quantity for the sake of quantity isn't freedom of the press given that the effect is shutting down the discussion of others -- their publishing
    activity.

    Pull the other one! Abuse of the net - in this case flooding - has
    nothing to do with censorship, quite the contrary.

    Yes.

    If you can't be bothered to - try to - prevent the abuse (of the net)
    which originates from your server, then just come out and say so, but
    don't spout this kind of nonsense to an audience which sees right
    through it.

    [...]

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ray Banana@21:1/5 to All on Sat Jun 19 06:41:11 2021
    XPost: news.admin.net-abuse.usenet

    Thus spake doctor@doctor.nl2k.ab.ca (The Doctor)

    Thank you for your concern, but I'm aware of the pitfalls of Cleanfeed's >>bad_path configuration file and I know how to filter based on the
    rightmost host name in the Path: header.


    Not my solution. Someone gave it to me.

    I know by now. However, adding the hostname to the ME: site definition
    in the newsfeeds file causes the same collateral damage as Cleanfeed's bad_path:
    /-------------------------------------------------------------------
    | If the "ME" entry has an exclusion sub-field, incoming articles are
    | rejected completely if any of the names specified in that
    | exclusion sub-field appear in their Path: headers.
    \___________________________________________________________________

    i.e. it rejects all articles that contain the excluded hostname *anywhere*
    in the Path: rather than rejecting just the articles that originate from
    that host (which is what you really want to do).

    --
    Time flies like an arrow, fruit flies like a Banana. http://www.eternal-september.org

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Thomas Hochstein@21:1/5 to bje@ripco.com on Sun Jul 18 11:17:40 2021
    bje@ripco.com wrote:

    In news.admin.net-abuse.usenet Ray Banana <rayban@raybanana.net> wrote:

    i.e. it rejects all articles that contain the excluded hostname *anywhere* in the Path: rather than rejecting just the articles that originate from that host (which is what you really want to do).

    So?

    So all articles that pass "the excluded hostname" are permanently
    rejected.

    Any system using neodome as their single outbound feed deserves what they get.

    Most news systems have multiple outbound feeds and if the one fed into neodome gets dropped, it goes on its merry way to one of the others.

    No, it doesn't - at least it won't reach you when you path-exclude news.neodome.net. The rejected article's Message-ID is logged to
    history and rejected as duplicate further on.

    This means that if your server gets the posting that went through news.neodome.net offered first, it will reject it because of the ME
    entry. If it the posting is offered again later via another route, it
    will reject it because of the history entry.

    -thh

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From bje@ripco.com@21:1/5 to Thomas Hochstein on Mon Jul 19 14:54:14 2021
    Thomas Hochstein <thh@thh.name> wrote:

    This means that if your server gets the posting that went through news.neodome.net offered first, it will reject it because of the ME
    entry. If it the posting is offered again later via another route, it
    will reject it because of the history entry.


    Oh, boo-hoo.

    It's cheap insurance against the retard who runs it deciding to test the
    waters again by opening up anonymous posting.

    For today, since midnight, there is a total of 63 rejects based on "Unwanted site" and more than half of those show a message-id using @neodome.net.

    It's not significant. Not missing anything of importance.

    -bruce
    bje@ripco.com

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