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 Phillip Smith <ph...@phillipsmith.com> on 2003/09/12 18:01:37 UTC

Modifying server handlers and repositories

This is my first post to this list so if it�s in the
wrong place, please advise.

I have re-implemented
org.apache.james.smtpserver.SMTPHandler to separate
the parsing of the stream from the handling of its
contents and to be configured for either blocking or
non-blocking mode.  I intend to do the same for the
org.apache.james.pop3server.POP3Handler and IMAP.  It
has been recently decided to add a MailRepository for
a modified MailDir format.  I know the James is built
on the Phoenix (Avalon), and allows its components to
be pluggable � but at want point does it stop being
James, if it stops at all?  I still intend to use the
Mailet functionality, the incoming spooling, and the
remote forwarding capabilities.  I�ve put non-James
classes (generic parsing) in my package namespace
(<toplevel-domain>.protocol.smtp, etc).  I�ve put
James classes in (<toplevel-domain>.james., etc).  Is
this appropriate?  I don�t want to call it James if it
isn�t, and vise versa.

Suggestions, advice, guidance requested

- Phillip

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


User attributes

Posted by Jason Webb <jw...@inovem.com>.
After some careful thought and good look through Darrell's code I think
I have most of the pieces I need.
However, I need to store attributes on the user for IMAP to work
properly. 
These are two lists:
1) The list of current folders
2) The list of subscribed folders

As there is no place to store this information, I propose to add
attributes to the User object to allow me to persist this information to
a store. 
I plan to implement this code (and thus the IMAP server) on the v3 code.

Any comments?

As an implementation detail you will never be able to unsubscribe from
the inbox folder, all user folders will be sub-folders of inbox and you
will always be able to get your mail either as POP3 or IMAP4. However if
you POP the mail out of your inbox and empty it, well that's your
problem :)
I note from the RFC that if you rename the inbox folder it simply
re-creates itself, after renaming the current inbox.


I plan to do no futher work on the Maildir implementation until the IMAP
server is at least in a usable state for futher development. 


-- Jason

P.S. My Apache account now works. Thanks Serge!



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


RE: Modifying server handlers and repositories

Posted by Phillip Smith <ph...@phillipsmith.com>.
--- "Noel J. Bergman" <no...@devtech.com> wrote:
> Phillip,
> 
> What is the purpose for what you're doing?  Are
> these things you are
> thinking of submitting as patches?

Intially no, this all started as a coding game.  I was
just going to toss the code, but the more I looked at
it, the more it looked like it could be more. And
after a couple of days tinkering, it turned into more.
There was a small test harnest and Outlook Express
successfully sends (but it doesn't go anywhere).  I am
looking to integrate it into James for the remaining
funtionality but if the code was ever 'released' I
wanted to be sure my package names did not offend the
community.

> 
> For example:
> 
> > I have re-implemented
> org.apache.james.smtpserver.SMTPHandler
> > to separate the parsing of the stream from the
> handling of its
> > contents and to be configured for either blocking
> or non-
> > blocking mode.
> 
> That sounds similar to what I have suggested we do
> to enable java.nio as an
> option.
> 
> > It has been recently decided to add a
> MailRepository for
> > a modified MailDir format.
> 
> Jason Webb was working on a MailDir MailRepository,
> having just finished
> mbox support.
> 

The modification (or extension) to the MailDir format
partitions messages using Dates instead of MessageIDs.
 This is more of a proof of concept than anything
else.

- Phillip

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


RE: Modifying server handlers and repositories

Posted by "Noel J. Bergman" <no...@devtech.com>.
Phillip,

What is the purpose for what you're doing?  Are these things you are
thinking of submitting as patches?

For example:

> I have re-implemented org.apache.james.smtpserver.SMTPHandler
> to separate the parsing of the stream from the handling of its
> contents and to be configured for either blocking or non-
> blocking mode.

That sounds similar to what I have suggested we do to enable java.nio as an
option.

> It has been recently decided to add a MailRepository for
> a modified MailDir format.

Jason Webb was working on a MailDir MailRepository, having just finished
mbox support.

	--- Noel


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


Re: Modifying server handlers and repositories

Posted by Phillip Smith <ph...@phillipsmith.com>.
The goal is not to distribute a derivative copy,
per-se, but to allow different implementations of the
internals.  There is no intention to provide a sar,
but once one has a sar, jars can be dropped in and the
xml config files updated to use the different
implementations.

I guess basically I'm asking: Is it ok to use the
James name outside of the org.apache namespace?

Thanks,
- Phillip

--- Serge Knystautas <se...@lokitech.com> wrote:
> Maybe you could give a bit more background so we can
> help "guide" you there.
> 
> If you want to distribute a derivative copy of
> James, then you cannot 
> call it James.  As for reworking the code, putting
> James code here and 
> there, a maildir implementation, whatever else...
> all that's just fine 
> and great.  In fact some of those might be
> interesting patches as others 
> could be interested.
> 
> Anyway, again nothing you've described is wrong. 
> But where are you 
> trying to go and what are you asking of us?
> 
> -- 
> Serge Knystautas
> President
> Lokitech >> software . strategy . design >>
> http://www.lokitech.com
> p. 301.656.5501
> e. sergek@lokitech.com
> 
> Phillip Smith wrote:
> > This is my first post to this list so if it�s in
> the
> > wrong place, please advise.
> > 
> > I have re-implemented
> > org.apache.james.smtpserver.SMTPHandler to
> separate
> > the parsing of the stream from the handling of its
> > contents and to be configured for either blocking
> or
> > non-blocking mode.  I intend to do the same for
> the
> > org.apache.james.pop3server.POP3Handler and IMAP. 
> It
> > has been recently decided to add a MailRepository
> for
> > a modified MailDir format.  I know the James is
> built
> > on the Phoenix (Avalon), and allows its components
> to
> > be pluggable � but at want point does it stop
> being
> > James, if it stops at all?  I still intend to use
> the
> > Mailet functionality, the incoming spooling, and
> the
> > remote forwarding capabilities.  I�ve put
> non-James
> > classes (generic parsing) in my package namespace
> > (<toplevel-domain>.protocol.smtp, etc).  I�ve put
> > James classes in (<toplevel-domain>.james., etc). 
> Is
> > this appropriate?  I don�t want to call it James
> if it
> > isn�t, and vise versa.
> > 
> > Suggestions, advice, guidance requested
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail:
> server-dev-help@james.apache.org
> 
> 
> 
> 


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


Re: Modifying server handlers and repositories

Posted by Serge Knystautas <se...@lokitech.com>.
Maybe you could give a bit more background so we can help "guide" you there.

If you want to distribute a derivative copy of James, then you cannot 
call it James.  As for reworking the code, putting James code here and 
there, a maildir implementation, whatever else... all that's just fine 
and great.  In fact some of those might be interesting patches as others 
could be interested.

Anyway, again nothing you've described is wrong.  But where are you 
trying to go and what are you asking of us?

-- 
Serge Knystautas
President
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. sergek@lokitech.com

Phillip Smith wrote:
> This is my first post to this list so if it’s in the
> wrong place, please advise.
> 
> I have re-implemented
> org.apache.james.smtpserver.SMTPHandler to separate
> the parsing of the stream from the handling of its
> contents and to be configured for either blocking or
> non-blocking mode.  I intend to do the same for the
> org.apache.james.pop3server.POP3Handler and IMAP.  It
> has been recently decided to add a MailRepository for
> a modified MailDir format.  I know the James is built
> on the Phoenix (Avalon), and allows its components to
> be pluggable – but at want point does it stop being
> James, if it stops at all?  I still intend to use the
> Mailet functionality, the incoming spooling, and the
> remote forwarding capabilities.  I’ve put non-James
> classes (generic parsing) in my package namespace
> (<toplevel-domain>.protocol.smtp, etc).  I’ve put
> James classes in (<toplevel-domain>.james., etc).  Is
> this appropriate?  I don’t want to call it James if it
> isn’t, and vise versa.
> 
> Suggestions, advice, guidance requested


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