without any credential usage, like paganini and tcpreset?
Testing... testing... 123...
Testing... testing... 123...
Looking at the PATH... is this a correct analysis of the various hops?
1. news.tcpreset.net is the injection point accepting the nntp post
2. .POSTED!not-for-mail confirms it's a direct NNTP POST
3. news-fra.pugleaf.net is likely one of tcpreset's primary peers.
4. srl.newsdeef.eu is a peering from a wider European mesh perhaps?
5. newsfeed.bofh.team Interesting. Do they share a peering relationship?
6. feeder.erje.net is a free-server feed node I think
7. 2.eu.feeder.erje.net another node, similar to what eternal-sept uses
8. news2.arglkargh.de now in the mid-tier general European mesh?
9. The final receiving peer (which varies per user)
Is this analysis of the path correct?
If not, what's the correct analysis?
!not-for-mail is a convention. You'll see that in a moderated newsgroup
in which the user's proto article isn't injected into Usenet till
approved by the moderator, and not directly by the user.
Am 20.06.26 um 16:33 schrieb Adam H. Kerman:
!not-for-mail is a convention. You'll see that in a moderated newsgroup
in which the user's proto article isn't injected into Usenet till
approved by the moderator, and not directly by the user.
You will see that in other articles too.
Dunno why that is included, as >https://datatracker.ietf.org/doc/html/rfc1036#section-2.1.6 explicitly
says it should not be used for mail replies.
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.
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.
LASTRELAY!news2.arglkargh.de!2.eu.feeder.erje.net!feeder.erje.net!newsfeed.bofh.team!srl.newsdeef.eu!news-fra.pugleaf.net!news.tcpreset.net!.POSTED!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!news.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.
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.
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 shall try harder to ignore ou from now on.
Anne Frank wrote:
without any credential usage, like paganini and tcpreset?
Testing... testing... 123...
CONTACT!!! Bearing unknown!!
https://www.planetusenet.com/groups/news.admin.peering/articles/3917 https://www.virebent.art/nntp.html
Speaking of news tcpreset net i would look for an https address with a >domain of the same name like https://news tcpreset net.
I invite you to inform you that everything should be there.
Some nym wrote:
https://www.planetusenet.com/groups/news.admin.peering/articles/3917
https://www.virebent.art/nntp.html
Links taken at random? I expected more from you.
:)
On 6/21/2026 10:23:34 AM, Mr. Man-wai Chang wrote:
CONTACT!!! Bearing unknown!!
Agree the tcpreset admin is incognito, almost certainly on purpose.
Even the web site has an anonymous registration identity.
https://www.planetusenet.com/groups/news.admin.peering/articles/3917
https://www.virebent.art/nntp.html
Gabx <dev@nu.ll> wrote:
Speaking of news tcpreset net i would look for an https address with a >>domain of the same name like https://news tcpreset net.
I invite you to inform you that everything should be there.
Some nym wrote:
https://www.planetusenet.com/groups/news.admin.peering/articles/3917
https://www.virebent.art/nntp.html
Links taken at random? I expected more from you.
:)
Why? The complaints were vague and random. I think he should get his
money refunded.
what's your problem instead?
https://www.virebent.art/nntp.html
What would be nice for those like me who are noobs is a set of steps for using the mail-to-news gateway (which I don't see described on that page).
Some nym wrote:
On 6/21/2026 10:23:34 AM, Mr. Man-wai Chang wrote:
CONTACT!!! Bearing unknown!!
Agree the tcpreset admin is incognito, almost certainly on purpose.
Even the web site has an anonymous registration identity.
https://www.planetusenet.com/groups/news.admin.peering/articles/3917
This is not my website and has nothing to do with id or contact.
I will explain,
I accidentally posted a promotion for my Usenet infrastructure in NAP,
I've already been insulted and pilloried for this insignificant mistake anyway. I apologized,
what's your problem instead?
https://www.virebent.art/nntp.html
Promotion has never been my strong point and in the end I care little
about being accommodating.
Virebent and Tcpreset are bastions of digital freedom.
We give exactly what we say.
Some nym <foo@bar.invalid> 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.
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?
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.
Some nym wrote:
What would be nice for those like me who are noobs is a set of steps
for using the mail-to-news gateway (which I don't see described on that
page).
Probably the easiest way to use a mail2news gateway, anonymously, is to
use the brand new Mixfit YAMN Remailer Mixnet client for Windows, Linux
and Android. https://github.com/Ch1ffr3punk/Mixfit.
In the To: header you set for example mail2news@dizum.com. Play with
Mixfit a bit in a test group and you will see how easy it is to post anonymously.
On Mon, 22 Jun 2026 17:40:25 +0000, Ch1ffr3punk wrote:
Some nym wrote:
What would be nice for those like me who are noobs is a set of steps
for using the mail-to-news gateway (which I don't see described on that page).
Probably the easiest way to use a mail2news gateway, anonymously, is to
use the brand new Mixfit YAMN Remailer Mixnet client for Windows, Linux
and Android. https://github.com/Ch1ffr3punk/Mixfit.
In the To: header you set for example mail2news@dizum.com. Play with
Mixfit a bit in a test group and you will see how easy it is to post anonymously.
I'd suggest they use news.tcpreset if they want anominity, a number of us (server admins) -but not all, block mail2news gateways because of extreme abuses, the muppets who abused google are finding other methods to flood
us with crap
On Mon, 22 Jun 2026 17:40:25 +0000, Ch1ffr3punk wrote:
Some nym wrote:
What would be nice for those like me who are noobs is a set of steps
for using the mail-to-news gateway (which I don't see described on
that page).
Probably the easiest way to use a mail2news gateway, anonymously, is
to use the brand new Mixfit YAMN Remailer Mixnet client for Windows,
Linux and Android. https://github.com/Ch1ffr3punk/Mixfit.
Mixfit a bit in a test group and you will see how easy it is to post
anonymously.
I'd suggest they use news.tcpreset if they want anominity, a number of
us (server admins) -but not all, block mail2news gateways because of
extreme abuses, the muppets who abused google are finding other
methods to flood us with crap
Well, I have never seen mail2news gateway postings been blocked over the decades, as remailer users rely on them.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 70 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 37:39:07 |
| Calls: | 948 |
| Calls today: | 2 |
| Files: | 1,325 |
| Messages: | 280,462 |