Re: Registering $hasAttachment & $hasNoAttachment

On Mon, Dec 04, 2017 at 10:25:16 +0000, Alexey Melnikov wrote:
> > On 4 Dec 2017, at 00:21, Neil Jenkins <[email protected]> wrote:
> >> On Mon, 4 Dec 2017, at 10:58 AM, Josef 'Jeff' Sipek wrote:
...
> >> 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 think everything after "and SHOULD" can be deleted. As presence of both
> means neither is present, both what is written above and what you suggest
> is a reasonable course of action.

Right.  Dropping the SHOULD would leave it least constrained.  Suggesting
that either they both get dropped, or that only the correct one remains is
an additional (but very weak) "constraint".

So, the options are:

1. remove the SHOULD completely
2. use SHOULD remove both keywords
3. use SHOULD keep only correct keyword

The $Junk & $NotJunk IANA registration texts [1,2] use option #2.

Finally, I received a suggestion off-list to possibly add something like:

	Whenever a client sets $HasAttachment, the server MAY assist by
	automatically clearing $HasNoAttachment. (and vice versa)


All three options are fine by me (either with or without the server MAY
addition).  I think I have a slight preference for #1 just because it merely
resolves the invalid state.  Once resolved (by ignoring both keywords), the
email is a known state and the client can proceed as normal - whatever that
may be.

Jeff.

[1] https://www.iana.org/assignments/imap-keywords/junk/junk-template
[2] https://www.iana.org/assignments/imap-keywords/notjunk/notjunk-template

-- 
The obvious mathematical breakthrough would be development of an easy way to
factor large prime numbers.
		- Bill Gates, The Road Ahead, pg. 265

_______________________________________________
imapext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imapext