I was excited, then I saw the script. :) This will install many instances of SA on the system. While it will work, it just doesn't seem right. It would be better to install sitewide and then just customize the calling of SA in users local procmail file. This way you just have to copy the procmail and sendmail local config dir. Much less storage taken up!
Chris -----Original Message----- From: Johnny L. Wales [mailto:johnny@;mail.booksys.com] Sent: Wednesday, October 16, 2002 6:03 PM To: [EMAIL PROTECTED] Subject: [SAtalk] Spam Assassin Installer Hi folks! I installed SpamAssassin on my own account here at work a couple weeks ago, and saw how cool it was, and then I showed it to my boss. Then she wanted it and mentioned it to the CEO. He wanted it, too. Then I brought it up in a programmers meeting and lots of people wanted it. Still, we don't want to install it on everyone's account. Why, you ask? Well, some of our clients like to send (*coughannoyingcough*) flamboyantly flashy HTML mail. Further, missing even 1 mail from a client would be unacceptable. So, the secretaries who get the email from our clients don't get spam protection, nor do our tech support people. Some sales people, all managers, and all programmers do. Anyhoo, I wrote a little perl script that takes the name of a user and automagically installs SpamAssassin for them. It's not quite ready for primetime, but I thought I'd send in what I had and maybe get some comments on it. Take a look, lemme know what you think. Thanks! -- Johnny Wales Book Systems, Inc. ------------------------------------------------------- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
