Alexey Melnikov writes:
After thinking more about comments received regarding the reject
draft, I would propose that instead of adding options to reject that
would make it behave "do X if able to reject message over protocol
and nothing otherwise" (originally proposed by Kejtil, if I am not
mistaken), we should define proper Sieve environment test extension.
The extension should define something for testing if Sieve engine is
running in MTA/MDA, versa running in MDA.
That's not equivalent. The equivalent would be "is sieve engine running
in MTA/MDA, and do all recipients of this invoke the reject action?".
That seems a little odd for an enviroment test extension. If course
it's possible to simplify a little and ask e.g. "is sieve engine
running in MTA/MDA, and is this a single-recipient message?" which
still seems out of scope for an environment test.
So I would like to poll the WG regarding the following:
1). Does the WG has enough information to decide if this is a
reasonable suggestion?
Perhaps.
2). If the answer to #1 is yes, does the WG want to delay publication
of reject until after the environment extension is done, or is it Ok
to submit it to IESG sooner?
No.
Arnt