SpamCop

From Wikipedia, the free encyclopedia
Jump to: navigation, search

SpamCop is a spam reporting service, allowing recipients of unsolicited bulk email (UBE) and unsolicited commercial email (UCE) to report IP addresses found by SpamCop's analysis to be senders of the spam to the abuse reporting addresses of those IP addresses. SpamCop uses these reports to compile a list of computers sending spam called the "SpamCop Blocking List" (SCBL) or "SpamCop Blacklist."

History[edit]

SpamCop was founded by Julian Haight in 1998 as an individual effort. As the reporting service became more popular, staff were added and the SCBL became more useful. It has commonly been the target of DDoS attacks and lawsuits from organizations listed in the SCBL.

Email security company IronPort Systems announced its acquisition of SpamCop on November 24, 2003,[1] but it remained independently run by Julian Haight, a small staff and volunteer help in its forum.

IronPort agreed to become a division of Cisco Systems on January 4, 2007[2] effectively making SpamCop a Cisco service. Julian Haight left approximately two years after the Cisco acquisition.[3]

It has been seen as remarkable that SpamCop has survived for so many years,[citation needed] considering the severity of opposition other anti-spam companies have faced in the past, most notably Osirusoft and Blue Frog. SpamCop has dealt with attacks by spammers thus far by hiring services from Akamai, but is still the target of many hackers.

SpamCop views itself as an attempt to stop spam without the necessity of governmental intervention, but because it lacks the power of a government or large ISP, it may have greater difficulty dealing with spammers' expertise as well as the large "bot" networks that they control and that they used to cripple Blue Security with a massive DDoS attack.[4]

Benefits[edit]

SpamCop is effective at helping ISPs, web hosts and email providers identify accounts that are being abused and shut them down before the spammer finishes operations. SpamCop provides information from its reports to third parties who are also working to fight spam, amplifying the impact of its services beyond its own reach.

Limitations[edit]

For first-time SpamCop Reporters, the SpamCop Parsing and Reporting Service requires that the reporter manually verify that each submission is spam and that the destinations of the spam reports are correct. People who use tools to automatically report spam, who report email that is not spam, or report to the wrong people may be fined or banned. This verification requires extra time and effort. Despite these steps, reports to innocent bystanders do happen and ISPs may need to configure SpamCop to not send further reports if they don't want to see them again.

It is not clear whether reporting spam using SpamCop's reporting service actually reduces the amount of spam that the reporter receives.[citation needed] While some spammers may use SpamCop's reports for listwashing, others could retaliate. Spammers who determine the identity of the complainants can, by doing so, also verify that the email addresses are still in use. Much spam email is filtered or blocked by the SCBL, which is fed by many SpamCop Reporters reporting their spam.

See also[edit]

References[edit]

  1. ^ Press release: Ironport System Acquires SpamCop 24 November 2003, accessed 11 August 2007
  2. ^ Cisco Announces Agreement to Acquire IronPort 4 January 2007, accessed 9 October 2008
  3. ^ D'Minion, Don. "Reporting problems today? - SpamCop Discussion Forums entry 81639". Retrieved 24 July 2012. 
  4. ^ Hansell, Saul (9 November 2003). "Spammers Can Run but They Can't Hide". The New York Times. p. 1. Retrieved 28 December 2010. 

External links[edit]