ownCloud (witch is based on SabreDAV) supports sync
enable site-wide bayesian filtering

Create directory in $STORAGE_ROOT for bayes database.

Added --username arg to sa-learn as the user mail does not have permission to edit files in $STORAGE_ROOT. There is probably a better solution to this...
catch-all addresses should not have precedence over mail users

Aliases have precedence over mail users. A catch-all address would grab mail intended for a mail user and send it elsewhere. This adds some SQL hackery to create dummy aliases for all mail users.

fixes #200
closes #214 another way
add catch-alls to the admin again with nicer instructions
make mail instructions clearer and describe greylisting, DMARC policy
preliminary work on a mail.log scanner to report things in the control panel
tweak the site-wide bayesian spam filtering config
move sa-learn-pipe.sh from /usr to /usr/local
Merge branch 'jmar71n-master' - site-wide bayesean spam filtering
Merge commit '93a722f'
dont log robots.txt and favicon.ico. we should REALLY consider creating seperate include files for *all* of our "apps", this is getting messy..
status checks: put DNSSEC tests in a better order w.r.t. other tests

* If the PRIMARY_HOSTNAME is in a zone with a DS record set at the registrar, show any DNSSEC failure (but only a failure) immediately since it is probably the cause of other DNS errors displayed later.
* For zones, if a DS record is set at the register, do the DNSSEC test first because even the NS test will fail if DNSSEC is improperly configure.
* But if a DS record is not set, the this is just a suggestion to configure DNSSEC so offer the suggestion last --- after mail and web checks.

see https://discourse.mailinabox.email/t/dns-nameserver-gandi-glue-records-issues/105/3
generate the locales before change to it.

For my german box changing the locale failed:
´´´´/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
setup/functions.sh: line 6: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)´´´´

see #206 and 4e6d572de9c917d5a96b3413923c115ab8fbf7bc
closes #220
commit modified by joshdata
Switch from SMTP+STARTTLS on port 587 to SMTPS on port 465

A good argument for using 465 is made at
https://www.agwa.name/blog/post/starttls_considered_harmful.

FastMail make a good case at
https://www.fastmail.fm/help/technical/ssltlsstarttls.html.
(https://www.fastmail.fm/help/technical/servernamesandports.html states that
587 is available but they do seem to recommend 465).

Gmail uses 465 too.

This shouldn't stop opportunistic TLS being used for incoming mail because
STARTTLS remains available on port 25 - which is what would have been used
before too.

Backward compatibility with clients that were setup to use 587 on existing
installations is maintained because we only change the setup to enable 465
 - we don't disable any existing SMTP+STARTTLS configuration.
Add support for TLS authenticated "sibling host" relayers

The use case for this is e.g. a www server that is a separate machine to
the mailinabox, but which needs to send emails to the internet - for example it
may be running Wordpress or some other web app and need to notify arbitrary
users of comments etc.

In such cases, as the www administrator is using mailinabox, they're almost
certainly better off letting mailinabox do as much as possible as far as email
is concerned (as opposed to having the www sibling host do full delivery
itself) - among other things this simplifies reasoning about DNS records.
Do not require admin as an alias for any domains, do require root for main host
Increase SPF and DMARC strictness