Re: Summary of Issues Raised to date

>
> Mark E. Mallett wrote:
> > On Tue, Mar 16, 2004 at 03:52:45PM -0500, Yakov Shafranovich wrote:
> >
> >>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.
> >
> >
> > Sorry to be picky, but I think that's redundant.  A filter can not
> > possibly command something downstream to take an action, so saying
> > that it shant do so doesn't really have any weight.  Plus, not all
> > labels are intended to represent an analysis.  Maybe simply
> note that
> > labels contain comments, some of which may represent
> conclusions that
> > can be used by downstream processors if so desired.
> >
>
> Maybe its just easier to take it out.

IMHO, it is necessary to distinguish between simple headers and data
added by email filters which may be consumed downstream.  Perhaps we
should distinguish between "classifications" and "recommendations for
action".

> Yakov
>