Hello Alexei,
here's a short how I do it:
1.) clone stable git head, like current for 3.4, into its specific
directory: git clone --branch james-project-3.4.0
https://github.com/apache/james-project.git james-3.4.0
2.) build it but skipping tests (cause some fail and it saves a lot of
time - they're not needed for just use it): mvn -DskipTests package
2.) a) maybe a maven version related issue on my side - but I got an
issue about "--parameter" not a valid parameter for the java compiler -
but if you also get this error (pretty early on) make sure to use a Java
9+ compiler or an older maven
2.) b) you can try to run James 3.4 with Java 9+, but if I remember
correctly someone told me that Java 3.3 is still to be run with only
Java 8 - I don't know about James 3.4
2.) c) you may hit the limit for open files - in that case increase the
limits and re-log
3.) after successful compiling and packaging you'll find the non-docker
server in <path to local cloned git
repo>/server/app/target/james-server-app-3.4.0-app.tar.gz (or .zip -
don't know why it's packaged into two different package styles - as on
unix .tar.gz is common - guess the .zip is for any of those not so
familiar with .tar.gz (windows users?)) - just copy this one to to
folder you want your James to be "installed" and unpack it (I just
copied und unpacked it in user home)
4.) you should have a look at some of the config files: some are quite
important, some are just to "fancy up" your James, it depends on how you
want to run your James (as an example: as I use MariaDB I had to manual
add its driver to the <path-to-james>/conf/lib folder and set database
access credentials (and type) in
<path-to-james>/conf/james-database.properties - also I edit some other
settings)
5.) after all configs are the way you like them just start james as root
(required for at least TCP/25 to receive mails from other MTAs) by:
<path-to-james>/bin/james start
5.) a) if you encounter issues you can either have a look at the log
<path-to-james>/log/wrapper.log - or run James in an interactive console
style: <path-to-james>/bin/james console
6.) after the server start up successful you have to add at least one
domain: <path-to-james>/bin/james-cli.sh -h localhost AddDomain
your-domain.example
7.) after you added your domain you should at least add a postmaster
user: <path-to-james>/bin/james-cli.sh -h localhost AddUser
postmaster@your-domain.example securepassword
That's pretty much it. Hope it helps you to get James running in
non-docker mode. If you need help with the configs just go them through
step by step, they're well documented. I would recommend to at least
enable SMTP AUTH (and disable the default access control as it's
explained by the docs) to prevent your server become an open relay.
greetings from Germany,
Matt
Hello,
I've wanted to try James without docker but the link
"https://james.apache.org/install.html"; from James main site
("https://james.apache.org/";) points to an invalid page (404 Not found).
Could you please point to a correct place with the instruction?
The broken link is located in the section "Get Started With James" -
"ALTERNATIVES" on https://james.apache.org/
Best regards,
Alexei Osipov.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
