Summary | notify action |
Queue | Ingo |
Queue Version | HEAD |
Type | Enhancement |
State | Resolved |
Priority | 1. Low |
Owners | selsky (at) columbia (dot) edu |
Requester | wolstena (at) sfu (dot) ca |
Created | 01/12/2005 (7485 days ago) |
Due | |
Updated | 10/27/2005 (7197 days ago) |
Assigned | 06/24/2005 (7322 days ago) |
Resolved | 10/27/2005 (7197 days ago) |
Milestone | 1.1 |
Patch | No |
State ⇒ Resolved
"denotify" action, let's open a new enhancement ticket.
field for notifiy actions, prefilled with some unique id. For the
denotify action we could generate a drop down list from the existing
notify ids.
Thinking more about this, the prefilled form doesn't make much sense
because a random unique id doesn't help identifying rules in the
denotify drop down later.
Or they can look for things like priority (which we don't currently
assign). How should we assign id tags to notify actions? And then
how to we ensure the denotify looks for a valid id tag? Or do we
allow the user to specify the id tag free-form? I'll play with this
more on my Cyrus setup later this week to see how much setup is
involved on the admin's part, if any.
some configuration on the admin side, it should be configurable and
turned off by default.
New Attachment: notify[2].diff
http://www.cyrusoft.com/sieve/drafts/sieve-notify-01.txt
State ⇒ Assigned
support denotify? Cyrus supports mailto and zephyr currently, so I
Beside that, give credit where credit due (CHANGES).
State ⇒ Feedback
New Attachment: notify[1].diff
support denotify? Cyrus supports mailto and zephyr currently, so I
don't think we need to implement further methods.
State ⇒ Assigned
implemented. I do know that it is implemented in the current cyrus
2.1, 2.2 and 2.3 streams.
model notify after "forward". Then I realized this would be incorrect.
servers/versions?
State ⇒ Accepted
New Attachment: notify.diff
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ notify action
Queue ⇒ Ingo
State ⇒ New
mailto and an IM I'd never heard of have been implemented. It would be
great to see other implementations such as IM and SMS.
Notify is great when you don't necessarilly care too much about the
content but need to now when a message arrives.
Currently, Ingo has no support for sieve notify so I thought I would
implement it. The implementation provided is pretty basic. UI
enhancements would include other form elements (eg notify
implementation -- mailto, sms, im, etc. and message).