RFC 5429: Sieve Email Filtering: Reject and Extended Reject Extensions
In plain English — editorial summary, not part of the RFC
This memo updates the definition of the Sieve mail filtering language "reject" extension, originally defined in RFC 3028. A "Joe-job" is a spam run forged to appear as though it came from an innocent party, who is then generally flooded by automated bounces, Message Disposition Notifications (MDNs), and personal messages with complaints. The original Sieve "reject" action defined in RFC 3028 required use of MDNs for rejecting messages, thus contributing to the flood of Joe-job spam to victims of Joe-jobs. This memo updates the definition of the "reject" action to allow messages to be refused during the SMTP transaction, and defines the "ereject" action to require messages to be refused during the SMTP transaction, if possible. The "ereject" action is intended to replace the "reject" action wherever possible. The "ereject" action is similar to "reject", but will always favor protocol-level message rejection. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5429
- Published
- March 2009
- Authors
- A. Stone
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 14
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3028 (2001)
- RFC 5228 (2008)
- RFC 5429 (2009)
Read the full history of Sieve Email Filtering: Reject and Extended Reject Extensions →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5550The Internet Email to Support Diverse Service Environments (Lemonade) ProfileCurrent
August 2009
- RFC 5784Sieve Email Filtering: Sieves and Display Directives in XMLCurrent
March 2010
- RFC 6009Sieve Email Filtering: Delivery Status Notifications and Deliver-By ExtensionsCurrent
October 2010
- RFC 5068Email Submission Operations: Access and Accountability RequirementsUpdated
November 2007
- RFC 9422The LIMITS SMTP Service ExtensionCurrent
February 2024
- RFC 5463Sieve Email Filtering: Ihave ExtensionCurrent
March 2009
- RFC 5337Internationalized Delivery Status and Disposition NotificationsObsoleted
September 2008
- RFC 4952Overview and Framework for Internationalized EmailObsoleted
July 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?