Andy Figueroa writes: > SpamAssassin puts a heavy load on a server compared to most programs, > and letting users write their own rules can make that a lot a lot > heavier. Of course, if the ISP did a really good job of managing their > SpamAssassin, you probably wouldn't be asking. > > Hosting provider policy is all over the map.
yep :( > If you really have access to ~/.spamassassin, that's where users' custom > rules go, IF the ISP's installation uses users' ~./spamassassin folders. > If your ISP's policy is a hard and fast rule, though you risk getting > kicked off. Otherwise, you can just try it and see if it works. > > 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. Of course, most low-end hosting packages where you don't get root privs won't allow you to run long-running daemons like spamd, so it's pointless :( --j. > I agree with Wofgang. Install SpamAssassin on your desktop or setup > your own mailserver. I'm assuming you don't run Windows. > > Andy Figueroa
