Re: blacklistd vs blocklistd
Michael Grimm <[email protected]>
| Newsgroups | gmane.os.freebsd.questions |
|---|---|
| Message-ID | <[email protected]> |
Doug Hardie <[email protected]> wrote: >> On Feb 8, 2026, at 12:05, Michael Grimm <[email protected]> wrote: >> Doug Hardie <[email protected]> wrote: >>> I tried that, and encountered the issue that postfix only supports blacklistd and ssh only supports blocklistd. As a result, a system that wants to use both cannot. Either one or the other works depending on which server is started. >> blocklistd runs perfectly well with both sshd and postfix(-current) on smtp and submission. Just use blocklistd_enable="YES" in your /etc/rc.conf and blocklistd should run as expected. And you need to rename your old /etc/blacklistd.conf into /etc/blocklistd.conf > > The version of postfix in the packages still has blacklist. Ah, now I see what you are referring to. But, that is just a lack in wording, respecting the upstream change of blocklistd sources. More or less a cosmetic issue in the Makefiles and patches in 'files' of all postfix ports. The patches in the mail/postfix* ports are referencing the installed blocklistd sources in /usr/src! Postfix becomes patched and postfix doesn't care whether you run blocklistd or blacklistd because both binaries are identical w.r.t to their functionality. HTH and regards, Michael