On 12/2/05, Dain Sundstrom <[EMAIL PROTECTED]> wrote: > We still need POP and IMAP transports for our JavaMail > implementation. Do any of you have some POP or IMAP client code > sitting around, or would you like to write one?
I wish I had this code just lying around because there's a fair amount of effort involved in going through the RFCs for each protocol and modeling everything. I started to look into this last night to try to guage the amount of effort required because I've got some experience working fairly deeply with IMAP in the past (see http://www.horde.org/imp/). But it's been a while since I've dug into the RFCs related to mail protocols. Below is my very rough map of what's needed: The protocols stacks: 1) Socket-based connection objects for each protocol 2) Full authentication and crypto providers 3) The full suite of IMAP commands, responses, etc. for communicating with the server (I'm sure there's more that I'm overlooking here) The transports: 1) A model of each message store 2) A model of each message type And of course tests for everything ;-). I'll try to get started on the IMAP side of things in the next day or two, after I complete a book chapter ;-). Once that's complete I'll see what I can do with the POP3 side. Bruce -- perl -e 'print unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' The Castor Project http://www.castor.org/ Apache Geronimo http://geronimo.apache.org/
