Ken Murchison wrote:
Florian G. Pflug wrote:
I've developed a patch that extends the "/vendor/cmu/cyrus-imapd/sieve"
mailbox annotation to be meaningful for a user's inbox
in addition to shared mailboxes.
For a user's inbox, the sieve-annotation specifies the name of a global
sieve script that is executed when new mail is delivery to that user
_before_ his private sieve-default-script is executed.
Why not just use the Sieve 'Include' extension to include your global
script at the top of the user's private script?
Because if I did that I'd have to patch any sieve webinterface I use
to let my users edit their filtering rules to include the necessary include.
My patch allows me to keep the spam-filtering policy seperated from any
user-defined filtering rules. I want to give my users a single-click option
for choosing between "File junk into the Junk folder", "Flag Junk" and
"Don't do anything". With my patch, I just have to change the "sieve"
annotation for the user's inbox - otherwise, I'd have to parse his sieve
script and modify the include - with the risk of somehow messing up his script.
Additionally, at least for me, my patch seemed like a natural extension of
the already existing sieve annotation for global mailboxes.
greetings, Florian Pflug
PS: I've subscribed to cyrus-devel in the meantime, so you don't need to
include my personal address in the recipient list anymore.
