This commit is contained in:
Zhang Huangbin 2020-06-06 01:15:41 +08:00
parent 40887e884e
commit 6d2a0ccc4d
2 changed files with 33 additions and 12 deletions

View File

@ -71,8 +71,11 @@ CREATE INDEX msgs_idx_time_iso ON msgs (time_iso);
release, please upgrade your iRedMail server by following the upgrade
tutorials: [iRedMail release notes and upgrade tutorials](./iredmail.releases.html).
With changes below, we now store matched log lines which triggerred the ban in
Fail2ban SQL database, also number of times the failure occurred in log files.
With changes below, we now store more info in Fail2ban SQL database:
- Matched log lines which triggerred the ban
- Number of times the failure occurred until ban
- Reverse DNS name of banned IP address
Please run SQL commands below as MySQL root user:
@ -127,8 +130,11 @@ CREATE INDEX msgs_idx_time_iso ON msgs (time_iso);
release, please upgrade your iRedMail server by following the upgrade
tutorials: [iRedMail release notes and upgrade tutorials](./iredmail.releases.html).
With changes below, we now store matched log lines which triggerred the ban in
Fail2ban SQL database, also number of times the failure occurred in log files.
With changes below, we now store more info in Fail2ban SQL database:
- Matched log lines which triggerred the ban
- Number of times the failure occurred until ban
- Reverse DNS name of banned IP address
Please run SQL commands below as MySQL root user:
@ -174,8 +180,11 @@ Now restart Fail2ban service.
release, please upgrade your iRedMail server by following the upgrade
tutorials: [iRedMail release notes and upgrade tutorials](./iredmail.releases.html).
With changes below, we now store matched log lines which triggerred the ban in
Fail2ban SQL database, also number of times the failure occurred in log files.
With changes below, we now store more info in Fail2ban SQL database:
- Matched log lines which triggerred the ban
- Number of times the failure occurred until ban
- Reverse DNS name of banned IP address
Please follow steps below to apply required changes.

View File

@ -100,8 +100,12 @@ SQL database</a>, if you're running an old iRedMail
release, please upgrade your iRedMail server by following the upgrade
tutorials: <a href="./iredmail.releases.html">iRedMail release notes and upgrade tutorials</a>.</p>
</div>
<p>With changes below, we now store matched log lines which triggerred the ban in
Fail2ban SQL database, also number of times the failure occurred in log files.</p>
<p>With changes below, we now store more info in Fail2ban SQL database:</p>
<ul>
<li>Matched log lines which triggerred the ban</li>
<li>Number of times the failure occurred until ban</li>
<li>Reverse DNS name of banned IP address</li>
</ul>
<p>Please run SQL commands below as MySQL root user:</p>
<pre><code>USE fail2ban;
ALTER TABLE banned ADD COLUMN failures INT(2) NOT NULL DEFAULT 0;
@ -141,8 +145,12 @@ SQL database</a>, if you're running an old iRedMail
release, please upgrade your iRedMail server by following the upgrade
tutorials: <a href="./iredmail.releases.html">iRedMail release notes and upgrade tutorials</a>.</p>
</div>
<p>With changes below, we now store matched log lines which triggerred the ban in
Fail2ban SQL database, also number of times the failure occurred in log files.</p>
<p>With changes below, we now store more info in Fail2ban SQL database:</p>
<ul>
<li>Matched log lines which triggerred the ban</li>
<li>Number of times the failure occurred until ban</li>
<li>Reverse DNS name of banned IP address</li>
</ul>
<p>Please run SQL commands below as MySQL root user:</p>
<pre><code>USE fail2ban;
ALTER TABLE banned ADD COLUMN failures INT(2) NOT NULL DEFAULT 0;
@ -176,8 +184,12 @@ SQL database</a>, if you're running an old iRedMail
release, please upgrade your iRedMail server by following the upgrade
tutorials: <a href="./iredmail.releases.html">iRedMail release notes and upgrade tutorials</a>.</p>
</div>
<p>With changes below, we now store matched log lines which triggerred the ban in
Fail2ban SQL database, also number of times the failure occurred in log files.</p>
<p>With changes below, we now store more info in Fail2ban SQL database:</p>
<ul>
<li>Matched log lines which triggerred the ban</li>
<li>Number of times the failure occurred until ban</li>
<li>Reverse DNS name of banned IP address</li>
</ul>
<p>Please follow steps below to apply required changes.</p>
<ul>
<li>Connect to PostgreSQL server as <code>postgres</code> user and connect to <code>vmail</code> database:<ul>