On 6/5/2019 16:30, Wietse Venema wrote:
Lefteris Tsintjelis:
On 6/5/2019 12:03, lists wrote:
SSHGuard now works for more than ssh. It has hooks for postfix and other
services.
That is great then! More and much better choices other than log parsers.
Fyi, SSHGuard is a logfile parser accordi
On 6/5/2019 20:07, @lbutlr wrote:
On 6 May 2019, at 06:33, Lefteris Tsintjelis wrote:
On 6/5/2019 15:14, @lbutlr wrote:
On 6 May 2019, at 02:10, Lefteris Tsintjelis wrote:
Fail2ban and equivalent log parsers are just too resource hungry,
No they aren't.
Yes they are.
Not on my super pow
On 2019-05-06 10:26:17 (-0700), @lbutlr wrote:
On 6 May 2019, at 11:22, lists wrote:
It had been my experience that the firewall uses more resources that
SSHGuard. Certainly it uses more memory.
But you do not have to use a firewall if that's an issue.
/etc/hosts.allow is always an option, a
. The password guessers will hammer postfix all day,
but fortunately those attacks are rare. At the moment I just use postfix rate
limiting.
Original Message
From: krem...@kreme.com
Sent: May 6, 2019 10:08 AM
To: postfix-users@postfix.org
Subject: Re: Blacklistd interaction
On 6 May 2019, at 11:22, lists wrote:
> It had been my experience that the firewall uses more resources that
> SSHGuard. Certainly it uses more memory.
But you do not have to use a firewall if that's an issue. /etc/hosts.allow is
always an option, and that block is practically free.
--
I ne
On 6 May 2019, at 06:33, Lefteris Tsintjelis wrote:
> On 6/5/2019 15:14, @lbutlr wrote:
>> On 6 May 2019, at 02:10, Lefteris Tsintjelis wrote:
>>> Fail2ban and equivalent log parsers are just too resource hungry,
>> No they aren't.
>
> Yes they are.
Not on my super powerful 7 year old i5 mail s
Lefteris Tsintjelis:
> On 6/5/2019 12:03, lists wrote:
> > SSHGuard now works for more than ssh. It has hooks for postfix and other
> > services.
>
> That is great then! More and much better choices other than log parsers.
Fyi, SSHGuard is a logfile parser according to https://www.sshguard.net/
On 6/5/2019 15:14, @lbutlr wrote:
On 6 May 2019, at 02:10, Lefteris Tsintjelis wrote:
Fail2ban and equivalent log parsers are just too resource hungry,
No they aren't.
Yes they are.
messy and more time consuming to maintain
Sounds like you are parting some false information others fed y
On 6 May 2019, at 02:10, Lefteris Tsintjelis wrote:
> On 6/5/2019 9:42, @lbutlr wrote:
>> On 4 May 2019, at 15:52, Lefteris Tsintjelis wrote:
>>> Would be great to consider its future adoption and if possible to take it
>>> even further to interact with postscreen.
>> Why would this be a good th
On 6/5/2019 12:03, lists wrote:
SSHGuard now works for more than ssh. It has hooks for postfix and other
services.
That is great then! More and much better choices other than log parsers.
SSHGuard now works for more than ssh. It has hooks for postfix and other
services.
Original Message
From: le...@spes.gr
Sent: May 6, 2019 1:11 AM
To: postfix-users@postfix.org
Subject: Re: Blacklistd interaction
On 6/5/2019 9:42, @lbutlr wrote:
> On 4 May 2019, at 15
On 6/5/2019 9:42, @lbutlr wrote:
On 4 May 2019, at 15:52, Lefteris Tsintjelis wrote:
Would be great to consider its future adoption and if possible to take it even
further to interact with postscreen.
Why would this be a good thing for postfix to do?
There are already plenty of tools that g
relay.
Original Message
From: krem...@kreme.com
Sent: May 5, 2019 11:43 PM
To: postfix-users@postfix.org
Subject: Re: Blacklistd interaction
On 4 May 2019, at 15:52, Lefteris Tsintjelis wrote:
> Would be great to consider its future adoption and if possible to take it
> even
On 4 May 2019, at 15:52, Lefteris Tsintjelis wrote:
> Would be great to consider its future adoption and if possible to take it
> even further to interact with postscreen.
Why would this be a good thing for postfix to do?
There are already plenty of tools that generate block lists for the vario
On 5/5/2019 0:26, Wietse Venema wrote:
Wietse Venema:
Lefteris Tsintjelis:
I am struggling to find some info about how postfix collaborates with
blacklistd but can't seem to find much. I assume this is only login
based so far (works REALLY great BTW). Besides the false logins, the
question I ha
Wietse Venema:
> Lefteris Tsintjelis:
> > I am struggling to find some info about how postfix collaborates with
> > blacklistd but can't seem to find much. I assume this is only login
> > based so far (works REALLY great BTW). Besides the false logins, the
> > question I have is if it is possibl
Lefteris Tsintjelis:
> I am struggling to find some info about how postfix collaborates with
> blacklistd but can't seem to find much. I assume this is only login
> based so far (works REALLY great BTW). Besides the false logins, the
> question I have is if it is possible to use blacklistd with
On 4 May 2019, at 14:32, Lefteris Tsintjelis wrote:
I am struggling to find some info about how postfix collaborates with
blacklistd but can't seem to find much.
Probably because that is implemented via patches unique to NetBSD and
FreeBSD. Perhaps you should ask the people who authored or al
I am struggling to find some info about how postfix collaborates with
blacklistd but can't seem to find much. I assume this is only login
based so far (works REALLY great BTW). Besides the false logins, the
question I have is if it is possible to use blacklistd with postscreen
also (I assume it
19 matches
Mail list logo
