I would have included the favicon as a static asset but the management daemon
isn't set up to support them.
Perhaps Josh would rather that mailinabox.email did not receive the traffic
this would add.
Perhaps hotlinking like this is untenable because users may be concerned about
referencing external resources unnecessarily.
Perhaps this is bad because deployed boxes should not make assumptions about
the location and availability of external resources. But a change of location/
availability of the favicon wouldn't make things any worse than they currently
are - and it is only a favicon.
If none of the above are issues, the web UI does look better with a favicon,
and this is a pretty quick way of adding one.
* also fixes the footer alignment to be within a container rather than a container-fluid
* this changed the width of the login form slightly, so am cleaning that up too
see #244
* 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.
David Piggott
Joshua Tauberer