Use the changed `mail_virtual_users` structure to ensure directories and
sieve rules are created for each defined account.

feat(monit): Enable web interface

Web interface listens on localhost only.
The web interface is needed for polling monit
status from the console via::

    monit summary

fix(mail): main_virtual_xx variables usage

mail_virtual_xx list were not use correctly in tasks.

We got error 'unicode object' has no attribute 'name' because:
with_items:
 - "{{ mail_virtual_xx }}
is understood has a list of strings containing information extracted from {{ mail_virtual_xx }} variable

 Now we use:
   with_items: virtual_domain_xx}}"

Add logwatch to the monitoring role to email daily log summaries

Based on playbook from https://github.com/phred/5minbootstrap

Roundcube managesieve plugin and automatic folder creation

These are the changes necessary to enable Roundcube's manage sieve plugin to mange server-side sieve filters.

Signed-off-by: PajamaSoft <support@pajamasoft.com>

ircbouncer: connect to default server (freenode) using ssl

Use gathered facts to determine the correct network interface in the OpenVPN role

OpenVPN role

Fix local tarsnap key path in readme

Turns out it should be in the tarsnap role, not common. :)

Added friendly_networks variable to denote whitelisted networks

Set permissions and owner on virtual mail domains

Move the settings of the virtual mail directories into a separate
ansible task.

Without the owner being set to vmail and dovecot, when a virtual user
tries to access their mail account, dovecot throws an error that it does
not have permission to create the mail folder for the user.

With the owner and permissions being set the user's mail directory is
created and they can successfully sign in.

Adds/subscribes Drafts, Sent, Junk, Trash and Archive mailboxes.

* Removed unicode char from task name (ansible 1.3 doesn’t like it)
* Use ansible sysctl module instead of lineinfile
* Wait for only 5 seconds (for fully automated deploy)

Updated the OpenVPN role so certificate expiration is handled correctly

correctly. The number of days that a certificate will be considered
valid is now a user-controlled variable and is set to five years by
default. (Fixes Issue #87)

Testing & CI

This URL works for all releases, not just the latest one.