Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

SIEVE Email Filtering: Spamtest and VirusTest Extensions (RFC3685)

IP.com Disclosure Number: IPCOM000021743D
Original Publication Date: 2004-Feb-01
Included in the Prior Art Database: 2004-Feb-05
Document File: 10 page(s) / 18K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

C. Daboo: AUTHOR

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 19% of the total text.

Network Working Group C. Daboo

Request for Comments: 3685 Cyrusoft International, Inc.

Category: Standards Track February 2004

SIEVE Email Filtering: Spamtest and VirusTest Extensions

Status of this Memo

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.

Copyright Notice

Copyright (C) The Internet Society (2004). All Rights Reserved.

Abstract

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.

Table of Contents

1. Introduction and Overview . . . . . . . . . . . . . . . . . . 2

2. SIEVE Extensions . . . . . . . . . . . . . . . . . . . . . . . 3

2.1. General Considerations . . . . . . . . . . . . . . . . . 3

2.2. Test spamtest. . . . . . . . . . . . . . . . . . . . . . 3

2.3. Test virustest . . . . . . . . . . . . . . . . . . . . . 4

3. Security Considerations . . . . . . . . . . . . . . . . . . . 5

4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6

4.1. spamtest registration. . . . . . . . . . . . . . . . . . 6

4.2. virustest registration . . . . . . . . . . . . . . . . . 6

5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7

5.1. Normative References . . . . . . . . . . . . . . . . . . 7

5.2. Informative References . . . . . . . . . . . . . . . . . 7

6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7

7. Intellectual Property Rights Statement . . . . . . . . . . . . 7

8. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 8

9. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 9

Daboo Standards Track [Page 1]

RFC 3685 SIEVE Spamtest and VirusTest Extensions February 2004

1. Introduction and Overview

SIEVE scripts are frequently being used to do spam and virus

filtering based on either implicit script tests (e.g., tests for

'black-listed' senders directly encoded in the SIEVE script), or via

testing messages modified by some external spam or virus checker that

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

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

status using some syntax defined by the particular tool. Each user

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

synchronization with the third party tool as it gets update...