That tailoring is beyond me...I did not and won't be touching any of that stuff! Thx Eric, all looks good.
-----Original Message----- From: Eric Shubert [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2008 9:50 AM To: [email protected] Subject: Re: [qmailtoaster] timeline to update spamassassin-toaster-3.2.4 Helmut Fritz wrote: > Looks good...message header: > > Received: by simscan 1.3.1 ppid: 16383, pid: 16385, t: 0.5770s > scanners: attach: 1.3.1 clamav: 0.92.1/m:45/d:5777 spam: > 3.2.4 > X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on > php4.phpwebservices.com > X-Spam-Level: * > X-Spam-Status: No, score=1.0 required=5.0 tests=RDNS_NONE autolearn=no > version=3.2.4 > > I will see if I can detail some of the error messages I get in > different scenarios in a different thread. Please do. > As far as SA goes, I got these warnings when it installed. I am > thinking no big deal, but let me know before I remove that > sandbox...in case you need files from it. There were also some > warnings about clamav - passing of argument messages... So this is > all probably just to make a clean make vs not working. > > ****first set**** > > Checking if your kit is complete... > Looks good > 'ENABLE_SSL' is not a known MakeMaker parameter name. > 'SYSCONFDIR' is not a known MakeMaker parameter name. I don't know why these messages are appearing. I saw documentation on the SA web site about them, and they seem to be working ok. I'm not inclined to track that down unless there's some other indication that warrants it. MakeMaker is somewhat of a PITA (IMHO). > ****second set**** > > Installing spamassassin-toaster-3.2.4-1.3.14 in the sandbox ... > Preparing... > ################################################## > spamassassin-toaster warning: /etc/mail/spamassassin/init.pre created > as /etc/mail/spamassassin/init.pre.rpmnew > warning: /etc/mail/spamassassin/v320.pre created as > /etc/mail/spamassassin/v320.pre.rpmnew > ################################################## > These are normal now, and unavoidable, at least without patching the Makefile.PL script considerably. This is the standard way in which rpm handles changes to configuration files. I would have expected the warnings for the local.cf and v310.pre files instead of init.pre and v320.pre. FWIW, you shouldn't change (and neither will the package) any of the .pre files. You should do all of your tailoring in the local.cf file, which will not be overwritten by an upgrade. -- -Eric 'shubes' --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
