RFC 3894: Sieve Extension: Copying Without Side Effects
In plain English — editorial summary, not part of the RFC
The Sieve scripting language allows users to control handling and disposal of their incoming e-mail. By default, an e-mail message that is processed by a Sieve script is saved in the owner's "inbox". Actions such as "fileinto" and "redirect" cancel this default behavior. This document defines a new keyword parameter, ":copy", to be used with the Sieve "fileinto" and "redirect" actions. Adding ":copy" to an action suppresses cancellation of the default "inbox" save. It allows users to add commands to an existing script without changing the meaning of the rest of the script. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3894
- Published
- October 2004
- Authors
- J. Degener
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3028Sieve: A Mail Filtering LanguageObsoleted
January 2001
- RFC 3734Extensible Provisioning Protocol (EPP) Transport Over TCPObsoleted
March 2004
- RFC 3646DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
December 2003
- RFC 3397Dynamic Host Configuration Protocol (DHCP) Domain Search OptionCurrent
November 2002
- RFC 28775250 Telnet EnhancementsObsoleted
July 2000
- RFC 4934Extensible Provisioning Protocol (EPP) Transport Over TCPObsoleted
May 2007
- RFC 2847LIPKEY - A Low Infrastructure Public Key Mechanism Using SPKMCurrent
June 2000
- RFC 2696LDAP Control Extension for Simple Paged Results ManipulationCurrent
September 1999
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?