SpamCopWiki : SCMaterialChanges

SpamCopWikiHome :: Categories :: PageIndex :: RecentChanges :: RecentlyCommented :: Login/Register
Most recent edit on 2008-06-02 18:29:47 by WazoO

Additions:

Update: spamcop newsgroup thread at http://zeta.cesmail.net/pipermail/scspamcop/2008-January/thread.html#5660 includes the following expansion;

SpamCop does what it does and doesn't do for a reason. Do not make any material changes to spam before submitting or parsing which may cause the SpamCop parser to find a link, address or URL it normally would not, by design, find.

The SpamCop parser does not generate reports for From: or Reply To: addresses. Do not add these within the body of the spam to cause a report for these to be generated.

The SpamCop parser does not decode javascript because it does not have its own javascript interpreter. Unless you can properly decode the javascript, even what you see may not be correct. Do not make any changes to the spam to cause SpamCop to report addresses, links or URLs that are contained within the javascript, decoded or not.

It is okay to munge your personal email address contained within links in the body of the spam, if the SpamCop parser does not find and munge them, with one exception. If a report is going to an abuse desk that does not accept munged reports, you must not make even these minor changes to the spam.

Base64 Encoded Spam - Many spammers are sending messages with Base64 encoded bodies. While SpamCop normally decodes and parses Base64 fine, it is possible for spammers to hide your address or other identifiable information within the encoded body.

For this reason, SpamCop has made an exception to the normal alteration rule for those who know what they are doing:



SpamCopReporting
CategorySpamCopReporting

Valid XHTML 1.0 Transitional :: Valid CSS :: Powered by Wikka Wakka Wiki 1.1.6.2
Page was generated in 0.1174 seconds