Post by Christopher A. Lee Post by David Canzi Post by Christopher A. Lee Post by David Canzi Post by Christopher A. Lee
Some psycho is trying to cause damage by posting thousands of long,
nonsense messages via neodome.net.
Agent user can do a domain-level filter on these with...
The sender of a posting can set the part of the Mesage-ID after the
@-sign to whatever he wants it to be. I've created a filter for my
newsreader that ignores an article if the Injection-Info line contains
You use thunderbird. I use agent - which doesn't allow this as far as
I am aware.
Post by David Canzi
The sender of this flood appears to be an old familiar nuisance. Once
people start filtering out articles posted from neodome.net, he will
probably find other servers to abuse.
Can you remember whom? I'd ask Mickey who's good at this, but s/h/it
will have rendered Google groups unusable for her (boo) although on
the bright side, it's done the same for Mad Joe (hooray.
He's an old familiar nuisance from long ago in other newsgroups, not
alt.atheism. The source code for his abuseware was available for a
while on sourceforge, and I got a copy of it. A comment in the source
code claimed that the author is Gennady Kalmykov and other evidence
indicated that he lived in Ukraine.
One of the classic design mistakes in newsreaders is to limit the set
of header fields that can be used for filtering to a hard-coded list.
No matter how hard they try to make a complete list of all fields
that might be useful for filtering, people will inevitably need to
use some field that is not on the list.
Thunderbird starts with a hard-coded list but allows users to add
new fields to the list. In talk.origins, I have filters based on
X-NNTP-Posting-Host, which will probably never be in any
newsreader's hard-coded list.
(1) check for "neodome.net" in Injection-Info
(2) check for "!news.neodome.net!.POSTED!" in Path
If Agent doesn't allow either of these checks, and doesn't allow
you to add more fields, you may simply be out of luck.
Forte are still selling agent, but not maintaining it any more. A date
bug appeared a few years ago, which meant that expiring filters by
date so the killfile didn't get too big, stopped working and the
entries disappeared immediately.
A power user came up with a fix which was fairly easy to port to
earlier versions, but it required a hex edit - and many antivirus
scans reported the patched version .
Which was hardly good business practice.
I was seriously disappointed in them because I'd purchased each new
version even though I didn't need all the latest bells and whistles,
because I wanted them to stay in business and fix errors.
Forte resell Usenet access from major provider, and seem to be using
this as income.
I miss the days of Unix rn (pre Linux) when I accessed the newsgroups
via a shell account, to a provider who gave direct access to the
message files until they switched to an internal client server setup
back when ethernet was much slower than it is now, and processing
killfiles that way took forever.
I used to use trn, which is rn with threading support. At its best,
it supported the ability to kill an article and to continue killing
all of its descendants. It was useful in some newsgroups where, at
any time in any thread, somebody could post a funny story about their
cat, and the thread thereafter would be dominated by cat stories.
At the end, this capability of trn stopped working.
I've rethought my comments regarding Gennady Kalmykov. His software
capitalized the first word of a sentence, put a punctuation mark at
the end of each sentence, and formatted the text to fit within a
reasonable line length. The software being used to flood alt.atheism
doesn't do these things. Nobody tinkering with kalmykov's software
would have any reason to want to remove these capabilities. Ergo,
this is flooding software the somebody else wrote, and Kalmykov is
not the perp.
I didn't notice the flooding from netfront until somebody commented
about it. Netfront has been in my filter for a long time.
Nobody is morally required to agree with you.