Re: [ietf-822] don't need a permission to re-sign header

"John R Levine" <johnl@taugh.com> Tue, 22 April 2014 23:57 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF5231A029A for <ietf-822@ietfa.amsl.com>; Tue, 22 Apr 2014 16:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level:
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mkvlff5hXuj9 for <ietf-822@ietfa.amsl.com>; Tue, 22 Apr 2014 16:56:55 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id A23B41A0283 for <ietf-822@ietf.org>; Tue, 22 Apr 2014 16:56:55 -0700 (PDT)
Received: (qmail 53646 invoked from network); 22 Apr 2014 23:56:49 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=d18d.535701c1.k1404; bh=teTwrdsXkohzei/uKQoQ4b6TrA1YMpOH+fcHl1xKFiQ=; b=Wk+mGf3R3nBPiP18o2kmT5IQoIf3J/gTC3NYsuXCRyaNT4U1NKeSu7+gARKmkQZdYjm4YG8H+vesv6IABOY7iKbb5E1FXNNK/wNOfJJkUz9u5VDcT4NmDgSLjXCYR3pZjjIKdlmH0DGlTMGqHVlO3fsXjc20lOhozladkdZ4SRL3wsJOBwc3VjXQVpDKuEw3Wb8o3Y4rvRX3vHz88DgNHdr3TS544UBS5OsoLUgjzd7yKXnk/m7SnERFLfmoU+7f
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=d18d.535701c1.k1404; bh=teTwrdsXkohzei/uKQoQ4b6TrA1YMpOH+fcHl1xKFiQ=; b=ehQDJfvvGB+d0KoH98zrCjOQ/+e6V6dqQfaKOKHmAQaLOmUolJHXCeKsM4sYiBEWsxn3oYZGzInghSDCqz4Z6LSAEKA2LqDW4fkECKg/9FULYy1leNykI+YxWp0Gb+6PvbrNHB1/oZ3pSbuT1nUZog0CKITC/vft+n2bcqxzzpB9Og1ayKwAc7KRjTyJmyDE2QMo374tZbE3XUg44S70gREJpftlEKeWBrcEcQrkUQlPB+Gh7ufW9mvIIL9KtsXw
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 22 Apr 2014 23:56:49 -0000
Date: Tue, 22 Apr 2014 19:56:48 -0400
Message-ID: <alpine.BSF.2.00.1404221830420.75229@joyce.lan>
From: John R Levine <johnl@taugh.com>
To: Ned Freed <ned.freed@mrochek.com>
In-Reply-To: <01P6Y9IJSOEG000052@mauve.mrochek.com>
References: <535646AA.2080400@pscs.co.uk> <20140422202403.42908.qmail@joyce.lan> <01P6Y9IJSOEG000052@mauve.mrochek.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/jXqwPh0bLYUMtkX1LSZoLSZEaO8
Cc: ietf-822@ietf.org
Subject: Re: [ietf-822] don't need a permission to re-sign header
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 23:57:00 -0000

>> I've said for years that lists should sign
>> their mail with their own DKIM keys, and recipients should look at
>> those list signatures to filter the mail.
>
> I'm not even sure that's necessary, but of course it can't hurt. Indeed, right
> now, with the exception of IETF lists, having a signature makes the odds it's
> spam more, not less, likely.

I think that depends on your mail stream.  Google signs all their mail 
including gmail and hosted domains, and that's a big chunk of the mail I 
get.  Yahoo signs all theirs, too.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.