Have read through the postscreen documentation closely and got it setup and running already, but could not find the three major possibilities provided by the tcp wrappers: 1. block by hostname 2. block clients with unknown hostname 3. block clients with invalid address<->name mapping
The last two produce the major bulk of spambot connections. Are there any other means to achieve these? пн, 8 февр. 2021 г. в 12:14, Eugene Podshivalov <yauge...@gmail.com>: > I'm new to postscreen and it's what I was looking for. Thanks a lot for > the answers! > > пн, 8 февр. 2021 г. в 11:22, Dominic Raferd <domi...@timedicer.co.uk>: > >> On 08/02/2021 08:04, Eugene Podshivalov wrote: >> > There are a bunch of spiders and spammers nowadays which are knocking >> > the service every hour or so every day. Postfix has a really powerful >> > access control system to protect itself but it becomes a bit hard to >> > read the log file flooded by the connection attempts. I'm currently >> > trying to filter those out by UFW but dynamic addresses make it quite >> > inefficient. >> >> My 2p (I also use ufw but as a last-resort): >> >> Postscreen of course >> >> Fail2ban 0.10+ with its postfix (and recidive) jails >> >> If you run postfix's dnsblog you could remove it to reduce the number of >> log entries >> >> If you allow incoming emails by IPv6 you might turn it off >> >>
