IETF Logo Mail Archive

Re: [Jmap] Submission

"Adrien de Croy" <adrien@qbik.com> Fri, 21 April 2017 06:16 UTC

Return-Path: <adrien@qbik.com>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0352127B52 for <jmap@ietfa.amsl.com>; Thu, 20 Apr 2017 23:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 bUNEWBAogCui for <jmap@ietfa.amsl.com>; Thu, 20 Apr 2017 23:16:46 -0700 (PDT)
Received: from smtp.qbik.com (smtp.qbik.com [122.56.26.1]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E81B127599 for <jmap@ietf.org>; Thu, 20 Apr 2017 23:16:45 -0700 (PDT)
Received: From [192.168.1.146] (unverified [192.168.1.146]) by SMTP Server [192.168.1.3] (WinGate SMTP Receiver v9.0.5 (Build 5926)) with SMTP id <0001025720@smtp.qbik.com>; Fri, 21 Apr 2017 18:16:42 +1200
From: Adrien de Croy <adrien@qbik.com>
To: John Levine <johnl@taugh.com>, "jmap@ietf.org" <jmap@ietf.org>
Date: Fri, 21 Apr 2017 06:16:42 +0000
Message-Id: <em7b8ab713-d303-46e1-b0de-eec9f43f18e0@bodybag>
In-Reply-To: <20170421001702.24991.qmail@ary.lan>
References: <emd3533c0d-dc08-45c3-801c-07972858ad64@bodybag> <20170421001702.24991.qmail@ary.lan>
Reply-To: Adrien de Croy <adrien@qbik.com>
User-Agent: eM_Client/7.0.27943.0
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/pYJpu8GiqMMTnQfUZHSPJETmkMI>
Subject: Re: [Jmap] Submission
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 06:16:49 -0000


------ Original Message ------
From: "John Levine" <johnl@taugh.com>
To: "jmap@ietf.org" <jmap@ietf.org>
Cc: "adrien@qbik.com" <adrien@qbik.com>
Sent: 21/04/2017 12:17:02 PM
Subject: Re: [Jmap] Submission

>In article <emd3533c0d-dc08-45c3-801c-07972858ad64@bodybag> you write:
>>I'd love to see a mail client that does at least initial validation on
>>destination email addresses as they are added to the message, so that
>>errors in the addresses which can be resolved at that stage (e.g.
>>NXDOMAIN) can be raised with the email author before the mail is even
>>submitted.
>
>This is quite the can of worms.  It's easy enough to look up a domain
>and see if it has an A or an MX, but whatever you were planning to do
>to validate mailboxes will get you blacklisted as a listwashing
>spammer.
sure, I think there are fundamental issues with trying to go further 
than an A/MX for now, but if we built in a mechanism to verify 
addresses, it could be extended later, rather than being blocked off for 
all of eternity.

Even A/MX would have some value.  Who knows what kind of trusted mail 
delivery infrastructure may come out in the future, at some stage we 
have to fix SMTP.  Forever is a long time.

Adrien


>
>
>Once again, I really do not think this is the time or place to try and
>fix all of SMTP's faults.
>
>R's,
>John
>
>_______________________________________________
>Jmap mailing list
>Jmap@ietf.org
>https://www.ietf.org/mailman/listinfo/jmap

v2.23.0 | Report a Bug | By Email