Since the problem is the sending host then a global list should be fine
as the broken sender could be sending to:
[email protected] or [email protected]
My system is configured through a MySQL (MariaDB) database. You could
use a plain text file.
At the top of the configuration where host lists and domain lists are
specified:
###
### whitelist_hosts - specifies host that we just accept inbound - because
### they are 'broken' in some way and would otherwise be rejected by our
### checking mechanisms
###
WHITELIST_HOSTS = select host from whitelist_hosts where active='1';
hostlist whitelist_hosts = +ignore_unknown : +ignore_defer : ${lookup
mysql{WHITELIST_HOSTS}{${sg{$value}{\\n}{ : }} }}
then in my acl_check_rcpt I check the host:
###
### acl_check_rcpt: This access control list is used for every RCPT
command in
### an incoming SMTP message. The tests are run in order until the
address is
### either accepted or denied.
###
acl_check_rcpt:
//
// other stuff
//
#
# accept white listed hosts
#
accept hosts = +whitelist_hosts
log_message = RCPT: Skipped checks because
$sender_fullhost whitelisted in database
//
// other stuff
//
Mike
On 04/02/2026 05:36, MRob via Exim-users wrote:
Some user forward mails from another host, breaks SPF and other rules.
Some important forwarded mails must be whitelist.
Is any way to keep a file like:
forwardinghost.example: [email protected]
So if mail coming from aaa.forwardinghost.example is from [email protected]
then make exim will accept mail.
Is any way to parse file with that format to be used in ACL rules? Or
better solution
TIA
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## [email protected]
## Exim details at https://www.exim.org/
## Please use the Wiki with this list - https://code.exim.org/exim/wiki/wiki
