uk.comp.os.linux is banned on news.aioe.org

[Spiros Bousbouras]

Just a heads up : in the last few weeks there has been an issue on
uk.comp.os.linux where almost every post gets reposted by an
apparently broken gateway with altered headers. For example

From: Davey <da...@example.invalid>
Newsgroups: uk.comp.os.linux
Subject: Re: Tesseract alternative
Date: Wed, 18 Aug 2021 09:41:08 +0100
Organization: A noiseless patient Spider
Lines: 20
Message-ID: <sfih34$gsi$1...@dont-email.me>
References: <sfam52$f5g$1...@dont-email.me>

got reposted as

From: Davey <Da...@f1.n221.z2.fidonet.fi>
Newsgroups: uk.comp.os.linux
Subject: Re: Tesseract alternative
Date: Wed, 18 Aug 2021 09:41:08 +0200
Organization: rbb soupgate
Message-ID: <33047...@f1.n221.z2.fidonet.fi>
References: <13329...@f0.n0.z0.fidonet.org>

For the reposts the header always had

Injection-Info: gioia.aioe.org; [...]

So on 2021-08-22 I tried posting on uk.comp.os.linux through news.aioe.org ,
which is my usual posting server , and got

Can't post the given input.
441 Banlist

.I wasn't sure whether it was my IP which was banned for some reason but I made
a post on alt.test shortly after and that was successful. So it is the group
which is banned.

So if you use news.aioe.org and want to post on uk.comp.os.linux , you need
to make alternative arrangements. I registered with eternal-september .

--
vlaho.ninja/prog

[Sn!pe]

See:

<https://news.aioe.org/documentation/access-restrictions/>

Newsgroups closed for posting:
uk.comp.os.linux messages duplication

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

My pet rock Gordon just is.

[Spiros Bousbouras]

On Mon, 23 Aug 2021 20:35:02 +0100
snip...@gmail.com (Sn!pe) wrote:

> Spiros Bousbouras <spi...@gmail.com> wrote:

[...]

> > So on 2021-08-22 I tried posting on uk.comp.os.linux through
> > news.aioe.org , which is my usual posting server , and got
> >
> > Can't post the given input.
> > 441 Banlist
> >
> > .I wasn't sure whether it was my IP which was banned for some reason but I
> > made a post on alt.test shortly after and that was successful. So it is
> > the group which is banned.
> >
> > So if you use news.aioe.org and want to post on uk.comp.os.linux , you
> > need to make alternative arrangements. I registered with
> > eternal-september .
> >
>
> See:
>
> <https://news.aioe.org/documentation/access-restrictions/>
>
> Newsgroups closed for posting:
> uk.comp.os.linux messages duplication

Thanks. It would have been useful if the 441 error included that link.

[Grant Taylor]

On 8/23/21 1:39 PM, Spiros Bousbouras wrote:
> It would have been useful if the 441 error included that link.

Agreed.

It's not always possible, much less easy, to get such hints to surface
where we want them to. But something worth striving for.



--
Grant. . . .
unix || die

[Aioe]

Il 23/08/21 21:11, Spiros Bousbouras ha scritto:

>
> So if you use news.aioe.org and want to post on uk.comp.os.linux , you need
> to make alternative arrangements. I registered with eternal-september .
>

filter is now updated, you can post.
thank you for your alert

[Retro Guy]

I've been in contact with the admin which is the source of the duplicates. Here is his reply: "There seems to be a loop in fidonet echomail side. i will check this asap."

It appears to be an unintentional issue and hopefully he can resolve it.

Retro Guy

[Spiros Bousbouras]

On Tue, 24 Aug 2021 16:54:31 -0700
Retro Guy <retr...@novabbs.com> wrote:
> On Tue, 24 Aug 2021 16:13:50 +0200
> Aioe <est...@aioe.org> wrote:
> > filter is now updated, you can post.
> > thank you for your alert
>
> I've been in contact with the admin which is the source of the duplicates.
> Here is his reply: "There seems to be a loop in fidonet echomail side. i will
> check this asap."

Since you have his contact details perhaps you can also bring to his attention
what RFC 5537 says :

An incoming gateway MUST add a Sender header field to the news
article it forms by containing the <mailbox> of the administrator of
the gateway. Problems with the gateway may be reported to this
<mailbox>.

There was no Sender header field in the duplicated messages hence we could
not contact the gateway hence aioe had to handle it.

[Retro Guy]

Done. He's using Soupgate so the header should really be introduced there, which it probably is not. I know nothing of Soupgate other than having heard about it years ago. I think it pre-dates RFC 5537 but maybe a previous RFC states the same.

Bringing this to my attention is appreciated also, as I need to add this to the code of one of my projects soon. Thanks.