Tickets :: [#1139] notify action

6.0.0-beta1

7/12/25

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 (7486 days ago)
Due
Updated	10/27/2005 (7198 days ago)
Assigned	06/24/2005 (7323 days ago)
Resolved	10/27/2005 (7198 days ago)
Milestone	1.1
Patch	No

10/27/2005 08:16:57 AM	Matt Selsky	Comment #14 State ⇒ Resolved	Reply to this comment
Committed the notify stuff to Ingo 1.1. If we want to do the "denotify" action, let's open a new enhancement ticket.

10/22/2005 11:05:48 AM	Jan Schneider	Deleted Original Message

10/22/2005 11:05:40 AM	Jan Schneider	Deleted Original Message

10/22/2005 11:04:59 AM	Jan Schneider	Comment #13	Reply to this comment
Any news on this?

07/03/2005 10:25:54 AM	Jan Schneider	Comment #12	Reply to this comment
Without looking at implementation details, I would offer a freeform 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.

07/03/2005 03:12:05 AM	Matt Selsky	Comment #11	Reply to this comment
Denotify actions work mostly with "id" tags from the notify action. 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.

07/01/2005 08:09:28 AM	Jan Schneider	Comment #10	Reply to this comment
Makes sense to implement that too. As this whole sieve extension needs some configuration on the admin side, it should be configurable and turned off by default.

07/01/2005 02:01:21 AM	Matt Selsky	Comment #9 New Attachment: notify[2].diff	Reply to this comment
"denotify" cancels a previous "notify" request. See http://www.cyrusoft.com/sieve/drafts/sieve-notify-01.txt

06/24/2005 08:58:54 AM	Jan Schneider	Comment #8 State ⇒ Assigned	Reply to this comment
Re-synched with HEAD and fixed a few typos, etc. Do we also want to support denotify? Cyrus supports mailto and zephyr currently, so I What does that (denotify) do? Beside that, give credit where credit due (CHANGES).

06/24/2005 12:08:14 AM	Matt Selsky	Comment #7 State ⇒ Feedback New Attachment: notify[1].diff	Reply to this comment
Re-synched with HEAD and fixed a few typos, etc. Do we also want to support denotify? Cyrus supports mailto and zephyr currently, so I don't think we need to implement further methods.

06/23/2005 11:58:32 PM	Matt Selsky	Assigned to Matt Selsky State ⇒ Assigned

01/13/2005 05:07:02 PM	wolstena (at) sfu (dot) ca	Comment #6	Reply to this comment
Regarding servers/versions, I'm not sure exactly when it was implemented. I do know that it is implemented in the current cyrus 2.1, 2.2 and 2.3 streams.

01/13/2005 05:05:26 PM	wolstena (at) sfu (dot) ca	Comment #5	Reply to this comment
The "outcommented $data['k']" is chaffe. Initially, I was going to model notify after "forward". Then I realized this would be incorrect.

01/13/2005 09:57:09 AM	Jan Schneider	Comment #4	Reply to this comment
Do you know if all Sieve implementations support this, or only certain servers/versions?

01/13/2005 09:55:56 AM	Jan Schneider	Comment #3 State ⇒ Accepted	Reply to this comment
What's up with these outcommented $data['k'] entries in lib/Storage/prefs.php?

01/12/2005 10:20:18 PM	wolstena (at) sfu (dot) ca	Comment #2 New Attachment: notify.diff	Reply to this comment
Here's a diff on HEAD

01/12/2005 10:19:42 PM	wolstena (at) sfu (dot) ca	Comment #1 Priority ⇒ 1. Low Type ⇒ Enhancement Summary ⇒ notify action Queue ⇒ Ingo State ⇒ New	Reply to this comment
Recent versions of Cyrus Imapd support sieve notify. ICurrently, only 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).