Hi, If you're going to do a filter plugin, I see three ways to do so:
- Implement a unique plugin that will be able to handle multiple filtering
systems (client-side, sieve, exim, etc)
- Implement multiple plugins, one for each filtering system
- Implement one general plugin with some hooks (Filter API) where each
particular plugin (client-side, sieve, etc) would use them
Just as a suggestion, I recommend to implement the simpler one (just client-side filtering plugin, as you say) and then see wich of these options is better/easier to implement and to manage. Personally, I'd prefer the thirst solution, which is extensible, clearer and faster (I suppose).
See you!! emi
2009/7/14 Andreas Wenk a.wenk@netzmeister-st-pauli.de
till schrieb:
On Tue, Jul 14, 2009 at 12:34 PM, Andreas Wenka.wenk@netzmeister-st-pauli.de wrote:
Hi,
first of all thanx for roundcube! It's awesome! I actually installed it
on our customer
server next to Squirell Mail. I wanna change to roundcube asap ;-)
Her's a question. Does anybody plan to develop a plugin for a message
filtering mechanism?
Is this possible - e.g. like in Thunderbird? Unfortunately I do not have
a starting point
how to do that ... so if anybody has a rough idea I could maybe start
with such a plugin ...
Comments are welcome.
Cheers
Andy
Glad you like RoundCube. As for filtering, we recommend sieve and there's a plugin for it:
http://trac.roundcube.net/browser/trunk/roundcubemail/plugins/managesieve
:-)
Cheers, Till
yeah it rocks!
Thanks for all the comments on this and thanks for the svn hint.
So now I have a problem because we are not using sieve. But maybe this is a kick in the ass to start using it :-)
Anyway and even if you recommend using sieve. *Would* it be possible to implement a simple filtering mechanism or is this approach too unuseful?
Cheers
Andy _______________________________________________ List info: http://lists.roundcube.net/dev/
List info: http://lists.roundcube.net/dev/