Spam Prevention Early Warning System

This article has multiple issues. Please help or discuss these issues on the talk page. (Learn how and when to remove these template messages) This article may need to be rewritten to comply with Wikipedia's quality standards. . The talk page may contain suggestions. (September 2018) This article relies too much on references to primary sources. Please improve this by adding secondary or tertiary sources. (September 2018) (Learn how and when to remove this template message) This article needs additional citations for verification. Please help by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources:  –  ·  ·  · scholar · JSTOR (September 2018) (Learn how and when to remove this template message) This article may rely excessively on sources too closely associated with the subject, potentially preventing the article from being verifiable and neutral. Please help by replacing them with more appropriate citations to reliable, independent, third-party sources. (September 2018) (Learn how and when to remove this template message) This article needs to be updated. The reason given is: It needs information about APEWS. Please help update this article to reflect recent events or newly available information. (December 2020) (Learn how and when to remove this template message)

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 networks' 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]

Overview[]

SPEWS itself published a large text file containing its listings, and operated a database where web users could query the reasons for a listing. Users of SPEWS could access these data via DNS for use by software for DNSBL anti-spam techniques.

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; often they did not understand that it was their provider that was listed. Sometimes, the only solution was to leave the blacklisted provider, as SPEWS was not willing to cut holes in a listing for a clean user in an otherwise dirty IP block. There was no way for either the customer or the provider to contact SPEWS, and SPEWS claimed that the listings would be removed only when the associated abuse stopped.

The SPEWS database has not been updated since August 24, 2006; dnsbl.com lists its status as dead.^[2] 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.

Process[]

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 Website made it 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 was anonymous—when these complaints were sent, they were 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 was large enough that the service provider is encouraged to take action by the complaints of its paying customers.

Criteria for listing[]

SPEWS criteria were based on "spam support"; when a network operation provided 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.

Listing data or evidence files[]

IP addresses listed in SPEWS were mentioned in "evidence files". These were plain text files, which appeared to have been edited by hand, in which those IP addresses along with the technical evidence backing the listing, were shown. The contents of those evidence files might seem rather cryptic to readers who were not intimately familiar with the technical jargon of the Internet.

Criticism of SPEWS[]

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

Contacting SPEWS[]

One common criticism is that there was 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 formerly maintained at RFC-Ignorant.^[3]

A countervailing view is that SPEWS adopted the policy as a response to vexatious litigation against, e.g. MAPS RBL. There was nothing on the SPEWS web site to indicate that they did not care about legitimate issues, just that they didn't want to deal with specious complaints from spammers.

Criticism[]

SPEWS critics claimed it blocked sites for reasons they considered unfair. They argued that an ordinary customer of an ISP should not be held responsible for the actions of other customers of that ISP.

Counter argument[]

Supporters responded that SPEWS was a list of ISPs with spam problems. The ISP was listed, not the customers. This was 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 pointed to the claim that SPEWS "blocked" email from sites as a misconception. A SPEWS listing only caused mail to be refused if the recipient of the email (or their ISP) chose to block based on the SPEWS IP list.

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

Delisting[]

According to the SPEWS FAQ, listings were removed when the spam or spam-support has stopped. Just as they did not solicit nominations for listings, the SPEWS operators did not solicit requests for delistings. There was no contact information published on the SPEWS Website. There was no spews.org mail server, and the operators of SPEWS did 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 claimed to know their identity. By the accounts of many of those regulars, SPEWS could detect automatically when such support stopped, but this was not supported by any information in the SPEWS FAQ.

See also[]

• News.admin.net-abuse.email (NANAE)

References[]

External links[]

SPEWS and APEWS websites[]

• SPEWS.org at the Library of Congress Web Archives (archived 2002-12-02) (Last good archive. Domain is now owned by another entity.)
• APEWS.org

Advice by others[]

• First Post To NANAE Newsgroup
• What to do if you are listed on APEWS (dnsbl.com)
• Listed on APEWS: what to do (and what definitely not to do!)