On 11/18/10 9:40 AM, "Sharma, Ashish" <[email protected]> wrote:
> Hi,
>
> I have a default installation of 'amavisd-new' and with it an old SpamAssassin
> installation version 3.2.5.
>
> Now I have compiled Spamassassin version 3.3.1 from source and installed it at
> a custom location.
That's seldom a good idea. Mixing packaged and non-packaged software tends
to cause problems.
>
> How can I load my compiled Spamassassin 3.3.1 to the original 'amavisd-new' so
> that it skips the old version and takes the new version
You could modify @INC so that your custom path is ahead of the standard
path. See perldoc -q @INC for suggestions on how to manipulate @INC.
Alternatively, remove the packaged version, and make certain that the custom
version is in @INC.
Or better yet, upgrade the packaged version. If you don't like the
available packaged version, then make a custom package; but allow the
package manager to remove the obsolete version and put all of the libraries
in the expected locations.
> The answer at:
>
>
http://serverfault.com/questions/24626/how-is-spamassasin-called-by-amavisd-ne>
w
>
> suggests that 'amavisd-new' uses SpamAssassin's perl modules directly.
>
> How to do the switching?
--
Daniel J McDonald, CCIE # 2495, CISSP # 78281
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
Please visit http://www.ijs.si/software/amavisd/ regularly
For administrativa requests please send email to rainer at openantivirus dot
org
