After we upgraded to 6.47 we no longer get email alerts for permblocks and the comments after the IP address in csf.deny are missing now (seel below). We do however still get alerts for temp blocks. Anyone else having this problem?
92.87.5.14 # lfd: (PERMBLOCK) 92.87.5.14 (RO/Romania/-) has had more than 4 temp blocks in the last 86400 secs - Tue Jan 14 11:08:32 2014
200.77.249.162 # lfd: (PERMBLOCK) 200.77.249.162 (MX/Mexico) has had more than 4 temp blocks in the last 86400 secs - Fri Jan 31 06:31:29 2014
112.72.98.108 # lfd: (PERMBLOCK) 112.72.98.108 (VN/Vietnam/-) has had more than 4 temp blocks in the last 86400 secs - Wed Feb 12 00:50:43 2014
171.25.159.192 # lfd: (PERMBLOCK) 171.25.159.192 (SE/Sweden/-) has had more than 4 temp blocks in the last 86400 secs - Fri Feb 21 04:45:32 2014
167.68.122.181 # lfd: (PERMBLOCK) 167.68.122.181 (US/United States/-) has had more than 4 temp blocks in the last 86400 secs - Wed Mar 26 17:05:05 2014
213.228.146.145
209.188.16.114
81.149.150.213
72.46.152.15
nope, upgrade did not fix it. IS not only not alerting but also as posted in the first message by AeroWeb is not logging the blocking reason, just listing the ip.
In my case after searching the blocked IPs in log files I found them in assp log and the issue was smtp login failure. Also had no issue on a cpanel server without assp.
So I think some new settings in assp is putting those IPs in deny file.
ehsan wrote:Thanks to ASSP Deluxe Support this is how it happens and you may disable it :
grscripts[.]com/changelog.html#02
grscripts[.]com/howtofaq.html#fa01
Just wanted to confirm that our original problem is related to ASSP and that the post by ehsan has fixed the problem for us too. Thanks! Now if only ASSP would trigger an alert message along with comments for each IP block rather than just surprising us like they did.
It might be good to put this issue in the CSF documentation read me file just in case someone else runs into the same issue.