X-Git-Url: https://git.exim.org/users/jgh/exim.git/blobdiff_plain/495ae4b01f36d0d8bb0e34a1d7263c2b8224aa4a..f331f3b639d802237239c3c3a19883ee89d062b5:/doc/doc-txt/README.SIEVE diff --git a/doc/doc-txt/README.SIEVE b/doc/doc-txt/README.SIEVE index 4d04851e1..53d5b01ed 100644 --- a/doc/doc-txt/README.SIEVE +++ b/doc/doc-txt/README.SIEVE @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/README.SIEVE,v 1.1 2004/10/07 15:04:35 ph10 Exp $ +$Cambridge: exim/doc/doc-txt/README.SIEVE,v 1.3 2005/03/29 15:21:57 ph10 Exp $ Notes on the Sieve implementation for Exim @@ -114,13 +114,14 @@ This may be implemented in future by adding a header line to mails that are filed into "inbox" due to an error in the filter. -Strings Containing Header Names +Strings Containing Header Names Or Envelope Elements RFC 3028 does not specify what happens if a string denoting a header -field does not contain a valid header name, e.g. it contains a colon. +field or envelope element does not contain a valid name, e.g. it +contains a colon for a header or it is not "from" or "to" for envelopes. This implementation generates an error instead of ignoring the header -field in order to ease script debugging, which fits in the common -picture of Sieve. +field in order to ease script debugging, which fits in the common picture +of Sieve. Header Test With Invalid MIME Encoding In Header @@ -363,12 +364,6 @@ is not required by the vacation draft, which does not specify how the UTF-8 reason is processed to compose the resulting message. -Envelope Sender - -The vacation draft does not specify the envelope sender. This -implementation uses the empty envelope sender to prevent mail loops. - - Default Subject The draft specifies that the default message subject is "Re: " @@ -388,25 +383,10 @@ the current draft concerning automatic mail responses. Rate Limiting Responses -The draft says: - - Vacation responses are not just per address, but are per address - per vacation command. - -This is badly worded, because commands are not enumerated. It meant -to say: - - Vacation responses are not just per address, but are per address - per reason string and per specified subject and ":mime" option. - -Existing implementations work that way and it makes more sense, too. -Including the ":mime" option is mostly for correctness, as the reason -strings with and without this option are rarely equal. - -This implementation hashes the reason, specified subject and ":mime" -option and uses the hex string representation as filename within the -"sieve_vacation_directory" to store the recipient addresses for this -vacation parameter set. +This implementation hashes the reason, specified subject, ":mime" +option and ":addresses" option and uses the hex string representation +as filename within the "sieve_vacation_directory" to store the recipient +addresses for this vacation parameter set. The draft specifies that sites may define a minimum ":days" value than 1. This implementation uses 1. The maximum value MUST greater than 7,