1
Date: Sun, 19 Oct 2008 12:31:58 +0200
2
From: Stephan Bosch <stephan@rename-it.nl>
3
To: ietf-mta-filters@imc.org
4
Subject: Questions regarding RFC 5228
5
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
6
Content-Transfer-Encoding: 7bit
10
I am finishing up a first release of my Sieve implementation, and one of
11
the TODO items that yet remains is getting some answers to questions
12
that arose during development. I've collected these into a file an now I
13
submit them to this list to get some clarification. Any help is greatly
16
* RFC 5228 (Sieve) : 5.1. Test address:
17
"Implementations MUST restrict the address test to headers that contain
18
addresses, but MUST include at least From, To, Cc, Bcc, Sender,
19
Resent-From, and Resent-To, and it SHOULD include any other header that
20
utilizes an "address-list" structured header body."
22
-> Will this cause a compile error, or are the disallowed headers
23
simply ignored? My implementation currently considers this to be a
25
-> Given the variables extension, sometimes the specified header names
26
aren't known until runtime. If the previous answer was to cause a
27
compile error, should this abort the script at runtime?
29
* RFC 5228 (Sieve) : 5.4. Test envelope:
30
"The "envelope" test is true if the specified part of the [SMTP] (or
31
equivalent) envelope matches the specified key. This specification
32
defines the interpretation of the (case insensitive) "from" and "to"
33
envelope-parts. Additional envelope-parts may be defined by other
34
extensions; implementations SHOULD consider unknown envelope parts an
37
-> Given the variables extension, sometimes the specified envelope
38
parts aren't known until runtime. Should invalid ones abort the script
39
or is ignoring them a better practice?