[opendmarc-users] Missing dmarc results header on incoming mail

[Juri Haberland]

On 14.07.2017 17:06, Dominic Raferd wrote:
> On 14 July 2017 at 14:25, Simon Wilson <simon at simonandkate.net> wrote:

>> So it would appear that opendmarc can interpret the Received-SPF header. I
>> do not have a dummy header being set. Unless I'm missing something :)
>>
>> Also, I fixed the issue of amamisd-new over-writing Authentication-Results
>> by having it use a different authservid (server name). So I can choose
>> which one I want to use now...
>>
> 
> On reflection, testing is not so easy. The email has a valid DKIM header so
> it will pass DMARC testing regardless of the SPF, and (unfortunately)
> opendmarc doesn't record the individual results (dkim, spf) for its
> testing. An email with valid SPF but without DKIM header (or a 'bad' DKIM
> header) would be a true test.​

It does record the individual results in the history file - see the
HistoryFile parameter in the config file. Unfortunately these results are
not logged in clear text, but as numbers:

# define DMARC_POLICY_SPF_OUTCOME_NONE          (0)
# define DMARC_POLICY_SPF_OUTCOME_PASS          (1)
# define DMARC_POLICY_SPF_OUTCOME_FAIL          (2)
# define DMARC_POLICY_SPF_OUTCOME_TMPFAIL       (3)
# define DMARC_POLICY_SPF_ALIGNMENT_PASS        (4)
# define DMARC_POLICY_SPF_ALIGNMENT_FAIL        (5)

# define DMARC_POLICY_DKIM_OUTCOME_NONE         (0)
# define DMARC_POLICY_DKIM_OUTCOME_PASS         (1)
# define DMARC_POLICY_DKIM_OUTCOME_FAIL         (2)
# define DMARC_POLICY_DKIM_OUTCOME_TMPFAIL      (3)
# define DMARC_POLICY_DKIM_ALIGNMENT_PASS       (4)
# define DMARC_POLICY_DKIM_ALIGNMENT_FAIL       (5)

  Juri