---------- Forwarded message ---------- From: Eric Charles <[email protected]> Date: Mon, Jul 29, 2013 at 3:59 PM Subject: Re: Using Apache James for Reputation Management in Email Systems To: James Users List <[email protected]>
Does the email client communicate with REST to the ReputationServer? This sounds a bit odd cause you will have to develop custom plugins/extensions for all clients. The intial idea was to develop a REST based communication between the client and the ReputationServer. That was before I considered James server for my project. The communication between the ReputationServer and email-client comprises below actions. 1. User views/retrieves the reputation score of a particular contact(s). 2. User shares his Map<Contact,ReputationScore> with others in his contact list. here I should apply authorization(Still haven't thought of how to control access to the reputationMap of a user). For the above 2 types of communication between the email client and server, I think I can even use IMAP (to retrieve repuScore data to client). Do you see LDAP as a better alternative ? Thanks, Dileepa I would rather have used LDAP which is supported by all major clients. On 2013-07-29 12:05, Dileepa Jayakody wrote: > Hi Eric, > > Thanks for ur response. Please find my high-level architecture diagram at : > http://creately.com/diagram/**example/hjkwxh261<http://creately.com/diagram/example/hjkwxh261> > It would be great to get your suggestions on the architecture to make it > more generic and extensible. > > Thanks, > Dileepa > > > On Mon, Jul 29, 2013 at 3:29 PM, Eric Charles <[email protected]> wrote: > > Yes, James is the ideal fit for such specific mail usecases. >> The inline image is not visible. Can you send a link rather than an >> attachment? >> >> >> On 2013-07-29 11:00, Dileepa Jayakody wrote: >> >> Hi All, >>> I'm Dileepa a newbie to Apache James. I'm doing my Msc research project >>> on : Reputation Management in Email Networks in which I aim to implement >>> a reputation management network among peers using email systems. >>> Each user will have an index of reputation scores for his contacts >>> (based on email content analysis as per his personal context and number >>> of spam/not-important messages sent by the contact). This reputation >>> scores should be shared among peers in a controlled manner (ACL, >>> authorization) to deliver a collaborative reputation network. I'm >>> planning to use an extended SMTP protocol to share reputation attached >>> to email users. >>> >>> I came across the Apache James <http://james.apache.org/> project and >>> >>> realized it provides an API to extend existing protocols like SMTP and >>> IMAP to perform additional tasks via APIs like James Mailet >>> <http://james.apache.org/****mailet/index.html<http://james.apache.org/**mailet/index.html> >>> <http://**james.apache.org/mailet/index.**html<http://james.apache.org/mailet/index.html> >>> >> >>> >>> and SMTP Hooks. >>> >>> >>> Below is the architecture I have in mind for reputation management via >>> email networks. Reputation Server, ReputationBox are analogous to the >>> email IMAP/POP servers and MBox of users. I highly appreciate your ideas >>> on my project and wish to incorporate your suggestions on using Apache >>> James or related technologies to my project. >>> >>> Your thoughts and tips on James are highly appreciated. >>> >>> Inline image 1 >>> Regards, >>> Dileepa >>> >>> >> ------------------------------****----------------------------** >> --**--------- >> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org< >> server-user-**[email protected]<[email protected]> >> > >> For additional commands, e-mail: [email protected].****org< >> server-user-help@james.**apache.org <[email protected]>> >> >> >> > ------------------------------**------------------------------**--------- To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<[email protected]> For additional commands, e-mail: [email protected].**org<[email protected]>
