fix filter-spamassassin with recent-ish smtpd

Hello, that time of the year again, where I okay a diff to bump the filter protocol and forget to actually double-check the consumers T.T everything is in the diff below, but basically now filters when logging to *stderr* can prepend "priority tags" (e.g. "DEBUG|", "WARN|" or ...) that gets propagated to syslog. this filter does the syslog stuff itself afaik, so it's a no-op. okay to commit this and backport to stable? Index: Makefile =================================================================== RCS file: /cvs/ports/mail/opensmtpd-filters/spamassassin/Makefile,v diff -u -p -r1.10 Makefile --- Makefile 17 Apr 2024 17:10:12 -0000 1.10 +++ Makefile 4 Nov 2026 10:08:00 -0000 @@ -3,6 +3,7 @@ COMMENT = Apache SpamAssassin integratio V = 0.8 FILTER_NAME = spamassassin DISTNAME = filter-spamassassin-${V} +REVISION = 0 HOMEPAGE = https://www.umaxx.net/ CATEGORIES = mail Index: patches/patch-filter-spamassassin_go =================================================================== RCS file: patches/patch-filter-spamassassin_go diff -N patches/patch-filter-spamassassin_go --- /dev/null 1 Jan 1970 00:00:00 -0000 +++ patches/patch-filter-spamassassin_go 4 Nov 2026 10:08:00 -0000 @@ -0,0 +1,18 @@ +handle the smtpd filter-protocol version 0.8 too + +the only difference is that messages can be prepended with +"priority tags". this filter is not logging to stderr though +so it's effectively a no-op. + +Index: filter-spamassassin.go +--- filter-spamassassin.go.orig ++++ filter-spamassassin.go +@@ -211,7 +211,7 @@ func run() { + for in.Scan() { + f := strings.Split(in.Text(), "|") + t, ver, ev, sid := f[0], f[1], f[4], f[5] +- if (t != "filter" && t != "report") || ver != "0.7" { ++ if (t != "filter" && t != "report") || ver != "0.8" { + l3.Err(fmt.Sprintln(sid, "protocol", t, ver)) + return + }

Re: [update] knot-3.6.2

On 2026 Nov 01 (Sun) at 14:58:09 +0100 (+0100), Jeremie Courreges-Anglas wrote: : :Here's an update to knot-3.6.2. It doesn't require lmdb 1.X but since :it implements an automated migration from lmdb 0.9 to 1.X, it will :help people upgrade. The new tarball includes some code from lmdb :0.9, still using system lmdb. The following diff adds the same :lack-of-UBC workaround as already used in databases/lmdb, I'm not 100% :certain it is needed. : :I have tested this with -current lmdb 0.9.33 and with the latest :lmdb-1.0.2 update diff. My test setup is very basic so more serious :tests would be welcome. oks too. : tested on my prod dns signing server, OK -- Green light in A.M. for new projects. Red light in P.M. for traffic tickets.