james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin" <robertburrelldon...@gmail.com>
Subject Re: Adding additional authentication mechanisms?
Date Thu, 19 Jun 2008 21:03:39 GMT
On Thu, Jun 19, 2008 at 3:21 PM, Rick McGuire <rickmcg@gmail.com> wrote:
> A comment of Stefano's on the Geronimo integration thread reminded me of an
> issue I had with the James servers while I was developing the Geronimo
> javamail providers.  Originally, I started out using James as my test server
> for the providers, but sort of hit a wall when it came to testing out the
> the different authentication mechanisms.  I needed a server that could
> support more than LOGIN and PLAIN authentication.  For a lot of things, I
> ended up using the GMAIL POP3 and IMAP servers.  I also had to set up and
> configure my own local FetchMail server for some of the mechanisms (several
> weeks of my life I'd like to get back :-)).

the IMAP implementation is reasonable complete but not production ready now

> Initially, I went with my own implementation of CRAM-MD5 and DIGEST-MD5
> authentication mechanisms because I was writing this for the Geronimo 1.x
> releases, which ran on 1.4.  Once we cut new development over to Geronimo
> 2.x, Java 5 was now required, and our javamail impl could start using the
> SASL API for authentication, which opened more possibilities for
> authentication.  Have there been any thoughts about doing the same for
> James?  This might be something I'd be interested in helping with, since in
> the long run, it makes testing of the Java API easier to do.

sounds like a good offer to me :-)

- robert

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message