Rename config examples directory (#2438)

config-examples/dovecot-quotas.cf

@@ -0,0 +1,3 @@
+# define user's quota in this file
+# E.g;
+# user@domain:50M

config-examples/dovecot.cf

@@ -0,0 +1,4 @@
+# File for additional dovecot configurations.
+# For more informations read https://doc.dovecot.org/configuration_manual/quick_configuration/
+
+#mail_max_userip_connections = 50

config-examples/fail2ban-fail2ban.cf

@@ -0,0 +1,69 @@
+# Fail2Ban main configuration file
+#
+# Comments: use '#' for comment lines and ';' (following a space) for inline comments
+#
+# Changes:  in most of the cases you should not modify this
+#           file, but provide customizations in fail2ban.local file, e.g.:
+#
+# [Definition]
+# loglevel = DEBUG
+#
+
+[Definition]
+
+# Option: loglevel
+# Notes.: Set the log level output.
+#         CRITICAL
+#         ERROR
+#         WARNING
+#         NOTICE
+#         INFO
+#         DEBUG
+# Values: [ LEVEL ]  Default: ERROR
+#
+#loglevel = INFO
+
+# Option: logtarget
+# Notes.: Set the log target. This could be a file, SYSLOG, STDERR or STDOUT.
+#         Only one log target can be specified.
+#         If you change logtarget from the default value and you are
+#         using logrotate -- also adjust or disable rotation in the
+#         corresponding configuration file
+#         (e.g. /etc/logrotate.d/fail2ban on Debian systems)
+# Values: [ STDOUT | STDERR | SYSLOG | SYSOUT | FILE ]  Default: STDERR
+#
+#logtarget = /var/log/fail2ban.log
+
+# Option: syslogsocket
+# Notes: Set the syslog socket file. Only used when logtarget is SYSLOG
+#        auto uses platform.system() to determine predefined paths
+# Values: [ auto | FILE ]  Default: auto
+#syslogsocket = auto
+
+# Option: socket
+# Notes.: Set the socket file. This is used to communicate with the daemon. Do
+#         not remove this file when Fail2ban runs. It will not be possible to
+#         communicate with the server afterwards.
+# Values: [ FILE ]  Default: /var/run/fail2ban/fail2ban.sock
+#
+#socket = /var/run/fail2ban/fail2ban.sock
+
+# Option: pidfile
+# Notes.: Set the PID file. This is used to store the process ID of the
+#         fail2ban server.
+# Values: [ FILE ]  Default: /var/run/fail2ban/fail2ban.pid
+#
+#pidfile = /var/run/fail2ban/fail2ban.pid
+
+# Options: dbfile
+# Notes.: Set the file for the fail2ban persistent data to be stored.
+#         A value of ":memory:" means database is only stored in memory 
+#         and data is lost when fail2ban is stopped.
+#         A value of "None" disables the database.
+# Values: [ None :memory: FILE ] Default: /var/lib/fail2ban/fail2ban.sqlite3
+#dbfile = /var/lib/fail2ban/fail2ban.sqlite3
+
+# Options: dbpurgeage
+# Notes.: Sets age at which bans should be purged from the database
+# Values: [ SECONDS ] Default: 86400 (24hours)
+#dbpurgeage = 1d

config-examples/fail2ban-jail.cf

@@ -0,0 +1,21 @@
+[DEFAULT]
+
+# "bantime" is the number of seconds that a host is banned.
+#bantime  = 10m
+
+# A host is banned if it has generated "maxretry" during the last "findtime"
+# seconds.
+#findtime  = 10m
+
+# "maxretry" is the number of failures before a host get banned.
+#maxretry = 5
+
+# "ignoreip" can be a list of IP addresses, CIDR masks or DNS hosts. Fail2ban
+# will not ban a host which matches an address in this list. Several addresses
+# can be defined using space (and/or comma) separator.
+#ignoreip = 127.0.0.1/8
+
+# Default ban action
+# iptables-multiport:	block IP only on affected port
+# iptables-allports:	block IP on all ports
+#banaction = iptables-allports

config-examples/fetchmail.cf

@@ -0,0 +1,13 @@
+## Example configuration: IMAP
+#poll imap.example.com with proto IMAP
+#	user 'username' there with
+#	password 'secret'
+#	is 'user1@domain.tld'
+#	here ssl
+
+## Example configuration: POP3
+#poll pop3.example.com with proto POP3
+#	user 'username' there with
+#	password 'secret'
+#	is 'user2@domain.tld'
+#	here options keep ssl

config-examples/user-patches.sh.dist

@@ -0,0 +1,7 @@
+#! /bin/bash
+##
+# This user patches script runs right before starting the daemons. That means, all the other configuration is in place, so the script can make final adjustments.
+# If you modify any supervisord configuration, make sure to run "supervisorctl update" or "supervisorctl reload" afterwards.
+# To enable the script, you must save it in your config directory as "user-patches.sh".
+##
+echo "Default user-patches.sh successfully executed"