Re: [ietf-smtp] Valid RFC5322 address
Hector Santos <hsantos@isdg.net> Sun, 03 May 2020 16:28 UTC
Return-Path: <hsantos@isdg.net>
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 CF3113A0F2A for <ietf-smtp@ietfa.amsl.com>; Sun, 3 May 2020 09:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Level:
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isdg.net header.b=MIoz6Ew/; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=QQUIX37+
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 itQZ3JONm_LJ for <ietf-smtp@ietfa.amsl.com>; Sun, 3 May 2020 09:28:05 -0700 (PDT)
Received: from mail.winserver.com (unknown [76.245.57.69]) (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 B62453A0F24 for <ietf-smtp@ietf.org>; Sun, 3 May 2020 09:28:04 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2058; t=1588523277; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=W3BScv6yTbkgtR3OObpOgSH4jWI=; b=MIoz6Ew/TwMx8ZkARtx94KwTotZcgG9Ea5anZ+ISx2TVqzI8o6Prt2K5NNljK3 6hwE+zMChEsCgGgQX9Hyl1K3tF6YVOJbTwbyOK6p881jxLCEUPzqZUEN/vOBXPy2 7fDo56LW/GnadsHgYqFeasvj4p0EfWBVYDeGlEBa7JpYE=
Received: by winserver.com (Wildcat! SMTP Router v8.0.454.9) for ietf-smtp@ietf.org; Sun, 03 May 2020 12:27:57 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; dmarc=pass policy=reject author.d=isdg.net signer.d=beta.winserver.com (atps signer);
Received: from beta.winserver.com ([76.245.57.74]) by winserver.com (Wildcat! SMTP v8.0.454.9) with ESMTP id 3545590282.9584.480; Sun, 03 May 2020 12:27:57 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2058; t=1588522924; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=/lKb+5Q 8Y3hWQRf+eQ33yohKGYNFgu/fT9wT/aULj7U=; b=QQUIX37+AfmaCThISTjmdwK CGCa+RMr2UBhfCNztT1gRDZl767LVt5M09f4uxNdvzIl6lVnXbsz4+aY4W9r/5SO nMPGsKtBZ/xHxXhDzldnZb12C5qrby+213V4Gq189Q0dY72uaPH3uzEymDm0RI2a HUzZlB9iZNjQIBHeiFJg=
Received: by beta.winserver.com (Wildcat! SMTP Router v8.0.454.9) for ietf-smtp@ietf.org; Sun, 03 May 2020 12:22:04 -0400
Received: from [192.168.1.68] ([75.26.216.248]) by beta.winserver.com (Wildcat! SMTP v8.0.454.9) with ESMTP id 256998781.3.3916; Sun, 03 May 2020 12:22:04 -0400
Message-ID: <5EAEF10B.5000509@isdg.net>
Date: Sun, 03 May 2020 12:27:55 -0400
From: Hector Santos <hsantos@isdg.net>
Reply-To: hsantos@isdg.net
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
CC: SMTP Interest Group <ietf-smtp@ietf.org>
References: <5EAEDA84.1050408@isdg.net> <09BDC808C0A7267EFE914CB8@PSB>
In-Reply-To: <09BDC808C0A7267EFE914CB8@PSB>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/QIn_tE4ApRPjT8AeYFSrlPiOf6E>
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 16:28:07 -0000
On 5/3/2020 11:57 AM, John C Klensin wrote: > > Technically, no. The "/" is not a problem. Colons are (they > are not in the list of valid characters for <atext> in RFC > 5322), I imagine at least in part because they were part of the > now-discouraged Source Route syntax (see Sections 3.6 and > Appendix C of RFC 5321 (and 5321bis, at least so far)) and so > would need to be quoted. Just from a reader pov, it wasn't quote clear between the two docs. I see now RFC5322 is defining atext clearly. RFC5321 probably needs a reference to RFC5322 for atext. > Noting that you seem to be turning blanks into ".", Yes, from the old MHS methods that took local user names, i.e. "Hector Santos" and dotted/underscored them when networking came to BBSes. char *MakeDotName(char *psz) { char *p = psz; while (*p) { switch (*p) { case ' ': *p = '.'; break; case '.': *p = '_'; break; } p++; } return psz; } >I'd also > want to be careful to be sure that any value "." characters to > the right of the "/" in your example don't get broken by any > de-conversion process. I see. > Also note that, if this is going to be used in conjunction with > web facilities, someone is likely to want to turn whatever you > produce into a MAILTO: URL and restrictions on those (both > restrictions imposed by the spec and those imposed by sloppy > implementations) are even worse. > > ... > > Recommendation: Don't push it. +1, I plan to change it. It was initially meant to be more for local MUAs (Not networking). Then the notify by email was added where there is a MakeDotName() translation and no consideration for special characters. I think I will first try this for the local name to email name translation. "Github Agent: github-hookshot/xxxxxxxxx" no-reply@winserver.com And check how Apple's web-based MUA handles it. Btw, the Apple iPhone Mail App display the field fine. I am also going to an wcSMTP server option to validate the local part of the return address. Thanks -- HLS
- Re: [ietf-smtp] Valid RFC5322 address Hector Santos
- Re: [ietf-smtp] Valid RFC5322 address Ned Freed
- [ietf-smtp] Valid RFC5322 address Hector Santos
- Re: [ietf-smtp] Valid RFC5322 address Claus Assmann
- Re: [ietf-smtp] Valid RFC5322 address John C Klensin
- Re: [ietf-smtp] Valid RFC5322 address Hector Santos
- Re: [ietf-smtp] Valid RFC5322 address Hector Santos
- Re: [ietf-smtp] Valid RFC5322 address John C Klensin
- Re: [ietf-smtp] Valid RFC5322 address cketti
- Re: [ietf-smtp] Valid RFC5322 address John C Klensin
- Re: [ietf-smtp] Valid RFC5322 address Viktor Dukhovni