On 13/08/22 16:13, Viktor Dukhovni wrote:
There is no such syntax, as you'd discover if you tried it. Access
tables are pre-registered while parsing *restriction classes*, both
built-in (smtpd_mumble_restrictions) and user-defined. On the RHS of
tables only already defined restriction classes a
On 13/08/22 22:04, Dominik George wrote:
Hi,
The capability to evaluate an access in this way could be a very powerful
feature for Postfix, it would open up a whole host of possibilities having
to do with requirements to say that certain users, be they sasl users, or
senders, or whatever can on
Dnia 13.08.2022 o godz. 11:22:30 Durga Prasad Malyala pisze:
> Did you try fail2ban. It is very good.
I already use fail2ban, but I could not use it in this case, as the AUTH
attempts were from different IP addresses and almost no address did repeat.
So fail2ban would not do anything.
--
Regards,
> "JR" == Jaroslaw Rafa writes:
JR> Dnia 13.08.2022 o godz. 11:22:30 Durga Prasad Malyala pisze:
>> Did you try fail2ban. It is very good.
JR> I already use fail2ban, but I could not use it in this case, as the AUTH
JR> attempts were from different IP addresses and almost no address did
JR>
Dnia 13.08.2022 o godz. 16:23:10 tog...@dinamizm.com pisze:
>
> Have you looked spamhaus or abusix for auth blacklists. They both do a decent
> job
> in blocking auth attempts from nasty IP addresses in my case.
I will look at them. Thank you!
--
Regards,
Jaroslaw Rafa
r...@rafa.eu.org
--
