[Ned Freed]:
I really don't want to try and force this into the setdate
framework. I'll see what I can do to write up the approach I have
in mind for this.
thanks.
> oh! if you run the Sieve script in batch, long after the
> delivery was made, the current date is completely useless.
> SETDATE should be changed to initialise the variables to the
> time of delivery, not current time.
Um, no, it may well be that it is the value in the Date: field
that is completely useless. It is all a question of what you're
trying to achieve. [...]
all right, the original idea for adding SETDATE was to use it with
FILEINTO so that you could make archives "dynamically". also, Sieve
is typically used by the delivery agent. the case where a Sieve
client uses IMAP or similar to access the message store after delivery
has taken place, is an edge case. furthermore, the spec says
| These variables SHOULD reference the time when execution of the
| Sieve script reaches the statement.
so such a client is allowed to use Received headers or whatever it
likes to find the date the user wants for SETDATE. still, the intent
is that it references the time of delivery. for the typical use, the
MDA, it doesn't make any difference. for the standalone MFA (mail
filtering agent), it does make a difference, and I think we should be
explicit about what we want the MFA to do.
--
Kjetil T.