From 2707992c442805b9c3c5c7f4561b3e66ad121c13 Mon Sep 17 00:00:00 2001
From: arcaine2 <arcaine2@users.noreply.github.com>
Date: Sun, 18 Dec 2016 13:06:45 +0100
Subject: [PATCH] Fail2ban fix for restarting container

Fail2ban doesn't seems to shutdown cleanly and leaves fail2ban.sock file that prevent it from starting after a container restart. That simple check should do the trick.
---
 target/start-mailserver.sh | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/target/start-mailserver.sh b/target/start-mailserver.sh
index d14175cd..9e8f8efe 100644
--- a/target/start-mailserver.sh
+++ b/target/start-mailserver.sh
@@ -840,6 +840,10 @@ function _start_daemons_saslauthd() {
 function _start_daemons_fail2ban() {
 	notify 'task' 'Starting fail2ban'
 	touch /var/log/auth.log
+	# Delete fail2ban.sock that probably was left here after container restart
+  	if [ -e /var/run/fail2ban/fail2ban.sock ]; then
+    	  rm /var/run/fail2ban/fail2ban.sock
+  	fi
 	/etc/init.d/fail2ban start
 }