The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: d235j.1@gmail.com (David Ryskalczyk)
Subject: Mangled and non-mangled TUHS mail lists
Date: Mon, 2 Oct 2017 09:34:18 -0400	[thread overview]
Message-ID: <EE7FBA19-0C8A-4138-9E63-C3271BFCB2A8@gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.02.1710020837230.94910@frieza.hoshinet.org>

Unfortunately if DKIM is to be preserved, and the DKIM signature covers the Subject line (which it usually does), changing the Subject would break the signature and cause the bouncing problem to start happening again.

Looking at Warren's message at the beginning of this thread, I see the following DKIM signature:

DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tuhs.org; s=dkim;
	t=1506828345; bh=JrrWTXe8/s8WUvyQhbjteoiXK8kMtqkyNHZyzoe+YwE=;
	h=Date:From:To:Subject:List-Id:List-Unsubscribe:List-Archive:
	 List-Post:List-Help:List-Subscribe:From;
	b=1bchv7u0p3glxS5aOdV2a2LcTPR/UNiVdxne762fZ8jTn8/PY6UDE0CEqfP1rS20G
	 t6uVy6iNk/xoDDKPeKGH4Tt8lSKqujoN682dKcAkHsM8/1ADamNo9ep/J7qiLUQIm7
	 62+lEKp7NZL8zsA2H+5iXtlcuKKIWJ3cTvhdhFLA=

This means that changing any of the headers listed under h= will break the signature (and cause bounces). This unfortunately includes the Subject.

For lists the alter the From: line, I prefer if they put the original From: address in the Cc: line as that means a reply-all goes both to the list and the originator. However I'm not sure whether this will cause DKIM issues as well (I haven't dug deep enough).

There's some discussion of this in RFC6377, unfortunately without a good solution given.

David

> On Oct 2, 2017, at 8:38 AM, Steve Nickolas <usotsuki at buric.co> wrote:
> 
> On Mon, 2 Oct 2017, jason-tuhs at shalott.net wrote:
> 
>> All else being equal, I would prefer the old list retain the old behaviour (i.e., to add the "[TUHS]" string to the Subject line) if possible.
> 
> Same.  My mailbox gets a lot of input from a lot of places and I generally use the subject line to optically filter - the tag really helps.
> 
> -uso.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171002/8b129567/attachment-0001.html>


  reply	other threads:[~2017-10-02 13:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-01  3:25 Warren Toomey
2017-10-01 14:00 ` Clem Cole
2017-10-01 14:08   ` Don Hopkins
2017-10-02  1:01 ` Dave Horsfall
2017-10-02  8:22   ` jason-tuhs
2017-10-02 12:38     ` Steve Nickolas
2017-10-02 13:34       ` David Ryskalczyk [this message]
2017-10-03  0:51         ` Dave Horsfall
2017-10-03  2:19           ` Steve Nickolas
2017-10-03  3:25             ` Grant Taylor
2017-10-03  3:33               ` Dave Horsfall
2017-10-03  3:55                 ` Grant Taylor
2017-10-03  4:17                   ` Dave Horsfall
2017-10-03  4:12                 ` Kurt H Maier
2017-10-03  7:40                   ` Ian Zimmerman
2017-10-03 14:08                 ` Steffen Nurpmeso
2017-10-03 18:20                   ` Grant Taylor
2017-10-03 18:43                     ` Ian Zimmerman
2017-10-03 21:59                       ` Grant Taylor
2017-10-03 18:49                     ` Steffen Nurpmeso
2017-10-03 21:54                       ` Grant Taylor
2017-10-03 22:00                         ` Mangled and non-mangled TUHS mail lists [ enough already? ] Jon Steinhart
2017-10-04 20:17                         ` Mangled and non-mangled TUHS mail lists Steffen Nurpmeso
2017-10-04  2:28                       ` Dave Horsfall
2017-10-04 20:59                         ` Steffen Nurpmeso
2017-10-03 10:12               ` Steve Nickolas
2017-10-03 19:21                 ` Bakul Shah

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=EE7FBA19-0C8A-4138-9E63-C3271BFCB2A8@gmail.com \
    --to=d235j.1@gmail.com \
    /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).