MBOX-Line: From gilles.lamiral at laposte.net  Sun Aug 11 06:10:16 2013
To: imap-protocol@u.washington.edu
From: Gilles LAMIRAL <gilles.lamiral@laposte.net>
Date: Fri Jun  8 12:34:51 2018
Subject: [Imap-protocol] PERMANENTFLAGS \* and server behavior with \ANYFOO
	flag.
In-Reply-To: <20130811114841.GC8165@gulbrandsen.priv.no>
References: <5206AB36.7080808@laposte.net>
	<CAKHUCzz=-kCLAmzswJeujL-ox+Y_GA+raDXXN9LANkC5ViBLNg@mail.gmail.com>
	<20130811083343.GA8165@gulbrandsen.priv.no>
	<CAKHUCzx8Oq4TeZ2B8CSx0YxA+=Ohma+Xkp4etE9Ag3fbOz9e4A@mail.gmail.com>
	<20130811114841.GC8165@gulbrandsen.priv.no>
Message-ID: <52078D38.3050502@laposte.net>

Hi,

> Gilles, anyway: \* means that you can store new flags, but now
> \attachments. \ is not a permitted character in the flag names YOU can
> store. RFCs can make up new names containing \, you can not.

Ok. I understand now. 
I guessed wrong because of the syntax \*, it is a terribly bad symbol.
It really means "anything else than what I look like".
A single * or a double ** (or anything else without a \) would have been less tortuous.

I MUST read the RFCs very carefully, with no background in mind, and I MUST retain 
what I read despite the syntax. All of this in a foreign language. I'm welcome.

Thanks for your clarifications. I guess it is not the last time I ask for them.


-- 
Au revoir,                             09 51 84 42 42
Gilles Lamiral. France, Baulon (35580) 06 20 79 76 06 

