Client-side Spam filtering instructions
Email clients such as Mozilla Mail, Netscape Mail and Microsoft Outlook have the ability to 'filter' emails based on specific
pieces of information contained within an email message. Monash Spam client-side filters are filters that are created
within the email client that redirect emails that Monash has 'marked' as Spam to a specific 'Spam' folder.
The instructions will by default provide the same overall functionality as server-side
filtering, but they operate after the email has been received and proceed by the email client.
This has the disadvantage
requiring that emails be downloaded off the server prior to being proceed (which can be annoying if you access your
email over a slow modem link) and will not work if you either don't use an email client to access your staff email or
you are using one of the two Web-based email interfaces for a period of time (i.e. the
WebMail or my.monash portal interfaces).
NOTE: You can verify the name and version of email client that you are using in almost all email clients by
clicking on the Help->About menu item. This should tell you both the 'name' of the product and the
version number.
The steps outlined in the link below are for customers who use the Netscape v4.7X email client.
These steps will enable Spam filtering on your email account with email detected as Spam being placed
in a folder called 'Spam-30' (by default).
Spam filtering steps for Netscape
The steps outlined in the link below are for establishing a list of 'whitelisted' addresses that you
want to bypass the spam filtering process because they were previously detected as being Spam but were actually
a legitimate email. These steps are for customers who use the Netscape v4.7X email client.
Whitelist address steps for Netscape
The steps outlined in the link below are for customers who use the Mozilla v1.X or the Monash customised
'Monzilla' email client.
These steps will enable Spam filtering on your email account with email detected as Spam being placed
in a folder called 'Spam-30' (by default).
Spam filtering steps for Mozilla
The steps outlined in the link below are for establishing a list of 'whitelisted' addresses that you
want to bypass the spam filtering process because they were previously detected as being Spam but were actually
a legitimate email. These steps are for customers who use the Mozilla v1.X or the Monash customised
'Monzilla' email client.
Whitelist address steps for Mozilla
The steps outlined in the link below are for customers who use the non-ITS supported Microsoft Outlook
email client. These steps will enable Spam filtering on your email account with email detected as Spam being placed
in a folder called 'Spam-30' (by default).
Spam filtering steps for Outlook
The steps outlined in the link below are for customers who use the non-ITS supported Unix based email accounts
email client. These steps will enable Spam filtering on your email account with email detected as Spam being placed
in a folder called 'spam' (by default).
Spam filtering steps for Unix
Troubleshooting
When configuring side-side filters there have been a number of common issues that staff have experienced. These
issues are documented at the following web-site:
Troubleshooting Client-side filters
Once you have set and enabled the Spam filter within your email client, you can verify their operation
by using the following two sites. These sites allow you to send a test 'Spam' email with your choice of Spam score
so you can test emails that were marked below, at and above the Spam Threshold
that you have set (by default the threshold is 5). You can also send a test email with the 'FROM' address
that matches the sender of an email which keeps being marked as Spam but is actually legitimate. This is useful
to verify the functionality of the 'whitelist' settings.
Send test Spam message
Send email for whitelist testing
|
