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 "Norman Maurer (JIRA)" <se...@james.apache.org> on 2006/06/16 17:30:29 UTC
[jira] Created: (JAMES-537) Add ConfigOption to disable the
RemoteManager
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
Assigned to: Norman Maurer
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
[jira] Updated: (JAMES-537) Add ConfigOption to disable the
RemoteManager
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-537?page=all ]
Norman Maurer updated JAMES-537:
--------------------------------
Attachment: RemoteManagerDisable.patch
Here is my patch for add this feature.. It also not change the standart behavior. So any problems with that ?If not i whould commit it to trunk
> 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
> 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
[jira] Resolved: (JAMES-537) Add ConfigOption to disable the
RemoteManager
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ 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
[jira] Updated: (JAMES-537) Add ConfigOption to disable the
RemoteManager
Posted by "Stefano Bagnara (JIRA)" <se...@james.apache.org>.
[ http://issues.apache.org/jira/browse/JAMES-537?page=all ]
Stefano Bagnara updated JAMES-537:
----------------------------------
Fix Version: 2.3.0b2
(was: 2.3.0)
(was: 2.4.0)
> 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.0b2
> 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