Re: Problem with RFC 4408
Scott Kitterman <scott@kitterman.com> Wed, 15 July 2015 18:08 UTC
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C14ED1B332C for <ietf@ietfa.amsl.com>; Wed, 15 Jul 2015 11:08:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 eorUTPye9mMa for <ietf@ietfa.amsl.com>; Wed, 15 Jul 2015 11:08:19 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F2341B331D for <ietf@ietf.org>; Wed, 15 Jul 2015 11:08:19 -0700 (PDT)
Received: from [10.115.109.122] (unknown [166.170.30.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 0F8A0C40385; Wed, 15 Jul 2015 13:08:18 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=201409; t=1436983698; bh=ITrV7p2fMcyM2CYkdfEi+eOWorY+nsRYvawg1ZTdw7g=; h=In-Reply-To:References:Subject:From:Date:To:From; b=Ad/tAbjha/mOT3RoMIXAo5Da8YLpjYu3YEJlb52tE7O5KMFpX5/qlvWR/Tt9DrmGT rqATO1vfT/jfRQVR8DCZnvjRl24P89lvWOxvq7b+daCCMFkUE+DtGgcLsYWPK3l2/y /E0F+6LWG66xp36Z/t4QZXf0Tmt9je1f0M/cjPVs=
User-Agent: K-9 Mail for Android
In-Reply-To: <14e92da898f-5bf-115db@webprd-m03.mail.aol.com>
References: <14e92da898f-5bf-115db@webprd-m03.mail.aol.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="UTF-8"
Subject: Re: Problem with RFC 4408
From: Scott Kitterman <scott@kitterman.com>
Date: Wed, 15 Jul 2015 14:08:16 -0400
To: jannisohms@aol.com, ietf@ietf.org
Message-ID: <C628A815-70F2-440E-851A-CA1D15925367@kitterman.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/6v9kyDF_Ah1--N8sXABpDF8omWw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 15 Jul 2015 18:08:20 -0000
On July 15, 2015 1:54:32 PM EDT, jannisohms@aol.com wrote: >Iam currently trying to implement a parser for spf . to achive this I >took the grammar defined in RFC 4408 and added some parts of RFC 2234 >and RFC2822. I use aparse 2.5 to build my parser. I used the following >grammar. I would recommend using RFC 7208 instead. There were some ABNF changes made, so maybe that will help and even if it doesn't, you'll be working off the current version. Scott K
- Problem with RFC 4408 jannisohms
- Re: Problem with RFC 4408 Scott Kitterman