Differences between revisions 10 and 11
Revision 10 as of 2017-01-09 06:07:32
Size: 2578
Editor: bonaccos
Comment:
Revision 11 as of 2017-01-09 06:07:50
Size: 2580
Editor: bonaccos
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
The Sieve mail filtering language [https://tools.ietf.org/html/rfc5228|(RFC 5228)] is a special data-driven language that is optimized to allow efficient server-side filtering of mails. A sieve mail filtering script can be installed from the user and is executed on the mail server at delivery of the mail to the user mailbox. Sieve is a modern alternative to the cryptic language of procmail filter scripts.<<BR>><<BR>> The Sieve mail filtering language [[https://tools.ietf.org/html/rfc5228|(RFC 5228)]] is a special data-driven language that is optimized to allow efficient server-side filtering of mails. A sieve mail filtering script can be installed from the user and is executed on the mail server at delivery of the mail to the user mailbox. Sieve is a modern alternative to the cryptic language of procmail filter scripts.<<BR>><<BR>>

The Sieve language

The Sieve mail filtering language (RFC 5228) is a special data-driven language that is optimized to allow efficient server-side filtering of mails. A sieve mail filtering script can be installed from the user and is executed on the mail server at delivery of the mail to the user mailbox. Sieve is a modern alternative to the cryptic language of procmail filter scripts.

The IETF Sieve working group has brought the following extensions to the base specification:

  • Body – allows a script to test the body of a message, not just its header. (RFC 5173)

  • Variables - allows the script to save and retrieve values in variables. (RFC 5229)

  • Vacation - specifies an action to send a response informing the sender that the recipient may be away. (RFC5230)

  • Relational tests - defines numeric tests, so that a script may test a field for a numeric value, and may test against the number of occurrences of a field. (RFC 5231)

  • IMAP4flags - allows a script to test and set a message's IMAP flags. (RFC 5232)

  • Subaddress - allows a script to test subaddresses of the form "user+detail@domain.example". (RFC 5233)

  • Spamtest and Virustest - allows a script to interface with implementation-dependent message filtering. (RFC 5235)

  • Date and Index Extensions (RFC 5260)

  • Editheader - allows a script to add and delete message header fields. (RFC5293)

  • Reject - allows messages to be rejected at either the LMTP/SMTP level or with an MDN or DSN. (RFC 5293)

  • Notifications - allows a script to trigger external notifications of email. (RFC 5435)

  • E-mail notifications - specifies notifications via e-mail. (RFC 5436)

  • XMPP notifications - specifies notifications via XMPP. (RFC 5437)

  • Checking - Mailbox status and accessing mailbox metadata. (RFC 5490)

  • MIME Part Tests, Iteration, Extraction, Replacement, and Enclosure (RFC 5703)

Managesieve

In modern mail systems the user has no longer file system access to any directory on the imap mail server. Therefore the user must be able to remotely manage his serverside sieve script. Managesieve is the solution to this task. It's a management protocol specification (RFC 5804) over which the sieve script can be manipulated remotely with a management service running on the imap server. All sieve plugins for webmailer/email programs and standalone client sieve editor programs are based on the Managesieve protocol.

Email/SieveIntro (last edited 2020-09-10 15:03:19 by gfreudig)