Re: [ietf-smtp] broken signatures, was Curious

e sam <e2009@hey.com> Thu, 23 July 2020 02:05 UTC

Return-Path: <e2009@hey.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F18D03A0B2E for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 19:05:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hey.com
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 JPToEIEpdd09 for <ietf-smtp@ietfa.amsl.com>; Wed, 22 Jul 2020 19:05:32 -0700 (PDT)
Received: from 101d.trial.hey.com (101d.trial.hey.com [204.62.115.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FB7C3A0B29 for <ietf-smtp@ietf.org>; Wed, 22 Jul 2020 19:05:32 -0700 (PDT)
Received: from hey.com (bigip-vip.rw-ash-int.37signals.com [10.20.0.17]) by 101.trial.hey.com (Postfix) with ESMTP id 13D8D40FD8; Thu, 23 Jul 2020 02:05:29 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 101.trial.hey.com 13D8D40FD8
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hey.com; s=heymail; t=1595469931; bh=17j1qNZmtBijYEyLKX37Plt7dt0hHP8lKPwAw21Xbjk=; h=Date:From:To:Cc:In-Reply-To:Subject; b=aO8nbq69zanbO2KczyjhQJvw/jc6+FdtcsA0Y7iWmDJ0uZnPxrO9QJt4K2i4OI+0j RdPkWOCpPmmX85wDRAD+Edd1n60ChXkk615DFu5THulfDQrXB9pmSn/g8Hu8MxdjeD qoaVt003k0bwq4RAK5CLW69OVAsHv3q3TdiIA0HRgXdCa9QL5R8kacgXSEIUlsW5rz m3KEIqQaYJPMysH4umDKNs8MHRgw5cFRiivmxrLEQC6c2fsAhjDkJf7jDWMhytTyzm ZTtjZ24LEvLpnS/4Sti4+T9jZfT//RpV49I36yliUu1umkng6Xk0rSPIpJwJUmF9EP zVVEbrYfYcrvg==
Date: Thu, 23 Jul 2020 02:05:29 +0000
From: e sam <e2009@hey.com>
To: Michael Richardson <mcr@sandelman.ca>, John Levine <johnl@taugh.com>
Cc: ietf-smtp <ietf-smtp@ietf.org>
Message-ID: <55e6444aa46a9f28a13bddba70a015c00ada6cd3@hey.com>
In-Reply-To: <e76b9ff-63d4-6482-db9b-39fd404a649d@taugh.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f18f06959704_2a912d78193bc"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/IuoCCuxRYcuHwcGyAzjJHVgdGQE>
Subject: Re: [ietf-smtp] broken signatures, was Curious
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jul 2020 02:06:39 -0000

John Levine <johnl@taugh.com> wrote:
“> I personally think that if there is enough time for it in EMAILCORE, then junk mail headers can be addressed.

Once again, it would be useful to understand what problem you believe 
needs to be solved. I don't see one, and based on the discussion to date, 
I don't think I'm unusual in that.

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

_______________________________________________
ietf-smtp mailing list
ietf-smtp@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-smtp”


Well isn't that what we are discussing? There may be an issue, but if it exists I wouldn't think it would be a big issue

Like I said, if there is a problem, it may not be a big one.

Other people have been discussing about if there is a problem, my opinions are mixed on whether or not putting more bandwidth on this issue is necessary.

I'm just talking about if there IS a problem, which I don't know if there is or isn't one..