I like it. I am probably going to put it on my backup server and try it as a alternative install... Just to try it out. It would save me a lot of trouble with running Evolution and Filters. I am no dev but i think it looks good.
One idea, what about using an enum on the filter_field column instead of a varchar. This might help to have to put 'subject', 'recipent', 'sender', etc. into the column... Just my thoughts... On Tue, 2005-09-20 at 15:28 +0400, Eugene Prokopiev wrote: > Hi, > > There are no suitable way for mail filtering with DBMail. Sieve support > is not stable and excluded by default, procmail will slow perfomance by > invoking another process ... > > So, I write very simple filtering engine for DBMail. It's attached and > based on this new table: > > CREATE TABLE dbmail_filters ( > user_id bigint(21) not null default '0', > filter_id bigint(21) not null default '0', > filter_field varchar(128) NOT NULL default '', > filter_value varchar(255) NOT NULL default '', > index user_id_index (user_id), > index filter_id_index (filter_id), > PRIMARY KEY (user_id, filter_id), > FOREIGN KEY user_id_fk (user_id) > REFERENCES dbmail_users (user_idnr) ON DELETE CASCADE ON UPDATE > CASCADE > ) TYPE=InnoDB; > > If mail message field value contains value of filter_value database > field it will be moved to folder referenced by mailbox database field. > > My implementation is not optimal and is not hight perfomance. It's seems > to work with MySQL, but it's make sense to test it more. It hasn't been > tested with PostgreSQL. > > Is my patch helpful for anybody? What can you say about including it in > main source tree of DBMail? > > -- > Regards, > Eugene Prokopiev > > _______________________________________________ > Dbmail mailing list > Dbmail@dbmail.org > https://mailman.fastxs.nl/mailman/listinfo/dbmail >
signature.asc
Description: This is a digitally signed message part
