Re: Re: Website link for 217.15.102.67

"Alexey Lobanov (dsbl)" <[email protected]>
Newsgroups gmane.mail.spam.dsbl.admin
Organization DSBL volunteer
Message-ID <[email protected]>
Hello.

On 23/09/05 09:45, Chris Z. wrote:

> I cannot fix the DNS entry, its not on my server or any server under my
> control and it will likely take days. Now be a man and remove the entry
> from your system, since your removal system does not allow me to do it.

Yes, because your system fails accountability test. You
(non-intentionally) publish false data in DNS, and this problem must be
fixed at your side.

> 
> broken DNS entries has nothing to do with spamming.

Broken DNS entries effectively prevent proper reporting of abuse evens
to host owners. It is exactly what "removalquery" checks, and it is
called "Accountability".

> But neither people
> who get infected by viruses (courtesy of MS Corp) should be blacklisted.

People are not blacklisted anyway; I hope, you are not a cyborg with
implanted network interface? In opposite, insecure and hijacked
computers (which are controlled by villains instead of legitimate
owners) - may and should be blacklisted (I believe).

> Condeming the victims, when u cannot condem the criminals...nice...

Blacklisting is not a punishment. It is a safety precaution, nothing
more: the Internet community wants to know and insulate insecure data
sources. At least, until they become secure.

Best,
Alexey
DSBL volunteer

> 
> ----- Original Message ----- From: "Dick Wesseling" <[email protected]>
> To: "chris z." <[email protected]>
> Cc: <[email protected]>
> Sent: Friday, September 23, 2005 03:07
> Subject: Re: Website link for 217.15.102.67
> 
> 
>>
>> "chris z." <[email protected]> wrote:
>>
>>> Someone has blacklisted the above IP - 217.15.102.67
>>
>>
>> If you look at the evidence at http://dsbl.org/listing?217.15.102.67
>> you will see SOCKS and HTTP proxies at unusual port addresses. A sure
>> sign of virus infection. Your computer is now owned by somebody else.
>> Has this been fixed? If not, removing yourself would be premature.
>>
>>> Can you please remove it from your system as it causes huge amount
>>> trouble due to the fact that is cannot be removed from your system as
>>> the IP is incorrectly resolved to abakus.com.mt.
>>
>>
>> The point of the DSBL removal procedure is to verify that there is an
>> abuse/postmaster for the IP that can be contacted if there is a problem.
>> Chances are that if you would have had correct reverse DNS, you would
>> have been notified of the problem before ending up in DSBL and other
>> blocklists.
>>
>>
>>> this is getting radiculous
>>
>>
>> [email protected] receives an enormous amount of spam. The trouble is that
>> DSBL cannot use its own list to filter incoming mail. For similar
>> reasons DSBL cannot use other blocklists. The only solution remaining is
>> a rigid sanity check on messages sent to this list, sorry about that.
>>
>> The recommended course of action is:
>>
>> - remove your trojan
>> - fix your broken reverse DNS
>>
>> Once this is done you can request removal.
>>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.