Plugin to update my sieve filter

[bilogic]

I'm very new to snappymail, but quite amazed with it so far.

1. Is possible to write a plugin to add a button next to the sender address when viewing emails?
2. I like to classify senders as Ads/News and Block
3. This then adds that address into a sieve filter which files their messages into the respective folders

[the-djmaze]

Not at the moment.
However, there's a search filters extension (written by a user) that could do some things for you.
It's not fully the same, but it might help you for now.

[bilogic]

Do you mean I can only edit the active script? Well, I would just edit a script identified by its name, it will be up to the user (me) to ensure I don't pick another script. What I meant is additional UI on snappy that leads to the modification happening.

[the-djmaze]

Say you also use Thunderbird (it's fictional, could be any other email app).
In Thunderbird you've added Sieve rules (in a Thunderbird script).
Now through SnappyMail you want to add a Sieve rule if sender address then classify as Ads/News and Block
SnappyMail finds 5 Sieve scripts:

1. USER
2. rainloop,user
3. rainloop,user.raw
4. thunderbird (active)
5. kmail

SnappyMail could add the rule to 4, but then Thunderbird might crash when it has no clue how to parse it (while it works on the Sieve server).
Instead, SnappyMail could add the rule to a new script 6 and modify 4 to include 6. If Thunderbird doesn't crash you can edit script 4 in Thunderbird, but will it save the include?
We potentially still have an issue!
Now SnappyMail add the rule to a new script 6 and include 4 and activates script 6. This is safe because Thunderbird script is untouched.

Now Sieve scripts:

1. USER
2. rainloop,user
3. rainloop,user.raw
4. thunderbird
5. kmail
6. snappy (active)

Now you open Thunderbird. Thunderbird sees that script 6 is active and not 4.
Thunderbird asks you to activate script 4 else the changes you make are not active (according to Thunderbird).
You say "yes" and now script 4 is active.
But... the rules you just added to 6 are now inactive!

If every Sieve editor in apps just supports everything, then there is no issue.

A good example of the mess is the SnappyMail Filter editor as well.
The "Simple" script is actually the old "rainloop.user" script as a simple GUI that RainLoop created.
At the bottom it has a button

to show you the real script source.
You see the mess that RainLoop requires?

So editing this script with a different email app will break it as well.
Also read #80

It would be best if every email app uses the Kolab USER script:

# USER Management Script
#
# This script includes the various active sieve scripts
# it is AUTOMATICALLY GENERATED. DO NOT EDIT MANUALLY!
# 
# For more information, see http://wiki.kolab.org/KEP:14#USER
#

require ["include"];

include :personal "rainloop.user.raw";
include :personal "kmail";

But how is it automatically generated?
Can it be updated outside kolab?
If so, any :personal script can be (de)activated

[bilogic]

I'm not familar with sieve architecture at all, but what I'm hearing you say is: sieve script is triggered only when running the email client e.g. SnappyMail/Thunderbird.

I think email clients run in 2 forms:

1. Can reside on the IMAP server with constant connection, e.g. SnappyMail
2. Resides on standalone on one of the client desktop/laptop/mobile. e.g. Thunderbird

I'm referring to 1, and I think we can exclude many of the considerations if we setup a cron job to run the sieve filters, or even better, get the IMAP server to run the sieve filter on every new mail, and this sieve filter can be modified by SnappyMail using the fixed name approach.

Is what I proposed feasible?

[the-djmaze]

No, what i mean is:

• Sieve can have 1000 scripts
• Only 1 can be active
• Many mail apps don't understand the 1000 scripts, only the one the app created
• You are screwed when using different apps

[bilogic]

Ok, let's handle 2 parts:

1. Using only SnappyMail - any problems? I think no
2. Using SnappyMail + others

• No problems if other clients don't run sieve
• If they run sieve, they cannot crash, if they crash, it's their problem

If IMAP can run sieve, then all clients do not need sieve, even better right?

And if SnappyMail can edit that sieve script, but not run it, instead let IMAP run it, then all clients don't have to run script (no crashes at all)

So my proposal:

1. Any email client can edit script
2. But script only executed by IMAP