List of open issues with Sieve reject draft (draft-ietf-sieve-refuse-reject-02.txt)

[Alexey Melnikov <[e-mail]>]

1). “SHOULD be incompatible with other actions” is too strong, for 
example there are good reasons to do reject+fileinto.

I tend to agree that reject should be made compatible with other actions 
(except for vacation), so I would like to at least downgrade SHOULD to MAY.

2). Non ASCII text in rejection string - should it cause creation of 
DSN/MDN, runtime error or stripping of non-ASCII content?
Should we add a tagged argument to control this?
Or maybe we need another capability to enable UTF-8 clean rejection?

I am leaning toward having an extra capability to enable UTF-8 rejection 
text over SMTP/LMTP protocol.

3). Arnt has requested to allow for reject+redirect to be treated as 
just reject. I am not sure I like that. Opinions?

Comments?

Alexey