Re: [imapext] Registering $hasAttachment & $hasNoAttachment

Josef 'Jeff' Sipek <jeff.sipek@dovecot.fi> Mon, 04 December 2017 01:53 UTC

Return-Path: <jeff.sipek@dovecot.fi>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB527127201 for <imapext@ietfa.amsl.com>; Sun, 3 Dec 2017 17:53:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 soVFqed5hJDz for <imapext@ietfa.amsl.com>; Sun, 3 Dec 2017 17:53:51 -0800 (PST)
Received: from mail.dovecot.fi (wursti.dovecot.fi [94.237.32.243]) by ietfa.amsl.com (Postfix) with ESMTP id 799111201F8 for <imapext@ietf.org>; Sun, 3 Dec 2017 17:53:51 -0800 (PST)
Received: from meili (josefsipek.net [71.174.113.7]) by mail.dovecot.fi (Postfix) with ESMTPSA id AAF6B2B3CD1; Mon, 4 Dec 2017 03:53:49 +0200 (EET)
Date: Sun, 3 Dec 2017 20:53:46 -0500
From: Josef 'Jeff' Sipek <jeff.sipek@dovecot.fi>
To: Neil Jenkins <neilj@fastmailteam.com>
Cc: imapext@ietf.org
Message-ID: <20171204015345.GC1632@meili>
References: <20171203235834.GB1632@meili> <1512346907.3913979.1192707160.32EA0EE2@webmail.messagingengine.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1512346907.3913979.1192707160.32EA0EE2@webmail.messagingengine.com>
User-Agent: Mutt/1.8.3 (2017-05-23)
Archived-At: <https://mailarchive.ietf.org/arch/msg/imapext/ZapEFZMl7XeJHdjZZjS1Ze6ISjE>
Subject: Re: [imapext] Registering $hasAttachment & $hasNoAttachment
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Dec 2017 01:53:53 -0000

On Mon, Dec 04, 2017 at 11:21:47 +1100, Neil Jenkins wrote:
> On Mon, 4 Dec 2017, at 10:58 AM, Josef 'Jeff' Sipek wrote:
> > IMAP keyword name: $hasAttachment
> 
> We're using $HasAttachment (capital H) at FastMail. Please can we
> standardise on this capitalisation? This is consistent with the other
> IMAP keyword registrations too.

Fine by me.

> > Note:
> > $hasAttachment and $hasNoAttachment are mutually exclusive.  If
> > more than> one of them is set for a message, the email client MUST treat
> > this as if> neither of them is set and SHOULD remove both of them from the IMAP
> > server.
> 
> Surely it SHOULD remove the one that is incorrect rather than both?

I basically copied the $Junk/$NotJunk mutual exclusion semantics.  It makes
more sense to do what you suggest - and since it is a SHOULD, the client can
just nuke both keywords (useful if the client doesn't have the whole message
downloaded but finds an inconsistency in keywords).

Jeff.

-- 
Research, n.:
  Consider Columbus:
    He didn't know where he was going.
    When he got there he didn't know where he was.
    When he got back he didn't know where he had been.
    And he did it all on someone else's money.