IETF Logo Mail Archive

Re: [ietf-smtp] Valid RFC5322 address

Claus Assmann <ietf-smtp@esmtp.org> Sun, 03 May 2020 15:11 UTC

Return-Path: <ietf-smtp@esmtp.org>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C6F33A0E67 for <ietf-smtp@ietfa.amsl.com>; Sun, 3 May 2020 08:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 pvFS22zXdETq for <ietf-smtp@ietfa.amsl.com>; Sun, 3 May 2020 08:11:31 -0700 (PDT)
Received: from kiel.esmtp.org (kiel.esmtp.org [195.244.235.220]) (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 8ACFD3A0E66 for <ietf-smtp@ietf.org>; Sun, 3 May 2020 08:11:31 -0700 (PDT)
Received: from kiel.esmtp.org (localhost. [127.0.0.1]) by kiel.esmtp.org (MeTA1-1.1.Alpha14.1) with ESMTPS (TLS=TLSv1.2, cipher=ECDHE-RSA-AES256-GCM-SHA384, bits=256, verify=OK) id S00000000000169AA00; Sun, 3 May 2020 17:11:29 +0200
Received: (from ca@localhost) by kiel.esmtp.org (8.16.0.41/8.12.10.Beta0/Submit) id 043FBT1E049920 for ietf-smtp@ietf.org; Sun, 3 May 2020 17:11:29 +0200 (CEST)
Date: Sun, 03 May 2020 17:11:29 +0200
From: Claus Assmann <ietf-smtp@esmtp.org>
To: ietf-smtp@ietf.org
Message-ID: <20200503151129.GA79775@kiel.esmtp.org>
Reply-To: ietf-smtp@ietf.org
Mail-Followup-To: ietf-smtp@ietf.org
References: <5EAEDA84.1050408@isdg.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5EAEDA84.1050408@isdg.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/Zk-ZKxE_a7wd0YEdCPRg4KQhy50>
Subject: Re: [ietf-smtp] Valid RFC5322 address
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 May 2020 15:11:33 -0000

On Sun, May 03, 2020, Hector Santos wrote:

> FROM:<github.agent:.github-hookshot/7431eee@winserver.com>

Not valid in 5321.

> with the ':' and also '/' ??

':' is not valid in a local part (unless quoted).

> It appears to be accepted by various servers, including my own.

Well, most mail servers accept all kind of garbage ("be liberal ... ").

Mine doesn't:
Mail from:<github.agent:.github-hookshot/7431eee@winserver.com>
501 5.1.7 Bad sender's mailbox address syntax.

Just quote it and you're ok:
<"github.agent:.github-hookshot/7431eee"@winserver.com>

> So I need to know if the address is valid. Its hard to decipher whether it
> is or not from the RFC5322/RFC5321 BNF. It seems to read the ':' and '/'
> characters are valid.

Where do you see an unquoted ':' as valid in "Local-part"?  ':' is
used to separate "At-Domain" parts.

v2.23.0 | Report a Bug | By Email