- Add backupmx role in a separate environment
- Configure backups on BHS (once ready to switch BHS to new instances)
- Fully configure sieve
- Configure spamassassin bayesian filter training
- Refactor large roles to better separate concerns by splitting up the roles
- Check ansible-galaxy for potentially useful roles
- Create collections for things like sogo and my separated IMAP / MX setup
- What to do about encrypting data?
- An issue is autorestarting in the case OVH needs to intervene (for example if the monitoring indicates non-responsiveness), which at least at first is a reboot.
- Make mail/groupware users and aliases PostgreSQL backed
- Use a separate repo for holding the demo users and aliases.
- Make sure I have a reasonable way of adding/removing uses and aliases from the database.
- Fix roles which are environment-specific in the role itself; that should be handled via data/variables
- Where possible, move environment data (even in vaults) out of this repo (decouple the logic/skeletons from the environment data) or move most of this repo into collections so that this repo is the data and not the logic/skeletons.
- Enable server status on port 80 without proxy protocol only for localhost for apache2.