Request for comments 3

[Julian Field]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, initial testing is showing it working very well. The aim is that 
you can have anything in the message (expressed as a SpamAssassin rule) 
trigger any action on the message, spam or not. So you can archive any 
message containing particular bits of text anywhere, or you can _not_ 
deliver any message with a certain bit of text in it.

Say you have all mail copied to an archive, but you want certain 
sensitive mail of your own (or your boss's) not archived, then you can 
write an SA rule for some subject keyphrase or piece of text in the body 
of the message. You can then not archive any mail matching that SA rule.

So the boss could have all his email CC'd to his secretary, except for 
personal mail containing "private" on the Subject line, or mail coming 
from his family.

The potential for this really is limited by your imagination, and I 
believe it could be used to provide very powerful setups.

Jules.

UxBoD wrote:
> Cool. Thanks Jules. Have a great HR application for it :)
> ----- Original Message -----
> From: "Julian Field" <MailScanner at ecs.soton.ac.uk>
> To: "MailScanner discussion" <mailscanner at lists.mailscanner.info>
> Sent: 23 July 2007 16:49:26 o'clock (GMT) Europe/London
> Subject: Re: Request for comments 3
>
>
> * PGP Signed by an unmatched address: 07/23/07 at 16:49:27
>
> Eventually yes. I want to get the design and code all working and 
> settled for spam first though.
>
> UxBoD wrote:
>   
>> Would this new functionality extend to MCP aswell Jules ?
>> ----- Original Message -----
>> From: "Julian Field" <MailScanner at ecs.soton.ac.uk>
>> To: "MailScanner discussion" <mailscanner at lists.mailscanner.info>
>> Sent: Monday, July 23, 2007 4:24:40 PM (GMT) Europe/London
>> Subject: Re: Request for comments 3
>>
>>
>>     
>>> Old Signed by an unmatched address: 07/23/07 at 16:24:41
>>>       
>>
>> John Wilcock wrote:
>>   
>>     
>>> Julian Field wrote:
>>>     
>>>       
>>>> How about this instead?
>>>>
>>>> SpamAssassin Rule Actions = rulename=>action, rulename=>action, ....
>>>>
>>>> the "rulename"s are the names of individual SpamAssassin rules, and 
>>>> the "action"s are list those in "Spam Actions". To specify multiple 
>>>> actions for a rule, you specify the rulename several times, with one 
>>>> action for each. Expressions with SpamAssassin rules are done with 
>>>> SpamAssassin meta-rules. If the rule hits, the action is taken.
>>>>
>>>> I'll write a few examples of meta-rules so you can see how to write 
>>>> them in spam.assassin.rules.conf or wherever they need to go. Mr 
>>>> Kettler, can you correct me on this please?
>>>>
>>>> Does this sound more useful than the previous suggestions?
>>>>       
>>>>         
>>> Sounds good, yes.
>>>
>>> Are the actions intended to *replace* the default non spam, spam or 
>>> high scoring spam actions, or are they taken in *addition* to those 
>>> actions?
>>>     
>>>       
>> In addition.
>>   
>>     
>>> IMO additional actions would be more flexible, but would need the 
>>> ability to negate an action, i.e. take a particular action by default 
>>> *unless* such-and-such rule hits.
>>>     
>>>       
>> Hmmm..... That makes life a bit more complicated. If I evaluated them 
>> after the existing rules then I should be able to do that. Good point 
>> though.
>>
>>   
>>     
>>> Non Spam Actions = deliver
>>> Spam Actions = deliver,store
>>> High Scoring Spam Actions = store
>>>
>>> SpamAssassin Rule Actions =
>>>     MY_BADSPAM_RULE=>not-store,
>>>     MY_SPECIAL_RULE=>forward theboss at domain
>>>
>>> John.
>>>
>>>     
>>>       
>> Jules
>>
>>   
>>     
>
> Jules
>
>   

Jules

- -- 
Julian Field MEng CITP
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
For all your IT requirements visit www.transtec.co.uk


-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.6.2 (Build 2014)
Charset: UTF-8

wj8DBQFGpdBxEfZZRxQVtlQRAsUFAJwJpB8Z8iBmulX0F8uRJPL/V8OTeQCgiPzM
liwZmw6DQHWnzc9oWUdQYSI=
=GyGM
-----END PGP SIGNATURE-----

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
For all your IT requirements visit www.transtec.co.uk