On Mon, 22 Sep 2003, Benjamin J. Weiss wrote: > > On Mon, 22 Sep 2003, Benjamin J. Weiss wrote: > > > > Hmmm, I wonder where the rpm put the spamassassin executable. Mine is in > > /usr/bin/spamassassin. See if it's there and it's in your path. > > Well, I see a /usr/bin/spamassassin binary. I'm not sure who the > MailScanner is running as, so I don't know about the path, but I did try > setting the binary path in the MailScanner.conf file:
> SpamAssassin Install Prefix = /usr/bin > > And no dice. I'm still getting the same error. I've even tried: > > SpamAssassin Install Prefix = /usr/bin/spamassassin > > Same deal. So then I tried doing a google on "SpamAssassn Install > Prefix", and found nothing. I have no idea why it doesn't work for you. I haven't touched the Prefix equates at all. Then again, I installed my last version of SpamAssassin using CPAN. However, before that I just used their rpm's. BTW, /usr/bin/spamassassin isn't a binary. It's a perl script. > > > Unless you can shed some light, I'll be going back to the old way of using > > > procmail to initiate spamassassin, rather than trying to use MailScanner > > > to do it. > > > > That works but it's slower. > > Why? If spamd is already loaded, wouldn't it be faster for MailScanner to > use spamc instead? I thought it would cut on loading time... It's faster because MailScanner is also a perl program and it makes calls directly to the SpamAssassin libraries. It bypasses the SpamAssassin application totally. -- Gerry "The lyfe so short, the craft so long to learne" Chaucer -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
