Problem on whitelist/blacklist rules

Julian Field MailScanner at ecs.soton.ac.uk
Thu Mar 23 14:13:36 GMT 2006


It actually doesn't matter where the "default" rule is placed, but it  
makes more logical sense to put it at the end, unless you're auto- 
generating the rulesets.

For all other rules, the order *does* matter, it's only the default  
rule that can be put anywhere.

On 23 Mar 2006, at 13:53, Steve Campbell wrote:

> Yes, that's right. Just add the sender to the blacklist file.
>
> The last line should be the default line in both files. I've seen  
> different opinions on where it can be placed, but I always thought  
> the lists were a "first find" type search-and-match, so the default  
> makes sense at the end.
>
> Steve Campbell
> campbell at cnpapers.com
> Charleston Newspapers
>
> ----- Original Message -----
> From: spart cus
> To: MailScanner discussion
> Sent: Wednesday, March 22, 2006 6:53 PM
> Subject: Re: Problem on whitelist/blacklist rules
>
>
>
> Steve Campbell <campbell at cnpapers.com> wrote:
> No, you're overlooking the blacklist part. The whitelist "no" parm  
> you used for "test" indicates that it is not whitelisted and must  
> go through the normal steps of any other email. You need to add  
> test to the blacklist to make it definitely spam.
>
> You should use your example in a circumstance where you might  
> whitelist an entire domain, but want only the "test" address "not"  
> to be whitelisted. For example:
>
> In whiteli! st file
> FromOrTo:    test at domain.com    no
> FromOrTo:    *@domain.com    yes
>
> In blacklist file
> FromOrTo:    test at domain.com    yes
>
> This would exclude the "test" address from whitelisting but  
> whitelist everyone else in that domain . The blacklist would make  
> "test" definitely spam. The "no" in the white/black list is used  
> mostly for exclusions, the "yes" is for inclusion, for the white or  
> black list file it is inside of.
>
> By removing both entries above from the whitelist and keeping the  
> blacklist rule, you would be changing the strategy only for the  
> *@domain.com , as now everyone but "test" would be required to pass  
> your rules before it is delivered. As stands above, everyone but  
> "test" automatically passes.
>
> Clear? or more confusing?
>
> Steve Campbell
> campbell at cnpapers.com
> Charleston Newspapers
>
>
> Hi Steve,
> Got some part of it. Since im getting some spam mails, i just want  
> to block certain sender. If thats the case then i would just add it  
> on the blacklil! st file. Is this correct ?
>
> In blacklist file
> FromOrTo:    test at domain.com    yes   # blacklist this sender
> FromOrTo:    default                        no   >>> ? Do i have to  
> put these on the last line of my blacklist.rules ???
>
> tia
>
>
>
> New Yahoo! Messenger with Voice. Call regular phones from your PC  
> and save big.
>
>
> -- 
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!
> -- 
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!

-- 
Julian Field
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20060323/63688c92/attachment.html


More information about the MailScanner mailing list