Turn off all possible message changes for some users?

[Mike Kercher]

Sounds like he's on the right track overall.  I'd attribute that to Julian's
straightforward and "simple" wording of the MailScanner.conf entries.  A new
user can have MailScanner up and running in a matter of minutes...even with
rulesets!

Mike


> -----Original Message-----
> From: MailScanner mailing list
> [mailto:MAILSCANNER at JISCMAIL.AC.UK] On Behalf Of Antony Stone
> Sent: Tuesday, September 02, 2003 2:43 PM
> To: MAILSCANNER at JISCMAIL.AC.UK
> Subject: Re: Turn off all possible message changes for some users?
>
>
> On Tuesday 02 September 2003 8:39 pm, Furnish, Trever G wrote:
>
> > For our next phase of testing I want to have mailscanner start
> > handling all the mail for several of our high-volume, many-user
> > domains, but I only want a small subset of those users to
> actually be
> > part of the testing - email for everyone else ought to be untouched
> > (at least as far as a user is likely to notice).  What is
> the proper /
> > best way of doing that?
> >
> > So far I've turned "Virus Scanning" and "Spam Checks" into
> rulesets.
> > I've also configured the MTA (sendmail) to split messages with
> > multiple recipients into one message per recipient.  The
> rulesets look
> > like so:
> >
> > To:     testuser at testdomain.com yes
> > FromOrTo:       default no
> >
> > I also set "Scanned Modify Subject" to a similar ruleset.
> >
> > Anything else I'm missing and should turn off for non-test users
> > before I deploy?
>
> Ensure that "Non Spam Actions" says something sensible for
> the non-test users.
>
> Antony.
>
> --
>
> Windows: just another pane in the glass.
>