# exim -bV
Exim version 4.92.3 #0 (FreeBSD 12.0) built 12-Feb-2020 04:08:17
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018
Probably Berkeley DB version 1.8x (native mode)
Support for: crypteq iconv() IPv6 use_setclassresources PAM Perl Expand_dlfunc OpenSSL Content_Scanning DKIM DNSSEC Event I18N OCSP PRDR
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch mysql passwd
Authenticators: cram_md5 dovecot plaintext spa
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp
Malware: f-protd f-prot6d drweb fsecure sophie clamd avast sock cmdline
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
2020-02-16 22:15:25 Warning: purging the environment.
Suggested action: use keep_environment.
Configuration file is /usr/local/etc/exim/configure
There is no SPF under 'Support for' list... Exim fails to start with SPF related ACL rules. Why there is no support for SPF in so popular MTA like Exim in so modern OS like FreeBSD?
Fix Summary and assign.
Note to submitter: "Ports Infrastructure" is a category we use only for the build farm at FreeBSD.org.
Please learn how to build the FreeBSD ports. SPF option is presented in the list of the available port build options.
This is not an answer.
I would like to know what is the problem for you as Exim maintainer to build package with SPF enabled. We have XXI century already and as FreeBSD is OS used mainly on servers, I don't see any reason why this option could not be enabled be default in binary, especially that with v4.91 this feature has been promoted from experimental to supported. Having this option disabled, you disallow from running SPF checks in incoming SMTP by using ACL rules.