amorfo77/parsedmarc
1
0
Fork 0
mirror of https://github.com/domainaware/parsedmarc.git synced 2026-03-14 10:41:25 +00:00
Code Issues Projects Releases Wiki Activity

Update docs

Browse Source
This commit is contained in:
Sean Whalen
2023-05-03 16:55:21 -04:00
parent 18504f46b4
commit b2139cbbe5
4 changed files with 31 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
_sources/mailing-lists.md.txt
View File

@@ -134,6 +134,13 @@ Where `list.example.com` the list ID, and `en` is the language.
Then restart mailman core.
### LISTSERV
[LISTSERV 16.0-2017a] and higher will rewrite the From header for domains
that enforce with a DMARC quarantine or reject policy.
Some additional steps are needed for Linux hosts.
### Workarounds
If a mailing list must go **against** best practices and
@@ -144,7 +151,7 @@ no longer spoof email addresses with domains protected by DMARC.
Configuration steps for common mailing list platforms are listed below.
### Mailman 2
#### Mailman 2
Navigate to Privacy Options> Sending Filters, and configure the settings below
@@ -170,7 +177,7 @@ the original sender.
Choose the option that best fits your community.
:::
### Mailman 3
#### Mailman 3
In the DMARC Mitigations tab of the Settings page, configure the settings below
@@ -193,13 +200,6 @@ accidentally reply to the entire list, when they only intended to reply to
the original sender.
:::
### LISTSERV
[LISTSERV 16.0-2017a] and higher will rewrite the From header for domains
that enforce with a DMARC quarantine or reject policy.
Some additional steps are needed for Linux hosts.
[joe nelson]: https://begriffs.com/posts/2018-09-18-dmarc-mailing-list.html
[listserv 16.0-2017a]: https://www.lsoft.com/news/dmarc-issue1-2018.asp
[rfc 2369]: https://tools.ietf.org/html/rfc2369

24
dmarc.html
View File

@@ -72,10 +72,12 @@
<li class="toctree-l3"><a class="reference internal" href="#do-not">Do not</a></li>
<li class="toctree-l3"><a class="reference internal" href="#mailman-2">Mailman 2</a></li>
<li class="toctree-l3"><a class="reference internal" href="#mailman-3">Mailman 3</a></li>
<li class="toctree-l3"><a class="reference internal" href="#workarounds">Workarounds</a></li>
<li class="toctree-l3"><a class="reference internal" href="#id1">Mailman 2</a></li>
<li class="toctree-l3"><a class="reference internal" href="#id2">Mailman 3</a></li>
<li class="toctree-l3"><a class="reference internal" href="#listserv">LISTSERV</a></li>
<li class="toctree-l3"><a class="reference internal" href="#workarounds">Workarounds</a><ul>
<li class="toctree-l4"><a class="reference internal" href="#id1">Mailman 2</a></li>
<li class="toctree-l4"><a class="reference internal" href="#id2">Mailman 3</a></li>
</ul>
</li>
</ul>
</li>
</ul>
@@ -392,6 +394,12 @@ command line instead, for example:</p>
<p>Where <code class="docutils literal notranslate"><span class="pre">list.example.com</span></code> the list ID, and <code class="docutils literal notranslate"><span class="pre">en</span></code> is the language.</p>
<p>Then restart mailman core.</p>
</section>
<section id="listserv">
<h3>LISTSERV<a class="headerlink" href="#listserv" title="Permalink to this heading"></a></h3>
<p><a class="reference external" href="https://www.lsoft.com/news/dmarc-issue1-2018.asp">LISTSERV 16.0-2017a</a> and higher will rewrite the From header for domains
that enforce with a DMARC quarantine or reject policy.</p>
<p>Some additional steps are needed for Linux hosts.</p>
</section>
<section id="workarounds">
<h3>Workarounds<a class="headerlink" href="#workarounds" title="Permalink to this heading"></a></h3>
<p>If a mailing list must go <strong>against</strong> best practices and
@@ -400,9 +408,8 @@ list administrator must configure the list to replace the From address of the
message (also known as munging) with the address of the mailing list, so they
no longer spoof email addresses with domains protected by DMARC.</p>
<p>Configuration steps for common mailing list platforms are listed below.</p>
</section>
<section id="id1">
<h3>Mailman 2<a class="headerlink" href="#id1" title="Permalink to this heading"></a></h3>
<h4>Mailman 2<a class="headerlink" href="#id1" title="Permalink to this heading"></a></h4>
<p>Navigate to Privacy Options&gt; Sending Filters, and configure the settings below</p>
<table class="docutils align-default">
<colgroup>
@@ -437,7 +444,7 @@ the original sender.</p>
</div>
</section>
<section id="id2">
<h3>Mailman 3<a class="headerlink" href="#id2" title="Permalink to this heading"></a></h3>
<h4>Mailman 3<a class="headerlink" href="#id2" title="Permalink to this heading"></a></h4>
<p>In the DMARC Mitigations tab of the Settings page, configure the settings below</p>
<table class="docutils align-default">
<colgroup>
@@ -467,11 +474,6 @@ accidentally reply to the entire list, when they only intended to reply to
the original sender.</p>
</div>
</section>
<section id="listserv">
<h3>LISTSERV<a class="headerlink" href="#listserv" title="Permalink to this heading"></a></h3>
<p><a class="reference external" href="https://www.lsoft.com/news/dmarc-issue1-2018.asp">LISTSERV 16.0-2017a</a> and higher will rewrite the From header for domains
that enforce with a DMARC quarantine or reject policy.</p>
<p>Some additional steps are needed for Linux hosts.</p>
</section>
</section>
</section>

16
mailing-lists.html
View File

@@ -276,6 +276,12 @@ command line instead, for example:</p>
<p>Where <code class="docutils literal notranslate"><span class="pre">list.example.com</span></code> the list ID, and <code class="docutils literal notranslate"><span class="pre">en</span></code> is the language.</p>
<p>Then restart mailman core.</p>
</section>
<section id="listserv">
<h3>LISTSERV<a class="headerlink" href="#listserv" title="Permalink to this heading"></a></h3>
<p><a class="reference external" href="https://www.lsoft.com/news/dmarc-issue1-2018.asp">LISTSERV 16.0-2017a</a> and higher will rewrite the From header for domains
that enforce with a DMARC quarantine or reject policy.</p>
<p>Some additional steps are needed for Linux hosts.</p>
</section>
<section id="workarounds">
<h3>Workarounds<a class="headerlink" href="#workarounds" title="Permalink to this heading"></a></h3>
<p>If a mailing list must go <strong>against</strong> best practices and
@@ -284,9 +290,8 @@ list administrator must configure the list to replace the From address of the
message (also known as munging) with the address of the mailing list, so they
no longer spoof email addresses with domains protected by DMARC.</p>
<p>Configuration steps for common mailing list platforms are listed below.</p>
</section>
<section id="id1">
<h3>Mailman 2<a class="headerlink" href="#id1" title="Permalink to this heading"></a></h3>
<h4>Mailman 2<a class="headerlink" href="#id1" title="Permalink to this heading"></a></h4>
<p>Navigate to Privacy Options&gt; Sending Filters, and configure the settings below</p>
<table class="docutils align-default">
<colgroup>
@@ -321,7 +326,7 @@ the original sender.</p>
</div>
</section>
<section id="id2">
<h3>Mailman 3<a class="headerlink" href="#id2" title="Permalink to this heading"></a></h3>
<h4>Mailman 3<a class="headerlink" href="#id2" title="Permalink to this heading"></a></h4>
<p>In the DMARC Mitigations tab of the Settings page, configure the settings below</p>
<table class="docutils align-default">
<colgroup>
@@ -351,11 +356,6 @@ accidentally reply to the entire list, when they only intended to reply to
the original sender.</p>
</div>
</section>
<section id="listserv">
<h3>LISTSERV<a class="headerlink" href="#listserv" title="Permalink to this heading"></a></h3>
<p><a class="reference external" href="https://www.lsoft.com/news/dmarc-issue1-2018.asp">LISTSERV 16.0-2017a</a> and higher will rewrite the From header for domains
that enforce with a DMARC quarantine or reject policy.</p>
<p>Some additional steps are needed for Linux hosts.</p>
</section>
</section>
</section>

2
searchindex.js
View File

File diff suppressed because one or more lines are too long