Newsgroups: alt.free.newsservers,alt.free.nntp,news.software.nntp
Path: news.neodome.net!server.example.net!sewer!news.dizum.net!not-for-mail >Injection-Info: sewer.dizum.com - 2001::1/128
Looks like it's kerplunked.
Newsgroups: alt.free.newsservers,alt.free.nntp,news.software.nntp
Path: news.neodome.net!server.example.net!sewer!news.dizum.net!not-for-mail >Injection-Info: sewer.dizum.com - 2001::1/128
Looks like it's kerplunked.
...[end quoted excerpts]
Inn2 Server Status
...
lux-feed1.newsdeef.eu
https://lux-feed1.newsdeef.eu/inn/inn_status.htm
Updated: Sun Jan 18 01:51:43 2026
(peers: 3, active-cxns: 3, sleeping-cxns: 0)
...
Innfeed Status
...
lux-feed1.newsdeef.eu
https://lux-feed1.newsdeef.eu/inn/innfeed.status.txt
Updated: Sun Jan 18 01:45:06 2026
...
Cleanfeed Status
...
lux-feed1.newsdeef.eu
https://lux-feed1.newsdeef.eu/inn/cleanfeed.stats.html
Report generated: Sun Jan 18 01:50:01 2026
Newsgroups: alt.free.newsservers,alt.free.nntp,news.software.nntp
Path: news.neodome.net!server.example.net!sewer!news.dizum.net!not-for-mail >Injection-Info: sewer.dizum.com - 2001::1/128
Looks like it's kerplunked.
If your IP address is blacklisted by a hosting company, it means that it has been[end quoted "search assist"]
flagged for sending spam or malicious content, which can prevent your emails from
being delivered. You can check if your IP is blacklisted using various online >tools that compare it against known blacklist databases. dnschecker.org abusix.com
Understanding IP Address Blacklisting
What is IP Address Blacklisting?
IP address blacklisting is a method used by networks to block specific IP >addresses suspected of sending spam or malicious content. When an IP address is
blacklisted, it may be unable to send emails or access certain online services.
This can significantly impact businesses that rely on email communication. >Reasons for Being Blacklisted
Several factors can lead to an IP address being blacklisted:
Spam Activity: If an IP address is associated with sending spam emails, it may
be flagged.
High Bounce Rates: A high rate of undeliverable emails can indicate poor email
practices.
Sudden List Growth: Rapid increases in email list size can raise suspicions of
spammy behavior.
Malicious Content: Hosting websites that distribute malware or phishing
attempts can lead to blacklisting.
How to Check if Your IP is Blacklisted
You can check if your IP address is blacklisted using various online tools. Here
are some popular options:
Tool Name Description
MXToolbox Checks against multiple blacklists.
WhatIsMyIPAddress Provides a simple interface for blacklist checks.
DNSChecker Offers advanced tools for checking IP and domain status.
Abusix Allows you to check against known blocklists.
Steps to Resolve Blacklisting Issues
Identify the Blacklist: Use the tools mentioned to find out where your IP is
listed.
Understand the Reason: Each blacklist may provide details on why your IP was
flagged.
Take Corrective Action: Address the issues that led to blacklisting, such as
improving email practices.
Request Removal: Follow the procedures outlined by the blacklist to request
delisting.
Regularly monitoring your IP address and maintaining good email practices can >help prevent blacklisting and ensure smooth online operations.
zerobounce.net dnschecker.org
From: Zax <admin@mixmin.net>snip
Newsgroups: alt.privacy.anon-server
Subject: Re: mixmin.net - staying power . . .
Date: Sun, 29 Jun 2025 16:58:37 -0000 (UTC)
Message-ID: <slrn1062s5t.v08e.admin@fleegle.mixmin.net>
Injection-Info: news.mixmin.net;
Yes, it does run pretty much on autopilot. It doesn't help that its^^^^^^^ ^^^^^^^ ^^^^^^ ^^ ^^^^ ^^^^^^^^^^^ ^^ ^^^ ^^ ^^^^^^^^^
hosting company appear to have blacklisted my own IP addresses.
From: "Billy G." <contact-5c2e-000@pugleaf.net>snip
Newsgroups: alt.free.newsservers
Subject: lux-feed1.newsdeef.eu --> 81-171-22-215.pugleaf.net
Date: Wed, 3 Sep 2025 16:34:15 +0100
Message-ID: <a271d8681ae87079945489f868351de90bd2c9ee@usenet.pugleaf.net> >Injection-Info: reader-nyc.newsdeef.eu;
The Usenet archive at 'lux-feed1.newsdeef.eu' is under heavy load.
The current single-core VPS can no longer proxy the traffic.
Rate limits are now enabled.
Please use lux-feed1 for casual reading only.
Do not download the entire archive via lux-feed1.
user: read
pass: only
or
user: usenet
pass: archive
@suckers:
Some canadian IPs are sucking hard...
Please use the new server with better latency to the archive.
81-171-22-215.pugleaf.net
From: "Billy G." <contact-5c2e-000@pugleaf.net>[end quoted excerpts]
Newsgroups: alt.free.newsservers
Subject: Re: lux-feed1.newsdeef.eu --> 81-171-22-215.pugleaf.net
Date: Wed, 3 Sep 2025 19:56:59 +0100
Message-ID: <920d5913a2929bcbc95ba8b02fca4d19031caf00@usenet.pugleaf.net> >References: <a271d8681ae87079945489f868351de90bd2c9ee@usenet.pugleaf.net>
<1099v6p$ig7$1@nnrp.usenet.blueworldhosting.com>
Injection-Info: reader-nyc.newsdeef.eu;
On 03.09.25 18:51, Jesse Rehmer wrote:
You may end up attracting a lot of people who will configure your server
in sabnzbd and STAT the ever living crap out of your server for articles
that will never exist. This happens to me from time to time. Not usually
as load intensive as a bunch of people sucking at the same time, but it
can add up depending on how efficient your history lookup works.
Yes I've dealt with that already no problem requesting message-ids is
only limited by ssd IO =) but lux-feed1 is a $3.50 vps acting as proxy
and pushed >9T in last 2 weeks. estimated this month more than double.
worked fine all the years but who thought that people actually start >downloading it all :D little cpu is burning sometimes.
new server at 81-171-22-215.pugleaf.net is dedicated
and can do 300T monthly + latency to backend is lower.
a first torrent ( 648 newsgroups @ ~800 GB ) will be ready later.
full database snapshot from https://rocksolid-us.pugleaf.net/stats
:: https://rocksolid-us.pugleaf.net/groups
Looks like it's kerplunked.
On Jan 17, 2026 at 3:26:35rC>PM CST, "60661" <none@usenet.net> wrote:
Looks like it's kerplunked.
Billy G. had some life circumstances. He may not be back. I haven't heard from
him in over a month.
On Jan 17, 2026 at 3:26:35rC>PM CST, "60661" <none@usenet.net> wrote:
Looks like it's kerplunked.
Billy G. had some life circumstances. He may not be back. I haven't
heard from him in over a month.
On Jan 17, 2026 at 3:26:35rC>PM CST, "60661" <none@usenet.net> wrote:
Looks like it's kerplunked.
Billy G. had some life circumstances. He may not be back. I haven't
heard from him in over a month.
On 20 Jan 2026, Jesse Rehmer <jesse.rehmer@blueworldhosting.com> posted
some news:10koj23$k18$1@nnrp.usenet.blueworldhosting.com:
On Jan 17, 2026 at 3:26:35rC>PM CST, "60661" <none@usenet.net> wrote:
Looks like it's kerplunked.
Billy G. had some life circumstances. He may not be back. I haven't
heard from him in over a month.
Too bad. Hope things work out for him. This project was working and had promise.
On Jan 31, 2026 at 4:22:56rC>PM CST, "7" <7@7.7> wrote:
On 20 Jan 2026, Jesse Rehmer <jesse.rehmer@blueworldhosting.com> posted some news:10koj23$k18$1@nnrp.usenet.blueworldhosting.com:
Billy G. had some life circumstances. He may not be back. I haven't
heard from him in over a month.
Too bad. Hope things work out for him. This project was working and had promise.
Me too. He was helping in a big way with my archive project and we didn't quite get to complete it.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 65 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 05:35:13 |
| Calls: | 862 |
| Files: | 1,311 |
| D/L today: |
921 files (14,318M bytes) |
| Messages: | 264,603 |