[Spambayes-checkins] spambayes README-DEVEL.txt, 1.9,
1.10 README.txt, 1.57, 1.58 WHAT_IS_NEW.txt, 1.19, 1.20
Anthony Baxter
anthonybaxter at users.sourceforge.net
Wed Nov 5 07:50:15 EST 2003
Update of /cvsroot/spambayes/spambayes
In directory sc8-pr-cvs1:/tmp/cvs-serv3171
Modified Files:
README-DEVEL.txt README.txt WHAT_IS_NEW.txt
Log Message:
ported changes from branch to trunk - mostly speling fixes.
Index: README-DEVEL.txt
===================================================================
RCS file: /cvsroot/spambayes/spambayes/README-DEVEL.txt,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -d -r1.9 -r1.10
*** README-DEVEL.txt 30 Oct 2003 00:07:04 -0000 1.9
--- README-DEVEL.txt 5 Nov 2003 12:50:13 -0000 1.10
***************
*** 25,29 ****
The code in this project requires Python 2.2 (or later).
! You should definately check out the FAQ:
http://spambayes.org/faq.html
--- 25,29 ----
The code in this project requires Python 2.2 (or later).
! You should definitely check out the FAQ:
http://spambayes.org/faq.html
***************
*** 71,74 ****
--- 71,79 ----
A collection of statistics functions.
+ IMPORTANT NOTE
+ ==============
+
+ The applications have all been renamed in preparation for 1.0 - the
+ following section refers to old application names.
Apps
***************
*** 79,83 ****
hammiefilter.py
A simpler hammie front-end that doesn't print anything. Useful for
! procmail filering and scoring from your MUA.
mboxtrain.py
--- 84,88 ----
hammiefilter.py
A simpler hammie front-end that doesn't print anything. Useful for
! procmail filtering and scoring from your MUA.
mboxtrain.py
***************
*** 92,96 ****
pop3proxy.py
! A spam-classifying POP3 proxy. It adds a spam-judgement header to
each mail as it's retrieved, so you can use your email client's
filters to deal with them without needing to fiddle with your email
--- 97,101 ----
pop3proxy.py
! A spam-classifying POP3 proxy. It adds a spam-judgment header to
each mail as it's retrieved, so you can use your email client's
filters to deal with them without needing to fiddle with your email
***************
*** 237,241 ****
runtest.sh
! A bourne shell script (for Unix) which will run some test or other.
I (Neale) will try to keep this updated to test whatever Tim is
currently asking for. The idea is, if you have a standard directory
--- 242,246 ----
runtest.sh
! A Bourne shell script (for Unix) which will run some test or other.
I (Neale) will try to keep this updated to test whatever Tim is
currently asking for. The idea is, if you have a standard directory
***************
*** 314,318 ****
arguments to allow using only a random subset of messages in each Set.
! CAUTION: The parititioning of your corpora across directories should
be random. If it isn't, bias creeps in to the test results. This is
usually screamingly obvious under the NxN grid method (rates vary by a
--- 319,323 ----
arguments to allow using only a random subset of messages in each Set.
! CAUTION: The partitioning of your corpora across directories should
be random. If it isn't, bias creeps in to the test results. This is
usually screamingly obvious under the NxN grid method (rates vary by a
***************
*** 462,465 ****
--- 467,473 ----
8-)
+ Anthony would rather eat live worms than trying to get a sane environment
+ on Windows, so his approach to building the zip file is at the end.
+
o If any new file types have been added since last time (eg. 1.0a5 went
out without the Windows .rc and .h files) then add them to MANIFEST.in.
***************
*** 480,484 ****
(a Debian VMWare box in my case).
o If you can, rename these with "rc" at the end, and make them available
! to the spambayes-dev crowd as release candidates. If all is ok, then
fix the names (or redo this) and keep going.
o Dance the SourceForge release dance:
--- 488,492 ----
(a Debian VMWare box in my case).
o If you can, rename these with "rc" at the end, and make them available
! to the spambayes-dev crowd as release candidates. If all is OK, then
fix the names (or redo this) and keep going.
o Dance the SourceForge release dance:
***************
*** 496,497 ****
--- 504,518 ----
Then announce the release on the mailing lists and watch the bug reports
roll in. 8-)
+
+ 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: README.txt
===================================================================
RCS file: /cvsroot/spambayes/spambayes/README.txt,v
retrieving revision 1.57
retrieving revision 1.58
diff -C2 -d -r1.57 -r1.58
*** README.txt 3 Oct 2003 05:23:15 -0000 1.57
--- README.txt 5 Nov 2003 12:50:13 -0000 1.58
***************
*** 26,30 ****
If you have any questions that this document does not answer, you should
! definately try the SpamBayes website <http://spambayes.org>, and in
particular, try reading the list of frequently asked questions:
<http://spambayes.org/faq.html>
--- 26,30 ----
If you have any questions that this document does not answer, you should
! definitely try the SpamBayes website <http://spambayes.org>, and in
particular, try reading the list of frequently asked questions:
<http://spambayes.org/faq.html>
***************
*** 36,40 ****
You need to have Python 2.2 or later (2.3 is recommended). You can
download Python from <http://www.python.org/download/>.
! Many distributions of unix now ship with Python - try typing 'python'
at a shell prompt.
--- 36,40 ----
You need to have Python 2.2 or later (2.3 is recommended). You can
download Python from <http://www.python.org/download/>.
! Many distributions of UNIX now ship with Python - try typing 'python'
at a shell prompt.
***************
*** 198,202 ****
Since no command line arguments are given, it relies on the options file
specified by the BAYESCUSTOMIZE variable for all parameters. While
! sb_filter.py is runnning, Procmail uses the lock file hamlock to prevent
multiple invocations from stepping on each others' toes. (It's not strictly
necessary in this case since no files on-disk are modified, but Procmail
--- 198,202 ----
Since no command line arguments are given, it relies on the options file
specified by the BAYESCUSTOMIZE variable for all parameters. While
! sb_filter.py is running, Procmail uses the lock file hamlock to prevent
multiple invocations from stepping on each others' toes. (It's not strictly
necessary in this case since no files on-disk are modified, but Procmail
***************
*** 292,296 ****
sb_mboxtrain.py -g ~/tmp/newham -s ~/tmp/newspam
! The above command is command-line-centric (eg. unix, or Windows command
prompt). You can also use the web interface for training as detailed above.
--- 292,296 ----
sb_mboxtrain.py -g ~/tmp/newham -s ~/tmp/newspam
! The above command is command-line-centric (eg. UNIX, or Windows command
prompt). You can also use the web interface for training as detailed above.
***************
*** 312,319 ****
below. By default it lives in a file called "hammie.db".
! o The tokeniser/classifier. This is the core engine of the system. The
tokenizer splits emails into tokens (words, roughly speaking), and the
classifier looks at those tokens to determine whether the message looks
! like spam or not. You don't use the tokeniser/classifier directly -
it powers the other parts of the system.
--- 312,319 ----
below. By default it lives in a file called "hammie.db".
! o The tokenizer/classifier. This is the core engine of the system. The
tokenizer splits emails into tokens (words, roughly speaking), and the
classifier looks at those tokens to determine whether the message looks
! like spam or not. You don't use the tokenizer/classifier directly -
it powers the other parts of the system.
***************
*** 329,333 ****
+-----------------+ +-------------+
! The POP3 server runs either at your ISP for internet mail, or somewhere
on your internal network for corporate mail. The POP3 proxy sits in the
middle and adds the classification header as you retrieve your email:
--- 329,333 ----
+-----------------+ +-------------+
! The POP3 server runs either at your ISP for Internet mail, or somewhere
on your internal network for corporate mail. The POP3 proxy sits in the
middle and adds the classification header as you retrieve your email:
***************
*** 360,364 ****
+-----------------+ +-------------+
! The SMTP server runs either at your ISP for internet mail, or somewhere
on your internal network for corporate mail. The SMTP proxy sits in the
middle and checks for mail to train on as you send your email:
--- 360,364 ----
+-----------------+ +-------------+
! The SMTP server runs either at your ISP for Internet mail, or somewhere
on your internal network for corporate mail. The SMTP proxy sits in the
middle and checks for mail to train on as you send your email:
Index: WHAT_IS_NEW.txt
===================================================================
RCS file: /cvsroot/spambayes/spambayes/WHAT_IS_NEW.txt,v
retrieving revision 1.19
retrieving revision 1.20
diff -C2 -d -r1.19 -r1.20
*** WHAT_IS_NEW.txt 19 Sep 2003 03:45:10 -0000 1.19
--- WHAT_IS_NEW.txt 5 Nov 2003 12:50:13 -0000 1.20
***************
*** 24,28 ****
ones for you, which we recommend. In the archive, the scripts are all
in a 'scripts' directory, and all the scripts start with the "sb_"
! prefix, to avoid clashing with similiarly named scripts from other
packages. Some name changes go further - "pop3proxy" is now named
"sb_server", "hammiefilter" is now named "sb_filter", "hammiecli" is now
--- 24,28 ----
ones for you, which we recommend. In the archive, the scripts are all
in a 'scripts' directory, and all the scripts start with the "sb_"
! prefix, to avoid clashing with similarly named scripts from other
packages. Some name changes go further - "pop3proxy" is now named
"sb_server", "hammiefilter" is now named "sb_filter", "hammiecli" is now
***************
*** 59,63 ****
Note that pop3proxy (sb_server) and imapfilter users can simply use the web
interface to check their options and correct any that are wrong. All
! incorrectlly named options in the configuration file will be removed.
Outlook Plugin
--- 59,63 ----
Note that pop3proxy (sb_server) and imapfilter users can simply use the web
interface to check their options and correct any that are wrong. All
! incorrectly named options in the configuration file will be removed.
Outlook Plugin
***************
*** 111,115 ****
last folder.
o Handle a folder name as a literal when presenting a list to choose from.
! o Handle imap servers that do not pass a blank result line for an empty
search.
o Fix IMAP over SSL.
--- 111,115 ----
last folder.
o Handle a folder name as a literal when presenting a list to choose from.
! o Handle IMAP servers that do not pass a blank result line for an empty
search.
o Fix IMAP over SSL.
***************
*** 147,152 ****
805351
! A url containing the details of these bugs can be made by appending the
! bug number to this url:
http://sourceforge.net/tracker/index.php?func=detail&group_id=61702&atid=498103&aid=
--- 147,152 ----
805351
! A URL containing the details of these bugs can be made by appending the
! bug number to this URL:
http://sourceforge.net/tracker/index.php?func=detail&group_id=61702&atid=498103&aid=
More information about the Spambayes-checkins
mailing list