Alexey Melnikov wrote:
Barry Leiba wrote:
I'm looking for consensus on one of these:
1. Using Auto-Submitted to avoid loops -- and, therefore, the risk of
loops if we send notifications for auto-submitted messages -- is
sufficiently important that the current "MUST NOT" text should stay.
2. The use cases for notifications on auto-submitted messages are
sufficiently important that the text should be changed. [Please
suggest new text, in this case.]
3. "SHOULD NOT" is an acceptable compromise. The current "MUST NOT"
should be changed to "SHOULD NOT", with some added text to explain the
danger very clearly. [In this case, you can suggest text, or I'll
craft it.]
Now that you mention this I prefer SHOULD NOT.
So I take it that means:
Implementations SHOULD NOT trigger notifications for messages
containing "Auto-Submitted:" header fields with any value other than
"No".
Then I assume we want to add a clause after that saying something like
"because notifications triggered by such messages can result in mail loops."
/psa
smime.p7s
Description: S/MIME Cryptographic Signature