On 31.10.18 13:16, Jaap Bril wrote:
As a new user (postfix as well as postscreen) I monitor maillog to get
a feel for how things work.
Today I noticed a site trying to AUTH from unknown (and I happen to
know there is no possibly valid user at that address).
I decided to try out blacklisting:
On 8 Mar 2018, at 0:59 (-0500), Maurizio Caloro wrote:
[Main.cf]
postscreen_blacklist_action = drop
postscreen_access_list = permit_mynetworks, hash:/etc/postfix/access
postscreen_bare_newline_enable = yes
Remove this. See http://www.postfix.org/POSTSCREEN_README.html#after_220
for the det
On May 23, 2012, at 15:35, Wietse Venema wrote:
> Wietse Venema:
>> Wietse Venema:
>>> Maciej Uhlig:
We run fail2ban to update postscreen blacklist which is cidr file. To
make postscreen see the changes we have to reload postfix. Yesterday we
found postfix was reloaded more than 300
Wietse Venema:
> Wietse Venema:
> > Maciej Uhlig:
> > > We run fail2ban to update postscreen blacklist which is cidr file. To
> > > make postscreen see the changes we have to reload postfix. Yesterday we
> > > found postfix was reloaded more than 3000 times. Sure it is not
> > > acceptable.
> >
>
On May 23, 2012, at 11:23, Maciej Uhlig wrote:
> We run fail2ban to update postscreen blacklist which is cidr file. To
> make postscreen see the changes we have to reload postfix. Yesterday we
> found postfix was reloaded more than 3000 times. Sure it is not acceptable.
>
> What would be the best
Wietse Venema:
> Maciej Uhlig:
> > We run fail2ban to update postscreen blacklist which is cidr file. To
> > make postscreen see the changes we have to reload postfix. Yesterday we
> > found postfix was reloaded more than 3000 times. Sure it is not acceptable.
>
> Surely you don't have to reload i
Maciej Uhlig:
> We run fail2ban to update postscreen blacklist which is cidr file. To
> make postscreen see the changes we have to reload postfix. Yesterday we
> found postfix was reloaded more than 3000 times. Sure it is not acceptable.
Surely you don't have to reload it EVERY 30 SECONDS. What ab
I'd let fail2ban write to a temporary file / cidr file which you move
by cronjob all 10 minutes if there has been a change (shasum).
That way your blacklist will updated at maximum all 10 minutes (or
whatever delay you define) and _only_ if there has been a change.
though 3000 times would mean ci
Thanks rob0,
when i set
postscreen_blacklist_action = drop
all works like a charm.
marko, from sunny hamburg
Am 27.09.2011 17:08, schrieb /dev/rob0:
On Tuesday 27 September 2011 09:52:16 Marko Weber wrote:
Hello i created an etc/postfix/postscreen_access.cidr in my postfix
dir.
now posts
On Tuesday 27 September 2011 09:52:16 Marko Weber wrote:
> Hello i created an etc/postfix/postscreen_access.cidr in my postfix
> dir.
> now postscreen checks on connect for the entries.
>
> i set one server in the list with reject
>
> Is it right, that the test mail goes thru postfix?
>
> i see
10 matches
Mail list logo
