Cullen Jennings wrote:
I don't think that is really implementable advice - it basically
wishes the problem away.
It is implementable, it applies to UIs and admin tools and many
implementations already follow it.
More inline ...
On Aug 17, 2007, at 2:34 PM, Alexey Melnikov wrote:
Cullen, does the following address your DISCUSS?
=============================
In section 4.2, last paragraph:
OLD:
Implementations SHOULD take measures to implement loop control,
possibly including adding headers to the message or counting Received
headers. If an implementation detects a loop, it causes an error.
NEW:
Implementations SHOULD take measures to implement loop control,
possibly including adding headers to the message or counting Received
headers as specified in section 6.2 of [SMTP]. If an
implementation detects a loop, it causes an error.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Add to the end of section 4.2 two new paragraphs:
Implementations SHOULD provide means of limiting the number of
redirects a
Sieve script can perform.
Well if it was the number of redirects SHOULD be limited to one it
would do it but as it is - not sure I see how it helps.
Cullen, I told you before, there is very strong WG consensus to allow
implementations to use more than one.
Please see
<http://www.imc.org/ietf-mta-filters/mail-archive/msg03601.html> and
<http://www.imc.org/ietf-mta-filters/mail-archive/msg03599.html>.
Now, if you have another suggestion how to address your issue, I would
like to hear it.