Ned Freed <ned(_dot_)freed(_at_)mrochek(_dot_)com> wrote:
Ned Freed <ned(_dot_)freed(_at_)mrochek(_dot_)com> wrote:
OK, but the problem is that the text above isn't correct. The language
*does* have loops,
Really? That's news to me. The loop construct that has been proposed for sieve
isn't a loop in the usual programming language sense - rather, it allows for
fixed iteration over the MIME structure of the message. AFAIK there's no way
to
create an infinite loop or even a loop where the number of iterates is set by
the script. And this is in any case an extension, not something in the core
language.
As I observed in my original review, I believe you may be able to
construct a loop using the redirect construct. It's not a loop internal
only to the sieve-processing MTA, but that doesn't mean it's not a loop.
Indeed, it's not clear to me that the langague isn't Turing complete at this
point.
Then please provide a script that loops indefinitely. I don't know how to
construct one myself.
Well, I'm no mail expert, but it looks to me that if you write a
redirect rule that goes to an unknown address, it may be possible
to create a loop. The key question is what the envelope sender
address is, which sieve leaves open (S 4.2).
The envelope sender address on the outgoing message is chosen by the
sieve implementation. It MAY be copied from the original message.
If you your own address, this creates a loop, right?
-Ekr