IETF Logo Mail Archive

Re: [OAUTH-WG] Off Topic: oauth-bounces

Benjamin Kaduk <kaduk@mit.edu> Tue, 07 May 2019 13:22 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4E1312012C for <oauth@ietfa.amsl.com>; Tue, 7 May 2019 06:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 7LMDy-NF59WN for <oauth@ietfa.amsl.com>; Tue, 7 May 2019 06:22:08 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 E343B12010C for <oauth@ietf.org>; Tue, 7 May 2019 06:22:07 -0700 (PDT)
Received: from kduck.mit.edu (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x47DM3iu022387 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 7 May 2019 09:22:05 -0400
Date: Tue, 07 May 2019 08:22:03 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Neil Madden <neil.madden@forgerock.com>
Cc: IETF oauth WG <oauth@ietf.org>
Message-ID: <20190507132202.GB19509@kduck.mit.edu>
References: <466CE750-3ACD-432A-9DB7-51D02F17533B@forgerock.com> <38C30749-0AF1-455B-84DA-29440864E198@forgerock.com> <DBBPR08MB4539FD7B2C7D27BFBF248E5EFA310@DBBPR08MB4539.eurprd08.prod.outlook.com> <771DAF49-BF74-4A78-A65F-78B5E94FE081@forgerock.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <771DAF49-BF74-4A78-A65F-78B5E94FE081@forgerock.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/K1OWCrer3xOrgTTdilQCrZ5BFX8>
Subject: Re: [OAUTH-WG] Off Topic: oauth-bounces
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2019 13:22:10 -0000

On Tue, May 07, 2019 at 10:46:43AM +0100, Neil Madden wrote:
> I notice that a few of my emails to the OAuth WG list have come through with the From field from “oauth-bounces”:
> 
> From: OAuth <oauth-bounces@ietf.org> On Behalf Of Neil Madden
> 
> Is this normal? I checked my subscription status on mailman and I’m posting from the same email address that I subscribed from.

It's the latest iteration of trying to maintain DMARC compliance when
mailing list software redistributes your message.
The IETF (well, AMS, LLC) mail servers are presumably not listed as
authorized senders for your actual domain, so they rewrite to a From:
address they are authorized to send from.

-Ben

v2.23.0 | Report a Bug | By Email