Spam Prevention Early Warning System

From Wikipedia, the free encyclopedia

The Spam Prevention Early Warning System (SPEWS) was an anonymous service which maintained a list of IP address ranges belonging to Internet service providers (ISPs) which host spammers and show little action to prevent their abuse of other network's resources. It could be used by Internet sites, as an additional source of information about the senders of unsolicited bulk email, better known as spam.

SPEWS is no longer active. A successor, the Anonymous Postmaster Early Warning System (APEWS), appeared in January 2007.^[1]

1 Overview
2 Process
- 2.1 Criteria for listing
- 2.2 Listing data or evidence files
3 Criticism of SPEWS
4 Delisting
5 References
6 External links
- 6.1 FAQ links

[edit] Overview

SPEWS itself published a large text file containing its listings, and operated a database where users could query the reasons for a listing. Users of SPEWS could reprocess these data into formats usable by software for anti-spam techniques (e-mail).

For instance, many mail sites used the SPEWS data provided at spews.relays.osirusoft.com. All DNSBLs hosted by Osirusoft were shut down on August 27, 2003 after several weeks of denial of service attacks. A number of other mirrors existed based on the SPEWS data, which remained accessible to the public. SORBS, for example, provided a mirror of SPEWS data until early 2007.

There was a certain degree of controversy regarding SPEWS' anonymity and its methods. By remaining anonymous, the SPEWS admins presumably wanted to avoid harassment and lawsuits of the sort which have hampered other anti-spam services such as the MAPS RBL and ORBS.

Some ISP clients whose providers were listed on SPEWS took umbrage that their own IP addresses were associated with spamming, and that their mail might be blocked by users of the SPEWS data. Sometimes, the only solution was to leave the blacklisted provider, as the provider would direct the customer to complain to SPEWS, and SPEWS would only pay attention to statements made by the provider, not the customer.

The SPEWS database has not been updated since August 24, 2006; dnsbl.com lists its status as dead. Since SPEWS became inactive, the Anonymous Postmaster Early Warning System (APEWS) has taken its place, using similar listing criteria and a nearly-identical web page.

[edit] Process

This article needs additional citations for verification.
Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (March 2007)

The precise process by which SPEWS gathered data about spam sources is unknown to the public, and it is likely that its operators used multiple techniques.

SPEWS seemed to collect some information from honeypots—mail servers or single email addresses to which no legitimate mail is received. These may be dummy addresses which have never sent any email (and therefore could not have requested to be subscribed to any legitimate mailing list). They may also be placed as bait in the header of a Usenet post or on a Web page, where a spammer might discover them and choose to spam them.

The SPEWS Web site makes clear that when spam was received, the operators filed a complaint with the ISP or other site responsible for the spam source. Only if the spam continued after this complaint was the source listed. However, SPEWS is anonymous—when these complaints were sent, they are not marked as being from SPEWS, and the site was not told that ignoring the complaint would result in a listing. This had the effect of determining the ISP's response to a normal user's spam complaint, and also discouraged listwashing—continuing to spam, but with the complaining address removed from the target list.

If the spam did not stop over time, SPEWS increased the size of the address range listed through a process referred to as "escalation". This process was repeated, conceivably until the entire netblock owned by the offending service provider was listed or the block is large enough that the service provider is encouraged to take action by the complaints of its paying customers.

[edit] Criteria for listing

SPEWS criteria was based on "spam support"; That means that when a network operation provides any services to the identified spammers, the resources involved were listed. For instance, part of an ISP's network may have been listed in SPEWS for providing DNS service to a domain mentioned in a piece of e-mail spam, even if the messages weren't sent from said provider's mail servers.

[edit] Listing data or evidence files

IP addresses listed in SPEWS are mentioned in "evidence files". Those are plain text files which upon inspection appear edited by hand, where those IP addresses along with the technical evidence backing the listing, is depicted. The contents of those evidence files may seem rather cryptic to readers who are not intimately familiar with the technical jargon of the Internet.

[edit] Criticism of SPEWS

This article needs additional citations for verification.
Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (March 2007)

No one knows how many service providers use the SPEWS list to reject mail.

[edit] Contacting SPEWS

One common criticism is that there is no way to contact SPEWS. According to the SPEWS FAQ: "Q41: How does one contact SPEWS? A41: One does not..." Having no way to contact SPEWS is seen as a way for SPEWS to avoid having to deal with complaints--even if they are legitimate--and to be immune from many consequences of mistakes, bad policies, or other problems. This caused SPEWS itself to be listed on some other DNSBLs such as those maintained at rfc-ignorant.org (e.g.)!

[edit] Criticism

SPEWS critics (often those who use IPs listed in SPEWS) claim it blocks sites and does so for reasons they consider unfair. Critics argue that an ordinary customer of an ISP should not be held responsible for the actions of other customers of that ISP.

[edit] Counter argument

Supporters (often those who use SPEWS) respond that SPEWS is a list of ISPs with spam problems. It is the ISP that's listed, not the customers. This is often argued with an analogy of pizza delivery companies who will not deliver to high crime areas. It's a bad situation for someone "stuck" in a bad area, but supporters argue that this also provides encouragement for a good citizen to unstick themselves and move to an ISP without a spam problem. The bad ISP loses revenue and the good ISP gets more customers, further encouraging bad ISPs to clean up.

Supporters of SPEWS often point to the claim that SPEWS "blocks" email from sites as a misconception. A SPEWS listing only causes mail to be refused if the recipient of the email (or their ISP) chooses to block based on the SPEWS IP list.

This counter argument has been criticized on the grounds that SPEWS is spreading information in a way conducive for blocking and in the knowledge that people are using it to block. According to this criticism, SPEWS should then be considered partly responsible for any blocking that happens and can be legitimately blamed if the blocking is inappropriate. In this view, the claims that lists such as SPEWS are advisory and that SPEWS itself does not block are seen as attempts to evade responsibility for SPEWS's own actions.

[edit] Delisting

According to the SPEWS FAQ^{[dead link]}, listings are removed when the spam or spam-support has stopped. Just as they do not solicit nominations for listings, the SPEWS operators do not solicit requests for delistings. There is no contact information published on the SPEWS Web site^{[dead link]}. There is no spews.org mail server, and the operators of SPEWS do not receive email under the SPEWS name.

It is believed that the operators read certain Usenet newsgroups related to spam and email abuse. However, no poster has claimed to be a SPEWS operator and no regular of the newsgroups claims to know their identity. By the accounts of many of those regulars, SPEWS can detect automatically when such support stops, but this is not supported by any information in the SPEWS FAQ.