Thanks for the very instructive email.
Wouldn't you mind stating in
http://james.apache.org/server/monitor-jmx.html that these system
properties might be setted for a remote JMX usage?
https://github.com/apache/james-project/blob/master/src/site/xdoc/server/monitor-jmx.xml
is the corresponding
Hi Jerry,
You need to be aware James restrict JMX access to localhost.
As you know, the James command line is currently using JMX.
JMX is known-to-be unsecure: read
https://www.cvedetails.com/cve/CVE-2017-12628/ for instance. Exposing
JMX only to localHost is a mitigation.
Could this be the
Hi Jerry
Well,
1. You are asking sometime hard questions that people can't answers
without significant work overhead.
2. This is OpenSource. This is Free. This is 'best effort' given a
limited time range.
Please read again carefully the Apache foundation mailing list guide
lines:
Sai,
Thanks for the quick response. But in the latest 3.3.0 download, there
is not a james.sh file. I've been using run.sh. There is a
james-cli.sh. But I have not been using it. But both the run.sh and
james-cli.sh files have those two parameters already specified in the
JAVA command.
Hi Jerry,
you need to add JVM options before starting the James server. See the
two parameters below:
Edit james.sh in vi editor or whichever you are comfortable with and
then add "-Dcom.sun.management.jmxremote=true" and
"-Dcom.sun.management.jmxremote.authenticate=false", see below the way
how
I figure if I keep asking questions, sooner or later I'm going to hit
one that SOMEBODY can help me with The issues keep backing up. And
my deadline is way too close Is anyone using James 3.3.0? Yet I'm
the only one having these out-of-the-box problems? This migration has
been an
Still nothing on making the logs work... While waiting on that, I'm
moving to SSL. I was not using SSL on beta5. So this is likely a
generic SSL question not specific to 3.3.0. See the setup and
configuration info below. When I try to create an account in
Thunderbird and also in an
