On 8/10/20 7:22 AM, Christos Zoulas wrote:
Can you try this?
christos
Index: smtpd.c
===
RCS file: /cvsroot/src/external/ibm-public/postfix/dist/src/smtpd/smtpd.c,v
retrieving revision 1.17
diff -u -u -r1.17 smtpd.c
--- smtpd.c
In article ,
Emile `iMil' Heitor wrote:
>
>Hi,
>
>On this machine:
>
>NetBSD senate.imil.net 9.0 NetBSD 9.0 (GENERIC) #0: Fri Feb 14 00:06:28
>UTC 2020
>mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64
>
>I have the following setup:
>
>$ cat /etc/blacklistd.conf
>[local]
On Fri, 7 Aug 2020, Martin Neitzel wrote:
You have to check the smtpd source to see if blacklist{,_r,_sa}
could be called at the point where the issue is logged.
Indeed the source code delivered. It suggests the notification should be
triggered when the auth attempt reach the
iMil> smtpd is indeed linked over libblacklist:
iMil>
iMil> $ ldd /usr/libexec/postfix/smtpd |grep black
iMil> -lblacklist.0 => /usr/lib/libblacklist.so.0
iMil> Anything I am missing here?
A daemon may well notify blacklistd about a possible attack at some
places along the code path but
Hi,
On this machine:
NetBSD senate.imil.net 9.0 NetBSD 9.0 (GENERIC) #0: Fri Feb 14 00:06:28 UTC
2020 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64
I have the following setup:
$ cat /etc/blacklistd.conf
[local]
domain dgram * * *
