[Cc: ing notifications list]
On Tue, 2006-02-07 at 12:05 +0100, Michael Haardt wrote:
I suggest that allowed modifications MUST or at least SHOULD be
Usage: valid_notif_method <notification-uris: string-list>
Of course that is real easy to implement, but it is also real ugly.
There is nothing I know of else in Sieve that checks certain options
of actions for validity. I still suggest a generic extension for
I don't know about generic exception handling, but wouldn't it make more
sense, in this particular case, that the available notifications are
present in the capabilities of the Sieve server?
So, just as IMAP4 Capability responds with a set such as AUTH=DIGEST-MD5
AUTH=ANONYMOUS or THREAD=ORDEREDSUBJECT THREAD=REFERENCES, a Sieve
server could respond with "notify notifymethod=mailto
notifymethod=xmpp", or something similar.
For a client implementation that has no idea what is suppored on the
server, this would be ideal. It will also save my client implementation
from an extra configuration option. :)
Since we broke compatibility with the original draft, I repeat my
point of view to remove ":method" and change its argument to an
argument of "notify", as in:
Good idea. I think that the current plan is a bit awkward. The Cyrus
implementation uses the :options field to define the email address:
notify :method "mailto" :options "foo(_at_)example(_dot_)org"
draft-ietf-sieve-notify-xmpp on the other hand uses the :method for the
notify :method "xmpp:romeo(_at_)example(_dot_)com"
How about a 'target' option, or as you suggest, no option at all, and a
general plan to use existing URLs defined in other documents.
* mailto URI:
*XMPP URI according to draft-saintandre-xmpp-iri
* SMS URI according to
* tel: URI according to RFC3966. Could probably leave a preconfigured,
implementation-specific voice mail message:
And so on.