Hello James users and Gurus,
I am the owner of the JXTA p2p-email project on www.jxta.org.
I intend to use a subset of James' code ("Jimmy") to create a
redirecting, e-mail proxy and email<->JXTA gateway.
I need help in identifying the relevant files as I don't want a full
fledged SMTP server installation especially
not - message storage, user management ...
It will work by intercepting all outgoing email from a client.
(The client will be fooled into thinking the proxy is the MTA and the
proxy will forward regular email to the actual MTA.)
Messages meant for transport via JXTA pipes to JXTA endpoints will have
a "jxta:" prefix in the "rfc822-proper" email address.
A mailet will match the prefix and collect all such addresses and hand
off a copy of the msg with JXTA addresses to a JXTA service which will
take it from there. The mailet will also create another copy of the
message with smtp-based destinations and
forward to the regular MTA.
Complementary things will happen for incoming messages which will end up
as regular MIME (multipart) documents in the inbox.
The assumption is that they have been sent by a similar facility to the
one described above, and are well formed MIME (multipart) docs, the only
distinguishing factor being that the from: address has a "jxta:" prefix.
They can seamlessly be forwarded to regular email destinations with NO
transformations.
The idea is to leverage existing email client facilities for msg
composition, folder management, directory and addressbook management
(LDAP etc.), account and profile management ... and only plug-in the 5%
of code that is relevant to a new transport, by extending the proxy.
Aside from that 5%, the typical email client is basically a
MIME-document/user account/address book management facility which
doesn't need to be re-invented. The mailet scheme could also be
generalized to other protocols than the JXTA re-direction, via
appropriate matching tags. This will work for async/store and forward
msg-ing but probably unwieldy for things like IM etc.
I have installed the full fledged James and played with it, have read
the user/developer docs especially the mailet stuff, but could use
pointers on how to draw the line between what Java files to keep and
what to leave out so that James may give birth to Jimmy.
So where do I begin ? I am hoping to save some time and pain by using
the collective wisdom on the list.( I know, get a CVS tree, then what
?) I am looking for non-obvious dependencies and hidden gotchas,
mostly.
Thanks for taking the time,
--
Nitin Borwankar
[EMAIL PROTECTED]
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
