On 12/1/03 11:39 PM, "Graham Murray" <[EMAIL PROTECTED]> wrote:
> "Logan Harbaugh" <[EMAIL PROTECTED]> writes:
>
>> I had to locate the RPM on the RedHat disks, install the package,
>> then go back and then install the dependencies that hadn't been
>> installed in the first place. Then I had to go through the
>> documentation and see what files needed to be changed and how, make
>> those changes, and then test the result. The whole process took me a
>> little over an hour.
>
> Would it not have been a lot simpler to just done
>
> #perl -MCPAN -e shell;
> cpan> install Mail::SpamAssassin
>
> which is the 'standard' way of installing almost any Perl based
> package?
>
Just an observation here, but, he mentioned that he ran SpamAssassin 2.44
because "it was included with the RedHat Linux 9.0 distribution." Based on
that, it should have merely been a matter of clicking the checkbox next to
"SpamAssassin" in the installer (assuming he used the default GUI installer)
That being said, it was ALREADY installed by the time he was logging into
the machine. He must be saying that it took him over an hour to figure out
how to do the following:
vi ~/.procmail (and add appropriate config lines to call spamassassin or
spamc)
chkconfig spamd on
service spamd start
Granted, that first one can be tricky if you don't RTFM. i'm pretty sure
even the SpamAssassin RPM includes readme files. not sure where they are?
rpm -ql SpamAssassin is your friend
anyways, enough said... i'm pretty sure this horse is dead.
alan
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
