From Newsgroup: news.software.nntp

At Tue, 4 Nov 2025 07:28:17 -0000 (UTC), Lawrence DrCOOliveiro
<ldo@nz.invalid> wrote:

On Tue, 4 Nov 2025 00:24:12 -0000 (UTC), Richard Tobin wrote:

Whichever way you do it, the article has a date header.

That date header comes from the NNTP client. Which could have a
completely wrong idea of the date/time.

Unless I'm mistaken, most NNTP reader connections won't accept
a POST Date: header too far from the current time.

(I haven't been a news admin for going on 20 years, so my memory
may be faulty.)

And, an anecdote: I used to graph article transit time by comparing
the article Date: to the arrival time, and discovered that most people's software was accurate enough to determine if a feed was slow. That
was in the 00's though, so maybe things are different now.

Anyway, it was fairly easy, since that info is in the history
file.

x-posted and fu2 news.software.nntp.
--
-v ASUS TUF DASH F15 x86_64 NVIDIA RTX 3060 Mobile 6G
OS: Linux 6.14.0-35-generic D: Mint 22.2 DE: Xfce 4.18
NVIDIA: 510.47.03 Mem: 15.9G
"If it's stupid and works, then it ain't stupid"
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: news.software.nntp

On 04.11.2025 11:35 Uhr vallor wrote:

Unless I'm mistaken, most NNTP reader connections won't accept
a POST Date: header too far from the current time.

reader connections.
Peering connections do not use the POST command.

E.g.
Message-ID:
<de08b15b-135e-4e4e-9b98-7770016194aa@c10g2000yqh.googlegroups.com>
Date: Sat, 16 Oct 2010 05:49:35 -0700 (PDT)

I assume the posting was imported into blueworldhosting (this is an
archive too and the operator might import old articles to it) and got distributed via normal peering connections. E-S accepted it.
--
kind regards
Marco

Send spam to 1762252517muell@stinkedores.dorfdsl.de

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: news.software.nntp

On Nov 4, 2025 at 1:02:04rC>PM CST, "Marco Moock" <mm@dorfdsl.de> wrote:

On 04.11.2025 11:35 Uhr vallor wrote:

Unless I'm mistaken, most NNTP reader connections won't accept
a POST Date: header too far from the current time.

reader connections.
Peering connections do not use the POST command.

E.g.
Message-ID: <de08b15b-135e-4e4e-9b98-7770016194aa@c10g2000yqh.googlegroups.com>
Date: Sat, 16 Oct 2010 05:49:35 -0700 (PDT)

I assume the posting was imported into blueworldhosting (this is an
archive too and the operator might import old articles to it) and got distributed via normal peering connections. E-S accepted it.

On which server are these old articles being seen? They should not be coming from BlueWorldHosting. The feeder that we use for peering does not accept articles older than 3 days.

None of our backend servers are configured to talk directly to the feeder. The only articles that can traverse from the backend to the feeder are articles posted from authenticated users via nnrpd.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: news.software.nntp

On 04.11.2025 22:43 Uhr Jesse Rehmer wrote:

On which server are these old articles being seen? They should not be
coming from BlueWorldHosting. The feeder that we use for peering does
not accept articles older than 3 days.

That are all the headers:

Path: nntp.eternal-september.org!eternal-september.org!feeder.eternal-september.org!nnrp.usenet.blueworldhosting.com!!spool1.usenet.blueworldhosting.com!not-for-mail
From: Hazel LURRY <cadygefatogireko@gmail.com>
Newsgroups: pl.rec.kuchnia,openwatcom.users.fortran,nl.misc,news.software.nntp,news.groups
Subject: HAIR STYLE
Date: Sat, 16 Oct 2010 05:49:35 -0700 (PDT)
Organization: http://groups.google.com
Lines: 3351
Message-ID: <de08b15b-135e-4e4e-9b98-7770016194aa@c10g2000yqh.googlegroups.com> NNTP-Posting-Host: 24.166.12.19
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: posting.google.com 1287233377 14985 127.0.0.1 (16 Oct 2010 12:49:37 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sat, 16 Oct 2010 12:49:37 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: c10g2000yqh.googlegroups.com; posting-host=24.166.12.19; posting-account=g9pZfgoAAADIMlwCA-PbJNtNjKC2HUEE
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0;
Trident/4.0; GTB6.5; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR
3.0.04506; .NET CLR 3.5.21022),gzip(gfe)
Xref: feeder.eternal-september.org pl.rec.kuchnia:63408 openwatcom.users.fortran:9 nl.misc:1379 news.software.nntp:12281 news.groups:15483
--
kind regards
Marco

Send spam to 1762292616muell@stinkedores.dorfdsl.de

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: news.software.nntp

On Tue, 04 Nov 2025 22:43:36 +0000, Jesse Rehmer wrote:

On Nov 4, 2025 at 1:02:04rC>PM CST, "Marco Moock" <mm@dorfdsl.de> wrote:

E.g.
Message-ID:
<de08b15b-135e-4e4e-9b98-7770016194aa@c10g2000yqh.googlegroups.com>
Date: Sat, 16 Oct 2010 05:49:35 -0700 (PDT)

I assume the posting was imported into blueworldhosting (this is an
archive too and the operator might import old articles to it) and got
distributed via normal peering connections. E-S accepted it.

On which server are these old articles being seen? They should not be
coming from BlueWorldHosting. The feeder that we use for peering does
not accept articles older than 3 days.

None of our backend servers are configured to talk directly to the
feeder. The only articles that can traverse from the backend to the
feeder are articles posted from authenticated users via nnrpd.

I think you might find it was E-S re-kicking things when you see its also
for group openwatcom.users.fortran


There is an openwatcom thread going around where Ray says he re-enabled
those groups a couple days back, thats possibly why E-S users see it,

I ran my openaxs test scipt and only you and paganini have that MID
(E-S not open access read, so script doesnt check it)

If I was a betting man, thats where id place my bets.
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: news.software.nntp

On Nov 5, 2025 at 1:26:48rC>AM CST, "Marco Moock" <mm@dorfdsl.de> wrote:

On 04.11.2025 22:43 Uhr Jesse Rehmer wrote:

On which server are these old articles being seen? They should not be
coming from BlueWorldHosting. The feeder that we use for peering does
not accept articles older than 3 days.

That are all the headers:

Path: <nntp.eternal-september.org>!<eternal-september.org>!<feeder.eternal-septemb er.org> !<nnrp.usenet.blueworldhosting.com>!!<spool1.usenet.blueworldhosting.com>!no t-for
-mail

I see, these are articles that were pulled by ES. If they had been pushed out through peering from me, you would see <usenet.blueworldhosting.com>!<diablo1.usenet.blueworldhosting.com> in the
Path
header.
--- Synchronet 3.21a-Linux NewsLink 1.2