Rocksolid Light

Welcome to Rocksolid Light

mail  files  register  newsreader  groups  login

Message-ID:  

It's all magic. :-) -- Larry Wall in <7282@jpl-devvax.JPL.NASA.GOV>


computers / alt.privacy.anon-server / Having Problem Posting Through Tnet

SubjectAuthor
* Having Problem Posting Through TnetTod
+* Having Problem Posting Through TnetFritz Wuehler
|`- Having Problem Posting Through TnetTod
`- Having Problem Posting Through TnetTod

1
Having Problem Posting Through Tnet

<2tug8ido65f1niubs5klp872v3p3ie3ftj@4ax.com>

  copy mid

https://news.novabbs.org/computers/article-flat.php?id=14465&group=alt.privacy.anon-server#14465

  copy link   Newsgroups: alt.privacy.anon-server
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!1.us.feeder.erje.net!feeder.erje.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx17.iad.POSTED!not-for-mail
From: Tod@invalid.com
Newsgroups: alt.privacy.anon-server
Subject: Having Problem Posting Through Tnet
Message-ID: <2tug8ido65f1niubs5klp872v3p3ie3ftj@4ax.com>
X-Newsreader: Forte Agent 1.93/32.576 English (American)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 13
X-Complaints-To: https://www.astraweb.com/aup
NNTP-Posting-Date: Tue, 13 Jun 2023 14:26:46 UTC
Date: Tue, 13 Jun 2023 09:26:46 -0500
X-Received-Bytes: 834
 by: Tod@invalid.com - Tue, 13 Jun 2023 14:26 UTC

Tnet was fine the other day, but today I cannot post through it with
QSL. I sent a test post usig fleegle and it went through QSL
without a problem. Has Tnet changed something or other?

My Tnet SMTP settings in QSL are:

tnet
smtp.tnetconsulting.net
port: 2525
TLS
Proxies: None
Authentication: None

Re: Having Problem Posting Through Tnet

<20230613.185549.d2680ad3@remailer.frell.eu.org>

  copy mid

https://news.novabbs.org/computers/article-flat.php?id=14469&group=alt.privacy.anon-server#14469

  copy link   Newsgroups: alt.privacy.anon-server
References: <2tug8ido65f1niubs5klp872v3p3ie3ftj@4ax.com>
Subject: Re: Having Problem Posting Through Tnet
Message-Id: <20230613.185549.d2680ad3@remailer.frell.eu.org>
From: fritz@spamexpire-202306.rodent.frell.theremailer.net (Fritz Wuehler)
Date: Tue, 13 Jun 2023 18:55:49 +0200
Newsgroups: alt.privacy.anon-server
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!sewer!news.dizum.net!not-for-mail
Organization: dizum.com - The Internet Problem Provider
X-Abuse: abuse@dizum.com
Injection-Info: sewer.dizum.com - 2001::1/128
 by: Fritz Wuehler - Tue, 13 Jun 2023 16:55 UTC

In article <2tug8ido65f1niubs5klp872v3p3ie3ftj@4ax.com> Tod@invalid.com
wrote:

>Tnet was fine the other day, but today I cannot post through it with
>QSL. I sent a test post usig fleegle and it went through QSL
>without a problem. Has Tnet changed something or other?
>
>My Tnet SMTP settings in QSL are:
>
>tnet
>smtp.tnetconsulting.net
>port: 2525
>TLS
>Proxies: None
>Authentication: None

Works here with OM through Tor:

| 08:47:58.304 0 SMTP State: ########## Trying to send 5 chunks to Anon SMTP host 'smtp.tnetconsulting.net', port 2525, EHLO 'domain.invalid' (pass 1 of 5, 5 chunks) ... ##############################
| 08:47:58.304 0 SMTP State: Connecting with mail host (smtp.tnetconsulting.net:2525 - 60000:60000 - TLS required - EHLO 'domain.invalid' - SOCKS5 - no authentication) ...
| 08:47:58.304 > SMTP State: Connecting to 127.0.0.1.
| 08:48:00.601 > SMTP State: Connected.
| 08:48:06.069 0 SMTP State: Connected with 'smtp.tnetconsulting.net', port 2525
| 08:48:06.069 0 SMTP Greeting:
| 08:48:06.069 0 SMTP Protocol Capabilities: ENHANCEDSTATUSCODES|PIPELINING|EXPN|VERB|8BITMIME|SIZE|DSN|ETRN|AUTH DIGEST-MD5 CRAM-MD5|STARTTLS|DELIVERBY|HELP
| 08:48:06.069 0 SMTP Encryption: TLS supported
| 08:48:06.069 0 SMTP State: Sending chunk 1 of 5 from 'anon@domain.invalid' to 'mixmaster@remailer.paranoici.org', server 'smtp.tnetconsulting.net', port 2525 ...
| 08:48:06.366 > SMTP SSL Status Info: SSL status: "before/connect initialization"
| 08:48:06.366 > SMTP SSL Status Info: SSL status: "before/connect initialization"
| 08:48:06.366 > SMTP SSL Status Info: SSL status: "SSLv2/v3 write client hello A"
| 08:48:06.788 > SMTP SSL Status Info: SSL status: "SSLv3 read server hello A"
| 08:48:06.866 > SMTP TLA Certificate (Depth 0, REJECTED_NOT_ACTIVE - Connection not refused (Filter deactivated)):
| 08:48:06.866 Fprint : B41C2559F65FE6A11AD8CC7D8B1599DB
| 08:48:06.866 Subject: /CN=tncsrv06.tnetconsulting.net
| 08:48:06.866 Issuer : /C=US/O=Let's Encrypt/CN=R3
| 08:48:06.866 Valid : 2023-03-26 09:00:22 ... 2023-06-24 09:00:21
| 08:48:06.882 > SMTP TLA Certificate (Depth 0, REJECTED_NOT_ACTIVE - Connection not refused (Filter deactivated)):
| 08:48:06.882 Fprint : B41C2559F65FE6A11AD8CC7D8B1599DB
| 08:48:06.882 Subject: /CN=tncsrv06.tnetconsulting.net
| 08:48:06.882 Issuer : /C=US/O=Let's Encrypt/CN=R3
| 08:48:06.882 Valid : 2023-03-26 09:00:22 ... 2023-06-24 09:00:21
| 08:48:06.882 > SMTP SSL Status Info: SSL status: "SSLv3 read server certificate A"
| 08:48:06.882 > SMTP SSL Status Info: SSL status: "SSLv3 read server key exchange A"
| 08:48:06.960 > SMTP SSL Status Info: SSL status: "SSLv3 read server certificate request A"
| 08:48:06.960 > SMTP SSL Status Info: SSL status: "SSLv3 read server done A"
| 08:48:06.960 > SMTP SSL Status Info: SSL status: "SSLv3 write client certificate A"
| 08:48:06.976 > SMTP SSL Status Info: SSL status: "SSLv3 write client key exchange A"
| 08:48:06.976 > SMTP SSL Status Info: SSL status: "SSLv3 write change cipher spec A"
| 08:48:06.976 > SMTP SSL Status Info: SSL status: "SSLv3 write finished A"
| 08:48:06.976 > SMTP SSL Status Info: SSL status: "SSLv3 flush data"
| 08:48:07.241 > SMTP SSL Status Info: SSL status: "SSLv3 read server session ticket A"
| 08:48:07.241 > SMTP SSL Status Info: SSL status: "SSLv3 read finished A"
| 08:48:07.241 > SMTP SSL Status Info: SSL status: "SSL negotiation finished successfully"
| 08:48:07.241 > SMTP SSL Status Info: SSL status: "SSL negotiation finished successfully"
| 08:48:07.241 > SMTP SSL Status Info: Cipher: name = ECDHE-RSA-AES256-GCM-SHA384; description = ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(256) Mac=AEAD|; bits = 256; version = TLSv1/SSLv3;
| 08:48:09.460 0 SMTP State: Sending chunk 2 of 5 from 'anon@domain.invalid' to 'mixmaster@remailer.paranoici.org', server 'smtp.tnetconsulting.net', port 2525 ...
| 08:48:11.398 0 SMTP State: Sending chunk 3 of 5 from 'anon@domain.invalid' to 'remailer@dizum.com', server 'smtp.tnetconsulting.net', port 2525 ...
| 08:48:13.226 0 SMTP State: Sending chunk 4 of 5 from 'anon@domain.invalid' to 'mixmaster@remailer.paranoici.org', server 'smtp.tnetconsulting.net', port 2525 ...
| 08:48:15.022 0 SMTP State: Sending chunk 5 of 5 from 'anon@domain.invalid' to 'remailer@dizum.com', server 'smtp.tnetconsulting.net', port 2525 ...
| 08:48:17.038 0 SMTP State: Mail was sent in 5 chunks.
| 08:48:17.319 > SMTP State: Disconnecting.
| 08:48:17.319 > SMTP Response: tncsrv06.tnetconsulting.net closing connection
| 08:48:17.319 > SMTP State: Disconnected.
| 08:48:17.319 0 SMTP State: Done sending ...
| 08:48:17.319 0 SMTP State: Mail has been sent in 5 chunks - 0 direct, 5 joint, 0 normal
| 08:48:17.319 0 ####################>>>>> SMTP output o.k. <<<<<####################
| 08:48:17.319 D Dummy message was sent.

But it looks as if the relay list has to be updated, as
yamn@erienetworks.net gets refused:

| 09:01:22.407 0 SMTP Error: <yamn@erienetworks.net>... Relaying denied. IP name lookup failed [23.129.64.210]: 250 - Reset state

Re: Having Problem Posting Through Tnet

<s8fh8il4e5u6hscm5cc2ef0hhcdtpos84u@4ax.com>

  copy mid

https://news.novabbs.org/computers/article-flat.php?id=14470&group=alt.privacy.anon-server#14470

  copy link   Newsgroups: alt.privacy.anon-server
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx10.iad.POSTED!not-for-mail
From: Tod@invalid.com
Newsgroups: alt.privacy.anon-server
Subject: Re: Having Problem Posting Through Tnet
Message-ID: <s8fh8il4e5u6hscm5cc2ef0hhcdtpos84u@4ax.com>
References: <2tug8ido65f1niubs5klp872v3p3ie3ftj@4ax.com> <20230613.185549.d2680ad3@remailer.frell.eu.org>
X-Newsreader: Forte Agent 1.93/32.576 English (American)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 32
X-Complaints-To: https://www.astraweb.com/aup
NNTP-Posting-Date: Tue, 13 Jun 2023 19:03:11 UTC
Date: Tue, 13 Jun 2023 14:03:11 -0500
X-Received-Bytes: 1680
 by: Tod@invalid.com - Tue, 13 Jun 2023 19:03 UTC

On Tue, 13 Jun 2023 18:55:49 +0200, Fritz Wuehler
<fritz@spamexpire-202306.rodent.frell.theremailer.net> wrote:

>In article <2tug8ido65f1niubs5klp872v3p3ie3ftj@4ax.com> Tod@invalid.com
>wrote:
>
>>Tnet was fine the other day, but today I cannot post through it with
>>QSL. I sent a test post usig fleegle and it went through QSL
>>without a problem. Has Tnet changed something or other?
>>
>>My Tnet SMTP settings in QSL are:
>>
>>tnet
>>smtp.tnetconsulting.net
>>port: 2525
>>TLS
>>Proxies: None
>>Authentication: None
>
>Works here with OM through Tor:
>
>| 08:47:58.304 0 SMTP State: ########## Trying to send 5 chunks to Anon SMTP host 'smtp.tnetconsulting.net', port 2525, EHLO 'domain.invalid' (pass 1 of 5, 5 chunks) ... ##############################

Edit

>
>But it looks as if the relay list has to be updated, as
>yamn@erienetworks.net gets refused:
>
>| 09:01:22.407 0 SMTP Error: <yamn@erienetworks.net>... Relaying denied. IP name lookup failed [23.129.64.210]: 250 - Reset state

I'm not using yamn.

Re: Having Problem Posting Through Tnet

<bc8j8itt4t526qfgc3fbjd22dq2i1b5c7i@4ax.com>

  copy mid

https://news.novabbs.org/computers/article-flat.php?id=14486&group=alt.privacy.anon-server#14486

  copy link   Newsgroups: alt.privacy.anon-server
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!fx18.iad.POSTED!not-for-mail
From: Tod@invalid.com
Newsgroups: alt.privacy.anon-server
Subject: Re: Having Problem Posting Through Tnet
Message-ID: <bc8j8itt4t526qfgc3fbjd22dq2i1b5c7i@4ax.com>
References: <2tug8ido65f1niubs5klp872v3p3ie3ftj@4ax.com>
X-Newsreader: Forte Agent 1.93/32.576 English (American)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 16
X-Complaints-To: https://www.astraweb.com/aup
NNTP-Posting-Date: Wed, 14 Jun 2023 11:17:39 UTC
Date: Wed, 14 Jun 2023 06:17:39 -0500
X-Received-Bytes: 1033
 by: Tod@invalid.com - Wed, 14 Jun 2023 11:17 UTC

On Tue, 13 Jun 2023 09:26:46 -0500, Tod@invalid.com wrote:

>Tnet was fine the other day, but today I cannot post through it with
>QSL. I sent a test post usig fleegle and it went through QSL
>without a problem. Has Tnet changed something or other?
>
>My Tnet SMTP settings in QSL are:
>
>tnet
>smtp.tnetconsulting.net
>port: 2525
>TLS
>Proxies: None
>Authentication: None

Tnet is working for me today. Ain't gotta clue what happened.


computers / alt.privacy.anon-server / Having Problem Posting Through Tnet

1
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor