ietf-mta-filters
[Top] [All Lists]

Re: List of issues with Sieve notifications

2005-10-17 11:06:25

On Mon, Oct 17, 2005 at 04:18:45PM +0100, Alexey Melnikov wrote:
Michael Haardt wrote:
Perhaps my suggestion of introducing ":from" was a bad idea and it should
be dropped along with ":priority", adding something like ":attributes",
that passes a string list of attribute-value pairs to the method,
leaving it up to the method definition or even the implementation which
attribute to process:

notify :attributes ["priority=low","from=sender(_at_)domain"] 
"mailto:0123456789(_at_)gateway";


notify :attributes ["route=immediate","from=0123456789"] "sms:0123456789" 
;


This doesn't make things better, because now we need to standardize 
attribute names.

I kind of like ":from" but it seems to me that something like
:attributes, to pass specific information to a particular notification
method, would be covered by the URI format for that method.  The
standardization of attribute names (if any) would be done at the URI
encoding level.  (If a URI has not been standardized for a specific
method, corresponding attribute names wouldn't have been, either.)

I guess an implementation would still be responsible for validating
the elements of a URI, e.g. if standard attribute names are enforced.

mm