Jump to content

This is the support site for Andrews & Arnold Ltd, a UK Internet provider. Information on these pages is generally for our customers but may be useful to others, enjoy!

Sieve Filtering: Difference between revisions

Interaction between Spam checking and Sieve filtering
(You can edit in raw format)
Tags: Mobile edit Mobile web edit
(Interaction between Spam checking and Sieve filtering)
 
(5 intermediate revisions by the same user not shown)
= What is Sieve filtering? =
 
At a basic level, Sieve is a system whereby the server is given rules by you to process incoming email - e.g. forward emails, discard emails, or filter your email into folders. It then means that, whatever email program you use, your email is already filed away in to their correct folder according to your needs. Sieve can do more than just move email into folders.
 
It is helpful if you:
*Read email from a number of devices
 
This page explains how to connect tto our sieve server using roundcubeRoundcube andor aother ThunderbirdManageSieve addonclient software, and gives some examples and also further about sieveSieve and the features we have enabled
 
=Sieve Server Settings=
*Maximum number of actions = 128
 
# Numbered list item
== Creating Sieve Filters ==
 
=Other Sieve Notes=
*When using fileinto: with :create, a new folder will be created if it does not already exist, this is normal. In this case, the new folder will be subscribed to automatically. -You may need to restart your client, or collapse and reopen the folder list (e.g. Thunderbird), for it to notice that there is a new folder that should be listed.
*spam folder: If you have a folder called 'spam' then email which is marked as spam will end up there bypassing any Sieve filters. If you do not wish to happen then rename or delete the folder called 'spam', and add a filter to move spam marked messages to another folder (e.g. junk, rubbish, etc.) '''Update November 2023''': this doesn'tappears seemnot to be the case - itthe looks'spam' likefolder is automatically created, but messages are processed by the spam engines, and then passed through Sieve filtering so you can decide what to do with the spam using your Sieve rules. To recreate the previous behaviour (and perhaps extend it a little) you might need a rule like:
require ["fileinto","mailbox"];
if exists "X-Spam-Flag" {
if header :is "X-Spam-Flag" "YES" {
if exists "X-Spam-Bar" {
# 20 OR MORE +
if header :contains "X-Spam-Bar" "++++++++++++++++++++" {
# Can't reject, not supported
fileinto :create "bad-spam";
stop;
}
}
fileinto :create "spam";
stop;
}
}
 
=Some Examples=
editor
471

edits