Summary | Ability to create raw sieve rules |
Queue | Ingo |
Queue Version | HEAD |
Type | Enhancement |
State | Accepted |
Priority | 2. Medium |
Owners | |
Requester | gentz (at) equinux (dot) de |
Created | 03/05/2008 (6279 days ago) |
Due | |
Updated | 04/29/2010 (5494 days ago) |
Assigned | |
Resolved | |
Milestone | |
Patch | No |
Ingo doesn't support (external rule inclusion, labels, colors, etc.,),
but if he does it externally, then Ingo will erase everything the next
time the user edits some rules using it.
So, it would be great if Ingo could:
1) leave custom changes alone.
2) allow script editing directly from the interface
if allof ( header :contains "Delivered-To" ["a@b.com","b@c.com"],
anyof(header :contains ["Subject"] "abc", header :contains ["From"]
"x@y.z")) {...}
or rules with sub-rules like
if header :contains ["to","cc","resent-to"] "c@d.com" {
if header :contains ["subject"] "abc" {
fileinto "...";
stop;
}
if header :contains ["subject"] ["def","ghi"] {
fileinto "...";
stop;
}
if ...
}
Ingo because some rules have AND and OR conditions mixed. However
we'd love to migrate smoothly to Ingo using the old rules as a raw
script.
not too hard since we already have AND and OR rule types. What sort
of rules do you have like with AND/OR?
because some rules have AND and OR conditions mixed. However we'd love
to migrate smoothly to Ingo using the old rules as a raw script.
allowing advanced users to access a sieve server that is otherwise
locked down (and only accessible via ingo).
State ⇒ Rejected
the filter scripting language. Users that can can write raw Sieve
rules can upload them on the server too.
Priority ⇒ 2. Medium
Type ⇒ Enhancement
Summary ⇒ Ability to create raw sieve rules
Queue ⇒ Ingo
State ⇒ New
accepts raw sieve syntax.
Otherwise, there is no possibility to switch current manual sieve
rules to Ingo.
Furthermore it would allow complex rules that include both AND and OR
conditions.