You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Samuel Sadek <sa...@hotmail.com> on 2002/05/11 19:10:09 UTC

Junk Filter

I'm sure someone has already posed this question to this mailing list but 
thought to highlight it once again.

Has anyone thought of migrating any static mailets currently held in 
config.xml file at JAMES startup-time to say to a more dynamic approach.

I'm thinking in the case where we may want to impose further mail 
restrictions form being delivered to users mailboxes by offering Junk 
Filters at the discretion of users  as well as to Postmasters?

I was thinking of going ahead and create a db repository version of dynamic 
lookups of mailet configurations and opposed to from a file and give users 
the control of defining mailets at run-time which I think is a more robust 
and flexible solution for JAMES.

Has there been any work done to achieve this yet?

I would appreciate feedback on this matter as I'm currently investigating 
this topic.

Thanks in advance.

Sam.


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: Junk Filter

Posted by Serge Knystautas <se...@lokitech.com>.
I would tend to agree with Danny on this... aside from the challenge of 
making the processor load from a DB, usually it's one or two 
mailets/matchers that you want dynamic configuration from, not dynamic 
configuration as a whole.
-- 
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com/

Noel J. Bergman wrote:
> Sam,
> 
> 
>>I was thinking of going ahead and create a db repository version of
> 
> dynamic
> 
>>lookups of mailet configurations [and] give users  the control of defining
>>mailets at run-time
> 
> 
> I don't know what it would take to build Processor chains dynamically, but
> am I unconvinced that I would want to allow arbitrary mailets to be loaded
> without admin authority.  It seems to me that there are less radical
> approaches than modifying James to build processing chains dynamically based
> upon matching.  Your salient point was "we may want to impose further mail
> restrictions [by] offering Junk Filters at the discretion of [users and
> postmasters.]"
> 
> Filters are generally matchers, not mailets.  There is already a matcher
> (NESSpamCheck) that filters based upon regex patterns.  The patterns are
> hardcoded in the matcher, but could be moved into a database table.  You
> could extend the notion to support more sophisticated matching driven by
> dynamic, even recipient specific, content in a database.
> 
> 	--- Noel


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: Junk Filter

Posted by "Noel J. Bergman" <no...@devtech.com>.
Sam,

> I was thinking of going ahead and create a db repository version of
dynamic
> lookups of mailet configurations [and] give users  the control of defining
> mailets at run-time

I don't know what it would take to build Processor chains dynamically, but
am I unconvinced that I would want to allow arbitrary mailets to be loaded
without admin authority.  It seems to me that there are less radical
approaches than modifying James to build processing chains dynamically based
upon matching.  Your salient point was "we may want to impose further mail
restrictions [by] offering Junk Filters at the discretion of [users and
postmasters.]"

Filters are generally matchers, not mailets.  There is already a matcher
(NESSpamCheck) that filters based upon regex patterns.  The patterns are
hardcoded in the matcher, but could be moved into a database table.  You
could extend the notion to support more sophisticated matching driven by
dynamic, even recipient specific, content in a database.

	--- Noel


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>