IETF Logo Mail Archive

Re: [art] Auto-configuring Email Clients via WebFinger

"Paul E. Jones" <paulej@packetizer.com> Tue, 16 July 2019 04:13 UTC

Return-Path: <paulej@packetizer.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D294C120188 for <art@ietfa.amsl.com>; Mon, 15 Jul 2019 21:13:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=packetizer.com
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 9VxDHzuSgnwK for <art@ietfa.amsl.com>; Mon, 15 Jul 2019 21:13:12 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [IPv6:2600:1f18:24d6:2e01:e842:9b2b:72a2:d2c6]) (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 EFC9D12006F for <art@ietf.org>; Mon, 15 Jul 2019 21:13:11 -0700 (PDT)
Received: from authuser (localhost [127.0.0.1])
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packetizer.com; s=dublin; t=1563250388; bh=FM2SWW/tVauua/D9kkzKNkAmpScW7sDvO2EI3BhtLqE=; h=From:To:Subject:Date:In-Reply-To:References:Reply-To; b=tSgSShL/1a2fE/F34BRELuK19B13OcQiiZzr7yV2d7LAfz23NucVUrJo3iLR8RBVN kP5Vw5Ldji8kjKjKNYLUqgdKUF/8MDtY0dhHWWpIS+FlKrKcht1OGuvMiDpGSdU4Q3 vHfsBZPF8IFE9VYhPZcnEzKdhKoWy+G+UVlwREkQ=
From: "Paul E. Jones" <paulej@packetizer.com>
To: John Levine <johnl@taugh.com>, art@ietf.org
Date: Tue, 16 Jul 2019 04:13:03 +0000
Message-Id: <em20c214d4-507e-4859-99fc-460e3919ac55@sydney>
In-Reply-To: <20190716023406.4F8AD4C3BE4@ary.qy>
References: <eme8317959-26f9-4a9d-b2be-d2f8cb0961f6@sydney> <20190716023406.4F8AD4C3BE4@ary.qy>
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
User-Agent: eM_Client/7.2.35595.0
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="------=_MBD076C677-052E-4129-B645-FD607BB7DF48"
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/tcU0GmodnXnqMacrm-i-wAe6TjI>
Subject: Re: [art] Auto-configuring Email Clients via WebFinger
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2019 04:13:14 -0000

John,

I use primarily two different email clients, and neither support that 
method.  One does support Microsoft's method:
https://docs.microsoft.com/en-us/Exchange/architecture/client-access/autodiscover?view=exchserver-2019

I have no strong preference for how we solve the problem, but I think we 
need a standard for this.  I also think we should take into 
consideration the privacy concerns that were raised when I first talked 
in context of WebFinger several years ago.  Specifically, people wanted 
a way to ensure access to the config file was protected.  (I do not 
recall now why people wanted to keep that private, but they did and were 
insistent on it.)

Paul

------ Original Message ------
From: "John Levine" <johnl@taugh.com>
To: art@ietf.org
Cc: paulej@packetizer.com
Sent: 7/15/2019 10:34:05 PM
Subject: Re: [art] Auto-configuring Email Clients via WebFinger

>In article <eme8317959-26f9-4a9d-b2be-d2f8cb0961f6@sydney> you write:
>>We'd love to have some dialog on this to see how we can address this
>>problem of auto-configuring email clients.
>
>The Thunderbird MUA has has this kind of autoconfiguration for many
>years, with the MUA fetching an XML config file.  I wouldn't say it's
>perfect but I would say it's widely deployed.
>
>See
>
>https://developer.mozilla.org/en-US/docs/Mozilla/Thunderbird/Autoconfiguration
>https://wiki.mozilla.org/Thunderbird:Autoconfiguration:ConfigFileFormat
>

v2.23.0 | Report a Bug | By Email