Order of spam delivery check changed?

[Julian Field]

At 11:41 10/03/2004, you wrote:
>Hmmm but isn't that annoying for those adresses you want to manually
>blacklist (to or from)?
>
>This way you have to add two rules for those addresses, one if the spam
>score is low, and a second if the mail's score is high!

You could make the 2 rules files point to the same addresses file.

Set
Spam Actions = %rules-dir%/spam.actions.rules
High Scoring Spam Actions = %rules-dir%/high.spam.actions.rules

Then in both of those 2 files add a line:
To:   /etc/MailScanner/rules/blacklist        delete

Then in /etc/MailScanner/rules/blacklist, put all the addresses you want to
blacklist, one per line. You can even nest the files to break them up if
necessary, by putting in another filename rather than an address.

So the "/etc/MailScanner/rules/blacklist" file could end up looking like
user at spam1.com
user2 at spam2.com
*@spam3.com
/etc/MailScanner/rules/blacklist.joe
sales@*

Neat huh? :-)

You can't make rules files that refer to other rules files, but you can
make rules files refer to extra "address pattern list" files to get a list
of addresses for which you want the same result. These "address pattern
list" files can include other "address pattern list" files.

>And I only wanted to blacklist it so that i'd never see any mails even if
>the score is 0!
>
>I use this feature with some e-mail adresses within our organization that
>are abused as return address by spammers. The mails coming back are spam
>but I just don't want to do anything with it, just put store in
>/dev/null
>
>Doing this with in /etc/aliases is not really an option since I am
>forwarding all scanned/checked mail 1:1 to an Exchange server and
>therefore the alias database isn't used for those domains that are
>forwarded to the exchange server.
>
>Hope this makes any sense :)
>
>
>On Wed, 10 Mar 2004, Julian Field wrote:
>
> > At 11:27 10/03/2004, you wrote:
> > >I just upgraded from an old MailScanner version.
> > >
> > >I had a
> > >Spam Actions = %rules-dir%/spam.deliver.rules
> > >
> > >rules list which included many non-existent e-mail addresses and domains
> > >and stuff with a delete action for mail that would arrive at our server
> > >but that I never wanted to see. Those mails would be instantly deleted.
> > >
> > >In the latest version of MS however it seems that *only* the highscoring
> > >spam action will apply for high scoring spam and the rule is completely
> > >ignored?
> >
> > That has only ever been the case. It either applies the normal spam actions
> > or the high scoring spam actions, not both. That was always the intention,
> > anyway!
> >
> > Has anyone else seen this problem?
> >
> > >Is there any way to first apply spam actions again and then high scoring
> > >spam actions after that?
> > >
> > >I have tons of extra spam now and I dont want to create a double list of
> > >addresses.
> > >
> > >Thanks!
> > >Remco
> >
> > --
> > Julian Field
> > www.MailScanner.info
> > MailScanner thanks transtec Computers for their support
> >
> > PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
> >

--
Julian Field
www.MailScanner.info
MailScanner thanks transtec Computers for their support

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654