* Created a new Python/flask-based management daemon.
* Moved the mail user management core code from tools/mail.py to the new daemon.
* tools/mail.py is a wrapper around the daemon and can be run as a non-root user.
* Adding a new initscript for the management daemon.
* Moving dns_update.sh to the management daemon, called via curl'ing the daemon's API.

This also now runs the DNS update after mail users and aliases are added/removed,
which sets up new domains' DNS as needed.

remove permit_dnswl_client because postfix has odd behavior when an IP address is not listed: it turns all bounces into deferrals (retry)

partially reverts 6d473f81

test_mail: if EHLO test fails continue testing the rest, since user may be waiting on DNS propagation

add more postfix rules: reject_non_fqdn_sender, reject_unknown_sender_domain, reject_rhsbl_sender, and permit_dnswl_client

test_dns: properly test the non-primary domain of a box (for email addresses on domains besides PUBLIC_HOSTNAME)

DKIM: For the benefit of ADSP and DMARC (not yet impl), each sending domain should be its signing domain

See http://phusion.github.io/baseimage-docker/ for why the stock Ubuntu
image from Docker is not good enough for a complex system.

Thanks to @pjz for updating the base image for Ubuntu 14.04 and starting
the service scripts.

see #16; merges #49

* let the base image's system services manager handle it
* move our container start script to occur before system services are started

our trees had diverged, various conflicts resolved

docker: re-run the start script on the container's first run because it won't know its hostname or IP address until then

don't ask the user to create an email account if the shell is non-interactive and provide a better default for the domain name

docker: disable the ufw firewall because it is not supported in a docker container and produces a lot of error output (by reverting a510e08f and setting an environment variable)

docker: do ADD container/docker later on so that the Dockerfile can be updated and still reuse a cached image after the major setup steps are done

docker: if container was launched with a tty start bash otherwise loop forever to keep the container going

don't reject mail to domains that only have aliases and not users

thanks @konklone for discussion

move the Dockerfile to the root to allow the working directory of the repo to be pushed inside the image (rather than inside the container getting a fresh mailinabox from github) so changes in the working copy can be tested in Docker quickly / without pushing to github

We were installing .deb's from Debian. The next apt-get upgrade would cause roundcube to be upgraded.
Maybe that also triggered the installation of apache. Now install roundcube from Ubuntu. So long as
Ubuntu doesn't post an update to roundcube, at least it won't trigger an upgrade on the next
apt-get upgrade. This should also mean we don't need to purge the installation of apache2.

Also try using apt-mark hold to prevent roundcube from being updated, in case that will trigger
dependencies.

make a bash function to use everywhere we apt-get-install (`DEBIAN_FRONTEND=noninteractive apt-get -qq -y `)

ensures the output is quiet

enable roundcube's password-change plugin