Dear Maintainer, sa-exim appears to be incompatible with exim4 4.99. I upgraded yesterday, and my exim4 mainlog filled with messages like this: 2025-11-19 08:33:43 1vLl7n-0000000Ei4N-2kmb local_scan() library open failed - message temporarily rejected 2025-11-19 08:33:43 1vLl7n-0000000Ei4N-2kmb F=bounces+848413-f909-me@sgmail.github.com H=o6.sgmail.github.com [192.254.113.101] P=esmtps temporarily rejected by local_scan(): Local configuration error - local_scan() library failure\n/usr/lib/exim4/local_scan/sa-exim.so: undefined symbol: expand_string I tried to rebuild sa-exim, but that fails with various compilation errors with exim4 4.99. Downgrading to 4.98.2 made it work again.
[...] Hello, there was a bug in exim 4.99 up to 4.99-4, expand_string was not available for local_scan. Also the ABI changed (expand_string is a macro now) and the API also changed: -extern int smtp_fflush(void); +extern int smtp_fflush(BOOL); As a side-effect of the change to expand_string() incorrect signedness of the args to expand_string() (signed char *) causes a compilation error. exim4 4.99-5 and newer bumped LOCAL_SCAN_ABI_VERSION_MINOR this version cannot be installed together with sa-exim 4.2.1-22 cu Andreas
On 2025-11-28 Andreas Metzler <ametzler@bebt.de> wrote: [...] Hello, Find attached an (almost untested) patch to fix the FTBFS. I do not intend to NMU since I would rather drop the localscan_dlopen patch to exim (and sa-exim). cu Andreas
Hi Andreas, I seem to have dropped out of the To: for the patch (expand_string_unsigned_char.diff), but I dug it out of the bug report and can confirm that I can successfully build sa-exim with 4.99.1-1 and that it seems to work correctly. Thank you, Omen