[Bug 3183] New: make $spf_result behave consistent like $dmarc_status
Exim Bugzilla via Exim-dev <[email protected]>
| Newsgroups | gmane.mail.exim.devel |
|---|---|
| Message-ID | <[email protected]/> |
https://bugs.exim.org/show_bug.cgi?id=3183
Bug ID: 3183
Summary: make $spf_result behave consistent like $dmarc_status
Product: Exim
Version: 4.99
Hardware: All
OS: All
Status: NEW
Severity: wishlist
Priority: medium
Component: String expansion
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
The documentation about $spf_result states: This contains the outcome of the
SPF check in string form, currently one of pass, fail, softfail, none, neutral,
permerror, temperror, or “(invalid)”.
warn spf =
neutral:none:temperror
set acl_m_costs = $acl_m_costs 2 +
set acl_m_flags = $acl_m_flags
spf_result_$spf_result +
warn spf =
fail:invalid:permerror:softfail
set acl_m_costs = $acl_m_costs
$acl_m_limit +
set acl_m_flags = $acl_m_flags
spf_result_${sg{$spf_result}{[()]}{}} +
warn dmarc_status =
none:norecord:temperror
set acl_m_costs = $acl_m_costs 2 +
set acl_m_flags = $acl_m_flags
dmarc_status_$dmarc_status +
warn dmarc_status =
nofrom:quarantine:reject
set acl_m_costs = $acl_m_costs
$acl_m_limit +
set acl_m_flags = $acl_m_flags
dmarc_status_$dmarc_status +
As seen in the second warn-ACL of this excerpt, the parenthesis for "invalid"
-> (invalid) must be removed manually via a regexp in order to retain
consistency. I do not understand this decision by the developers but it would
be highly appreciated if this could be corrected. Should be a very easy change.
--
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):
## [email protected]
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/