Arnt Gulbrandsen wrote:
Cyrus Daboo writes:
But SIEVE has to operate on the message data - there isn't enough
information before the DATA command to run SIEVE, unless you extend
SIEVE with tests for SMTP-Envelope data (e.g. a MAIL FROM test).
As I remember the draft I read, a spamtest implementation can legally
arrive at a conclusion without considering the body, so if the
script's first rule is a spam test, the body need not be considered.
(I agree that the body will almost always be considered.)
In theory any Sieve script that doesn't test message headers/body can be
executed before DATA command.
But the task of checking if a Sieve script doesn't require message
content might not be a trivial task. Especially if the Sieve engine also
supports variables.
So I would rather ignore the issue of executing Sieve scripts before
DATA command in the Sieve "refuse" extension.
Anyway, I think the possibility of e.g. a future MAIL FROM test is
reason enough to _permit_ the refusal to happen at any stage of the
SMTP/LTMP process.
Frankly any system-wide script like that is better left to the SMTP
implentation's own filtering/ruleset behaviour.
Sure, but that own filtering behaviour might just be sieve ;)
Alexey
__________________________________________
Isode Limited, http://www.isode.com
IETF standard related pages:
http://www.melnikov.ca/mel/devel/Links.html
Personal Home Page: http://www.melnikov.ca
__________________________________________