Ned Freed wrote:
> This actually isn't true. Some Sieve implementations, including ours, operate
> before final delivery. (Usually just before.) Others operate just after. And
> in the imap-sieve case there is now a situation where Sieve can be executate
> LONG after final delivery.
Indeed.
and FYI:
<http://bbiw.net/specifications/draft-crocker-email-arch-10.html>
> Figure 5 shows a Sieve specification going from the rMUA to the MDA. However
> filtering can be done at many different points along the transit path and any
> one or more of them might be subject to Sieve directives, especially within a
> single ADMD. Hence the Figure shows only one relationship, for (relative)
> simplicity.
The document inches ever-closer to finalization, with the intent of
standardization, but the contents represent pretty good community consensus IMO,
and the portion about SIEVE isn't controversial. I believe it never has been.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
IETF mailing list
IETF@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf