Please,
can someone write a list of *FREE of charge* Usenet servers that *allow posting* (also with registration, if needed) and are still stable and functioning?
Here Below my small list of servers that I test(ed) and I use(d).
All of them are still working, to date!
- blueworldhosting.com -(registration required)
- corradoroberto.it -(registration required)
- Eternal-September.org -(registration required)
- paganini.bofh.team -(NO reg. Required) - using/testing it right now!
- solani.org -(registration required)
OHERS?? MTIA
Taf< wrote:
Please,
can someone write a list of *FREE of charge* Usenet servers that *allow
posting* (also with registration, if needed) and are still stable and
functioning?
Here Below my small list of servers that I test(ed) and I use(d).
All of them are still working, to date!
- blueworldhosting.com -(registration required)
- corradoroberto.it -(registration required)
- Eternal-September.org -(registration required)
- paganini.bofh.team -(NO reg. Required) - using/testing it right now!
- solani.org -(registration required)
OHERS?? MTIA
news.tcpreset.net
https://news.tcpreset.net
Gabx
OHERS?? MTIA
news.tcpreset.net
https://news.tcpreset.net
Gabx
tnxalot
Please,--
can someone write a list of *FREE of charge* Usenet servers that *allow posting* (also with registration, if needed) and are still stable and functioning?
Here Below my small list of servers that I test(ed) and I use(d).
All of them are still working, to date!
- blueworldhosting.com -(registration required)
- corradoroberto.it -(registration required)
- Eternal-September.org -(registration required)
- paganini.bofh.team -(NO reg. Required) - using/testing it right now!
- solani.org -(registration required)
OHERS?? MTIA
news.tcpreset.net
https://news.tcpreset.net
{news.} neodum & dizum [dot] net
enjoy
Afk <no.thanks@you.spamer> wrote:
{news.} neodum & dizum [dot] net
enjoy
news.neodum.net did not connect. pinging and nslookup failed for neodum.net domain. :(
news.dizum.net worked nicely. No registration to read and post via SSL port 563. :)
On Fri, 11/21/2025 10:16 PM, Ant wrote:
Afk <no.thanks@you.spamer> wrote:
{news.} neodum & dizum [dot] net
enjoy
news.neodum.net did not connect. pinging and nslookup failed for neodum.net domain. :(
news.dizum.net worked nicely. No registration to read and post via SSL port 563. :)
neodome is spelled neodome .
Paul <nospam@needed.invalid> wrote:
On Fri, 11/21/2025 10:16 PM, Ant wrote:
Afk <no.thanks@you.spamer> wrote:
{news.} neodum & dizum [dot] net
enjoy
news.neodum.net did not connect. pinging and nslookup failed for neodum.net domain. :(
news.dizum.net worked nicely. No registration to read and post via SSL port 563. :)
neodome is spelled neodome .
Thanks, Paul! No posting and SSL/TLS port 563? :(
I assume no binaries.
<---
Someone else might know the history. Server may have had
a rough ride in the past, causing the owner to think defensively.
On Sat, 22 Nov 2025 01:53:12 -0500, Paul wrote:[...]
Someone else might know the history. Server may have had
a rough ride in the past, causing the owner to think defensively.
AFAIK it's used by trolls.
s|b <me@privacy.invalid> wrote:
On Sat, 22 Nov 2025 01:53:12 -0500, Paul wrote:[...]
Someone else might know the history. Server may have had
a rough ride in the past, causing the owner to think defensively.
AFAIK it's used by trolls.
Neodome was the source of a number of floods a few years ago;
the story is in nanau. It may have been redeemed since then,
I'm not aware of any current problems.
Moments ago I successfully made my first post starting from >Paganini.BOFH.team
Thanks to the BOFH team!
Interestingly a moment earlier I failed with the only difference being
that the successful version's body is all in ASCII (with German Word fuer >spelled as 4 ASCII letters), whereas the failed version has this German
word spelled as one Unicode non-ASCII letter (with an Umlaut) plus two
ASCII letters.
The Unicode non-ASCII From: field in both versions is unchanged.
Alpine showed an error message about an invalid content type while
failing.
nntp-server=paganini.BOFH.team/home/gloucester $
On Sun, 21 Dec 2025, Adam H. Kerman wrote:
"Alpine is doing its job. That is indeed an error, a mismatch between the >character set declaration and characters you used in the composer."
Is this really an Alpine issue instead of a BOFH.team issue? I used
exactly the same copy of Alpine to post the Unicode non-ASCII body of >news:c062aef9-ac4c-6f44-d64a-d0fc9f00b013@insomnia247.nl
on
Date: Sat, 6 Dec 2025 13:53:05 +0100
The only difference in settings is the sending NNTP server - i.e. nothing
to do with a character set or editing. I.e.
/home/gloucester $ diff
Gloucester_.pinerc_backed_up_on_21st_December_2025_before_replacing_Eternal_September_for_posting .pinerc
25c25
< nntp-server=news.eternal-September.org/user=ColinPaulGloster
---
nntp-server=paganini.BOFH.team/home/gloucester $
thanks-to@Taf.com wrote:
On Sun, 21 Dec 2025, Adam H. Kerman wrote:
"Alpine is doing its job. That is indeed an error, a mismatch between the
character set declaration and characters you used in the composer."
Is this really an Alpine issue instead of a BOFH.team issue? I used
exactly the same copy of Alpine to post the Unicode non-ASCII body of
news:c062aef9-ac4c-6f44-d64a-d0fc9f00b013@insomnia247.nl
on
Date: Sat, 6 Dec 2025 13:53:05 +0100
The only difference in settings is the sending NNTP server - i.e. nothing
to do with a character set or editing. I.e.
/home/gloucester $ diff
Gloucester_.pinerc_backed_up_on_21st_December_2025_before_replacing_Eternal_September_for_posting .pinerc
25c25
< nntp-server=news.eternal-September.org/user=ColinPaulGloster
---
nntp-server=paganini.BOFH.team/home/gloucester $
I can't offer a further opinion without having access to logs as to why
the proto article was rejected. If I guessed wrong and it wasn't a nonstandard character set description, then I agree that alpine passed
along an error message from the server and wasn't informing you of an
issue found by the client.
Did you check that option? Do you have anything set?
Il 21/12/2025 17:12, Adam H. Kerman ha scritto:
thanks-to@Taf.com wrote:
On Sun, 21 Dec 2025, Adam H. Kerman wrote:
"Alpine is doing its job. That is indeed an error, a mismatch between the >>>character set declaration and characters you used in the composer."
Is this really an Alpine issue instead of a BOFH.team issue? I used >>>exactly the same copy of Alpine to post the Unicode non-ASCII body of >>>news:c062aef9-ac4c-6f44-d64a-d0fc9f00b013@insomnia247.nl
on
Date: Sat, 6 Dec 2025 13:53:05 +0100
The only difference in settings is the sending NNTP server - i.e. nothing >>>to do with a character set or editing. I.e.
/home/gloucester $ diff >>>Gloucester_.pinerc_backed_up_on_21st_December_2025_before_replacing_Eternal_September_for_posting .pinerc
25c25
< nntp-server=news.eternal-September.org/user=ColinPaulGloster
---
nntp-server=paganini.BOFH.team/home/gloucester $
I can't offer a further opinion without having access to logs as to why
the proto article was rejected. If I guessed wrong and it wasn't a >>nonstandard character set description, then I agree that alpine passed >>along an error message from the server and wasn't informing you of an
issue found by the client.
Did you check that option? Do you have anything set?
My filter check the content type:
text\/plain|multipart\/mixed|application\/news-groupinfo|application\/news-checkgroups|multipart\/signed|text\/html|multipart\/alternative
if the content type specified by client don't reflect the permitted
type, the post are rejected. Content type text plain is always accepted.
[...]
This version of Tin is as follows . . .
/home/gloucester $ echo $LANG
UTF-8
/home/gloucester $ tin -V
Can't set the specified locale!
/home/gloucester $ echo $LANG || |
UTF-8 |
/home/gloucester $ tin -V |
Can't set the specified locale! |
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 54 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 01:56:13 |
| Calls: | 743 |
| Files: | 1,218 |
| Messages: | 187,760 |