james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Webb" ...@inovem.com>
Subject RE: Future direction for James
Date Mon, 17 Nov 2003 15:19:17 GMT


> -----Original Message-----
> From: Danny Angus [mailto:Danny_Angus@slc.co.uk] 
> Sent: 17 November 2003 15:11
> To: James Developers List
> Subject: RE: Future direction for James
> 
> 
> 
> 
> 
> 
> > Therefore I think that users should have a processing pipeline as 
> > well. When LocalDelivery runs it should not just blindly 
> deliver the 
> > mail, it should execute the user's mail pipeline as well.
> 
> W/O trawling through this discussion I think you've just 
> resurected an idea from days of yore. Per account pipelines.
> 
> Of course following my own advice I'd say that this should be 
> implemented by a specialised processor, where workflow is 
> split into an individually describe path for each user.
> 
> You might want to restrict what was carried out so that you 
> could have a spam filet, then a quota matcher, then a 
> forwarding rule and perhaps an out-of-office mailer. Features 
> installed by admins an not users.
This is what I was getting at. 
I assume these would be configured via a web interface rather than using
the XML files as you don't always want your out-of-office handler on all
the time...
This point then leads back to the old issue of dynamic pipeline
configuration. If it's good enough for UserMailets etc., why not use it
for the main pipeline as well.
> 
> A simple manager for user defined functions would read 
> per-user configurations to instantiate and configure a set of 
> normal linear-processors, and route mail through the right one.
> 
> How to allow users to config their own settings is another 
> matter, but some kind of auto-responder for each mailet would 
> be a possibility, we might have to subclass Mailet to arrive 
> at a useful definition of a User Configured Mailet.
> 
> I suppose the main issue would be where and how to store and 
> read settings, then again we could relate it to User repository.
> 
> Just speculating.
> 
> d..
> 
> 
> 
> **************************************************************
> *************
> The information in this e-mail is confidential and for use by 
> the addressee(s) only. If you are not the intended recipient 
> (or responsible for delivery of the message to the intended 
> recipient) please notify us immediately on 0141 306 2050 and 
> delete the message from your computer. You may not copy or 
> forward it or use or disclose its contents to any other 
> person. As Internet communications are capable of data 
> corruption Student Loans Company Limited does not accept any  
> responsibility for changes made to this message after it was 
> sent. For this reason it may be inappropriate to rely on 
> advice or opinions contained in an e-mail without obtaining 
> written confirmation of it. Neither Student Loans Company 
> Limited or the sender accepts any liability or responsibility 
> for viruses as it is your responsibility to scan attachments 
> (if any). Opinions and views expressed in this e-mail are 
> those of the sender and may not reflect the opinions and 
> views of The Student Loans Company Limited.
> 
> This footnote also confirms that this email message has been 
> swept for the presence of computer viruses.
> 
> **************************************************************
> ************
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
> 
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message