Re: Summary of Issues Raised to date

Mark E. Mallett wrote:
> On Tue, Mar 16, 2004 at 11:28:25AM -0600, David Nicol wrote:
> 
>>Yakov Shafranovich wrote:
>>
>>
>>>How about this:
>>>
>>>* Filters can choose to either take actions on a message or label the 
>>>message. If a message is labeled, then the filter should not dictate 
>>>what type of actions should be taken downstream but only provide the 
>>>information or suggest a possible action.
>>>
>>>Yakov
>>
>>"take actions" is about as vague as you can get, and labeling is itself 
>>an action.  A list of actions filters take
>>might make more sense
>>
>>   label 
>>   reject
>>   delay
>>   deliver
> 
> 
> I would agree.  Those are all potential outputs of a filter, and any
> one does not necessarily prohibit any other.  A filter can have
> multiple outputs for a given message.  Some of the actions (or
> outputs) do affect the downstream of course; others don't.
> 

How about this:

* Filters can have mutliple outputs (e.g. reject, delay, deliver, label, 
etc.). If a filter labels a message, the labeling should not dictate 
actions to be taken downstream, only suggest and/or provide information 
for such actions.

Yakov