This is something that should be reflected in the BCPs for mail
administrators - investigate the blacklist before you use it.
At 08:30 AM 8/11/2003, Alan Monaghan wrote:
So don't use their list. All of the block lists have problems. Some worse
than others.
If Spews did give any contact information, they would be out of business in
a week as people try to take them to court for any number of things just to
make them spend all their money and time.
The Register Article did not present any balance in the information nor did
it show that the ISP in question is a problem for everyone.
Spews is working the only way it can right now. Again, if it doesn't work
for you, don't use it.
-----Original Message-----
From: Yakov Shafranovich [mailto:research(_at_)solidmatrix(_dot_)com]
Sent: Sunday, August 10, 2003 6:00 PM
To: asrg(_at_)ietf(_dot_)org
Subject: [Asrg] 7. Best Practices - DNSBLs - Article
Here is a Register article describing a site being blacklisted by SPEWS.org
and how they are dealing with it:
http://www.theregister.co.uk/content/6/32231.html
Also see this Politech Bot post:
http://www.politechbot.com/p-05013.html
The site in question was blacklisted for using an ISP that has been known
for hosting spammers in the past. SPEWS.org does not provide contact
information nor are their operations audited by anyone.
The problem with SPEWS.org specifically and other similar initiatives, is
that they do not provide contact information and there is no way to gauge
whether their internal operations are run properly. This is a problem with
all anti-spam tools and is something that should be addressed in the BCP
area. Additionally, mail administrators should be cautious when selecting
or relying on a specific tool (this also goes into BCPs). Within the
consent framework, these are SOURCE TRACKING COMPONENTs which should be
selected carefully.
Yakov
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg