-
Notifications
You must be signed in to change notification settings - Fork 60
Description
Hello
$ uname -v
FreeBSD 14.2-RELEASE-p1 GENERIC
$ opendmarc -V
opendmarc: OpenDMARC Filter v1.4.2
SMFI_VERSION 0x1000001
libmilter version 1.0.1
Active code options:
WITH_SPF
WITH_SPF2
When I was looking for the reason why the arc=fail in my outgoing reports, I noticed that in the opendmarс-reports.in expects 1 for arc=pass
OpenDMARC/reports/opendmarc-reports.in
Line 715 in 9cebf72
| case 1 { $arcstr = "pass"; } |
In README file written what arc must be 0 for pass.
Line 183 in 9cebf72
| arc ARC evaluation (0 = pass, 2 = fail) |
Value "arc" in opendmarc. database may be 0 or 7, but result in outgoing reports will be arc=fail.
Both reports from this data have arc=fail.
- .dat file:
arc 0
arc_policy 2 json:[{ "i": 3, "d":"google.com", "s":"arc-20240605", "ip":"" }, { "i": 2, "d":"google.com", "s":"arc-20240605", "ip":"" }, { "i": 1, "d":"mydomen.com", "s":"sel15", "ip":"" }]
action 2
report:
<type>local_policy</type> <comment>arc=fail as[3].d=google.com as[3].s=arc-20240605 as[2].d=google.com as[2].s=arc-20240605 as[1].d=mydomen.com as[1].s=sel15</comment>
2. .dat file:
arc 7
arc_policy 2 json:[]
action 0
report:
<type>local_policy</type> <comment>arc=fail</comment>
In my case, changing case 1 to case 0 in opendmarc.in does not affect the overall result in the sent report, in it the value of arc is taken from $arcpolicy, which is always 2 for me (I have not yet found why).