draft-ietf-sieve-spamtestbis-02.txt   draft-ietf-sieve-spamtestbis-03.txt 
SIEVE Email Filtering Working C. Daboo SIEVE Email Filtering Working C. Daboo
Group January 20, 2006 Group June 12, 2006
Internet-Draft Internet-Draft
Expires: July 24, 2006 Expires: December 14, 2006
SIEVE Email Filtering: Spamtest and Virustest Extensions SIEVE Email Filtering: Spamtest and Virustest Extensions
draft-ietf-sieve-spamtestbis-02 draft-ietf-sieve-spamtestbis-03
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 24, 2006. This Internet-Draft will expire on December 14, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
The SIEVE email filtering language "spamtest", "spamtestplus" and The SIEVE email filtering language "spamtest", "spamtestplus" and
"virustest" extensions permit users to use simple, portable commands "virustest" extensions permit users to use simple, portable commands
for spam and virus tests on email messages. Each extension provides for spam and virus tests on email messages. Each extension provides
a new test using matches against numeric 'scores'. It is the a new test using matches against numeric "scores". It is the
responsibility of the underlying SIEVE implementation to do the responsibility of the underlying SIEVE implementation to do the
actual checks that result in values returned by the tests. actual checks that result in proper input to the tests.
Change History (to be removed prior to publication as an RFC) Change History (to be removed prior to publication as an RFC)
Changes from -02:
1. Changed formatting of tables.
2. Fixed missing 2119 definitions.
3. Moved reference to previous extension to informative.
4. Minor text improvements.
5. Fixed some single/double quote issues.
6. Reworded abstract, introduction and overview to use better SIEVE
terminology when describing tests, commands and results.
7. Remove "untested" string result from ":percent" test.
8. Allow ":count" match type to be used for tested/untested checks.
Changes from -01: Changes from -01:
1. Changed ACAP reference to i18n-comparators draft. 1. Changed ACAP reference to i18n-comparators draft.
2. Changed MUST in security section for virus checker updates to 2. Changed MUST in security section for virus checker updates to
plain must. plain must.
3. Return string "untested" when :percent is used and no test has 3. Return string "untested" when :percent is used and no test has
been done. been done.
4. Remove MUST NOT for having both spamtestplus and spamtest 4. Remove MUST NOT for having both spamtestplus and spamtest
capabilities present, and instead make it a SHOULD NOT. capabilities present, and instead make it a SHOULD NOT.
5. Add text to state that implementations MUST return an error if 5. Add text to state that implementations MUST return an error if
spamtestplus is not present when :percent is used. spamtestplus is not present when :percent is used.
6. Tweak first para of security considerations to better reflect 6. Tweak first para of security considerations to better reflect
reality of testing. reality of testing.
7. Syntax -> Usage. 7. Syntax -> Usage.
8. Updated references to 3028bis and 3431bis. 8. Updated references to 3028bis and 3431bis.
Changes from -00: Changes from -00:
1. Added description of how to check for untested when using 1. Added description of how to check for untested when using
:percent. :percent.
2. Changed requires item to 'spamtestplus'. 2. Changed requires item to "spamtestplus".
3. Changed text describing which requires item needs to be present. 3. Changed text describing which requires item needs to be present.
Changes from RFC3685: Changes from RFC3685:
1. Added ':percent' argument to spamtest. 1. Added ":percent" argument to spamtest.
Table of Contents Table of Contents
1. Introduction and Overview . . . . . . . . . . . . . . . . . . 4 1. Introduction and Overview . . . . . . . . . . . . . . . . . . 4
2. Conventions Used in This Document . . . . . . . . . . . . . . 4 2. Conventions Used in This Document . . . . . . . . . . . . . . 4
3. SIEVE Extensions . . . . . . . . . . . . . . . . . . . . . . . 5 3. SIEVE Extensions . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. General Considerations . . . . . . . . . . . . . . . . . . 5 3.1. General Considerations . . . . . . . . . . . . . . . . . . 5
3.2. Test spamtest . . . . . . . . . . . . . . . . . . . . . . 5 3.2. Test spamtest . . . . . . . . . . . . . . . . . . . . . . 5
3.2.1. spamtest without :percent argument . . . . . . . . . . 6 3.2.1. spamtest without :percent argument . . . . . . . . . . 6
3.2.2. spamtest with :percent argument . . . . . . . . . . . 6 3.2.2. spamtest with :percent argument . . . . . . . . . . . 7
3.3. Test virustest . . . . . . . . . . . . . . . . . . . . . . 7 3.3. Test virustest . . . . . . . . . . . . . . . . . . . . . . 9
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
5.1. spamtestplus registration . . . . . . . . . . . . . . . . 9 5.1. spamtest registration . . . . . . . . . . . . . . . . . . 11
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.2. virustest registration . . . . . . . . . . . . . . . . . . 12
6.1. Normative References . . . . . . . . . . . . . . . . . . . 10 5.3. spamtestplus registration . . . . . . . . . . . . . . . . 12
6.2. Informative References . . . . . . . . . . . . . . . . . . 10 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 10 6.1. Normative References . . . . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 11 6.2. Informative References . . . . . . . . . . . . . . . . . . 13
Intellectual Property and Copyright Statements . . . . . . . . . . 12 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 13
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14
Intellectual Property and Copyright Statements . . . . . . . . . . 15
1. Introduction and Overview 1. Introduction and Overview
SIEVE scripts are frequently being used to do spam and virus SIEVE scripts are frequently being used to do spam and virus
filtering based on either implicit script tests (e.g. tests for filtering based on either implicit script tests (e.g. tests for
'black-listed' senders directly encoded in the SIEVE script), or via "black-listed" senders directly encoded in the SIEVE script), or via
testing messages modified by some external spam or virus checker that testing messages modified by some external spam or virus checker that
handled the message prior to SIEVE. The use of third-party spam and handled the message prior to SIEVE. The use of third-party spam and
virus checker tools poses a problem since each tool has its own way virus checker tools poses a problem since each tool has its own way
of indicating the result of its checks. These usually take the form of indicating the result of its checks. These usually take the form
of a header added to the message, the content of which indicates the of a header added to the message, the content of which indicates the
status using some syntax defined by the particular tool. Each user status using some syntax defined by the particular tool. Each user
has to then create their own SIEVE scripts to match the contents of has to then create their own SIEVE scripts to match the contents of
these headers to do filtering. This requires the script to stay in these headers to do filtering. This requires the script to stay in
synchronisation with the third party tool as it gets updated or synchronization with the third party tool as it gets updated or
perhaps replaced with another. Thus scripts become tied to specific perhaps replaced with another. Thus scripts become tied to specific
environments, and lose portability. environments, and lose portability.
The purpose of this document is to introduce two SIEVE tests that can The purpose of this document is to introduce two SIEVE tests that can
be used to implement 'generic' tests for spam and viruses in messages be used to implement "generic" tests for spam and viruses in messages
processed via SIEVE scripts. These tests return a string containing processed via SIEVE scripts. The spam and virus checks themselves
a range of numeric values that indicate the severity of spam or are handled by the underlying SIEVE implementation in whatever manner
viruses in a message, or a string that indicates the message has not is appropriate, so that the SIEVE spam and virus test commands can be
passed through any spam or virus checking tools, or provides a direct used in a portable way.
indication of whether the message has been tested for spam or not.
The spam and virus checks themselves are handled by the underlying
SIEVE implementation in whatever manner is appropriate, and the
implementation maps the results of these checks into the numeric
ranges defined by the new tests. Thus a SIEVE implementation can
have a spam test that implicitly checks for third-party spam tool
headers and determines how those map into the spamtest numeric range.
In order to do numeric comparisons against the returned strings, In order to do numeric comparisons against the returned strings,
server implementations MUST also support the SIEVE relational server implementations MUST also support the SIEVE relational
[I-D.ietf-sieve-3431bis] extension, in addition to the extensions [I-D.ietf-sieve-3431bis] extension, in addition to the extensions
described here. All examples below assume the relational extension described here. All examples below assume the relational extension
is present. is present.
2. Conventions Used in This Document 2. Conventions Used in This Document
Conventions for notations are as in [I-D.ietf-sieve-3028bis] section Conventions for notations are as in [I-D.ietf-sieve-3028bis] section
1.1, including use of [RFC2119]. 1.1.
The term 'spam' is used in this document to refer to unsolicited or The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
The term "spam" is used in this document to refer to unsolicited or
unwanted email messages. This document does not attempt to define unwanted email messages. This document does not attempt to define
what exactly constitutes spam, or how it should be identified, or what exactly constitutes spam, or how it should be identified, or
what actions should be taken when detected. what actions should be taken when detected.
The term 'virus' is used in this document to refer to any type of The term "virus" is used in this document to refer to any type of
message whose content can cause malicious damage. This document does message whose content can cause malicious damage. This document does
not attempt to define what exactly constitutes a virus, or how it not attempt to define what exactly constitutes a virus, or how it
should be identified, or what actions should be taken when detected. should be identified, or what actions should be taken when detected.
3. SIEVE Extensions 3. SIEVE Extensions
3.1. General Considerations 3.1. General Considerations
The "spamtest" and "virustest" tests described below can both return The "spamtest" and "virustest" tests described below evaluate the
a string that starts with a numeric value, followed by an optional results of implementation-specific spam and virus checks in a
space (%x20) character and optional arbitrary text. The numeric portable way. The implementation may, for example, check for third-
value can be compared to specific values using the SIEVE relational party spam tool headers and determine how those map into the way the
[I-D.ietf-sieve-3431bis] extension in conjunction with the "i;ascii- test commands are used. To do this, the underlying SIEVE
numeric" comparator [I-D.newman-i18n-comparator], which will test for implementation provides a normalized result string as one of the
the presence of a numeric value at the start of the string, ignoring inputs to each test command. The normalized result string is
any additional text in the string. The additional text can be used considered to be the value on the left hand side of the test, and the
to carry implementation specific details about the tests performed comparison values given in the test command are considered to be on
and descriptive comments about the result. Tests can be done using the right hand side.
standard string comparators against this text if it helps to refine
behaviour, however this will break portability of the script as the The normalized result starts with a digit string, with its numeric
text will likely be specific to a particular implementation. value within the range of values used by the specific test,
indicating the severity of spam or viruses in a message or whether
any tests were done at all. This may optionally be followed by a
space (%x20) character and arbitrary text, or in one specific case a
single keyword is returned. The numeric value can be compared to
specific values using the SIEVE relational [I-D.ietf-sieve-3431bis]
extension in conjunction with the "i;ascii-numeric" comparator
[I-D.newman-i18n-comparator], which will test for the presence of a
numeric value at the start of the string, ignoring any additional
text in the string. The optional text can be used to carry
implementation specific details about the tests and descriptive
comments about the result. Tests can be done using standard string
comparators against this text if it helps to refine behavior, however
this will break portability of the script as the text will likely be
specific to a particular implementation.
In addition, the SIEVE relational [I-D.ietf-sieve-3431bis] ":count"
match type can be used to determine if the underlying implementation
actually did a test. If the underlying spam or virus test was done,
the ":count" of the normalized result will return the numeric value
"1", whilst if the test was not done, the ":count" value will be "0"
(zero).
3.2. Test spamtest 3.2. Test spamtest
Usage: spamtest [":percent"] [COMPARATOR] [MATCH-TYPE] Usage: spamtest [":percent"] [COMPARATOR] [MATCH-TYPE]
<value: string> <value: string>
SIEVE implementations that implement the "spamtest" test use an SIEVE implementations that implement the "spamtest" test use an
identifier of either "spamtest" or "spamtestplus" for use with the identifier of either "spamtest" or "spamtestplus" for use with the
capability mechanism. capability mechanism.
If the ":percent" argument is not used with any spamtest test, then If the ":percent" argument is not used with any spamtest test, then
one of either the "spamtest" or "spamtestplus" capability identifiers one of either the "spamtest" or "spamtestplus" capability identifiers
MUST be present. MUST be present.
If the ":percent" argument is used with any spamtest test, then the If the ":percent" argument is used with any spamtest test, then the
"spamtestplus" capability identifier MUST be present. SIEVE "spamtestplus" capability identifier MUST be present. SIEVE
skipping to change at page 5, line 49 skipping to change at page 6, line 20
MUST be present. MUST be present.
If the ":percent" argument is used with any spamtest test, then the If the ":percent" argument is used with any spamtest test, then the
"spamtestplus" capability identifier MUST be present. SIEVE "spamtestplus" capability identifier MUST be present. SIEVE
implementations MUST return an error if the ":percent" argument is implementations MUST return an error if the ":percent" argument is
used and "spamtestplus" is not specified. used and "spamtestplus" is not specified.
In the interests of brevity and clarity, scripts SHOULD NOT specify In the interests of brevity and clarity, scripts SHOULD NOT specify
both "spamtestplus" and "spamtest" capability identifiers together. both "spamtestplus" and "spamtest" capability identifiers together.
The "spamtest" test evaluates to true if the spamtest result matches The "spamtest" test evaluates to true if the normalized spamtest
the value. The type of match is specified by the optional match result matches the value. The type of match is specified by the
argument, which defaults to ":is" if not specified. optional match argument, which defaults to ":is" if not specified.
3.2.1. spamtest without :percent argument 3.2.1. spamtest without :percent argument
When the ":percent" argument is not present in the "spamtest" test, When the ":percent" argument is not present in the "spamtest" test,
the result of the test is a string starting with a numeric value in the normalized result string provided for the left hand side of the
the range "0" (zero) through "10", with meanings summarised below: test starts with a numeric value in the range "0" (zero) through
"10", with meanings summarized below:
spamtest interpretation
value
0 message was not tested for spam +----------+--------------------------------------------------------+
1 message was tested and is clear of spam | spamtest | interpretation |
2 - 9 message was tested and has a varying likelihood | value | |
of containing spam in increasing order +----------+--------------------------------------------------------+
10 message was tested and definitely contains spam | 0 | message was not tested for spam |
| 1 | message was tested and is clear of spam |
| 2 - 9 | message was tested and has a varying likelihood of |
| | containing spam in increasing order |
| 10 | message was tested and definitely contains spam |
+----------+--------------------------------------------------------+
The underlying SIEVE implementation will map whatever spam check is The underlying SIEVE implementation will map whatever spam check is
done into this numeric range, as appropriate. done into this numeric range, as appropriate.
Examples: Examples:
require ["spamtest", "fileinto", require ["spamtest", "fileinto",
"relational", "comparator-i;ascii-numeric"]; "relational", "comparator-i;ascii-numeric"];
if spamtest :value "eq" :comparator "i;ascii-numeric" "0" if spamtest :value "eq" :comparator "i;ascii-numeric" "0"
{ {
fileinto "INBOX.unclassified"; fileinto "INBOX.unclassified";
} }
elsif spamtest :value "ge" :comparator "i;ascii-numeric" "3" elsif spamtest :value "ge" :comparator "i;ascii-numeric" "3"
{ {
fileinto "INBOX.spam-trap"; fileinto "INBOX.spam-trap";
} }
In this example, any message that has not passed through a spam check In this example, any message that has not passed through a spam check
tool will be filed into the mailbox "INBOX.unclassified". Any tool will be filed into the mailbox "INBOX.unclassified". Any
message with a spamtest value greater than or equal to "3" is filed message with a normalized result value greater than or equal to "3"
into a mailbox called "INBOX.spam-trap" in the user's mailstore. is filed into a mailbox called "INBOX.spam-trap" in the user's
mailstore.
3.2.2. spamtest with :percent argument 3.2.2. spamtest with :percent argument
When the ":percent" argument is present in the "spamtest" test, the When the ":percent" argument is present in the "spamtest" test, the
result of the test is a string starting with a numeric value in the normalized result string provided for the left hand side of the test
range "0" (zero) through "100", with meanings summarised below, or starts with a numeric value in the range "0" (zero) through "100",
the string "untested" for the case where the message was not tested with meanings summarized below:
for spam (corresponding to the "0" value returned when the ":percent"
argument is not used):
spamtest interpretation
value
"untested" message was not tested for spam +----------+--------------------------------------------------------+
0 message was tested and is clear of spam | spamtest | interpretation |
1 - 99 message was tested and has a varying likelihood | value | |
of containing spam in increasing order +----------+--------------------------------------------------------+
100 message was tested and definitely contains spam | 0 | message was tested and is clear of spam, or was not |
| | tested for spam |
| 1 - 99 | message was tested and has a varying likelihood of |
| | containing spam in increasing order based on the |
| | spamtest value |
| 100 | message was tested and definitely contains spam |
+----------+--------------------------------------------------------+
The underlying SIEVE implementation will map whatever spam check is The underlying SIEVE implementation will map whatever spam check is
done into the numeric range, as appropriate. done into the numeric range, as appropriate.
To determine whether the message was tested for spam or not, the To determine whether the message was tested for spam or not, the
preferred solution is to use the test without the ":percent" preferred solution is to use the test without the ":percent"
argument, testing for the value "0" as described in Section 3.2.1. argument, testing for the normalized result value "0" as described in
Section 3.2.1.
Examples: Examples:
require ["spamtestplus", "fileinto", require ["spamtestplus", "fileinto",
"relational", "comparator-i;ascii-numeric"]; "relational", "comparator-i;ascii-numeric"];
if spamtest :value "eq" if spamtest :value "eq"
:comparator "i;ascii-numeric" "0" :comparator "i;ascii-numeric" "0"
{ {
fileinto "INBOX.unclassified"; fileinto "INBOX.unclassified";
} }
elsif spamtest :percent :value "ge" elsif spamtest :percent :value "eq"
:comparator "i;ascii-numeric" "30" :comparator "i;ascii-numeric" "0"
{
fileinto "INBOX.not-spam";
}
elsif spamtest :percent :value "lt"
:comparator "i;ascii-numeric" "37"
{ {
fileinto "INBOX.spam-trap"; fileinto "INBOX.spam-trap";
} }
else
{
discard;
}
In this example, any message that has not passed through a spam check In this example, any message that has not passed through a spam check
tool will be filed into the mailbox "INBOX.unclassified". Any tool will be filed into the mailbox "INBOX.unclassified". Any
message with a spamtest percentage value greater than or equal to message that is classified as definitely not containing spam
"30" is filed into a mailbox called "INBOX.spam-trap" in the user's (normalized result value "0") will be filed into the mailbox
mailstore. "INBOX.not-spam". Any message with a normalized result value less
than "37" is filed into a mailbox called "INBOX.spam-trap" in the
user's mailstore. Any other normalized result value will result in
the message being discarded.
Alternatively, the SIEVE relational [I-D.ietf-sieve-3431bis] ":count"
match type can be used:
Examples:
if spamtest :percent :count "eq"
:comparator "i;ascii-numeric" "0"
{
fileinto "INBOX.unclassified";
}
elsif spamtest :percent :value "eq"
:comparator "i;ascii-numeric" "0"
{
fileinto "INBOX.not-spam";
}
elsif spamtest :percent :value "lt"
:comparator "i;ascii-numeric" "37"
{
fileinto "INBOX.spam-trap";
}
else
{
discard;
}
This example will result in exactly the same behavior as the previous
one.
3.3. Test virustest 3.3. Test virustest
Usage: virustest [COMPARATOR] [MATCH-TYPE] Usage: virustest [COMPARATOR] [MATCH-TYPE]
<value: string> <value: string>
SIEVE implementations that implement the "virustest" test have an SIEVE implementations that implement the "virustest" test have an
identifier of "virustest" for use with the capability mechanism. identifier of "virustest" for use with the capability mechanism.
The "virustest" test evaluates to true if the virustest result The "virustest" test evaluates to true if the normalized result
matches the value. The type of match is specified by the optional string matches the value. The type of match is specified by the
match argument, which defaults to ":is" if not specified. optional match argument, which defaults to ":is" if not specified.
The virustest result is a string starting with a numeric value in the
range "0" (zero) through "5", with meanings summarised below:
virustest interpretation The normalized result string provided for the left side of the test
value starts with a numeric value in the range "0" (zero) through "5", with
meanings summarized below:
0 message was not tested for viruses +-----------+-------------------------------------------------------+
1 message was tested and contains no known viruses | virustest | interpretation |
2 message was tested and contained a known virus | value | |
which was replaced with harmless content +-----------+-------------------------------------------------------+
3 message was tested and contained a known virus | 0 | message was not tested for viruses |
which was "cured" such that it is now harmless | 1 | message was tested and contains no known viruses |
4 message was tested and possibly contains a | 2 | message was tested and contained a known virus which |
known virus | | was replaced with harmless content |
5 message was tested and definately contains a | 3 | message was tested and contained a known virus which |
known virus | | was "cured" such that it is now harmless |
| 4 | message was tested and possibly contains a known |
| | virus |
| 5 | message was tested and definately contains a known |
| | virus |
+-----------+-------------------------------------------------------+
The underlying SIEVE implementation will map whatever virus checks The underlying SIEVE implementation will map whatever virus checks
are done into this numeric range, as appropriate. If the message has are done into this numeric range, as appropriate. If the message has
not been categorised by any virus checking tools, then the virustest not been categorized by any virus checking tools, then the virustest
result is "0". result is "0".
Example: Example:
require ["virustest", "fileinto", require ["virustest", "fileinto",
"relational", "comparator-i;ascii-numeric"]; "relational", "comparator-i;ascii-numeric"];
if virustest :value "eq" :comparator "i;ascii-numeric" "0" if virustest :value "eq" :comparator "i;ascii-numeric" "0"
{ {
fileinto "INBOX.unclassified"; fileinto "INBOX.unclassified";
skipping to change at page 8, line 48 skipping to change at page 10, line 37
{ {
fileinto "INBOX.quarantine"; fileinto "INBOX.quarantine";
} }
elsif virustest :value "eq" :comparator "i;ascii-numeric" "5" elsif virustest :value "eq" :comparator "i;ascii-numeric" "5"
{ {
discard; discard;
} }
In this example, any message that has not passed through a virus In this example, any message that has not passed through a virus
check tool will be filed into the mailbox "INBOX.unclassified". Any check tool will be filed into the mailbox "INBOX.unclassified". Any
message with a virustest value equal to "4" is filed into a mailbox message with a normalized result value equal to "4" is filed into a
called "INBOX.quarantine" in the user's mailstore. Any message with mailbox called "INBOX.quarantine" in the user's mailstore. Any
a virustest value equal to "5" is discarded (removed) and not message with a normalized result value equal to "5" is discarded
delivered to the user's mailstore. (removed) and not delivered to the user's mailstore.
4. Security Considerations 4. Security Considerations
SIEVE implementations SHOULD ensure that "spamtest" and "virustest" SIEVE implementations SHOULD ensure that "spamtest" and "virustest"
tests only report spam and virus test results for messages that tests only report spam and virus test results for messages that
actually have gone through a legitimate spam or virus check process. actually have gone through a legitimate spam or virus check process.
In particular, if such checks rely on the addition and subsequent In particular, if such checks rely on the addition and subsequent
checking of private header fields, it is the responsibility of the checking of private header fields, it is the responsibility of the
implementation to ensure that such headers cannot be spoofed by the implementation to ensure that such headers cannot be spoofed by the
sender or intermediary and thereby prevent the implementation from sender or intermediary and thereby prevent the implementation from
skipping to change at page 9, line 30 skipping to change at page 11, line 20
viruses, and they should continue to exercise caution when dealing viruses, and they should continue to exercise caution when dealing
with messages of unknown content and origin. with messages of unknown content and origin.
Beyond that, the "spamtest" and "virustest" extensions do not raise Beyond that, the "spamtest" and "virustest" extensions do not raise
any security considerations that are not present in the base any security considerations that are not present in the base
[I-D.ietf-sieve-3028bis] protocol, and these issues are discussed in [I-D.ietf-sieve-3028bis] protocol, and these issues are discussed in
[I-D.ietf-sieve-3028bis]. [I-D.ietf-sieve-3028bis].
5. IANA Considerations 5. IANA Considerations
The following template specifies the IANA registration of the Sieve The following templates specify the IANA registration of the Sieve
extensions specified in this document, that are not already extensions specified in this document. The registrations for
registered in [RFC3685]: "spamtest" and "virustest" replace those from in [RFC3685]:
5.1. spamtestplus registration 5.1. spamtest registration
To: iana@iana.org To: iana@iana.org
Subject: Registration of new Sieve extension Subject: Registration of new Sieve extension
Capability name: spamtestplus Capability name: spamtest
Capability keyword: spamtest Capability keyword: spamtest
Capability arguments: N/A
Standards Track/IESG-approved experimental RFC number: this RFC
Person and email address to contact for further information:
Cyrus Daboo
<mailto:cyrus@daboo.name>
This information should be added to the list of sieve extensions
given on http://www.iana.org/assignments/sieve-extensions.
5.2. virustest registration
To: iana@iana.org
Subject: Registration of new Sieve extension
Capability name: virustest
Capability keyword: virustest
Capability arguments: N/A
Standards Track/IESG-approved experimental RFC number: this RFC
Person and email address to contact for further information:
Cyrus Daboo
<mailto:cyrus@daboo.name>
This information should be added to the list of sieve extensions
given on http://www.iana.org/assignments/sieve-extensions.
5.3. spamtestplus registration
To: iana@iana.org
Subject: Registration of new Sieve extension
Capability name: spamtestplus
Capability keyword: spamtestplus
Capability arguments: :percent Capability arguments: :percent
Standards Track/IESG-approved experimental RFC number: this RFC Standards Track/IESG-approved experimental RFC number: this RFC
Person and email address to contact for further information: Person and email address to contact for further information:
Cyrus Daboo Cyrus Daboo
<mailto:cyrus@daboo.name> <mailto:cyrus@daboo.name>
This information should be added to the list of sieve extensions This information should be added to the list of sieve extensions
given on http://www.iana.org/assignments/sieve-extensions. given on http://www.iana.org/assignments/sieve-extensions.
6. References 6. References
6.1. Normative References 6.1. Normative References
[I-D.ietf-sieve-3028bis] [I-D.ietf-sieve-3028bis]
Showalter, T. and P. Guenther, "Sieve: An Email Filtering Showalter, T. and P. Guenther, "Sieve: An Email Filtering
Language", draft-ietf-sieve-3028bis-05 (work in progress), Language", draft-ietf-sieve-3028bis-06 (work in progress),
November 2005. March 2006.
[I-D.ietf-sieve-3431bis] [I-D.ietf-sieve-3431bis]
Segmuller, W. and B. Leiba, "Sieve Extension: Relational Segmuller, W. and B. Leiba, "Sieve Extension: Relational
Tests", draft-ietf-sieve-3431bis-04 (work in progress), Tests", draft-ietf-sieve-3431bis-04 (work in progress),
December 2005. December 2005.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3685] Daboo, C., "SIEVE Email Filtering: Spamtest and VirusTest
Extensions", RFC 3685, February 2004.
6.2. Informative References 6.2. Informative References
[I-D.newman-i18n-comparator] [I-D.newman-i18n-comparator]
Newman, C., "Internet Application Protocol Collation Newman, C., "Internet Application Protocol Collation
Registry", draft-newman-i18n-comparator-05 (work in Registry", draft-newman-i18n-comparator-11 (work in
progress), September 2005. progress), May 2006.
[RFC3685] Daboo, C., "SIEVE Email Filtering: Spamtest and VirusTest
Extensions", RFC 3685, February 2004.
Appendix A. Acknowledgments Appendix A. Acknowledgments
Thanks to Tony Hansen, Jutta Degener, Ned Freed, Ashish Gawarikar, Thanks to Mark E. Mallett, Tony Hansen, Jutta Degener, Ned Freed,
Alexey Melnikov and Nigel Swinson for comments and corrections. Ashish Gawarikar, Alexey Melnikov and Nigel Swinson for comments and
corrections.
Author's Address Author's Address
Cyrus Daboo Cyrus Daboo
Email: cyrus@daboo.name Email: cyrus@daboo.name
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
 End of changes. 41 change blocks. 
121 lines changed or deleted 237 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/