Skip to main content

Fail2ban - Block attacks

Your server is venerable to attacks, and you have to time and again monitor. After monitoring you have to block the attackers IP’s. Use Fail2ban package, which would ease you a bit. To install Fail2ban you need to add extra 3rd party repositories - Extra Package for Enterprise Linux (EPEL). After that you can use yum to install the package.

How to install addition repositories for your linux box (Add Repository)

yum install fail2ban
Labels:

Comments

Post a Comment

Popular posts from this blog

Clear Zimbra Mail Queue

If you want to clear mail queue from specific email address run the following command in your terminal. Below will remove mail queues, by checking FROM sender. eg. remove all mail queues sent by info@example.com /opt/zimbra/postfix/sbin/mailq | tail -n +2 | grep -v '^ *(' | awk 'BEGIN { RS = "" } { if ($7 == "info@example.comt") print $1 } ' | tr -d '*!' | xargs -rn1 /opt/zimbra/postfix/sbin/postsuper -d Below will remove mail queues, by checking TO sender. eg. remove all mail queues sent to info@example.com /opt/zimbra/postfix/sbin/mailq | tail -n +2 | grep -v '^ *(' | awk 'BEGIN { RS = "" } { if ($8 == "info@example.comt") print $1 } ' | tr -d '*!' | xargs -rn1 /opt/zimbra/postfix/sbin/postsuper -d
Post a Comment
Read more

Zimbra Mail Error: not enough free space in mail queue

If you are using Zimbra Mail and you are not able to send any mails and also you see an Error Message " not enough free space in mail queue " under /var/log/message. Then you should try out this solution. 1. Login to the server, and then again login as zimbra as follows: #su - zimbra 2. Check the Postfix message_size_limit, by default it should be 10MB (i.e. '10240000' bytes) as follows: $postconf message_size_limit message_size_limit = 10240000 3. If the value is higher than that, set it as follows to 10MB $ zmprov modifyConfig zimbraMtaMaxMessageSize 10240000 $ postfix reload Now try sending Mail, It should work. You could try out this solution for Error: " SMTP Server Reported: 452 4.3.1 Insufficient System Storage "
Post a Comment
Read more