Multiple SpamAssassin Rule Actions in ruleset not obeyed??

Julian Field MailScanner at ecs.soton.ac.uk
Thu Jan 22 16:40:06 GMT 2009


I never defined the behaviour you might see if you have *2* "default" 
rules in the same ruleset. I hate to think what might happen.
What you probably meant was this (all on one line)
FromOrTo: default SHSU_PHISH=>not-deliver,store-spam,forward 
postmaster at shsu.edu, JKF_ANTI_PHISH=>not-deliver,store,forward 
postmaster at shsu.edu

There should be a comma and a space better "... at shsu.edu" and "JKF_ANTI...".

On 22/1/09 14:47, Laskie, Norman wrote:
> I have the following two rules defined in spamassassin.rule.actions.rules, but it appears that when both are enabled the actions aren't obeyed.  The messages in question still get tagged with the appropriate rule, but are still delivered to the end user (in this case me) and aren't forwarded onto the postmaster account.
>
> SpamAssassin Rule Actions = %rules-dir%/spamassassin.rule.actions.rules
>
> FromOrTo:      default SHSU_PHISH=>not-deliver,store-spam,forward postmaster at shsu.edu
> FromOrTo:      default JKF_ANTI_PHISH->not-deliver,store,forward postmaster at shsu.edu
>
>
> Oh yea, I hate phishers... HAHA
>
>
> Thanks in advance,
> Norman
>    

Jules

-- 
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at Jules.FM

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
PGP public key: http://www.jules.fm/julesfm.asc


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



More information about the MailScanner mailing list