You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Charles Benett <ch...@benett1.demon.co.uk> on 2001/10/19 12:57:23 UTC
IMAP server
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.)
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
Re: IMAP server
Posted by Gabriel Bucher <ga...@razor.ch>.
No voting rights but +1 for moving to proposal!
Quoting Charles Benett <ch...@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
Re: IMAP server
Posted by Serge Knystautas <se...@lokitech.com>.
+1
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com/
----- Original Message -----
From: "Danny Angus" <da...@thought.co.uk>
To: <ja...@jakarta.apache.org>
Sent: Friday, October 19, 2001 8:00 AM
Subject: RE: IMAP server
> I haven't looked closely at IMAP, POP/SMTP/NNTP are enough to keep me
> occupied as it is ;-), but this seems like a reasonable suggestion.
>
> I'd say the only overriding consideration should be for IMAP
implementation
> to have configuration, and repository
> as close to the ones for the other protocols as is possible.
>
> Obviously the re-use of existing code is both polite to previous authors,
> and saves time, but a total revolution is preferable to no progress, and
if
> John is prepared to do it, why not.
>
> Should we vote on moving IMAP back to a proposal seperately to what
happens
> to it after that and before we procede with the mooted alpha release?
>
> d.
>
> > -----Original Message-----
> > From: charles [mailto:charles]On Behalf Of Charles Benett
> > Sent: Friday, October 19, 2001 11:57 AM
> > To: Java Apache Mail Server
> > Subject: IMAP server
> >
> >
> > 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.)
> >
> > 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
RE: IMAP server
Posted by Danny Angus <da...@thought.co.uk>.
I haven't looked closely at IMAP, POP/SMTP/NNTP are enough to keep me
occupied as it is ;-), but this seems like a reasonable suggestion.
I'd say the only overriding consideration should be for IMAP implementation
to have configuration, and repository
as close to the ones for the other protocols as is possible.
Obviously the re-use of existing code is both polite to previous authors,
and saves time, but a total revolution is preferable to no progress, and if
John is prepared to do it, why not.
Should we vote on moving IMAP back to a proposal seperately to what happens
to it after that and before we procede with the mooted alpha release?
d.
> -----Original Message-----
> From: charles [mailto:charles]On Behalf Of Charles Benett
> Sent: Friday, October 19, 2001 11:57 AM
> To: Java Apache Mail Server
> Subject: IMAP server
>
>
> 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.)
>
> 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