RFC 7489 was published last month. Using zdkimfilter 1.5 it is easy to meet DMARC minimum implementation requirements --section 8 of the RFC. That section stresses the ability to send and receive reports, which is the most noteworthy addition with respect to ADSP. It makes mail servers of different domains interact with one another. Now, I'm not so clever as to tell exactly what should be memorized and for how long, but I'm more and more convinced that a database of peers is necessary for SMTP to operate sensibly.
Personally, I BCC outgoing DMARC reports to myself, and read them using the XSLT at http://www.tana.it/sw/dmarc-xsl/. When I get the feeling that only phishes fail DMARC check, I enable DMARC for that domain. ADSP can be enabled per domain too, in the new version. In the other cases, when DMARC fails amiss, I'm comforted that remote domains hear my voice, however statistically irrelevant it may be. For incoming reports, there is no way to publish per-domain policies, so there's not much to decide. I'm open to suggestions. Version 1.5 also fixes a couple of issues, long From:, garbled logs. There are some additional requirements, see release notes. Feel like giving it a try? http://www.tana.it/sw/zdkimfilter/ Ale ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
