mirror of
https://github.com/mjl-/mox.git
synced 2025-07-10 06:34:40 +03:00
change mox to start as root, bind to network sockets, then drop to regular unprivileged mox user
makes it easier to run on bsd's, where you cannot (easily?) let non-root users bind to ports <1024. starting as root also paves the way for future improvements with privilege separation. unfortunately, this requires changes to how you start mox. though mox will help by automatically fix up dir/file permissions/ownership. if you start mox from the systemd unit file, you should update it so it starts as root and adds a few additional capabilities: # first update the mox binary, then, as root: ./mox config printservice >mox.service systemctl daemon-reload systemctl restart mox journalctl -f -u mox & # you should see mox start up, with messages about fixing permissions on dirs/files. if you used the recommended config/ and data/ directory, in a directory just for mox, and with the mox user called "mox", this should be enough. if you don't want mox to modify dir/file permissions, set "NoFixPermissions: true" in mox.conf. if you named the mox user something else than mox, e.g. "_mox", add "User: _mox" to mox.conf. if you created a shared service user as originally suggested, you may want to get rid of that as it is no longer useful and may get in the way. e.g. if you had /home/service/mox with a "service" user, that service user can no longer access any files: only mox and root can. this also adds scripts for building mox docker images for alpine-supported platforms. the "restart" subcommand has been removed. it wasn't all that useful and got in the way. and another change: when adding a domain while mtasts isn't enabled, don't add the per-domain mtasts config, as it would cause failure to add the domain. based on report from setting up mox on openbsd from mteege. and based on issue #3. thanks for the feedback!
This commit is contained in:
38
doc.go
38
doc.go
@ -14,8 +14,7 @@ low-maintenance self-hosted email.
|
||||
|
||||
mox [-config config/mox.conf] ...
|
||||
mox serve
|
||||
mox quickstart user@domain
|
||||
mox restart
|
||||
mox quickstart user@domain [user | uid]
|
||||
mox stop
|
||||
mox setaccountpassword address
|
||||
mox setadminpassword
|
||||
@ -41,6 +40,7 @@ low-maintenance self-hosted email.
|
||||
mox config domain add domain account [localpart]
|
||||
mox config domain rm domain
|
||||
mox config describe-sendmail >/etc/moxsubmit.conf
|
||||
mox config printservice >mox.service
|
||||
mox checkupdate
|
||||
mox cid cid
|
||||
mox clientconfig domain
|
||||
@ -83,26 +83,14 @@ requested, other TLS certificates are requested on demand.
|
||||
|
||||
Quickstart generates configuration files and prints instructions to quickly set up a mox instance.
|
||||
|
||||
Quickstart prints initial admin and account passwords, configuration files, DNS
|
||||
records you should create, instructions for setting correct user/group and
|
||||
permissions, and if you run it on Linux it prints a systemd service file.
|
||||
Quickstart writes configuration files, prints initial admin and account
|
||||
passwords, DNS records you should create. If you run it on Linux it writes a
|
||||
systemd service file and prints commands to enable and start mox as service.
|
||||
|
||||
usage: mox quickstart user@domain
|
||||
The user or uid is optional, defaults to "mox", and is the user or uid/gid mox
|
||||
will run as after initialization.
|
||||
|
||||
# mox restart
|
||||
|
||||
Restart mox after validating the configuration file.
|
||||
|
||||
Restart execs the mox binary, which have been updated. Restart returns after
|
||||
the restart has finished. If you update the mox binary, keep in mind that the
|
||||
validation of the configuration file is done by the old process with the old
|
||||
binary. The new binary may report a syntax error. If you update the binary, you
|
||||
should use the "config test" command with the new binary to validate the
|
||||
configuration file.
|
||||
|
||||
Like stop, existing connections get a 3 second period for graceful shutdown.
|
||||
|
||||
usage: mox restart
|
||||
usage: mox quickstart user@domain [user | uid]
|
||||
|
||||
# mox stop
|
||||
|
||||
@ -390,6 +378,16 @@ Describe configuration for mox when invoked as sendmail.
|
||||
|
||||
usage: mox config describe-sendmail >/etc/moxsubmit.conf
|
||||
|
||||
# mox config printservice
|
||||
|
||||
Prints a systemd unit service file for mox.
|
||||
|
||||
This is the same file as generated using quickstart. If the systemd service file
|
||||
has changed with a newer version of mox, use this command to generate an up to
|
||||
date version.
|
||||
|
||||
usage: mox config printservice >mox.service
|
||||
|
||||
# mox checkupdate
|
||||
|
||||
Check if a newer version of mox is available.
|
||||
|
Reference in New Issue
Block a user