On Sat, 13 Apr 2002, Frank Kintrup wrote:

> Has anyone any idea how to complete the installation without fighting it out
> with the support of my ISP?

First I suggest getting the latest CVS version of spamassassin from
sourceforge, because it contains changes to the default rules search paths
to accomodate nonstandard installations.  However, most of the rest of
these instructions should work with 2.11 as well.

Decide what directory you'd like to install into.  Subdirectories named
bin, etc, lib, share, and man are going to be created or written into in
that directory, so choose it with care.  I'm going to write "/SAhome" to
represent that directory name in the rest of this message, but you should
always use the one you're installing into.

Edit Makefile.PL to make this change:

5c5
< my $LOCAL_RULES_DIR   = '/etc/mail/spamassassin';
---
> my $LOCAL_RULES_DIR   = '${PREFIX}/etc/mail/spamassassin';

If your ISP has an existing SA installation so e.g. /etc/spamassassin.cf
already exists, you may have to comment out the "migrate_cfs:" commands
in Makefile.PL as well (leave the target, just remove the commands).

If you have the CVS version, edit lib/Mail/SpamAssassin.pm to find the
"use Config;" line and immediately after that insert:

my %Config = %Config;
$Config{prefix} = '/SAhome';

(This copies the global perl configuration to the file scope and then
replaces the prefix path so that functions defined later will see your
prefix instead of the default one.)

(If you *don't* have the CVS version, you'll have to remember to invoke
spamassassin and/or spamd with the "-c /SAhome/share/spamassassin" option
to specify the directory where you've installed the rules.  In that case
/SAhome/etc/mail/spamassassin/local.cf will NOT be used.)

Then, run:

make PREFIX=/SAhome
make test
make PREFIX=/SAhome install

and you should be all set.


_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to