-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Ok. So I will simply create a class to provide an interface to manage filters :).

Regards,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFG1blHjKKs5/FTCjURArtaAJ4yf7mEfA1btkzu2u8M1vUJkNj2gQCfU9t1
kd+JoCu2TyN+WLR8ccO8xik=
=eSMm
-----END PGP SIGNATURE-----

On 8/29/07, till <klimpong@gmail.com> wrote:
Hey,

On 8/29/07, Maximilien Cuony <maxi.the.glu@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> > Please switch your signing to S/MIME - inline is so oldschool and "ugly".
> ;-)
>
> It's in our TODO list, "As soon as possible" ;) (I use FireGPG/Gmail)

I should really check out this extension! ;-)

> > IMO - I'd welcome an interface for server-side filters. It has to be
> > very abstract, because some IMAPDs have filters build in, others use
> > maildrop or/and procmail to achieve the same. So an interface would
> > need to be configurable (through a config file) and then people can
> > build filters.
>
> Mmm.. ok, like an option to select the filter's interface who will be used ?

Ok, basically I know that there is Sieve, Procmail, Maildrop and
"custom" solutions. So for example Macnews/Macbay runs Communigate Pro
which has build in filters/rules.

For Sieve, Procmail and Maildrop, there should be PHP implementations
already - at least so I think I remember. ;-) Maybe you can clean them
up and create an Abstract/Interface class which is implemented.

E.g.
abstract class rc_filter
{}

rc_filter_sieve extends rc_filter
{}

To provide one class interface which can always be used when someone
says, "hey my vanilla imap got his own rules, i am gonna contribute".

Cheers,
Till



--
(  o  _    Maximilien Cuony [The glu]
/ /  \       Mon Blog : http://theglu.tuxfamily.org
V_ /_     www.ubuntu-fr.org www.getfirefox.com
Ce mail est signé numériquement avec FireGPG.
Clé publique : http://theglu.tuxfamily.org/public/cle.pgp