And so it begins? SPF failure on self

Paul Wouters <paul@nohats.ca> Fri, 28 October 2016 04:42 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CC14129514 for <ietf@ietfa.amsl.com>; Thu, 27 Oct 2016 21:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.431
X-Spam-Level:
X-Spam-Status: No, score=-2.431 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.431] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 0kYs37QZtHuC for <ietf@ietfa.amsl.com>; Thu, 27 Oct 2016 21:42:41 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 D260F12944E for <ietf@ietf.org>; Thu, 27 Oct 2016 21:42:39 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3t4rhs6Lysz1P6 for <ietf@ietf.org>; Fri, 28 Oct 2016 06:42:37 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1477629757; bh=gzZBNpu4HblqFJq7EmO6kY4Kuc4RgP/Y2he7s0ZQ9wE=; h=Date:From:To:Subject; b=L36DafsLiDIl/BXRHBSsYogCWozmveqfNl6wrtmhnOKux2efnmRxuk8lXt9w7AkDa dBaWQflift95KmloJE8uTGdS49RYChYUJh/gFQe71xAFrVldsscWmo7nlBqCMwzfiw nK5hD2DzMicfcL7Nx6IGTHqtXotj887mCx0IYF4w=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id O_n58nBuflJ4 for <ietf@ietf.org>; Fri, 28 Oct 2016 06:42:17 +0200 (CEST)
Received: from bofh.nohats.ca (206-248-139-105.dsl.teksavvy.com [206.248.139.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS for <ietf@ietf.org>; Fri, 28 Oct 2016 06:42:16 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id DC2A879B12; Fri, 28 Oct 2016 00:42:15 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.10.3 bofh.nohats.ca DC2A879B12
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id C6BAB40B7E88 for <ietf@ietf.org>; Fri, 28 Oct 2016 00:42:15 -0400 (EDT)
Date: Fri, 28 Oct 2016 00:42:15 -0400
From: Paul Wouters <paul@nohats.ca>
To: ietf@ietf.org
Subject: And so it begins? SPF failure on self
Message-ID: <alpine.LRH.2.20.1610280032240.14506@bofh.nohats.ca>
User-Agent: Alpine 2.20 (LRH 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Jj6xDo_NksJvhEArQa6c5IBqMBU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Oct 2016 04:42:42 -0000

Using my redhat.com address, I replied to a draft alias email address
that includes myself, and the ietf mail server rejected the message
to me (or at least I hope the others still got it)

Is this a new ietf.org mail "feature" or did something on my redhat.com
end change?

Is there a way to make the email processing server at ietf.org a little
smarter to not check SPF for outgoing mails that were expanded by
itself?

Paul