https://bugs.exim.org/show_bug.cgi?id=3083
Bug ID: 3083
Summary: Allow multiple uses of options defining servers for
database lookups
Product: Exim
Version: N/A
Hardware: All
OS: All
Status: NEW
Severity: wishlist
Priority: medium
Component: Lookups
Assignee: unallocated@exim.org
Reporter: lehmann@cnm.de
CC: exim-dev@lists.exim.org
In complex MTA setups that include many servers (for example mailin, relay and
smart host, each at scale), the exim configuration typically includes different
independent features (for example greylisting and DKIM) according to the
specific service while sharing a common base.
Things are already a bit complicated, because the configuration of each feature
often requires several blocks throughout the whole configuration. So instead of
using one exim ".include" per feature it's more likely to use some kind of
templating language like Jinja2, empowering you with conditional inline
includes.
It get's really tricky though when independent features require independent
datasources, yet you can only use options like mysql_servers, pgsql_servers or
redis_servers once globally. It's quite a challenge to provide a list to exim,
separated by colons, when the features are agnostic of each other and the
datasources required before and after them. Exim will return an error on
multiple uses:
LOG: PANIC DIE
Exim configuration error in line 65 of /etc/exim4/exim4.conf:
"pgsql_servers" option set for the second time
Therefore, I'd like to suggest to allow multiple uses of these options. Instead
of defining all datasources at once, exim should add server(s) to the global
dictionary each time the option is used.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-dev.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-dev-unsubscribe@lists.exim.org
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
Bug ID: 3083
Summary: Allow multiple uses of options defining servers for
database lookups
Product: Exim
Version: N/A
Hardware: All
OS: All
Status: NEW
Severity: wishlist
Priority: medium
Component: Lookups
Assignee: unallocated@exim.org
Reporter: lehmann@cnm.de
CC: exim-dev@lists.exim.org
In complex MTA setups that include many servers (for example mailin, relay and
smart host, each at scale), the exim configuration typically includes different
independent features (for example greylisting and DKIM) according to the
specific service while sharing a common base.
Things are already a bit complicated, because the configuration of each feature
often requires several blocks throughout the whole configuration. So instead of
using one exim ".include" per feature it's more likely to use some kind of
templating language like Jinja2, empowering you with conditional inline
includes.
It get's really tricky though when independent features require independent
datasources, yet you can only use options like mysql_servers, pgsql_servers or
redis_servers once globally. It's quite a challenge to provide a list to exim,
separated by colons, when the features are agnostic of each other and the
datasources required before and after them. Exim will return an error on
multiple uses:
LOG: PANIC DIE
Exim configuration error in line 65 of /etc/exim4/exim4.conf:
"pgsql_servers" option set for the second time
Therefore, I'd like to suggest to allow multiple uses of these options. Instead
of defining all datasources at once, exim should add server(s) to the global
dictionary each time the option is used.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-dev.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-dev-unsubscribe@lists.exim.org
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/