IETF Logo Mail Archive

Re: [ietf-822] Mailing lists - assumptions

"John R Levine" <johnl@taugh.com> Sat, 19 April 2014 23:18 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 6128A1A0099 for <ietf-822@ietfa.amsl.com>; Sat, 19 Apr 2014 16:18:10 -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 UrgihYNwExgR for <ietf-822@ietfa.amsl.com>; Sat, 19 Apr 2014 16:18:08 -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 CC7EC1A0092 for <ietf-822@ietf.org>; Sat, 19 Apr 2014 16:18:07 -0700 (PDT)
Received: (qmail 63959 invoked from network); 19 Apr 2014 23:18:03 -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=f9d6.5353042b.k1404; bh=YiPStdpW/b4idpDjh4Hyu4spHnSTMB1mLckk18ZEKMk=; b=YwJYlsA7ioJSP6/s4AKzsB+VEPVinjS8o/gMIt4VK0LWxu50Y+sLF6q1Yycd9rvM5uV60a3UUPJjOvikdZV5Hp1jSTqtua2NWZefgClqxdr9FOcnIbhequzY8bbp+GUjiu9PZ3UQhfGwFH255dCG7gofhMllde1gT6ov58txGnC5xlzbmkV+2zPbtDXQsI+sicvcoYp3I0gGbEelVDeFFM12CP2DiwFrHUKGaVPuQ2DZVNkl4v52ONFfVK7MIw16
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=f9d6.5353042b.k1404; bh=YiPStdpW/b4idpDjh4Hyu4spHnSTMB1mLckk18ZEKMk=; b=bTj88YQAWEHRDPQ/J8pKnwExqh9F02u22kSEIUdXsGv2Edkq8jDPUFkgpjk2esO+7mlPkq+dbtxvgHsr5aA8WugEtnTEWg565rSv8WmanyELxOOuBYU+ESwbe0ezv8SLglz8+0Bp7MOK4hYowDVRlnHGeFFkgrp8rLVmIBpH8zoyXsbNNYhroZjbrJSEexA1135fgjgHecTlW8lPbDdl/N/iF/3ajm/W2HQH9LFgMcanUie7svUw4SutyEbbAoA7
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; 19 Apr 2014 23:18:03 -0000
Date: Sat, 19 Apr 2014 19:18:02 -0400
Message-ID: <alpine.BSF.2.00.1404191917160.94224@joyce.lan>
From: John R Levine <johnl@taugh.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
In-Reply-To: <5352FED4.8090208@qti.qualcomm.com>
References: <20140419163937.77537.qmail@joyce.lan> <5352FED4.8090208@qti.qualcomm.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/YQ_6Zn6eHUYsEO4u3PWUIxcBuDY
Cc: ietf-822@ietf.org
Subject: Re: [ietf-822] Mailing lists - assumptions
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: Sat, 19 Apr 2014 23:18:10 -0000

> n. John get a message from an example.net server that says it's "From: 
> pete@yahoo.com", and it has a cryptographically verified token that indicates 
> that it was sent directly by pete@yahoo.com from a yahoo.com server directly 
> to somelist@example.net, even though it was just example.net faking up my 
> address and using a fake token.

Now I'm really confused.  Untill a few minutes ago I was saying the token 
has to be signed, and you were (as far as I can tell) saying it doesn't. 
Now we seem to agree.

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

v2.23.0 | Report a Bug | By Email