You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by Apache Wiki <wi...@apache.org> on 2005/06/26 23:23:48 UTC

[Spamassassin Wiki] Update of "HandClassifiedCorpora" by JustinMason

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.

The following page has been changed by JustinMason:
http://wiki.apache.org/spamassassin/HandClassifiedCorpora

The comment on the change is:
does anyone have the luxury of cleaning out dups anymore? ;)

------------------------------------------------------------------------------
  Like a Bayesian learning system, SpamAssassin's GeneticAlgorithm requires a corpus of hand-classified mail.  Our guidelines are (quoting and expanding on "masses/CORPUS_POLICY"):
  
    * hand-verified as "spam" and "ham" (non-spam) piles -- *not* just classified using existing spam-classification algorithms (such as SpamAssassin itself).  Note that it's fine to use SpamAssassin to pre-filter them into the right piles, just make sure you scan the results "by hand" afterwards to verify that SpamAssassin made the correct diagnosis in each case. 
- 
-   * eliminate duplicates -- there should be one and only one copy of any single email, whether spam or ham.  (JustinMason: in my opinion, this isn't a hard and fast rule, as it can be very time-consuming.  I'd suggest just removing dups where they all arrive at the same time, in sequence.)
  
    * containing a representative mix of ham mail -- that includes commercial-sounding-but-not-spam messages, legitimate business discussions (which may include talk of "sales", "marketing", "offers", bankruptcies, mortgages, etc), or verified opt-in mail newsletters. This is a ''very'' important point! Your ham corpus should contain as much ham as is possible, as close to ALL valid emails received by everybody as is possible, with only the exceptions noted here. ("as is possible" recognizes that for privacy and confidentiality reasons some ham cannot be stored anywhere but its destination email folder.) 
  
@@ -18, +16 @@

  
  (Aside: yes, it's "corpora".  See PluralOfCorpus)
  
+ == Minor things that are nice to have ==
+ 
+   * eliminate duplicates -- there should be one and only one copy of any single email, whether spam or ham.  (JustinMason: in my opinion, this isn't a hard and fast rule, as it can be very time-consuming.  I'd suggest just removing dups where they all arrive at the same time, in sequence, if possible, but don't really worry about it too much.)
+