Requiring that commands appear in one place, the easiest for automated machine handling; at the beginning, is welcomed.
I would also like to suggest that the experience of Debian BTS is applied. There should be a special keyword to *end* commands. See http://www.debian.org/Bugs/server-control#comment "<following words: quit ...> On a line by itself, in any case, possibly followed by whitespace, tells the control server to stop processing the message; the remainder of the message can include explanations, signatures or anything else, none of it will be detected by the control server."
An email example:
From:
Subject:
<COMMAND>
<COMMAND>
quit
stop
thank
thanks
thankyou
thank you
--
Requiring that commands appear in one place, the easiest for automated machine handling; at the beginning, is welcomed.
I would also like to suggest that the experience of Debian BTS is applied. There should be a special keyword to *end* commands. See http:// www.debian. org/Bugs/ server- control# comment "<following words: quit ...> On a line by itself, in any case, possibly followed by whitespace, tells the control server to stop processing the message; the remainder of the message can include explanations, signatures or anything else, none of it will be detected by the control server."
An email example:
From:
Subject:
<COMMAND>
<COMMAND>
quit
stop
thank
thanks
thankyou
thank you
--
<The rest of the bug report body; normal text>