> Yes, I run James as root; but only because I couldn't find an easy way
> to run it as anything else. I did look at other options but it didn't
What's so hard at running James as non-root? The only 'problem' is that you
cannot bind to port 25 but that can be easily solved by running James on port
2525 (or any other post > 1024) and using iptables to map port 25 to 2525.
Regards,
Martijn Brinkers
On Tue, 2008-10-14 at 15:42 +0100, David Legg wrote:
> Hi Ebe,
>
> > Is it ok to run James as root? Should I create a specific user for James?
> > How should the directory rights be set? Should I use a chroot-environment,
> > if yes, how?
> > How can I install James as service, where should log files go, ....
> >
>
> I installed James as a service on an Ubuntu server by creating a new
> file called 'james' in the /etc/init.d directory which looks as follows: -
>
> #!/bin/sh
> #
> # Set the environment - this is crucial... it doesn't exist at boot time.
> export JAVA_HOME=/usr/local/java
>
> case "$1" in
> 'start')
> echo "Starting James Mail Server: "
> /usr/local/james/bin/phoenix.sh start
> ;;
> 'stop')
> echo "Stopping James Mail Server: "
> /usr/local/james/bin/phoenix.sh stop
> ;;
> 'restart')
> echo "Restarting James Mail Server: "
> /usr/local/james/bin/phoenix.sh restart
> ;;
> *)
> echo "Usage: $0 { start | stop | restart }"
> ;;
> esac
> exit 0
>
>
> Once you have done that execute the following commands as root: -
>
> # chmod +x /etc/init.d/james
> # update-rc.d james defaults 20 80
> Adding system startup for /etc/init.d/james ...
> /etc/rc0.d/K80james -> ../init.d/james
> /etc/rc1.d/K80james -> ../init.d/james
> /etc/rc6.d/K80james -> ../init.d/james
> /etc/rc2.d/S20james -> ../init.d/james
> /etc/rc3.d/S20james -> ../init.d/james
> /etc/rc4.d/S20james -> ../init.d/james
> /etc/rc5.d/S20james -> ../init.d/james
>
>
> Assuming you installed James in /usr/local/james you should find all the
> log files get stored in /usr/local/james/apps/james/logs
>
> Yes, I run James as root; but only because I couldn't find an easy way
> to run it as anything else. I did look at other options but it didn't
> look easy. I do of course run iptables as a firewall to only expose
> essential ports like 25 and 110.
>
> Hope that helps.
>
> Regards,
> David Legg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
