-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Changes
- -------
Revise and consolidate existing paragraphs 3 and 4 into a shorter functional
description.
Rationale
- ---------
Paragraphs 3 and 4 in 2.3 specify complex, hard to test requirements for
little clear gain. Regarding the redirection as a black box makes the
specification
more concise and allows more space for novel approaches.
- --------------------------------------------------------------------------
[1] Proposed Text
- --------------------------------------------------------------------------
2.3. :list tagged argument to the "redirect" action
Usage: redirect :list
The "redirect" action with the ":list" argument is used to send the
message to one or more email addresses stored in the externally
stored list 'ext-list-name'. This variant of the redirect command
can be used to implement a personal distribution list.
The Sieve engine and list server SHOULD collaborate to achieve a
redirection consistent with the semantics described in [Sieve]. If
they are unable to do so then the situation MUST result in a
runtime error.
See Section 2.4 for the detailed description of syntax used for
naming externally stored lists.
- --------------------------------------------------------------------------
[2] Original Text
- --------------------------------------------------------------------------
2.3. :list tagged argument to the "redirect" action
Usage: redirect :list
The "redirect" action with the ":list" argument is used to send the
message to one or more email addresses stored in the externally
stored list 'ext-list-name'. This variant of the redirect command
can be used to implement a personal distribution list.
Use of this feature requires that the list resolve to a list of email
addresses, and that the Sieve engine be able to enumerate those
addresses. [[anchor5: Alexey would like the option of allowing the
list handler to enumerate the addresses and do the redirect there.
Barry thinks that's contrary to Sieve, which expects to queue the
redirect action for processing at a later stage, and that it would be
a bad idea to have the redirect happen in the list handler. The WG
needs to resolve this issue.]] In cases where, for example, a list
contains hashed email address values or an email address pattern
("sz*(_at_)example(_dot_)com", "*+ietf(_at_)example(_dot_)net"), it will not
be possible to
redirect to that list.
If the Sieve engine [[anchor6: or list handler?]] is permanently
unable to enumerate the list or the list does not resolve to email
addresses, the situation MUST result in a runtime error in the Sieve
script.
See Section 2.4 for the detailed description of syntax used for
naming externally stored lists.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.6)
iQIcBAEBAgAGBQJKaXkZAAoJEHl6NpRAqILLt74P/2VpgofdttuAXkn0TZg60DJC
p3QT+jnnBMNNnBhGXKAQbG+h3REKThAvdDHgsfaAGXWLSQyCqz0ymdHU4S2Stp6w
WvhWJbQ9su1W54+lH7GjND0BCVw9X8ZqSvCSBtUKw+5p9oSOI29mSoR/ytPUspP0
y9qtQHBCjqTpslrOAqva3jtl7mK1iV6kBInfeqrhf/+V4jqAZQxXe3CMxOxPGU2Y
p+pT1cQgl/og76H1ZPomBmyO6RMQFhhELnXoDBp+kDWiHoW/0wpeiNGOl36zMd+H
KwdhxxWRqo26Za+w7oYP8VbV2mohepYEsN+PDcKCnTU+/U+zaS/Wk3HM1u/yVdmj
VGOijT/2NzUyeZZdloBYqN0cG9FLuQ1WBgILGSAyyYgDhHxe9Iss1gHwwfDy4mn7
djVnWBrS1vtr0SEo4Iaxypc7/s8ng3k1/557VZ070+cKuagtimya1qITGUtldU27
gZhwkxhrk3EXszZJBx8Op4qzk44ccZTVaG4i3CeDgSrF3AVF7J2PJnI/Qj4s2vM8
Qpcu+T1UDKOeWAapSPb7OmreKze/RTWi9gT0xiZA9Un3JZ4XcMLnq7BVZHYYzm40
x5ygqW1CWeQ+LOoxSM3wFuV7iAGrJnrtHV4qmCBaD2O9xHm8hEEGgVvfxbQnxWfe
HBXczQZuO61ojHSMCW4U
=g4tW
-----END PGP SIGNATURE-----