[Spambayes-checkins] spambayes README.txt, 1.60, 1.61 README-DEVEL.txt, 1.10, 1.11 WHAT_IS_NEW.txt, 1.20, 1.21

Mark Hammond mhammond at users.sourceforge.net
Thu Dec 4 23:45:48 EST 2003


Update of /cvsroot/spambayes/spambayes
In directory sc8-pr-cvs1:/tmp/cvs-serv32249

Modified Files:
	README.txt README-DEVEL.txt WHAT_IS_NEW.txt 
Log Message:
Merging old 1.0 branch


Index: README.txt
===================================================================
RCS file: /cvsroot/spambayes/spambayes/README.txt,v
retrieving revision 1.60
retrieving revision 1.61
diff -C2 -d -r1.60 -r1.61
*** README.txt	17 Nov 2003 21:47:47 -0000	1.60
--- README.txt	5 Dec 2003 04:45:43 -0000	1.61
***************
*** 123,127 ****
  All you need to do to configure SpamBayes is to open a web page to
  <http://localhost:8880>, click on the "Configuration" link at the top
! right, and fill in the relevant details.  Everything should be ok with the
  defaults, except for the POP3 and SMTP server information at the top, which
  is required.  Note that *nix users may not have permission to bind ports
--- 123,127 ----
  All you need to do to configure SpamBayes is to open a web page to
  <http://localhost:8880>, click on the "Configuration" link at the top
! right, and fill in the relevant details.  Everything should be OK with the
  defaults, except for the POP3 and SMTP server information at the top, which
  is required.  Note that *nix users may not have permission to bind ports
***************
*** 146,150 ****
  To configure SpamBayes, run "sb_imapfilter.py -b", which should open a web
  page to <http://localhost:8880>, click on the "Configuration" link at the
! top right, and fill in the relevant details.  Everything should be ok with
  the defaults, except for the server information at the top.
  
--- 146,150 ----
  To configure SpamBayes, run "sb_imapfilter.py -b", which should open a web
  page to <http://localhost:8880>, click on the "Configuration" link at the
! top right, and fill in the relevant details.  Everything should be OK with
  the defaults, except for the server information at the top.
  
***************
*** 186,190 ****
  
  (Replace the latter with the location of the .hammiedb file that
! sb_filter created in the first step).
  
  Once you've trained SpamBayes on your
--- 186,190 ----
  
  (Replace the latter with the location of the .hammiedb file that
! sb_filter.py created in the first step).
  
  Once you've trained SpamBayes on your
***************
*** 203,210 ****
  will still complain if you don't specify a lock file.)
  
! The result of running sb_filter.py in filter mode is that Procmail will use the
! output from the run as the mail message for further processing downstream.
! sb_filter.py inserts an X-SpamBayes-Classification header in the output message
! which looks like:
  
      X-SpamBayes-Classification: ham; 0.00; '*H*': 1.00; '*S*': 0.00; 'python': 0.00;
--- 203,210 ----
  will still complain if you don't specify a lock file.)
  
! The result of running sb_filter.py in filter mode is that Procmail will
! use the output from the run as the mail message for further processing
! downstream. sb_filter.py inserts an X-SpamBayes-Classification header in
! the output message which looks like:
  
      X-SpamBayes-Classification: ham; 0.00; '*H*': 1.00; '*S*': 0.00; 'python': 0.00;
***************
*** 267,274 ****
  same number of spams as hams.
  
! You can train it on lots of messages in one go by either using the Hammie
! script as explained in the "Command-line training" section, or by giving
! messages to the web interface via the "Train" form on the Home page.  You
! can train on individual messages (which is tedious) or using mbox files.
  
  
--- 267,275 ----
  same number of spams as hams.
  
! You can train it on lots of messages in one go by either using the
! sb_filter.py script as explained in the "Command-line training" section,
! or by giving messages to the web interface via the "Train" form on the
! Home page. You can train on individual messages (which is tedious) or
! using mbox files.
  
  
***************
*** 385,389 ****
     contain the word Viagra"?), find particular messages, and most
     importantly, train it on the emails you've received.  When you start
!    using the system, unless you train it using the Hammie script it will
     classify most things as Unsure, and often make mistakes.  But it keeps
     copies of all the email's its seen, and through the web interface you
--- 386,390 ----
     contain the word Viagra"?), find particular messages, and most
     importantly, train it on the emails you've received.  When you start
!    using the system, unless you train it using the sb_filter script it will
     classify most things as Unsure, and often make mistakes.  But it keeps
     copies of all the email's its seen, and through the web interface you
***************
*** 402,411 ****
     easy to file all the suspected spam into its own folder, for instance.
  
!  o The Hammie script.  This does three jobs: command-line training,
     procmail filtering, and XML-RPC.  See below for details of how to use
!    Hammie for training, and how to use it as procmail filter.  Hammie can
!    also run as an XML-RPC server, so that a programmer can write code that
     uses a remote server to classify emails programmatically - see
!    hammiesrv.py.
  
   o The IMAP filter.  This is a cross between the POP3 proxy and the Outlook
--- 403,412 ----
     easy to file all the suspected spam into its own folder, for instance.
  
!  o The sb_filter.py script.  This does three jobs: command-line training,
     procmail filtering, and XML-RPC.  See below for details of how to use
!    sb_filter for training, and how to use it as procmail filter. You  can
!    also run an XML-RPC server, so that a programmer can write code that
     uses a remote server to classify emails programmatically - see
!    sb_xmlrpcserver.py.
  
   o The IMAP filter.  This is a cross between the POP3 proxy and the Outlook

Index: README-DEVEL.txt
===================================================================
RCS file: /cvsroot/spambayes/spambayes/README-DEVEL.txt,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** README-DEVEL.txt	5 Nov 2003 12:50:13 -0000	1.10
--- README-DEVEL.txt	5 Dec 2003 04:45:44 -0000	1.11
***************
*** 77,80 ****
--- 77,86 ----
  following section refers to old application names.
  
+ IMPORTANT NOTE
+ ==============
+ 
+ The applications have all been renamed in preparation for 1.0 - the
+ following section refers to old application names.
+ 
  Apps
  ====
***************
*** 246,250 ****
      currently asking for.  The idea is, if you have a standard directory
      structure (below), you can run this thing, go have some tea while it
!     works, then paste the output to the spambayes list for good karma.
  
  
--- 252,256 ----
      currently asking for.  The idea is, if you have a standard directory
      structure (below), you can run this thing, go have some tea while it
!     works, then paste the output to the SpamBayes list for good karma.
  
  
***************
*** 507,518 ****
  Anthony's Alternate Approach to Building the Zipfile
  
! o Unpack the tarball somewhere, making a spambayes-1.0a7 directory
!   (version number will obviously change in future releases)
! o Run the following two commands:
  
!     find spambayes-1.0a7 -type f -name '*.txt' | xargs zip -l sb107.zip 
!     find spambayes-1.0a7 -type f \! -name '*.txt' | xargs zip sb107.zip 
  
! o This makes a tarball where the .txt files are mangled, but everything
!   else is left alone.
  
--- 513,524 ----
  Anthony's Alternate Approach to Building the Zipfile
  
!  o Unpack the tarball somewhere, making a spambayes-1.0a7 directory
!    (version number will obviously change in future releases)
!  o Run the following two commands:
  
!      find spambayes-1.0a7 -type f -name '*.txt' | xargs zip -l sb107.zip 
!      find spambayes-1.0a7 -type f \! -name '*.txt' | xargs zip sb107.zip 
  
!  o This makes a tarball where the .txt files are mangled, but everything
!    else is left alone.
  

Index: WHAT_IS_NEW.txt
===================================================================
RCS file: /cvsroot/spambayes/spambayes/WHAT_IS_NEW.txt,v
retrieving revision 1.20
retrieving revision 1.21
diff -C2 -d -r1.20 -r1.21
*** WHAT_IS_NEW.txt	5 Nov 2003 12:50:13 -0000	1.20
--- WHAT_IS_NEW.txt	5 Dec 2003 04:45:44 -0000	1.21
***************
*** 10,14 ****
  noted in the "Transition" section.
  
! New in Alpha Release 6
  ======================
  
--- 10,14 ----
  noted in the "Transition" section.
  
! New in Alpha Release 7
  ======================
  
***************
*** 17,22 ****
  --------------------------
  
! There are two major changes in this release, which *will* effect you if you
! are upgrading from an older version:
  
   o The scripts have all moved (in the archive), and their names have been
--- 17,33 ----
  --------------------------
  
!  o If you are using a pickle for storage, your 'message info' database
!    would previously still have been a dbm (where available).  This is
!    no longer the case - if you are using a pickle for the statistics
!    database, you have a pickle for everything.  Your old 'message info'
!    database is not converted (and there is no utility provided to do so).
!    If you are using a pickle for storage, you should delete your old
!    'spambayes.messageinfo.db' file before restarting after the upgrade.
!    You should not suffer any ill effects from this, *unless* you are
!    using sb_imapfilter.py.  In that case, you will find that the filter
!    trains and classifies all messages in the folders it examines, even
!    if it has seen them before - this will only occur once, however.
! 
! There should be no other incompatible changes (from 1.0a6) in this release.
  
   o The scripts have all moved (in the archive), and their names have been
***************
*** 74,106 ****
  POP3 Proxy / SMTP Proxy
  -----------------------
!  o If running Windows, and have the win32 extensions installed, and a
!    configuration file cannot be found, then default to placing it in the
!    "Application Data" directory (as defined by Windows).  Also default to
!    storing the caches and databases in this directory.
!  o Correctly save and close the database when changing options.  This
!    fixes a bug for those using gdbm databases.
  
  Web Interface
  -------------
!  o Place a threshold on the number of items displayed per section in the
!    review page.
!  o Correctly display the proxy data when it is specified on the command
!    line.
  
  POP3 Proxy Service / POP3 Proxy Tray Application
  ------------------------------------------------
  
!  o The POP3 proxy tray application (for Windows users), which quietly
!    appeared in the 1.0a5 release, should be ready for use.  If you have
!    the service installed, it will attempt to use that; if you do not,
!    it will start up sb_server for you.
!    ** Note that the tray application currently only works with Windows
!    NT, Windows 2000 and Windows XP, not Windows 95, 98, or ME.  This
!    will be remedied in a future version, and in the binary release of
!    the tray application. **
!  o As the service starts, it reports the username and configuration file
!    that it is using.
!  o Added a version check option to the tray application.
!  o Improved logged for both the service and the tray application.
  
  IMAP Filter
--- 85,103 ----
  POP3 Proxy / SMTP Proxy
  -----------------------
!  o An error where a failure message would be printed by
!    the SMTP proxy, even on success, was fixed.
  
  Web Interface
  -------------
!  o The bug which caused the "TypeError" when trying to access
!    the database after setting a configuration option via the
!    interface has been fixed.
  
  POP3 Proxy Service / POP3 Proxy Tray Application
  ------------------------------------------------
  
!  o Both the pop3proxy_service.py and pop3proxy_tray.py
!    scripts are now installed (with "setup.py install") if
!    the user is using Windows.
  
  IMAP Filter
***************
*** 117,137 ****
  General
  -------
!  o Add a new file: NEWTRICKS.TXT to record ideas that have and haven't
!    been tried.  If you would like to add to this, please submit a patch
!    via the Sourceforge system.
!  o Change the default to tokenizer the "To", "CC", "Reply-To", "Sender",
!    and "From" address headers, rather than just "From".
!  o Fix the database opening code so that hammie* again works with both
!    dbm and pickles.
!  o Minor performance boosts to hammiebulk and mboxtrain.
! 
! Developer
! ---------
!  o Add a close method to the various storage classes.
!  o Removed the gary_combining option and code.
  
  Transition
  ==========
! If you are transitioning from a version older than 1.0a5, please also
  read the notes in the previous release notes (accessible from
  <http://sourceforge.net/project/showfiles.php?group_id=61702>).
--- 114,137 ----
  General
  -------
!  o Various improvements have been made to the management of the
!    'message info' database.  As outlined above, it will now be
!    stored as a pickle, if your statistics database uses a pickle.
!    In addition, we attempt to close the database when we should,
!    and make sure that we explicitly update it.  This should hopefully
!    go some way to solving the "DB_RUN_RECOVERY" errors that have
!    been regularly reported - we would be interested to hear from
!    you if upgrading to 1.0a7 does appear to solve this problem
!    for you (email spambayes at python.org).
!  o We now try to determine the type of dbm storage used from the
!    file, if one already exists.  This should make the transition
!    between formats a little easier.
!  o Fix sb_xmlrpcserver to work with the renamed (since 1.0a5)
!    scripts.
!  o Fix the sense of include_trained in sb_mboxtrain.
!    
  
  Transition
  ==========
! If you are transitioning from a version older than 1.0a6, please also
  read the notes in the previous release notes (accessible from
  <http://sourceforge.net/project/showfiles.php?group_id=61702>).
***************
*** 144,149 ****
  ===================
  The following bugs tracked via the Sourceforge system were fixed:
! 803501, 802545, 802347, 801952, 798362, 800555, 806632, 795145, 806238, 
! 805351
  
  A URL containing the details of these bugs can be made by appending the
--- 144,148 ----
  ===================
  The following bugs tracked via the Sourceforge system were fixed:
! 809769, 814322, 816400, 810342, 818552
  
  A URL containing the details of these bugs can be made by appending the





More information about the Spambayes-checkins mailing list