Re: tcpreset

On 20 Jun 2026, "Adam H. Kerman" <[email protected]> posted some
news:[email protected]: 

> Some nym <[email protected]> wrote:
> 
>>>This addresses an instance in which
>>>not-for-mail appears on path even though the user did not submit his
>>>proto article for injection himself.
> 
>>AFAICT, the Path header only shows that the proto-article was injected
>>by the server news.tcpreset.net. The presence of the pseudo-sites
>>POSTED and not-for-mail indicates that the article was posted directly
>>by a user via NNTP and that no email-based injection was involved.
> 
> That's not a concept. It's not possible. There has to be a gateway. I
> just gave you an example in which the user does not submit his own
> article for injection. The moderator approves the proto article then
> submits it for injection. There is a gateway. There are mailing lists
> gated to and from Usenet, which is possible thanks to the shared
> format. 
> 
> There are mail2news servers; these are literal gateways.
> 
> If the proto article travelled some portion of the way to Usenet via
> email relays, these are not shown on Path. Path begins with injection.
> 
> Since Marco had me reread RFC 1036, I remembered why not-for-mail is
> used at all.

Chuckle...now there's a ruinous source.

>>LASTRELAY!news2.arglkargh.de!2.eu.feeder.erje.net!feeder.erje.net!newsf
>>eed.bofh.team!srl.newsdeef.eu!news-fra.pugleaf.net!news.tcpreset.net!.P
>>OSTED!not-for-mail 
>>LASTRELAY!news2.arglkargh.de!2.eu.feeder.erje.net!feeder.erje.net!news.
>>mb-net.net!open-news-network.org!srl.newsdeef.eu!news-fra.pugleaf.net!n
>>ews.tcpreset.net!.POSTED!not-for-mail 
> 
>>news.tcpreset.net - injecting server that accepted the post from the
>>user POSTED - the article originated from a user session, not from a
>>peer. not-for-mail - it was not injected via email or a mail-to-news
>>gateway. 
> 
> Wrong. You'd see the News side of the gateway but not the gateway
> itself, I think.
> 
> Uh, try it yourself? Doesn't dizum still have an associated mail2news
> gateway?

One of the most reliable in Usenet history.

>>It seems to me, an outside observer, that the Path header does not
>>reveal the user's connection method. I don't see how it can prove or
>>disprove whether the posting was done via clearnet NNTP, Tor, I2P,
>>VPN, or any other transport.
> 
> I ate a ham sandwich on the same day I posted to Usenet. That's not
> revealed on Path either.
> 
>>Mostly what I was asking about, given that news-fra.pugleaf.net and
>>srl.newsdeef.eu appear identically in both paths, is whether it is
>>reasonable to infer that news.tcpreset.net uses a consistent upstream
>>feed route through these peers when propagating articles toward those
>>destinations?
> 
> I already gave you an answer, which you clearly did not like. I shall
> try harder to ignore ou from now on.

lol, smh.