A MIME Encoding for Spam Inoculation Messages
draft-yerazunis-spamfilt-inoculation-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Bill Yerazunis | ||
| Last updated | 2004-02-16 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes in detail a method for encapsulating an email message or text sample for the purpose of training (or 'inoculating') a mail filter. The sample messages or text (the 'payload') provide the contextual information necessary for the filter to reject ('spam') or accept ('non-spam') the message being inoculated, or messages similar in design. RFC 1521 defines the MIME format. This document expands on this by adding an 'inoculation' MIME subtype, and also adds additional header fields necessary to the functionality being provided. This message format is designed to enable different mail filters of different design to communicate inoculations with one another using the MIME subtype introduced.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)