james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Yoost <Jo...@jeld-wen.com>
Subject RE: IMAP server
Date Fri, 19 Oct 2001 19:10:37 GMT
GREAT

> -----Original Message-----
> From:	Danny Angus [SMTP:danny@thought.co.uk]
> Sent:	Friday, October 19, 2001 12:00 PM
> To:	james-dev@jakarta.apache.org
> Subject:	RE: IMAP server
> 
> The list I guess.
> Unless its so much that you don't want to spam the list, then just
> announce
> its ready, and whoever is available can step up to the plate and do it.
> d.
> 
> > -----Original Message-----
> > From: John Yoost [mailto:JohnY@jeld-wen.com]
> > Sent: Friday, October 19, 2001 7:44 PM
> > To: james-dev@jakarta.apache.org
> > Subject: RE: IMAP server
> >
> >
> > OK,
> >
> > When I get enough stuff working I'll send it to who???? to be put into
> > proposal/imapserverB.
> >
> > -John Yoost
> >
> > > -----Original Message-----
> > > From:	Gabriel Bucher [SMTP:gabriel.bucher@razor.ch]
> > > Sent:	Friday, October 19, 2001 5:55 AM
> > > To:	james-dev@jakarta.apache.org
> > > Subject:	Re: IMAP server
> > >
> > > No voting rights but +1 for moving to proposal!
> > >
> > > Quoting Charles Benett <charles@benett1.demon.co.uk>:
> > >
> > > > My thoughts on the IMAP server are:
> > > >
> > > > 1) Move current code back to proposal dir. (imapserverA ??)
> > > > 2) Don't include IMAP server in standard binary dist
> > > > 3) Remove all IMAP tie-oins from src/cvs
> > > > 4) John Yoost adds his stuff in another proposal dir (imapserverB
> ??)
> > > > 5) As and when either imap version reaches RFC2060 full compliance,
> we
> > > > can then vote to move it to the main tree.
> > > > (Which will probably be John's as I am swamped for the next few
> > > > months.)
> > > Im interesting to help!
> > >
> > > Buchi
> > >
> > > >
> > > > Re: current imap code in cvs
> > > > See
> > > > http://jakarta.apache.org/james/commandsIMAP.html
> > > > http://jakarta.apache.org/james/statusIMAPserver.html
> > > >
> > > > ie when I last worked on the imap code, I could login from pine and
> > > > netscape clients. I think all the repository code worked as well.
> > > > The main issue was message parsing and some of the wire protocol.
> > > > Hence
> > > > several commands have a YES in the telnet column of status but not
> in
> > > > the pine/ netscape columns.
> > > >
> > > > if people can't login at the moment, that means the (extensive)
> > > > changes
> > > > in Avalon since then have not been applied correctly. Which is quite
> > > > likely.
> > > >
> > > > Cheers,
> > > >
> > > > Charles
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: james-dev-help@jakarta.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: james-dev-help@jakarta.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: james-dev-help@jakarta.apache.org
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: james-dev-help@jakarta.apache.org

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


Mime
View raw message