ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Gerben Wierda <gerben.wierda@rna.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: This mailing list is not DKIM (DMARC) compatible
Date: Tue, 17 Sep 2019 10:21:40 +0200	[thread overview]
Message-ID: <32AE2AE4-7E8E-4A84-96AD-B8B9B0947CEE@rna.nl> (raw)
In-Reply-To: <0c9058f4-ecff-3fdb-dd51-3a9eb8193d1b@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 5512 bytes --]

Mailman already has settings for this, but one is advised not to use the ‘munging’ option.

My guess is that if you leave the change of body in place, participants that are sending through mail servers that support SPF will fail (because of the resend by the list) and support for DKIM will fail (because of the changed body)

You will still receive the 'list-forwarded’ messages from senders who do not use DMARC, you will start missing those that do. It is unlikely that you will suddenly stop receiving all messages from the list (e.g. mine will go through as I haven’t yet turned DMARC fully on, but as soon as I do, I will be unable to send messages via this list to those at the receiving end that do DMARC checking, and that holds for more and more users.).

The sender’s email manager will also get unnecessary reports of the list server illegally sending messages on their behalf.

Most list these days that I am on already have removed the footer, and leave the Subject: line alone. Sorting can be done on other headers than Subject.

Using dmarc_moderation_action (mailman setting) means that you start to munge headers etc, which is not optimal:

https://begriffs.com/posts/2018-09-18-dmarc-mailing-list.html <https://begriffs.com/posts/2018-09-18-dmarc-mailing-list.html> writes about munging:
However this is a poor use of email, since it’s misrepresenting who originated the message. Also email clients often have a degraded interface with respect to the Reply-To header. It’s usually not visible in the message list, not used for sorting, and not added to the address book.

But whatever you guys do, make sure you are DMARC-proof to prevent running into these issues later on. Either munge, or remove the footer and the change of Subject (I would prefer the latter).

Gerben Wierda
Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/>
Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>
Architecture for Real Enterprises <https://www.infoworld.com/blog/architecture-for-real-enterprises/> at InfoWorld
On Slippery Ice <https://eapj.org/on-slippery-ice/> at EAPJ

> On 16 Sep 2019, at 22:46, Henri Menke <henrimenke@gmail.com> wrote:
> 
> I think this is better reported to Mailman.  I'm not sure to what extent list
> administrators have control over DKIM settings.
> https://gitlab.com/groups/mailman/-/issues
> 
> On 9/17/19 1:34 AM, Gerben Wierda wrote:
>> In addition: Lists should keep the From address, the Subject, and the Message totally unchanged. They should add a Sender header to indicate their relay role, and set at least the List-Id and List-Unsubscribe headers for mailbox rules and subscription management.
>> 
>> 
>> Gerben Wierda
>> Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/>
>> Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>
>> Architecture for Real Enterprises <https://www.infoworld.com/blog/architecture-for-real-enterprises/> at InfoWorld
>> On Slippery Ice <https://eapj.org/on-slippery-ice/> at EAPJ
>> 
>>> On 16 Sep 2019, at 15:21, Gerben Wierda <gerben.wierda@rna.nl <mailto:gerben.wierda@rna.nl>> wrote:
>>> 
>>> The footer that is added to each message in this list is not DKIM (and thus DMARC) compatible. DKIM requires the ability to create a signature on a set of headers and the body. By changing the body, the DKIM signature fails and the resulting messages sent by the mail list may in the future be blocked by  more and more mail servers.
>>> 
>>> Gerben Wierda
>>> Chess and the Art of Enterprise Architecture <https://ea.rna.nl/the-book/>
>>> Mastering ArchiMate <https://ea.rna.nl/the-book-edition-iii/>
>>> Architecture for Real Enterprises <https://www.infoworld.com/blog/architecture-for-real-enterprises/> at InfoWorld
>>> On Slippery Ice <https://eapj.org/on-slippery-ice/> at EAPJ
>>> 
>>> ___________________________________________________________________________________
>>> If your question is of interest to others as well, please add an entry to the Wiki!
>>> 
>>> maillist : ntg-context@ntg.nl <mailto:ntg-context@ntg.nl> / http://www.ntg.nl/mailman/listinfo/ntg-context
>>> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
>>> archive  : https://bitbucket.org/phg/context-mirror/commits/
>>> wiki     : http://contextgarden.net
>>> ___________________________________________________________________________________
>> 
>> 
>> ___________________________________________________________________________________
>> If your question is of interest to others as well, please add an entry to the Wiki!
>> 
>> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
>> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
>> archive  : https://bitbucket.org/phg/context-mirror/commits/
>> wiki     : http://contextgarden.net
>> ___________________________________________________________________________________
>> 
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 7854 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2019-09-17  8:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 13:21 Gerben Wierda
2019-09-16 13:34 ` Gerben Wierda
2019-09-16 20:46   ` Henri Menke
2019-09-17  8:21     ` Gerben Wierda [this message]
2019-09-21 16:53       ` Henning Hraban Ramm
2019-09-21 17:08         ` Henning Hraban Ramm
2019-09-25 15:17   ` Taco Hoekwater

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=32AE2AE4-7E8E-4A84-96AD-B8B9B0947CEE@rna.nl \
    --to=gerben.wierda@rna.nl \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).