[rfc-dist] RFC 3685 on SIEVE Email Filtering: Spamtest and VirusTest Extensions

rfc-editor@rfc-editor.org rfc-editor@rfc-editor.org
Fri, 06 Feb 2004 10:49:50 -0800


A new Request for Comments is now available in online RFC libraries.

        RFC 3685

        Title:      SIEVE Email Filtering: Spamtest and VirusTest
        Author(s):  C. Daboo
        Status:     Standards Track
        Date:       February 2004
        Mailbox:    daboo@cyrusoft.com
        Pages:      9
        Characters: 17436
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-daboo-sieve-spamtest-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3685.txt

The SIEVE mail filtering language "spamtest" and "virustest"
extensions permit users to use simple, portable commands for spam
and virus tests on email messages.  Each extension provides a new
test using matches against numeric 'scores'.  It is the
responsibility of the underlying SIEVE implementation to do the
actual checks that result in values returned by the tests.  

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

Content-Type: Multipart/Alternative; Boundary="OtherAccess"

Content-Type:  Message/External-body;

Content-Type: text/plain
Content-ID: <040206104821.RFC@RFC-EDITOR.ORG>

DOC-ID: rfc3685

Content-Type:   Message/External-body;

Content-Type: text/plain
Content-ID: <040206104821.RFC@RFC-EDITOR.ORG>