Imapflags: Added FIXME.

TODO

@@ -10,10 +10,6 @@ Next (in order of descending priority/precedence):
 	- Vacation: If the Sieve variables extension is used, the arguments 
 	  MUST NOT have undergone variable expansion prior to their use in response 
 	  tracking.
-	- Vacation: The ":subject" parameter specifies a subject line to attach to 
-	  any vacation response that is generated. UTF-8 characters can be used in
-	  the string argument; implementations MUST convert the string to [RFC2047] 
-	  encoded words if and only if non-ASCII characters are present.
 * Fix security issues:
 	- Impose limitations on the imapflags extension regarding the number of
 	  set flags and the length of each flag name.
@@ -36,6 +32,10 @@ Next (in order of descending priority/precedence):
 	- Detect assignment of too large constant values to variables at runtime.
 	- Verify outgoing mail addresses at runtime when necessary
 	  (e.g. after variables substitution)
+	- Vacation: The ":subject" parameter specifies a subject line to attach to 
+	  any vacation response that is generated. UTF-8 characters can be used in
+	  the string argument; implementations MUST convert the string to [RFC2047]
+ 	  encoded words if and only if non-ASCII characters are present.
 * Imapflags: merge execution of setflags, removeflags and addflags into one 
   common implementation. 
 * Warn about the use of syntactically invalid header names. 

src/lib-sieve/plugins/imapflags/ext-imapflags-common.c

@@ -310,6 +310,9 @@ static bool flag_is_valid(const char *flag)
 		 * target mailbox for the message is known. Meaning that the 
 		 * verfication of keyword can only be performed when the
 		 * action side effect is about to be executed.
+		 *
+		 * FIXME: technically this is nonsense, since we can simply parse
+		 * using the flag-keyword grammar provided by imap.
 		 */					
 	}