There was an API bump. I’ve updated the port in -current, so next snapshot will contain a working package.
However, most filters were removed as they are not considered ready and the API will be subject to further changes. For now, it is recommended to look for alternatives, e.g. filter-dkim-signer can be replaced with dkimproxy and instead of dnsbl one might want to use spamd from base, etc. > On 04 Jul 2016, at 10:35, Heiko <[email protected]> wrote: > > Hi together, > > I get some Filter-API errors. Build with current Snapshot and Ports. > > Any chance for me to fix this? Or do I have to wait for a Source Code > Update? > > Thank you in advance. > > Heiko > > ---- snip ---- > Jul 4 10:17:05 atarax filter-dnsbl-spamcop[17487]: warn: > filter_api:filter-dnsbl-spamcop API mismatch > > Jul 4 10:17:05 atarax filter-dnsbl-sorbs[45978]: warn: > filter-api:filter-dnsbl-sorbs API mismatch > > Jul 4 10:17:05 atarax filter-dnsbl-spamhaus[16763]: warn: > filter-api:filter-dnsbl-spamhaus API mismatch > > Jul 4 10:17:05 atarax filter-dnsbl-sorbs[45978]: fatal: filter-api: > exiting > > Jul 4 10:17:05 atarax filter-dnsbl-spamhaus[16763]: fatal: filter-api: > exiting > > Jul 4 10:17:05 atarax smtpd[82042]: warn: pony -> filter-dnsbl-spamcop: > pipe closed > > Jul 4 10:17:05 atarax smtpd[82042]: warn: filter "filter-dnsbl-spamcop" > closed unexpectedly > > ... > ---- snip ---- > > -- > You received this mail because you are subscribed to [email protected] > To unsubscribe, send a mail to: [email protected] > -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
