Hi All,

Can I please get some pointers for ways of extending James Server?

To implement the reputation server using James, I intend to extend the
james-mailbox as a reputationbox..
After implementing reputationbox, how can I configure the new components in
James at runtime?
If I drop it in $JAMES/lib will it pick up the new libraries?

Thanks,
Dileepa


On Mon, Jul 29, 2013 at 5:42 PM, Dileepa Jayakody <[email protected]
> wrote:

> Thanks a lot for your valuable input Josip:)
> I will share my project details on my way forward in the implementation.
>
> Regards,
> Dileepa
>
>
> On Mon, Jul 29, 2013 at 5:39 PM, Josip Almasi <[email protected]> wrote:
>
>> Hi,
>>
>> for a while now I have james rep system on my wish list.
>> Did some research, and was going to implement it... soon... just after I
>> do this and that... and so it goes on for years:)
>> So here are my ideas about, maybe you can use them somehow.
>>
>> NeuroGrid [1] is a neat yet simple reputation system, works with simple
>> positive and negative stimulus.
>> Negative stimulation is received when user gets recommendiation, and
>> positive when user confirms it.
>> In web environment, that would correspond to receiving search results,
>> and clicking on a link.
>> In mail environment, corresponding negative and positive stimulus is
>> downloading envelope, and downloading message body.
>> Note this applies to IMAP only.
>> Furthermore, additional positive stimuli apply when a reply is sent; SMTP
>> only
>>
>> In JAMES environment, you'd need to
>> - extend IMAP server
>> - extend message store
>> - write you own mailet
>> - possibly, extend user store
>>
>> And you don't need to customize email client.
>> Of course, it may be nice to query users reputation, but that need not be
>> integrated into email client - a web app will do.
>> As for standard operation during reading of mails, usual subject changes
>> would do, i.e.
>> [troll 42.03%] original subject here
>> [guru 99.98%] and the subject
>> etc.
>> Once you get that working, it's easy to do the rest with standard mail
>> filters.
>>
>> That's in short about my would-be rep system, see if you can use any.
>> Also, I would love to learn more details of yours.
>>
>> Regards...
>>
>>
>> [1] http://www.neurogrid.net/
>> Aww the site is down:(
>> Look it up on SourceForge, and check p2p reputation papers by Sam Joseph
>> et al.
>>
>>
>> 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>>
>>> 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
>>>
>>
>>
>

Reply via email to