On Tue, Sep 17, 2019 at 08:04:47AM +0200, Martijn van Duren wrote: > Thanks. Apparently I had a opensmtpd.h still lingering in /usr/include > on this machine.
I got rusty with OpenBSD ports, so I don't have anything to comment regards the port itself, but dnsbl filter works (started with options -vm and runs as _smtpd user): 2019-09-18T20:34:45.388Z ks28975 smtpd[62206]: info: OpenSMTPD 6.6.0 starting 2019-09-18T20:36:40.396Z ks28975 smtpd[53386]: 7f750e1df82c8768 smtp connected address=209.85.222.169 host=mail-qk1-f169.google.com 2019-09-18T20:36:40.519Z ks28975 smtpd[37832]: spamcop: 7f750e1df82c8768 not listed 2019-09-18T20:36:40.538Z ks28975 smtpd[37832]: spamhaus: 7f750e1df82c8768 not listed 2019-09-18T20:36:40.692Z ks28975 smtpd[37832]: blocklist: 7f750e1df82c8768 not listed 2019-09-18T20:36:40.742Z ks28975 smtpd[37832]: megarbl: 7f750e1df82c8768 not listed 2019-09-18T20:36:41.137Z ks28975 smtpd[53386]: 7f750e1df82c8768 smtp tls ciphers=TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256 Note from myself, not related to the port itself. I found that spamd(8) in front of smtpd(8) and periodic `smtpctl spf walk` on Big Mail Corps domains to white list their SPF exposed subnets via <nospamd> pf table gives very good results, so I never felt a need to reach for additional filtering signal via DNSBLs. In other words, I'm not sure will I stick to above filters in long run. Nonetheless, thanks Martijn for this additional tool. -- Regards, Mikolaj
