Simon Josefsson <jas(_at_)extundo(_dot_)com> writes:
Quoting the document:
,----
| 3. Action addheader
|
| Syntax:
| "addheader" <name: string> <value: string>
|
| The addheader action appends a header field to the existing
| message header.
...
| The header field MUST be added at the end of the existing
| header.
`----
It isn't clear if a Sieve statement
addheader "To" "foo(_at_)bar(_dot_)com";
invoked on a message that have a header
...
To: baz(_at_)foo(_dot_)com
...
To: apa(_at_)baz(_dot_)com
...
will result in:
...
4) A message header that looks like:
...
To: baz(_at_)foo(_dot_)com
...
To: apa(_at_)baz(_dot_)com
...
To: foo(_at_)bar(_dot_)com
Given the meanings layed out in rfc2822 for "header" and "header field",
I don't see how the text can be interpreted as permitting anything
besides #4. The other choices all either appended text *to* a header
field or added the header field somewhere besides the end of the
existing header, neither of which match the text of the draft.
Philip Guenther
guenther(_at_)sendmail(_dot_)com