Serge Knystautas wrote:
> 
> I sent through a ton of the changes I had made this past week (mostly this
> weekend).  Here's an overview of what I changed:
> 
> - Patched Avalon to support configurable repositories.  Moved configuration
> for database mail repositories and LDAP user repository to the repository
> configuration part of the conf file.
> - Removed user manager altogether.  All it was doing was wrapping a user
> repository.  At this point seemed more logical to just have a shared user
> repository within JAMES rather than a separate object.
> - Moved user repository classes to org.apache.james.userrepository.
> - Moved mail repository classes to org.apache.james.mailrepository.
> - Added some anti-spam measures, including some new matchers/mailets, and
> configured JAMES out of box to **not relay any message sent from a remote
> machine**.
> - Changed mailet API slightly...
>   - MailetContext.bounce method optional 3rd parameter is now a MailAddress
> instead of a String.
>   - MailetException now extends MessagingException.  Originally was modeled
> on ServletException, but then MessagingException already does the wrapping
> of another exception, and we were already throwing MessagingException
> anyway.  Cleans it up and creates a specific type of MessagingException.
> - Reindented and started intro documentation at top of JAMES.conf.xml.  We
> had some many options with comments, all of them indented differently, was
> becoming unwieldly.  Not perfect, but hopefully at least better.
> - Completed listservs... the TownListserv was tested extensively, and the
> AvalonListserv is basically the same code, just extending the
> GenericListserv differently to handle configuration differently.  Also
> there's GenericListservManager, AvalonListservManager and the matcher
> CommandForListserv, which will send your list-on@host and list-off@host
> message to the listservmanager which will add/remove the email address from
> the user repository (which in theory could be an LDAP user repository now).
> 
> Really, that's it.  Aside from the configurations of repositories and some
> small bug fixes here and there, nothing I did was very substantial... just
> largely bug fixing here and there.  I spent a long time this evening working
> on exception handling in the processor.  As part of this, I created
> NotifyPostmaster and NotifySender which can be placed in the spam or
> processors.  These will send a notification email to the appropriate address
> (from the postmaster, which is overridable), optionally with the complete
> stack trace as an additional attachment.  These should make it much friendly
> for people trying to write mailets and matchers, so they can see the stack
> trace along with the exact message that it failed on.
> 
> I'm going to be working more on the exception handling and other robustness
> issues in my evenings this week... ideally I'd like JAMES to not die if the
> spool managers are unable to start... so even if something is misconfigured,
> you can still be receiving incoming email that can just queue up in the
> spool.
> 

Lots of new stuff, Serge. Must have been a long weekend!

> Anyway, hope people can have a go with it.

I've smoothed a few bumps in cvs and I have it back doing
smtp/pop3/remote mgr using file repositories for mail and users, with
and without TLS on pop3 and remote.

  I'm pretty confident with the
> code right now, although I can't test the LDAP stuff as I don't have a
> server (let along configured with the right schema) to test that, but
> hopefully it's receiving the settings properly.

I'll try to look at LDAP tomorrow.

  If it's not working, I
> might just be off one level in the Configuration object... should be easy to
> fix.  I'll try to test some Monday or Tuesday.  I also want to finish the
> packaged mailet and matcher documentation so people know what they can do
> out of the box, but that shouldn't very hard.
> 
> It's about time to release (and a return to other things in my life).

Yes, I think we should be close. I suggest we go for feature freeze
soon, then allow a few days for testing (bug fixes only) before release.
Thoughts?

Charles


------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives:  <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?:           [EMAIL PROTECTED]

Reply via email to