geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajith Attapattu" <>
Subject RE: Who wants to write POP and IMAP transports? [status]
Date Tue, 06 Dec 2005 17:37:36 GMT
>There is an implementation of all of the javamail api classes
(including >support for multipart-MIME messages).  There's very little
done in terms of >protocol-specific implementation classes other than
the SMTPTransport code >that was just promoted out of the sandbox.

Going by what Rick mentioned above, I assume that we do have an
implementation for the Message classes. Or did u refer to the reference
impl from sun??

If the Message implementation is done by Geronimo developers then we can
extend and provide POP3Message and IMAPMessage implementations.

As for the portlet thingy I got it all mixed up :)
I thought the configuration module for the underlying JavaMail
implementation was exposed as a portlet through the console.

But as Bruce mentioned I guess for now we are concentrating more on
getting the JavaMail implementation.


Rajith Attapattu.

-----Original Message-----
From: Bruce Snyder [] 
Sent: Tuesday, December 06, 2005 12:23 PM
Subject: Re: Who wants to write POP and IMAP transports? [status]

On 12/6/05, Rick McGuire <> wrote:

> >Is the goal to create a full IMAP client with offline capabilities.
If so
> >what local message format is going to be used? Is this client going
to be
> >plugged in as a portlet in the console?

We're not building a client application. We're simply writing
transports for the Geronimo JavaMail distribution to allow
communication with mail servers via the various protocols. This effort
has nothing to do with plugging into the console, it's far below that
in the architecture sense.

> >I have the code for an online imap client. It has basic functionality
> >grab folders and pull down messages. What are the feature
requirements for
> >this thing?
> >
> >
> The requirements here are to add POP3 and IMAP support to the geronimo
> implementation of the javamail apis.  The end target is an
> implementation that functions exactly the same as the Sun
> of the same.  Everything implemented here needs to be under the
> of the javamail apis.  So, for example, the local message format will
> an implementation of the javamail message class.

POP3 and IMAP each have their own defintion of a message as well. So
this is one of the things we're providing.

> Currently, all that is implemented is an outbound smtp transport.
> transport takes as input a javamail Message instance and send it to an
> smtp server.  Missing right now is the capability for inbound messages
> (i.e., POP3 or IMAP).   These need to be implementations of the
> AbstractStore and AbstractFolder class.  Currently, we have some stub
> implementations of these classes in the sandbox/mail directory, but
> are currently just empty autogenerated classes.  Somebody needs to
> in the blanks.

Yes, in addition to modeling both POP3 and IMAP Stores and Folders, we
also need to be able to connect to each server type and speak each
protocol. In addition we'll need handlers that implement
DataContentHandler for each message type including plain text, html
and RFC822 (MIME messages). These impls just read messages from a
javax.activation.DataSource and write messages to an OutputStream. The
Sun JavaMail distribution provides both implementations, but it's not
licensed in a way for us to make use of it.

And like I said before, once we get these completed, maybe we can
consider offering Maildir and Mbox implementations if we're feeling

perl -e 'print

The Castor Project

Apache Geronimo

View raw message