[lemonade] ManageSieve server location discovery

Alexey Melnikov <alexey.melnikov@isode.com> Sat, 13 September 2008 16:06 UTC

Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 823F828C0DD; Sat, 13 Sep 2008 09:06:25 -0700 (PDT)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6375C3A6C7F for <lemonade@core3.amsl.com>; Sat, 13 Sep 2008 09:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.39
X-Spam-Level:
X-Spam-Status: No, score=0.39 tagged_above=-999 required=5 tests=[AWL=-1.007, BAYES_50=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8gEvzAUj76gA for <lemonade@core3.amsl.com>; Sat, 13 Sep 2008 09:06:23 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 4E8023A6C7C for <lemonade@ietf.org>; Sat, 13 Sep 2008 09:06:23 -0700 (PDT)
Received: from [192.168.2.23] (host86-157-9-9.range86-157.btcentralplus.com [86.157.9.9]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <SMvlBgAxOYpe@rufus.isode.com>; Sat, 13 Sep 2008 17:06:31 +0100
Message-ID: <48CBCE58.4060403@isode.com>
Date: Sat, 13 Sep 2008 15:29:44 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Ned Freed <ned.freed@mrochek.com>
References: <480436090.137141216933705734.JavaMail.root@dogfood.zimbra.com> <1838981617.137721216933976809.JavaMail.root@dogfood.zimbra.com> <01MXJKE040TO00007A@mauve.mrochek.com> <1YRGls0RHq1VpAtqr1hS/Q.md5@lochnagar.oryx.com> <01MXKC8H3LLK00007A@mauve.mrochek.com>
In-Reply-To: <01MXKC8H3LLK00007A@mauve.mrochek.com>
MIME-Version: 1.0
Cc: lemonade@ietf.org
Subject: [lemonade] ManageSieve server location discovery
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Ned Freed wrote:

>> Reminds me of something else. I've mentioned it before but I want to
>> harp on this.
>
>> Lemonade now tells clients to connect to three separate servers (at
>> various times), but offers no advice on how to locate those servers.
>> One person (Eric? I forget) thought it was a provisioning issue: The
>> client would be correctly configured by the time the user receives it.
>
>> I disagree. I think people must be expected to read their mail with
>> several devices (at least two — a mobile and something else), and to
>> replace these devices occasionally. One of these 2+ devices will often
>> be supplied by the service provider, but IMNSHO not all, not even most.
>
> +1.
>
>> So I think profile-bis ought to say something like "A lemonade client
>> can locate its Submission, IMAP and Managesieve servers by taking the
>> domain of the user's email address, prefixing it with
>> _submission._tcp., _imap._tcp. and _managesieve._tcp., and doing SRV
>> DNS lookups for the resulting labels. Lemonade server operators should
>> set up suitable SRV records."
>
> Well, I don't tnink this properly belongs in a profile specification, but
> I'm definitely in favor of specifying it somewhere. in the specific
> case of managesieve, where we're talking about an entirely new protocol,
> I'd reallly like to see this done in the base specification. This
> should probably be discussed on the Sieve WG list though.

As per various discussions during the Dublin IETF, I've updated the 
ManageSieve protocol to require clients to use SRV records.


_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade