Email Feedback Report Type Value: not-spam
RFC 6430
|
| Document |
Type |
|
RFC - Proposed Standard
(November 2011; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Replaces |
|
draft-li-marf-not-spam-feedback
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Murray Kucherawy
|
|
Shepherd write-up |
|
Show
(last changed 2011-08-02)
|
| IESG |
IESG state |
|
RFC 6430 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Pete Resnick
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force (IETF) K. Li
Request for Comments: 6430 B. Leiba
Category: Standards Track Huawei Technologies
ISSN: 2070-1721 November 2011
Email Feedback Report Type Value: not-spam
Abstract
This document defines a new Abuse Reporting Format (ARF) feedback
report type value: "not-spam". It can be used to report an email
message that was mistakenly marked as spam.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6430.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Li & Leiba Standards Track [Page 1]
RFC 6430 Email Feedback Type: not-spam November 2011
Table of Contents
1. Introduction ....................................................2
1.1. Discussion .................................................2
2. Feedback Report Type: not-spam ..................................3
3. Example .........................................................3
4. Security Considerations .........................................5
5. IANA Considerations .............................................6
6. Acknowledgements ................................................6
7. References ......................................................6
7.1. Normative References .......................................6
7.2. Informative References .....................................6
1. Introduction
In RFC 5965 [RFC5965], an Abuse Reporting Format (ARF) is defined for
reporting email abuse. Currently, two feedback report types are
defined that are related to the spam problem and that can be used to
report abusive or fraudulent email messages:
o abuse: indicates unsolicited email or some other kind of email
abuse.
o fraud: indicates some kind of fraud or phishing activity.
This specification defines a new feedback report type: "not-spam".
It can be used to report a message that was mistakenly marked as
spam.
1.1. Discussion
In some cases, the email client receives an email message that was
incorrectly tagged as spam, perhaps by the email system, or
accidentally by the user. The email client accepts the end user's
"not-spam" report instruction, retrieves information related to the
message, and reports this email as not-spam to the email operator.
When the email operator receives the report, it can determine what
action is appropriate for the particular message and user. (The
requirement for a not-spam report type is from the Open Mobile
Alliance (OMA) Spam Report Requirement Document [OMA-SpamRep-RD].)
For example, in response to a "not-spam" report, the email system can
remove the spam tag or otherwise reclassify the message, possibly
preventing similar email for this user from being marked as spam in
the future. The report can be used to adjust the training of an
automated classifier. After processing the report, the email
Li & Leiba Standards Track [Page 2]
RFC 6430 Email Feedback Type: not-spam November 2011
operator might send a notification to the email client about the
processing result (for example, by moving the message from one
mailbox to another, such as from "Junk" to "Inbox").
In most cases, "not-spam" reports will probably not be taken on their
Show full document text