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

e sam <> Thu, 23 July 2020 02:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B203B3A0B57 for <>; Wed, 22 Jul 2020 19:37:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.099
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=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rW4yqtc_rOlD for <>; Wed, 22 Jul 2020 19:37:15 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4951D3A0B59 for <>; Wed, 22 Jul 2020 19:37:15 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 583AA211DF; Thu, 23 Jul 2020 02:37:12 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 583AA211DF
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=heymail; t=1595471833; bh=qVVnLrRTR5WCbJgeccB5i72nhRwDqRzSyqu1HaF9fJY=; h=Date:From:To:Cc:In-Reply-To:Subject; b=RuubXAZX2qsn+LM74X9Z1eH+8DTCePYmHluJO/V8AggSQ/FgPaS/tgE7WTuATba1G h4XMkZZr16z4udIYSOKddoF3LNl1+y+wuZLkzRxjBu/JtrjcInzFhRMAnRMKVPFyfr 36SEySs4gFZp+IJan7qekb+wCDNCuJM3rkoE1OGDHZ/8nIK/ynVhtjvRwkFA6V2IGK Nr/cl/zP7eZ0HGOcAjXRt0a+izUQjJmHrP8U9waKOWj/WXujC+Ju9YwrwzjXSZ6YQU HxzPnSRmbtXJDL8sqozZvzSI8GNjTQFHBvCXiH7Z2Yz82uHd2dI05do9ONum7+ZAVW sYxjsWOW+QCfQ==
Date: Thu, 23 Jul 2020 02:37:12 +0000
From: e sam <>
To: e sam <>, Michael Richardson <>, John Levine <>,
Cc: ietf-smtp <>
Message-ID: <>
In-Reply-To: <>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f18f7d812fd1_2b562d7869435"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [ietf-smtp] broken signatures, was Curious
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\]" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 23 Jul 2020 02:37:17 -0000

Dave Crocker <> wrote:
“On 7/22/2020 7:05 PM, e sam wrote:
> I'm just talking about if there IS a problem, which I don't know if 
> there is or isn't one..

For an effort of the narrow type intended here, when someone posts about 
a problem, they should include documentation that it is actually a problem.

It's easy to hypothesize about an infinite range of possibilities. It 
takes work to document the realities.


Dave Crocker
Brandenburg InternetWorking

ietf-smtp mailing list”

I didn't say that there was a problem or not, all I was saying is that I get the feeling that if there was a problem, it is a minor one compared to the other stuff on the EMAILCORE agenda. Other people in this mailing list have already brought up their own problems. In fact, in my first post which sparked all this discussion I just said it was something to consider. If people thought there was a problem, then we could take it further. If there wasn't a problem, then we could leave it at that.

I agree with your last paragraph about the work and documenting it!