ANNOUNCE: Version 3.14-1 released

[Julian Field]

It's documented near the top of
http://www.sng.ecs.soton.ac.uk/mailscanner/install/conf.shtml

Basically you've got it right, but to over-ride the default "deliver"
action you'll need a line
         *.              delete
and not just
         *               delete
Sorry about that, it's just how it got implemented...

For messages with multiple recipients, deliver over-rides store, which in
turn over-rides delete. So if any of the recipients match a "deliver" rule,
the message will be delivered (to all the recipients). Failing that, if any
of the recipients match a "store" rule, the message will be stored. Failing
that, if all the recipients match "delete" rules, the message will be deleted.

At 12:26 14/05/2002, you wrote:
>Hi Julian,
>any info on the structure of the per-user and per-domain spam control file ?
>
>is it as simple as:
>
># Filename : spam.actions.conf
># Spam Control for use by mailscanner 3.14-1
>#
>mydomain.com            deliver
>user at mydomain.com               delete
>me at mydomain.com         delete
>user at anotherplace.com   store
>*                               delete
>
># end of spam.actions.conf
>
>
>or is there something else needed ?
>
>Thanks,
>Declan
>
> >
> > I've just released MailScanner Version 3.14.
> >
> > Changes for this version are:
> >
> > Features:
> >   - Implemented per-user and per-domain control of what to do with spam
> >   - Added "Subject:" line modification for viruses, same as for spam
> >   - SpamAssassin report now also includes names of successful tests
> >

--
Julian Field                Teaching Systems Manager
jkf at ecs.soton.ac.uk         Dept. of Electronics & Computer Science
Tel. 023 8059 2817          University of Southampton
                             Southampton SO17 1BJ