Hi Jerry,
I'm very happy to see the community is able to make business on top of
James! That's great!
As James seems to be a non negligible part of your business, there's
things you can do not to be left behind with tight deadline in the future:
- Join server-dev mailing list:
- You will
Hi Jerry,
I don't use 3.3.0, however, I just downloaded 3.3.0 for you and ran a
quick test by running run.bat file in my windows command prompt and
JMX is working fine without issues.
I can also see the basic logs in my console. May be you have to try
starting the server in different way. I don't
The way I understand tunneling, with SSH tunneling, I am technically
connecting locally. I use PuTTY on my local machine. But I set up a
secure tunnel to port on the remote host. When I connect to
localhost: on my machine it's the same as connecting to
localhost: on the target
I apologize that my posts have appeared course. I'm very frustrated and
nervous about my client base. I committed my business to James around
2004, I believe. I upgraded from v2 to v3b5 in 2014 with relatively
minor issues. When I started what I thought would be an even less
stressful
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
