Only add iptables rules if they don't already exist

Only add iptables rules if they don't already exist

Complete rmilter/rspamd setup.

Remove unused variables in jessie

- google_auth_version
- znc_version

bash syntax cleanup

Make OpenDMARC cron job log everything instead of mailing some output to root.

as per discussion in https://github.com/sovereign/sovereign/pull/504

Pass {auth_type} to milters, fixing OpenDKIM signing of authenticated SMTP messages.

DRY in openvpn role and allow other rc.local tasks

Remove obsolete documentation note.

Remove stray + prefix in sudoers file.

Update ownCloud role for ownCloud 8.2

DRY in openvpn role and allow other rc.local tasks

Update ansible in jessie

The ``sudo`` and ``sudo_user`` directives are replaced with ``become``
and ``become_user`` in Ansible 1.9.

Ansible 1.9 or greater is required.

Let's Encrypt support

Fix travis build by fixing ansible-lint version

Before sudo rule merge
https://github.com/willthames/ansible-lint/pull/96

* Add test-requirements.txt
* travis: enable cache for pip packages

The installer automatically updates itself, which registers as a change
in the git repo.  To maintain idempotency of the task list, the repo
download must be forced.

- Remove unnecessary dependencies
- Clean up postgresql server setup
- Install from official package repository
- Expect package installer to enable modules that are needed
- Update virtual host config with owncloud 8.2 configuration
- Update post-deploy instructions

Fix opendmarc installation

Fix Apache's configuration for version 2.4.8 and above.  See
https://community.letsencrypt.org/t/untrusted-on-mobile-newbe/7903

Don't copy the LE certificates.  Instead use the ssl-cert group to
manage access to the LE certificates directly.  See
https://github.com/letsencrypt/letsencrypt/issues/1425 for a request to
have the LE client do this itself.

Let's Encrypt uses DNS to verify domain ownership, so DNS records must
be set up before the paybook is run the first time.

This method uses Subjective Alternative Names (SANs) to get one
certificate for all the subdomains that Sovereign employs, whether or
not the user configured their site with the roles.