IETF Logo Mail Archive

Re: Review of draft-kucherawy-dmarc-base-04

mrex@sap.com (Martin Rex) Wed, 23 April 2014 00:31 UTC

Return-Path: <mrex@sap.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 ED6281A02B9 for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 17:31:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level:
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, 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 TZi8ngXMeomv for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 17:31:09 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id BD66E1A02AE for <ietf@ietf.org>; Tue, 22 Apr 2014 17:31:08 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id s3N0UkS6018771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 23 Apr 2014 02:30:46 +0200 (MEST)
Subject: Re: Review of draft-kucherawy-dmarc-base-04
In-Reply-To: <6.2.5.6.2.20140422074852.0d368728@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Date: Wed, 23 Apr 2014 02:30:45 +0200
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140423003045.EBE6F1ACDC@ld9781.wdf.sap.corp>
From: mrex@sap.com
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_C23rWNA2DtzMfSjmVGFr8XOrms
Cc: ietf@ietf.org, Nevil Brownlee <rfc-ise@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
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: <http://www.ietf.org/mail-archive/web/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, 23 Apr 2014 00:31:10 -0000

S Moonesamy wrote:
> 
> In Section 8:
> 
>    "If the RFC5322.From domain does not exist in the DNS, Mail Receivers
>     SHOULD direct the receiving SMTP server to reject the message."
> 
> Why is there such a recommendation?  What is a mail receiver?  I am 
> asking the question as there is "receiving SMTP server" in that sentence.

That would be silly.  RFC5322.From might contain no DNS domain to begin with.


> 
> In Section 10.1:
> 
>    "Have no RFC5322.From field (which is also forbidden under RFC 5322
>     [MAIL])"
> 
> Where is it stated in RFC 5322 that it is forbidden?  That RFC 
> specifies a syntax for the Internet Message Format.

Some MTAs (sendmail?) seem to recreate an RFC5322.From from the Envelope,
in case that it is missing in the message.

-Martin

v2.23.0 | Report a Bug | By Email