<!-- The default stylesheets generate both chapters and sections with <h2>
headings in the HTML. The argument is that the HTML headings don't go deep
enough to match the DocBook levels. But surely it would be better to stop them
-at the bottom end? Anyway, the Exim documents have only one level of section
-within chapters, and even if they went to two, it wouldn't exhaust HTML's
-capabilities. So I have copied the style stuff here, making a 1-character
+at the bottom end? Anyway, the Exim documents have no more than two levels of
+section within chapters, which won't exhaust HTML's capabilities.
+So I have copied the style stuff here, making a 1-character
change from "+ 1" to "+ 2" in roughly the middle. -->
<xsl:template name="section.heading">
that headers will be in /usr/local/include, and that the libraries
are in /usr/local/lib.
-. subsection
+.subsection Configuration SSECDMARCCONFIG
+.cindex DMARC configuration
There are three main-configuration options:
.cindex DMARC "configuration options"
the dsn_from option, and <> is used for the
envelope from.
-. I wish we had subsections...
-
+.subsection Controls SSECDMARCCONTROLS
.cindex DMARC controls
+
By default, the DMARC processing will run for any remote,
non-authenticated user. It makes sense to only verify DMARC
status of messages coming from remote, untrusted sources. You can
There are no options to either control. Both must appear before
the DATA acl.
-. subsection
+.subsection ACL SSECDMARCACL
+.cindex DMARC "ACL condition"
DMARC checks cam be run on incoming SMTP messages by using the
&"dmarc_status"& ACL condition in the DATA ACL. You are required to
is any error, including no DMARC record.
.endlist
-. subsection
+.subsection Logging SSECDMARCLOGGING
+.cindex DMARC logging
By default, Exim's DMARC configuration is intended to be
non-intrusive and conservative. To facilitate this, Exim will not
enable sending DMARC forensic reports
.endlist
-. subsection
+.subsection Example SSECDMARCEXAMPLE
+.cindex DMARC example
Example usage:
.code