On 2025-06-09 at 17:00:42 UTC-0400 (Mon, 9 Jun 2025 14:00:42 -0700)
Doug Hardie
is rumored to have said:
I am removing this from the postfix list. It's really not applicable
to that.
Please do not send anything further to me off-list.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
On 9 Jun 2025, at 21:46, Bill Cole via Postfix-users
wrote:
>
> Is a blacklistd entry for port587 supposed to block port 25?
>
> I use blacklistd with ipfw, where the 'portxyz' tables are used in rules that
> only block port xyz. I would expect that it does the same with pf.
Same behavior wi
On 9 Jun 2025, at 21:34, Doug Hardie via Postfix-users
wrote:
>
> Indeed it is just that. I dug into the port and found that blacklistd
> support was an added patch. It only is called for failed authentication, not
> for the other myriad of reasons that postfix will drop a connection.
> Un
On Jun 9, 2025, at 05:21, Wietse Venema via Postfix-users
wrote:
> blacklistd support is a *BSD feature.
Doug Hardie:
> Indeed it is just that. I dug into the port and found that
> blacklistd support was an added patch. It only is called for
> failed authentication, not for the other myriad of
Your anchor is populated, at least for port 587. If you don’t see any PF block
based on this anchor it might be a rule ordering problem.
You must ensure your anchor is high enough in the ruleset (super-high, just
below the default "block all" rule)
> On 9 Jun 2025, at 20:59, Doug Hardie wrote
On 2025-06-09 at 14:59:39 UTC-0400 (Mon, 9 Jun 2025 11:59:39 -0700)
Doug Hardie via Postfix-users
is rumored to have said:
On my mail server:
mail# blacklistctl dump -br | tail
218.94.104.180/32:587 OK 3/3 4h12m17s
222.132.167.110/32:587 OK 3/3 1h59m1s
91.45.76.228/32:5
Indeed it is just that. I dug into the port and found that blacklistd support
was an added patch. It only is called for failed authentication, not for the
other myriad of reasons that postfix will drop a connection. Unfortunately
this is not a postfix issue as I am sure it would be fixed if i
On my mail server:
mail# blacklistctl dump -br | tail
218.94.104.180/32:587 OK 3/3 4h12m17s
222.132.167.110/32:587 OK 3/3 1h59m1s
91.45.76.228/32:587 OK 3/3 5h1m53s
36.39.140.2/32:587 OK 3/3 5h9m34s
87.200.232.247/32:587 OK 6/3 4h3m9s
6
Viktor Dukhovni via Postfix-users:
> On Sun, Jun 08, 2025 at 07:29:22PM +0200, Geert Hendrickx via Postfix-users
> wrote:
> > On Mon, Jun 09, 2025 at 00:42:20 +1000, Viktor Dukhovni via Postfix-users
> > wrote:
> > > On Sun, Jun 08, 2025 at 09:29:17AM -0400, Wietse Venema via Postfix-users
> > >
Hello,
> On 9 Jun 2025, at 02:13, Doug Hardie via Postfix-users
> wrote:
>
> I believe that pf is not properly blocking IPs that are supposedly blocked by
> blacklistd. In trying to test this, I am using postfix. However, I don't
> seem to be able to get postfix to call blacklistd. The app
blacklistd support is a *BSD feature.
Wietse
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
11 matches
Mail list logo
