Dear All,

we are running an Usenet server with local groups only.

Only *.test groups accepts unauthorized posts here. With the advent of
Thunderbird's NNTP implementation in JS we get a some complains that it
is impossible to post to the server.

We have added information to our Web page, but we also want to keep the
message in the *.test group.
We tried posting a message with the date in the future (like year 2023),
but INN is rejecting the post.

Is there any other way to protect the message? We can access the files
and it is possible to alter both the content and file attributes.

--
ejs
news://news.rkm.lt

ejs <Usernet.eternal-september@seniejitrakai.net> writes:

> we are running an Usenet server with local groups only.

> Only *.test groups accepts unauthorized posts here. With the advent of
> Thunderbird's NNTP implementation in JS we get a some complains that it
> is impossible to post to the server.

> We have added information to our Web page, but we also want to keep the
> message in the *.test group. We tried posting a message with the date
> in the future (like year 2023), but INN is rejecting the post.

> Is there any other way to protect the message? We can access the files and
> it is possible to alter both the content and file attributes.

There have been various proposals for how to do pinned messages, but so
far as I know no one has ever implemented any of them.

Your best bet with existing technology is probably to post a message with
an Expires far into the future and make sure your expiration rules for the
relevant group allow Expires to override the normal expiration period.
That will eventualy make that the first unexpired message in the group.
(You may have to add some rules to protect against users abusing Expires
as well.)

--
Russ Allbery (eagle@eyrie.org) <https://www.eyrie.org/~eagle/>

Please post questions rather than mailing me directly.
<https://www.eyrie.org/~eagle/faqs/questions.html> explains why.

2022-10-03 22:30, Russ Allbery rašė:
> ejs <Usernet.eternal-september@seniejitrakai.net> writes:

> Your best bet with existing technology is probably to post a message with
> an Expires far into the future and make sure your expiration rules for the
> relevant group allow Expires to override the normal expiration period.
> That will eventualy make that the first unexpired message in the group.
> (You may have to add some rules to protect against users abusing Expires
> as well.)

Thank you for the response.

We are testing this suggestion right now.

One way of dealing with 'Expires' headers is to allow them from
authorized users only, where Perl/Pyhon filtering comes handy.

--
ejs
news://news.rkm.lt