[dev] Sieve filtering module

[Julian Jares]

About project 2:

(btw, my english is not what it used to be :-( )

I was thinking of two "blacklisting methods":
1. 
a. Ask all my users (currently 4) to send spam to a mailbox spam@domain
b. Have a daemon check that mailbox, and add to the mysql database (under 
username all) the froms
c. install rules for all users that include this rules, and their own.
d. the spam rules should send to a INBOX.junk folder (for if any mistakes)
e. monthly manteinance can clean the junk folder, say each week

2.
(this is cleaner, but doesn't support the cooperative spam reporting)
a. Basically replace the blacklist function with something that adds sieve 
filters... Im looking at the projects api.php to see how is that done.

Also, did you like what I did? disliked it? I used a lot of Chuck's code, just 
to use as much of the Horde framework as possible, but every time I look at 
imp, I just see I reinvented the wheel a lot :-)

Thanks,
Julian

Quoting Jan Schneider <janmailing@gmx.de>:

> Zitat von Julian Jares <julian@jares.com.ar>:
> 
> > yep, my mistake... just replace the line for
> >         if (isset($this->rules))
> > I think I have some of those scattered around :-)
> 
> Ok, no more error messages anymore.
> 
> > What I do, is on every disruptive change (add rule, edit rule,
> > delete rule, undelete rule) I build the actual rules and pass
> > them on to sieve.
> 
> You probably don't need the database anymore if you've got your "project 1"
> 
> done.
>  
> > I have two projects I'm working on:
> > 1. something to read the rules currently installed, and upload
> > them to the database
> 
> That would be a great feature! Have fun with the parser coding! ;-)
> 
> > 2. tell my users to an e-mail address, and have that read by a
> > deamon, and add it to common rules for all users (note the all user
> > in mysql, and the ALL_USERS constants everywhere)
> > (2 could be replaced by blacklist send to a junk folder, and
> > monthly maintenance deleting old files from that folder)
> 
> Sorry, but I don't understand what you mean.
> 
> Jan.
> 
> 
> 
> -- 
> Horde Developers mailing list: http://horde.org/
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: dev-unsubscribe@lists.horde.org
> 
> 


-- 
Julian