Summary | Sieve filter updates to features |
Queue | Ingo |
Queue Version | Git master |
Type | Enhancement |
State | Resolved |
Priority | 1. Low |
Owners | slusarz (at) horde (dot) org |
Requester | ricardo (at) wenn (dot) com |
Created | 12/17/2009 (5680 days ago) |
Due | |
Updated | 04/15/2014 (4100 days ago) |
Assigned | |
Resolved | 04/14/2014 (4101 days ago) |
Milestone | |
Patch | No |
commit 770646adad052fe56f0fce8c8836abfc41c96c94
Author: Michael M Slusarz <slusarz@horde.org>
Date: Mon Apr 14 20:03:30 2014 -0600
Use server defined notification message for enotify (
Request #8784)ingo/lib/Script/Sieve/Action/Notify.php | 18 +++++++++++-------
1 files changed, 11 insertions(+), 7 deletions(-)
http://github.com/horde/horde/commit/770646adad052fe56f0fce8c8836abfc41c96c94
work. In particular the variables in the :message-tag won't work that
way.
You can find examples with working subject/from variables in the RFC
section 3.7: https://tools.ietf.org/html/rfc5435#page-6 (example 1)
Also note that the RFC recommends to include the from + subject
headers by default (section 3.6). That's why my patch just removes it.
Afaik Dovecot just includes the subject.
Assigned to Michael Slusarz
Version ⇒ Git master
State ⇒ Resolved
commit f02779988d2e0bae25286b62f0440071389837c2
Author: Michael M Slusarz <slusarz@horde.org>
Date: Mon Apr 14 17:49:34 2014 -0600
[mms] Use standardized 'enotify' sieve extension (RFC 5435) by
default instead of deprecated 'notify' extension (
Request #8784).ingo/config/backends.php | 4 ++++
ingo/docs/CHANGES | 2 ++
ingo/docs/UPGRADING | 8 ++++++--
ingo/lib/Script/Sieve.php | 6 +++++-
ingo/lib/Script/Sieve/Action/Notify.php | 26 +++++++++++++++++++-------
ingo/package.xml | 1 +
6 files changed, 37 insertions(+), 10 deletions(-)
http://github.com/horde/horde/commit/f02779988d2e0bae25286b62f0440071389837c2
commit 199448a47e4be0f41a3c36db006a59d92ec8e872
Author: Michael M Slusarz <slusarz@horde.org>
Date: Mon Apr 14 17:28:51 2014 -0600
[mms] Use standardized 'imap4flags' sieve extension (RFC 5232) by
default instead of deprecated 'imapflags' extension (
Request #8784).ingo/config/backends.php | 5 ++
ingo/docs/CHANGES | 2 +
ingo/docs/UPGRADING | 8 ++++
ingo/lib/Script/Sieve.php | 57 ++++++++++++++++++++-----
ingo/lib/Script/Sieve/Action/Flag.php | 72
+++++++++++++++++----------------
ingo/package.xml | 1 +
ingo/test/Ingo/Unit/SieveTest.php | 2 +-
7 files changed, 99 insertions(+), 48 deletions(-)
http://github.com/horde/horde/commit/199448a47e4be0f41a3c36db006a59d92ec8e872
support imap4flags as far as I know.
extension is supported for backward compatibility.
This is a heads up to mabey consider it as a toggle for servers that
do/dont support for if/when its removed.
http://tools.ietf.org/html/rfc5232
State ⇒ Feedback
extension is supported for backward compatibility.
Patch ⇒ No
State ⇒ New
Milestone ⇒
Queue ⇒ Ingo
Summary ⇒ Sieve filter updates to features
Type ⇒ Enhancement
Priority ⇒ 1. Low
imap4flags instead of imapflags.
This should mabey be a toggle option depending on what version of
software people are using.
Taken from http://wiki.dovecot.org/LDA/Sieve
Note that the CMU Sieve plugin implements an older specification of
the enotify extension which was called notify. Something similar is
true for the imap4flags extension, which was known as imapflags for
CMU Sieve. For backwards compatibility, Dovecot Sieve plugin also
supports the old imapflags extension. The most valuable extension that
the new Sieve implementation adds to the list is the variables
extension. As the name implies, this adds support for variables to the
language.