Here is what my direct.xml file looks like
more direct.xml
-p tcp
--dport 22 -m state --state NEW -m recent --set
-p tcp
--dport 22 -m state --state NEW -m recent --update --seconds 30 --hitcount 4 -j
REJECT --reject-with tcp-reset
-p tcp
--dport 25 -m state --state NEW -m recent
Hi Eric:
This is the patch that we used with Bill's toaster and it was very
effective in limiting the damage from hijacked email accounts.
http://spamthrottle.qmail.ca/
Let me know what you think
Jeff
On 8/22/2019 7:18 PM, Eric Broch wrote:
What about this tcpserver limits patch
Hi Eric:
That patch might work - is it already installed?
Jeff
On 8/22/2019 7:18 PM, Eric Broch wrote:
What about this tcpserver limits patch
https://qmail.jms1.net/ucspi-tcp/
On 8/22/2019 9:32 AM, Jeff Koch wrote:
Hi List
Sometimes a user's email credentials get hijacked and before we
I can share what I have for firewalld later today
> Il giorno 22 ago 2019, alle ore 10:20, Leonardo Porto
> ha scritto:
>
>
> I do some port connection limits with iptables and xt_recent, but still have
> some spam as well, a limit in user accounts would be useful.
>
>
>
> Em 22/08/2019
I do some port connection limits with iptables and xt_recent, but still
have some spam as well, a limit in user accounts would be useful.
Em 22/08/2019 12:32, Jeff Koch escreveu:
Hi List
Sometimes a user's email credentials get hijacked and before we know
it 100,000 spams go out. This
Hi List
Sometimes a user's email credentials get hijacked and before we know it
100,000 spams go out. This doesn't happen very often but when it does
it's a mess. Our mailserver gets blocked by major ISP and it takes weeks
to get the blocks lifted. So I was thinking - is there any way to
