[ietf-smtp] Curious, with this now being associated to emailcore, should list name change?

Michael Peddemors <michael@linuxmagic.com> Fri, 17 July 2020 21:57 UTC

Return-Path: <michael@linuxmagic.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 4A0283A086E for <ietf-smtp@ietfa.amsl.com>; Fri, 17 Jul 2020 14:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.498
X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id dgfhHxIfiprn for <ietf-smtp@ietfa.amsl.com>; Fri, 17 Jul 2020 14:57:09 -0700 (PDT)
Received: from mail-ob1.cityemail.com (mail-ob1.cityemail.com []) by ietfa.amsl.com (Postfix) with ESMTP id 1CDE23A086D for <ietf-smtp@ietf.org>; Fri, 17 Jul 2020 14:57:08 -0700 (PDT)
Received: (qmail 24655 invoked from network); 17 Jul 2020 21:57:08 -0000
Received: from riddle.wizard.ca (HELO []) (michael@wizard.ca@ by fe1.cityemail.com with (DHE-RSA-AES128-SHA encrypted) SMTP (7597bc2c-c878-11ea-b60b-e703a6376daa); Fri, 17 Jul 2020 14:57:08 -0700
To: ietf-smtp@ietf.org
From: Michael Peddemors <michael@linuxmagic.com>
Organization: LinuxMagic Inc.
Message-ID: <81c2a19c-f19e-b495-3441-22c2a112037c@linuxmagic.com>
Date: Fri, 17 Jul 2020 14:57:08 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-MagicMail-OS: Linux 3.11 and newer
X-MagicMail-UUID: 7597bc2c-c878-11ea-b60b-e703a6376daa
X-MagicMail-Authenticated: michael@wizard.ca
X-MagicMail-RegexMatch: 0
X-MagicMail-EnvelopeFrom: <michael@linuxmagic.com>
X-Archive: Yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/myQM9K9-X-ILawhGYtrvHdshhkE>
Subject: [ietf-smtp] Curious, with this now being associated to emailcore, should list name change?
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: Fri, 17 Jul 2020 21:57:11 -0000

Not sure what normally happens, but it might be confusing.

"Email Core" would have a wider scope, and it might be confusing if the 
list name was limited to 'smtp'.

Suggestion for topic for this group as well:

Unifying all the 'autodiscover' and 'autoconfig' methods currently in 
place.. email client developers have now a very convoluted set of 
requirements in order to find the 'recommended' settings for that domain 
or ISP etc..

There are several independent databases out there, eg Apple's own, the 
ISPDB, and even some of Microsofts' own email clients no longer follow 
traditional methods of lookups.. It is a bit of a mess, that maybe the 
IETF would like to weigh in on?

"Catch the Magic of Linux..."
Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.
604-682-0300 Beautiful British Columbia, Canada

This email and any electronic data contained are confidential and intended
solely for the use of the individual or entity to which they are addressed.
Please note that any views or opinions presented in this email are solely
those of the author and are not intended to represent those of the company.