draft-reject
“SHOULD be incompatible with other actions” is too strong, for example there are good reasons to do reject+fileinto.
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?
/var/www/sieve.info/data/pages/draft-reject.txt · Last modified: 2008/04/17 17:36 (external edit)