IETF Logo Mail Archive

Re: [Uta] tlsrpt

Alice Wonder <alice@domblogger.net> Sun, 14 April 2019 16:49 UTC

Return-Path: <alice@domblogger.net>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D634C1200DF for <uta@ietfa.amsl.com>; Sun, 14 Apr 2019 09:49:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=domblogger.net
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 sVMQBR0RqIhV for <uta@ietfa.amsl.com>; Sun, 14 Apr 2019 09:49:19 -0700 (PDT)
Received: from mail.domblogger.net (mail.domblogger.net [104.200.18.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D08A1200E6 for <uta@ietf.org>; Sun, 14 Apr 2019 09:49:18 -0700 (PDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.domblogger.net 85724485
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=domblogger.net; s=default2019; t=1555260555; bh=5GDeoDDPQH8Yh/j6MTskNsLbBg2IXqn3xK+W7CmnuNs=; h=Subject:To:References:From:Date:In-Reply-To:From; b=o/fX08SlWIUoaROYvnxNQGL2pK+quF6qIkuj2kiw5Dq6sDljSXEZt9MW/+CBcETFH SAmJoXy+XAJ5WSTYzUY8eUsBeB0Utzk+/QhMl+ytzMCn5yzXBv0Ii/0e5hHyUSGN0H SJzWXd2DoA18aZOOX1X74Vnanorzk5yF6bOLC8QTOkxjHqH4aHiASDUucy2MlgjTYu b4wNG0vxIuLXwnkoV4gdkGKkYdIlktK7cT6C11QCUt3r1w4ujQCQaO8qQCFI4vfqQ/ 4W1BYTWwgiSg7z5ok1g2A6ZQGIGjlSg5pJQMJQI0VQtHltY6QDpKdlnKxsNyKxCedI axvCEKsWDCfhg==
To: uta@ietf.org
References: <m3imvj9sk3.fsf@carbon.jhcloos.org>
From: Alice Wonder <alice@domblogger.net>
Message-ID: <a91070f8-a4af-476d-ca70-80868e4a98f2@domblogger.net>
Date: Sun, 14 Apr 2019 09:49:14 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <m3imvj9sk3.fsf@carbon.jhcloos.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-384"; boundary="------------ms060004070806080402060606"
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/svM6g6v3a-2NEW1JmQH63VnEJXw>
Subject: Re: [Uta] tlsrpt
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Apr 2019 16:49:21 -0000

On 4/12/19 8:01 AM, James Cloos wrote:
> I see that google has started sending tls reports to the rua listed in
> _smtp._tls.ZONE. TXT RRs.
> 
> Has anyone else?
> 
> -JimC
> 

Yes, and they are sending them to me even when there are no errors.
They are sending them to my little used mail server when they have made 
no attempts to deliver to that domain.

And there is no indication as to whether or not the report contains a 
failure, I have to open the JSON file to find out.

I want to RFC changed so that reports are only sent when there was a 
failure, like how I recall DMARC worked before I stopped using it due to 
the mail list false positive problem.

Google assumes I have software receiving those messages that will 
decompress the archive and parse the JSON. I don't, and do not plan to. 
Reports should only be sent when there is an error to report. In my opinion.

v2.23.0 | Report a Bug | By Email