Re: [ietf-smtp] MTA-STS reports via HTTPS

James Cloos <> Mon, 13 April 2020 15:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5C8503A1835 for <>; Mon, 13 Apr 2020 08:59:00 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 017QEBHCVovi for <>; Mon, 13 Apr 2020 08:58:56 -0700 (PDT)
Received: from ( [IPv6:2604:2880::b24d:a297]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6B4853A181C for <>; Mon, 13 Apr 2020 08:58:55 -0700 (PDT)
Received: by (Postfix, from userid 10) id 458D41E395; Mon, 13 Apr 2020 15:58:54 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=ore17; t=1586793534; bh=N7zj3mtDVzWO+69Qrdd3BhxzDIkp+uI9SPB4RXE6v7M=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=bh5JFGTvdfHFxJ1z0ffnxgn8Qr/LgqVVMXDUn6ldxoj4HoRJvtt5JpQ05LDy7DN21 0uVxwGwpzrtLnZ7sNJS61/u8bGSvgjUjMB4V8nlPXmkrDGnvXYHoa0pKnM+I+r+boq shiCneIWsl2zNJ7ZaNr1giv9qH5wxLI71yU0H5FFpS39NAzKji2oxdIr9jevV52/QP kSAf1N819iBmGkvjOjFNd/gKdpGFCVt7gUENjVPlYyTopmAIZJ1hcycdAY8Z2GqkPv 0u8omq4kjisABDCSzpzDgl0MYpGvHyREKcr4IjmyVRdNAjlgw62/xqnP1m5JX239bc 1nvrqjj4Mnabw==
Received: by (Postfix, from userid 500) id C8197252FC; Mon, 13 Apr 2020 15:58:47 +0000 (UTC)
From: James Cloos <>
To: "John R. Levine" <>
In-Reply-To: <alpine.OSX.2.22.407.2004130923410.3597@ary.qy> (John R. Levine's message of "13 Apr 2020 09:23:50 -0400")
References: <alpine.OSX.2.22.407.2004091338360.79592@ary.qy> <> <alpine.OSX.2.22.407.2004130923410.3597@ary.qy>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
Copyright: Copyright 2020 James Cloos
OpenPGP: 0x997A9F17ED7DAEA6; url=
OpenPGP-Fingerprint: E9E9 F828 61A4 6EA9 0F2B 63E7 997A 9F17 ED7D AEA6
Date: Mon, 13 Apr 2020 11:58:47 -0400
Message-ID: <>
Lines: 23
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <>
Subject: Re: [ietf-smtp] MTA-STS reports via HTTPS
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: Mon, 13 Apr 2020 15:59:00 -0000

>>>>> "JL" == John R Levine <> writes:
>>>>>>> "JL" == John R Levine <> writes:

JL> Does anyone else send reports by https?

JC> I get them regularly from goog.

JL> Odd, they're still mailing them to me.

i ay have mixed up why they are sening those reports...

(a nodei used for internal mail went dark when i was back in the stroke
center -- the vendor shut down -- and i only just got internal mail
woking again.  including delivery of 4 months of backlog.

the mail from the webmachine mentioned sts, but looking at my dns i see
that they are actually due to TLSRPTv1 TXT RRs for _smtp._tls.$DOMAIN.

i hadn't thought about this stuff in too long...

James Cloos <>         OpenPGP: 0x997A9F17ED7DAEA6