Re: And so it begins? SPF failure on self

S Moonesamy <sm+ietf@elandsys.com> Mon, 31 October 2016 07:07 UTC

Return-Path: <sm@elandsys.com>
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 4002812953C for <ietf@ietfa.amsl.com>; Mon, 31 Oct 2016 00:07:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.287
X-Spam-Level:
X-Spam-Status: No, score=-3.287 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.497, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=dTmxU7Jn; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=39kZGCpM
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 NAwDPTAN0uFn for <ietf@ietfa.amsl.com>; Mon, 31 Oct 2016 00:07:51 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D4D7129554 for <ietf@ietf.org>; Mon, 31 Oct 2016 00:07:51 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.227.87.25]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id u9V77RMb017304 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Oct 2016 00:07:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1477897661; x=1477984061; bh=K2m1WYIZ0jdrXrWXno2KhYNvOXZ7nDlCeLLIoFBZtMQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dTmxU7JnEjzzNA7nuepAFrtNr/lJHx5pjvK6oGnNpUtaZhcWophzjEBtM2BfVnSQZ 6PSvjTVsNXiA6RUr3L8Q8/tVk3oUTD6SF40GyhWcxbL1kPr2U6cDGOr1xvmqdGsX/u eUA+oyOB3UcFYDNKX4SNoh0PwVH4MJB2NoqQrrzQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1477897661; x=1477984061; i=@elandsys.com; bh=K2m1WYIZ0jdrXrWXno2KhYNvOXZ7nDlCeLLIoFBZtMQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=39kZGCpM0AHbCIVNcc+pRAT9FoOgF0BbAKvYBsyviPhLAnogKbYA8eXTHvy4ewZ7W RgyQ99D8LLzQLllKxZHl9CKpu8XlVcofTUDDS7SoJZlrnDAsvn+qpX5oWVxELZOG3Z jf5ZinQwlxYmJJ8ea2vJmR5X9RcxVVue3ZTa/e+0=
Message-Id: <6.2.5.6.2.20161030235554.0c7b97d0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 31 Oct 2016 00:06:09 -0700
To: Paul Wouters <paul@nohats.ca>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: And so it begins? SPF failure on self
In-Reply-To: <alpine.LRH.2.20.1610280032240.14506@bofh.nohats.ca>
References: <alpine.LRH.2.20.1610280032240.14506@bofh.nohats.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8vPhEXR53RrREV0UBB3h6cHc5tg>
Cc: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Christian Huitema <huitema@huitema.net>, ietf@ietf.org
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: Mon, 31 Oct 2016 07:07:52 -0000

Hi Paul,

For information about the facilitators experiment, please see
http://www.ietf.org/mail-archive/web/ietf/current/msg97290.html

At 21:42 27-10-2016, Paul Wouters wrote:
>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?

I suggest opening a ticket about the above by sending a message to 
ietf-action@ietf.org

Regards,
S. Moonesamy