We have our wrapper script (replacement hook in qmail) check to see if a trigger file/marker exists on the user's account. If not, it gets passed through without ever touching SA. Otherwise, depending on which marker was found, different behavior can occur.
-- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 > -----Original Message----- > From: Chuck Wolber [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, May 01, 2002 11:31 AM > To: Henry Kwan > Cc: [EMAIL PROTECTED] > Subject: Re: [SAtalk] Selective site-wide usage? > > > > > > Just recently found out about SA and have spent a little > time playing > > with it and of course, had some questions. > > > > We have a low-volume mail server (P3-733/256MB, > RH7.0/sendmail) and I > > wanted to install SA as a selective site-wide option. So > the folks that > > would want to run it need to opt-in. Is there an easy way > to do this? > > At our site, we just mark the spam with a ***SPAM*** in the > subject line > and let the end users decide what to do with them. Many of > their e-mail > clients can auto filter based on this being in the subject line. I > instruct them to go through their SPAM folder once per week > to make sure > nothing legit made it in there. > > I've seen talk of a de-spamassassin procmail recipe. I'd like > to implement > that when it's figured out. > > -Chuck > > > > -- > Chuck Wolber > System Administrator > AltaServ Corporation > (425)576-1202 > ten.vresatla@wkcuhc "Condense facts from the vapor of nuance." > > >
