2023-01-30 16:27:06 +03:00
package main
import (
"context"
cryptorand "crypto/rand"
"fmt"
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!
2023-02-27 14:19:55 +03:00
"io/fs"
2023-01-30 16:27:06 +03:00
"net"
"os"
"os/signal"
"path/filepath"
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!
2023-02-27 14:19:55 +03:00
"runtime"
2023-01-30 16:27:06 +03:00
"runtime/debug"
"strings"
"sync"
"syscall"
"time"
"github.com/prometheus/client_golang/prometheus"
"github.com/prometheus/client_golang/prometheus/promauto"
2023-02-27 16:12:58 +03:00
"github.com/mjl-/mox/dmarcdb"
2023-01-30 16:27:06 +03:00
"github.com/mjl-/mox/dns"
"github.com/mjl-/mox/dnsbl"
2023-02-27 16:12:58 +03:00
"github.com/mjl-/mox/http"
"github.com/mjl-/mox/imapserver"
2023-01-30 16:27:06 +03:00
"github.com/mjl-/mox/message"
"github.com/mjl-/mox/metrics"
"github.com/mjl-/mox/mlog"
"github.com/mjl-/mox/mox-"
"github.com/mjl-/mox/moxvar"
2023-02-27 16:12:58 +03:00
"github.com/mjl-/mox/mtastsdb"
"github.com/mjl-/mox/queue"
"github.com/mjl-/mox/smtpserver"
2023-01-30 16:27:06 +03:00
"github.com/mjl-/mox/store"
2023-02-27 16:12:58 +03:00
"github.com/mjl-/mox/tlsrptdb"
2023-01-30 16:27:06 +03:00
"github.com/mjl-/mox/updates"
)
func monitorDNSBL ( log * mlog . Log ) {
defer func ( ) {
// On error, don't bring down the entire server.
x := recover ( )
if x != nil {
log . Error ( "monitordnsbl panic" , mlog . Field ( "panic" , x ) )
debug . PrintStack ( )
metrics . PanicInc ( "serve" )
}
} ( )
l , ok := mox . Conf . Static . Listeners [ "public" ]
if ! ok {
log . Info ( "no listener named public, not monitoring our ips at dnsbls" )
return
}
var zones [ ] dns . Domain
for _ , zone := range l . SMTP . DNSBLs {
d , err := dns . ParseDomain ( zone )
if err != nil {
log . Fatalx ( "parsing dnsbls zone" , err , mlog . Field ( "zone" , zone ) )
}
zones = append ( zones , d )
}
if len ( zones ) == 0 {
return
}
type key struct {
zone dns . Domain
ip string
}
metrics := map [ key ] prometheus . GaugeFunc { }
var statusMutex sync . Mutex
statuses := map [ key ] bool { }
resolver := dns . StrictResolver { Pkg : "dnsblmonitor" }
var sleep time . Duration // No sleep on first iteration.
for {
time . Sleep ( sleep )
sleep = 3 * time . Hour
new feature: when delivering messages from the queue, make it possible to use a "transport"
the default transport is still just "direct delivery", where we connect to the
destination domain's MX servers.
other transports are:
- regular smtp without authentication, this is relaying to a smarthost.
- submission with authentication, e.g. to a third party email sending service.
- direct delivery, but with with connections going through a socks proxy. this
can be helpful if your ip is blocked, you need to get email out, and you have
another IP that isn't blocked.
keep in mind that for all of the above, appropriate SPF/DKIM settings have to
be configured. the "dnscheck" for a domain does a check for any SOCKS IP in the
SPF record. SPF for smtp/submission (ranges? includes?) and any DKIM
requirements cannot really be checked.
which transport is used can be configured through routes. routes can be set on
an account, a domain, or globally. the routes are evaluated in that order, with
the first match selecting the transport. these routes are evaluated for each
delivery attempt. common selection criteria are recipient domain and sender
domain, but also which delivery attempt this is. you could configured mox to
attempt sending through a 3rd party from the 4th attempt onwards.
routes and transports are optional. if no route matches, or an empty/zero
transport is selected, normal direct delivery is done.
we could already "submit" emails with 3rd party accounts with "sendmail". but
we now support more SASL authentication mechanisms with SMTP (not only PLAIN,
but also SCRAM-SHA-256, SCRAM-SHA-1 and CRAM-MD5), which sendmail now also
supports. sendmail will use the most secure mechanism supported by the server,
or the explicitly configured mechanism.
for issue #36 by dmikushin. also based on earlier discussion on hackernews.
2023-06-16 19:38:28 +03:00
ips , err := mox . IPs ( mox . Context , false )
2023-01-30 16:27:06 +03:00
if err != nil {
log . Errorx ( "listing ips for dnsbl monitor" , err )
continue
}
for _ , ip := range ips {
if ip . IsLoopback ( ) || ip . IsPrivate ( ) {
continue
}
for _ , zone := range zones {
status , expl , err := dnsbl . Lookup ( mox . Context , resolver , zone , ip )
if err != nil {
log . Errorx ( "dnsbl monitor lookup" , err , mlog . Field ( "ip" , ip ) , mlog . Field ( "zone" , zone ) , mlog . Field ( "expl" , expl ) , mlog . Field ( "status" , status ) )
}
k := key { zone , ip . String ( ) }
statusMutex . Lock ( )
statuses [ k ] = status == dnsbl . StatusPass
statusMutex . Unlock ( )
if _ , ok := metrics [ k ] ; ! ok {
metrics [ k ] = promauto . NewGaugeFunc (
prometheus . GaugeOpts {
Name : "mox_dnsbl_ips_success" ,
Help : "DNSBL lookups to configured DNSBLs of our IPs." ,
ConstLabels : prometheus . Labels {
2023-03-09 22:18:34 +03:00
"zone" : zone . LogString ( ) ,
2023-01-30 16:27:06 +03:00
"ip" : k . ip ,
} ,
} ,
func ( ) float64 {
statusMutex . Lock ( )
defer statusMutex . Unlock ( )
if statuses [ k ] {
return 1
}
return 0
} ,
)
}
time . Sleep ( time . Second )
}
}
}
}
2023-03-12 12:38:02 +03:00
// also see localserve.go, code is similar or even shared.
2023-01-30 16:27:06 +03:00
func cmdServe ( c * cmd ) {
c . help = ` Start mox , serving SMTP / IMAP / HTTPS .
Incoming email is accepted over SMTP . Email can be retrieved by users using
IMAP . HTTP listeners are started for the admin / account web interfaces , and for
automated TLS configuration . Missing essential TLS certificates are immediately
requested , other TLS certificates are requested on demand .
`
args := c . Parse ( )
if len ( args ) != 0 {
c . Usage ( )
}
2023-03-01 00:12:27 +03:00
// Set debug logging until config is fully loaded.
2023-01-30 16:27:06 +03:00
mlog . Logfmt = true
2023-03-01 00:12:27 +03:00
mox . Conf . Log [ "" ] = mlog . LevelDebug
mlog . SetConfig ( mox . Conf . Log )
2023-03-06 01:56:02 +03:00
checkACMEHosts := os . Getuid ( ) != 0
2023-03-01 00:12:27 +03:00
2023-01-30 16:27:06 +03:00
log := mlog . New ( "serve" )
if os . Getuid ( ) == 0 {
2023-06-16 14:27:27 +03:00
mox . MustLoadConfig ( true , checkACMEHosts )
2023-05-31 15:09:53 +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!
2023-02-27 14:19:55 +03:00
// No need to potentially start and keep multiple processes. As root, we just need
// to start the child process.
runtime . GOMAXPROCS ( 1 )
2023-01-30 16:27:06 +03:00
2023-07-02 15:46:20 +03:00
moxconf , err := filepath . Abs ( mox . ConfigStaticPath )
log . Check ( err , "finding absolute mox.conf path" )
domainsconf , err := filepath . Abs ( mox . ConfigDynamicPath )
log . Check ( err , "finding absolute domains.conf path" )
log . Print ( "starting as root, initializing network listeners" , mlog . Field ( "version" , moxvar . Version ) , mlog . Field ( "pid" , os . Getpid ( ) ) , mlog . Field ( "moxconf" , moxconf ) , mlog . Field ( "domainsconf" , domainsconf ) )
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!
2023-02-27 14:19:55 +03:00
if os . Getenv ( "MOX_SOCKETS" ) != "" {
log . Fatal ( "refusing to start as root with $MOX_SOCKETS set" )
2023-01-30 16:27:06 +03:00
}
2023-05-31 15:09:53 +03:00
if os . Getenv ( "MOX_FILES" ) != "" {
log . Fatal ( "refusing to start as root with $MOX_FILES set" )
}
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!
2023-02-27 14:19:55 +03:00
if ! mox . Conf . Static . NoFixPermissions {
// Fix permissions now that we have privilege to do so. Useful for update of v0.0.1
// that was running directly as mox-user.
workdir , err := os . Getwd ( )
if err != nil {
log . Printx ( "get working dir, continuing without potentially fixing up permissions" , err )
} else {
configdir := filepath . Dir ( mox . ConfigStaticPath )
datadir := mox . DataDirPath ( "." )
err := fixperms ( log , workdir , configdir , datadir , mox . Conf . Static . UID , mox . Conf . Static . GID )
if err != nil {
log . Fatalx ( "fixing permissions" , err )
}
}
2023-01-30 16:27:06 +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!
2023-02-27 14:19:55 +03:00
} else {
2023-05-31 15:09:53 +03:00
mox . RestorePassedFiles ( )
2023-06-16 14:27:27 +03:00
mox . MustLoadConfig ( true , checkACMEHosts )
2023-07-19 12:32:19 +03:00
log . Print ( "starting as unprivileged user" , mlog . Field ( "user" , mox . Conf . Static . User ) , mlog . Field ( "uid" , mox . Conf . Static . UID ) , mlog . Field ( "gid" , mox . Conf . Static . GID ) , mlog . Field ( "pid" , os . Getpid ( ) ) )
2023-01-30 16:27:06 +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!
2023-02-27 14:19:55 +03:00
syscall . Umask ( syscall . Umask ( 007 ) | 007 )
2023-01-30 16:27:06 +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!
2023-02-27 14:19:55 +03:00
// Initialize key and random buffer for creating opaque SMTP
// transaction IDs based on "cid"s.
recvidpath := mox . DataDirPath ( "receivedid.key" )
recvidbuf , err := os . ReadFile ( recvidpath )
if err != nil || len ( recvidbuf ) != 16 + 8 {
recvidbuf = make ( [ ] byte , 16 + 8 )
if _ , err := cryptorand . Read ( recvidbuf ) ; err != nil {
log . Fatalx ( "reading random recvid data" , err )
2023-01-30 16:27:06 +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!
2023-02-27 14:19:55 +03:00
if err := os . WriteFile ( recvidpath , recvidbuf , 0660 ) ; err != nil {
log . Fatalx ( "writing recvidpath" , err , mlog . Field ( "path" , recvidpath ) )
}
err := os . Chown ( recvidpath , int ( mox . Conf . Static . UID ) , 0 )
log . Check ( err , "chown receveidid.key" , mlog . Field ( "path" , recvidpath ) , mlog . Field ( "uid" , mox . Conf . Static . UID ) , mlog . Field ( "gid" , 0 ) )
err = os . Chmod ( recvidpath , 0640 )
log . Check ( err , "chmod receveidid.key to 0640" , mlog . Field ( "path" , recvidpath ) )
}
if err := mox . ReceivedIDInit ( recvidbuf [ : 16 ] , recvidbuf [ 16 : ] ) ; err != nil {
log . Fatalx ( "init receivedid" , err )
2023-01-30 16:27:06 +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!
2023-02-27 14:19:55 +03:00
// Start mox. If running as root, this will bind/listen on network sockets, and
// fork and exec itself as unprivileged user, then waits for the child to stop and
// exit. When running as root, this function never returns. But the new
// unprivileged user will get here again, with network sockets prepared.
//
// We listen to the unix domain ctl socket afterwards, which we always remove
// before listening. We need to do that because we may not have cleaned up our
// control socket during unexpected shutdown. We don't want to remove and listen on
// the unix domain socket first. If we would, we would make the existing instance
// unreachable over its ctl socket, and then fail because the network addresses are
// taken.
const mtastsdbRefresher = true
const skipForkExec = false
if err := start ( mtastsdbRefresher , skipForkExec ) ; err != nil {
log . Fatalx ( "start" , err )
2023-01-30 16:27:06 +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!
2023-02-27 14:19:55 +03:00
log . Print ( "ready to serve" )
2023-01-30 16:27:06 +03:00
if mox . Conf . Static . CheckUpdates {
2023-01-31 02:16:01 +03:00
checkUpdates := func ( ) time . Duration {
next := 24 * time . Hour
2023-01-30 16:27:06 +03:00
current , lastknown , mtime , err := mox . LastKnown ( )
if err != nil {
2023-01-31 02:16:01 +03:00
log . Infox ( "determining own version before checking for updates, trying again in 24h" , err )
return next
2023-01-30 16:27:06 +03:00
}
2023-01-31 02:16:01 +03:00
// We don't want to check for updates at every startup. So we sleep based on file
// mtime. But file won't exist initially.
2023-01-30 16:27:06 +03:00
if ! mtime . IsZero ( ) && time . Since ( mtime ) < 24 * time . Hour {
2023-01-31 02:16:01 +03:00
d := 24 * time . Hour - time . Since ( mtime )
log . Debug ( "sleeping for next check for updates" , mlog . Field ( "sleep" , d ) )
time . Sleep ( d )
next = 0
2023-01-30 16:27:06 +03:00
}
now := time . Now ( )
if err := os . Chtimes ( mox . DataDirPath ( "lastknownversion" ) , now , now ) ; err != nil {
2023-01-31 02:16:01 +03:00
if ! os . IsNotExist ( err ) {
log . Infox ( "setting mtime on lastknownversion file, continuing" , err )
}
2023-01-30 16:27:06 +03:00
}
2023-01-31 02:16:01 +03:00
2023-01-30 16:27:06 +03:00
log . Debug ( "checking for updates" , mlog . Field ( "lastknown" , lastknown ) )
updatesctx , updatescancel := context . WithTimeout ( mox . Context , time . Minute )
latest , _ , changelog , err := updates . Check ( updatesctx , dns . StrictResolver { } , dns . Domain { ASCII : changelogDomain } , lastknown , changelogURL , changelogPubKey )
updatescancel ( )
if err != nil {
log . Infox ( "checking for updates" , err , mlog . Field ( "latest" , latest ) )
2023-01-31 02:16:01 +03:00
return next
2023-01-30 16:27:06 +03:00
}
if ! latest . After ( lastknown ) {
log . Debug ( "no new version available" )
2023-01-31 02:16:01 +03:00
return next
2023-01-30 16:27:06 +03:00
}
if len ( changelog . Changes ) == 0 {
log . Info ( "new version available, but changelog is empty, ignoring" , mlog . Field ( "latest" , latest ) )
2023-01-31 02:16:01 +03:00
return next
2023-01-30 16:27:06 +03:00
}
var cl string
2023-02-17 22:14:26 +03:00
for _ , c := range changelog . Changes {
2023-06-28 20:55:31 +03:00
cl += "----\n\n" + strings . TrimSpace ( c . Text ) + "\n\n"
2023-01-30 16:27:06 +03:00
}
2023-03-06 01:15:34 +03:00
cl += "----"
2023-01-30 16:27:06 +03:00
a , err := store . OpenAccount ( mox . Conf . Static . Postmaster . Account )
if err != nil {
log . Infox ( "open account for postmaster changelog delivery" , err )
2023-01-31 02:16:01 +03:00
return next
2023-01-30 16:27:06 +03:00
}
2023-02-16 15:22:00 +03:00
defer func ( ) {
err := a . Close ( )
log . Check ( err , "closing account" )
} ( )
2023-01-30 16:27:06 +03:00
f , err := store . CreateMessageTemp ( "changelog" )
if err != nil {
log . Infox ( "making temporary message file for changelog delivery" , err )
2023-01-31 02:16:01 +03:00
return next
2023-01-30 16:27:06 +03:00
}
2023-03-06 01:15:34 +03:00
defer func ( ) {
if f != nil {
err := os . Remove ( f . Name ( ) )
log . Check ( err , "removing temp changelog file" )
err = f . Close ( )
log . Check ( err , "closing temp changelog file" )
}
} ( )
2023-07-24 22:21:05 +03:00
m := & store . Message {
Received : time . Now ( ) ,
Flags : store . Flags { Flagged : true } ,
}
2023-07-25 09:24:05 +03:00
n , err := fmt . Fprintf ( f , "Date: %s\r\nSubject: mox %s available\r\nContent-Type: text/plain; charset=utf-8\r\nContent-Transfer-Encoding: 8-bit\r\n\r\nHi!\r\n\r\nVersion %s of mox is available, this install is at %s.\r\n\r\nChanges:\r\n\r\n%s\r\n\r\nRemember to make a backup with \"mox backup\" before upgrading.\r\nPlease report any issues at https://github.com/mjl-/mox, thanks!\r\n\r\nCheers,\r\nmox\r\n" , time . Now ( ) . Format ( message . RFC5322Z ) , latest , latest , current , strings . ReplaceAll ( cl , "\n" , "\r\n" ) )
2023-01-30 16:27:06 +03:00
if err != nil {
log . Infox ( "writing temporary message file for changelog delivery" , err )
2023-01-31 02:16:01 +03:00
return next
2023-01-30 16:27:06 +03:00
}
m . Size = int64 ( n )
if err := a . DeliverMailbox ( log , mox . Conf . Static . Postmaster . Mailbox , m , f , true ) ; err != nil {
2023-03-06 01:15:34 +03:00
log . Errorx ( "changelog delivery" , err )
return next
2023-01-30 16:27:06 +03:00
}
2023-03-06 01:15:34 +03:00
f = nil
2023-01-30 16:27:06 +03:00
log . Info ( "delivered changelog" , mlog . Field ( "current" , current ) , mlog . Field ( "lastknown" , lastknown ) , mlog . Field ( "latest" , latest ) )
if err := mox . StoreLastKnown ( latest ) ; err != nil {
// This will be awkward, we'll keep notifying the postmaster once every 24h...
log . Infox ( "updating last known version" , err )
}
2023-01-31 02:16:01 +03:00
return next
2023-01-30 16:27:06 +03:00
}
go func ( ) {
for {
2023-01-31 02:16:01 +03:00
next := checkUpdates ( )
time . Sleep ( next )
2023-01-30 16:27:06 +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!
2023-02-27 14:19:55 +03:00
go monitorDNSBL ( log )
2023-01-30 16:27:06 +03:00
ctlpath := mox . DataDirPath ( "ctl" )
2023-02-16 15:22:00 +03:00
_ = os . Remove ( ctlpath )
2023-01-30 16:27:06 +03:00
ctl , err := net . Listen ( "unix" , ctlpath )
if err != nil {
log . Fatalx ( "listen on ctl unix domain socket" , err )
}
go func ( ) {
for {
conn , err := ctl . Accept ( )
if err != nil {
log . Printx ( "accept for ctl" , err )
continue
}
cid := mox . Cid ( )
ctx := context . WithValue ( mox . Context , mlog . CidKey , cid )
2023-03-12 12:38:02 +03:00
go servectl ( ctx , log . WithCid ( cid ) , conn , func ( ) { shutdown ( log ) } )
2023-01-30 16:27:06 +03:00
}
} ( )
// Remove old temporary files that somehow haven't been cleaned up.
tmpdir := mox . DataDirPath ( "tmp" )
os . MkdirAll ( tmpdir , 0770 )
tmps , err := os . ReadDir ( tmpdir )
if err != nil {
log . Errorx ( "listing files in tmpdir" , err )
} else {
now := time . Now ( )
for _ , e := range tmps {
if fi , err := e . Info ( ) ; err != nil {
log . Errorx ( "stat tmp file" , err , mlog . Field ( "filename" , e . Name ( ) ) )
} else if now . Sub ( fi . ModTime ( ) ) > 7 * 24 * time . Hour {
p := filepath . Join ( tmpdir , e . Name ( ) )
if err := os . Remove ( p ) ; err != nil {
log . Errorx ( "removing stale temporary file" , err , mlog . Field ( "path" , p ) )
} else {
log . Info ( "removed stale temporary file" , mlog . Field ( "path" , p ) )
}
}
}
}
// Graceful shutdown.
sigc := make ( chan os . Signal , 1 )
signal . Notify ( sigc , os . Interrupt , syscall . SIGTERM )
sig := <- sigc
log . Print ( "shutting down, waiting max 3s for existing connections" , mlog . Field ( "signal" , sig ) )
2023-03-12 12:38:02 +03:00
shutdown ( log )
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!
2023-02-27 14:19:55 +03:00
if num , ok := sig . ( syscall . Signal ) ; ok {
os . Exit ( int ( num ) )
} else {
os . Exit ( 1 )
}
}
2023-03-12 12:38:02 +03:00
func shutdown ( log * mlog . Log ) {
// We indicate we are shutting down. Causes new connections and new SMTP commands
// to be rejected. Should stop active connections pretty quickly.
mox . ShutdownCancel ( )
// Now we are going to wait for all connections to be gone, up to a timeout.
done := mox . Connections . Done ( )
second := time . Tick ( time . Second )
select {
case <- done :
log . Print ( "connections shutdown, waiting until 1 second passed" )
<- second
case <- time . Tick ( 3 * time . Second ) :
// We now cancel all pending operations, and set an immediate deadline on sockets.
// Should get us a clean shutdown relatively quickly.
mox . ContextCancel ( )
mox . Connections . Shutdown ( )
second := time . Tick ( time . Second )
select {
case <- done :
log . Print ( "no more connections, shutdown is clean, waiting until 1 second passed" )
<- second // Still wait for second, giving processes like imports a chance to clean up.
case <- second :
log . Print ( "shutting down with pending sockets" )
}
}
err := os . Remove ( mox . DataDirPath ( "ctl" ) )
log . Check ( err , "removing ctl unix domain socket during shutdown" )
}
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!
2023-02-27 14:19:55 +03:00
// Set correct permissions for mox working directory, binary, config and data and service file.
//
// We require being able to stat the basic non-optional paths. Then we'll try to
// fix up permissions. If an error occurs when fixing permissions, we log and
// continue (could not be an actual problem).
func fixperms ( log * mlog . Log , workdir , configdir , datadir string , moxuid , moxgid uint32 ) ( rerr error ) {
type fserr struct { Err error }
defer func ( ) {
x := recover ( )
if x == nil {
return
}
e , ok := x . ( fserr )
if ok {
rerr = e . Err
} else {
panic ( x )
}
} ( )
checkf := func ( err error , format string , args ... any ) {
if err != nil {
panic ( fserr { fmt . Errorf ( format , args ... ) } )
}
}
// Changes we have to make. We collect them first, then apply.
type change struct {
path string
uid , gid * uint32
olduid , oldgid uint32
mode * fs . FileMode
oldmode fs . FileMode
}
var changes [ ] change
ensure := func ( p string , uid , gid uint32 , perm fs . FileMode ) bool {
fi , err := os . Stat ( p )
checkf ( err , "stat %s" , p )
st , ok := fi . Sys ( ) . ( * syscall . Stat_t )
if ! ok {
checkf ( fmt . Errorf ( "got %T" , st ) , "stat sys, expected syscall.Stat_t" )
}
var ch change
if st . Uid != uid || st . Gid != gid {
ch . uid = & uid
ch . gid = & gid
ch . olduid = st . Uid
ch . oldgid = st . Gid
}
if perm != fi . Mode ( ) & ( fs . ModeSetgid | 0777 ) {
ch . mode = & perm
ch . oldmode = fi . Mode ( ) & ( fs . ModeSetgid | 0777 )
}
var zerochange change
if ch == zerochange {
return false
}
ch . path = p
changes = append ( changes , ch )
return true
}
xexists := func ( p string ) bool {
_ , err := os . Stat ( p )
if err != nil && ! os . IsNotExist ( err ) {
checkf ( err , "stat %s" , p )
}
return err == nil
}
// We ensure these permissions:
//
// $workdir root:mox 0751
// $configdir mox:root 0750 + setgid, and recursively (but files 0640)
// $datadir mox:root 0750 + setgid, and recursively (but files 0640)
// $workdir/mox (binary, optional) root:mox 0750
// $workdir/mox.service (systemd service file, optional) root:root 0644
const root = 0
ensure ( workdir , root , moxgid , 0751 )
fixconfig := ensure ( configdir , moxuid , 0 , fs . ModeSetgid | 0750 )
fixdata := ensure ( datadir , moxuid , 0 , fs . ModeSetgid | 0750 )
// Binary and systemd service file do not exist (there) when running under docker.
binary := filepath . Join ( workdir , "mox" )
if xexists ( binary ) {
ensure ( binary , root , moxgid , 0750 )
}
svc := filepath . Join ( workdir , "mox.service" )
if xexists ( svc ) {
ensure ( svc , root , root , 0644 )
}
if len ( changes ) == 0 {
return
}
// Apply changes.
log . Print ( "fixing up permissions, will continue on errors" )
for _ , ch := range changes {
if ch . uid != nil {
err := os . Chown ( ch . path , int ( * ch . uid ) , int ( * ch . gid ) )
log . Printx ( "chown, fixing uid/gid" , err , mlog . Field ( "path" , ch . path ) , mlog . Field ( "olduid" , ch . olduid ) , mlog . Field ( "oldgid" , ch . oldgid ) , mlog . Field ( "newuid" , * ch . uid ) , mlog . Field ( "newgid" , * ch . gid ) )
}
if ch . mode != nil {
err := os . Chmod ( ch . path , * ch . mode )
log . Printx ( "chmod, fixing permissions" , err , mlog . Field ( "path" , ch . path ) , mlog . Field ( "oldmode" , fmt . Sprintf ( "%03o" , ch . oldmode ) ) , mlog . Field ( "newmode" , fmt . Sprintf ( "%03o" , * ch . mode ) ) )
}
}
walkchange := func ( dir string ) {
err := filepath . WalkDir ( dir , func ( path string , d fs . DirEntry , err error ) error {
if err != nil {
log . Printx ( "walk error, continuing" , err , mlog . Field ( "path" , path ) )
return nil
}
fi , err := d . Info ( )
if err != nil {
log . Printx ( "stat during walk, continuing" , err , mlog . Field ( "path" , path ) )
return nil
}
st , ok := fi . Sys ( ) . ( * syscall . Stat_t )
if ! ok {
log . Printx ( "syscall stat during walk, continuing" , err , mlog . Field ( "path" , path ) )
return nil
}
if st . Uid != moxuid || st . Gid != root {
err := os . Chown ( path , int ( moxuid ) , root )
log . Printx ( "walk chown, fixing uid/gid" , err , mlog . Field ( "path" , path ) , mlog . Field ( "olduid" , st . Uid ) , mlog . Field ( "oldgid" , st . Gid ) , mlog . Field ( "newuid" , moxuid ) , mlog . Field ( "newgid" , root ) )
}
omode := fi . Mode ( ) & ( fs . ModeSetgid | 0777 )
var nmode fs . FileMode
if fi . IsDir ( ) {
nmode = fs . ModeSetgid | 0750
} else {
nmode = 0640
}
if omode != nmode {
err := os . Chmod ( path , nmode )
log . Printx ( "walk chmod, fixing permissions" , err , mlog . Field ( "path" , path ) , mlog . Field ( "oldmode" , fmt . Sprintf ( "%03o" , omode ) ) , mlog . Field ( "newmode" , fmt . Sprintf ( "%03o" , nmode ) ) )
}
return nil
} )
log . Check ( err , "walking dir to fix permissions" , mlog . Field ( "dir" , dir ) )
}
// If config or data dir needed fixing, also set uid/gid and mode and files/dirs
// inside, recursively. We don't always recurse, data probably contains many files.
if fixconfig {
log . Print ( "fixing permissions in config dir" , mlog . Field ( "configdir" , configdir ) )
walkchange ( configdir )
}
if fixdata {
log . Print ( "fixing permissions in data dir" , mlog . Field ( "configdir" , configdir ) )
walkchange ( datadir )
}
return nil
2023-01-30 16:27:06 +03:00
}
2023-02-27 16:12:58 +03:00
// start initializes all packages, starts all listeners and the switchboard
// goroutine, then returns.
func start ( mtastsdbRefresher , skipForkExec bool ) error {
smtpserver . Listen ( )
imapserver . Listen ( )
http . Listen ( )
if ! skipForkExec {
// If we were just launched as root, fork and exec as unprivileged user, handing
// over the bound sockets to the new process. We'll get to this same code path
// again, skipping this if block, continuing below with the actual serving.
if os . Getuid ( ) == 0 {
mox . ForkExecUnprivileged ( )
panic ( "cannot happen" )
} else {
2023-05-31 15:09:53 +03:00
mox . CleanupPassedFiles ( )
2023-02-27 16:12:58 +03:00
}
}
if err := dmarcdb . Init ( ) ; err != nil {
return fmt . Errorf ( "dmarc init: %s" , err )
}
if err := mtastsdb . Init ( mtastsdbRefresher ) ; err != nil {
return fmt . Errorf ( "mtasts init: %s" , err )
}
if err := tlsrptdb . Init ( ) ; err != nil {
return fmt . Errorf ( "tlsrpt init: %s" , err )
}
done := make ( chan struct { } , 1 )
if err := queue . Start ( dns . StrictResolver { Pkg : "queue" } , done ) ; err != nil {
return fmt . Errorf ( "queue start: %s" , err )
}
store . StartAuthCache ( )
smtpserver . Serve ( )
imapserver . Serve ( )
http . Serve ( )
go func ( ) {
2023-08-08 00:14:31 +03:00
store . Switchboard ( )
<- make ( chan struct { } )
2023-02-27 16:12:58 +03:00
} ( )
return nil
}