27
diff -urNad --exclude=CVS --exclude=.svn ./ldap/README /tmp/dpep-work.hAWYqo/spamassassin/ldap/README
28
--- ./ldap/README 2005-08-11 20:38:44.000000000 -0400
29
+++ /tmp/dpep-work.hAWYqo/spamassassin/ldap/README 2005-08-17 23:46:34.000000000 -0400
27
diff -urNad spamassassin~/README spamassassin/README
28
--- spamassassin~/README 2006-03-10 14:30:24.000000000 -0500
29
+++ spamassassin/README 2006-05-07 16:45:40.000000000 -0400
31
Distributed configuration files, with all defaults. Do not modify
32
these, as they are overwritten when you upgrade.
34
- - /etc/mail/spamassassin/*.cf:
35
+ - /etc/spamassassin/*.cf:
37
Site config files, for system admins to create, modify, and
38
add local rules and scores to. Modifications here will be
39
appended to the config loaded from the above directory.
41
- - /etc/mail/spamassassin/*.pre:
42
+ - /etc/spamassassin/*.pre:
44
Plugin control files, installed from the distribution. These are
45
used to control what plugins are loaded. Modifications here will
48
You want to modify these files if you want to load additional
49
plugins, or inhibit loading a plugin that is enabled by default.
50
- If the files exist in /etc/mail/spamassassin, they will not
51
+ If the files exist in /etc/spamassassin, they will not
52
be overwritten during future installs.
54
- /usr/share/spamassassin/user_prefs.template:
56
Distributed default user preferences. Do not modify this, as it is
57
overwritten when you upgrade.
59
- - /etc/mail/spamassassin/user_prefs.template:
60
+ - /etc/spamassassin/user_prefs.template:
62
Default user preferences, for system admins to create, modify, and
63
set defaults for users' preferences files. Takes precedence over
64
the above prefs file, if it exists.
66
Do not put system-wide settings in here; put them in a file in the
67
- "/etc/mail/spamassassin" directory ending in ".cf". This file is
68
+ "/etc/spamassassin" directory ending in ".cf". This file is
69
just a template, which will be copied to a user's home directory
72
diff -urNad spamassassin~/UPGRADE spamassassin/UPGRADE
73
--- spamassassin~/UPGRADE 2006-03-10 14:30:23.000000000 -0500
74
+++ spamassassin/UPGRADE 2006-05-07 16:45:40.000000000 -0400
76
perldoc Mail::SpamAssassin::Plugin::* (ie AWL, DCC, etc)
78
- There are now multiple files read to enable plugins in the
79
- /etc/mail/spamassassin directory; previously only one, "init.pre" was
80
+ /etc/spamassassin directory; previously only one, "init.pre" was
81
read. Now both "init.pre", "v310.pre", and any other files ending
82
in ".pre" will be read. As future releases are made, new plugins
83
will be added to new files named according to the release they're
85
- If you are using a UNIX machine with all database files on local disks,
86
and no sharing of those databases across NFS filesystems, you can use a
87
more efficient, but non-NFS-safe, locking mechanism. Do this by adding
88
- the line "lock_method flock" to the /etc/mail/spamassassin/local.cf
89
+ the line "lock_method flock" to the /etc/spamassassin/local.cf
90
file. This is strongly recommended if you're not using NFS, as it is
91
much faster than the NFS-safe locker.
93
diff -urNad spamassassin~/USAGE spamassassin/USAGE
94
--- spamassassin~/USAGE 2006-03-10 14:30:24.000000000 -0500
95
+++ spamassassin/USAGE 2006-05-07 16:45:40.000000000 -0400
97
CPU-intensive task before they can send mail to you, so we give that
98
some bonus points. However, it requires that you list what addresses
99
you expect to receive mail for, by adding 'hashcash_accept' lines to
100
- your ~/.spamassassin/user_prefs or /etc/mail/spamassassin/local.cf
101
+ your ~/.spamassassin/user_prefs or /etc/spamassassin/local.cf
102
files. See the Mail::SpamAssassin::Plugin::Hashcash manual page for
103
details on how to specify these.
105
@@ -128,14 +128,14 @@
108
- You can create your own system-wide rules files in
109
- /etc/mail/spamassassin; their filenames should end in ".cf". Multiple
110
+ /etc/spamassassin; their filenames should end in ".cf". Multiple
111
files will be read, and SpamAssassin will not overwrite these files
112
when installing a new version.
115
- You should not modify the files in /usr/share/spamassassin; these
116
will be overwritten when you upgrade. Any changes you make in
117
- files in the /etc/mail/spamassassin directory, however, will
118
+ files in the /etc/spamassassin directory, however, will
119
override these files.
122
diff -urNad spamassassin~/ldap/README spamassassin/ldap/README
123
--- spamassassin~/ldap/README 2006-03-10 14:29:49.000000000 -0500
124
+++ spamassassin/ldap/README 2006-05-07 16:45:40.000000000 -0400
31
126
database or LDAP server.
91
186
=item B<-p> I<prefs>, B<--prefspath>=I<prefs>, B<--prefs-file>=I<prefs>
93
diff -urNad --exclude=CVS --exclude=.svn ./README /tmp/dpep-work.hAWYqo/spamassassin/README
94
--- ./README 2005-08-11 20:38:58.000000000 -0400
95
+++ /tmp/dpep-work.hAWYqo/spamassassin/README 2005-08-17 23:46:34.000000000 -0400
97
Distributed configuration files, with all defaults. Do not modify
98
these, as they are overwritten when you upgrade.
100
- - /etc/mail/spamassassin/*.cf:
101
+ - /etc/spamassassin/*.cf:
103
Site config files, for system admins to create, modify, and
104
add local rules and scores to. Modifications here will be
105
appended to the config loaded from the above directory.
107
- - /etc/mail/spamassassin/*.pre:
108
+ - /etc/spamassassin/*.pre:
110
Plugin control files, installed from the distribution. These are
111
used to control what plugins are loaded. Modifications here will
114
You want to modify these files if you want to load additional
115
plugins, or inhibit loading a plugin that is enabled by default.
116
- If the files exist in /etc/mail/spamassassin, they will not
117
+ If the files exist in /etc/spamassassin, they will not
118
be overwritten during future installs.
120
- /usr/share/spamassassin/user_prefs.template:
121
@@ -102,14 +102,14 @@
122
Distributed default user preferences. Do not modify this, as it is
123
overwritten when you upgrade.
125
- - /etc/mail/spamassassin/user_prefs.template:
126
+ - /etc/spamassassin/user_prefs.template:
128
Default user preferences, for system admins to create, modify, and
129
set defaults for users' preferences files. Takes precedence over
130
the above prefs file, if it exists.
132
Do not put system-wide settings in here; put them in a file in the
133
- "/etc/mail/spamassassin" directory ending in ".cf". This file is
134
+ "/etc/spamassassin" directory ending in ".cf". This file is
135
just a template, which will be copied to a user's home directory
138
diff -urNad --exclude=CVS --exclude=.svn ./rules/30_text_fr.cf /tmp/dpep-work.hAWYqo/spamassassin/rules/30_text_fr.cf
139
--- ./rules/30_text_fr.cf 2005-08-11 20:38:50.000000000 -0400
140
+++ /tmp/dpep-work.hAWYqo/spamassassin/rules/30_text_fr.cf 2005-08-17 23:46:34.000000000 -0400
188
diff -urNad spamassassin~/rules/30_text_fr.cf spamassassin/rules/30_text_fr.cf
189
--- spamassassin~/rules/30_text_fr.cf 2006-03-10 14:30:02.000000000 -0500
190
+++ spamassassin/rules/30_text_fr.cf 2006-05-07 16:45:40.000000000 -0400
142
192
# Latest revision: 2003/11/14
193
243
=item B<-p> I<prefs>, B<--prefspath>=I<prefs>, B<--prefs-file>=I<prefs>
195
diff -urNad --exclude=CVS --exclude=.svn ./sa-update.raw /tmp/dpep-work.hAWYqo/spamassassin/sa-update.raw
196
--- ./sa-update.raw 2005-08-11 20:38:58.000000000 -0400
197
+++ /tmp/dpep-work.hAWYqo/spamassassin/sa-update.raw 2005-08-17 23:46:34.000000000 -0400
200
--updatedir path Directory to place updates, defaults to the
201
SpamAssassin site rules directory (def:
202
- /etc/mail/spamassassin)
205
--channel channel Retrieve updates from this channel
206
Use multiple times for multiple channels
210
Typically sa-update will use whatever the default site rules directory
211
-SpamAssassin uses. (usually /etc/mail/spamassassin) If the updates should be
212
+SpamAssassin uses. (usually /etc/spamassassin) If the updates should be
213
stored in another location, specify it here.
216
diff -urNad --exclude=CVS --exclude=.svn ./spamc/spamc.pod /tmp/dpep-work.hAWYqo/spamassassin/spamc/spamc.pod
217
--- ./spamc/spamc.pod 2005-08-11 20:38:54.000000000 -0400
218
+++ /tmp/dpep-work.hAWYqo/spamassassin/spamc/spamc.pod 2005-08-17 23:46:34.000000000 -0400
220
C<spamc> will attempt to load defaults as follows.
222
If the installation prefix begins with C</usr>,
223
-C</etc/mail/spamassassin/spamc.conf> will be attempted. If it begins with
224
+C</etc/spamassassin/spamc.conf> will be attempted. If it begins with
225
C</opt>, C</etc/opt/mail/spamassassin/spamc.conf> will be attempted. If those
226
don't exist, C</etc/spamc.conf> will be appended to the prefix and tried. If
227
none of those exist, no configuration file will be read by default.
228
diff -urNad --exclude=CVS --exclude=.svn ./spamd/README /tmp/dpep-work.hAWYqo/spamassassin/spamd/README
229
--- ./spamd/README 2004-10-22 21:39:19.000000000 -0400
230
+++ /tmp/dpep-work.hAWYqo/spamassassin/spamd/README 2005-08-17 23:46:34.000000000 -0400
245
diff -urNad spamassassin~/spamc/spamc.pod spamassassin/spamc/spamc.pod
246
--- spamassassin~/spamc/spamc.pod 2006-03-10 14:30:13.000000000 -0500
247
+++ spamassassin/spamc/spamc.pod 2006-05-07 16:46:23.000000000 -0400
250
If the B<-F> switch is specified, that file will be used. Otherwise,
251
C<spamc> will attempt to load spamc.conf in C<SYSCONFDIR> (default:
252
-/etc/mail/spamassassin). If that file doesn't exist, and the B<-F>
253
-switch is not specified, no configuration file will be read.
254
+/etc/spamassassin). If that file doesn't exist, and the B<-F> switch
255
+is not specified, no configuration file will be read.
259
diff -urNad spamassassin~/spamd/README spamassassin/spamd/README
260
--- spamassassin~/spamd/README 2006-03-10 14:30:23.000000000 -0500
261
+++ spamassassin/spamd/README 2006-05-07 16:45:40.000000000 -0400
231
262
@@ -105,7 +105,7 @@
232
263
If you plan to use Bayesian classification (the BAYES rules) with spamd,
233
264
you will need to either
297
328
loadplugin myTestPlugin
298
329
header MY_TEST_PLUGIN eval:check_test_plugin()
299
diff -urNad --exclude=CVS --exclude=.svn ./UPGRADE /tmp/dpep-work.hAWYqo/spamassassin/UPGRADE
300
--- ./UPGRADE 2005-08-11 20:38:58.000000000 -0400
301
+++ /tmp/dpep-work.hAWYqo/spamassassin/UPGRADE 2005-08-17 23:46:34.000000000 -0400
303
perldoc Mail::SpamAssassin::Plugin::* (ie AWL, DCC, etc)
305
- There are now multiple files read to enable plugins in the
306
- /etc/mail/spamassassin directory; previously only one, "init.pre" was
307
+ /etc/spamassassin directory; previously only one, "init.pre" was
308
read. Now both "init.pre", "v310.pre", and any other files ending
309
in ".pre" will be read. As future releases are made, new plugins
310
will be added to new files named according to the release they're
312
- If you are using a UNIX machine with all database files on local disks,
313
and no sharing of those databases across NFS filesystems, you can use a
314
more efficient, but non-NFS-safe, locking mechanism. Do this by adding
315
- the line "lock_method flock" to the /etc/mail/spamassassin/local.cf
316
+ the line "lock_method flock" to the /etc/spamassassin/local.cf
317
file. This is strongly recommended if you're not using NFS, as it is
318
much faster than the NFS-safe locker.
320
diff -urNad --exclude=CVS --exclude=.svn ./USAGE /tmp/dpep-work.hAWYqo/spamassassin/USAGE
321
--- ./USAGE 2005-08-11 20:38:58.000000000 -0400
322
+++ /tmp/dpep-work.hAWYqo/spamassassin/USAGE 2005-08-17 23:46:34.000000000 -0400
324
CPU-intensive task before they can send mail to you, so we give that
325
some bonus points. However, it requires that you list what addresses
326
you expect to receive mail for, by adding 'hashcash_accept' lines to
327
- your ~/.spamassassin/user_prefs or /etc/mail/spamassassin/local.cf
328
+ your ~/.spamassassin/user_prefs or /etc/spamassassin/local.cf
329
files. See the Mail::SpamAssassin::Plugin::Hashcash manual page for
330
details on how to specify these.
332
@@ -127,14 +127,14 @@
335
- You can create your own system-wide rules files in
336
- /etc/mail/spamassassin; their filenames should end in ".cf". Multiple
337
+ /etc/spamassassin; their filenames should end in ".cf". Multiple
338
files will be read, and SpamAssassin will not overwrite these files
339
when installing a new version.
342
- You should not modify the files in /usr/share/spamassassin; these
343
will be overwritten when you upgrade. Any changes you make in
344
- files in the /etc/mail/spamassassin directory, however, will
345
+ files in the /etc/spamassassin directory, however, will
346
override these files.