On Fri, May 31, 2002 at 04:37:32PM -0600, Randy Cassingham wrote:
> At 08:39 PM 5/28/2002 -0400, Michael Stenner said:
>
> >Well, if you're running Red Hat Linux, I recommend downloading and
> >installing the rpm from the spamassassin page. ...
> >You might want to spend some time reading about the wonders of package
> >management
>
> OK, I did. I got the RPM and installed it on my RH (7.1) server. And it
> failed. The error message:
>
> Can't locate Mail/SpamAssassin/NoMailAudit.pm in @INC (@INC
> contains: /usr/lib/perl5/5.6.0/i386-linux /usr/lib/perl5/5.6.0
> /usr/lib/perl5/site_perl/5.6.0/i386-linux
> /usr/lib/perl5/site_perl/5.6.0 /usr/lib/perl5/site_perl .) at
> /usr/bin/spamassassin line 89.
> BEGIN failed--compilation aborted at /usr/bin/spamassassin line 89.
>
> There is, in fact, a /usr/lib/perl5/site_perl/5.6.0 directory. But the SA
> .pm file is in /usr/lib/perl5/site_perl/5.6.1/Mail
>
> I fixed things by going into /usr/bin/spamassassin and adding
>
> eval 'exec /usr/bin/perl -S $0 ${1+"$@"}'
> if 0; # not running under some shell
>
> use lib qw(/usr/lib/perl5/site_perl/5.6.1); <---this line
>
> use Getopt::Std;
The problem there is that the rpm you got appears to have been built
for 7.2, which uses perl 5.6.1, not 5.6.0. Your solution is
adequate. Alternatively, you can download the source rpm and rebuild
it, by doing:
rpm --rebuild <source rpm>
the resulting binary rpm will appear under /usr/src/redhat/RPMS/
and it should work for you (I'm not 100% sure, though... it depends on
how the source rpm was built).
> For testing on this not-yet-in-production server, I put the following
> in /etc/procmailrc:
>
> LOGFILE=/var/log/proclog
> SHELL=/bin/sh
> LINEBUF=4096
> VERBOSE=off
> COMSAT=no
> PATH=$HOME/bin:/bin:/usr/bin:/usr/local/bin
> FORMAIL=/usr/bin/formail
>
> :0fw
> | /home/user/bin/SpamAssassin/spamassassin -P -c /home/user/bin/SpamAssassin/rules
>
>
> (I know it's better to use the spamd daemon, but this is testing, dammit!
> Besides: the docs for spamd are completely unclear on HOW to run it in the
> background, and to run it automatically when the server reboots. One thing
> at a time, I guess....)
Well, it's only better in the system load and speed senses. There are
a number of downsides, too, such as greater security concerns. If the
load is OK with you, there's no problem running it that way.
It should be easy to set up, though. You just want to enable spamd
with
chkconfig spamassassin on
service spamassassin start
and put the comparable spamc call in your procmail.
I must comment on the spamassassin path, though. I'm pretty sure
that's not where the rpm put it :) What's up with that? You edited
the global procmailrc.
> I sent a test message to a mailbox on the server; it got through,
> but there's no SA header, and no procmail entries in proclog.
>
> The server, btw, has an ensim webbapliance front end, so I copied
> the procmailrc to the /etc directory of the test site and sent
> another test message, figuring the virtual site doesn't read the
> system-wide /etc/procmailrc (though WHY that would be, I dunno).
> Result: the test message DID go through procmail -- I know this
> because the mailbox ended up hosed because of the "From" reads as
> "rom" procmail bug (*sigh*; is there a workaround for this, such as
> running the mail through formail?). So I went into the mailbox and
> looked at the message, but
I think people have talked about the procmail bug on this list. Check
the archives for the last month or so. I can't really help you on the
rest, though. I've never used spamassassin from the global procmailrc.
> there are no SA headers on the message. The procmail log entry is:
>
> /home/user/bin/SpamAssassin/spamassassin: /home/user/bin/SpamAssassin/spamassassin:
>No such file or directory
> procmail: Program failure (127) of "/home/user/bin/SpamAssassin/spamassassin"
> procmail: Rescue of unfiltered data succeeded
> Subject: Test SA 2
> Folder: /var/spool/mail/admin 1144
>
> (the spamassassin script is in /usr/bin, so I edited the procmail line to
> reflect that; a similar error generated.)
Hmmm... ok, I commented on the path earlier. Are you saying here that
you changed the path to /usr/bin/spamassassin ? What happened then?
Id dit still say it couldn't find the executable?
> I dunno what to do next. I'd REALLY like to have SA running
> server-wide; I do not want to have to install it again and again and
> again, once for each virtual site on the machine. Anyone available
> to hit me with a clue stick?
I think the bit at the end here is the best direction to follow. Only
mess with the rpm stuff later if you get things working and you want a
"tidier" system.
-Michael
--
Michael Stenner Office Phone: 919-660-2513
Duke University, Dept. of Physics [EMAIL PROTECTED]
Box 90305, Durham N.C. 27708-0305
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
