rigacci.org

User Tools

Site Tools

Trace:
doc:appunti:linux:sa:sieve_filtering_examples

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
doc:appunti:linux:sa:sieve_filtering_examples [2023/03/24 12:49] – [Filtering with Sieve] niccolodoc:appunti:linux:sa:sieve_filtering_examples [2023/03/24 12:59] (current) – [Filtering with Sieve] niccolo
Line 4: Line 4:
  
 The [[https://doc.dovecot.org/configuration_manual/sieve/pigeonhole_sieve_interpreter/|Pigeonhole Sieve Interpreter]] provides the //pipe//, //filter// and //execute// commands, where the //pipe// was the older one implemented (starting from v0.2). Currently the more modern //execute// command can be used instead of the //pipe// one. The [[https://doc.dovecot.org/configuration_manual/sieve/pigeonhole_sieve_interpreter/|Pigeonhole Sieve Interpreter]] provides the //pipe//, //filter// and //execute// commands, where the //pipe// was the older one implemented (starting from v0.2). Currently the more modern //execute// command can be used instead of the //pipe// one.
 +
 +The following recipes were tested into a **$HOME/.dovecot.sieve** file, i.e. the users's Sieve filter applied by the Dovecot Local Delivery Agent.
 +
 +FIXME Document the timeout options.
  
 ===== Sender ===== ===== Sender =====
  
-Storing in different folder upon (envelope) sender:+Storing messages in different folder upon (envelope) sender:
  
 <code> <code>
Line 18: Line 22:
 ===== Recipient ===== ===== Recipient =====
  
-Storing in different folder upon destination address:+Storing messages in different folder upon destination address:
  
 <code> <code>
Line 96: Line 100:
 } }
 </code> </code>
 +
 +Here the **execute** //command// is called with the **:pipe** //tag//, this causes the execution of the external program much like the older ''pipe'' command.
  
 The **execute** command is not considered a final action (which "consumes" the message), so the **keep** action is eventually taken, saving the message into the INBOX. The **execute** command is not considered a final action (which "consumes" the message), so the **keep** action is eventually taken, saving the message into the INBOX.
doc/appunti/linux/sa/sieve_filtering_examples.1679658554.txt.gz · Last modified: 2023/03/24 12:49 by niccolo