Date: Sat, 20 Jul 2019 12:03:10 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 239334] mail/milter-greylist bring GeoIP support back, utilizing libmaxminddb implemented by Markus Wennrich Message-ID: <bug-239334-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239334 Bug ID: 239334 Summary: mail/milter-greylist bring GeoIP support back, utilizing libmaxminddb implemented by Markus Wennrich Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: bugzilla.freebsd@omnilan.de CC: m.tsatsenko@gmail.com Flags: maintainer-feedback?(m.tsatsenko@gmail.com) CC: m.tsatsenko@gmail.com Created attachment 205923 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D205923&action= =3Dedit Add libmaxminddb (GeoIP2) support to mitler-greylist In r490200, GeoIP support was authoritatively removed. The reason was that Maxmind no longer provides geolocation data in the legacy format used by net/GeoIP, which milter-greylist uses. (https://svnweb.freebsd.org/ports?view=3Drevision&revision=3D490211). While there is a UPDATING record, this action has an unexpected and big imp= act for users already using GeoIP databases with milter-greylist. It had to be left to their decision if they want to use outdated data, or abandon GeoIP support at all. Especially in the milter-greylist case, I can't imagine anybody would consider removing GeoIP support was the correct solution. I g= uess they would live with outdated data until somebody skilled spends a signific= ant amount of time to implement the successor library net/libmaxminddb, which we already have in the ports tree. Thankfully, Markus Wennrich did that job. His decision was to publish a complete fork on github: https://github.com/mwennrich/milter-greylist-geoip2 I simply created a patch from his commit, keeping the existing mail/milter-greylist port using the original sources, and adding support by unconditionally applying the patch enabling support for --with-libmaxminddb. I'm not sure if it's wise to cary such a big patch containing ./configure modifications, which are done by autoconf. Maybe time to utilize autorecon= f? Please find attached a workaround for making milter-greylist GeoIP aware ag= ain. I haven't done extensive testing! In case the maintainer doesn't accept that change, please revert the GeoIP removal from milter-greylist, until anybody else offers a different solutio= n, which doesn't break production setups that badly. Btw: Any hint appreciated what milter-greylist uses ftp/curl for!? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-239334-7788>