From Newsgroup: alt.free.newsservers
On Mon, 30 Jun 2025 06:39:19 +0200, Ivano Rossi <
Ivano.Rossi@nospam.tin.it> wrote:
On Sun, 29 Jun 2025 18:22:38 -0000 (UTC), Steve Crook wrote:
Mixmin is available on Port 563 only.
I'd like to use the nntp server news.mixmin.net:563 to post using a
newsreader to Usenet newsgroups but I can't find the allowed groups.
Should be all of the text newsgroups.
How about now?
Mixmin runs largely on autopilot. Bad things happened when a filesystem
filled up.
Thanks Mr. Crook for responding, where I'll check out if the common text >newsgroups are available for posting using news.mixmin.net:563 via nntp.
We all appreciate your efforts especially given the spammers had caused you >grief when netfront & Paolo were forced offline (as you were by your ISP). >I'll let you know via this thread if any of the most common text newsgroups >don't work using nntp (as I'm not talking about the remailer mechanism).
Much appreciated your generous support of the aging Usenet community.
been using "freenews.netfront.net" but only on occasion (e.g. once per month) for many years, just checked and it's working normally (always seems to work)
also, these enlightening (and much anticipated) updates were posted yesterday . . .
Date: Sun, 29 Jun 2025 16:58:37 -0000 (UTC)
From: Zax <admin@mixmin.net>
Newsgroups: alt.privacy.anon-server
Subject: Re: mixmin.net - staying power . . .
Message-ID: <slrn1062s5t.v08e.admin@fleegle.mixmin.net>
...
snip
Yes, it does run pretty much on autopilot. It doesn't help that its
hosting company appear to have blacklisted my own IP addresses.
The server pretty much died when /var filled up. This was caused by me
using a non-standard mail.info logfile that wasn't handled by logrotate.
When it died, it killed my yamn pinger which in-turn uncovered a yamn
bug. If no remailers are available, it crashes when attempting to send >dummies. I fixed that issue and merged a branch that addresses some
Go static checks in yamn. Maybe when I retire I'll have the time to
properly tidy it up. Not long to wait! Maybe.
Remailers and pinger should be recovering now.
--
pub 1024D/228761E7 2003-06-04 Steven Crook <steve@mixmin.net>
Key fingerprint = 1CD9 95E1 E9CE 80D6 C885 B7EB B471 80D5 2287 61E7
ssb rsa4096/832C8F4DCD904263 created: 2019-05-04 expires: 2024-05-02 usage: S >...
Date: Sun, 29 Jun 2025 18:00:05 -0000 (UTC)
From: Zax <admin@mixmin.net>
Newsgroups: alt.privacy.anon-server
Subject: Re: banana and slow
Message-ID: <slrn1062vp5.v4or.admin@fleegle.mixmin.net>
...
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Thu, 26 Jun 2025 10:14:17 -0400, SEC3 wrote in
Message-Id: <184c9d40f6a27a10$4742$586627$802601b3@news.usenetexpress.com>:
This is odd because the last known version of Yamn - the one
available at <https://github.com/crooks/yamn> - is version 0.2.6.
Correction. Zax did make changes to YAMN's code. On June 21 2024
5 days ago. <https://github.com/crooks/yamn/branches>
So. Not dead.
Further investigation shows that he has updated the version no. from
0.2.6 to 0.2.7.
Zax, come and visit us at apa-s. We miss you.
Hi,
Yes, I did a recent fix on yamn after my server filled up. I did a post >about it earlier today but my PGP signing subkey had expired so it
posted unsigned. An updated pubkey can be found here:- >https://mixmin.net/pgpkey.txt
I miss apa-s too but work, family and grandchildren are keeping me very
busy! I'll try and do some more updates to yamn in the near future.
- --
pub 1024D/228761E7 2003-06-04 Steven Crook <steve@mixmin.net>
Key fingerprint = 1CD9 95E1 E9CE 80D6 C885 B7EB B471 80D5 2287 61E7
sub rsa4096/8C45BF55CEB7248F 2025-06-29 [S] [expires: 2030-06-28] >-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEqFvjXjQA3cHqtT32jEW/Vc63JI8FAmhhfx8ACgkQjEW/Vc63 >JI/AJQ//Y54XGre71DeObLZMauhxqwUuFE45hQt+2cEk+3VWTvM+kSPmY4zNTkf2 >gSrmUACBDCfWkMG9UMJHIWk4Gn4bvRX8kK9P3UlBz37TgrMB+F7GE1SeFxWzzihy >837r0NIjqgRo3sDc2EoT+7RdVrwxLuU43a5fFwoSs49+zqRWKvpH91iXit+TkcLS >gL7tLZosVjGOD8paR+eksNgwJE1Oc+A7ecRisENdGbfF5AGHv2lCQtv77mR5etB/ >D+70p6sHxK+udRX/Rg7B600OhQQX07krnB8XckxBPzR1aBGMbT/LunlpW01MZOk8 >7ZDaYv3CzrFRm01c8dG/Z8O4jEvdd0Enuyu4gzphFTNMPTS7WZieA0B9P3NGTlJV >dVm2pYTuHzTDwGepfmZ3UgjIWm19od85vI7f8tSXZRO5oWla0dNNYGaSXSThMQql >7NijUqBNy4ythGCSG2CenxCEVyvnhIGcGXUqp0S2z+3PrgeWZZ4eZWbRq8TTmFIH >4/4QlUH8t+TOytuSPR6VKfw+gM2KATE+aY/VHduEZJq6lMC/NogbUJ2oVeOppXWL >4Z4sEaHxQmEFt8RpOtv7Vw2evXCHOq+VkZAqyR2PLcLjn/ILG6yCRK91EYS8kQk7 >zgdnt3d+H4UYFLNvfSRSr1z3h21I2XxuHCE4NKs/0kXwGtZHF0k=
=rYuR
-----END PGP SIGNATURE-----
[end quoted plain text]
"blacklisting" ips could be due to some technical issue . . . been
learning about public dns servers for use with omnimix and dynamic
dns, where some servers are shown "blacklisted" (e.g. opendns.com)
on ipfire <
https://www.ipfire.org/docs/dns/public-servers> because
they are "used in schools and homes" ... reminiscent of south park
yet it could be that some ips are singled out because of political
and religious coercion ("church of" lawyers, guns and money, etc.)
but nowadays with big brother's "a.i" watching the entire universe
forever, it's pointless to use such archaic epithets as "blacklist"
(resistance isn't futile ... it was never an option to begin with)
--- Synchronet 3.21d-Linux NewsLink 1.2