I'm getting very close to completing separating the mailet API from
JAMES and Avalon... the latest Javadocs (much more complete) are again
posted to http://www.lokitech.com/~sergek/mailetdocs/.
One of the hardest design decisions is how to keep mailets avalon
independent while still allowing particular mailets to leverage the
avalon framework... for instance, listservs that use the user manager or
the ToRepository mailet. What I've done to facilitate this is have the
Avalon server store as a MailetContext attribute the Avalon
SimpleComponentManager object. This means in most cases your mailet is
avalon independent, but if you want, you can get a reference to the
SimpleComponentManager and grab a UserRepository, MailRepository, or
whatever you want out of Avalon.
Down from 63+ classes with errors to about 8 now... I've added several
methods to MailetContext (the mailet container) to facilitate many of
the standard mail server operations.
getPostmaster() - gets the postmaster address
getServerNames() - gets a Collection of valid local server names (will
likely change this to an Iterator)
getLocalUsers() - gets a Collection of a list of usernames of local
mailboxes (will change this to an Iterator)
sendMail(sender, recipients, message) - sends a message (puts at the top
of the message stack)
storeMail(sender, recipient, message) - stores a message in a local
mailbox. (the reason I have to pass the sender is because local
mailboxes store a Mail object instead of just a MimeMessage, so you need
a sender I do believe... if Mail does not require it, I will remove this
parameter from storeMail).
Hope nobody is annoyed with my constant (longwinded) posts, but I'm
spending a lot of time on JAMES and want to keep everyone who is
interested aware of anything I might be changing.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
