Mulberry has a built-in facility called Local Rules (under its Mailbox menu) with which you can set up simple filtering for your email. This uses client-side filtering as opposed to server-side filtering, so is less efficient and only works when you are logged in to Mulberry.
Local Rules filtering is an alternative to the Sieve server-side filtering system, which for technical reasons cannot be made available to Mulberry users at present. A server-side filter with limited functionality is available via My Accounts. For more information, see our guide to server-side filtering.
The following guide is an introduction to Mulberry Local Rules, but is not a complete description. See the Where to find out more section for more information.
In Mulberry, a Rule consists of one or more conditions or search criteria to be met, and one or more actions to be taken. The conditions and actions apply to email messages and mailboxes. For example, a condition might be for an email message to have come from a particular sender's address or mail domain. An example action is for the email to be moved to another mailbox. A Rule is normally associated with one or more Triggers which define an event when that Rule should be invoked. An example of a Trigger event is when a mailbox is opened or closed.
Follow the steps shown below to create a Rule.
![[Local tab in Rules window]](/its/images/mulberry-rules-panel-arrowed.jpg)
button, then enter a
suitable name for this Rule in the box at the top:![[Name box in Edit Rule window]](/its/images/mulberry-rules-rulewindow-arrowed.jpg)
![[Example Find Messages condition]](/its/images/mulberry-sieve-fromexample.jpg)
Follow the steps shown below to create a Trigger.
button,
then add a suitable name for the Trigger in the box:![[Name box in Edit Trigger window]](/its/images/mulberry-rules-triggerwindow-arrowed.jpg)
![[More Targets button in Edit Trigger window]](/its/images/mulberry-rules-triggerwindow-applynone.jpg)
You need to associate a Rule with a Trigger before it will start working. The table given below shows the available trigger events:
| Trigger event | What it means |
|---|---|
| New Messages Arrive | Operates when new messages are detected in a mailbox that is open or being checked. |
| Opening a Mailbox | Operates whenever a mailbox is opened. |
| Closing a Mailbox | Operates whenever a mailbox is closed. |
| All | Operates when any of the above three events occur. |
| Never | Does nothing: this is used to disable a trigger without deleting it. |
In the Rules window, double-click on the Rule you created earlier, then click the
button. Then, from the list that
appears, select the Trigger you want to associate with this Rule. Then click OK.
Whenever you need to make any changes to a Rule, you just need to follow these steps:
Spam is difficult to identify reliably through automatic means. The Sussex mail system currently runs a system called SpamAssassin which applies complex tests to incoming messages to try to intercept spam. This happens before messages are actually delivered. Although SpamAssassin currently intercepts and rejects up to 250,000 spam emails every day, many still get through and it can never be fully effective. If you are being troubled by persistent spam from a particular source, you can create rules to discard it, but you need to be very careful. Some of the examples in the next section may help you.
For this, your Rule needs to examine the 'From:' address (the sender's address), in the incoming message. Let's suppose you want to put all messages coming from salesteam@example.com into a folder called JUNK. Your Rule could look like this:
![[Example Rule for ignoring address]](/its/images/mulberry-rules-movejunkaddr.jpg)
Note how this Rule has been called junkmail in the example; you could add other addresses for which you want to apply the same treatment, by clicking the More Choices button. Click OK when you have finished creating or editing the Rule.
The domain is that part of an email address which appears to the right of the '@' symbol. For example, example.com (as in another@example.com) and sussex.ac.uk (as in a.n.other@sussex.ac.uk) are both domains. If you want to 'junk' all email from a particular domain then you can use the same method as that described in the previous example, and just specify the mail domain instead of the full address, such as @example.com (it's best to include the @ sign together with the domain).
Much junk email is readily identifiable from certain key words in the subject line. Suppose you wanted to 'junk' any messages that have the word 'anatrim' in the subject line. You could use a Rule like this:
You could add tests for other keywords by clicking the More Choices button.
You can do more than one test on any one message. For example, you might want to combine tests for both a mail domain (in the From line) and a keyword (in the Subject line), or you might want to test for several different keywords. For each extra test, you just need to click the More Choices for each extra test you want to perform, as illustrated below:
Notice that the examples show unwanted mail being moved into nominated junk mail folders instead of being discarded altogether (for example using the Expunge Message action). This is because there is a danger that immediate expunging might discard genuine messages. It is safer to move these messages into a specially reserved mailbox, then at regular intervals check that mailbox yourself for any genuine email, move any to another folder, and delete and expunge the rest. The following detail from the Actions section of a Rule entry dialogue box illustrates how to use the Move Message To action:
In this example, we are saving unwanted messages to a mailbox called
'SPAM'. Note the use of Mail/,
which prefixes the mailbox name. You will need this if your SPAM mailbox is stored in
your Mail/ hierarchy, if you have one, but you should omit the Mail/ part if
the SPAM mailbox is stored
in your topmost mailstore hierarchy. When choosing a mailbox to receive such mail,
you can use the browse (
) button at the far end
of the text box instead.
It's extremely important that you frequently review the contents of your nominated mailbox, checking quickly for 'genuine' messages, and deleting everything else therein. You must never leave the mailbox to grow unimpeded: if you do, this will waste a huge amount of disk space (remember that you share the system with around 14,000 other people!) and could overdraw your disk quota.
Circumstances for filter rules may change. For example, junk mail from a particular domain which you have been filtering, may stop coming if that domain ceases to exist or stops sending junk. In such cases you should consider removing the filter rule that handles this so as to conserve resources. The less the mail server is asked to do, the more efficiently it will work for everyone.
Do not be tempted to discard mail from an address or domain from which you have received only a few junk mails. 'Spammers' tend to use false addresses and change addresses frequently, so it's only worth filtering junk email from persistent sources. It's better just to "Ignore, Delete and Forget" occasional junk mail rather than set up a filter against it.
You can find out more about Mulberry Local Rules by reading pages 167-172 and pages 175-186 of the online Mulberry Reference Manual.
If you are a University of Sussex student or staff member and you have any queries about Local Rule filtering, please contact us at IT Services Online Support.
Updated on 24 August 2010