Opened 13 months ago

Closed 9 months ago

#91 closed defect (out-of-scope)

Revise Authentication-Results Result Registry Update

Reported by: vesely@… Owned by: todd.herr@…
Priority: minor Milestone: Deliverable #3 (changes to DMARC base spec + DMARC Usage Guide
Component: dmarc-bis Version:
Severity: - Keywords: Authentication-Results
Cc:

Description

The current draft only specifies pass, fail, permerror, and temperror. Those result names don't reflect the effective policy. In particular, a mail filter which evaluates DMARC status during the SMTP exchange can enforce a policy of p=reject, but cannot dispose how to treat p=quarantine. It needs to convey the results of DMARC authentication checks to a downstream agent.

I propose to add two new result name codes, named after the policy requests:

dmarc=quarantine, and

dmarc=reject (of course, you only see this if the filter didn't honor the request).

See also https://mailarchive.ietf.org/arch/msg/dmarc/iWveRQ53XlFSl_CZwLfoqbbaKDs

Change History (4)

comment:1 Changed 13 months ago by vesely@…

See also tickets #86 and #90

Last edited 13 months ago by vesely@… (previous) (diff)

comment:2 Changed 9 months ago by todd.herr@…

  • Owner set to todd.herr@…
  • Status changed from new to accepted

comment:3 Changed 9 months ago by todd.herr@…

  • Status changed from accepted to assigned

comment:4 Changed 9 months ago by todd.herr@…

  • Resolution set to out-of-scope
  • Status changed from assigned to closed

Out of scope, as it calls for modification of Authentication-Results RFCs.

Also probably not necessary, since mail receiving sites that implement DMARC have already figured out ways to convey placement decisions made by their MTA layer to their message deliver and storage layers.

Note: See TracTickets for help on using tickets.