james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Norman Maurer ...@byteaction.de>
Subject RE: JAMES Administration
Date Wed, 26 Jul 2006 06:05:32 GMT
Kann you explain what was not workin for you ? Was it a bug in the code?
If so please make a bugreport!

bye
Norman


Am Mittwoch, den 26.07.2006, 07:07 +1000 schrieb Mark Brennand:
> Thanks. I have been building from trunk for the last couple of weeks (I
> moved the SpamAssassin stuff over into my JAMES 2.3 install, modifying
> header and logging behaviour as it was not working for me) but I have not
> had the chance to test it yet.
> 
> I am very keen to read up on the JMX stuff as it looks like it could/would
> be perfect to use in what I would use as a management interface: a *) webmin
> module and.or *) a small web based console.
> 
> The wizard driven install is a great idea; starting from a total set of
> options and eventually writing out to the config files the user desired ones
> although placement of mailets may get tricky based on my current config
> (i.e. SPAM gets sent to a spam account for monitoring but not if it came
> from a whitelisted account, then it is tagged and sent to local recipient
> and other such stuff)
> 
> I have been playing with small PHP setup; attempting to read, alter and
> write the xml files that form the configuration backbone of JAMES but JMX
> seems more robust, scalable and extensible.
> 
> Thanks for the pointers.
> 
> Regards MB
> 
> -----Original Message-----
> From: Stefano Bagnara [mailto:apache@bago.org] 
> Sent: Tuesday, 25 July 2006 11:02 PM
> To: James Users List
> Subject: Re: JAMES Administration
> 
> Bernd Fondermann wrote:
> > However, in James 2.2.0 and the upcoming 2.3 release, the support for 
> > JMX within James is limited.
> > 
> > But, work has started to put more management operations in. This can 
> > currently be found in source code only (in the "trunk"). It covers 
> > more or less all operations already available in the telnet console 
> > (RemoteManager).
> > This functionality will become available in the next major release, I 
> > guess.
> 
> Nightly builds for the current trunk are available here if you want to test
> it:
> http://people.apache.org/builds/james/nightly/
> 
> Stefano
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
> 
> !EXCUBATOR:1,44c6882f43382057716539!

Mime
View raw message