JWM wrote:
Stefano,
The domain in question is: brandilyncollins.com
# host -t mx brandilyncollins.com
brandilyncollins.com mail is handled by 0 mxmail.register.com.
# host -t a mxmail.register.com.
mxmail.register.com is an alias for rcom-outblaze-com.mr.outblaze.com.
rcom-outblaze-com.mr.out
When can we see release 2.3.0 going live?
Regards,
Pierre
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
How do I change the jmx provider so that I can connect from different IP's?
Pierre
Stefano Bagnara wrote:
However, when I connect to 10.0.0.4:8082 with my browser I
get a connection refused.
By default James JMX accept only connections from 127.0.0.1.
Just run a local browser and use 12
How do I change the jmx provider so that I can connect from different IP's?
Stefano Bagnara wrote:
However, when I connect to 10.0.0.4:8082 with my browser I
get a connection refused.
By default James JMX accept only connections from 127.0.0.1.
Just run a local browser and use 127.0.0.1:
To my understanding the patch
(http://issues.apache.org/jira/browse/JAMES-426) works fine against a
jdbc connected VirtualUserTable. Daniel points out that it should also
connect to stores as xmlVirtualUserTable and others. I agree to that.
But such could be road mapped.
However it will not
Is it possible to release on a more scheduled basis, e.g. quarterly or so?
This would show that James isn't dead and thus would attract more users,
testers, documentalist and so on.
Regards,
Pierre
-
To unsubscribe, e-mail:
Stefano,
I really appreciate your help in this ordeal.
I copied your response to Register. According them, RFCs are now simply
'suggestions'... Is that true? I thought they were already mandatory.
The one thing that is still nagging at me is the fact that James is widely
used, and Register.co
