On Fri, 2 Feb 2007, Justin Mason wrote: > > I don't believe you can install SpamAssassin successfully in your home > > directory. It would be a huge hack job to set up and maintain, and > > certainly against your ISP's policy. > > Actually, it's quite easy to install in your home dir; you install > perl into ~/perl , and then install SpamAssassin and the other perl > modules using that perl and they'll all "make install" into ~/perl > too. I've done this a few times.
Actually, it's probably even simpler than that. SA is already installed. All he needs to do is set up a personal config and yes the local delivery agent (e.g. procmail) to run his messages through something like: spamassassin --siteconfigpath=$HOME/my_spamassassin/ This will leverage all the default rules plus any personal ones he wants to add. Unfortunately, this doesn't include the scores of the non-default rules the hosting provider has in place, processess messages twice, and adds to the load on the server, so it's obviously worse than being able to add personal rules to user_prefs. -- John Hardin KA7OHZ http://www.impsec.org/~jhardin/ [EMAIL PROTECTED] FALaholic #11174 pgpk -a [EMAIL PROTECTED] key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 ----------------------------------------------------------------------- For those who are being swayed by Microsoft's whining about the GPL, consider how aggressively viral their Shared Source license is: If you've *ever* seen *any* MS code covered by the Shared Source license, you're infected for life. MS can sue you for Intellectual Property misappropriation whenever they like, so you'd better not come up with any Innovative Ideas that they want to Embrace... ----------------------------------------------------------------------- 10 days until Abraham Lincoln's and Charles Darwin's 198th Birthdays
