[smtpd/qpsmtpd] 974806: Dmarc result note (#261)
[email protected] (GitHub) Tue, 03 May 2016 10:35:44 -0700
| Newsgroups | perl.qpsmtpd.dev |
|---|---|
| Message-ID | <5728e17033dd8_4dad3f8ac56ff2b8637b5@hookshot-fe1-cp1-prd.iad.github.net.mail> |
----==_mimepart_5728e170339fd_4dad3f8ac56ff2b8636b3
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Branch: refs/heads/master
Home: https://github.com/smtpd/qpsmtpd
Commit: 9748064889d0ed7b2214d566125bd68e659e57ec
https://github.com/smtpd/qpsmtpd/commit/9748064889d0ed7b2214d566125bd68e659e57ec
Author: Daniel B <[email protected]>
Date: 2016-05-03 (Tue, 03 May 2016)
Changed paths:
M plugins/dmarc
Log Message:
-----------
Dmarc result note (#261)
* Update data_post_headers documentation
We cannot reject at this stage, which is only there to alter headers.
Fix #258
* DMARC plugin: reject in data_post
Followup of #258: we cannot reject a connection during data_post_headers. So add a new hook in data_post to do the real rejection
* Add a note with dmarc_result
So other plugins can easily check DMARC status.
For example, a simple plugin can be added after DMARC when SPF hard failed, but no DMARC policy is published (so no rejection by the DMARC plugin).
With this note, we can easily check the result of SPF and DMARC and reject if the first is failed, and the second is none
----==_mimepart_5728e170339fd_4dad3f8ac56ff2b8636b3--