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

Ned Freed <ned.freed@mrochek.com> Wed, 23 April 2014 00:17 UTC

Return-Path: <ned.freed@mrochek.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 0ED6B1A02AE for <ietf-822@ietfa.amsl.com>; Tue, 22 Apr 2014 17:17:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level:
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 r_JaTAWRA0q2 for <ietf-822@ietfa.amsl.com>; Tue, 22 Apr 2014 17:17:50 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id BAD281A02B4 for <ietf-822@ietf.org>; Tue, 22 Apr 2014 17:17:50 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6YDM0I6CG0002ZK@mauve.mrochek.com> for ietf-822@ietf.org; Tue, 22 Apr 2014 17:12:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1398211962; bh=N4GYXTGGPXUbbghTBw2MJPUymlK3LDBgwmApWSkCadI=; h=Cc:Date:From:Subject:In-reply-to:References:To; b=ol8Qs/rJCeUs8w+bJ8RSteEHt89D4HPmD+6e+z3trr2LSz5LyBthNyllEWZaxFnkZ Q6i96smayHkRoRrS6cJJXsanWIHnJvvP2886Z31J8NExCKl2HHrL3Oig8cOkSiZ5HF zO6rW8vz26sFE//0aaMIPDwoV13StRM6Hb6yOwjQ=
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="iso-8859-1"; format="flowed"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6WZAZ2YYO000052@mauve.mrochek.com>; Tue, 22 Apr 2014 17:12:40 -0700 (PDT)
Message-id: <01P6YDLYUMPY000052@mauve.mrochek.com>
Date: Tue, 22 Apr 2014 17:11:58 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Tue, 22 Apr 2014 19:56:48 -0400" <alpine.BSF.2.00.1404221830420.75229@joyce.lan>
References: <535646AA.2080400@pscs.co.uk> <20140422202403.42908.qmail@joyce.lan> <01P6Y9IJSOEG000052@mauve.mrochek.com> <alpine.BSF.2.00.1404221830420.75229@joyce.lan>
To: John R Levine <johnl@taugh.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/6hvl3vL7f0S3eZBcmdGdDxhrQLA
Cc: ietf-822@ietf.org, Ned Freed <ned.freed@mrochek.com>
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: Wed, 23 Apr 2014 00:17:55 -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.

The overwhelming majority of list spam I get is from Google. All with
nice quthentic DKIM signatures.

				Ned