Most recent edit on 2008-12-01 16:30:16 by DbieL [Added QuickReporting to the See Also list]
Additions:
QuickReporting
Edited on 2008-07-30 08:41:45 by DbieL [Added see also section + added some wiki links]
Additions:
SpamCop uses a combination of network queries (dns, whois) to cross-check all the information in an email header and find the email address of the administrator on the network where the email originated, also known as the InjectionPoint. It then formulates a polite request for discipline, including all the information the admin needs to track down the user responsible.
See Also
SpamCopReportingAccounts
SpamCopReportTypes
Deletions:
SpamCop uses a combination of network queries (dns, whois) to cross-check all the information in an email header and find the email address of the administrator on the network where the email originated. It then formulates a polite request for discipline, including all the information the admin needs to track down the user responsible.
Oldest known version of this page was edited on 2006-08-19 02:20:56 by DbieL []
Page view:
The SpamCop.net Reporting process
SpamCop will
parse the headers of unwanted email and (if all goes well) phrase a
complaint to the system administrator responsible for the spammer's internet access. This complaint will be addressed from a blind SpamCop.net email address, however any responses to that address will be routed to the email address you have provided with your SpamCop account. You may be presented with more than one address to send your complaint to and can select whether to send to each individual address or not.
Network administrators don't usually know that spammers are abusing their networks, nor should they be expected to. However, most administrators are interested to learn of abuse, and they will often take action against the people responsible. This is usually no more severe punishment than yanking the user's account. Some
ISPs (Internet service providers) take punishment farther - actually billing the spammers and kicking them off.
Unfortunately, it is usually too difficult to figure out who was responsible for any one email, particularly with the advanced techniques that savvy spammers use. However, the key to this puzzle is the combination of the
IP address of the sender and the time and date at which the mail was sent. These two pieces of information can lead an administrator back to the user who actually sent the mail. Both pieces of information are in your email header.
SpamCop uses a combination of network queries (dns, whois) to cross-check all the information in an email header and find the email address of the administrator on the network where the email originated. It then formulates a polite request for discipline, including all the information the admin needs to track down the user responsible.
Rules - everybody read!
How can I unsend a Report?
How should I select the recipients for my spam report?
Why am I sending a Report to SpamCop? (example: abuse#isp.net@devnull.spamcop.net)
Why doesn't SpamCop make reports about "reply-to" and "from" addresses?
SpamCop E-mail Account
Errors (wondering if this part should actually be placed under
SpamCopParsing and just a link to Errors / Problems on this page?)
Why does SpamCop want to send a report to my own network administrator?
SpamCop said "No reports filed." What does it mean?
CategorySpamCopReporting