Date: Tue, 2 Dec 2025 09:46:15 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Lexi Winter <ivy@FreeBSD.org> Cc: stable@freebsd.org Subject: Re: blacklistd, blocklistd and Postfix Message-ID: <86464084-D46B-4744-89A2-B30BBDC346A0@FreeBSD.org> In-Reply-To: <aS6jpfm5YZMNhbpB@amaryllis.le-fay.org> References: <aS6hkE0DoXwI9Jk-@amaryllis.le-fay.org> <38446FB2-D17B-4F91-BDFA-866B1F025DE1@lutter.sk> <aS6jpfm5YZMNhbpB@amaryllis.le-fay.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2 Dec 2025, at 09:30, Lexi Winter <ivy@FreeBSD.org> wrote: > > Juraj Lutter wrote in <38446FB2-D17B-4F91-BDFA-866B1F025DE1@lutter.sk>: >>> in /etc/rc.conf, i have this for Postfix: >>> >>> blocklistd_flags="-r -s /var/spool/postfix/var/run/blacklistd.sock" >>> >>> does Postfix still need blacklistd.sock, or does it prefer >>> blocklistd.sock? >> >> mail/postfix maintainer here: >> >> It relies on whatever blacklist_open() wants/needs/provides. > > thanks. so i will ask a new question: what does blacklist_open() > expect? contrib/blocklist/include/bl.h has: #ifndef _PATH_BLSOCK #define _PATH_BLSOCK "/var/run/blocklistd.sock" #endif I don't see it overridden anywhere in a Makefile, but I may have missed it. :) -Dimitry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86464084-D46B-4744-89A2-B30BBDC346A0>