#1150546 milter-greylist fails to start when geoip rules are defined in the greylist.conf

Package:
milter-greylist
Source:
milter-greylist
Description:
Greylist milter for sendmail
Submitter:
Thomas Antepoth
Date:
2026-10-10 16:17:05 UTC
Severity:
normal
#1150546#5
Date:
2026-10-10 16:05:16 UTC
From:
To:
Dear Maintainer,

The Debian milter-greylist package is built without GeoIP support.
When GeoIP ACL rules are present in the configuration, the daemon
fails to start.

With the GeoIP ACLs enabled, the log contains:

  GeoIP support not compiled in, ignore line 38
  GeoIP support not compiled in, ignore line 39
  unexpected acl clause type 61
  milter-greylist.service: Control process exited,
  code=exited, status=70/SOFTWARE
  milter-greylist.service: Failed with result 'exit-code'

The "unexpected acl clause type 61" is located in acl.c in get_acl_clause_rec().
The "type 61" is an enum defined in acl.h as AC_GEOIP_LIST.

After commenting out the GeoIP ACL rules, milter-greylist starts successfully.

However, this removes the configured GeoIP filtering.

The Debian packaging change in commit 825fc531d0e80789cdb3d44fd080ac34871beb73
removed libgeoip-dev from the build dependencies, stating that it was obsolete
and that upstream should migrate to libmmdb-dev.

However, libgeoip-dev is still available in
Debian Trixie (version 1.6.12-11.2~deb13u1).

Could you clarify whether dropping GeoIP support was intentional?

Please consider restoring GeoIP support or updating milter-greylist
to use libmmdb-dev. If the loss of support is intentional, please
document that GeoIP ACLs can prevent the daemon from starting.

Thanks a lot in advance and best regards


Thomas Antepoth