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

Re: List of issues with Sieve notifications

2005-10-19 08:42:02

On Wed, 2005-10-19 at 15:49 +0200, Michael Haardt wrote:
The user could have meant to use mailto, because he set a :from, but
then typed sms as method.  Or he could have meant sms, but typed from
by mistake.  That's the problem with overloading: You don't select
methods by name, but by signature, and if signatures don't match, you
have no idea what could have been meant.

you _do_ select the method by name.  don't try to be smart, use the
scheme the user has named.  if the user makes a typo in the scheme name,
that is no different from any other typo in a Sieve script.

Putting all possible options in the notify spec, no matter if as syntactic
elements, or as generic attribute-value pairs, solves this problem:
The method decides which options to look at and other options are ignored.
That's a rule users can understand very well.

no, that's much more confusing.  silently ignoring, say, :from, is not
helpful to the user who wonders why the sender address is wrong ("it
worked with mailto!")
-- 
Kjetil T.