On 2020-07-14 09:29, Michael Orlitzky wrote:
It appears that the blacklist entry is superseded by the cache?
...
Is that intentional? Fixable? Work-aroundable?
On 15.07.20 09:25, Michael Orlitzky wrote:
For posterity: digging into the source led me to discover the
You apparently missed my
Michael Orlitzky:
> On 2020-07-14 09:29, Michael Orlitzky wrote:
> > It appears that the blacklist entry is superseded by the cache?
> >
> > ...
> >
> > Is that intentional? Fixable? Work-aroundable?
> >
>
> For posterity: digging into the source led me to discover the
>
> postscreen_blackl
On 2020-07-14 09:29, Michael Orlitzky wrote:
> It appears that the blacklist entry is superseded by the cache?
>
> ...
>
> Is that intentional? Fixable? Work-aroundable?
>
For posterity: digging into the source led me to discover the
postscreen_blacklist_action (default: ignore)
parameter
On 14.07.20 09:29, Michael Orlitzky wrote:
Out postmaster/abuse addresses fall through a trapdoor at the top of
smtpd_recipient_restrictions, and every once in a while someone decides
to abuse that kindness. Yesterday I added 84.54.12.0/24 to postscreen's
blacklist to prevent them from ever reach
Out postmaster/abuse addresses fall through a trapdoor at the top of
smtpd_recipient_restrictions, and every once in a while someone decides
to abuse that kindness. Yesterday I added 84.54.12.0/24 to postscreen's
blacklist to prevent them from ever reaching the trapdoor. This morning
I was surprise
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:
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:
*postscreen_access.cidr:185.36.8
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
Hello Together
i will download the Banned Blacklist IP from Internet and add to me Postfix
with Postscreen
after i check the config from Postscreen i have the following
configurations.
strange thing are i will become this message von Mail.log
Equal from where i send the email to my domain th
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
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 tim
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.
>
> Wh
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.
>
> Sure
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
mean circa all 30 minutes, if I calculated
correctly, that doesn't sound that bad imo.
On Wed, 23 May 2012 11:23:14 +0200
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. Yest
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 way to refresh postscreen blacklist (something
like kill
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
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 in logs :
Sep 27 16:43:30 netcogw postfix/postscreen[15206]: CONNECT f
19 matches
Mail list logo
