On Wed, 23 Aug 2006 08:18:42 -0400, Mehmet Tolga Avcioglu mehmet@activecom.net wrote:
Martin Marques wrote:
On Mon, 21 Aug 2006, Thomas Bruederli wrote:
Let's keep RoundCube a mail CLIENT and focus on the creation of a plugin API which can be used to build all sorts of admin panels for procmail, Sieve, and whatever.
Sorry, but Mail Clients don't add procmail rules AFAIK.
He is not saying that this one should either. He is saying that there should be an API that allows for external modules/plugins to be written for whatever you want to do with. Write one to administer your LDAP or Apache for all that matters.
Let's make it clearer, for what matters.
Let's say I have a mail server to maintain, with web mail access. I add the the antivirus and antispam to the mail server.
The antivirus isn't a problem, as virus should never go through, as they are a threat to the internal security.
The antispam is different problem. Namely, different people have different notions of what is spam, so what is spam for you could or could not be spam for me. So the filtering of that spam should be managed by the end user and not the sys-admin. All the sys-admin does is add a feature to the MTA where mail get cataloged with a spam score. The end user says what's spam and what isn't.
To make this easy to install, and configure, so that the end user add's the spam filters as wanted, and per-user, not globally, you need a filter system. All MUA have it. Well all except RC.
Now put this in a system with no user account (all virtual), or even better, in a DB. Would you let them add code for a procmail execution? All your security goes down in that instant.
Maybe it's just me that isn't getting the plugin stuff, but as I see it, filters is the way that mail filtering should be handled.
--
Lic. Martín Marqués | SELECT 'mmarques' || Centro de Telemática | '@' || 'unl.edu.ar'; Universidad Nacional | DBA, Programador, del Litoral | Administrador