<html>
<body>
<font size=3>At 10:44 PM 10/25/2007, Matt S Trout wrote:<br>
<blockquote type=cite class=cite cite="">On Fri, Oct 26, 2007 at
01:04:54AM +0100, Matt S Trout wrote:<br>
> Reported to nabble abuse. I'll be killing the post out the archives
as<br>
> well.<br><br>
Reply:<br><br>
"Thanks for reporting this. This is a persistent spammer and he
had
<br>
faked many accounts to post. We keep deleting him and his accounts
and <br>
his IP address but he seems to have controlled many zombie
computers
<br>
(infected by his viruses). We will continue monitor him closely.
But
<br>
thanks again!"<br><br>
Came within about 20 minutes as well.<br><br>
nabble++</font></blockquote><br>
Any chance from a guy named 'Rod'? Google for nabble and you'll see
other problems also. Nabble allows people to post through nabble
into maillists that nabble is subscribed to. The email came from
nabble:<br>
Received: from isper.nabble.com ([192.168.236.156])<br>
<x-tab> </x-tab>by
kuber.nabble.com with esmtp (Exim 4.63)<br>
<x-tab> </x-tab>
(envelope-from <bounces@nabble.com>) id 1Il2U3-00048s-G3<br>
<x-tab> </x-tab>for
catalyst@lists.scsys.co.uk; Thu, 25 Oct 2007 06:10:47 -0700<br><br>
The solution is simply to not accept postings from nabble to the
list. Since they have a history of being abused, and not being able
to stop it, a read-only subscription would be required. <br>
</body>
</html>