james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Norman Maurer (JIRA)" <server-...@james.apache.org>
Subject [jira] Resolved: (JAMES-537) Add ConfigOption to disable the RemoteManager
Date Fri, 16 Jun 2006 19:13:30 GMT
     [ http://issues.apache.org/jira/browse/JAMES-537?page=all ]
     
Norman Maurer resolved JAMES-537:
---------------------------------

    Fix Version: 2.3.0
                 2.4.0
     Resolution: Fixed

Forget about this patch.. My brain must not on the right place when writting it. Only modify
the james.xml is needed ..

> Add ConfigOption to disable the RemoteManager
> ---------------------------------------------
>
>          Key: JAMES-537
>          URL: http://issues.apache.org/jira/browse/JAMES-537
>      Project: James
>         Type: New Feature

>     Reporter: Norman Maurer
>     Assignee: Norman Maurer
>      Fix For: 2.3.0, 2.4.0
>  Attachments: RemoteManagerDisable.patch
>
> At the moment there is no option for disabling the RemoteManager. Some people maybe don'T
want the RemoteManger be run. If someone use james only as gateway there is no need for this
service!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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


Mime
View raw message