Date: Mon, 26 Jan 2004 10:25:25 -0600 From: Eric F Crist <ecrist@adtechintegrated.com> To: "Matt Emmerton" <matt@gsicomp.on.ca> Cc: freebsd-questions@freebsd.org Subject: Re: Spam Assassin? Message-ID: <200401261026.07800.ecrist@adtechintegrated.com> In-Reply-To: <000801c3e3b6$7bed5410$1200a8c0@gsicomp.on.ca> References: <200401242251.14708.ecrist@adtechintegrated.com> <200401252021.19637.ecrist@adtechintegrated.com> <000801c3e3b6$7bed5410$1200a8c0@gsicomp.on.ca>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sunday 25 January 2004 08:45 pm, Matt Emmerton wrote: > As for your "subscriber opt-out", this is easy to do. When SpamAssassin > runs, it creates a ~/.spamassassin directory in each user's homedir > account. In here there is a file called "user_prefs", which contains > per-user configuration. To disable SpamAssassin for their account, you can > just change "required_hits" to a huge value, like 1000 or something that > won't catch anything. This effectively disables SpamAssassin for their > account. (Well, all incoming mail will get filtered, so you'll still get > the performance hit. There's probably a better way for now, but this will > get you started.) You can create a CGI script that can edit this file, or > have your postmaster@ handle user requests to opt-out manually. Matt, I wasn't expectinga walk through, but I greatly appreciate it! Thanks a lot! As for the subscriber opt-out, isn't it as simple as creating a .procmailrc file in each users home directory to disable filtering, since it goes through procmail? TIA -- Eric F Crist AdTech Integrated Systems, Inc (612) 998-3588 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAFT+fzdyDbTMRQIYRAn4HAKCyuj6nP38mEJX7XwTlCJIWvIIO0QCdFsGU XdI+cw2sEuLHZe37AgiJMl0= =bb/g -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200401261026.07800.ecrist>