Re: Clarifying "implementations MUST NOT allow variable expansion in the script name argument" [WAS Re: I-D Action: draft-ietf-sieve-include-12.txt]
Robert Burrell Donkin <[email protected]>
| Newsgroups | gmane.ietf.mta-filters |
|---|---|
| Message-ID | <CAKTa1mh3ArGqYj4kxqHwLW1jOOf6pzvAuJ4AbYADgrEA6txVTQ@mail.gmail.com> |
On Tue, Sep 27, 2011 at 9:12 PM, Barry Leiba <[email protected]> wrote: > On Tue, Sep 27, 2011 at 16:10, Aaron Stone <[email protected]> wrote: >> The full sentence is: >> >> 187 The script name argument MUST be a constant string as >> 188 defined in <xref target='RFC5229'>VARIABLES</xref>, Section 3; >> 189 implementations MUST NOT allow variable expansion in the script >> 190 name argument. >> >> I believe that this is sufficient, bordering on repeating itself. When an implementation (of this proposed standard) supporting RFC5229 encounters a non-constant string, what behaviour is expected? > I agree; I see no reason to change that text. Which perhaps explains the poor quality of recent output of this working group... Robert _______________________________________________ sieve mailing list [email protected] https://www.ietf.org/mailman/listinfo/sieve